	ProLiant BL p-Class GbE2 Interconnect Switch Firmware		
		Customer-Level Release Notes
			Version 3.2.0
			  2/21/2007

A. Description -

	This version of ProLiant BL p-Class GbE2 Interconnect Switch Firmware
	contains several enhancements and fixes.


B. Upgrade Requirement -

	Not-Critical.


C. New Features -
	
	1) Updated Daylight Savings Time (DST) behavior to comply with the 
	U.S. Energy Policy Act of 2005.

	2) Disabling STP when the cross-connect ports are enabled or enabling
	the cross-connect ports when STP is disabled results in a cautionary 
	message.

	3) Hot Links are defined as a pair of layer 2 interfaces consisting of 
	either an individual port or a trunk.  Typically, one interface is 
	configured as a backup interface to the master interface.  This feature
	offers basic link redundancy for topologies that require STP to be off.
	Basic operation assumes that the master interface is set to the active 
	state and forwards traffic while the backup interface is set to the 
	standby state, blocking traffic until the master interface fails.  Only
	one interface can be in the active state at any given time.  If the 
	master interface fails, control will switch to the backup interface to 
	start forwarding traffic.  If the master interface is restored, it will
	transition to the standby state where it waits and blocks traffic until
	the backup interface relinquishes control due to a failure.  STP is 
	disabled on all Hot Links interfaces.

	4) A watchdog timer has been implemented which will reboot the switch
	should it become unresponsive.

	5) The DHCP relay agent information option (82) has been implemented.


D. Problems Fixed -

	1) Switch no longer resets port auto-negotiation to on after save and 
	reset.

	2) Auto-MDI now works on ports 19-22 for forced speed and duplex mode.


E. Known Problems -

	1) The SAN cube option number displayed in both the CLI and BBI is 
	"321745- 21" but should be "321745-B21".

	2) Under some circumstances the "/i/l2/igmp/dump" CLI command may
	include ports that are no longer valid.  A port that has been blocked
	by STP will no longer transmit/receive the igmp packets and will
	eventually time out and be dropped from the group.

	3) Contrary to the CLI, when the user assigns an address for IP
	interface 1 through the BBI, BOOTP is automatically disabled.

	4) The commands IF and IFCLEAR under /stat should be under "port"
	according to RFC 1573.  This change has been incorporated into the CLI
	but is not yet incorporated into the BBI and SNMP.

	5) For a port that belongs to multiple VLANs, a configuration change 
	from tagged to non-tagged results in the port remaining only in the
	VLAN specified in the PVID rather than remaining only in the default
	VLAN as reported.  If the port needs to belong to the default VLAN, 
	make sure PVID is 1 before changing the port tagged field.

	6) If the switch is configured for UFD and RSTP mode with the LtM port 
	down, it is possible for one of the LtD ports to be marked as link UP 
	after a reboot even as the LtM is marked link DOWN.  Use the log 
	messages to find two consecutive messages to determine that port x is 
	the port still showing link UP status with /i/ufd.  For example:
		Jun  8 15:32:19 NOTICE  system: link up on port x
		Jun  8 15:32:19 WARNING ufd: Link to monitor is down
	In order to force the port link status to the proper state of disabled,
	use the "/cfg/ufd off" command (and "apply") to see all the LtD ports' 
	link state return to UP.  Then use the command "revert apply" so that 
	ufd is re-enabled resulting in all the LtD ports returning to a link 
	state of disabled.

	7) If a port has been configured as one of the LtD ports and the LtM 
	port is down, any configuration change of the port's 
	speed/mode/autonegotiation/flowcontrol will causes a port link 
	transition resulting in the port being marked as link UP even as the 
	LtM is marked link DOWN.  Use the /oper/port x/disable command to force
	the link back to disabled to be consistent with an LtM state of down.

	8) Statistics for Broadcast and Multicast Jumbo frames are not reported 
	correctly. Jumbo frames statistics are displayed under 
	"dot3StatsFrameTooLongs" instead of displaying as valid Ethernet frames.

	9) When Uplink Fast is enabled, it increases the bridge priority to 
	65500 for all Spanning Tree instances and path cost by 3000 for all 
	external Spanning Tree ports.  When you disable Uplink Fast and 
	enable RSTP (Rapid Spanning Tree) followed by the disable operation, 
	the default spanning tree bridge priority and path cost are not 
	restored.  Manually reconfigure the bridge priority and path cost to 
	default value or a newly desired value.

	10) Performing a revert apply after making MSTP configuration changes 
	may result in error messages ("bcm_stg") being displayed.  These debug 
	messages may be ignored.

	11) If the LTM is associated with multiple Spanning Tree Groups (STG),
	and one of the STGs goes to blocking mode, the LTD ports will be 
	marked down even though the traffic on the other STGs might still be 
	forwarding.

	12) The preferred management interface is the Command Line Interface 
	(CLI), since the browser (BBI) and SNMP interfaces do not provide
	full functionality.

	13) While initially configuring the first ACL via SNMP, some SNMP 
	managers query ACL variables in a way that may cause the switch CPU 
	utilization to spike for a few seconds. If the manager continuously 
	queries the variables, the switch may become unresponsive.  To avoid 
	this, initial ACL configuration should be done via the CLI.


F. Notes -

	1) How BOOTP works:

		1. BOOTP is enabled by default. It is expected that user will 
		configure their BOOTP/DHCP server to issue both IP interface
		and gateway address upon request.

		2. BOOTP assigned addresses will override IP interface 1 and 
		gateway 1. 

		3. BOOTP assigned addresses will not be saved to the
		configuration dump. 

		4. If user manually configures an IP interface 1 or gateway 1
		through CLI, BOOTP will NOT be automatically disabled; but the
		BOOTP process will also be re-initiated when the apply is done.
		Note that if BOOTP addresses become available, #2 and #3 above
		will still apply; otherwise, the configuration will be updated
		with the user assigned addresses as they become active.

		5. BOOTP assigned addresses will be automatically applied while
		user assigned addresses will need to be applied.
 
		6. BOOTP can be disabled manually. Any manually configured IP 
		interface and gateway addresses will be saved to the
		configuration.

		NOTES: 
		------
		- When BOOTP addresses are assigned, if BOOTP is then disabled,
		the current assigned addresses are still active 

		- When going from BOOTP enabled/dynamic address assigned, to
		BOOTP disabled/static addresses assigned, then doing a revert
		apply takes configuration back to BOOTP enabled but the
		addresses must be reassigned by the BOOTP server.

		- If BOOTP is enabled, user assigned addresses get saved only
		if they haven't been overwritten by a dynamic BOOTP address yet
		(see #4 above) 

		- User assigned addresses cannot be the same as BOOTP assigned 
		addresses.


----------------------------------------------------------------------------

Usage information can be obtained from the following documentation:

    HP ProLiant BL p-Class GbE2 Interconnect Switch User Guide
    HP ProLiant BL p-Class GbE2 Interconnect Switch Application Guide
    HP ProLiant BL p-Class GbE2 Interconnect Switch Command Reference Guide
    HP ProLiant BL p-Class GbE2 Interconnect Switch Browser-based Interface
	Reference Guide 

This documentation is downloadable from http://www.hp.com/support

----------------------------------------------------------------------------

Hewlett-Packard Company shall not be liable for technical or editorial errors
or omissions contained herein. The information in this document is provided 
"as is" without warranty of any kind and is subject to change without notice.
The warranties for HP products are set forth in the express limited warranty 
statements accompanying such products. Nothing herein should be construed as 
constituting an additional warranty.

(c) 2002-2007 Hewlett-Packard Development Company, L.P.
