04-29-2020 04:45 AM
dears
i have installed 2 RSP880 as active/standby. but while doing #show redundancy
i see
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-not-configured
Node 0/RSP0/CPU0 is in process group PRIMARY role
Process Redundancy Partner (0/RSP1/CPU0) is in BACKUP role
Backup node in 0/RSP1/CPU0 is ready
Backup node in 0/RSP1/CPU0 is NSR-ready
i read on other topic that it's normal. but i want to do test to switch over between Active/standby just to make sure.
so what the procedure you suggest is there a command line to switchover or just pulling the RSP active and let the standby handle the rest.
thanks in advance.
04-29-2020 05:21 AM
Can you post the full "show redundancy" ? we need to check which protocol is not ready and see what is not configured.
thanks
04-29-2020 06:04 AM
04-29-2020 06:50 AM
Looks like Sam had a similar post.
it seems the behavior was changed.
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvb78536/?rfs=iqvred
Thanks
04-29-2020 06:54 AM
thanks so this is normal
what about the switchover procedure is it safe to proceed?
is there a command line or just pulling the active RSP? and if yes for pulling is there minimum time to insert it back?
04-29-2020 07:35 AM
"redundancy switchover" is the command we can use to switchover
04-29-2020 12:59 PM
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-not-configured
Node 0/RSP0/CPU0 is in process group PRIMARY role
Process Redundancy Partner (0/RSP1/CPU0) is in BACKUP role
Backup node in 0/RSP1/CPU0 is ready
Backup node in 0/RSP1/CPU0 is NSR-ready
You are nsr-ready, as I stated in the other thread "
In the earlier releases the "Node Groups" were also marked as "NSR Ready", the output has been enhanced in the 6.2.x release to reflect the fact the it is applicable to "Backup node" only.
The "Process groups" are the actual processes which get sync'd between the active and standby RSP. As we can see in the output that the process groups for the device are completely in sync and that the processes themselves also report being NSR ready as well."
Seeing nsr-ready for the node groups before 6.2.x was a mistake as that's not the process groups (which is what NSR syncs).
Sam
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide