ON-LINE CONFIGURATION
OPERATION
B - 4
I-E96-203C
Elsag Bailey
Process A utom ation
n
01xx0x0x
z
z
n+1
00xx1x0x
5
{
4. The backup module can now be placed in execute mode provided no errors
remain in the new configuration.
Additional configuration changes can be made by entering configure mode
(Step 2). If no changes have been made, a backup module reset returns the
backup to the state of Step 1. If changes have been made, the backup must be
put into configure mode and initialized to get to the state of Step 1.
NOTE: The backup cycle step transition 3 to 4 occurs automatically after a suc-
cessful Step 3 backup module execute. The transaction completion time depends
on the MFP configuration.
n
01xx0x0x
z
z
n+1
10xx1x0x
{
5
5. When the checkpoint data for the old configuration is received from the
primary module, the reconfigured backup module can assume the role of the
primary module if a failure is detected in the old configuration (Step 8). However,
the primary module still indicates that no backup is available when the configura-
tion is different.
Additional configuration changes can be made by entering configure mode
(Step 2). If no changes have been made, a backup module reset returns the
backup to the state of Step 1. If changes have been made, the backup must be
put into configure mode and initialized to get to the state of Step 1.
n
01xx0x0x
z
z
n+1
00xx1x0x
{
{
6. After the changes have been made, tell the reconfigured backup module to
assume the role of the primary module by pressing and releasing the stop/
release button on the backup module 2 times. The first time stops the module;
the second time resets the module. The backup module comes up in execute
mode with the configuration marked as valid.
n
01xx0x0x
z
z
n+1
10xx1x0x
5
{
7. Backup cycle step transitions 5 to 6 to 7 to 8 occur automatically after the
Step 5 backup module reset. The time it takes to complete these transitions
depends on MFP configuration. The status indicated in cycles 5, 6 and 7 may not
be seen depending on the actual step transition times. The important status to
wait on is indicated by Step 8.
After the checkpoint data is updated, the backup module is ready to take over the
duties of the primary module.
n
01xx0x0x
z
z
n+1
11xx1x0x
{
5
8. The backup module requests the primary module to shut down and assume
the role of a hot backup (n+1). The backup module waits to act as the primary
module (n). A hot backup retains the old configuration and control data and is
ready to assume control if an error is detected in the new configuration.
n+1
01xx0x0x
{
z
n
01xx1x0x
5
5
9. The primary module has removed the bus clock (BUSCLK) and acts as a hot
backup (n+1). The reconfigured backup module is now serving as the primary
module (n).
Before proceeding to the following commands, insure that LED/module status is
as shown in Step 8.
To return to Step 4, reset the backup module (n). This allows correcting a bad
configuration.
The primary module (n+1) must be reset at this point in order for the on-line con-
figuration cycle to complete. Resetting the primary module (n+1), currently acting
as the hot backup, tells it to get a copy of the new configuration.
n+1
10xx0x0x
{
z
n
00xx0x0x
z
z
10. After the backup module copies the new configuration into the primary mod-
ule, the cycle is complete. The backup module is now serving as the primary
module (n) while the primary handles the backup role (n+1). The LED combina-
tion and module status is the opposite of Step 1, indicating the role reversal.
Table B-2. Backup Cycle
(continued)
Primary
Backup
Procedure
