Basic Operation Guide 2013/06

Table Of Contents
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 place, you can easily reboot the switch with the correct startup-config
file for either software version.
If the destination startup-config file already exists, it is overwritten by the content
of the source startup-config file.
If the destination startup-config file does not already exist, it will be created in
the first empty configuration memory slot on the switch.
If the destination startup-config file does not already exist, but there are no
empty configuration memory slots on the switch, then a new startup-config file
is not created and instead, the CLI displays the following error message:
Unable to copy configuration to "target-filename".
For example, suppose both primary and secondary flash memory contain software release "A"
and use a startup-config file named config1:
Example 61 Using one startup-config file for both Primary and Secondary flash
HP Switch(config)# show config files
Configuration files:
id | act pri sec | name
---+-------------+-----------------------------------------------
1 | * * * | Config1
2 | |
3 | |
If you wanted to experiment with configuration changes to the software version in secondary flash,
you could create and assign a separate startupconfig file for this purpose.
80 Switch memory and configuration