Setting-up the
Standby-to-be
Controller
You may now power up the second controller, which will be the Standby-to-be
controller.
It's supposed here that the Standby unit controller's memory is clear or at least in a
"No Conf" state. In these circumstances, the memory update of the Standby unit,
starting from the Primary unit's memory, will be done automatically. An automatic
transfer should also occur when the configuration staying in the Standby-to-be
controller is different from the one staying in the Primary Controller.
In a first step, the keypad of this second controller displays "Initializing" for a few
seconds after the power up. During this phase, looking at this controller's front panel,
you should notice that the STS LED is lit in a steady on state, indicating that the
system is not (yet) redundant. By the way, this also indicates that the controller's
Redundancy Copro has done its boot after a power up, and has ended its self-tests.
The COM LED is off for a while, indicating there is no communication activity
between Primary and Standby controllers.
The COM LED will then blink for some seconds, and then switch to a steady on
state, so indicating there is some communication activity between Primary and
Standby controllers. At that point, the STS LED should have turned to a blinking
state, indicating so that the system is now redundant, and that data are exchanged
from the primary to the Standby controller.
The keypad of the first controller should display "Run Primary" and the second
controller should display "Run Standby". To return the display to the default, press
the ESC key and the keypad displays its first page.
Checking the
CRP LED Status
When the Hot Standby system is operational, the green "Ready" LED is steady on
for both the Primary's and Standby's RIO communication processor module (CRP).
Also, the Primary CRP's green "Com Act" LED should be steady on, while the LED
of the Standby CRP should be blinking
