	ProLiant BL p-Class GbE2 Interconnect Switch Firmware		
		Customer-Level Release Notes
			Version 2.0.0
			  1/14/2005

A. Description -

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

B. Upgrade Requirement -

	Not-Critical

C. New Features -
	
	TACACS+
	MSTP/RSTP
	IGMP Snooping

D. Problems Fixed -

	1)  Insertion of a SAN module during switch operation is now 
	supported.

	2) The port cost range prompt for the CLI command, 
	"/cfg/stp 1/port 24/cost" now correctly includes 0.

	3) Typing CTRL-\ no longer causes the switch to panic.

	4) The CLI command, "/b/ptimg boot" now succeeds.

	5) This warning message is no longer displayed when a downgrade is
	not being attempted:

		WARNING: Factory reset and software downgrade detected.

E. Known Problems -

	1) The MAC addresses in the SNMP dot1dTPFdbTable are given an 
	"other" status (status 1) in dot1dTpFdbStatus. This value should 
	properly be set to "learned" (status 3) for dynamically learned 
	addresses, or "mgmt" (status 5) for static MAC address mappings.

	2) The CLI commands, "/info/link" and "/info/trunk" may show 
	conflicting information when these commands are performed on a port
	in a trunk:

		/oper/port # disable
		/cfg/port # disable
		apply
		/oper/port # enable

	/info/link will report the port as UP while /info/trunk will report 
	the port as DOWN.  The conflict may be resolved via:

		/cfg/port # enable
		apply

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

	4) The "/i/igmp/dump" CLI command shows an invalid state for 
	some ports.

	5) STP port costs in the "/i/stp" CLI command do not revert after a 
	"revert apply" command.  To work around this problem, explicitly 
	set the port cost back to its original value.

	6) BBI login fails using TACACS+, even with server approval.

	7) The default /cfg/igmp/snoop/mrto timeout is 255, but the User 
	Guide, Appendix D-6, and the Command Reference, p6-35, say 60.

	8) For broadcast/multicast/unknown traffic, the STP port of a trunk 
	group is used. This behavior is dynamic and depends on which port 
	comes up first, and is Usually the lowest numbered port.  If that
	port goes down, another port is selected and stays active even if
	the originally selected port comes back up later.  This behavior
	is by design, but is not described correctly in the Application
	Guide, page 2-4.

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

	10) The BBI STP Groups Dashboard "or" search option does not show 
	all STP groups.

	11) Port mirroring/monitoring must be among ports serviced by the
	same chipset within the switch.  The two port groups are:

		1-6, 8, 18-22
		7, 9-17, 23

	12) The User Guide incorrectly states that the Putty terminal
	emulator is not supported.

	13) The TACACS+ Priv 3/Oper level allows the maint option, which 
	allows for panic/reset.  Oper level should not have this ability.

	14) Dynamic port cost allocation (setting port cost to zero)
	is supported in STP mode, but is not supported in MSTP/RSTP mode.

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

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