Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
8558
Views
10
Helpful
8
Replies

I can't bring my system full "NSR-ready"!

alain.schmoutz
Level 1
Level 1

‎12-27-2013 04:48 AM

Hi all,

I can't bring my system full "NSR-ready"!

The standby RSP of the "Backup-DSC" chassis stay in "NSR-not-Configured" state!

#############################################################################

RP/0/RSP0/CPU0:NFR-NORD-AGGR-PE01#show redundancy

Mon Dec 23 11:21:40.868 CET

Redundancy information for node 0/RSP0/CPU0:

==========================================

Node 0/RSP0/CPU0 is in ACTIVE role

Node Redundancy Partner (0/RSP1/CPU0) is in STANDBY role

Standby node in 0/RSP1/CPU0 is ready

Standby node in 0/RSP1/CPU0 is NSR-ready

Node 0/RSP0/CPU0 is in process group PRIMARY role

Process Redundancy Partner (1/RSP1/CPU0) is in BACKUP role

Backup node in 1/RSP1/CPU0 is ready

Backup node in 1/RSP1/CPU0 is NSR-ready

Group                    Primary               Backup                Status        

---------                     ---------                  ---------                  ---------     

v6-routing              0/RSP0/CPU0     1/RSP1/CPU0     Ready         

mcast-routing         0/RSP0/CPU0     1/RSP1/CPU0     Ready         

netmgmt                0/RSP0/CPU0     1/RSP1/CPU0     Ready         

v4-routing              0/RSP0/CPU0     1/RSP1/CPU0     Ready         

central-services      0/RSP0/CPU0     1/RSP1/CPU0     Ready         

dlrsc                       0/RSP0/CPU0     1/RSP1/CPU0     Ready         

dsc                         0/RSP0/CPU0     1/RSP1/CPU0     Ready         

Reload and boot info

----------------------

A9K-RSP440-TR reloaded Mon Dec 23 08:41:25 2013: 2 hours, 40 minutes ago

Active node booted Mon Dec 23 08:41:25 2013: 2 hours, 40 minutes ago

Standby node boot Mon Dec 23 08:41:24 2013: 2 hours, 40 minutes ago

Standby node last went not ready Mon Dec 23 11:09:38 2013: 12 minutes ago

Standby node last went ready Mon Dec 23 11:09:38 2013: 12 minutes ago

There have been 0 switch-overs since reload

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

Standby node reload "Cause: User initiated reload rack"

Redundancy information for node 1/RSP1/CPU0:

==========================================

Node 1/RSP1/CPU0 is in ACTIVE role

Node Redundancy Partner (1/RSP0/CPU0) is in STANDBY role

Standby node in 1/RSP0/CPU0 is ready

Standby node in 1/RSP0/CPU0 is NSR-not-configured

Reload and boot info

----------------------

A9K-RSP440-TR reloaded Mon Dec 23 08:22:43 2013: 2 hours, 58 minutes ago

Active node booted Mon Dec 23 08:22:36 2013: 2 hours, 59 minutes ago

Last switch-over Mon Dec 23 11:08:47 2013: 12 minutes ago

Standby node boot Mon Dec 23 11:09:22 2013: 12 minutes ago

Standby node last went not ready Mon Dec 23 11:10:18 2013: 11 minutes ago

Standby node last went ready Mon Dec 23 11:11:18 2013: 10 minutes ago

There has been 1 switch-over since reload

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

RP/0/RSP0/CPU0:NFR-NORD-AGGR-PE01#

#############################################################################

My config:

Version:

Cisco IOS XR Software, Version 4.3.2[Default]

ROM: System Bootstrap, Version 0.71(c) 1994-2012 by Cisco Systems,  Inc.

#############################################################################

RP/0/RSP0/CPU0:NFR-NORD-AGGR-PE01#show run mpls

Mon Dec 23 11:20:37.892 CET

mpls ldp

nsr

graceful-restart

...

!

RP/0/RSP0/CPU0:NFR-NORD-AGGR-PE01#show run router ospf

Mon Dec 23 11:18:33.469 CET

router ospf OSPF

nsr

nsf cisco

...

!

RP/0/RSP0/CPU0:NFR-NORD-AGGR-PE01#show run router bgp

Mon Dec 23 11:19:28.839 CET

router bgp 39440

nsr

bgp graceful-restart graceful-reset

bgp graceful-restart

...

!

Control-Links are OK:

RP/0/RSP0/CPU0:NFR-NORD-AGGR-PE01#show nv edge control control-link-protocols location 0/RSP0/CPU0

Mon Dec 23 11:27:17.654 CET

...

Priority lPort             Remote_lPort      UDLD STP

