Loading...
Loading...
Cisco-IOS-XR-shellutil-oper:system-time/uptime stops working
1. sh telemetry model-driven subscription internal will show the sysdb path as resolved , however all get requests will fail. Router#sh telemetry model-driven subscription sub-interface-models internal Mon Jul 31 14:14:04.387 UTC Subscription: sub-interface-models ------------- State: ACTIVE Sensor groups: Id: sg-interface-models Sensor Path: Cisco-IOS-XR-shellutil-oper:system-time/uptime Sensor Path State: Resolved <<<<<<<< Id: 19 Sample Interval: 15000 ms Encoding: gpb Num of collection: 9385 Collection time: Min: 0 ms Max: 0 ms Total time: Min: 20 ms Avg: 23 ms Max: 33 ms Total Deferred: 0 Total Send Errors: 0 Total Send Drops: 0 Total Other Errors: 9385 No data Instances: 0 Last Collection Start:2017-07-31 14:12:40.2678941204 +0000 Last Collection End: 2017-07-31 14:12:40.2678967204 +0000 Sensor Path: Cisco-IOS-XR-shellutil-oper:system-time/uptime Sysdb Path: /oper/clock/gl/system_uptime Count: 9385 Method: GET Min: 0 ms Avg: 0 ms Max: 0 ms Item Count: 0 Status: Active Missed Collections:11996 send bytes: 0 packets: 0 dropped bytes: 0 success errors deferred/drops Gets 0 9385 <<<<<<< List 0 0 Datalist 0 0 Finddata 0 0 GetBulk 0 0 Encode 0 0 Send 0 0 2. Verifying via sysdbcon will show below error message sysdbcon:[m]/oper/clock/gl/> ls [bag] 'clock' [bag] 'system_uptime' sysdbcon:[m]/oper/clock/gl/> get system_uptime %SYSDB-SYSDB-4-SC_GET : [Sysdbcon] While fetching item system_uptime the following error occurred: 'sysdb' detected the 'warning' condition 'Multiple EDMs incorrectly returned more than one successful result for an operation' sysdbcon:[m]/oper/clock/gl/>
1. Process restart showd_lc process to recover Router#process restart showd_lc Tue Aug 1 13:49:17.973 UTC Aug 1 13:49:18 testing sysmgr_control: [68276]: %OS-SYSMGR-4-PROC_RESTART_NAME : User cisco (con0_RP0_CPU0) requested a restart of process showd_lc at 0/RP0/CPU0
Based on the DE analysis the issue occurs when two different threads in the showd_lc process have registered an EDM for the clock path and so both are replying, leading to this issue. This can be verified using below CLI Router#sh sysdb registrations edm shared-plane | in clock Mon Jul 31 15:01:23.818 UTC Jul 24 15:30:14.780 00198 0/RP0/CPU0 7822 0x00005f '/oper/clock/gl/' Jul 24 15:30:14.777 00198 0/RP0/CPU0 7825 0x00005d '/oper/clock/gl/'
Cisco Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.