         HP GbE2c Ethernet Blade Switch for c-Class BladeSystem Firmware
                       Customer-Level Release Notes
                              Version 1.1.0
                                8/30/2006

A. Description -

	HP GbE2c Ethernet Blade Switch for c-Class BladeSystem firmware.


B. Upgrade Requirement -

	Not-Critical.


C. New Features -

	1) Port 19 is now available as a dedicated management interface to the 
	Onboard Administrator (OA).  The port has a permanent setup as a member
	of VLAN 4095, STG 32, and interface 256 and, therefore, cannot be 
	changed.  By default this port is enabled for DHCP.

	2) Support for up to 1000 VLANs and 32 STGs, as compared to 256 VLANs 
	and 16 STGs in the 1.0.0 release.

	3) A user selectable CLI provides a choice between the standard CLI 
	and an industry-standard CLI (IS-CLI).  All commands that are available
	in the CLI are available in the IS-CLI.

	4) Configuration reminders have been added for the following features:

		IP interface
		VLAN
		STP
		Trunking
	
	5) The following mapping exists between TACACS+ privilege levels and 
	switch management access levels:

		TACACS+ priv-lvl = switch management access level
		-----------------------------------------------
		0                = CLI_AUTH_USER
		3                = CLI_AUTH_OPER
		6                = CLI_AUTH_ADMIN

	All other values of priv-lvl are considered as "access deny". 
 
	priv-lvl 15 is mapped to CLI_AUTH_ADMIN and priv-lvl 1 is mapped to 
	CLI_AUTH_USER for ease of configuration.



D. Problems Fixed -

	1) Performing a "revert apply" CLI command no longer causes ports 17 
	and 18 (the cross-connects) to be marked down.

	2) The correct SNMP traps are listed in the bt4trap.mib MIB,
	including: 

		bt4SwTempExceedThreshold
		bt4SwTempReturnThreshold

	3) All SNMP traps are sent with the GbE2c bt4SwTrapDisplayString.

	4) Once the "verbose 0" CLI command is issued, command prompts
	appear.


E. Known Problems -

	1) When both BOOTP and DHCP are enabled, and DHCP receives an offer 
	with gateway information first, then BOOTP cannot receive its offer or
	will receive it after considerable delay.  The workaround is to 
	disable/enable BOOTP to cause a new BOOTP offer.


F. Notes -

	1) If you are upgrading from a GbE2 p-Class environment, note that 
	the switch cross-connect ports now are disabled by default in the 
	c-Class environment.  Cross-connect ports were enabled by default 
	for p-Class.

	2) Ports 1-18 (downlink and XConnect ports) support the e-Keying 
	mechanism.  The e-Keying feature allows the OnBoard Administration (OA)
	to communicate with the switch, via the I2C interface, as to whether 
	or not there is a port type mismatch.  Depending on that mismatch 
	information, the switch will enable/disable that specific port.  If 
	the port (1-18) is attached to an Ethernet device, depending on what 
	is plugged in to the enclosure, then it is a match so the switch will 
	enable the port.  Otherwise the switch will disable the port to protect
	the port from damage.  The switch will also display the log message 
	"disabled because of a mismatch".  For more details on e-Keying refer 
	to c-Class enclosure documents.

	3) 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 GbE2c Ethernet Blade Switch for c-Class BladeSystem User Guide
    HP GbE2c Ethernet Blade Switch for c-Class BladeSystem Application Guide
    HP GbE2c Ethernet Blade Switch for c-Class BladeSystem Command Reference
    HP GbE2c Ethernet Blade Switch for c-Class BladeSystem 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-2006 Hewlett-Packard Development Company, L.P.
