Cisco Gigabit Ethernet Switch Module (CGESM) for HP BladeSystem p-Class
 
Management Utilities
==============================================================================

Overview
--------

Windows installation folder:
	%SystemDrive%\Program Files\ProLiant\Interconnect Switch\
		tools\CGESM Utilities\Version 12.2(25)SEE2

	(%SystemDrive% is usually C:)

Linux installation folder:
	/usr/local/ProLiant/Interconnect_Switch/Utilities/
		CGESM/version12.2.25.SEE2



The Interconnect Switch Utilities package is comprised of the following items:

	Switch SNMP MIBs.  The SNMP MIBs and description file are included 
	in the "mibs" folder.

	Switch firmware information tool, "swfwinfo".

	Switch port to blade server NIC (network interface card) name 
	mapping tool, "hpecm".  (Windows)

	TFTP server (Windows).  See the TFTP discussion below if you use the 
	RDP PXE TFTP server.  The TFTP server is in the "tftpserver" folder.

	Integration of the switch into the Systems Insight Manager (HP-SIM)
	server.

	Windows Start Menu items.  See: 
		Start->Programs->ProLiant Interconnect Switch

See the discussion below for more information on these features.


New features
------------
hpecm supports more servers and Linux versions.


Known problems
---------------
None.


Supported OS List
-----------------

This package is supported on:

	Microsoft(R) Windows(R):
		Windows 2000
		Windows Server (TM) 2003

	Linux:
		Red Hat Enterprise Linux 3, 4 (x86)
		SuSE Linux Enterprise Server 8, 9/OES (x86)
	

Support Web page
----------------

	The switch may be kept up-to-date with the latest firmware which
	is available at http://www.hp.com/support  


==============================================================================

Integration of the switch into HP-SIM
-------------------------------------

	To compile the SNMP MIBs into the Systems Insight Manager to enable 
	it to discover and manage the switch, run "CGESM_to_SIM" after 
	the Utilities package is installed on the SIM server.  
	The Insight Manager service will be restarted by the command. 


==============================================================================

Switch firmware information tool, "swfwinfo"
--------------------------------------------

NAME
	swfwinfo - Display information about a Proliant BL Interconnect Switch
	firmware file

SYNOPSIS

	Windows: swfwinfo [drive:][path]filename 

	Linux: swfwinfo filename

DESCRIPTION

	Swfwinfo probes a firmware file and prints information about the
	firmware file to STDOUT.  If the filename provided is a valid and 
	readable Interconnect Switch firmware file, the printed information 
	includes the filename, version, build date, manufacturer, and
	firmware type.  

	Upon successful completion, swfwinfo exits with an exit code of 0.  If 
	an error was encountered during processing, a short description of the
	error is output to STDERR and swfwinfo exits with the appropriate 
	error code.

OPTIONS

	None

ERROR CODES

	0	Normal.  Valid data is returned.
	1	Incorrect command syntax was provided. A Usage Error message 
		is printed on STDERR.
	2	The switch firmware file could not be found or read.  
	3	The checksum is invalid.
	4	The file signature is invalid.
	5	Unknown product ID.

	There is a precedence for printing and returning error codes when 
	multiple errors are found involving the checksum, signature, or 
	product ID of a firmware file.  Only one of the errors is printed, in 
	this precedence order:
  
		checksum error
		signature error
		product ID error


==============================================================================

Switch port to NIC enumeration mapping tool, "hpecm"
----------------------------------------------------

NAME
	hpecm - HP Ethernet Connectivity Mapper

	Display the mapping between ProLiant BL blade server NIC names 
	(as chosen by the OS) and interconnect switch or patch panel ports, 
	and provide enclosure configuration validation.

SYNOPSIS

	WIN32: hpecm 

