Software release 07.8.04a supersedes earlier software releases in the 07.x software branch. (For information
Release Notes
V ersion 07.8.04a Operating System
for the ProCurve 9304M, 9308M, and 9315M Routing Switches
with Redundant Management (M2, M4, EP, and T-Flow), September 2008
about software branches and minimum release requirements for management module support, refer to “Software
Branches” on page 3.)
The 07.8.04a release notes provide information on the following items:
•New hardware and software enhancements introduced with software release 07.8.04a
•Known issues in software release 07.8.04a
•Procedure for upgrading the software code on ProCurve 9304M, 9308M, and 9315M Routing Switches with
M2, M4, or EP Redundant Management modules. See “Upgrading Software on an M2, M4, or EP
Management Module to Release 07.8.04a” on page 7.
•General procedures, usage information, and helpful notes for operating and managing ProCurve routing
switches
•Software fixes in release 07.8.04a and earlier releases
Descriptions of the enhancements in release 07.8.00 are included in the manuals for the 07.8.00 release. If you
purchased a Redundant Management module with software version 07.8.00 or greater installed, the CD shipped
with the module includes the 07.8.00 manuals.
If you need to access ProCurve product documentation, refer to “Downloading the Latest Software and
Documentation” on page 3 for information on how to download PDF versions of the latest manuals.
NOTES:
Software Update Notice: Check the ProCurve Website frequently for free software updates for various ProCurve
switch products. (Refer to “Downloading the Latest Software and Documentation” on page 3.)
Mini-GBIC ports: Hewlett-Packard offers and supports only mini-GBICs having a ProCurve label (with product
number J4858B, J4859B, or J4860B) for use with the following modules:
- J4885A ProCurve 9300 EP 8-port Mini-GBIC Redundant Management Module
- J4894A ProCurve 9300 EP 16-port Mini-GBIC Module
- J8177B ProCurve Gigabit-copper mini-GBIC is supported for use in only the EP modules (J4885A and J4894A)
Use of other brands of mini-GBICs is not supported.
Flash Images: The flash image files for this software release differ depending on the type of management module
you use. Refer to “Boot Code Requirements for ProCurve Software” on page 5.
SNMP: Starting with software release 05.2.16, the software does not have a default read-write SNMP community.
If you use the default community name “private” as the password for web management access or for read-write
access through a network management application, you need to use the CLI to add the read-write community
string first.
Devices Without Redundant Management: For information about how to upgrade software on the ProCurve
9304M and ProCurve 9308M routing switches without redundant management, refer to the latest 6.6.x release
notes. (See “Downloading the Latest Software and Documentation” on page 3.)
The information contained in this document is subject to
change without notice.
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. HewlettPackard 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.
9304M/9308M Redundant Power Supply. . . . (J4147A)
The following table defines basic product terms used in ProCurve routing switch documentation.
TermDefinition
chassis device or chassisA routing switch that accepts optional modules or power supplies. The
ProCurve 9315M, ProCurve 9304M, and ProCurve 9308M routing switches
are chassis devices.
EP (Enhanced Performance)
and Standard
routing switch or routerA Layer 3 device that switches and routes network traffic. The term router is
switchA Layer 2 device that switches network traffic.
ProCurve 9300#An example Command Line Interface (CLI) prompt. Actual prompts show the
Routing switches can be EP or Standard devices, depending on whether the
management module is an EP or Standard (M2 or M4) module. For a listing of
ProCurve routing switches and their product numbers, see Table 4 on page 5.
sometimes used in this document in descriptions of a routing switch’s Layer 3
routing protocol features.
product number for the routing switch, such as ProCurve 9300#.
Product Documentation for Software Release 07.8.04a
Software release 07.8.04a includes all of the features in release 07.8.00a, plus several new features.
•For documentation on the features in 07.8.04a that were avail able in earlier releases, refer to the product
documentation set identified for “Software Version 07.8.00a”.
Table 1 describes the main topics covere d in the ProCurve Routing Switch documentation set. If you do not
already have a PDF version of the 07.8.00a documentation set, refer to “Downloading the Latest Software and
Documentation” on page 3.
1
Product Documentation for Software Release 07.8.04aRelease Notes for 07.8.04
Table 1: Where To Get More Information
TitleContents
Installation and Basic
Configuration Guide
Security Guide•Security (passwords, user accounts, AAA, RADIUS, and TACACS/TACACS+)
•Installation
•Basic Features
•System (SNMP, SNTP, Syslog, broadcast and multicast throttling)
•Port configuration (speed, mode)
•Layer 2 (MAC table parameters, MAC filters, broadcast and multicast
filters, port locks)
•Parameter table resizing
•Port monitoring
•Link Aggregation
•Spanning Tree Protocol
•Virtual LANs
•Layer 2 Multicast
•Base Layer 3
•Upgrading Software (Important: See also “Upgrading Software on an M2,
M4, or EP Management Module to Release 07.8.04a” on page 7 in this
document.)
•Hardware Specifications and RFCs
•Secure Shell (SSH)
•Denial of Service Protection
Advanced Configuration and
Management Guide
Command Line Interface
Reference
Diagnostics Guide•Diagnostic commands
•QoS
•ACLs
•EP rate limiting
•Standard rate limiting
•IP
•RIP
•IP Multicast
•OSPF
•BGP4
•Network Address Translation
•VRRP and VRRPE
•IPX
•AppleTalk
Syntax information for all CLI commands.
•Backplane debugging commands
•Changing CAM partitions
2
Release Notes for 07.8.04Downloading the Latest Software and Documentation
Downloading the Latest Software and Documentation
You can download software version 07.8.04a and the latest routing switch product documentation from the
ProCurve website as described below.
To Download a Software Version:
1.Go to the ProCurve website at http://www.procurve.com.
2.Click on software (in the sidebar).
3.Under “latest software”, click on switches.
NOTE: If you are downloading software for the ProCurve 9304M or ProCurve 9308M, select the option that
matches the type of management module(s) you are using in the routing switch—with redundant management or
without redundant management.
To Download Product Documentation:
For the latest version of product documentation for ProCurve routing switches:
Go to the ProCurve website at http://www.procurve.com.
1.
2.Click on technical support, then manuals.
3.Click on the name of the product for which you want manuals.
4.On the page listing the manuals, find the latest manuals under the heading “For software version 7.8.00a”.
You will need the Adobe® Acrobat® Reader (version 4.0 or greater) to view or print the manuals.
Software Branches
Starting with software releases 06.6.28 and 07.1.10, ProCurve offers the software branches described in Table 2:
Table 2: Software Branches
Software ReleaseIncludes:Operates on:
06.6.28 and later 06.x
releases
07.1.10 and later 07.1.x
releases
07.5.04 releaseBug fixes, new features, and
07.6.00 and 07.6.01b
releases
Bug fixesProCurve 9304M and ProCurve 9308M routing
switches without redundant management (that is,
with M1 modules)
Note: To determine the
FPGA versions running on a
10GE module, enter show flash. The version
information is listed
separately for each 10
Gigabit Ethernet module in
the chassis.
HPR06636.bin
2
M1B07108.bin or greater
recommended
Release Notes for 07.8.04Upgrading Software on an M2, M4, or EP Management Module to Release 07.8.04a
Routing
Switch
ProCurve 6208M-SX—
1
M1 management modules (without Redundant Management) have been discontinued.
2
Does not support Secure Shell (SSH) version 1.
ModulesSoftware ImageMinimum Boot Code
Required
HPS06636.bin
2
M1B07108.bin or greater
recommended
Upgrading Software on an M2, M4, or EP Management Module to
Release 07.8.04a
This section explains how to upgrade the software used on M2, M4, and EP redundant management modules on
a ProCurve 9304M, ProCurve 9308M, or ProCurve 9315M routing switch to release 07.8.04a.
NOTE: As shown in Table 5, newer software versions require newer versions of boot code. Software versions
use a five-digit number in the format: xx.x.xx; for example, 07.8.04a. Boot code versions use a six-digit number in
the format: xx.xx.xx; for example, 07.06.05.
Different procedures are used to upgrade an M2, M4, or EP management module, depending on the version of
software running on the module:
•A software release earlier than 07.6.01b
•Software release 07.6.01b or greater
NOTE: M1 Management modules (discontinued) do not support software releases 07.x.xx, and are, therefore,
not described in this section. The latest software release supported on an M1 management module is 06.6.36.
Restrictions
•Software release 07.8.04a requires boot code version 07.06.05 to support all hardware modules and
decompress new software imag e s .
A new compression algorithm was introduced in software releases greater than 07.6.01b to generate
software images. The new compression algorithm allows a software image to contain more features.
Software release 07.6.01b was introduced as a special release that is used as an intermediate step when you
upgrade to a later software release. After you install release 07.6.01 b and reboot a routing switch, the switch
is able to copy the latest software images to flash memory.
•On an M2, M4, or EP redundant management module, boot code is not automatically copied from the active
to the standby management module. (However, software code is automatically copied to a standby
management module.)
To copy boot code from the active to a standby management module, you must enter the sync boot
command.
•On a ProCurve 9315M, software release 07.5.04 is the earliest release supported. If a management module
is running software earlier than release 07.5.04, you cannot upgrade the module in a 9315M chassis. Instead,
you must upgrade it in a 9304M or 9308M chassis.
Upgrading to Software Release 07.8.04a: Overview
To upgrade an M2, M4, or EP management module to release 07.8.04a, you must follow these general steps:
A. Upgrade the boot code on the management mo dule to version 07.06.05. If necessary, use the sync boot
command to copy boot code from the active to a standby management module in the routing switch. Then reboot
the routing switch to load boot code 07.06.05.
7
Upgrading Software on an M2, M4, or EP Management Module to Release 07.8.04aRelease Notes for 07.8.04
B. If the routing switch is running software EARLIER than release 07.6.01b, copy release 07.6.01b to flash
memory. Then reboot the device to load the 07.6.01b software.
C. Copy release 07.8.04a to flash memory, and reboot the routing switch to load 07.8.04a software.
A. Upgrading Boot Code on a Management Module to Version 07.06.05
To upgrade the boot code on an M2, M4, or EP management module to version 07.06.05:
1.Store boot code version 07.06.05 (filename: M2B07605.bin) on a TFTP server that the routing switch can
access.
2.Enter the following command at the privileged EXEC level of the CLI (for example: ProCurve 9300#) to copy
the boot code from the TFTP server into the flash memory of the management module:
copy tftp flash <ip-addr> <image-file-name> boot
3.Verify that the code has been successfully copied by entering the following command at any level of the CLI:
show flash
The boot code version is displayed on the line that begins with “Boot Image size”. Ensure that boot code
version 07.06.05 is displayed for the active management module.
4.If a standby (redundant) management module is installed in the routing switch, synchronize the boot code on
the standby management module by entering the sync boot command.
Verify that boot code 07.06.05 has been successfully copied on the standby management module by entering
the show flash command.
5.Reboot the routing switch to load boot code 07.06.05.
B. Upgrading Software on a Management Module From a Release Earlier than
07.6.01b
To upgrade the software on an M2, M4, or EP management mo dule from a release EARLIER than 07.6.01b to
release 07.8.04a:
1.Verify the version of boot code installed on the management module by entering the show flash command.
The boot code version is displayed at the end of the line that begins with “Boot Image size”. Ensure that boot
code version 07.06.05 is displayed.
NOTE: The show flash command only displays the version of boot code installed on the device. It does not
display the version of boot code running on the device.
If you rebooted the routing switch after installing boot code 07.06.05 (as described in “A. Upgrading Boot
Code on a Management Module to Version 07.06.05”), the required boot code is running. If you are not sure,
ProCurve recommends that you reboot the device now.
2.Store software release 07.6.01b (filename: H2R07601b.bin) on a TFTP server that the routing switch can
access.
3.Upgrade the software on the management module to version 07.6.01b by entering the following command:
copy tftp flash <ip-address> H2R07601b.bin [primary | secondary]
Where:
primary copies software to the primary (default) storage area in flash memory.
secondary copies software to the secondary area in flash memory.
If no redundant management module is installed, the message TFTP to Flash Done is displayed when the
upgrade is complete.
If a redundant management module is installed, the message Sync Secondary code in flash...Done
8
Release Notes for 07.8.04Upgrading Software on an M2, M4, or EP Management Module to Release 07.8.04a
is displayed when the flash images are synchronized and the upgrade is complete.
4.Verify that the software has been successfully copied by entering the show flash command at any level of the
CLI:
•The software release in the primary flash is displayed at the end of the line that begins with “Compressed
Pri Code Size”.
•The software release in the secondary flash is displayed at the end of the line that begins with
“Compressed Sec Code Size”.
Ensure that software release 07.6.01b is stored in the primary or secondary flash area.
5.Reboot the routing switch to load software release 07.6.01b from the area of flash memory (primary or
secondary) where you stored it.
6.Continue with “C. Upgrading Software on a Management Module From Release 07.6.01b or Greater” to
upgrade the software to release 07.8.04a.
C. Upgrading Software on a Management Module From Release 07.6.01b or
Greater
To upgrade the software on an M2, M4, or EP management module from release 07.6.01b or greater to release
07.8.04a:
1.Verify the version of boot code running on the management module by entering the show flash command.
The boot code version is displayed at the end of the line that begins with “Boot Image size”. Ensure that boot
code version 07.06.05 is displayed.
NOTE: The show flash command only displays the version of boot code installed on the device. It does not
display the version of boot code running on the device.
If you rebooted the routing switch after installing boot code 07.06.05 (as described in “A. Upgrading Boot
Code on a Management Module to Version 07.06.05”), the required boot code is running. If you are not sure,
ProCurve recommends that you reboot the device now.
2.Store software release 07.8.04a (filename: H2R07801d.bin) on a TFTP server that the routing switch can
access.
3.Upgrade the software on the management module to version 07.8.04a by entering the following command:
copy tftp flash <ip-address> H2R07801d.bin [primary | secondary]
Where:
primary copies software to the primary (default) storage area in flash memory.
secondary copies software to the secondary storage area.
If no redundant management module is installed, the message TFTP to Flash Done is displayed when the
upgrade is complete.
If a redundant management module is installed, the message Sync Secondary code in flash...Done
is displayed when the flash images are synchronized and the upgrade is complete.
4.Verify that the software has been successfully copied by entering the show flash command at any level of the
CLI:
•The software release in the primary flash is displayed at the end of the line that begins with “Compressed
Pri Code Size”.
•The software release in the secondary flash is displayed at the end of the line that begins with
“Compressed Sec Code Size”.
Ensure that software release 07.8.04a is stored in the primary or secondary flash area.
9
Using SNMP to Upgrade Software on a Management ModuleRelease Notes for 07.8.04
5.Reboot the routing switch to load software release 07.8.04a from the area of flash memory (primary or
secondary) where you stored it.
NOTE: When you reload the software after upgrading the software to release 07.8.04a, the routing switch
displays a message to say that the configuration has changed and prompts you to save the changes. This
message is displayed even if you do not make any configuration changes because the software records its
release number in the running-config file when the software is loaded onto the switch. Enter Y to reload
without saving the change or save the change and reload.
Using SNMP to Upgrade Software on a Management Module
Third-party SNMP management applications such as HP OpenView can upgrade software on a routing switch.
NOTE: In software releases earlier than 07.5.04, the SNMP agent does not check for type validity with the
SNMP version. In software release 07.5.04 and greater, the SNMP agent does not send a reply for a varbind, if the
type of the varbind is not a known type for that version of SNMP. For example, MIB objects of type Counter64
cannot be retrieved using a v1 packet, as Counter64 is a v2c and v3 type.
Make sure you use the correct procedure for your device and processor type. For example, do not use the
Management Processor procedure to upgrade the switching processors on a T-Flow module.
The syntax shown in this section assumes that you have installed HP OpenView in the “/usr” directory.
ProCurve recommends that you make a backup copy of the startup-config file before you upgrade the software. If
you need to run an older release, you will need to use the backup copy of the startup-config file.
Upgrading a Management Processor using SNMP
Use the following procedure to upgrade:
•An M2, M4, or EP module
•Management processor on the T-Flow module
To upgrade software code on the Management Processor:
1.Configure a read-write community string on the ProCurve device, if one is not already config ured. To
configure a read-write community string, enter the following command from the global CONFIG level of the
CLI:
snmp-server community <string>rw
where <string> is the community string and can be up to 32 characters long.
2.On the ProCurve device, enter the following command from the global CONFIG level of the CLI:
no snmp-server pw-check
This command disables password checking for SNMP set requests. If a third-party SNMP management
application does not add a password to the password field when it sends SNMP set requests to an ProCurve
device, by default the ProCurve device rejects the request.
3.From the command prompt in the UNIX shell, enter the following command:
Where:
<rw-community-string> is a read-write community string configured on the ProCurve device.
<hp-ip-addr> is the ProCurve device’s IP address.
Release Notes for 07.8.04Upgrading the FPGA on a 10 Gigabit Ethernet Module
<tftp-ip-addr> is the TFTP server’s IP address.
<file-name> is the image file name.
<command-integer> is one of the following values:
20 – Downloads the software code into the device’s primary flash area.
22 – Downloads the software code into the device’s secondary flash area.
Upgrading the FPGA on a 10 Gigabit Ethernet Module
This section explains how to upgrade an FPGA (Field-Programmable Gate Array) on a 10 Gigabit Ethernet
module. 10 Gigabit Ethernet modules do not have boot code separate from the management module. However,
they do have FPGAs that require separate software.
NOTE: The J8174A 2-port 10 Gigabit Ethernet module with XENPAK optics uses a different FPGA file than the
older J4891A 1-port 10 Gigabit Ethernet module. See Table 5 on page 6 for a list of the FPGA files supported on
both the 1-port and 2-port 10 Gigabit Ethernet modules.
The J8174A 2-port 10 Gigabit Ethernet module with XENPAK optics can function in the same chassis with the
older J4891A 1-port 10 Gigabit Ethernet module.
If an upgrade is required for any of the FPGA files, you must upgrade all the FPGA files.
To upgrade the FPGA on a 10 Gigabit Ethernet module:
1.Complete the upgrades of the boot code and software code, if required.
2.Enter the following command for the 10 Gigabit Ethernet module at the privileged EXEC level of the CLI:
10gig copy tftp flash <ip-addr> <filename> [module <slotnum>]
Where:
tftp specifies the location of the FPGA file. The tftp parameter shows that the file is on a TFTP server.
<ip-addr> specifies the IP address of the TFTP server, if you specify tftp.
<filename> specifies the FPGA file name. The 2-port 10 Gigabit Ethernet module has only two FPGA files;
xpp.bin and xtm.bin. For more information on the supported FPGA files, see Table 5 on page 6.
module <slotnum> is an optional parameter that specifies the modules on which you want to install the
upgrade. If you do not specify a slot number, the command upgrades the FPGA on all 10 Gigabit Ethernet
modules in the chassis.
NOTE: You can store and copy the FPGA files using any valid filename. You are not required to store and
copy the files using the names listed in “Boot Code Requirements for ProCurve Software” on page 5. The
device uses information within the files to install them in the correct FPGAs, and the show flash command
lists the FPGAs according to the names in “Boot Code Requirements for ProCurve Software” on page 5.
3.Reload the software by entering one of the following commands:
•reload (this command boots from the default boot source, which is the primary flash area by default)
•boot system flash primary | secondary
11
Using Different Combinations of Management ModulesRelease Notes for 07.8.04
NOTE: The show flash command will list the new FPGA code versions but the new versions do not take
effect until you reload the software.
Using Different Combinations of Management Modules
This section describes the different combinations of M1, M2, M4, EP, and T-Flow management modules supported
on ProCurve 9304M, ProCurve 9308M, and ProCurve 9315M routing switches.
Table 6: Supported Management Module Combinations
Primary Management Module Secondary Management
Module
J4885A EP Mini-GBIC Redundant
Management Module
Any M2 or M4 Redundant
Management Module (Discontinued)
NOTE: The following types of management modules are mutually exclusive:
- M1 management modules
- M2 or M4 redundant management modules
- EP redundant management modules
- T-Flow redundant management modules
A ProCurve routing switch does not operate if two redundant management modules of different types are installed.
Also, M1 management modules do not operate in a ProCurve 9315M routing switch.
Another EP Redundant
Management Module
Another M2 or M4
Redundant Management
Module
Another J4879A T-Flow
Redundant Management
Module
N/ASupported only in the ProCurve 9304M
Notes
—
When you use an M2 and M4 in the same
switch, ProCurve recommends using the
faster M4 as the primary redundant
management module. If the M4 fails, the
system will use the slower M2 module.
—
and ProCurve 9308M routing switches. No
redundant management options.
Redundant management means that a device can operate with two management modules installed; one active
(primary) and one standby (secondary). If the active management module becomes unavailable, the standby
management module automatically takes over system operation.
Management modules with redundant management capabilities include the follo wing M2, M4, EP, and T-Flow
modules:
•J4885A ProCurve 9300 EP Mini-GBIC Redundant Management Module (8-port)
If you are using a Redundant Management module, you can install either one or two such modules in the routing
switch, as shown in Table 6. For more information, see “U sing Redundant Management Modules” in the
Installation and Basic Configuration Guide included on the Documentation CD-ROM shipped with your
12
Release Notes for 07.8.04 Non-Redundant Management on ProCurve 9304M and ProCurve 9308M Routing Switches
management module, and also downloadable from the ProCurve website (see “To Download Product
Documentation:” on page 3).
Non-Redundant Management on ProCurve 9304M and ProCurve
9308M Routing Switches
Management modules without Redundant Management are sometimes termed “M1” modules (for “Management
1”). These modules, now discontinued, operate only in the ProCurve 9304M and ProCurve 9308M routing
switches. M1 modules include:
NOTE: M1 management modules do not operate in the ProCurve 9315M routing switch. Also, if you are using an
M1 management module in a ProCurve 9304M or ProCurve 9308M, no other management module (nonredundant or redundant) can be installed in the routing switch.
Maximum Size of Startup-Config and Running-Config Files
Each ProCurve device has a maximum supported size for the running-config and the startup-config file. If you use
TFTP to load additional information into a device’s running-config or startup-config file, it is possible to exceed the
maximum supported size. If this occurs, you will not be able to save the configuration changes.
Table 7 lists the maximum size of the running-config and the startup-config files on ProCurve devices.
Table 7: Maximum Sizes Supported for running-config and the startup-config Files
Device Maximum Size of running-config
and startup-config files
ProCurve 9315 using Management II or
higher
ProCurve 9304M or ProCurve 9308M
using Management II or higher
ProCurve 9304M or ProCurve 9308M
using Management I (discontinued)
ProCurve 6308M-SX or ProCurve
6208M-SX (discontinued)
NOTE: The maximum supported file size of each file is not the combined size of the running-config and startupconfig files. The running-config and startup-config files can each be the size listed in Table 7.
To determine the size of an ProCurve device’s running-config or startup-config file, copy the file to a TFTP server.
Then use the directory services on the server to list the size of the copied file. To copy the running-config or
startup-config file to a TFTP server, use one of the following commands.
256 kilobytes (KB)
256 KB
128 KB
64 KB
•To copy the running-config to a TFTP server:
copy running-config tftp <ip-addr> <filename>
•To copy the startup-config file to a TFTP server:
copy startup-config tftp <ip-addr> <filename>
13
Removing a Module from an Active DeviceRelease Notes for 07.8.04
Removing a Module from an Active Device
Before you remove a module from a routing switch in operation, first disable the module. Disabling the module
before removing it prevents a brief service interruption on other unmanaged modules. The brief interruption can be
caused by the device re-initializing other modules when you remove an enabled module.
NOTE: This section does not apply to the active or standby Redundant Management modules. The disable
module and enable module commands are not supported on management modules.
To disable a module, enter the following command at the Privileged EXEC level of the CLI:
disable module <slot-num>
Where <slot-num> specifies the slot number as follows:
•Slots in a 4-slot chassis are numbered 1 – 4, from top to bottom.
•Slots in an 8-slot chassis are numbered 1 – 8, from left to right.
•Slots in a 15-slot chassis are numbered 1 – 15, from left to right.
Example
ProCurve 9300# disable module 3
This command disables the module in slot 3.
NOTE: If you remove the module without first disabling it, the routing switch re-initializes the other modules in the
device, causing a brief interruption in service after which the device resumes normal operation.
You do not have to enable a module after inserting it in the chassis. The module is automatically enabled when
you insert the module into a running device or when you power on the device.
To replace a removed module with a different type of module, you must configure the slot for the new module. To
configure a slot for a module, use the module command at the global CONFIG level of the CLI.
After disabling a module, if you decide not to remove the module, re-enable the module using the following
command:
enable module <slot-num>
Example
The following command re-enables the module in slot 3:
ProCurve 9300# enable module 3
Configuring the ProCurve 9315M
When configuring a ProCurve 9315M 15-slot routing switch, take into account the guidelines and restrictions in
this section.
Minimum Software Release Supported
The ProCurve 9315M requires software release 07.5.04 or greater.
NOTE: On a ProCurve 9315M, software release 07.5.04 is the earliest release supported. If a management
module is running software earlier than release 07.5.04, you cannot upgrade the module i n a 9315M chassis.
Instead, you must upgrade it in a 9304M or 9308M chassis. For more information, see “Upgrading Software on an
M2, M4, or EP Management Module to Release 07.8.04a” on page 7.
14
Release Notes for 07.8.04Enhancements and Configuration Notes in 07.8.03
Inserting or Removing an EP Module on a ProCurve 9315M
NOTE: This section applies only to a ProCurve 9315M (15-slot chassis) with EP modules.
Do not insert or remove EP modules in a ProCurve 9315M until the device has fully booted. Generally, booting
takes around two minutes. You can determine whether the device has fully booted by looking at the management
console. Once the device boots, a command prompt or login prompt is displayed.
After the device has booted, allow time for the device to fully complete the removal or insertion before removing or
inserting another module. Generally, this takes about 30 seconds. After you remove or insert a module, the CLI
displays a message confirming completion of the change. Wait for this message before removing or inserting
another module.
Slot Locations for Redundant Management Modules
The 15 slots in the ProCurve 9315M are divided among 4 internal regions. Slots 1 – 4 belong to the same region;
slots 5 – 8 belong to the same region; slots 9 – 12 belong to the same region, and slots 13 – 15 belong to the
same region. If you are using redundant management modules, ProCurve recommends that you place both
management modules in slots belonging to the same region. For example, if you place one management mo dule
in slot 5, ProCurve recommends that you place the other management module in slot 6, 7, or 8.
MAC Addresses
The ProCurve 9315M makes use of locally administered MAC addresses. If your site already uses locally
administered MAC addresses of the vendor OUI, which is 00e052, there could be a MAC address conflict with one
of the ports on the ProCurve device.
Server Trunk Groups
If you plan to configure ports on a module into a server trunk group, use the following guideline:
•For a multi-slot trunk group (one configured on two forwarding modules), the modules must both be in the
same set of slots (slots 1 – 7 or 9 – 15).
You do not need to follow this guideline for a switch trunk group.
NOTE: In software releases earlier than 07.6.00, the management module(s) and the module that had the server
trunk group’s ports were required to be in the same set of slots (slots 1 – 7 or 9 – 15). In software release 07.6.00
and later, there is no longer a restriction on the location of the management module relative to the module used for
server trunking. However, it is still a requirement that the module that has the server trunk group’s lead ports
cannot reside in slot 8.
VLANs
In release 07.6.01b, you could configure only up to 2195 Layer 2 VLANs on the ProCurve 9315M routing switch.
The system-max vlan <num> command allowed you to allocate a higher number of VLANs, but the software
allowed you to actually create only 2195 of the allocated VLANs.
Starting with release 07.6.04, this restriction has been removed. You can create the full number of allocated Layer
2 VLANs on the 15-slot ProCurve 9315M routing switch, up to 4095.
Enhancements and Configuration Notes in 07.8.03
On ProCurve 9300M Series routing switches, no new software enhancements are supported in software release
07.8.03.
15
Software FixesRelease Notes for 07.8.04
Software Fixes
The fixes for software bugs found on ProCurve 9300M Series routing switches in software releases 07.8.00h
through 07.8.03 are described in the following table. Software fixes are listed by bug ID for the software release in
which they were implem e nted.
Bug IDBug DescriptionProtocol/
Feature
07.8.00h
25991In the display of InUcastPkts and OutUcastPkt 64-
bit packet counters, the packet counts wrap after 32
bits.
31045The default route learned through OSPF is not
displayed in the routing table if you enter the clear ip route 0.0.0.0/0.0.0 .0 command.
32896802.1w packets are not forwarded by the routing
switch.
35710If you enter the no web management command,
access on port 80 is disabled while access on port
280 is allowed.
35727During a system reload, the following error
message is displayed even when the number of
Spanning Tree Protocol (STP) instances is reduced
by using topology groups:
Error - failed to bind STP to vlan xxx
3676After you modify an access control list (ACL),
protection against a reload is performed.
Other07.8.00
OSPF07.8.00
Spanning Tree07.8.00
Web
Management
Spanning Tree07.8.00
ACL07.8.00
Version
Found
Version
Fixed
07.8.00
40829 A Border Gateway Protocol (BGP) reload is
performed when the preceding NLRI entry is NULL.
41630When private VLANs are configured, if you remove
the lowest numbered port mapping in the primary
VLAN, higher port mappings are disabled.
44374An error message is displayed when you configure
multiple IP address on a group router interface.
44949ARP learning is performed much slower when
Layer 3 bidirectional traffic is transmitted at a 100M
rate.
45104A watchdog reset is caused when BGP passes out
of the Direct Memory Access (DMA) range.
45198 Port 280 remains up if you enter the no web-
management http command followed by the no
web-management hp-top-tools command.
45277A system reload is performed following a link-list
subroutine error.
16
BGP07.8.00
VLAN07.8.00
Other07.8.00
Other07.8.00
BGP07.8.00
Web
Management
Other07.8.00
07.8.00
Release Notes for 07.8.04Software Fixes
Bug IDBug DescriptionProtocol/
Feature
45318After you disable and swap a module, the active
management module crashes.
45319When you enter the ip rebind-acl all command, the
following message is logged:
Exceed max DMA 9 L4 cam resource,
using flow based ACL instead
45415SSH may reload if a different client public-key is
received for authentication.
45550A 10 Gigabit Ethernet port is not displayed in show
fdp interface command output.
46777The globally configured value for the sFlow
sampling rate is not applied to the secondary trunk
links when you enter the config-trunk-ind
command in the startup configuration.
46924The sflow sample command entered at the trunk
level is not supported on a routing switch during a
reload.
47464A variable is not initialized to zero. As a result, a
large data chunk may be allocated, causing a
system reload.
System07.8.00
ACL07.8.00
SSH07.8.00
CLI07.8.00
sFlow07.8.00
sFlow07.8.00
System07.8.00
Version
Found
Version
Fixed
47599If route-only mode is configured, forwarding stops
when you exit from monitor mode.
47855The OSPF timer displays the following message:
Warning Checksum bad in Link State
Database error.
48115The debug ip igmp ph ysical_port command is not
performed on ports 32 to 48 on an EP 48-Port 10/
1000-TX RJ45 module.
48132When a trunk server is used, the first packet in a
flow is sent twice.
48313A Protocol Independent Multicast (PIM) reload is
performed after detecting a virtual port (instead of a
physical port) configured in the forwarding OIF.
48383ACL-denied packets are not copied to a redirected
interface.
48442The BGP route dampening feature does not always
dampen flapping routes after four flaps. Some
routes are still dampened after two flaps.
48721The routing switch reloads if an SSH client starts a
session when SSH debugging is enabled.
48823If you configure multiple addresses on an interface
and reload the switch, RIPv2 advertises from only
the lowest IP address.
System07.8.00
OSPF07.8.00
IGMP07.8.00
System07.8.00
PIM07.8.00
ACL07.8.00
BGP07.8.00
SSH07.8.00
RIPv207.8.00
17
Loading...
+ 46 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.