                       HP 10Gb Ethernet BL-c Switch
                       Customer-Level Release Notes
                              Version 1.1.0
                                9/14/2007

A. Description -

	HP 10Gb Ethernet BL-c Switch firmware.  This firmware should be 
	used with the same version boot image.


B. Upgrade Requirement -

	Not-Critical.


C. Supported Hardware:

        HP 10Gb Ethernet BL-c Switch


D. New Features -

	1) DHCP is supported on the management interface.

	2) Added option to select image on bootup.

	3) Verbose 0 now supported in the CLI.


E. Problems Fixed -

	1) The ISCLI interface no longer allows setting a trunk member as a 
	monitor port.

	2) These SNMP traps are now implemented:
		bntSFPInserted
		bntSFPRemoved
		bntSwTempExceedThreshold
		bntSwTempReturnThreshold

	3) SNMP traps can now be sent via the management port.

	4) Port mirroring is allowed when mirrored port is in a different STG 
	than the monitor port.

	5) Switch no longer reboots if tab is entered after the port PVID 
	command.

	6) Multicast traffic is no longer blocked when mrouter learned on 
	same port is cleared.

	7) The correct pathcost for 10Gb ports is set when changing between 
	MSTP/RSTP/STP modes.

	8) A reboot is no longer required when the hostname is updated in the 
	OA via SNMP.

	9) In LACP mode, changes to root bridge no longer causes LTM port to 
	go into discarding mode although the LTD port is not disabled.

	10) The maximum length defined in the SNMP MIB for RADIUS and TACACS+
	secrets is now 32 characters.


F. Known Problems -

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

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

	3) With NTP enabled, the rollover 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.

	4) An illegal XFP insertion will cause the uplink port to be disabled.
	Subsequent use of a valid XFP will not automatically get link until
	the user enables the appropriate uplink port.

	5) When running HTTP rather than HTTPS, it is possible that the 
	browser timeout can be circumvented if the browser is not killed after 
	the browser timeout.

	6) Switch does not generate an SNMP trap or syslog event when switch 
	reaches or exceeds temperature thresholds.  The OA monitors the 
	switch temperature and takes corrective actions, including generating 
	log messages, increasing fan speed, or powering the switch off when 
	the switch passes temperature thresholds

	7) The switch Health UID does not transition from off to amber when the
	switch is powered off and the OA detects mismatches in the enclosure 
	corresponding to the switch and the mezzanine cards.  Health status is
	displayed properly by the OA when the switch is powered off.


G. Notes -

	1) Ports 1-16 (downlink) 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 blade mezzanine slots 2 or 3 are populated by the NC512m mezzanine 
	card, then downlink ports 1-16 will have a match for 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.

	2) The management port (17) is interface 250 and STP 32 and is disabled 
	by default in this release. In order to use this port, interface 250 
	and gateway 254 must be configured for static addresses. Also, 
	interfaces 1 and interface 250 cannot be in the same subnet since data 
	and management ports cannot be on the same network.

	3) The NC512m mezzanine card is supported in slot 2 or 3 (not both).

	4) 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 10Gb Ethernet BL-c Switch User Guide
    HP 10Gb Ethernet BL-c Switch Application Guide
    HP 10Gb Ethernet BL-c Switch Command Reference Guide
    HP 10Gb Ethernet BL-c Switch Browser-based Interface Reference Guide
    HP 10Gb Ethernet BL-c Switch ISCLI 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.
