Switch Memory and Configuration
Multiple Configuration Files
Changing the Reboot Configuration Policy.
For a given reboot, the
switch automatically reboots from the startup-config file assigned to the flash
location (primary or secondary) being used for the current reboot. The switch
copies the existing startup-config file (named
oldConfig
) into memory slot 2,
renames this file to
workingConfig
, and assigns
workingConfig
as:
■
The active configuration file
■
The configuration file to use when booting from either primary or second
ary flash.
In this case, the switch is configured to automatically use the
workingConfig
file in memory slot 2 for all reboots. (Refer to figure 6-19 on page page 6-27.)
You can use the following command to change the current policy so that the
switch automatically boots using a different startup-config file.
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.
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-29.
For example, suppose:
■
Software release R.11.01 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
6-28
Summary of Contents for ProCurve 2610-24
Page 1: ...Management and Configuration Guide 2610 2610 PWR ProCurve Switches R 11 XX www procurve com ...
Page 2: ......
Page 18: ...xvi ...
Page 24: ...Product Documentation xxii ...
Page 54: ...Using the Menu Interface Where To Go From Here 3 16 ...
Page 94: ...Using the Web Browser Interface Status Reporting Features 5 24 ...
Page 132: ...Switch Memory and Configuration Multiple Configuration Files 6 38 ...
Page 148: ...Interface Access and System Information System Information 7 16 ...
Page 192: ...Time Protocols SNTP Messages in the Event Log 9 24 ...
Page 256: ...Power Over Ethernet PoE Operation PoE Event Log Messages 11 18 ...
Page 280: ...Port Trunking Port Status and Configuration 12 24 ...
Page 362: ...File Transfers Copying Diagnostic Data to a Remote Host PC or Unix Workstation A 24 ...
Page 438: ...Troubleshooting Restoring a Flash Image C 48 ...
Page 446: ...MAC Address Management Viewing the MAC Addresses of Connected Devices D 8 ...
Page 450: ...Daylight Savings Time on ProCurve Switches Configuring Daylight Savings Time E 4 ...
Page 462: ...12 Index ...
Page 463: ......