Basic Operation Guide 2014/02

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 58 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.
Example 59 Creating and assigning a new startup-config file
HP Switch(config)# copy config config1 config config2
HP Switch(config)# startup-default secondary config config2
HP Switch(config)# show config files
Configuration files:
id | act pri sec | name
---+-------------+-----------------------------------------------
1 | * * | Config1
2 | * | Config2
3 | |
NOTE: You can also generate a new startup-config file by booting the switch from a flash memory
location from which you have erased the currently assigned startup-config file. See "Erasing a
Startup-Config File" in the next section.
Erasing a startup-config file. You can erase any of the startup-config files in the switch’s memory
slots. In some cases, erasing a file causes the switch to generate a new, default-configuration file
for the affected memory slot.
In a redundant management system, this command erases the config or startup config file on both
the active and the standby management modules as long as redundancy has not been disabled.
If the standby management module is not in standby mode or has failed selftest, the config or
startup config file is not erased.
Syntax:
erase <config <filename>> | startup-config>
config <filename>:
78 Switch Memory and Configuration