Software Management

Downloading switch documentation and software from the web

You can download software updates and the corresponding product documentation from the HP Networking website. Check the website frequently for the latest software version available for your switch.

Viewing or downloading the software manual set

Go to: www.hp.com/networking/support

Downloading software updates for your switch

HP periodically provides switch software updates through the HP Networking website (www.hp.com/networking/support). After you acquire the new software file, you can use one of the following methods for downloading it to the switch:

For a TFTP transfer from a server, do either of the following:
- Select Download OS in the Main Menu of the switch’s menu interface and use the (default) TFTP option.
- Use thecopy tftp command in the switch’s CLI (see below).
For an Xmodem transfer from a PC or Unix workstation, do either of the following:
- Select Download OS in the Main Menu of the switch’s menu interface and select the XMODEM option.
- Use the copy xmodem command in the switch’s CLI (page Xmodem download from a PC or Unix workstation).
Use the USB port to download a software file from a USB flash drive (page Using USB to download switch software).
Use the download utility in PCM+ management software.


	NOTE: Downloading new software does not change the current switch configuration. The switch configuration is contained in a separate file that can also be transferred, for example, to archive or to be used in another switch of the same model.

This section describes how to use the CLI to download software to the switch. You can also use the menu interface for software downloads. For more information, see Using the Menu Interface in this guide.

TFTP download from a server

Syntax

copy tftp flash <ip-address> <remote-os-file> [ <primary | secondary> ]

Note that if you do not specify the flash destination, the TFTP download defaults to the primary flash.

For example, to download a software file named K_15_10_0001.swi from a TFTP server with the IP address of 10.28.227.103:

Execute the copy command as shown below:

HP Switch# copy tftp flash 10.28.227.103
K_15_10_0001.swi
The primary OS image will be deleted. continue
continue[y/n]? Y
03125K

When the switch finishes downloading the software file from the server, it displays the progress message
```
Validating and Writing System Software to FLASH...
```
When the CLI prompt re-appears, the switch is ready to reboot to activate the downloaded software:
1. Use the show flash command to verify that the new software version is in the expected flash area (primary or secondary)
2. Reboot the switch from the flash area that holds the new software (primary or secondary), using the following command:
Syntax

boot system flash [ <primary | secondary> ]

After the switch reboots, it displays the CLI or Main Menu, depending on the Logon Default setting last configured in the menu’s Switch Setup screen.
Verify the software version by displaying the system information for the switch (for example, through the show system-information command), and viewing the Software revision field.

Xmodem download from a PC or Unix workstation

This procedure assumes that:

The switch is connected via the Console RS-232 port to a PC operating as a terminal. (See your switch Installation and Getting Started Guide for information on connecting a PC as a terminal and running the switch console interface.)
The switch software is stored on a disk drive in the PC.
The terminal emulator you are using includes the Xmodem binary transfer feature. (For example, in the HyperTerminal application included with most Windows systems, the Send File option in the Transfer drop-down menu supports the Xmodem protocol.)

Using Xmodem and a terminal emulator, you can download a switch software file to either primary or secondary flash using the CLI.

Syntax

copy xmodem flash [ [<primary] | secondary> ]

To reduce the download time, you may want to increase the baud rate in your terminal emulator and in the switch to a value such as 115200 bits per second. (The baud rate must be the same in both devices.) For example, to change the baud rate in the switch to 115200, execute this command:
```
HP Switch(config)# console baud-rate 115200
```
(If you use this option, be sure to set your terminal emulator to the same baud rate.)

Changing the console baud-rate requires saving to the Startup Config with the write memory command. Alternatively, you can logout of the switch and change your terminal emulator speed and allow the switch to Auto-Detect your new higher baud rate (i.e., 115200 bps)

Execute the following command in the CLI:

HP Switch# copy xmodem flash primary
The primary OS image will be deleted. continue [y/n]? Y
Press ‘Enter’ and start XMODEM on your host...

