On a chassis router, the control plane and the data plane live in separate hardware modules.
The Route Processor (RP) handles routing protocols, configuration, and management.
The Line Cards (LC) handle packet forwarding.
Because these modules are physically separate, your chassis can hold two Route Processors (RPs) in dedicated slots.
One is Active, the other is Standby. Both live inside the same device.Two RPs, One Chassis
The Active RP runs your control plane.
The Standby RP sits in a second slot, ready to take over if the Active fails.
Figure 1 – Chassis router: Active RP, Standby RP, and Line Cards in separate slots
If the Active RP fails, the Standby takes over.
But how that takeover happens makes all the difference.Answer the question below
Which hardware module handles packet forwarding inside a chassis router?
What Happens Without Protection
Without any high availability mechanism, the Standby RP is either powered off or only partially initialized.
When the Active RP fails, your router essentially reboots.
The Standby RP must load IOS, read the startup configuration, reload the Line Cards, and rebuild all routing adjacencies from scratch.
Figure 2 – RP failover without high availability: minutes of downtime
All your interfaces go down. All routing adjacencies (OSPF, BGP) are lost.
The routing table is empty. No packets are forwarded.
The entire failover can take several minutes. In a modern network, that is not acceptable.Earlier RP redundancy modes (HSA, RPR, RPR+) each tried to reduce this failover time. But none of them preserved Layer 2 or Layer 3 protocol states.
Every failover still meant re-convergence, and re-convergence meant downtime.Answer the question below
On a chassis router, which removable module runs the control plane?
So how do you make a failover truly seamless?
SSO is the modern RP redundancy mode used on Cisco chassis devices.
Unlike earlier modes, SSO fully boots and initializes the Standby RP, keeping it ready to take over at any moment.Copying Everything at Boot
The key mechanism behind SSO is called checkpointing.
Checkpointing is the process of syncing state information from the Active RP to the Standby RP.When the Standby RP first boots, a bulk synchronization is performed.

Figure 3 – SSO bulk synchronization: the Active RP sends all state to the Standby RP at boot
The Active RP sends everything at once: running configuration, interface states, and all Layer 2 protocol states (STP, LACP, PAgP, VTP, Port Security).
After this initial transfer, the Standby RP has a complete copy of the Active RP's state.
But your network is not static. Configurations change, interfaces go up and down, STP topologies evolve.Answer the question below
What is the process of syncing state from Active RP to Standby RP called?
Syncing Every Change in Real Time
After the initial bulk sync, SSO switches to incremental synchronization.
Any change on the Active RP is immediately sent to the Standby RP.
Figure 4 – SSO incremental sync: every change on the Active RP is sent to the Standby in real time
You change a configuration, an interface goes up or down, an STP topology changes: every update is synced in real time.
Your Standby RP is always an up-to-date mirror of the Active RP, ready to take over in seconds.Answer the question below
After the bulk sync, what type of synchronization keeps the Standby RP current?
SSO should be enabled by default on any device that supports it.
If for some reason it is not, you can enable it manually.Enabling SSO
R1# conf t Enter configuration commands, one per line. End with CNTL/Z. R1(config)# redundancy R1(config-red)# mode sso R1(config-red)# endThe
redundancycommand enters redundancy configuration mode.
Themode ssocommand enables Stateful Switchover.Reading the show redundancy Output
To verify the current redundancy mode and the status of both RPs, run the following command.
R1# show redundancy Redundant System Information : ------------------------------ Available system uptime = 3 days, 14 hours, 22 minutes Switchovers system experienced = 0 Standby failures = 0 Last switchover reason = none Hardware Mode = Duplex Configured Redundancy Mode = sso Operating Redundancy Mode = sso Maintenance Mode = Disabled Communications = Up Current Processor Information : ------------------------------- Active Location = slot 1 Current Software state = ACTIVE Uptime in current state = 3 days, 14 hours, 20 minutes Image Version = Cisco IOS Software, Version 17.3.4a Peer Processor Information : ---------------------------- Standby Location = slot 2 Current Software state = STANDBY HOT Uptime in current state = 3 days, 14 hours, 18 minutes Image Version = Cisco IOS Software, Version 17.3.4aHere are the key fields to look at:
Configured and Operating Redundancy Mode confirm SSO is active
The Active RP shows
ACTIVEas its software stateThe Standby RP shows
STANDBY HOT, meaning it is fully synchronized and ready for immediate takeover
Answer the question below
What Standby RP state confirms it is fully synchronized and ready for failover?
Answer the question below
From the uptimes, how many minutes after slot 1 did slot 2 reach STANDBY HOT?
When the Active RP fails with SSO enabled, the Standby RP takes over within seconds.
Your interfaces stay up, STP does not re-converge, and your EtherChannels remain operational.
Layer 2 forwarding continues without interruption.But Layer 3 protocol states (OSPF, BGP, EIGRP adjacencies) are not checkpointed to the Standby RP.
When the failover happens, all routing adjacencies go down and your routing table is cleared.To complete the picture, SSO works together with three additional techniques.
Forwarding Without the RP
On a chassis device, your Line Cards (LC) use Distributed CEF: each Line Card has its own copy of the FIB (Forwarding Information Base) and can forward packets independently.
Non-Stop Forwarding (NSF) checkpoints the FIB to the Standby RP.
When the Active RP fails, your Line Cards still have a valid FIB and continue forwarding packets at Layer 3.
Figure 5 – NSF: the FIB is distributed to every Line Card and the Standby RP
NSF is enabled by default when SSO is active. It is a function of the local device only and does not require cooperation from neighboring routers.
However, even with NSF, your neighboring routers lose their adjacency with the failing device.
They remove all routes via your device and stop sending traffic.
Your device can forward, but no traffic arrives.Answer the question below
Which table does NSF checkpoint to maintain Layer 3 forwarding during failover?
Convincing Your Neighbors to Stay
Your device can forward, but neighbors have already torn down their adjacencies. Two techniques solve this.
Graceful Restart (GR) (RFC 3623 for OSPF, RFC 4724 for BGP) asks neighbors to keep their routes toward your device during failover. This requires neighbor cooperation.
Non-Stop Routing (NSR) checkpoints the routing protocol state to your Standby RP.
Your neighbors never see the adjacency go down. No cooperation needed.
You cannot enable both on the same routing protocol.
Choose one or the other.Technique
What It Maintains
Requires Neighbor Cooperation
SSO
Interfaces + Layer 2 protocol states
No
NSF
FIB / Local Layer 3 forwarding
No
GR
Neighbor routes via this device
Yes
NSR
Routing protocol adjacencies
No
Table 1 – RP failover techniques comparison
Keep in mind that these features do not replace good network design.
Ideally, your network should have redundant routers (using FHRP, for example), not just a router with redundant Route Processors.Answer the question below
Which technique requires cooperation from neighboring devices: GR or NSR?