KSC Reports showing incorrect values during collection after a active/standby supervisor failover
Description
Environment
System Details
--------------
OpenNMS Version: 1.8.12-1
Java Version: 1.5.0_18 Sun Microsystems Inc.
Java Virtual Machine: 1.5.0_18-b02 Sun Microsystems Inc.
Operating System: Linux 2.6.18-194.26.1.el5 amd64
Servlet Container: jetty/6.1.24 (Servlet Spec 2.5)
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_7) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.71 Safari/534.24
Acceptance / Success Criteria
None
Attachments
1
Lucidchart Diagrams
Activity
Show:
Jason Lixfeld May 31, 2011 at 9:29 PM
Same issue here. Not limited to KSC reports, but node resource graphs are broken as well if a custom timeframe is selected where the supervisor switchover time intersects the start and end times of a graph custom timeframe.
Details
Details
Assignee
Unassigned
UnassignedReporter
Eric W Abrahamsen
Eric W AbrahamsenComponents
Priority
MajorPagerDuty
PagerDuty Incident
PagerDuty
PagerDuty Incident
Created May 31, 2011 at 10:47 AM
Updated September 21, 2021 at 6:24 PM
I have observed an issue where if a Cisco device collecting SNMP interface data and also have redundant supervisor engines during the failover from active to standby the data shows in the KSC reports incorrectly. This has been observed using NX-OS, IOS, and IOS XR Cisco platforms. The failover can be either due to a fault or due to a stateful switchover, either way the graphs show incorrect data. Please see the image for the example graph.
-Eric