DESCRIPTION

	hpecm is a graphical tool which collects information about the 
	contents of a ProLiant BL blade enclosure, including enclosure type, 
	blade type, and blade operating system (OS).  It then displays the 
	mapping between the switch or patch panel ports and the OS 
	enumeration (naming order) of the blade network interface controller 
	(NIC) ports.  Configuration validation is performed as items are 
	selected, so hpecm may also be used as an aid to configuration and/or
	deployment planning.

	Since different operating systems (such as Linux or Windows) 
	enumerate the NICs in differing order for different blade types, an 
	OS selection field will appear for some blade types.  The "Default OS"
	selection field defines what OS is selected by default.
	
	The following OS enumerations are supported in this version of hpecm:

		Select "Windows" as the OS for servers running:
			MS Windows 2000 Server
			MS Windows Server 2003

		Select "Red Hat 3" as the OS for servers running:
			Red Hat Enterprise Linux 3 (x86)

		Select "RH 4, SLES 9" as the OS for servers running:
			Red Hat Enterprise Linux 4 (x86)
			SuSE Linux Enterprise Server 9/OES (x86)
	
	The following Blade Servers are supported in this version of hpecm:
		BL20p
		BL20p +NIC upgrade (i.e., with FE to GE NIC upgrade card)
		BL20p-G2
		BL20p-G3
		BL25p
		BL30p
		BL35p
		BL40p
		BL45p

	The NIC enumeration is displayed as a switch/patch panel identifier 
	(A or B), a switch/patch panel port number (1-16), and an 
	OS-enumerated NIC device name (LAC 1, eth0, etc.).  For example, 
	"A-4, LAC 2" in the column under Bay 2 would signify that switch A, 
	port 4 is connected to the second NIC in the blade server, as 
	enumerated by the Windows OS.  The Linux device names are of the
	format "eth0, eth1", etc.  Note that since Linux device names may
	be manually specified, the actual device names may differ from 
	those displayed.

	There are two enclosure types: "standard" and "enhanced".  The 
	enhanced (also termed "high density" or "dedicated iLO") enclosure 
	routes the Integrated Lights Out (iLO) NIC to the enhanced 
	enclosure's dedicated (aggregated) iLO port.  The standard enclosure 
	routes the iLO NIC to a switch or patch panel port.  Some newer blade
	server types require that an "enclosure upgrade kit" be installed 
	before the blade may be deployed in a standard (older) enclosure.
	The enclosure upgrade kit makes a standard enclosure functionally
	equivalent to an enhanced enclosure for the purposes of this tool.
	Some blade types (e.g., BL20p-G3) are supported only in an
	enhanced enclosure, even though they may be used in a standard
	enclosure with reduced functionality, such as loss of use of a 
	blade NIC.

	NOTE: When running some versions of Linux (e.g., Red Hat) and using 
	the /proc/net/nicinfo/eth*.info files to determine link status, 
	be aware that the file name on a BL20p-G3 blade server (containing 
	4 nics, eth0-eth3) does not always correspond to the device of the 
	same name.  For instance, the eth2.info file may actually contain 
	link status (as well as other status) for the fourth NIC device, eth3.
		
	The "Fill With Same" button fully populates the enclosure with the 
	top left-most selected blade and OS.

	The "Reset" button erases all selections and calculated information
	and returns hpecm to the startup state.

	The "Cancel" button may be used to exit the tool.

OPTIONS

	None

ERROR CODES

	None


==============================================================================

TFTP SERVER
-----------

The Win32 Interconnect Switch Utilities installation includes a public domain 
TFTP server, which may be used for TFTP operations with the switch, such as
upgrading firmware.
  
The following files comprise this feature and are installed in the 
"tftpserver" subfolder:
	tftpd32.exe	The server
	tftpd32.hlp	The help file


Please note the following if you use the RDP TFTP server:

	The RDP PXE TFTP server uses the default TFTP IP port, 69, and is 
	unidirectional (to switch) only.  Therefore any other TFTP use on
	the RDP server must use a port other than 69.  The included TFTP
	server should be configured to use another port, and the switch
	must also be configured to use that same port number.  The switch's
	CLI or SNMP interface may be used to configure the TFTP port, if
	necessary.  A firmware upgrade tool, which automatically chooses a
	free TFTP port and configures the switch TFTP port, is included with 
	firmware obtained from the Support web page listed above.

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

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.