for theProCurve Series 3500yl, 6200yl, 5400zl, and 8212zl Switches
These release notes include information on the following:
■Downloading switch software and documentation from the Web (page 2)
■Best practices for major software updates, including contingency procedures for rolling back
to previous software versions and configurations. Please read before updating software
versions from K.12.xx to K.13.xx (page 7).
■Notes for ROM updates required for all yl and zl switches running K.13.45 or earlier (page 17)
■Clarifications for certain software features (page 20)
■A listing of software enhancements in recent releases (page 26)
■A listing of software fixes included in releases K.11.11 through K.13.49 (page 145)
■Support Notes and Known Issues in releases K.11.11 through K.13.49 (page 17)—includes
"Security notes about SNMP access to the hpSwitchAuth MIB objects" and other topics.
Support Notices:
WARNING. Updating to Version K.13.xx: . It is important that you update to K.13.xx from a
configuration that has not been previously converted from a pre-K.13.xx format (e.g. a K.11.xx or
K.12.xx configuration). If you have previously updated to K.13.xx and rolled back to K.12.xx to
workaround an issue, you should load a saved K.12.xx configuration to the switch and boot to it prior
to updating to K.13 again.
Performing major software updates: Before updating your software version from K.12.xx to
K.13.xx, read the recommended best practices for performing major software updates (page 7).
Restriction in number of ACL mirror destinations: The K.13.01 software introduced a new
restriction to a single ACL mirror destination. For more information, see "Restriction in number of
ACL mirror destinations (page 24) .
PIM-SM: PIM-SM users should make sure ProCurve switches that run K software should all be on
the either pre-K.13.21 or post-K.13.21 versions of software due to a bug fix in K.13.21 that changes
the way a rendezvous point is chosen.
ProCurve Switch 3500yl-24G-PWR Intelligent Edge (J8692A)
ProCurve Switch 3500yl-48G-PWR Intelligent Edge (J8693A)
ProCurve Switch 6200yl-24G-mGBIC (J8992A)
ProCurve Switch 5406zl (J8697A)
ProCurve Switch 5412zl (J8698A)
ProCurve Switch 5406zl-48G (J8699A)
P r o C u r v e S w i t c h 5 4 1 2 z l - 9 6 G ( J 8 7 0 0 A )
P r o C u r v e S w i t c h 8 2 1 2 z l ( J 8 7 1 5 A )
Trademark Credits
Microsoft®, Windows®, and Windows NT® are US
registered trademarks of Microsoft Corporation.
Adobe® and Acrobat® are trademarks of Adobe Systems
Incorporated. Java™ is a US trademark of Sun
Microsystems, Inc.
Disclaimer
HEWLETT-PACKARD COMPANY MAKES NO WARRANTY
OF ANY KIND WITH REGARD TO THIS MATERIAL,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS
FOR A PARTICULAR PURPOSE. Hewlett-Packard shall not
be liable for errors contained herein or for incidental or
consequential damages in connection with the furnishing,
performance, or use of this material.
The only warranties for HP products and services are set
forth in the express warranty statements accompanying
such products and services. Nothing herein should be
construed as constituting an additional warranty. HP shall
not be liable for technical or editorial errors or omissions
contained herein.
Hewlett-Packard assumes no responsibility for the use or
reliability of its software on equipment that is not furnished
by Hewlett-Packard.
Warranty
See the Customer Support/Warranty booklet included with
the product.
A copy of the specific warranty terms applicable to your
Hewlett-Packard products and replacement parts can be
obtained from your HP Sales and Service Office or
authorized dealer.
Software Credits
SSH on ProCurve Switches is based on the OpenSSH software toolkit. This product includes software developed by
the OpenSSH Project for use in the OpenSSH Toolkit. For
more information on OpenSSH, visit
www.openssh.com
SSL on ProCurve Switches is based on the OpenSSL software toolkit. This product includes software developed by
the OpenSSL Project for use in the OpenSSL Toolkit. For
more information on OpenSSL, visit
www.openssl.org.
This product includes cryptographic software written by
Eric Young (eay@cryptsoft.com). This product includes
software written by Tim Hudson (tjh@cryptsoft.com)
.
Hewlett-Packard Company
8000 Foothills Boulevard, m/s 5551
Roseville, California 95747-5551
The ProCurve 3500yl and 5400zl switches ship with the ProCurve Intelligent Edge software feature
set. The additional Premium License switch software features for the 3500yl and 5400zl switches can
be acquired by purchasing the optional Premium License and installing it on the Intelligent Edge
version of these switches. As of February 2008, the Premium License features include the following:
•OSPF
•PIM Dense mode
•PIM Sparse mode
•VRRP
•QinQ
Part numbers for the Premium Licenses are:
•3500yl switches: J8993A
•5400zl switches: J8994A
All software features are automatically included on the ProCurve 6200yl and 8212zl switches without
the need for a Premium License.
To purchase a Premium License for the 3500yl or 5400zl switches, go to the following Web page and
click on How To Buy.
www.hp.com/rnd/accessories/J8994A/accessory.htm
To view or download a listing of Intelligent Edge and Premium License features, refer to the Software Features Index available for download on the product documentation page for your switch model.
Note:
Switch software Version K.11.33 software or newer is required for proper functioning of Intelligent
Edge features on ProCurve Switch 3500yl series, and ProCurve Switch 5400zl series
Software Updates
Check the ProCurve Networking Web site frequently for free software updates for the various
ProCurve switches you may have in your network.
1
Download Switch Documentation and Software from the Web
Software Management
Download Switch Documentation and Software from the Web
You can download software updates and the corresponding product documentation from the
ProCurve Networking Web site as described below.
View or Download the Software Manual Set
Go to: www.procurve.com/manuals
You may want to bookmark this Web page for easy access in the future.
You can also register on the My ProCurve portal to receive a set of ProCurve switch manuals on
CD-ROM. To register and request a CD, go to www.procurve.com and click on My ProCurve Sign In.
After registering and entering the portal, click on My Manuals.
Downloading Software to the Switch
ProCurve Networking periodically provides switch software updates through the ProCurve
Networking Web site (www.procurve.com). 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 the copy 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 3).
■Use the USB port to download a software file from a USB flash drive (page 5).
■Use the download utility in ProCurve Manager Plus.
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, for archive purposes
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, refer to the Management and Configuration Guide for your switch.
2
Software Management
Download Switch Documentation and Software from the Web
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.
4.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. (Refer
to the Installation and Getting Started Guide you received with the switch 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 Windows NT, you would use the
Send File option in the Transfer drop-down menu.)
Using Xmodem and a terminal emulator, you can download a switch software file to either primary
or secondary flash using the CLI.
3
Download Switch Documentation and Software from the Web
1.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:
ProCurve(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 AutoDetect your new higher baud rate (i.e. 115200 bps)
2.Execute the following command in the CLI:
ProCurve # copy xmodem flash primary
The primary OS image will be deleted. continue [y/n]? Y
Press ‘Enter’ and start XMODEM on your host...
3.Execute the terminal emulator commands to begin the Xmodem transfer. For example, using
HyperTerminal:
a.Click on Transfer, then Send File.
b.Type the file path and name in the Filename field.
c.In the Protocol field, select Xmodem.
d.Click on the Send button.
The download can take several minutes, depending on the baud rate used in the transfer.
4.If you increased the baud rate on the switch (step 1), use the same command to return it to its
previous setting. (ProCurve recommends a baud rate of 9600 bits per second for most applications.) Remember to return your terminal emulator to the same baud rate as the switch.)
5.Use the show flash command to verify that the new software version is in the expected flash
area (primary or secondary)
6.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.
4
Software Management
Download Switch Documentation and Software from the Web
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_12_10.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, refer to the HP ProCurve support Website:
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.
4.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.
5
Saving Configurations While Using the CLI
Software Management
Saving Configurations While Using the CLI
The switch operates with two configuration files:
■Running-Config File: Exists in volatile memory and controls switch operation. Rebooting
the switch erases the current running-config file and replaces it with an exact copy of the
current startup-config file. To save a configuration change, you must save the running
configuration to the startup-config file.
■Startup-Config File: Exists in flash (non-volatile) memory and preserves the most
recently-saved configuration as the “permanent” configuration. When the switch reboots for
any reason, an exact copy of the current startup-config file becomes the new running-config
file in volatile memory.
When you use the CLI to make a configuration change, the switch places the change in the
running-config file. If you want to preserve the change across reboots, you must save the change to
the startup-config file. Otherwise, the next time the switch reboots, the change will be lost. There are
two ways to save configuration changes while using the CLI:
■Execute write memory from the Manager, Global, or Context configuration level.
■When exiting from the CLI to the Main Menu, press [Y] (for Yes) when you see the “save
configuration” prompt:
Do you want to save current configuration [y/n]?
6
Software Management
Best Practices for Major Software Updates
Best Practices for Major Software Updates
Major software updates contain new features and enhancements, and are designated by an increment
to the major release version number. That is, K.12.xx represents a major update to software version(s)
K.11.xx, and K.13.xx represents a major update to K.12.xx, and so forth. To mitigate against potential
migration issues when performing such an update, this section documents best practices for updating
the switch, including contingency procedures for rolling back to previous software versions and
saved configurations.
Caution
Before you update the switch software to a major new version, ProCurve strongly recommends that
you save off a copy of your config file to an external location. ProCurve advises against rolling back
(going from a newer software version to an older software version) without copying on a backup
config file to the device.
Updating the Switch: Overview
To perform a major update to your switch software, follow the steps below (see page 8 for details):
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.
7.Verify that your images and configuration are set correctly.
8.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.13.06)
■Secondary image will hold the image you are currently running (for example, K.12.57)
■Primary image will boot with config1 (config file corresponding to new software version—in
this example, K.13.06)
■Secondary image will boot with config2* (config file corresponding to previous software
version—in this example, K.12.57)
* The current config file must be copied to config2, or you will be unable to revert if the need arises.
7
Best Practices for Major Software Updates
Software Management
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,
ProCurve strongly recommends 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.
Updating the Switch: Detailed Steps
The following detailed steps shows how to update the switch software from an existing version to a
major new release (in the example provided here, from version K.12.57 to version K.13.06).
1.Download the latest release software image to your TFTP server from the ProCurve Web site.:
http://www.hp.com/rnd/software/switches.htm
2.Save your current configuration (Config1) to backup configuration file (Config2).
a.Before copying the config, verify the current state of your system using the show version,
show flash, and show config files commands. For example:
Switch1# show version
Image stamp: /sw/code/build/btm(t2g)
Dec 7 2007 14:54:57
K.12.57
2415
Boot Image: Primary
Switch1# show flash
Image Size(Bytes) Date Version
This step is necessary because ProCurve does 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.
4.Backup your current running image (primary) to the secondary image.
Switch1# copy flash flash secondary
Switch1# show flash
Image Size(Bytes) Date Version
This step will enable you to revert from K_13_05 to your previous image with your previous
configuration just by invoking the command boot system flash secondary.
6.Download the new primary image.
Switch1# copy tftp flash 192.168.1.60 K_13_06.swi primary
The Primary OS Image will be deleted, continue [y/n]?
At the prompt, answer 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 ...
7.Verify that your images and configuration are set correctly. For example, if you updated from
K.12.57 to K.13.06, you should see the following outputs from the switch show commands:
Switch1# show version
Image stamp: /sw/code/build/btm(t2g)
Mar 14 2008 09:59:53
K.12.57
2415
Boot Image: Primary
Switch1# show flash
Image Size(Bytes) Date Version
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.
To roll back your switch from K.13.06 to K.12.57, for example, follow the steps below:
1.Verify that your images and configuration are set correctly using the show version, show flash,
and show config files commands.
11
Switch1# show version
Image stamp: /sw/code/build/btm(t2g)
Mar 14 2008 09:59:53
K.13.06
211
Boot Image: Primary
Switch1# show flash
Image Size(Bytes) Date Version
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
Answer y, for yes, and the switch will boot from the secondary image (K.12.57, 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.12.57 and saved as config2, and if
it is then viewed or transferred while the switch is running K.13.06, it will appear as though K.13.06
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.12.57 to a TFTP server with an IP address of 10.10.10.15 as
follows:
If, for example, the user deems it necessary to revert to the use of K.12.57, she 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.12.57 and then saved to flash:
And later, the configuration that was created on K.12.57 is viewed while the switch is running K.13.06:
ProCurve5406zl-onK1306# show config K1257config <cr>
The command output will show how the K.12.57 config would be interpreted, if it were to be used
by the K.13.06 software. Copying the K1257config 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.13.06 to K.12.57 with a command like
the following (given that K.12.57 is stored in secondary flash), the K.12.xx formatted config is still
intact and valid.
ProCurve5406zl# boot system flash secondary config K1257config
This “interpretation” during a TFTP or show command execution is inherent in the architecture of
the switch. When switch features change significantly (e.g. 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.
13
ProCurve Switch, Routing Switch, and Router Software Keys
Software Management
ProCurve Switch, Routing Switch, and Router Software Keys
Software
Letter
CYSwitch 8100fl Series (8108fl and 8116fl)
ProCurve Networking Products
C1600M, 2400M, 2424M, 4000M, and 8000M
ESwitch 5300xl Series (5304xl, 5308xl, 5348xl, and 5372xl)
FSwitch 2500 Series (2512 and 2524), Switch 2312, and Switch 2324
GSwitch 4100gl Series (4104gl, 4108gl, and 4148gl)
HSwitch 2600 Series, Switch 2600-PWR Series: H.07.81 and earlier, or H.08.55 and greater,
Switch 2600-8-PWR requires H.08.80 or greater.
Switch 6108: H.07.xx and earlier
ISwitch 2800 Series (2824 and 2848)
JSecure Router 7000dl Series (7102dl and 7203dl)
KSwitch 3500yl Series (3500yl-24G-PWR and 3500yl-48G-PWR), Switch 6200yl-24G, 5400zl Series (5406zl,
5406zl-48G, 5412zl, 5412zl-96G) and Switch 8212zl.
LSwitch 4200vl Series (4204vl, 4208vl, 4202vl-72, and 4202vl-48G)
MSwitch 3400cl Series (3400-24G and 3400-48G): M.08.51 though M.08.97, or M.10.01 and greater;
Series 6400cl (6400cl-6XG CX4, and 6410cl-6XG X2 ): M.08.51 though M.08.95, or M.08.99 to M.08.100 and
greater.
All yl and zl switches running K.12.45 system software or earlier, will have the BootROM updated by
this new version of system software. This software download will boot the switch twice, first to
update the BootROM to version K.12.14, and then to load the system software. Following file copy
to the switch flash and initiation of the reload, no additional user intervention is needed. Do not interrupt power to the switch during this important update.
To confirm that the boot ROM and system software have updated successfully following a reload into
software version K.13.49 or newer, follow the process below at your switch CLI.
ProCurve_zl_yl_Switch# show flash
Image Size(Bytes) Date Version
----- ---------- -------- -------
Primary Image : 7497667 12/10/08 K.13.49 <--Indicates that system software is
updated
Secondary Image : 7497667 12/10/08 K.13.49
Boot Rom Version: K.12.14 <-- Indicates the boot ROM is updated
Default Boot : Primary
Using SNMP To View and Configure Switch Authentication Features
Beginning with software release K.12.01, manager read/write access is available for a subset of the
SNMP MIB objects for switch authentication (hpSwitchAuth) features. That is, in the default state,
a device with management access to the switch can view the configuration for several authentication
features, and using SNMP sets, can change elements of the authentication configuration.
Security Note
In the default configuration for SNMP MIB object access, SNMP sets can be used to reconfigure
password and key MIB objects. This means that a device operating as a management station with
access to the switch can be used to change the SNMP MIB settings. This can pose a security risk if
the feature is used to incorrectly configure authentication features or to reconfigure authentication
features to unauthorized settings.
If you want to block the SNMP MIB object access described above, use the following command to
disable the feature:
For more information on the above topic, refer to "Using SNMP To View and Configure Switch
Authentication Features" in the "RADIUS Authentication and Accounting" chapter of the Access Security Guide for your switch. For an overview of the security features available on the switch,
refer to chapter 1, "Security Overview", in the Access Security Guide for your switch.
Security:
Downloading and booting software release K.12.01 or greater for the first time automatically
enables SNMP access to the hpSwitchAuth MIB objects. If this is not desirable for your network,
ProCurve recommends that you disable it after downloading and rebooting with the latest switch
software.
ACL numbering restrictions:
The K.12.01 release enforces ACL numbering restrictions.
See the Note under Version K.12.01 Software Fixes on page 160 (PR_1000389442) for details.
OSPF virtual link:
OSPF virtual links configurations will be lost with the update to K.12.01.
Support Notes
See the Note under Version K.12.01 Software Fixes on page 161 (PR_1000374003) for details.
MSTP auto-edge-port support and default settings:
With version K.12.04 (page 33), automatic detection of edge ports is supported, along with revised
command options and default settings.
Resources (PR_1000388697):
When the switch is writing large files to flash (for example, a transfer of a very large configuration
or a software update), switch resources may be impacted during the write operation, causing
some potential loss of hello packets. This may impact VRRP, OSPF or spanning tree protocol. In
order to mitigate potentially undesirable affects, updates to the switch software should be made
during a scheduled downtime. Increasing the hello interval of time sensitive protocols may also
assist with mitigation of this issue.
Support for the Wireless Edge Services zl Module
The addition of support for the zl Wireless Edge Services Module will change the way in which radio
ports are treated by the zl and yl Series Switches. If the default setting of LLDP auto-provisioning is
left intact, LLDP information from the ProCurve Radio Ports (J9004A, J9005A, J9006A) will trigger
these devices to be placed into VLAN 2100 or the first available VLAN not already configured above
that (see the section entitled Using Auto-Provisioning to Establish a Radio Port VLAN in the
18
Support Notes
Minimum Software Versions
Management and Configuration Guide for ProCurve Wireless Edge Services zl Module here:
administrators who do not wish to have the radio ports moved to the auto-provisioned VLAN should
disable this feature with the command "no lldp auto-proision" at the CLI.
). Network
CAUTION: Updating to Version K.13.xx
It is important that you update to K.13.xx from a configuration that has not been previously converted
from a pre-K.13.xx format (e.g. a K.11.xx or K.12.xx configuration). If you have previously updated
to K.13.xx and rolled back to K.12.xx to workaround an issue, you should load a saved K.12.xx
configuration to the switch and boot to it prior to updating to K.13 again.
19
Loading...
+ 189 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.