Yet another TMS thread

[Morgan81]

I know there are a bunch of threads on this already, half I've probably started, but I was wondering if anyone had seen this before or any similar problems.
When a system is not responding, and the event notifications are setup correctly for a "Lost Response" I have seen multiple Tandbergs not send a notification. We have almost 300 systems loaded worldwide but it's a dedicated server so I don't think it would be overwhelming it with SNMP traps. It's just strange that sometimes things work like this and sometimes they don't.

[Sean Lessman]

I know there are a bunch of threads on this already, half I've probably started, but I was wondering if anyone had seen this before or any similar problems.
When a system is not responding, and the event notifications are setup correctly for a "Lost Response" I have seen multiple Tandbergs not send a notification. We have almost 300 systems loaded worldwide but it's a dedicated server so I don't think it would be overwhelming it with SNMP traps. It's just strange that sometimes things work like this and sometimes they don't.
Hi,

You have sniffed the codec that isn't sending the trap? Or you have checked the logs on TMS and it never received them?

Also, if you can details on codec software level and TMS software level that would be great.

Sean

[Morgan81]

E4.0 is on the codec, TMS 8.0 and the logs in TMS show that it generates other traps right before it lost response but, since the codec got turned off, it wouldn't genererate a trap for it, it would have to be sent by the TMS server, or am I mistaken?

[dbl]

Check that the TMSWatchdogScanner service is running proparly. The codec does (for obvious reasons :) ) not send out a lost response-trap, but this "trap" is logged when the watchdogscanner (that periodically checks the systems) looses connection with the system. When TMS regains contact a got response "trap" is logged.