Anybody who would like to take stab on this? Appreciate any assistance, suggestion or recommendation the community can share.
We have this issue in 11.5 and after upgrading to 12 it seems to be fine now.
1 of 1 people found this helpful
This is a common problem but if you dissect it a little it will make sense
- The Cisco graph which is derived from on-board CPU load history shows the spike
- The Orion graph which is derived from SNMP gathered history shows a data gap.
- When the Cisco device goes to 100% CPU, it's too busy to respond to SNMP queries from Orion and thus there is no data point to graph
- When the CPU comes out of 100% utilization, SNMP can reply to Orion and you get data points again
Observation: The rising and falling edges of the Orion graph should line up with the device going into and coming out of 100% CPU utilization.
Observation: This is not Orion or Cisco version dependent.
Solution 1: Increase the SNMP timeout for polling this device (All devices would be a bad idea). This MAY give SNMP time to reply to Orion.
Solution 2: Write an alert that triggers when a device returning valid data points. This is the UNKNOWN state.