======== =====             ============      ==== ========

0        0/RSP0/CPU0/1     1/RSP0/CPU0/1     UP   Forwarding

1        0/RSP0/CPU0/0     1/RSP1/CPU0/1     UP   Blocking 

2        0/RSP1/CPU0/0     1/RSP1/CPU0/0     UP   On Partner RSP

3        0/RSP1/CPU0/1     1/RSP0/CPU0/0     UP   On Partner RSP

Active Priority is 0

Active switch is   RSP0

CLM Table version is 8

!

#############################################################################

Thanks for your support,

Best regards,

Alain Schmoutz

Labels:
0 Helpful
8 Replies 8

Rivalino Tamaela
Cisco Employee
Cisco Employee

‎12-27-2013 09:15 AM

Hello Alain,

This is expected. Only the active RP nodes which are running the primary NSR apps will be NSR-ready and active RP nodes which are not running any primary NSR apps will be NSR-not-configured. In your case, NSR apps are running primary on 0/RSP0/CPU0 and so it is a NSR-ready. But, there are no primary NSR apps running on 1/RSP0/CPU0 (only backup processes for NSR), so it is a NSR-not-configured.

HTH,

Rivalino

0 Helpful

alain.schmoutz
Level 1
Level 1
In response to Rivalino Tamaela

‎12-30-2013 01:06 AM

Hi Rivalino,

I don't agree.

If we compare the "show redundancy" with another system we have, we can see that the Standby node is also "NSR-Ready"!!

So I still don't understand what I am doing wrong in the configuration of my cluster..

The version of the system below is 4.2.3 while the system in the beginning of the discussion is in 4.3.2 version. This could make a difference?

#############################################################################

show redundancy

Mon Dec 30 09:50:18.729 CET

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-ready

Node 0/RSP1/CPU0 is in process group PRIMARY role

Process Redundancy Partner (1/RSP1/CPU0) is in BACKUP role

Backup node in 1/RSP1/CPU0 is ready

Backup node in 1/RSP1/CPU0 is NSR-ready


Group              Primary               Backup               Status        

---------               ---------                  ---------                  --------     

dsc                   0/RSP1/CPU0     1/RSP1/CPU0     Ready         

dlrsc                 0/RSP1/CPU0     1/RSP1/CPU0     Ready         

central-services 0/RSP1/CPU0    1/RSP1/CPU0     Ready         

v4-routing         0/RSP1/CPU0     1/RSP1/CPU0     Ready         

netmgmt           0/RSP1/CPU0     1/RSP1/CPU0     Ready         

mcast-routing    0/RSP1/CPU0     1/RSP1/CPU0     Ready         

v6-routing          0/RSP1/CPU0     1/RSP1/CPU0     Ready        


Reload and boot info

----------------------

A9K-RSP440-SE reloaded Wed Dec  4 05:26:13 2013: 3 weeks, 5 days, 4 hours, 24 minutes ago

Active node booted Wed Dec  4 05:26:13 2013: 3 weeks, 5 days, 4 hours, 24 minutes ago

Standby node boot Fri Dec 20 05:34:14 2013: 1 week, 3 days, 4 hours, 16 minutes ago

Standby node last went not ready Fri Dec 20 05:35:14 2013: 1 week, 3 days, 4 hours, 15 minutes ago

Standby node last went ready Fri Dec 20 05:36:14 2013: 1 week, 3 days, 4 hours, 14 minutes ago

There have been 0 switch-overs since reload


Active node reload "Cause: Backup DSC cannot go to Non-Backup DSC without reset - resetting node"

Standby node reload "Cause: self-reset to use new boot image"


Redundancy information for node 1/RSP1/CPU0:

==========================================

Node 1/RSP1/CPU0 is in ACTIVE role

Node Redundancy Partner (1/RSP0/CPU0) is in STANDBY role

Standby node in 1/RSP0/CPU0 is ready

Standby node in 1/RSP0/CPU0 is NSR-ready


Reload and boot info

----------------------

A9K-RSP440-SE reloaded Wed Dec  4 05:28:56 2013: 3 weeks, 5 days, 4 hours, 21 minutes ago

Active node booted Wed Dec  4 05:28:56 2013: 3 weeks, 5 days, 4 hours, 21 minutes ago

Standby node boot Fri Dec 20 05:19:05 2013: 1 week, 3 days, 4 hours, 31 minutes ago

Standby node last went not ready Fri Dec 20 05:20:16 2013: 1 week, 3 days, 4 hours, 30 minutes ago

Standby node last went ready Fri Dec 20 05:21:16 2013: 1 week, 3 days, 4 hours, 29 minutes ago

