Switch Memory and Configuration
Multiple Configuration Files
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.
ProCurve(config)# startup-default pri config minconfig
ProCurve(config) # startup-default sec config newconfig.
Overriding the Default Reboot Configuration Policy. This command
provides a method for manually rebooting with a specific startup-config file
other than the file specified in the default reboot configuration policy.
Syntax: boot system flash < primary | secondary > config < filename >
Specifies the name of the startup-config file to apply for the
immediate boot instance only. This command overrides the
current reboot policy.
Using Reload To Reboot From the Current Flash Image and Startup-
Config File.
Syntax: [no] reload [after <[dd:]hh:]mm> | at <hh:mm[:ss]> [<mm/dd[/[yy]yy]>]]
Enables a scheduled warm reboot of the switch. The switch boots
up with the same startup config file and using the same flash
image as before the reload.
Caution: When using redundant management, the reload at/after
command causes a switchover at the scheduled time to the other
management module, which may not be running the same soft-
ware image or have the same configurations.
Parameters include:
• after: Schedules a warm reboot of the switch after a given
amount of time has passed.
• at: Schedules a warm reboot of the switch at a given time.
The no form of the command removes a pending reboot request.
For more details and examples, see below.
6-29
To Next Page
Loading...
Need help?
General