Showing results for 
Search instead for 
Did you mean: 

CSCug28911 - NSR state discrepancy between summary and full command output

I see where this is applicable to 4.3.x code... but why would this still be showing up in 6.3.3 code?


asr9k-k9sec-supp, V 6.3.3[Default], Cisco Systems, at disk0:asr9k-k9sec-supp-6.3.3
Built on Tue Aug 28 18:31:48 EST 2018

RP/0/RSP1/CPU0:CORE-02#sh redundancy
Tue Jan 22 08:52:36.407 EST
Redundancy information for node 0/RSP1/CPU0:
Node 0/RSP1/CPU0 is in ACTIVE role
Node Redundancy Partner (0/RSP0/CPU0) is in STANDBY role
Standby node in 0/RSP0/CPU0 is ready
Standby node in 0/RSP0/CPU0 is NSR-not-configured
Node 0/RSP1/CPU0 is in process group PRIMARY role
Process Redundancy Partner (0/RSP0/CPU0) is in BACKUP role
Backup node in 0/RSP0/CPU0 is ready
Backup node in 0/RSP0/CPU0 is NSR-ready

Group Primary Backup Status
--------- --------- --------- ---------
v6-routing 0/RSP1/CPU0 0/RSP0/CPU0 Ready
mcast-routing 0/RSP1/CPU0 0/RSP0/CPU0 Ready
netmgmt 0/RSP1/CPU0 0/RSP0/CPU0 Ready
v4-routing 0/RSP1/CPU0 0/RSP0/CPU0 Ready
central-services 0/RSP1/CPU0 0/RSP0/CPU0 Ready
dsc 0/RSP1/CPU0 0/RSP0/CPU0 Ready
dlrsc 0/RSP1/CPU0 0/RSP0/CPU0 Ready

Reload and boot info
A9K-RSP880-LT-TR reloaded Tue Jan 22 00:24:49 2019: 8 hours, 27 minutes ago
Active node booted Tue Jan 22 01:30:12 2019: 7 hours, 22 minutes ago
Last switch-over Tue Jan 22 01:37:28 2019: 7 hours, 15 minutes ago
Standby node boot Tue Jan 22 02:41:18 2019: 6 hours, 11 minutes ago
Standby node last went not ready Tue Jan 22 02:42:28 2019: 6 hours, 10 minutes ago
Standby node last went ready Tue Jan 22 02:43:28 2019: 6 hours, 9 minutes ago
There have been 2 switch-overs since reload

Active node reload Cause: MBI-HELLO reloading node on receiving reload notification
Standby node reload "Cause: MBI-HELLO reloading node on receiving reload notification"

Everyone's tags (6)
CreatePlease to create content
Content for Community-Ad
July's Community Spotlight Awards