SOFTPACK NUMBER: SP32432 PART NUMBER: FILE NAME: SP32432.tgz TITLE: ProLiant BL p-Class GbE2 Interconnect Switch Firmware Upgrade for Linux VERSION: 3.0.1 LANGUAGE: English (US) CATEGORY: Firmware - Blade Infrastructure DIVISIONS: Server PRODUCTS AFFECTED: ProLiant BL20p All Models ProLiant BL25p All Models ProLiant BL30p All Models ProLiant BL35p All Models ProLiant BL40p All Models ProLiant BL45p All Models ProLiant BL p-Class GbE2 Interconnect Switch OPERATING SYSTEM: All HP-supported Linux versions (32 bit x86) SYSTEM CONFIGURATION: N/A PREREQUISITES: EFFECTIVE DATE: 5/15/2006 ELECTRONIC DISTRIBUTION ALLOWED: Yes SOFTPACK UTILITY VERSION: SUPERSEDES: SP31452 DESCRIPTION: This SoftPaq contains the ProLiant BL p-Class GbE2 Interconnect Switch firmware image and Readme files. It should be used with the same version ProLiant BL p-Class GbE2 Interconnnect Switch boot image to ensure correct operation and behavior. ------------------------------------------------------------------------ Enhancements: ------------------------------------------------------------------------ 1) Layer 3 Features IP Forwarding 128 IP interfaces 4096 ARP entries Global default route Static routing support with 128 routing table entries Dynamic routing support with entries in routing table (4K entries) Routing protocol RIP v1 RIP v2 OSPF 2) Layer 2 Enhancements Manual entry of MAC address in forwarding table Broadcast, Multicast, and DA Unknown Storm Suppression QoS 802.1p Metering – policing or shaping Commit rate Packet marking Queuing Fast Uplink Convergence Port Fast-Forwarding LACP (IEEE 802.3-2002) Configurable Trunk Hash algorithm 3) Management Enhancements Upgrade Firmware via FTP client Secondary NTP Support 4) Security Enhancements PortX Security based 802.1x ACL Filtering (SMAC, DMAC, SIP, DIP, Sport, Dport) SSH v2 SNMP v3 HTTPS Secure BBI 5) High Availability Enhancements Router Redundancy via VRRP 6) The command menu structure in the CLI (Command Line Interface) has changed in 3.0.1. For example, the /cfg/stp command has been moved to /cfg/l2/stp and /info/log has been moved to /info/sys/log. Please see the Command Reference for an overview of the new command layout. Most commands can be entered into the CLI interactively using the old syntax, they will be accepted and translated into the new syntax. The translated syntax will be seen when the configuration is output to a file (/cfg/ptcfg) or dumped to the screen (/cfg/dump). Configuration files are upwardly compatible from 2.x to 3.0.1, but 3.0.1 configuration files are not supported with previous versions of the firmware. When upgrading to 3.0.1, please archive your current configuration first. Then, when the new 3.0.1 firmware is installed, the configuration will be automatically translated into the new syntax. When downgrading from 3.0.1 firmware to previous versions of the firmware, you must reset the configuration to factory defaults before the firmware downgrade operation. 7) MSTP differences between the 2.2.x, 3.0.0, and 3.0.1 releases: 2.2.x: Any vlan can be moved to CIST. VLAN1 can not be moved from CIST. Default action when switching to MSTP: vlan 1 moved to CIST. Default region revision: 1 3.0.0: No VLAN allowed to CIST. VLAN1 can be moved to any STG. Default action when switching to MSTP: no action performed. Default region revision: 0 3.0.1: Any VLAN can be moved to CIST. VLAN1 can be moved to any STG. Default action when switching to MSTP: vlan 1 moved to CIST. Default region revision: 1 Although in 2.2.x you can move VLANs to CIST there are a lot of issues generated by this movement. 3.0.1 solves these issues. The only high level difference between 2.2.x and 3.0.1 is that VLAN1 can be moved to any STG and isn't stuck in CIST as in 2.2.x. Please note that in the 2.0 Application Guide it is written that when you turn on MSTP, the switch automatically moves all VLANs from STG 1 to CIST, which is not true. Only Vlan 1 is moved to CIST. ------------------------------------------------------------------------ Fixed Issues: 1) The switch appeared to hang when a port was removed from a large number of VLANs (e.g., "/cfg/port tag dis"), but eventually returned. 2) Switching between active/backup config block images and the factory config block no longer causes the active/backup config block image to be lost. ---------------------------------------------------------------------------- HOW TO USE: Download the SoftPaq to a directory on your target computer. The SoftPaq is a .tgz file with a file name based on the SoftPaq Number. Run this command to extract the files from the .tgz file: tar -zxvf *.tgz Place the firmware image file (*.bin) on a TFTP server that is network-accessible from the switch you wish to update. Use the switch's command line interface (CLI) to update the firmware. Alternately, the switch's serial console may be used to update the firmware. See the switch's User Guide for detailed instructions. Refer to the Softpaq README file for installation instructions and firmware information. (C) Copyright 2006 Hewlett-Packard Development Group, L.P. Product names mentioned herein may be trademarks and/or registered trademarks of their respective companies