Basic Operation Guide 2013/06

Image Size(Bytes) Date Version
------ ----------- ------- -------
Primary Image : 11537788 04/23/10 K.15.01.0031
Secondary Image : 9839140 11/06/09 K.14.47
Boot Rom Version: K.15.09
Default Boot : Primary
Switch1# show config files
Configuration files:
id | act pri sec | name
---+-------------+-----------------------------
1 | * * | config1
2 | * | config2
3 | |
2. Boot the switch using the secondary image (with config2).
Switch1# boot system flash secondary
System will be rebooted from secondary image. Do
you want to continue [y/n]? y
Enter ‘y’ for yes, and the switch will boot from the secondary image (K.14.47, in this example)
with the corresponding configuration for that software version (Config2).
Viewing or transferring alternate configuration files
Viewing or copying an alternate configuration saved to the switch will always be accomplished
through the software currently running on the switch. This may result in a misleading portrayal of
the configuration. For example, if a configuration is created on K.14.47 and saved as config2,
and if it is then viewed or transferred while the switch is running K.15.01.0031, it will appear as
though K.15.01.0031 has converted the configuration. However, the alternate configuration file,
config2, will still be intact on the switch and load properly when the switch is booted into the same
software version from which the configuration file originated.
When an enhancement introduces a feature that did not previously exist in the switch, it may
present several challenges to the user.
Backwards compatibility of the configuration created with a version of software that supports a
new feature or parameter is not guaranteed. Software versions that did not recognize or support
a particular command or parameter will not be able to interpret that line in the configuration. For
this reason, it is strongly recommended that network administrators always save their configuration
while still running the switch with the original software version, and with a notation indicating the
software version on which the configuration was saved. For example, a user might save a
configuration for a switch running K.14.47 to a TFTP server with an IP address of 10.10.10.15
as follows:
HP Switch-onK1447# copy running-config tftp
10.10.10.15 5406onK1447
If, for example, the user deems it necessary to revert to the use of K.14.47, the user can boot into
it and then restore the saved config from the TFTP server.
Viewing or copying an alternate configuration that is saved to the switch flash can be accomplished
only with the software that is currently running on the switch.
Here, for example, a configuration is created on K.14.47 and then saved to flash:
HP Switch-onK1447# copy config config2 config
K1447config <cr>
And later, the configuration that was created on K.14.47 is viewed while the switch is running
K.15.01.0031:
Downloading switch documentation and software from the web 137