Basic Operation Guide 2014/02

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” (page
130):
1. Download the image to your TFTP server.
2. Save your current configuration (Config1) to a backup configuration file (Config2).
3. Save your current configuration to an external tftp server.
4. Backup your current running image (Primary) to the secondary image.
5. Set your secondary image to boot with Config2.
6. Download the new image to the switch’s primary image.
Downloading switch documentation and software from the web 129