GbE2c and GbE2c Layer 2/3 Ethernet Blade Switch for HP c-Class BladeSystem
                       Customer-Level Release Notes
                              Version 2.0.0
                                1/8/2007

A. Description -

	GbE2c and GbE2c Layer 2/3 firmware.  This firmware should be used with
	the same version boot image.


B. Upgrade Requirement -

	Not-Critical.


C. Supported Hardware:
        GbE2c Ethernet Blade Switch
        GbE2c Layer 2/3 Ethernet Blade Switch


D. New Features -

	1) Support for Layer 2/3 hardware, with dual mode ports supporting 
	1Gb RJ45 and Fiber SFP ports.

	2) Support for Layer 3 on the Layer 2/3 GbE2c.


E. Problems Fixed -

	None.


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

	2) An ACL filter configured to filter on MPLS packets with additional
	L3 header fields set will not filter the traffic.  An ACL filter 
	configured to filter only on MPLS packets will correctly apply the 
	action (deny or allow) to any matching traffic.  If the ACL filter is 
	configured to filter on IPv4 or TCP/UDP header in addition to MPLS, 
	then the filter will not filter out any matching traffic.  For example,
	if the filter action is set to deny traffic, the packets will not be 
	dropped.  There is no workaround for this issue. The hardware used for
	ACL does not allow MPLS packets to be further inspected for L3 headers.

	3) When an ACL configured to re-mark In-profile packets is matched, 
	the switch will correctly re-mark with the 802.1p value.  But, it will 
	also re-mark any Out-Profile packets received on that port using the 
	same 802.1p value.  This problem will also occur if the re-marking is 
	configured to update the 802.1p value using the TOS precedence field.
	The switch chip does not distinguish between In-Profile and Out-Profile
	packets when re-marking.  There is no workaround for this issue.

	4) Some switch types may not be able to link to the fiber ports unless
	auto-negotiation is enabled on that switch.

	5) When the virtual reset button is clicked in the Onboard 
	Administrator, GbE2c Ethernet Blade Switches will go into an endless 
	loop.  Virtual reset works fine for GbE2c Layer 2/3 Blade Switches.  
	To work around this problem, log into the switch console and type 
	CTRL-SHIFT-^.  Then, instead of the virtual reset button, use the 
	virtual "Power off" and "Power on" buttons.

	6) The OA GUI displays the firmware and boot images as "GbE2c" for 
	both GbE2c and GbE2c Layer 2/3 switches.
 
	7) With NTP enabled, the roll over for Daylight Savings Time does not 
	occur on the correct Fall date.  With the new OLDDST command menu and 
	the pre07DST either enabled or disabled, the DST rolls forward for 
	Spring, but does not roll back for Fall.

	8) Attempting to upgrade version 1.0.0 firmware directly to 2.0.0
	will fail with a CLI error message saying the image file is too big
	to FLASH.  The workaround is to upgrade to firmware version 1.1.0
	first, and then upgrade to 2.0.0.  This does not affect the boot image
	upgrade.
 

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