Here are the steps on performing the switchover of Route Switch Processor (RSP) or Route Processor (RP) in Cisco ASR9000 platforms running in Cisco IOS-XR.
- Check the redundancy status information to see which RSP or RP running active or standby.
show redundancy
Example:
RP/0/RSP0/CPU0:IOS-XR#show redundancy
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-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
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-RSP880-SE reloaded Sun Apr 9 21:14:41 2023: 2 hours, 4 minutes ago
Active node booted Sun Apr 9 21:14:41 2023: 2 hours, 4 minutes ago
Standby node boot Sun Apr 9 21:42:53 2023: 1 hour, 36 minutes ago
Standby node last went not ready Sun Apr 9 21:44:26 2023: 1 hour, 34 minutes ago
Standby node last went ready Sun Apr 9 21:45:26 2023: 1 hour, 33 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: MBI-HELLO reloading node on receiving reload notification”
As you can see, the current active is RSP0 and standy is RSP1
| 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 |
2. Use this command to see any configuration inconsistencies to make sure configuration are both synch.
show configuration inconsistency replica location <standby node-id>
Example:
RP/0/RSP0/CPU0:IOS-XR#show configuration inconsistency replica location 0/RSP1/CPU0
Replica is consistent
3. Switch over from active to standby using this command
redundancy switchover location <active node-id>
This command will cause the primary (active) route processor (RP) to fail over to the redundant standby RP
Example:
RP/0/RSP0/CPU0:IOS-XR#redundancy switchover location 0/RSP0/CPU0
Proceed with switchover 0/RSP0/CPU0 -> 0/RSP1/CPU0? [confirm]
Initiating switch-over.
RP/0/RSP1/CPU0:Apr 9 23:30:26.406 UTC: rmf_svr[423]: %HA-REDCON-4-FAILOVER_REQUESTED : failover
Reboot on ASR9006-V2 RSP4L (0x10031a) in slot 0
By rmf_svr via REBOOT_CAUSE_FAILOVER (4000004)
Current time: 2023-04-09 23:30:26.529, Up time: 2h 15m 45s
Release mastership on RSP4L
Normal reboot
4. Use “show redundancy” command to verify if the other RSP already took over as the active. During the switchover the active will reboot, so you can use “show platform” to confirm status.
show redundancy
show platform
Example:
RP/0/RSP1/CPU0:IOS-XR#show platform
Node Type State Config State
—————————————————————————–
0/RSP0/CPU0 A9K-RSP880-SE(Standby) IOS XR RUN PWR,NSHUT,MON
0/RSP1/CPU0 A9K-RSP880-SE (Active) IOS XR RUN PWR,NSHUT,MON
RP/0/RSP1/CPU0:IOS-XR#show redundancy
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 not NSR-ready
Group Primary Backup Status
——— ——— ——— ———
v6-routing 0/RSP1/CPU0 0/RSP0/CPU0 Ready
mcast-routing 0/RSP1/CPU0 0/RSP0/CPU0 Ready
mcast-routing 0/RSP1/CPU0 0/RSP0/CPU0 Not NSR-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
Process Group Details
———————
Current primary rmf state: Ready
All backup not-ready bits clear – backup should be ready
Current primary rmf state for NSR: Not Ready
<jid> <node> <name> <group> Reason for backup not NSR-ready
1215 0/RSP1/CPU0 pim6 mcast-routing Standby partner proc not connected to Active
Not ready set Sun Apr 9 23:30:27 2023: 7 minutes ago
1214 0/RSP1/CPU0 pim mcast-routing Standby partner proc not connected to Active
Not ready set Sun Apr 9 23:30:27 2023: 7 minutes ago
Reload and boot info
———————-
A9K-RSP880-SE reloaded Sun Apr 9 21:14:41 2023: 2 hours, 23 minutes ago
Active node booted Sun Apr 9 21:42:52 2023: 1 hour, 55 minutes ago
Last switch-over Sun Apr 9 23:30:26 2023: 7 minutes ago
Standby node boot Sun Apr 9 23:34:48 2023: 3 minutes ago
Standby node last went not ready Sun Apr 9 23:35:51 2023: 2 minutes ago
Standby node last went ready Sun Apr 9 23:36:51 2023: 1 minute ago
There has been 1 switch-over since reload
Active node reload “Cause: MBI-HELLO reloading node on receiving reload notification”
Standby node reload “Cause: Initiating switch-over.”
Be First to Comment