There have been 0 switch-overs since reload


Active node reload "Cause: Multiple Primary DSC Nodes: 0/RSP0/CPU0"

#############################################################################

Thanks for your help,

Alain

0 Helpful

smilstea
Cisco Employee
Cisco Employee
In response to alain.schmoutz

‎12-31-2013 05:16 AM

Hi Alain,

Yes this is due to the version. We changed this for 4.3.1

What Rivalino has said is correct about the behavior in 4.3.1+

HTH,

Sam

0 Helpful

cisco_lad2004
Level 5
Level 5
In response to smilstea

‎06-20-2014 03:20 AM

Hi Sam,

 

Are you aware of link where  can find this information documented ?

I was unable to find anything on release notes.

 

TIA 

 

/Samir

0 Helpful

smilstea
Cisco Employee
Cisco Employee
In response to cisco_lad2004

‎06-20-2014 05:25 AM

Hi Samir,

 

There is an enhancement bug, actually two, that was filed to address this, but this bug is not visible externally.

 

One of the bugs addressed some API changes, and the other addressed apps which needed to be changed in order to use the new API.

The API change came in 4.3.0 but not all the apps were changed over until 4.3.1

 

I can write up a document here on the supportforums addressing this change as I don't see the configuration guide or release notes as being the appropriate place to document the change.

 

Thanks,

Sam

 

cisco_lad2004
Level 5
Level 5
In response to smilstea

‎06-21-2014 06:20 AM

Many thanks Sam !

0 Helpful

Rivalino Tamaela
Cisco Employee
Cisco Employee
In response to alain.schmoutz

‎12-31-2013 05:42 AM

Hello Alain,

Yes this is related with version. I checked in my lab and it shows NSR-ready in 4.2.3, but NSR-not-configured in 4.3.2. This is the same router with same configuration, the changes only the version.

VERSION 4.2.3 :

RP/0/RSP0/CPU0:ASR9006-H#show redundancy

Mon Dec 30 10:05:08.434 EST

Redundancy information for node 0/RSP0/CPU0:

==========================================

Node 0/RSP0/CPU0 is in ACTIVE role

Node Redundancy Partner (0/RSP1/CPU0) is in STANDBY role

Standby node in 0/RSP1/CPU0 is ready

Standby node in 0/RSP1/CPU0 is NSR-ready

Node 0/RSP0/CPU0 is in process group PRIMARY role

Process Redundancy Partner (1/RSP0/CPU0) is in BACKUP role

Backup node in 1/RSP0/CPU0 is ready

Backup node in 1/RSP0/CPU0 is NSR-ready

Group            Primary         Backup          Status

---------        ---------       ---------       ---------

dsc              0/RSP0/CPU0     1/RSP0/CPU0     Ready

dlrsc            0/RSP0/CPU0     1/RSP0/CPU0     Ready

central-services 0/RSP0/CPU0     1/RSP0/CPU0     Ready

v4-routing       0/RSP0/CPU0     1/RSP0/CPU0     Ready

netmgmt          0/RSP0/CPU0     1/RSP0/CPU0     Ready

v6-routing       0/RSP0/CPU0     1/RSP0/CPU0     Ready

Reload and boot info

----------------------

A9K-RSP440-SE reloaded Fri Dec 27 12:56:27 2013: 2 days, 21 hours, 8 minutes ago

Active node booted Fri Dec 27 12:56:27 2013: 2 days, 21 hours, 8 minutes ago

Standby node boot Fri Dec 27 12:56:45 2013: 2 days, 21 hours, 8 minutes ago

Standby node last went not ready Fri Dec 27 14:55:40 2013: 2 days, 19 hours, 9 minutes ago

Standby node last went ready Fri Dec 27 14:55:40 2013: 2 days, 19 hours, 9 minutes ago

There have been 0 switch-overs since reload

Active node reload "Cause: dSC node reload is required by install operation"

Standby node reload "Cause: Node reload is required by install operation"

Redundancy information for node 1/RSP0/CPU0:

==========================================

Node 1/RSP0/CPU0 is in ACTIVE role

Node Redundancy Partner (1/RSP1/CPU0) is in STANDBY role

Standby node in 1/RSP1/CPU0 is ready

Standby node in 1/RSP1/CPU0 is NSR-ready

Reload and boot info

----------------------

A9K-RSP440-SE reloaded Fri Dec 27 12:56:45 2013: 2 days, 21 hours, 8 minutes ago

Active node booted Fri Dec 27 12:56:45 2013: 2 days, 21 hours, 8 minutes ago

Standby node boot Fri Dec 27 12:56:43 2013: 2 days, 21 hours, 8 minutes ago

