Additional Commands Affected By Redundant Management - HP ProCurve Management And Configuration Manual

Redundancy (Switch 8212zl)
Existing CLI Commands Affected by Redundant Management
15-34
Additional Commands Affected by Redundant
Management
The other existing commands operate with redundant management as shown
below.
Command
auto-tftp
banner
chassislocate
clear
console
copy
crypto
erase flash
erase config
erase startup-config
Action
If a new image is downloaded using auto-tftp, the active
management module downloads the new software version to both
the active and standby modules. Rebooting after the auto-tftp
completes reboots the entire system.
The banner will not been seen on the standby module, only the
active module.
If the management module performs a switchover, the LED does
not remain lit.
The clear crypto command causes public keys to be deleted from
both modules when the second module is in standby mode.
Console settings, such as mode, flow-control, and baud-rate, are
the same on both management modules. There cannot be
individual settings for each management module.
Files are automatically sync'd from the active management module
to the standby management module.
When no parameter is specified with the copy crash-data or copy
crash-log command, files from all modules (management and
interface) are concatenated. See "Crash Files" on page 15-42.
Note: If redundancy is disabled or the standby module failed
selftest, the copy command affects only the active management
module.
Authentication files for ssh or the https server are copied to the
standby management module. The clear crypto command deletes
the public keys from both modules when the second module is in
standby mode.
Erases the software version on the active and standby modules. If
redundancy has been disabled, or the standby module has not
passed selftest, the flash is not erased on the standby module.
Erases the config file on the active and standby modules. If
redundancy has been disabled, or the standby module has not
passed selftest, the config file is not erased on the standby module.
Affects both modules if the second module is in standby mode. If
redundancy has been disabled, or the standby module has not
passed selftest, the startup-config file is not erased on the standby
module.