ASR9010 XR RSP manual switchover

[matthewng]

Hi there

I need to failover to our standby RSP-4G on our 9k due to cisco wanting to RMA our current Active RSP.

Is it a hitless operation when I do a switchover? so no impact / loss of traffic?

Once the RSP has been switched over, I can eject the ex-active RSP then insert the RSP sent by Cisco?

After its booted, I should then be able to failover back to the new RSP right?

Thanks

Matthew

[smailmilak]

Hi Matt,

First chech with show redundancy if all is ok and ready. It should be hitless because everything is replicated.

You SSH session will fail but you will be able to reconnect

I have done a dozen switchovers and it was always hitless. You should also use NSR on your routing protocols.

After that you can insert new RSP and wait until it's ready. It will take some time.

You should also check FPD on new RSP.

[matthewng]

Thank you

Standby RSP is ready (see output below)

Is there any documentation from cisco about the manual switchover being hitless? as I could not find it anywhere

Also BGP have NSR enabled but our IGP (OSPF) have NSR disable

Will that cause any issue ?

#show redundancy
Fri Dec 2 12:38:43.573 NZDT
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 (0/RSP1/CPU0) is in BACKUP role
Backup node in 0/RSP1/CPU0 is ready
Backup node in 0/RSP1/CPU0 is NSR-ready

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

Reload and boot info
----------------------
A9K-RSP-4G reloaded Thu Nov 24 03:09:43 2016: 1 week, 1 day, 9 hours, 29 minutes ago
Active node booted Thu Nov 24 03:09:43 2016: 1 week, 1 day, 9 hours, 29 minutes ago
Standby node boot Thu Nov 24 03:09:46 2016: 1 week, 1 day, 9 hours, 28 minutes ago
Standby node last went not ready Thu Nov 24 03:14:49 2016: 1 week, 1 day, 9 hours, 23 minutes ago
Standby node last went ready Thu Nov 24 03:17:15 2016: 1 week, 1 day, 9 hours, 21 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: Install operation. Shutdown standby node gracefully."

[smailmilak]

Hi,

I doubt that you will find such document. You should enable NSR for OSPF, just in case.

If you have any doubts regarding the switchover, then ask for a maintenance window and do the switchover.

[Adam Vitkovsky]

I would actually suggest to always perform RE switchover during maintenance window. There are so many thing that can go wrong.

Yes you can check the global switchover status then you can check details of switchover status for each protocol specifically to make sure all data structures are indeed synchronized correctly and then assuming you haven’t missed anything you can still run into some unexpected bug.

adam