Basic Operation Guide 2014/02

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.
HP Switch(config)# startup-default pri config minconfig
HP Switch(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:
reload
This command boots the switch from the currently active flash image and
startup-config file. Because reload bypasses some subsystem self-tests, the switch
boots faster than if you use a boot command.
Note: To identify the currently active startup-config file, use the show config files
command.
Managing startup-config files in the switch
Renaming an existing startup-config file
Syntax:
rename config <current-filename> <newname-str>
This command changes the name of an existing startupconfig file. A file name can
include up to 63, alphanumeric characters. Blanks are allowed in a file name
enclosed in quotes (" " or ‘ ‘). (File names are not case-sensitive.)
For redundant management systems, renaming a config file affects both the active
management module and the standby management module, unless redundancy is
disabled or the standby module failed selftest.
Creating a new startup-config file
The switch allows up to three startup-config files. You can create a new startup-config file if there
is an empty memory slot or if you want to replace one startup-config file with another.
Syntax:
copy config <source-filename>
config <target-filename>
This command makes a local copy of an existing startupconfig file by copying the
contents of an existing startupconfig file in one memory slot to a new startup-config
file in another, empty memory slot. This enables you to use a separate configuration
file to experiment with configuration changes, while preserving the source file
unchanged.
It also simplifies a transition from one software version to another by enabling you
to preserve the startup-config file for the earlier software version while creating a
separate startupconfig file for the later software version. With two such versions in
Multiple configuration files 77