@zanyterp: 1. Troubleshooting: 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 greets sthon
... View more