I am doing initial setup of a SA box , and just wanted to check ping access from the Internal & External ports from the GUI , but checking 4 different SSL appliances all on codes varying from 6.5 to 7.1 and none of them have the option to ping from the external interface....
Am I missing something ? I.e. is this something that is explicitly not allowed or does this need to be enabled somewhere ?
I know this is possible from the Console , but I was just interested to know about the GUI....
Solved! Go to Solution.
Thnx for Reply ,, doesn't make sense though why would this function be specifically "removed" from the GUI , just wondering is its been done for some bizarre security reason.
i dont need it , but its just weird why would you do the Internal and not the External
I can tell you several JTAC case where troubleshooting looked like:
- enable debugging, collect systemsnapshot, send it to JTAC (waiting several days til JTAC decrypted and analysed the snapshot, because this could do only a few JTAC guys), getting feedback to collect the next snapshots :-(
JTAC requests for the snapshot looked like:
- enable debugging before (!) problem occurrs (not sure how I should do that)
- take snapshot within short time after problem occured to find the requested infos in the snapshot (no one could told me the time definition of short time)
- send snapshot to JTAC
2. there are a lot of features / things, which were helpful to know, some examples:
- logging of leader change (only possible via systemsnapshot)
- which process uses which cpu power / memory (not sure if it«s implemented in the snapshot)
- snmp support for User Monitoring (e.g. active Meetings, active User per Meeting or in total, active NC Clients, etc)
the parameters must be somewhere on the box, cause the WebGUI shows some of these parameters
- monitoring BW usage of different IVEs, Roles, or Implementations like Secure Meeting, Network Connect, etc)
... but I think we don«t have to discuss the Troubleshooting methods at this board
Thank you for clarifying the concerns. Yes, there is some information that is only in the system snapshot, such as specific process usage and if there is something that looks like it could be system-side, we need that and there is some delay (apologies).
The leader in a cluster means nothing so it is not logged, you are correct.
The logging details you mentioned would be nice to have; these are best brought up through your local account team as a request to implement.
You are correct, specific issues probably ought not to be discussed publicly here; please feel free to PM me if you have any specific questions that I _may_ be able to answer or get you to the right people (or JTAC case you would like me to look at to assist in moving along).
"The leader in a cluster means nothing so it is not logged"
--> that«s not correct.
short hint: which node in an active/passive Cluster perform the "Virus Signature Download" ?
Should be the one hosting the VIP/the node that hits the timer to download first.
If you are seeing something different, have you worked with JTAC on this? (or is that where the frustration is from on snapshots?)
If the download is _only_ being done on the leader node, it is the first time that has meant anything.
it«s every time the leader who perfom the update, not the active.
and therefore it would be great to have a look, when the leader is changing
We need a long time with JTAC to figure that out :-)
Oh my, that is concerning.
Glad to hear you are working with JTAC (succesfully-ish) to find out more of what is happening.