When The Active Cpm Goes Offline; Configuration Guidelines For Synchronization Of Active And Standby Cpm On 7210 Sas-R6 - Alcatel-Lucent 7210 SAS M Configuration Manual

System Basics Introduction

When the Active CPM Goes Offline

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 then comes
back online, it becomes the standby CPM.
When the standby CPM comes online, the following output displays:
Active CPM in Slot A has stopped
Slot B is now active CPM
Attempting to exec configuration file:
'cf3:/config.cfg' ...
...
Executed 49,588 lines in 8.0 seconds from file cf3:\config.cfg
Configuration Guidelines for synchronization of active and
standby CPM on 7210 SAS-R6
•
•
•
•
•
•
Page 214
Active CPM and Standby CPM should boot from same boot drives i.e. if Active is booted
from cf1:\ then standby must use cf1:\ to bootup, and if active uses cf2:\ then standby must
use cf2:\ and so on if using uf1:\. Even though it is possible to make the CPM operational
by booting them using any drive on active and standby, it is recommended to use same
drives for booting the system.
User should ensure that a valid boot-image (boot.tim) and bof-file (bof.cfg) must exist in
either cf1:/cf2:/uf1 drive of both active and stand-by CPM card. Ensure bof.cfg should
reside at the same drive as the boot.tim.
The TiMOS application images cpm.tim and iom.tim and configuration file can reside in
any location (local or remote), but the locations in the BOF file should be configured
identically on both active and standby CPM for primary/secondary/tertiary locations.
Boot-env synchronisation has to be done prior to config synchronization. To do this,
execute admin redundancy synchronize boot-env and then execute admin redundancy
synchronize config.
Synchronization can only occur locally between Compact Flash drives cf1:Active to
cf1:Standby, cf2:Active to cf2:Standby, and uf1:Active to uf1:Standby. In other words,
synchronization across different drives is not supported.
If the active and standby are not synchronized for some reason, users can manually
synchronize the standby CPM by admin redundancy synchronize boot-env and by
rebooting the standby by issuing the admin reboot standby command.
7210 SAS M, T, X, R6 Basic System Configuration Guide