ProCurve 3500yl Series, Руководство по управлению и настройке

Страница: 144 / 732

6-32
Switch Memory and Configuration
Multiple Configuration Files
For example, suppose:
■ Software release “A” is stored in primary flash and a later software release
is stored in secondary flash.
■ The system operator is using memory slot 1 for a reliable, minimal
configuration (named
minconfig
) for the software version in the primary
flash, and slot 2 for a modified startup-config file (named
newconfig
) that
includes untested changes for improved network operation with the
software version in secondary flash.
The operator wants to ensure that in case of a need to reboot by pressing the
Reset button, or if a power failure occurs, the switch will automatically reboot
with the minimal startup-config file in memory slot 1. Since a reboot due to
pressing the Reset button or to a power cycle always uses the software version
in primary flash, the operator needs to configure the switch to always boot
from primary flash with the startup-config file named
minconfig
(in memory
slot 1). Also, whenever the switch boots from secondary flash, the operator
also wants the startup-config named
newconfig
to be used. The following two
commands configure the desired behavior.
Syntax: startup-default [ primary | secondary ] config < filename >
Specifies a boot configuration policy option:
[ primary | secondary ] config < filename >:
Designates the
startup-config file to use in a reboot with the software
version stored in a specific flash location. Use this option
to change the reboot policy for either primary or
secondary flash, or both.
config < filename >:
Designates the startup-config file to use
for all reboots, regardless of the flash version used. Use
this option when you want to automatically use the same
startup-config file for all reboots, regardless of the flash
source used.
For redundant management systems, this command affects
both the active management module and the standby manage-
ment module. The config file is copied immediately to the
standby management module and becomes the default on that
module when the next bootup occurs, unless redundancy is
disabled or the standby module has failed selftest.
Note: To override the current reboot configuration policy for
a single reboot instance, use the
boot system flash
command
with the options described under “Overriding the Default
Reboot Configuration Policy” on page 6-33.
3500-5400-6200-8200-MCG-Jan08-K_13_01.book Page 32 Monday, January 28, 2008 10:04 AM