	ProLiant BL p-Class GbE2 Interconnect Switch Firmware		
		Customer-Level Release Notes
			Version 2.2.0
			  6/8/2005

A. Description -

	This version of ProLiant BL p-Class GbE2 Interconnect Switch Firmware
	contains changes made to the previous firmware version.

B. Upgrade Requirement -

	Not-Critical

C. New Features -
	
	Uplink Failure Detection (UFD)

D. Problems Fixed -

	Several minor fixes and enhancements are in this version.

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/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.

		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. 

	4) The switch appears to hang when a port is removed from a large number
	of VLANs (e.g., "/cfg/port tag dis"), but will eventually return.  Since
	some functions, such as STP, may fail and require a reboot if
	CPU-starved too long, it is not advised to perform this action on a port
	belonging to more than approximately 40 VLANs.

	5) IGMP empty groups may not be updated when making VLAN changes on
	server/data source ports.  When making VLAN changes to the data server
	ports for multicast (L3MC) traffic, flush the IGMP table after such a
	change so that the IGMP table can be updated with the correct VLAN.  The
	IGMP table can be flushed via the CLI command "/maint/igmp/clear".

	6) 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.

	7) 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.

	8) 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.

	9) 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.

	10) In a configured trunk group, load distribution for 
	Multicast/Broadcast traffic is determined by the firmware choosing to 
	use the first port in the trunk group that comes up rather than using 
	the lowest port in the trunk algorithm.  (276394)

	11) When the switch is configured for MST (multiple spanning tree), the 
	/info/stp command does not display current information.  Some 
	information is available by using /cfg/mrst/cur instead. 

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

Caution:  Do not use the Browser-based Interface (BBI) to upgrade version 
	1.0.0 or 1.0.1 Firmware, since it may cause the switch to panic.
	Use the CLI, serial interface, or the Upgrade Tool.  The BBI may
	be used to upgrade version 1.1.0 and later firmware.

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

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-2005 Hewlett-Packard Development Company, L.P.
