HP ProCurve 6600 and Hotswapped Module, Hotswapping In a Management Module, Software Version Mismatch Between Active, no redundancy, management-module, transfer is aborted

Redundancy (Switches 8200zl)

Hotswapping Management Modules

	When the Standby Module is not Available
	If you have disabled redundancy with the no redundancy management-module
	command, or the standby module failed selftest, the Dwn LED will not turn
	green to indicate it is OK to hotswap out the active management module.
N o t e	If you remove the active management module without pressing the MM
	Shutdown button, any files that may have been in the process of
	synchronizing will not finish synchronizing to the standby module and all file
	transfer is aborted.

Hotswapping In a Management Module

If another management module is hotswapped in while there is an active management module booted up, the newly hotswapped management module becomes the standby module. It partially boots up and heartbeats are sent back and forth with the active management module. No negotiating is needed as to which module will become the active management module as there is already a functioning active management module. However, these conditions must be met to determine if the hotswapped module can become a standby management module:

■ The hotswapped module must pass selftest

■ Redundancy is not administratively disabled (using the no redundancy management-modulecommand). If the active management module’s config file has redundancy administratively disabled, the hotswapped manage­ ment module goes into “offline” mode.

Software Version Mismatch Between Activeand Hotswapped Module

Sometimes the software version in the hotswapped module may not match the software version in the active module. In these cases the following occurs:

1. The active module sends the primary and secondary images in flash to the hotswapped module.

2. The module that was hotswapped in then reboots if necessary to primaryor secondary flash, whichever matches (if it doesn’t match already).

3. After the hotswapped management module finishes booting, it is sent the config and other critical files from the active management module.

4. The hotswapped management module goes into standby mode and is ready to take over in case of a switchover.

15-16