Execute the terminal emulator commands to begin the Xmodem transfer. For example, using HyperTerminal:
1. Click on Transfer, then Send File.
2. Type the file path and name in the Filename field.
3. In the Protocol field, select Xmodem.
4. Click on the Send button.
The download can take several minutes, depending on the baud rate used in the transfer.
If you increased the baud rate on the switch (1), use the same command to return it to its previous setting. (A baud rate of 9600 bits per second is recommended for most applications.) Remember to return your terminal emulator to the same baud rate as the switch.
Use theshow flash command to verify that the new software version is in the expected flash area (primary or secondary).
Reboot the switch from the flash area that holds the new software (primary or secondary).

After the switch reboots, it displays the CLI or Main Menu, depending on the Logon Default setting last configured in the menu’s Switch Setup screen.

Using USB to download switch software

To use the USB port on the switch to download a software version from a USB flash drive:

The software version must be stored on the USB flash drive, and you must know the file name (such as K_15_10_0001.swi).

The USB flash drive must be properly installed in the USB port on the switch.


	NOTE: Some USB flash drives may not be supported on your switch. For information on USB device compatibility, See the HP networking support (www.hp.com/networking/support).

Syntax

copy usb flash <filename> [ <primary | secondary> ]

For example, to download a software file named K_15_10_0001.swi from a USB flash drive:

Execute thecopy command as shown below:

HP Switch# copy usb flash K_15_10_0001.swi
secondary
The secondary OS image will be deleted. continue
[y/n]? Y
03125K

When the switch finishes downloading the software file from the server, it displays the progress message
```
Validating and Writing System Software to FLASH...
```
When the CLI prompt re-appears, the switch is ready to reboot to activate the downloaded software:
1. Use the show flash command to verify that the new software version is in the expected flash area (primary or secondary)
2. Reboot the switch from the flash area that holds the new software (primary or secondary), using the following command:
Syntax

boot system flash [ <primary | secondary> ]

After the switch reboots, it displays the CLI or Main Menu, depending on the Logon Default setting last configured in the menu’s Switch Setup screen.
Verify the software version by displaying the system information for the switch (for example, through the show system-information command), and viewing the Software revision field.

Software signing and verification

As an enhanced security feature, you can verify whether a software image being downloaded to or stored in your switch has, in fact, been provided by HP Networking without any modification or corruption.

Validation is based on the image signature that is generated and attached to the switch software by HP Code Signing Service (HPCSS). HP Networking implemented digital signature validation starting with specific switch software versions. For a list of these software versions, go to: www.hp.com/networking/swvalidation.


	NOTE: Once a switch software image has been digitally signed on a specific version, all later versions will also be signed.

Switches supporting digital signature verification will generate an error message if you attempt to download an image that is not digitally signed. For example, using the CLI commands described above to revert back to an image that isn’t signed from an image that is signed and supports verification would result in the following message:

This software image does
not contain a digital signature and
cannot be validated as originating
from HP. You may bypass this
validation by using the
'allow no-signature’ option. Please
see www.hp.com/networking/swvalidation
for information about which versions
of software contain digital signatures.

When you use the copy command to download a properly signed image, the CLI logs the following syslog message:

Update: Firmware image contains valid signature.

Errors related to signature validation will generate one of the following log messages:

Update: Aborted. Downloaded file invalid.
Update: Aborted. Firmware image does not contain a signature. 
Update: Aborted. Firmware image signature is not valid.

Using the CLI to validate or bypass a signature verification

Manually validating software. If necessary, you can validate software that does not support signature verification by executing the following command:

verify signature flash {primary|secondary}

If the signature is valid, the following message will be displayed:

Signature is valid.

Bypassing verification. If necessary, you can use the allow-no-signature option to bypass signature verification. To do this, execute thecopy command as follows:

copy {tftp|sftp|usb|xmodem} flash [<hostname/IP>] [<filename>] {primary|secondary} allow-no-signatures


	NOTE: The allow-no-signature option is available on switches that support non-signed legacy software releases and should be used with caution. To determine support for your switch, go to: www.hp.com/networking/swvalidation.

Important: Best Practices for software updates


	NOTE: With version K.15.01.0031 and later software, you will notice a slight change in the versioning system.

