File Synchronization Between The Active And Standby Redundant Management Modules - HP ProCurve 9304M Installation And Configuration Manual

Installation and Basic Configuration Guide
USING THE CLI
To view the system log, enter the following command at any level of the CLI:
HP9300> show log
Syslog logging: enabled (0 messages dropped, 0 flushes, 0 overruns)
Buffer logging: level ACDMEINW, 8 messages logged
level code: A=alert C=critical D=debugging M=emergency E=error
I=informational N=notification W=warning
Static Log Buffer:
Dynamic Log Buffer (50 entries):
at 0 days 0 hours 0 minutes 0 seconds, level alert
Management module at slot 1 state changed,
changed state from standby to active
USING THE WEB MANAGEMENT INTERFACE
1. Log on to the device using a valid user name and password for read-write access. The System configuration
dialog is displayed.
2. Click on the plus sign next to Monitor in the tree view to display the Monitor options.
3. Select the System Log link to display the system log.
File Synchronization Between the Active and Standby Redundant Management
Modules
Each redundant management module contains four files that can be synchronized between the two modules:
• Boot code – The code the module runs when it first starts up. By default, the boot code is not synchronized
between redundant management modules. This ensures that the system can still operate if a new version of
boot code contains a bug that prohibits normal operation. If the new code on the active module does not work
properly, the system can still run using the older version of boot code on the standby module.
You can configure the standby redundant management module to synchronize with the active redundant
management module's boot code whenever the boot code on the active module is updated or the system
starts up.
• Flash code (system software) – The flash code is automatically synchronized between the redundant
management modules. When the system starts up, the active redundant management module sends its flash
code to the standby redundant management module to boot the module.
NOTE: The flash code on T-Flow TSP CPUs (non-management CPUs) is not automatically synchronized.
To synchronize the flash code on the TSP CPUs, use the vm copy tftp flash command, described in
"Immediately Synchronizing Software" on page 3-13. The flash code on the CPU is automatically
synchronized.
• System-config file – The system-config file is automatically copied from the active redundant management
module to the standby redundant management module when the system starts up. The file is also copied to
the standby module whenever you save changes to the file. If switchover occurs, the standby redundant
management module loads system parameters from the running-config data that was last received from the
active redundant management module. If the standby module did not receive running-config data from the
active module, the standby module uses configuration information in the system-config file copied from the
active module.
3 - 10