Comments
-
Hi Jeff, I have encountered several cases where there was lots of events about sensors went to Unknown status and later Up again. This issues were also related to upgrade to NPM 10.7. I can't tell if it also your case but in NPM 10.7 there is Topology turned on for all nodes which supports it. Unfortunately in some cases…
-
Hi Dennis, I got the case and already responsed, I have found a thread where was meantioned very similar problem. I hope it helps you.
-
Hi, This comes from fact that Cisco devices report statuses for these sensors even the related interfaces are shutdown. That's the reason why NPM still gets even these sensors.
-
Thank you for closer look, however even though it is not easy to spot the issue. As I stated in previous comment: If you can, please create a support ticket and attach diagnostics and snmp walks. This really helps to discover the issue and hopefully fix it. Thanks for understanding.
-
Sorry there is no resolution to this issue yet. We are still awaiting diagnostics and snmp walks to be able to reproduce and eliminate the issue. If you can, please create a support ticket, attach diagnostics and snmp walks.
-
Hi, this kind of issues are quite common, especially with Cisco. They report something to command line and something different via SNMP (NPM reads everything via SNMP). I cannot tell you for sure that this is what happened in your case, but it is most probable. As you can notice the sensor is named "Sw1, Ps2 Faulty, RPS…
-
Hello, I am sorry, but I can't tell directly what's wrong with your device. Please create a support ticket and attach diagnostics and SNMP walks for both devices - for the one which seems to show correct values in Orion and the one which you have trouble with. To speed things up please write down the ticket number here so…