Talking about the output of command [show redundancy] in ASR9K 6.2.3

[LEO HOU]

Hello, engineers,

When performing command  [show redundancy]  in ASR9K 6.2.3, i found something different with asr9k 5.3.3.

Please have a look at  below output.

RP/0/RSP1/CPU0:PE1#sh redundancy
Wed Aug 21 05:50:36.659 UTC
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

 In green highlighted in ACTIVE role, Standby node in 0/RSP0/CPU0 is NSR-not-configured

however in process group PRIMARY role, Backup node in 0/RSP0/CPU0 is NSR-ready,

I am confused by the difference between ACTIVE role and process group primary role, standby node and backup node,

and why NSR status changed from not configured to ready when role changed.

Thanks 

[Giuseppe Larosa · Accepted solution]

Hello Leo,

I have tried to read the command reference for the command show redundancy

I have found the following link:

https://www.cisco.com/c/en/us/td/docs/routers/asr9000/software/asr9k-r6-4/system-management/command/reference/b-system-managment-cr-asr9000-64x/b-system-managment-cr-asr9000-64x_chapter_01001.html#wp2934003239

it does not provide a complete explanation of your output.

RP/0/RSP1/CPU0:PE1#sh redundancy
Wed Aug 21 05:50:36.659 UTC
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

According to the command reference we see that a route processor "global" state can be Active or Standby.

However, there is no mention of the second part of your output.

It looks like your system has a "subset" of features named primary group and for them the Active RSP is Primary, the standby RSP is backup and for this "subset" of features the standby RSP is Backup, Ready and NSR-ready.

Non Stop Routing Ready.

Ideally we would like to see standby is NSR-ready and not standby is NSR-not configured.

So it looks like there are some protocols or processes that are in NSR and others that are not.

Review the node configuration and look for possible specific settings regarding NSR on each protocol.

Hope to help

Giuseppe