File Synchronization Between The Active And Standby Management Modules - IBM s-series Installation And User Manual

File synchronization between the active and standby management
modules
Each active and standby management module contains the following files that can
be synchronized between the two modules:
v Flash code - The flash code can include the following files:
v System-config file - The flash code also includes the system-config file. During
v SSH and SSL keys
v Flash file for the DHCP snooping feature
Each active and standby management module also includes boot code, which is the
code a module runs when it first starts up. The boot code resides in each module's
boot flash. The boot code is synchronized between the two modules.
Figure 32 on page 80 shows how the files are synchronized between the active
module and the standby module.
– Primary - Contains the management module's primary IronWare image.
– Secondary - Contains the management module's secondary IronWare image.
The primary and secondary files also include a monitor file, which contains the
management module's Real Time Operating System (RTOS).
The IronWare image contains the layer 1 - 3 software run by the management
module.
During startup or switchover, the active module automatically synchronizes the
standby module's flash code with its own. Also, when you update the flash code
on the active module, the active module automatically synchronizes the standby
module's flash code with its own.
startup or switchover, the active module compares the standby module's
system-config file to its own. If differences exist, the active module synchronizes
the standby module's system-config file with its own. When you save changes to
the system-config file on the active module, the active module automatically
synchronizes (without comparison) the standby module's system-config file with
its own.
Chapter 6. Using a redundant management module
79