Software updates that contain significant new features and enhancements may be designated by an increment to both the major and minor release version numbers. That is, K.15.01.0031 represents a major update to software version(s) K.14.xx, and K.14.xx represents a major update to K.13.xx, and so forth. In addition, a future version (such as K.15.02.xxxx) may represent a minor release to version K.15.01.xxxx, but may still contain significant changes. To mitigate against potential migration issues when performing such updates, this section documents best practices for updating the switch, including contingency procedures for rolling back to previous software versions and saved configurations.

Updating the switch

Overview

CAUTION: Before you update the switch software to a new version:

We strongly recommend that you save a copy of your config file to an external location.
We advise against rolling back (going from a newer software version to an older software version) without copying a backup config file to the device.

If you do choose to downgrade software using your existing config file, unpredictable changes in the config file and switch behavior may occur. If booting a K.15.01.0031 or later config file into a K.14.xx or earlier versions of software, the following commands may be removed from your config file:

Any commands that are present in K.15.01.0031 (or later) but are not present in earlier versions of software
logging
snmp-server
mirror-session
auto-tftp
filter source-port
fault-finder
interface loopback

To perform an update to your switch software, follow the steps below (see Detailed steps:

Download the image to your TFTP server.
Save your current configuration (Config1) to a backup configuration file (Config2).
Save your current configuration to an external tftp server.
Backup your current running image (Primary) to the secondary image.
Set your secondary image to boot with Config2.
Download the new image to the switch’s primary image.
Verify that your images and configuration are set correctly.
Reload the switch.

After following these steps, you should end up with the following results:

Primary image will hold the new software image you want to install (for example, K.15.01.0031)
Secondary image will hold the image you are currently running (for example, K.14.47)
Primary image will boot with Config1 (config file corresponding to new software version—in this example, K.15.01.0031)
Secondary image will boot with Config2* (config file corresponding to previous software version—in this example, K.14.47)

* The current config file must be copied to Config2, or you will be unable to revert if the need arises.


	NOTE: You might opt to use a different methodology in which the new software will be installed as the secondary and not the primary image, in which case you would use the commands boot system flash secondary, and/or boot set-default flash secondary to change the location of the default boot. However, since you will still need to take precautions to allow you to revert to your previous configuration, We strongly recommend that you follow the methods that are proposed in our update process. This will ensure that you can use our proposed roll back procedures should the need arise.

Detailed steps

The following detailed steps shows how to update the switch software from an existing version to a significant new version (in the example provided here, from version K.14.47 to version K.15.01.0031).

Download the latest software image to your TFTP server from the HP networking web site: www.hp.com/networking/support

Save your current configuration (Config1) to backup configuration file (Config2).

Before copying the config, verify the current state of your system using theshow version, show flash and show config files commands. For example:

Switch1# show version
Image stamp:   /sw/code/build/btm(t4a)
               Nov 6 2009 13:20:26
               K.14.47
               188
Boot Image:    Primary

Switch1# show flash
Image           Size(Bytes)   Date    Version
------          -----------  -------  -------
Primary Image   : 9839140    11/06/09 K.14.47
Secondary Image : 0
Boot Rom Version: K.12.20
Default Boot    : Primary

Switch1# show config files

Configuration files:

 id | act pri sec | name
 ---+-------------+-----------------------------
  1 | *    *   *  | config1
  2 |             | 
  3 |             |

Create a backup configuration file and verify the change.

Switch1# copy config config1 config config2
Switch1# show config files

Configuration files:

 id | act pri sec | name
 ---+-------------+-----------------------------
  1 | *    *   *  | config1
  2 |             | config2
  3 |             |

Save the current config to a tftp server using the copy tftp command. For example:

Switch1# copy startup-config tftp 10.1.1.60
Switch1_config_K_14_47.cfg


	NOTE: This step is necessary because HP switches do not support roll back (going from a newer software version to an older software version) without the ability to copy a backup config file onto the device.

Backup your current running image (primary) to the secondary image.

Switch1# copy flash flash secondary

Switch1# show flash
Image           Size(Bytes)   Date    Version
------          -----------  -------  -------
Primary Image   :  9839140   11/06/09 K.14.47
Secondary Image :  9839140   11/06/09 K.14.47
Boot Rom Version: K.12.20
Default Boot    : Primary

Set your secondary image to boot with Config2.

Switch1# startup-default secondary config config2 

Switch1# show config files

Configuration files:

 id | act pri sec | name
 ---+-------------+-----------------------------
  1 | *    *      | config1
  2 |          *  | config2
  3 |             |


	NOTE: Step 5 will enable you to revert from K.15.01.xxxx to your previous image with your previous configuration just by invoking the command boot system flash secondary.

Download the new primary image.
```
Switch1# copy tftp flash 192.168.1.60
K_15_10_0001.swi primary
The Primary OS Image will be deleted, continue [y/n]?
```
At the prompt, enter ‘y’ for yes, and the new image will be downloaded and written to the File system. Once tftp download has been completed you will see the following message:
```
Validating and Writing System Software to the
Filesystem ...
```

Verify that your images and configuration are set correctly. For example, if you updated from K.14.47 to K.15.01.0031, you should see the following outputs from the switch show commands:

Switch1# show version
Image stamp:   /sw/code/build/btm(t4a)
               Nov 6 2009 13:20:26
               K.14.47
               188
Boot Image:    Primary


Switch1# show flash
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 |             |

Reload the new switch image.

Switch1# reload
System will be rebooted from primary image. Do you want
to continue [y/n]? y

At the prompt, enter ‘y’, for yes, and the switch will boot with the new image.


	NOTE: As an additional step, we recommend saving the startup-config to a tftp server using the copy tftp command. For example: Switch1# copy startup-config tftp 10.1.1.60 Switch1_config_K_15_10_0001.cfg

Rolling back switch software

If you have followed the update procedures documented in the previous section, you should be able to revert to your previous configuration and software version using the steps below.

CAUTION: Long usernames and passwords. Software versions K.15.01.0032 and later support the longer usernames and passwords introduced in K.14.59.

Before downgrading to a software version that does not support long user-names and passwords, use one of the following procedures:

Using the password CLI command or the Web browser interface, change usernames or passwords to be no more than 16 characters in length, and without any special characters. Then execute a CLI write memory command (required if the include-credentials feature has ever been enabled).
Clear the values using the no password all CLI command. Then execute a CLI write memory command (required if the include-credentials feature has ever been enabled).
Clear password values by using the "Clear" button on the switch. Then execute a CLI write memory command (required if the include-credentials feature has ever been enabled).

Note: The procedures above should be used only when downgrading from a software version that supports long usernames and passwords to a version that does not.

To roll back your switch from K.15.01.0031 to K.14.47, for example, follow the steps below:

Verify that your images and configuration are set correctly using the show version, show flash and show config files commands.

Switch1# show version
Image stamp:   /sw/code/build/btm(t5a)
               Apr 23 2010 05:43:42
               K.15.01.0031
               67
Boot Image:    Primary


Switch1# show flash
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 |             |

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:

HP Switch-onK1501# show config K1447config <cr>

The command output will show how the K.14.47 config would be interpreted if it were to be used by the K.15.01.0031 software. Copying the K1447config file to a TFTP server would similarly trigger an interpretation by the software performing the file transfer. Note, however, that this does not actually change the configuration. If the version is rolled back from K.15.01.0031 to K.14.47 with a command like the following (given that K.14.47 is stored in secondary flash), the K.14.xx formatted config is still intact and valid.

HP Switch# boot system flash secondary config
K1447config

This "interpretation" during a TFTP or show command execution is inherent in the architecture of the switch. When switch features change significantly (such as the move from IPv4 support to IPv6 support), there may be configuration parameters from the previous config that cannot be translated by the switch for viewing while it is running the new software. This necessitates storing configurations for each version of software to an external location, if the user would like to view the stored config prior to reloading it.

prev		next
Configuring a single source IP address	home	Job Scheduler