Standby node last went not ready Fri Dec 27 13:00:02 2013: 2 days, 21 hours, 5 minutes ago

Standby node last went ready Fri Dec 27 13:00:02 2013: 2 days, 21 hours, 5 minutes ago

There have been 0 switch-overs since reload

Active node reload "Cause: Node reload is required by install operation"

RP/0/RSP0/CPU0:ASR9006-H#show install active summary

Mon Dec 30 10:05:29.983 EST

  Active Packages:

    disk0:asr9k-px-4.2.3.CSCud37351-1.0.0

    disk0:asr9k-mini-px-4.2.3

    disk0:asr9k-mpls-px-4.2.3

    disk0:asr9k-px-4.2.3.CSCud98419-1.0.0

    disk0:asr9k-fpd-px-4.2.3

    disk0:asr9k-px-4.2.3.CSCud54093-1.0.0

RP/0/RSP0/CPU0:ASR9006-H#

UPGRADE TO VERSION 4.3.2:

RP/0/RSP0/CPU0:ASR9006-H#show redundancy

Mon Dec 30 10:49:31.872 EST

Redundancy information for node 0/RSP0/CPU0:

==========================================

Node 0/RSP0/CPU0 is in ACTIVE role

Node Redundancy Partner (0/RSP1/CPU0) is in STANDBY role

Standby node in 0/RSP1/CPU0 is ready

Standby node in 0/RSP1/CPU0 is NSR-ready

Node 0/RSP0/CPU0 is in process group PRIMARY role

Process Redundancy Partner (1/RSP0/CPU0) is in BACKUP role

Backup node in 1/RSP0/CPU0 is ready

Backup node in 1/RSP0/CPU0 is NSR-ready

Group            Primary         Backup          Status

---------        ---------       ---------       ---------

dsc              0/RSP0/CPU0     1/RSP0/CPU0     Ready

dlrsc            0/RSP0/CPU0     1/RSP0/CPU0     Ready

central-services 0/RSP0/CPU0     1/RSP0/CPU0     Ready

v4-routing       0/RSP0/CPU0     1/RSP0/CPU0     Ready

netmgmt          0/RSP0/CPU0     1/RSP0/CPU0     Ready

mcast-routing    0/RSP0/CPU0     1/RSP0/CPU0     Ready

v6-routing       0/RSP0/CPU0     1/RSP0/CPU0     Ready

Reload and boot info

----------------------

A9K-RSP440-SE reloaded Mon Dec 30 10:35:36 2013: 13 minutes ago

Active node booted Mon Dec 30 10:35:36 2013: 13 minutes ago

Standby node boot Mon Dec 30 10:36:18 2013: 13 minutes ago

Standby node last went not ready Mon Dec 30 10:38:05 2013: 11 minutes ago

Standby node last went ready Mon Dec 30 10:39:05 2013: 10 minutes ago

There have been 0 switch-overs since reload

Active node reload "Cause: dSC node reload is required by install operation"

Standby node reload "Cause: Node 0/RSP1/CPU0 is in STANDBY role and is not ready

"

Redundancy information for node 1/RSP0/CPU0:

==========================================

Node 1/RSP0/CPU0 is in ACTIVE role

Node Redundancy Partner (1/RSP1/CPU0) is in STANDBY role

Standby node in 1/RSP1/CPU0 is ready

Standby node in 1/RSP1/CPU0 is NSR-not-configured

Reload and boot info

----------------------

A9K-RSP440-SE reloaded Mon Dec 30 10:36:21 2013: 13 minutes ago

Active node booted Mon Dec 30 10:36:21 2013: 13 minutes ago

Standby node boot Mon Dec 30 10:36:03 2013: 13 minutes ago

Standby node last went not ready Mon Dec 30 10:38:22 2013: 11 minutes ago

Standby node last went ready Mon Dec 30 10:39:22 2013: 10 minutes ago

There have been 0 switch-overs since reload

Active node reload "Cause: Node reload is required by install operation"

RP/0/RSP0/CPU0:ASR9006-H#show install active summary

Mon Dec 30 10:49:38.283 EST

Default Profile:

  SDRs:

    Owner

  Active Packages:

    disk0:asr9k-mini-px-4.3.2

    disk0:asr9k-mpls-px-4.3.2

RP/0/RSP0/CPU0:ASR9006-H#

thanks,

Rivalino

alain.schmoutz
Level 1
Level 1
In response to Rivalino Tamaela

‎12-31-2013 06:43 AM

Hi Samuel and Rivalino,

Thanks for your participation and help!

I wish you an Happy New Year!

Best regards,

Alain

0 Helpful
Customers Also Viewed These Support Documents