When an active CPM goes offline (due to reboot, removal, or failure), the standby CPM takes control without rebooting or initializing itself. It is assumed that the CPMs are synchronized, therefore, there is no delay in operability. When the CPM that went offline boots and comes back online, it becomes the standby CPM.
The following console message is displayed when the active CPM goes offline and the standby CPM assumes the active role:
Active CPM in Slot A has stopped
Slot B is now active CPM
Attempting to exec configuration file:
'cf1:/config.cfg' ...
...
Executed 49,588 lines in 8.0 seconds from file cf1:\config.cfg