HP GBE2C User Manual

HP GbE2c Layer 2/3 Ethernet Blade Switch for  
c-Class BladeSystem  
User Guide  
Part Number 440948-001  
December 2006 (First Edition)  
Contents  
Contents 3  
Cannot access the switch serial console interface using null modem connection from a PC Terminal Emulation  
Contents 4  
The port activity LEDs continuously indicate activity after connecting more than one port to another switch or  
The switch does not let the user enable two adjacent ports into two different VLANs while assigning the ports to  
While using TFTP to download firmware, the switch fails to connect to the TFTP server, or after connection the  
The switch fails to connect to the TFTP server while using TFTP to download or upload a configuration file, or after  
The console screen displays a message to change the baud rate for the terminal emulation session for XModem  
Contents 5  
Introduction  
In this section  
Overview ................................................................................................................................................ 6  
Features .................................................................................................................................................. 6  
Switch architecture ................................................................................................................................... 9  
Overview  
This user guide provides installation and reference information for the HP GbE2c Layer 2/3 Ethernet  
Blade Switch for c-class BladeSystem.  
Additional references  
Configure the switch after installation. Detailed information about how to configure the switch is available  
in the reference guides listed below. To obtain these guides, see the HP website  
HP GbE2c Ethernet Blade Switch for c-Class BladeSystem Application Guide  
HP GbE2c Ethernet Blade Switch for c-Class BladeSystem Command Reference Guide  
HP GbE2c Ethernet Blade Switch for c-Class BladeSystem Browser-based Interface Reference Guide  
HP GbE2c Layer 2/3 Ethernet Blade Switch for c-Class BladeSystem Quick Setup Instructions  
The HP GbE2c Layer 2/3 Ethernet Blade Switch for c-Class BladeSystem interconnect kit contains one  
switch.  
The switch uses Gigabit Layer 2/3 switching technology to provide between 16-to-1 to 16-to-5 reduction  
in the number of networking cables per BL c-Class server blade enclosure.  
Each switch reduces sixteen server networking ports to one to five uplink Gigabit ports.  
Features  
The switch is designed for easy installation and high performance in an environment where traffic on the  
network and the number of users increases continually.  
Enterprise class performance  
The switch features include:  
Up to a 16-to-1 reduction in networking cables and connections, concentration of sixteen Gigabit  
Ethernet server ports down to as little as one Gigabit Ethernet port, or up to five Gigabit Ethernet  
uplink ports for additional bandwidth and redundant connections to the network backbone  
Fully supported on the HP c-Class BladeSystem server blade enclosure and infrastructure compatible  
with any combination of HP c-Class BladeSystem server blades  
Introduction 6  
         
Ability to replace an existing switch without having to power down the server blades or the server  
blade enclosure  
Pre-configured for immediate use with the HP c-Class BladeSystem server blade enclosure  
System security including SSH, SCP, 255 port-based IEEE 802.1Q tagged VLANs per switch,  
RADIUS user authentication and authorization, or TACACS+ AAA  
An extensive list of industry standard protocol support, compatible with widely-used networking  
components  
9K jumbo frames that improve performance by increasing application throughput and decreasing  
server processor utilization  
Robust configuration and management from any switch port using the included browser-based and  
scriptable command line user interfaces  
Support for Telnet, SNMP, SCP, FTP, and TFTP file transfer, human read/write configuration file,  
XModem, and an extensive list of MIB objects further enhance the management capabilities  
Fully redundant end-to-end architecture maximizing server availability from the network  
Support for IGMP snooping for multicasting  
Support for UFD for network path resiliency. It works in conjunction with NIC teaming functionality  
that is supported on the blade servers. This feature tracks the link state on uplink ports. When an  
uplink port goes down or is in STP blocking state, this feature will enable the switch to auto disable  
the downlinks which are connected to the blade server NICs. This enables NIC teaming software to  
detect link failure on the primary NIC port and fail over to the secondary NIC in the team. As a  
result, the secondary path is enabled for continued blade server access.  
When used in conjunction with UFD, NIC teams on the blade server must be configured for switch  
redundancy. That is, the team will span ports on both Switch 1 and Switch 2. See the HP network  
adapter teaming: load balancing in ProLiant servers running Microsoft Windows operating systems  
white paper for additional information. To locate this white paper:  
b. Enter "nic" in the product search box.  
c. A product list displays. Select one of the NIC products.  
d. Select the "Manuals" link to display the documentation list. This white paper will be under the  
"White papers" category.  
RMON feature, which allows network devices to exchange network monitoring data. RMON  
performs these major functions:  
o Gathers cumulative statistics for Ethernet interfaces  
o Tracks a history of statistics for Ethernet interfaces  
o Creates and triggers alarms for user-defined events  
An administrator can define end user accounts that permit limited access to the switch. The switch  
requires username/password authentication for end users.  
Fast Uplink Convergence that enables the switch to quickly recover from the failure of the primary  
link or trunk group in a Layer 2 network using Spanning Tree Protocol.  
Support for SSH version 2. SSH is a protocol that enables remote administrators to log securely into  
the switch over a network to execute management commands.  
Switch software provides SNMP support for access through any network management software, such  
as HP OpenView.  
Support for HTTP software upgrade using the BBI. FTP or TFTP server is not required to perform a  
software upgrade.  
Port Fast Forwarding that allows a port that participates in Spanning Tree to bypass the Listening and  
Learning states and enter directly into the Forwarding state.  
Allows secure browser access (HTTPS) to management functions  
Introduction 7  
Switch redundancy  
In a dual switch configuration, the switches offer several redundancy and failover features. With these  
features, the network configuration is designed to allow for continued network access to each server  
blade in case of a component or link failure. The switch redundancy and failover features include:  
Up to eight separate switches per one HP c-Class BladeSystem server blade enclosure  
Five Gigabit Ethernet uplink ports, per switch, for designing fully meshed uplink paths to the network  
backbone  
Server networking connections routed to each of the separate switches for redundant paths to  
tolerate a switch or port malfunction  
Redundant data path Gigabit Ethernet cross connections between switches  
STP support that eliminates potential problems caused by redundant networking paths and provides  
for failover with a secondary path in case of primary path failure; supports IEEE 802.1D Spanning  
Tree Protocol and is compatible with Cisco® PVST+ and Cisco PVST, when the other device is  
configured as untagged or configured to use 802.1q tagging. The switch also supports IEEE 802.1s  
MSTP and IEEE 802.1w RSTP.  
Redundant power supplies and redundant cooling fans within the server blade enclosure  
Redundant firmware images and configuration settings on switch flash memory  
Redundant, configurable DNS clients, syslog servers, gateways, and community strings and SNMP  
trap manager hosts  
Configuration and management  
The switch provides these configuration and management interfaces and tools:  
A scriptable CLI allows local, Telnet, or SSH access.  
A BBI allows remote access using a Web browser such as Microsoft® Internet Explorer or Netscape  
Navigator.  
SNMP manageability and monitoring are supported.  
The switch functionality allows uploading and downloading of switch configurations through TFTP  
and SCP, thus allowing the rapid deployment of multiple server blade systems, and providing robust  
backup and restore capabilities.  
NTP is supported, allowing the switch to display and record the accurate date and time as provided  
by an NTP server.  
Two firmware images, either of which can be selected to be the current runtime image, can be held  
in memory.  
RADIUS provides support for user authentication and authorization.  
TACACS+ provides support for Cisco TACACS+ server compatible authentication, authorization,  
and accounting.  
The user interfaces provide multi-level password protected user accounts.  
IP settings are set manually or obtained automatically from a BOOTP server.  
A text-based, human read/write configuration file provides viewing, printing, and editing  
capabilities.  
A DNS client supports primary and secondary DNS servers.  
Any port can be enabled or disabled as desired.  
Any switch port can be used to perform switch management and PXE.  
Introduction 8  
   
Diagnostic tools  
The hardware, software, and firmware diagnostic tools that are available include:  
HP Systems Insight Manager automatic discovery and identification  
POST built into the switch boot process  
Switch port mirroring  
Switch LED panel displaying per port status and speed  
System, management, and option compatibility status LEDs  
Rear panel reset power switch and DB-9 management serial port  
Statistic monitoring including port utilization, data packets received/transmitted, port error packets,  
trunk utilization, and so on  
Ping and trace route capability  
Remote syslog with support for primary and secondary syslog server  
The ability to return the switch to known good condition in case of firmware corruption  
State information dump for tuning and debugging switch performance  
Panic command for immediate state dump to flash memory and automatic switch boot  
Ability to set NVRAM diagnostic flags  
Switch architecture  
The HP c-Class BladeSystem provides Ethernet switching technology for network cable reduction.  
The switch does not affect or determine NIC enumeration and the associated mapping of NIC interfaces  
to switch ports. The numbering of the NICs on the server (for example, NIC 1, NIC 2, NIC 3) is  
determined by the server type, the server operating system, and what NICs are enabled on the server.  
Port Mapping  
For detailed port mapping information, see the HP BladeSystem enclosure installation poster or the HP  
BladeSystem enclosure setup and installation guide on the HP website  
Dual switches  
In a dual switch configuration, two switches in the server blade enclosure provide switch redundancy and  
redundant paths to the network ports on the server blades. Each switch has five external Gigabit Ethernet  
ports and sixteen internal Gigabit Ethernet ports providing connectivity to the blade servers within the  
enclosure.  
Each pair of switches consolidates up to thirty-two Gigabit Ethernet signals into one-to-ten Gigabit ports  
(on the back of the enclosure).  
Redundant crosslinks  
In a dual switch configuration, the two switches are connected through redundant Gigabit crosslinks.  
These two crosslinks provide an aggregate throughput of 2 Gb/s for traffic between the switches.  
These crosslinks are disabled by default. The crosslinks must be enabled for use.  
Introduction 9  
         
Redundant paths to server bays  
In a dual switch configuration, redundant Ethernet signals from each blade server are routed through the  
enclosure backplane to separate switches within the enclosure. This configuration provides redundant  
paths to each server bay.  
Redundant Ethernet signals from each blade server are routed through the enclosure backplane to  
separate switches within the enclosure. However, specific switch port to server mapping varies depending  
on which type of server blade is installed.  
On a heavily used system, using a single uplink port for 32 Ethernet signals causes a traffic bottleneck.  
For optimum performance, HP recommends using at least one uplink port per switch.  
Supported technologies  
Layer 2 switching  
The switch uses Gigabit Layer 2 switching technology. Layer 2 refers to the Data Link layer of the OSI  
model, which is concerned with moving data packets across a network by enforcing CSMA/CD. This  
layer performs:  
Ethernet packet framing  
MAC addressing  
Physical medium transmission error detection  
Medium allocation (collision avoidance)  
Contention resolution (collision handling)  
Layer 2 switching technology allows the switch to look into data packets and redirect them based on the  
destination MAC address. This reduces traffic congestion on the network because packets, instead of  
being transmitted to all ports, are transmitted to the destination port only.  
Layer 3 switching  
In addition to Layer 2 features, the switch also supports Layer 3 switching. Layer 3 switching features  
include:  
IP forwarding  
Static routing  
Dynamic routing based on RIP V1/V2 or OSPF protocols  
High availability VRRP  
Layer 3 switching provides more power, flexibility, and security capabilities to network administrators.  
Network traffic is managed much more efficiently and broadcast traffic between servers remains within  
the enclosure. Security features provide added protection for switch configuration data, while packet  
filtering helps secure and segment sensitive traffic or network access.  
IEEE 802.1 Q-based VLAN  
The switch provides support for a total of 255 IEEE 802.1Q VLANs for server grouping and isolation. A  
VLAN is a network segment configured according to a logical scheme rather than a physical layout.  
VLANs are used to combine any collection of LAN segments into an autonomous user group that appears  
as a single LAN.  
Introduction 10  
         
VLANs also logically segment the physical network into different broadcast domains so that packets are  
forwarded only between ports within the VLAN. This technology enhances performance by conserving  
bandwidth and improves security by limiting traffic to specific domains. For example, isolate the server  
blade iLO ports from the rest of the NICs. The iLO ports on Switch 2 are assigned to their own VLAN and  
go to a dedicated uplink or share an uplink using VLAN tagging.  
IMPORTANT: The greater the number of VLANs, the greater the switch CPU utilization. For  
maximum switch performance, HP recommends being judicious when configuring the number  
of VLANs.  
NOTE: VLAN 4095 is reserved for future functionality.  
Spanning Tree Protocol  
The switch supports IEEE 802.1D STP, which allows the blocking of links that form loops between switches  
in a network. When multiple links between switches are detected, a primary link is established.  
Duplicated links are blocked from use and become standby links. If the primary link fails, the standby link  
is activated.  
In addition, the switch provides a spanning tree domain per VLAN. The switch is compatible with Cisco®  
PVST+ and Cisco PVST, when the other device is configured as untagged or configured to use 802.1q  
tagging. Sixteen spanning tree domains are supported per switch.  
NOTE: STP 16 is reserved for future functionality.  
The switch also provides IEEE 802.1s-based MSTP and IEEE 802.1w-based RSTP.  
SNMP  
The switch is configured and monitored remotely from an SNMP-based network management station. The  
switch supports industry-standard SNMP MIBs and proprietary HP enterprise switch MIBs for fault  
detection and monitoring of switch functionality. In addition, the switch supports various environmental  
traps such as temperature and fan failure traps.  
To secure the management interface, the switch administrator configures community strings with two levels  
of access: Read and Read/Write. Access to the switch is also restricted to only management stations that  
are members of a specific IP network. This is achieved by configuring the address/mask of that specific  
network as a restricted management network address/mask.  
Port mirroring  
The switch allows mirroring of one or multiple ports (source ports) to another port (destination port) for  
network monitoring and troubleshooting purposes. This technology offers a way for network packet  
analyzers to view the traffic moving through the switch by providing a copy of the traffic that is currently  
being passed through any other port. The packets are sent to a network packet analyzer or other  
monitoring device attached to the mirror port.  
Port trunking and load balancing  
The switch supports EtherChannel compatible IEEE 802.3ad (without LACP) port trunking allowing several  
ports to be grouped together and act as a single logical link called a trunk. This feature provides a  
Introduction 11  
       
bandwidth that is a multiple of the bandwidth of a single link. It also improves reliability since load  
balancing is automatically applied to the ports in the trunked group. A link failure within the group causes  
the network traffic to be directed to the remaining links in the group.  
TFTP support  
TFTP support allows the switch firmware to be upgraded by downloading a new firmware file from a TFTP  
server to the switch. Firmware images of the switch are also uploaded to a TFTP server, a configuration  
file is downloaded into a switch from a TFTP server, and configuration settings are saved to the TFTP  
server.  
Store and forward switching scheme  
The switch provides a store and forward switching scheme that allows each packet to be buffered (stored)  
before it is forwarded to its destination. While this method creates latency, it improves reliability in a  
heavily used switch. Packets that cannot be forwarded are saved immediately, rather than dropped, so  
that packets behind them are less likely to be dropped in periods of heavy usage.  
BOOTP  
By default, the switch is configured to obtain an IP address from a BOOTP server during the boot process.  
The IP settings are also manually configured by means of the serial interface. The IP settings are  
configurable from the browser-based interface, but because the connection is based on an IP address for  
these interfaces, users will have to reconnect with the newly assigned IP address.  
NTP  
The switch maintains the current date and time. This information displays on the management interfaces  
and is used to record the date and time of switch events. Current date and time information are manually  
set on the switch or are obtained through NTP. NTP allows the switch to send a request to a primary NTP  
server in each polling period asking for GMT.  
RADIUS  
The switch supports the RADIUS method to authenticate and authorize remote administrators for managing  
the switch. This method is based on a client/server model. The RAS, the switch, is a client to the back-end  
database server. A remote user (the remote administrator) interacts only with the RAS, not the back-end  
server and database.  
RADIUS authentication consists of:  
A protocol with a frame format that utilizes UDP over IP, based on RFC 2138 and 2866  
A centralized server that stores all the user authorization information  
A client, in this case, the switch  
The switch, acting as the RADIUS client, communicates to the RADIUS server to authenticate and authorize  
a remote administrator using the protocol definitions specified in RFC 2138 and 2866. Transactions  
between the client and the RADIUS server are authenticated using a shared key that is not sent over the  
network. In addition, the remote administrator passwords are sent encrypted between the RADIUS client  
(the switch) and the back-end RADIUS server.  
The benefits of using RADIUS are:  
Authentication of remote administrators  
Introduction 12  
         
Identification of the administrator using name/password  
Authorization of remote administrators  
Determination of the permitted actions and customizing service for individual administrators  
TACACS+  
The switch supports the TACACS+ method to authenticate, authorize, and account for remote  
administrators managing the switch. This method is based on a client/server model. The switch is a client  
to the back-end TACACS+ AAA server. A remote user (the remote administrator) interacts only with the  
client, and not with the back end AAA server.  
The TACACS+ AAA method consists of:  
A protocol with a frame format that utilizes TCP over IP  
A centralized AAA server that stores all the user authentication, authorization, and accounting (of  
usage) information  
A NAS or client (in this case, the switch)  
The switch, acting as the TACACS+ client or NAS, communicates to the TACACS+ server to authenticate,  
authorize, and account for user access. Transactions between the client and the TACACS+ server are  
authenticated using a shared key that is not sent over the network. In addition, the remote administrator  
passwords are sent encrypted between the TACACS+ client (the switch) and the back-end TACACS+  
server.  
The switch supports:  
Only standard ASCII inbound login authentication. PAP, CHAP, or ARAP login methods are not  
supported. One-time password authentication is also not supported.  
Authorization privilege levels of only 0, 3, and 6. These map to management levels of user, oper,  
and admin, respectively.  
The accounting attributes of protocol, start_time, stop_time, and elapsed_time. For BBI users,  
accounting stop records are only sent if the user presses the QUIT button.  
SSH and SCP  
SSH and SCP use secure tunnels to encrypt and secure messages between a remote administrator and the  
switch. Telnet does not provide this level of security. The Telnet method of managing a switch does not  
provide a secure connection.  
SSH is a protocol that enables remote administrators to log securely into the switch over a network to  
execute management commands.  
SCP is used to copy files securely from one machine to another. SCP uses SSH for encryption of data on  
the network. On a switch, SCP is used to download and upload the switch configuration via secure  
channels.  
XModem  
The switch supports XModem for transferring files during direct dial-up communications. XModem sends  
blocks of data in 128-byte blocks, and includes an error-detection system called a checksum. When the  
data is received, the error detection system ensures that the entire message reached its destination. If not,  
the receiving computer sends a request for retransmission of the data.  
Introduction 13  
     
IGMP Snooping  
The switch supports IGMP Snooping for multicasting. Both Version 1- and Version 2-based IGMP  
Snooping are supported. In addition, auto detection of the multicast router port and manual configuration  
of the multicast router port is supported. For efficient multicast traffic management, the IGMP Filtering  
option is supported.  
Jumbo frames  
By default, the switch supports jumbo frames up to 9216 bytes, which help reduce server CPU utilization  
and increase application throughput. No configuration is required. The switch does not fragment frames  
as they exit, or assemble packets into jumbo frames as they enter the switch.  
Auto-MDI/MDIX  
The switch Ethernet ports are MDI/MDI crossover capable. MDI/MDIX is a type of Ethernet port  
connection using twisted pair cabling. The MDI is the component of the MAU that provides the physical  
and electrical connection to the cabling medium. An MDIX is a version of MDI that enables connection  
between like devices. MDI ports connect to MDIX ports via straight-through twisted pair cabling whereas  
both MDI-to-MDI and MDIX-to-MDIX connections use crossover twisted pair cabling. The switch has the  
capability to automatically detect the cable selection/type, making the distinction between a straight-  
through cable and a crossover cable unimportant.  
Auto-negotiation of duplex mode and speed  
Auto-negotiation of duplex mode and speed are configured on the switch. Network adapters that support  
multiple data speeds, such as Fast Ethernet and Gigabit Ethernet, choose the speed at which they run  
through a procedure called auto-negotiation. Auto-negotiation involves probing the capability of the  
network using low-level signaling techniques to select compatible Ethernet speeds. Auto-negotiation was  
originally developed to make the migration from traditional Ethernet to Fast Ethernet products easier.  
Redundant images in firmware  
The switch stores up to two different software images, called image1 and image2, as well as boot  
software, called boot. When downloading new software, the ability to specify where it is to be placed  
(into image1, image2, or boot) is activated.  
For example, if the active image is currently loaded into image1, load the new image software into  
image2. This allows a test of the new software and the option to revert back to the original image stored  
in image1, if needed.  
CAUTION: Unlike the firmware that has two images, there is only one image of boot  
supported. Upgrading the boot image replaces the original boot image.  
Introduction 14  
         
Component identification  
In this section  
GbE2c Layer 2/3 front panel .................................................................................................................. 15  
GbE2c Layer 2/3 front panel  
CAUTION: Pressing the Reset button while the Health LED is green resets the switch.  
Item  
Description  
1 UID  
2 Hea  
LED  
lth LED  
Off—Not powered up  
Green—Powered up and all ports match  
Amber—Indicates a problem such as a port mismatch. For more  
information, see the HP BladeSystem enclosure setup and  
installation guide.  
3
DB-9 management serial port  
RJ-45 port 20  
4
5
SFP transceiver cages 21-24  
RJ-45 ports 21-24  
button  
6
7 Reset  
Component identification 15  
   
Installing the switch  
In this section  
Planning the switch configuration............................................................................................................. 16  
Installing the switch ................................................................................................................................ 19  
Installing SFP transceivers........................................................................................................................ 21  
Planning the switch configuration  
NOTE: Only one port number can be used at a time. SFP transceiver ports have priority over  
the RJ-45 ports.  
The switch ships with a default configuration in which all downlink and uplink ports are enabled and  
assigned a default VLAN with a VID equal to 1. This default configuration simplifies the initial setup by  
allowing use of a single uplink cable (from any external Ethernet connector) to connect the server blade  
enclosure to the network. By default, the X-connect ports (17 and 18) are disabled. Assess the particular  
server environment to determine any requirements for other considerations.  
The switch does not affect or determine NIC numeration and the associated mapping of NIC interfaces to  
switch ports. The numbering of the NICs on the server (for example, NIC 1, NIC 2, NIC 3) is determined  
by the server type, the server operating system, and which NICs are enabled on the server.  
NOTE: Port 19 is reserved for connection to the Onboard Administrator module for switch  
management. This allows a user to enable the functionality of future firmware upgrade  
releases.  
The Onboard Administrator module controls all port enabling. Enabling is based on matching ports  
between the server and the interconnect bay. Before power up, the Onboard Administrator module  
verifies that the server NIC option matches the switch bay that is selected and enables all ports for the  
NICs installed.  
For detailed port mapping information, see the HP BladeSystem enclosure installation poster or the HP  
BladeSystem enclosure setup and installation guide on the HP website  
Default settings  
The switch ships with a default configuration in which all downlink and uplink ports are enabled and  
assigned a default VLAN with a VID equal to 1. This default configuration simplifies the initial setup by  
allowing use of a single uplink cable (from any external Ethernet connector) to connect the server blade  
enclosure to the network. By default, the X-connect ports (17 and 18) are disabled. Assess the particular  
server environment to determine any requirements for other considerations.  
The switch does not affect or determine NIC numeration and the associated mapping of NIC interfaces to  
switch ports. The numbering of the NICs on the server (for example, NIC 1, NIC 2, NIC 3) is determined  
by the server type, the server operating system, and what NICs are enabled on the server.  
Installing the switch 16  
     
The Onboard Administrator module controls all port enabling. Enabling is based on matching ports  
between the server and the interconnect bay. Before power up, the Onboard Administrator module  
verifies that the server NIC option matches the switch bay that is selected and enables all ports for the  
NICs installed.  
NOTE: Port 19 is reserved for connection to the Onboard Administrator module for switch  
management. This allows a user to enable the functionality of future firmware upgrade  
releases.  
For detailed port mapping information, see the HP BladeSystem enclosure installation poster or the HP  
BladeSystem enclosure setup and installation guide on the HP website  
When planning the configuration, consider the default settings for these parameters:  
Switch IP settings  
VLAN settings  
STP settings  
Port names and types  
Port trunking settings  
Interswitch X-Connect port settings  
SNMP settings  
User name and password settings  
Default access to various management interfaces  
NTP settings  
IMPORTANT: See "Runtime switching software default settings (on page 29)" for a complete  
list of default configuration settings.  
Switch security  
When planning the switch configuration, secure access to the management interface by:  
Creating users with various access levels  
Enabling or disabling access to various management interfaces to fit the security policy  
Changing default SNMP community strings for read-only and read-write access  
User, operator, and administrator access rights  
To enable better switch management and user accountability, three levels or classes of user access have  
been implemented on the switch. Levels of access to CLI, Web management functions, and screens  
increase as needed to perform various switch management tasks. Conceptually, access classes are  
defined as:  
User interaction with the switch is completely passive. Nothing can be changed on the switch. Users  
can display information that has no security or privacy implications, such as switch statistics and  
current operational state information.  
Operators can only effect temporary changes on the switch. These changes will be lost when the  
switch is rebooted/reset. Operators have access to the switch management features used for daily  
switch operations. Because any changes an operator makes are undone by a reset of the switch,  
operators cannot severely impact switch operation.  
Installing the switch 17  
 
Administrators are the only ones that can make permanent changes to the switch configuration,  
changes that are persistent across a reboot/reset of the switch. Administrators can access switch  
functions to configure and troubleshoot problems on the switch. Because administrators can also  
make temporary (operator-level) changes as well, they must be aware of the interactions between  
temporary and permanent changes.  
Access to switch functions is controlled through the use of unique surnames and passwords. Once  
connected to the switch via the local console, Telnet, or SSH, a password prompt appears.  
NOTE: It is recommended to change the default switch passwords after initial configuration  
and as regularly as required under the network security policies. For more information, see the  
HP GbE2c Ethernet Blade Switch for c-Class BladeSystem Command Reference Guide.  
The default user name and password for each access level are:  
User account  
Description and tasks performed  
Password  
User  
The user has no direct responsibility for switch management. He or she user  
can view all switch status information and statistics, but cannot make  
any configuration changes to the switch.  
Operator  
The operator manages all functions of the switch. The operator can  
reset ports or the entire switch.  
By default, the operator account is disabled and has no password.  
Administrator  
The super user administrator has complete access to all menus,  
information, and configuration commands on the switch, including the  
ability to change both the user and administrator passwords.  
admin  
Manually configuring a switch  
The switch is configured manually using a command line interface, a browser-based interface, or an  
SNMP interface. See the HP GbE2c Ethernet Blade Switch for c-Class BladeSystem Command Reference  
Guide for more information on using these management interfaces to configure the switch.  
After a switch is configured, back up the configuration as a text file to a TFTP server. The backup  
configuration file is then downloaded from the TFTP server to restore the switch back to the original  
configuration. This restoration is necessary if one of these conditions apply:  
The switch configuration becomes corrupted during operation.  
The switch must be replaced because of a hardware failure.  
Configuring multiple switches  
Configure multiple switches by using scripted CLI commands through Telnet or by downloading a  
configuration file using a TFTP server.  
Using scripted CLI commands through Telnet  
The CLI, provided with the switch, executes customized configuration scripts on multiple switches. A  
configuration script is tailored to one of the multiple switches, and then that configuration can be  
deployed to other switches from a central deployment server.  
Installing the switch 18  
   
Using a configuration file  
If planning for the base configuration of multiple switches in a network to be the same, manually  
configure one switch, upload the configuration to a TFTP server, and use that configuration as a base  
configuration template file.  
Switch IP addresses are acquired by default using BOOTP, therefore, each switch has a unique IP  
address. Each switch is remotely accessed from a central deployment server and an individual switch  
configuration is downloaded to meet specific network requirements. See the HP GbE2c Ethernet Blade  
Switch for c-Class BladeSystem Command Reference Guide for additional information on using a TFTP  
server to upload and download configuration files.  
Installing the switch  
Preparing for installation  
IMPORTANT: Before installing the switch, make a record of the MAC address (printed on the  
MAC address label attached to the switch). This address is needed when configuring the  
switch.  
Installing the switch  
CAUTION: Do not cable the switch until after configuration.  
IMPORTANT: Make sure that the server NIC configuration matches the switch bay selected.  
NOTE: When installing two switches, there are two switch interconnect ports between  
adjacent I/O bays. These ports (17 and 18) are disabled by default. The ports must be  
manually enabled to use.  
Installing the switch 19  
     
A successful installation is indicated by a green Health LED. If the Health LED is amber or power is not  
applied to the switch, see the "Troubleshooting" section of the HP BladeSystem enclosure setup and  
installation guide for more information.  
Accessing the switch  
The switch is accessed remotely using the Ethernet ports or locally using the DB-9 management serial port.  
To access the switch remotely:  
1.  
Assign an IP address. By default, the switch is set up to obtain its IP address from a BOOTP server  
existing on the attached network.  
2.  
3.  
From the BOOTP server, use the switch MAC address to obtain the switch IP address.  
From a computer connected to the same network, use the IP address to access the switch using a  
Web browser or telnet application, which enables access to the switch BBI or CLI. The switch logon  
prompt appears.  
Installing the switch 20  
 
NOTE: If the switch does not obtain the IP address by means of the BOOTP service, access the  
switch locally and configure the IP address manually. After assigning the IP address to the  
switch, then access the switch remotely.  
To access the switch locally:  
1.  
Connect the switch DB-9 serial connector, using a null-modem serial cable to a local client device  
(such as a laptop computer) with VT100 terminal emulation software.  
2.  
Open a VT100 terminal emulation session with these settings: 9600 baud rate, eight data bits, no  
parity, one stop bit, and no flow control.  
Logging on and configuring the switch  
To log on to the switch:  
1.  
Access the switch ("Accessing the switch" on page 20). After connecting to the switch console, the  
login prompt appears.  
2.  
Enter admin as the default administrator password.  
The Main Menu appears and displays all administrator privileges:  
See the HP GbE2c Ethernet Blade Switch for c-Class BladeSystem Command Reference Guide for  
information on configuring the IP address, changing configuration settings, and monitoring switch  
operation using one of the following interfaces:  
Local RS-232 serial console management interface  
Remote telnet console management interface  
See the HP GbE2c Ethernet Blade Switch for c-Class BladeSystem Browser-based Interface Reference  
Guide for information on using the embedded HTML interface to manage the switch from anywhere on  
the network using a standard browser, such as Netscape Navigator or Microsoft® Internet Explorer.  
See "SNMP MIBs support (on page 43)" for more information on the SNMP agents. This section also  
describes how to use the MIBs to configure and monitor the switch using a generic SNMP manager, such  
as HP OpenView Network Node Manager or HP Systems Insight Manager.  
Installing SFP transceivers  
Installing the switch 21  
   
CAUTION: Do not install or remove fiber-optic SFP transceivers with cables attached because  
of the potential damage to the cables, the cable connector, or the optical interfaces in the SFP  
transceiver. Disconnect all cables before removing or installing an SFP transceiver.  
Removing and installing an SFP transceiver can shorten the useful life. Do not remove and  
insert SFP transceivers more often than is necessary.  
1.  
Attach an ESD-preventative wrist strap to your wrist and to a bare metal surface on the chassis.  
CAUTION: Do not remove the dust plugs from the fiber-optic SFP transceiver or the rubber  
plugs from the fiber-optic cable until you are ready to connect the cable. The plugs and caps  
protect the SFP transceiver ports and cables from contamination and ambient light.  
2.  
3.  
Remove the dust cap and save for future use.  
IMPORTANT: Use only SFP transceivers purchased from HP.  
Insert the SFP transceiver.  
Supporting software and special considerations  
Supporting software is available to assist in configuring and managing the switch.  
Server Blade and Power Management Module Firmware—Provides firmware and installation  
instructions required for proper rack location operation.  
Utilities package and documentation—Provides utilities and documentation for switch management.  
Firmware Upgrade Smart Component (for Microsoft Windows only)—Provides quick and easy  
installation of the switch firmware, firmware upgrade tool, and readmefile. A SoftPaq is available  
for use with Linux operating systems.  
The utilities package and documentation, and the SoftPaq listed above, are available on the HP website  
Installing the switch 22  
 
Replacing a switch  
In this section  
Replacing an existing switch.................................................................................................................... 23  
Replacing an existing switch  
CAUTION: Removing the switch from a powered enclosure results in the loss of network  
communications between the server blade network ports that are connected through this switch  
and the segment of network infrastructure those ports need to communicate.  
For continued blade server network communication and services availability before removing  
the switch, redirect critical high-availability services or applications to use the redundant  
network ports available on those blade servers that are connected through the redundant  
switch in the enclosure.  
CAUTION: Do not cable the switch until after configuration.  
To replace an existing switch:  
1.  
Save the configuration file to a TFTP server for later retrieval. For more information on saving a  
configuration file to a TFTP server, see the HP GbE2c Ethernet Blade Switch for c-Class BladeSystem  
Command Reference Guide.  
2.  
3.  
Remove and label the cables.  
Remove the switch.  
4.  
5.  
Slide the new switch fully into the interconnect bay. For more installation information, see "Installing  
the switch (on page 19, on page 19)."  
Close the ejector lever and wait for the switch boot up completely.  
Replacing a switch 23  
   
6.  
If the configuration file was saved to a TFTP server, download the configuration. For more  
information on downloading a configuration file, see the HP GbE2c Ethernet Blade Switch for c-  
Class BladeSystem Command Reference Guide.  
Replacing a switch 24  
Regulatory compliance notices  
In this section  
Class A equipment ................................................................................................................................. 25  
Cables.................................................................................................................................................. 25  
Canadian notice .................................................................................................................................... 25  
European Union regulatory notice............................................................................................................ 25  
Japanese class A notice .......................................................................................................................... 26  
Laser compliance ................................................................................................................................... 27  
Class A equipment  
This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant  
to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful  
interference when the equipment is operated in a commercial environment. This equipment generates,  
uses, and can radiate radio frequency energy and, if not installed and used in accordance with the  
instructions, may cause harmful interference to radio communications. Operation of this equipment in a  
residential area is likely to cause harmful interference, in which case the user will be required to correct  
the interference at personal expense.  
Modifications  
The FCC requires the user to be notified that any changes or modifications made to this device that are  
not expressly approved by Hewlett-Packard Company may void the user’s authority to operate the  
equipment.  
Cables  
Connections to this device must be made with shielded cables with metallic RFI/EMI connector hoods in  
order to maintain compliance with FCC Rules and Regulations.  
Canadian notice  
This Class A digital apparatus meets all requirements of the Canadian Interference-Causing Equipment  
Regulations.  
Cet appareil numérique de la classe A respecte toutes les exigences du Règlement sur le matériel  
brouilleur du Canada.  
European Union regulatory notice  
This product complies with the following EU Directives:  
Regulatory compliance notices 25  
           
Low Voltage Directive 73/23/EEC  
EMC Directive 89/336/EEC  
Compliance with these directives implies conformity to applicable harmonized European standards  
(European Norms) which are listed on the EU Declaration of Conformity issued by Hewlett-Packard for this  
product or product family.  
This compliance is indicated by the following conformity marking placed on the product:  
This marking is valid for non-Telecom products and EU harmonized Telecom products (e.g. Bluetooth).  
This marking is valid for EU non-harmonized Telecom products.  
*Notified body number (used only if applicable—refer to the product label)  
Hewlett-Packard GmbH, HQ-TRE, Herrenberger Strasse 140, 71034 Boeblingen, Germany  
BSMI notice  
Japanese class A notice  
Korean class A notice  
Regulatory compliance notices 26  
     
Laser compliance  
This product may be provided with an optical storage device (that is, CD or DVD drive) and/or fiber optic  
transceiver. Each of these devices contains a laser that is classified as a Class 1 Laser Product in  
accordance with US FDA regulations and the IEC 60825-1. The product does not emit hazardous laser  
radiation.  
Each laser product complies with 21 CFR 1040.10 and 1040.11 except for deviations pursuant to Laser  
Notice No. 50, dated May 27, 2001; and with IEC 60825-1:1993/A2:2001.  
WARNING: Use of controls or adjustments or performance of procedures other than those  
specified herein or in the laser product's installation guide may result in hazardous radiation  
exposure. To reduce the risk of exposure to hazardous radiation:  
Do not try to open the module enclosure. There are no user-serviceable components inside.  
Do not operate controls, make adjustments, or perform procedures to the laser device other  
than those specified herein.  
Allow only HP Authorized Service technicians to repair the unit.  
The Center for Devices and Radiological Health (CDRH) of the U.S. Food and Drug Administration  
implemented regulations for laser products on August 2, 1976. These regulations apply to laser products  
manufactured from August 1, 1976. Compliance is mandatory for products marketed in the United States.  
Regulatory compliance notices 27  
 
Technical specifications  
In this section  
General specifications ............................................................................................................................ 28  
Physical and environmental specifications ................................................................................................. 36  
Performance specifications ...................................................................................................................... 36  
General specifications  
Category  
Standards:  
Specification  
IEEE 802.3 10Base-T Ethernet  
IEEE 802.3u 100Base-TX Fast Ethernet  
IEEE 802.3ab 1000Base-T Ethernet  
IEEE 802.3z 1000Base-SX Ethernet  
IEEE 802.1D Spanning Tree Protocol  
IEEE 802.1s Multiple Spanning Tree Protocol  
IEEE 802.1w Rapid Spanning Tree Protocol  
IEEE 802.1Q VLAN  
IEEE 802.3ac Frame Extensions for VLAN  
IEEE 802.3ad Link Aggregation Protocol (No LACP support)  
IEEE 802.3x Full-Duplex Flow Control  
ANSI/IEEE 802.3 Nway Auto-Negotiation  
A/CD  
Protocols: CSM  
Data transfer rates:  
Ethernet  
Half-Duplex: 10 Mb/s  
Full-Duplex: 20 Mb/s  
Half-Duplex: 100 Mb/s  
Full-Duplex: 200 Mb/s  
Half-Duplex: 2000 Mb/s  
Full-Duplex: 2000 Mb/s  
Fast Ethernet  
Gigabit Ethernet  
Connectors:  
HP GbE2c switch  
10Base-T  
5 RJ-45, 1 DB-9, 4 SFP transceiver cages  
Two Pair UTP Category 3, 4, 5 (100 m)  
EIA/TIA-568 100-ohm STP (100 m)  
Two Pair or Four Pair UTP Category 5 (100 m)  
EIA/TIA-568 100-ohm STP (100 m)  
Four Pair UTP Category 5e (100 m)  
EIA/TIA-568 100-ohm STP (100 m)  
100Base-TX  
1000Base-T  
Technical specifications 28  
   
Category  
Specification  
Number of ports per switch: 16 x 1000-Mb/s ports dedicated to the server blade for switch communications  
2 x 1000-Mb/s ports dedicated to communications between switches that are  
inserted in ports 1 and 2, 3 and 4, 5 and 6, or 7 and 8  
5 x 10Base-T/100Base-TX/1000Base-T RJ-45 ports  
1 x serial RS-232 DB-9 rear panel management serial port  
4 x SFP 1000Base-SX transceivers  
Runtime switching software default settings  
General default settings  
Setting  
Value  
Notice None  
Banner None  
User names and  
passwords  
User names and passwords:  
user—Enabled, password is user  
oper—Disabled, no password  
admin—Enabled (cannot be disabled), password is admin  
BOOTP service  
Enabled  
0.0.0.0  
IP address (if manual IP  
option is selected)  
Subnet mask (if manual IP 0.0.0.0  
option is selected)  
Primary default gateway  
0.0.0.0  
0.0.0.0  
Secondary default  
gateway  
Primary DNS server  
address  
0.0.0.0  
0.0.0.0  
Secondary DNS server  
address  
Default domain name  
None  
Management  
network/mask  
0.0.0.0 / 0.0.0.0  
Switch software image on Image 1  
next boot  
Switch Config file on next Active  
boot  
Display Hostname  
(sysName) in CLI prompt  
Disabled  
Idle timeout  
Telnet status  
Telnet port  
Web status  
5 minutes  
Enabled  
23  
Enabled  
Technical specifications 29  
   
Setting  
Value  
Web port  
80  
Backpressure Disabled  
Port state  
Enabled  
Port speed/duplex  
Flow control  
STP  
Auto  
Receive & transmit  
STG 1—Enabled with default VLAN (VID=1)  
Port 1-16 (server ports) STP—Disabled at port level  
STG 2-16—Disabled  
20 seconds  
2 seconds  
Bridge Max Age  
Bridge Hello Time  
Bridge Forward Delay  
Bridge Priority  
15 seconds  
32768  
MAC Address Aging Time 300 seconds  
Port Priority  
Path Cost  
128  
4
Static VLAN Entry  
Port VID  
Default VLAN (VID = 1)  
1 for all ports  
Port Trunking  
Trunk group 1, enabled with port 17 and 18  
Port Trunking Load Sharing The algorithm selects the following as forwarding ports for forwarding traffic:  
Algorithm  
1
2
3
For forwarding IP Packets—modulus of XOR of last 3 bits of source and last 3  
bits of Destination IP address  
For forwarding non-IP packets—modulus of XOR of last 3 bits of source and  
last 3 bits of Destination MAC address  
For forwarding broadcast, multicast packets, and unknown unicast packets—  
the lowest active port number in the trunk group  
Port Mirroring-Mirror Status Disabled  
Port Mirroring-Mirror Port  
None selected  
Port Mirroring-Mirror Port  
Traffic Direction  
None selected  
Port Mirroring-Monitoring  
Port  
None selected  
SNMP Read/  
write  
None  
SNMP System Name  
SNMP System Location  
SNMP System Contact  
None  
None  
SNMP Community  
String/Access Right  
Public—read-only  
Private—read/write  
0.0.0.0  
SNMP Trap Host 1  
SNMP Trap Host 1  
Community String  
Public  
SNMP Trap Host 2  
0.0.0.0  
Public  
SNMP Trap Host 2  
Community String  
Technical specifications 30  
Setting  
Value  
SNMP Authentication  
Traps  
Disabled  
SNMP Link Up/Down  
Traps  
Enabled  
Security IP Network/Mask 0.0.0.0 / 0.0.0.0  
TFTP Server IP Address  
TFTP Port Number  
0.0.0.0  
69  
Firmware upgrade  
File name—none  
File name—none  
Configuration file from  
TFTP server  
Configuration file to TFTP  
server  
File name—none  
PING tool  
Target address—undefined  
Default tries—5  
Trace Route tools  
Serial Port Baud Rate  
Serial Port Data Bit  
Serial Port Parity Bit  
Serial Port Stop Bit  
Serial Port Flow Control  
Default VLAN  
Target address—undefined  
9600  
8
None  
1
None  
Default VLAN (VID=1) with all ports assigned including CPU, STG=1  
NTP State  
Disabled  
0.0.0.0  
NTP Server  
NTP Resync Interval  
GMT Timezone Offset  
1440 minutes  
-06:00  
Daylight Savings Time  
State  
Disabled  
System Up Time  
Current time  
0 days 00 :00 :00  
RTC or NTP (00 :00 :00)  
Date None  
Syslog Host  
0.0.0.0  
0.0.0.0  
7
Syslog Host 2  
Syslog Host Severity  
Syslog Host 2 Severity  
Syslog Console Output  
7
Disabled  
Technical specifications 31  
Setting  
Value  
Log  
0
console—Enabled  
system—Enabled  
mgmt—Enabled  
cli—Enabled  
stp—Enabled  
vlan—Enabled  
ssh—Enabled  
ntp—Enabled  
ip—Enabled  
web—Enabled  
RSA Server Key Autogen  
Interval  
RSA Server Key Autogen  
SSH Server  
Disabled  
On  
SCP-only Administrator  
Password  
admin  
SSH Server Port  
22  
SCP Apply and Save  
RADIUS Server  
Disabled  
Off  
RADIUS Secret  
None  
0.0.0.0  
Primary RADIUS Server  
Secondary RADIUS Server 0.0.0.0  
RADIUS Server Port  
1645  
RADIUS Server Retries  
RADIUS Server Timeout  
3
3
RADIUS Backdoor for  
Telnet Access  
Disabled  
Re-ARP Period in Minutes  
MSTP Di  
10  
sabled  
RSTP  
MSTP Default Mode  
MSTP Region Name  
MSTP Region Version  
MSTP Max Hop Count  
CIST Bridge Max Age  
CIST Bridge Hello Time  
None  
1
20  
20 seconds  
2 seconds  
15 seconds  
CIST Bridge Forward  
Delay  
CIST Bridge Priority  
32768  
CIST MAC Address Aging 300 seconds  
Time  
CIST Port Priority  
CIST Port Path Cost  
MSTP Link Type  
128  
20000  
Auto  
Technical specifications 32  
Setting  
Value  
MSTP Edge Port  
Enabled: ports 1-16  
Off  
TACACS+ Service  
TACACS+ Primary Secret None  
TACACS+ Secondary  
Secret  
None  
Primary TACACS+ Server 0.0.0.0  
Secondary TACACS+  
Server  
0.0.0.0  
TACACS+ Server Port  
49  
TACACS+ Server Retries  
3
TACACS+ Server Timeout 5 seconds  
TACACS+ Backdoor for  
Telnet Access  
Disabled  
IGMP Snooping  
IGMP VLANs  
Disabled  
None  
IGMP Report Timeout  
10 seconds  
255 seconds  
IGMP Multicast Router  
Timeout  
IGMP Robust  
2
Aggregate IGMP Report  
IGMP Fastleave  
IGMP Fastleave VLANs  
IGMP Filtering  
Disabled  
Disabled  
None  
Disabled  
None  
IGMP Filters  
Static Multicast Router Port None  
Uplink Failure Detection  
(UFD)  
Off  
UFD Failure Detection Pair Disabled  
UFD Link To Monitor - Port None  
UFD Link To Monitor -  
Trunk  
None  
UFD Link to Disable - Ports None  
UFD Link To Disable -  
Trunks  
None  
None  
None  
RMON History Group  
Number  
RMON History Interface  
MIB to Monitor  
RMON History Number of 30  
Requested Buckets  
RMON History Polling  
Interval  
1800  
RMON History Owner  
None  
Technical specifications 33  
Setting  
Value  
RMON Event Group  
Number  
None  
RMON Event Description  
RMON Event Type  
None  
None  
None  
RMON Alarm Group  
Number  
RMON Alarm MIB to  
Monitor  
None  
RMON Alarm Interval  
1800  
abs  
RMON Alarm Sample  
Type  
RMON Alarm Type  
either  
0
RMON Alarm Rising  
Threshold  
RMON Alarm Falling  
Threshold  
0
0
RMON Alarm Rising Event  
Index  
RMON Alarm Falling Event 0  
Index  
RMON Alarm Owner  
IP Forwarding  
Null  
Disabled  
Configurable User Name - admin  
admpw  
Configurable User Name - Disabled  
opw  
Configurable User Name - user  
usrpw  
Configurable User Name - Disabled  
UID 1-10  
Uplink Fast  
Disabled  
SIP and DIP  
public  
THASH - enable  
SNMPv1 - Read  
community string:  
SNMPv1 - Write  
community string:  
private  
5
SNMPv1 - SNMP state  
machine timeout:  
SNMPv1 - authentication  
traps:  
Disabled  
Disabled  
Enabled  
Enabled  
SNMPv1 - Uplink Failure  
Detection traps:  
SNMPv1 - link up/down  
traps:  
SNMPv1 - v1/v2 access:  
IGMP off  
Technical specifications 34  
Setting  
Value  
MCAST/BCAST/UCAST off  
SNMPv3 - SNMP access  
SNMPv3 - v1v2 access  
SNMPv3 - adminmd5  
SNMPv3 - adminsha  
SNMPv3 - v1v2only  
read/write enabled  
Enabled  
authentication = md5, privacy = des  
authentication = sha, privacy = des  
authentication = none, privacy = none  
level=authPriv,  
SNMPv3 - admingrp  
users=adminmd5,  
adminsha, rview, wview, nview=iso  
level=noAuthNoPriv,  
SNMPv3 - v1v2grp  
users=v1v2only,  
rview, wview=iso,  
nview=v1v2only  
SNMPv3 - iso  
subtree = 1, included  
subtree=1, included  
SNMPv3 - v1v2only  
subtree=1.3.6.1.6.3.15, excluded  
subtree=1.3.6.1.6.3.16, excluded  
subtree=1.3.6.1.6.3.18, excluded  
21 (not configurable)  
Enabled, (not configurable)  
Disabled  
FTP - port  
Browser upgrade option  
STP Fast  
HTTPS Port  
Disabled  
Port names, VLANs, STP, trunking default settings  
These default settings apply to all ports:  
Speed—Autonegotiate  
PVID—1  
Tag (Y/N)—N  
VLAN Name—Default VLAN  
Port type  
Port number  
Port name  
Downlink1  
Downlink2  
Downlink3  
Downlink4  
Downlink5  
Downlink6  
Downlink7  
Downlink8  
Downlink9  
Downlink10  
STP  
Trunk group  
Server 1  
Disabled  
Disabled  
Disabled  
Disabled  
Disabled  
Disabled  
Disabled  
Disabled  
Disabled  
Disabled  
Server 2  
Server 3  
Server 4  
Server 5  
Server 6  
Server 7  
Server 8  
Server 9  
Server 10  
Technical specifications 35  
 
Port type  
Server 11  
Server 12  
Server 13  
Server 14  
Server 15  
Server 16  
X-Connect 17  
X-Connect 18  
Port number  
Port name  
Downlink11  
Downlink12  
Downlink13  
Downlink14  
Downlink15  
Downlink16  
XConnect1  
XConnect1  
STP  
Trunk group  
Disabled  
Disabled  
Disabled  
Disabled  
Disabled  
Disabled  
Enabled  
Enabled  
1
1
Reserved for future  
use  
19  
Uplink 20  
Uplink 21  
Uplink 22  
Uplink 23  
Uplink 24  
Uplink1  
Uplink2  
Uplink3  
Uplink4  
Uplink5  
Enabled  
Enabled  
Enabled  
Enabled  
Enabled  
Physical and environmental specifications  
Category  
Specification  
DC inputs  
12VDC: 2.0A maximum per switch  
25 W maximum per switch  
Power  
consumption  
Operating  
10° to 40° C (50° to 104° F)  
-40° to 70° C (-40° to 158° F)  
5% to 95% RH noncondensing  
5% to 95% RH noncondensing  
temperature  
Storage  
temperature  
Operating  
humidity  
Storage humidity  
Switch dimensions 267.7 x 192.79 x 27.94 mm (10.5 x 7.5 x 1.1 in.)  
Weight  
Safety  
1.8 Kg (3.97 lbs.)  
TUV to UL 60950-1, and CAN/CSA C22.2 No.  
60950-1 and to EN 60950-1  
CE Marking  
RoHS 5/6 compliant  
Performance specifications  
Category  
Specification  
Transmission  
method  
Store-and-forward  
Memory  
128 MB main, 16 MB flash, and 1 MB shared packet  
buffer memory per switch  
Technical specifications 36  
   
Category  
Specification  
MAC address  
table size  
8 KB per switch  
Packet forwarding 1,488,095 packets per second with 64 byte packets per  
rate port (for 1000 Mb/s)  
Maximum external 5 X 1 GB port = 5 X 1,488,095 = 7,440,475 pps per  
port packet  
switch  
16 : 5  
forwarding rate  
Best downlink  
external port  
packet forwarding  
rate ratio  
Interswitch x-  
connects across  
enclosure  
2 X 1 GB ports bundled in Port Trunk of 2 GB size  
Automatic update  
backplane  
MAC address  
learning  
Forwarding table  
age time  
Maximum age: 1 to 1,000,000 seconds  
Default: 300 seconds  
Technical specifications 37  
Performing a serial download  
In this section  
Introduction ........................................................................................................................................... 38  
Serial upgrade of operating system firmware procedure ............................................................................. 40  
Introduction  
Perform a serial download of the switch operating system firmware, or boot code firmware if upgrading a  
switch directly from any existing OS or boot code images.  
This procedure requires:  
A computer running terminal emulation software  
A standard null modem cable with a female DB-9 connector  
A switch OS firmware and/or boot code images  
Serial upgrade of boot code firmware image  
procedure  
To perform a serial upgrade of the switch boot code firmware image, usually named  
pGbE2c_b_100.bin:  
1.  
2.  
Using the null modem, connect the console port of the switch to the serial port of a PC that supports  
XModem/1K XModem.  
Start HyperTerminal (part of Microsoft Windows) or equivalent terminal emulation application  
(depending on the computer operating system), and set the parameters for the terminal emulation  
console:  
Parameter  
Value  
9600  
8
Baud rate  
Date bits  
Parity None  
Stop bits  
1
Flow control  
None  
3.  
Power on the switch.  
Performing a serial download 38  
     
4.  
Hold down the Shift key and press the D key repeatedly during the Memory Test, until this message  
appears:  
NOTE: To perform serial downloads at 57600 baud rate, press the Shift-F keys. To perform  
serial downloads at 115200 baud rate, press the Shift-D keys.  
5.  
After the message in Step 4 appears, reconfigure the terminal emulation console using these  
parameters.  
Parameter  
Value  
115200  
8
Baud rate  
Data bits  
Parity None  
Stop bits  
1
Flow control  
None  
6.  
Press the Enter key several times on the PC that is connected to the console port of the switch. When  
the console port is successfully communicating with the PC, indicating readiness for image transfer,  
continuous C's appear:  
7.  
8.  
Be sure that the new switch boot code firmware file is available on the computer. This file can be  
downloaded from the CD that is shipped with the switch or from the HP website  
Select <Transfer-Send File> from the menu and choose these options in the Send File window:  
The Send File window displays progress of the file transfer. The file transfer might take up to seven  
minutes.  
NOTE: Although slower, XModem also works if 1K MODEM is not used.  
9.  
After completing the transfer, a message displays how many bytes transferred, followed by another  
message displaying the status of image extraction. Do not power cycle the switch during this  
process. After extracting the image, it is updated to flash and a message with a progress indicator  
displays as shown.  
Performing a serial download 39  
CAUTION: Do not power off the switch until the message: "Change your baud rate to 9600  
bps and power cycle the switch," is displayed, otherwise, the switch will be inoperable.  
10. Change the baud rate to 9600 and power off the switch, wait for a few seconds, and power on the  
switch.  
The switch boots with the new version of the boot code image that was just downloaded.  
Serial upgrade of operating system firmware  
procedure  
To perform a serial upgrade of the switch operating system firmware image, usually named  
pGbE2c_100.bin:  
1.  
2.  
Using the null modem cable, connect the console port of the switch to the serial port of a PC that  
supports XModem/1K XModem.  
Start HyperTerminal (part of Microsoft Windows) or equivalent terminal emulation application  
(depending on the computer operating system) and set the parameters for terminal emulation  
console:  
Parameter  
Value  
9600  
8
Baud rate  
Data bits  
Parity None  
Stop bits  
1
Flow control  
None  
3.  
4.  
Power on the switch.  
Hold down the Shift key and press the D key repeatedly during the Memory Test, until this message  
appears:  
Performing a serial download 40  
 
NOTE: To perform serial downloads at 57600 baud rate, press the Shift-F keys. To perform  
serial downloads at 115200 baud rate, press the Shift-D keys.  
5.  
After the message in Step 4 appears, reconfigure the terminal emulation console using these  
parameters.  
Parameter  
Value  
115200  
8
Baud rate  
Data bits  
Parity None  
Stop bits  
1
Flow control  
None  
6.  
Press the Enter key several times on the PC that is connected to the console port of the switch. When  
the console port is successfully communicating with the PC, indicating readiness for image transfer,  
continuous C's appear:  
7.  
8.  
Be sure that the new switch operating system firmware file is available on the computer. This file can  
be downloaded from the CD that is shipped with the switch or from the HP website  
Select <Transfer-Send File> from the menu and choose these options in the Send File window:  
The Send File window displays the progress of the file transfer. The file transfer might take up to five  
minutes.  
NOTE: Although slower, XModem also works if 1K MODEM is not used.  
9.  
After completing the transfer, a message displays how many bytes transferred, followed by another  
message displaying the status of image extraction. Do not power cycle the switch during this  
process.  
CAUTION: Do not power off the switch until the message: "Change your baud rate to 9600  
bps and power cycle the switch," is displayed, otherwise, the switch will be inoperable.  
10. After extracting the image, the system prompts to select which current operating system image  
(image1 or image2) needs to be updated by the new operating system image. It also provides an  
option (n) not to update any and to quit the update procedure.  
Performing a serial download 41  
Depending on the selection, 1 or 2, the system updates image1 or image2 on the flash and a  
message with a progress indicator displays as shown below. If selecting n, the system aborts the  
update procedure and prompts to reset the baud rate and power cycle the switch.  
-or-  
-or-  
11. Change the baud rate to 9600 and power off the switch. Wait for a few seconds, and power on the  
switch.  
During bootup the switch the following prompt appears:  
To use the other operating system image, press the Ctrl-o keys.  
Performing a serial download 42  
SNMP MIBs support  
In this section  
SNMP Manager software........................................................................................................................ 43  
Supported MIBs ..................................................................................................................................... 44  
Supported traps ..................................................................................................................................... 44  
MIB overview  
Management and statistics information is stored in the switch in the MIB. The switch supports several  
standard MIBs. Values for MIB objects are retrieved with any SNMP-based network management  
software.  
In addition to the standard MIBs, the switch also supports its own proprietary enterprise MIB as an  
extended MIB. The proprietary MIB is retrieved by specifying the MIB OID at the network manager  
station.  
MIB values are either read-only or read/write variables.  
Read-only MIB variables are constants that are programmed into the switch or variables that change  
while the switch is in operation. Examples of read-only constants include the number and types of  
ports. Examples of read-only variables are the statistics counters, such as the number of errors that  
have occurred or how many kilobytes of data have been received and forwarded through a port.  
Read/write MIB variables are usually related to user-customized configurations. Examples include  
the IP address of the switch, Spanning Tree Algorithm parameters, and port status.  
SNMP Manager software  
Using third-party vendor SNMP software to manage the switch allows access to proprietary enterprise  
MIBs for the switch. The MIBs are found in the utilities on the HP website  
If the software provides functions to browse or modify MIBs, the MIB values (if the MIB attributes permit  
the write operation) are changeable. This process can be quite involved, because the MIB OIDs (available  
in the MIB files) must be used and retrieved one by one.  
Use an SNMP manager, such as HP OpenView Network Node Manager or HP Systems Insight Manager,  
to access the enterprise-specific MIBs. Compile the MIBs into the MIB database and then use a MIB  
browser to navigate through them. For detailed information, access the individual descriptions of each  
MIB or see the documentation that came with the SNMP manager software.  
The switch SNMP agent supports SNMP Version 1. Security is provided through SNMP community strings.  
The default community strings are "public" for SNMP GET operation and "private" for SNMP SET  
operation.  
Users can specify up to two trap hosts for receiving SNMP traps. The agent sends the SNMP trap to the  
specified hosts when appropriate. Traps are not sent if there is no host specified.  
SNMP MIBs support 43  
     
Supported MIBs  
The SNMP agent for the switch supports these MIBs:  
bt4Network.mib  
bt4Physical.mib  
bt4Switch.mib  
bt4trap.mib  
cpqhost.mib  
cpqsinfo.mib  
cpqrack.mib  
hpswitchpl.mib  
rfc1213.mib  
rfc1493.mib  
rfc1573.mib  
rfc1643.mib  
rfc1757.mib  
rfc1907.mib  
rfc2037.mib  
rfc2571.mib  
rfc2572.mib  
rfc2573.mib  
rfc2574.mib  
rfc2575.mib  
rfc2576.mib  
Supported traps  
The switch SNMP agent supports these traps:  
bt4trap.mib traps  
o bt4SwDefGwUp  
o bt4SwDefGwDown  
o bt4SwDefGwInService  
o bt4SwDefGwNotInService  
o bt4SwLoginFailure  
o bt4SwTempExceedThreshold  
o bt4SwApplyComplete  
o bt4SwSaveComplete  
o bt4SwFwDownloadSucess  
o bt4SwFwDownloadFailure  
o bt4SwTempReturnThreshold  
o bt4SwUfdfoLtMFailure  
o bt4SwUfdfoLtMUP  
SNMP MIBs support 44  
   
o bt4SwUfdfoGlobalEna  
o bt4SwUfdfoGlobalDis  
o bt4SwUfdfoLtDAutoEna  
o bt4SwUfdfoLtDAutoDis  
rfc1215.mib traps  
o coldStart  
o warmStart  
o linkDown  
o linkUp  
o authenticationFailure  
o egpNeighborLoss  
rfc1493.mib traps  
o newRoot  
o topologyChange  
rfc1757.mib traps  
o risingAlarm  
o fallingAlarm  
SNMP MIBs support 45  
Electrostatic discharge  
In this section  
Grounding methods to prevent electrostatic discharge ................................................................................ 46  
Preventing electrostatic discharge  
To prevent damaging the system, be aware of the precautions you need to follow when setting up the  
system or handling parts. A discharge of static electricity from a finger or other conductor may damage  
system boards or other static-sensitive devices. This type of damage may reduce the life expectancy of the  
device.  
To prevent electrostatic damage:  
Avoid hand contact by transporting and storing products in static-safe containers.  
Keep electrostatic-sensitive parts in their containers until they arrive at static-free workstations.  
Place parts on a grounded surface before removing them from their containers.  
Avoid touching pins, leads, or circuitry.  
Always be properly grounded when touching a static-sensitive component or assembly.  
Grounding methods to prevent electrostatic discharge  
Several methods are used for grounding. Use one or more of the following methods when handling or  
installing electrostatic-sensitive parts:  
Use a wrist strap connected by a ground cord to a grounded workstation or computer chassis. Wrist  
straps are flexible straps with a minimum of 1 megohm 10 percent resistance in the ground cords.  
To provide proper ground, wear the strap snug against the skin.  
Use heel straps, toe straps, or boot straps at standing workstations. Wear the straps on both feet  
when standing on conductive floors or dissipating floor mats.  
Use conductive field service tools.  
Use a portable field service kit with a folding static-dissipating work mat.  
If you do not have any of the suggested equipment for proper grounding, have an authorized reseller  
install the part.  
For more information on static electricity or assistance with product installation, contact an authorized  
reseller.  
Electrostatic discharge 46  
     
RJ-45 pin specification  
In this section  
Standard RJ-45 receptacle/connector....................................................................................................... 47  
Standard RJ-45 receptacle/connector  
When connecting the switch to a switch, bridge, or hub, an Ethernet cable is necessary.  
The table indicates the pin number and wire color assignments for the switch-to-network adapter card  
connection, and the Ethernet cable for the switch-to-switch, switch-to-hub, or switch-to-bridge connection.  
Contact  
Media direct interface  
signal  
Color match  
1
Tx + (transmit)  
Tx - (transmit)  
Rx + (receive)  
used  
White/Orange  
Orange/White  
White/Green  
Blue/White  
2
3
4 Not  
5 Not  
6
used  
White/Blue  
Rx - (receive)  
used  
Green/White  
White/Brown  
Brown/White  
7 Not  
8 Not  
used  
The table provides the same information for the Gigabit over Copper ports.  
Contact  
Media direct interface  
signal  
Color match  
1 BI_DA+  
2 BI_DA-  
3 BI_DB+  
4 BI_DC+  
5 BI_DC-  
6 BI_DB-  
7 BI_DD+  
8 BI_DD-  
White/Orange  
Orange/White  
White/Green  
Blue/White  
White/Blue  
Green/White  
White/Brown  
Brown/White  
RJ-45 pin specification 47  
   
Troubleshooting  
In this section  
Health LED on the switch is not on............................................................................................................ 48  
destination device .................................................................................................................................. 51  
Cannot connect to the switch remotely using the Web interface................................................................... 52  
VLANs .................................................................................................................................................. 52  
The download fails after starting to download the firmware file ................................................................... 54  
The switch configuration is corrupt ........................................................................................................... 54  
Forgotten administrator user name and password  
that was configured on the switch  
Action:  
Call HP technical support at 1-800-652-6672, or call a service representative to get a backdoor  
password.  
Health LED on the switch is not on  
Action:  
The switch is not seated properly. Be sure that the switch is inserted completely and seated properly.  
Troubleshooting 48  
     
The server blade enclosure is not powered up. Be sure that the server blade enclosure is powered up  
and all the power connections are intact.  
There is a faulty LED. Check the console to see if the switch is booted.  
The switch fuse is blown. Send for repair.  
Health LED on the switch stays amber for more than  
30 seconds and switch does not boot  
Action:  
The Standby Mode Timeout function is malfunctioning. Force the switch to reboot by pressing the Reset  
button.  
No link LED appears, even after plugging the  
Category 5 cable in the RJ-45 connector of the  
external port  
Action:  
The cable is not properly plugged in. Check the cable at both ends to ensure that it is plugged in  
and seated properly.  
The cable or connector heads are faulty. Replace the cable with another tested cable.  
The RJ-45 connector on the switch or LED is faulty.  
o After checking and replacing the cable, if no link LED displays, check whether the port is  
transferring data. If yes, the LED is faulty. If no, it could be a faulty RJ-45 connector. Call a  
service representative.  
o This could be caused by using a crossover cable instead of a straight through cable.  
Cannot access the switch serial console interface  
using null modem connection from a PC Terminal  
Emulation Program  
Action:  
The null modem cable is faulty. Be sure the null modem cable, provided by HP with this hardware,  
was used.  
The connection settings do not match the switch serial settings. Be sure that the PC Terminal  
Emulation session settings match the switch serial settings.  
Troubleshooting 49  
     
Error message that the switch failed to complete the  
system self-testing appears on the serial console  
screen  
Action:  
The system diagnostic tests failed. Note the reason for the failure from the serial console screen message  
and call a service representative.  
The switch fails to get its IP settings from the BOOTP  
server, even though by default it is configured for  
BOOTP  
Action:  
The switch is not connected properly to the network. Check the cable and connections and be sure  
that there is network connectivity between the switch and the BOOTP server.  
The BOOTP server is not available on the network or VLAN that is attached to the switch  
management port. Be sure that the BOOTP server is present on the network or VLAN attached to the  
switch.  
The BOOTP server cannot offer IP settings to the switch because no IP addresses are available. Add  
additional IP addresses as necessary.  
The switch timed out its request for IP settings. Reset the switch.  
The keyboard locks up when using HyperTerminal to  
log on to the switch through the console interface  
Action:  
Scroll lock is on. Press the Scroll Lock key on the keyboard and be sure that the scroll lock is off.  
Cannot connect to the switch console interface  
remotely using Telnet  
Action:  
The switch IP address is not configured or correct.  
o From the serial console interface, be sure that the switch IP address is configured and valid on  
the network.  
o Use the correct IP address to establish the Telnet connection with the switch.  
The setting allowing access to the switch using the Telnet interface is disabled. From the serial  
console interface, be sure that the Telnet interface is enabled.  
Troubleshooting 50  
       
The management network address/mask (if used) does not contain the IP address of the  
management station. From the serial console interface, be sure that the Management Network  
Address/Mask contains the IP address of the management station.  
Password is not accepted by the switch using the  
remote console interface immediately after a reboot  
Action:  
The switch is still working on network convergence. Wait up to 10 seconds for the password to be  
accepted.  
Cannot connect to the switch console interface  
remotely using SSH  
Action:  
The switch IP address is not configured or correct.  
o From the serial console interface, be sure that the switch IP address is configured and valid on  
the network.  
o Use the correct IP address to establish the SSH connection with the switch.  
The setting allowing access to the switch using the SSH interface is disabled.  
From the serial console interface, be sure that the SSH interface is enabled and all the settings are  
configured correctly.  
The management network address/mask (if used) does not contain the IP address of the  
management station. From the serial console interface, be sure that the management network  
address/mask contains the IP address of the management station.  
Cannot connect to the switch SNMP interface  
Action:  
The switch IP address is not configured or correct.  
o From the serial console interface, be sure that the switch IP address is configured and valid on  
the network.  
o Use the correct IP address to establish the SNMP connection with the switch.  
The management network address/mask (if used) does not contain the IP address of the  
management station. From the serial console interface, be sure that the management network  
address/mask contains the IP address of the management station.  
The port activity LEDs continuously indicate activity  
after connecting more than one port to another  
switch or destination device  
Action:  
Troubleshooting 51  
       
Because there are multiple links across this device and the destination device, they form loops, which  
cause broadcast storms. Enable STP for multiple links. This setting prevents loops and maintains standby  
links for resilience in case of primary link failure.  
Cannot connect to the switch remotely using the Web  
interface  
Action:  
The switch IP address is not configured or correct.  
o From the serial console interface, be sure that the switch IP address is configured and valid on  
the network.  
o Use the correct IP address to establish the Web connection with the switch.  
Access to the switch using the Web interface is disabled. From the serial console interface, be sure  
that the Web interface is enabled.  
The Proxy server settings are configured on the Internet browser and the proxy server does not know  
the switch IP address. Disable the manual proxy settings on the Web browser and let it automatically  
find Web servers using the IP address.  
The management network address/mask (if used) does not contain the IP address of the  
management station. From the serial console interface, be sure that the management network  
address/mask contains the IP address of the management station.  
Cannot enable a port in multiple VLANs while  
configuring VLANS  
Action:  
A port is part of only one VLAN unless the port is a tagged port. Be sure that the port is enabled as a  
tagged port.  
The switch does not let the user enable two adjacent  
ports into two different VLANs while assigning the  
ports to VLANs  
Action:  
The ports are two adjacent ports that are bundled in a Port Trunk. Two ports that are assigned to a Port  
Trunk cannot be assigned to two different VLANs. Either break the trunk to assign it two different VLANs  
or assign the ports to one VLAN.  
Troubleshooting 52  
     
While using TFTP to download firmware, the switch  
fails to connect to the TFTP server, or after connection  
the download fails  
Action:  
The TFTP server is not available to connect to or there is connectivity failure between the switch and  
TFTP server.  
o Be sure that the IP address of the TFTP server is correct.  
o Be sure that the TFTP server exists on the same network and VLAN as the switch.  
o Be sure that the TFTP server can be pinged from the switch and vice versa.  
The firmware file is not found on the TFTP server. The file name could be wrong.  
o Be sure that a valid firmware file exists on the TFTP server to download to the switch.  
o On the switch, check the file name configured to download.  
The TFTP server was started with a configured directory. The switch must be configured using the full  
path name, if it is not in the directory specified in the TFTP server.  
The switch fails to connect to the TFTP server while  
using TFTP to download or upload a configuration  
file, or after connection the download or upload fails  
Action:  
The TFTP server is not available to connect or there is a connectivity failure between the switch and  
the TFTP server.  
o Be sure that the TFTP server exists on the same network or VLAN as that of the switch.  
o Be sure that the TFTP server can be pinged from the switch and vice versa.  
o Be sure that the IP address of the TFTP server is correct.  
The configuration file is not found on the TFTP server. The file name could be wrong.  
o Be sure that a valid configuration file exists on the TFTP server to download to the switch.  
o On the switch, check the file name configured to download or upload.  
The TFTP server was started with a configured directory. The switch must be configured using the full  
path name, if it is not in the directory specified in the TFTP server.  
Troubleshooting 53  
   
The console screen displays a message to change  
the baud rate for the terminal emulation session for  
XModem transfer after forcing the switch into the  
download mode, and does not display CCCC...  
Action:  
The terminal emulation session baud rate does not match the switch serial console baud rate in the  
download mode. Change the baud rate of the terminal emulation session to match the switch serial  
console baud rate in the download mode.  
IMPORTANT: The baud rate for the switch serial console in the download mode and runtime  
mode are two separate settings.  
The download fails after starting to download the  
firmware file  
Action:  
The firmware file is not the correct one or is corrupt. Obtain the latest firmware file that is specified for this  
switch.  
The switch configuration is corrupt  
Action:  
An error was made when saving the switch configuration. Reboot the switch and reload the factory  
settings. This action clears all settings and restores them to the initial values that were present when the  
switch was purchased. See the HP GbE2c Ethernet Blade Switch for c-Class BladeSystem Command  
Reference Guide for more information.  
After reloading the factory settings, reconfigure the switch settings.  
Troubleshooting 54  
     
Acronyms and abbreviations  
AAA  
authentication, authorization, and accounting  
BBI  
browser-based interface  
BOOTP  
Bootstrap Protocol  
CLI  
Command Line Interface  
CPU  
central processing unit  
CSMA/CD  
Carrier Sense Multiple Access with Collision Detection  
DNS  
domain name system  
FDB  
forwarding database  
FTP  
file transfer protocol  
GMT  
Greenwich mean time  
HTTP  
hypertext transfer protocol  
HTTPS  
hypertext transfer protocol secure sockets  
Acronyms and abbreviations 55  
 
IEEE  
Institute of Electrical and Electronics Engineers  
IGMP  
Internet Group Management Protocol  
IP  
Internet Protocol  
LACP  
Link Aggregation Control Protocol  
LAN  
local-area network  
MAC  
medium access control  
MAU  
media attachment unit  
MDI  
medium dependent interface  
MDI-X  
medium dependent interface-crossover  
MIB  
management information base  
MSTP  
Multiple Spanning Tree Protocol  
NAS  
network access server  
NIC  
network interface controller  
NTP  
network time protocol  
Acronyms and abbreviations 56  
NVRAM  
non-volatile memory  
OID  
object identifier  
OS  
operating system  
OSI  
Open Systems Interconnection  
OSPF  
open shortest path first  
POST  
Power-On Self Test  
PXE  
Preboot Execution Environment  
RADIUS  
Remote Authentication Dial-In User Service  
RAS  
remote access service  
RFC  
request for comments  
RIP  
routing information protocol  
RMON  
remote monitoring  
RSTP  
Rapid Spanning Tree Protocol  
SCP  
Secure Copy  
Acronyms and abbreviations 57  
SFP  
small form-factor pluggable  
SNMP  
Simple Network Management Protocol  
SSH  
Secure Shell  
STP  
Spanning Tree Protocol  
TACACS+  
Terminal Access Controller Access Control System Plus  
TFTP  
Trivial File Transfer Protocol  
UDP  
User Datagram Protocol  
UFD  
uplink failure detection  
UTP  
unshielded twisted pair  
VID  
VLAN ID  
VLAN  
virtual local-area network  
VRRP  
virtual redundant router protocol  
Acronyms and abbreviations 58  
Index  
A
G
access rights, overview 18  
accessing the switch serial console interface,  
troubleshooting 52  
additional references 6  
architecture 9  
grounding methods 49  
H
Health LED, troubleshooting 51, 52  
HyperTerminal, troubleshooting 53  
Auto-MDI/MDIX 15  
auto-negotiation of duplex mode and speed 15  
I
B
IEEE 802.1 Q-based Virtual Local Area Network 11  
IGMP snooping 14  
installation 17  
boot code firmware image, performing a serial  
upgrade 40  
BOOTP server, troubleshooting 53  
Bootstrap Protocol (BOOTP) 13  
BSMI notice 28  
installing the switch 17  
J
Japanese notice 28  
jumbo frames 14  
C
Canadian notice 27  
K
configuration and management of switch 8, 22  
configuration, troubleshooting 57  
configuring multiple switches, using a configuration  
file 20  
configuring multiple switches, using scripted CLI  
commands 20  
Korean notices 29  
L
laser compliance 29  
Layer 2 switching 10  
Layer 3 switching 11  
link LED, troubleshooting 52  
load balancing 12  
configuring the switch, manually 19  
D
default configuration 17, 31  
default settings 31  
logging on to the switch 22  
diagnostic tools 9  
duplex mode, auto-negotiation of 15  
N
Network Time Protocol (NTP) 13  
E
O
electrostatic discharge 49  
operating system firmware, performing a serial  
upgrade 42  
enterprise class performance 6  
overview, product 6  
F
features 6, 16  
firmware 23  
P
password, troubleshooting 51, 54  
firmware with redundant images 15  
Index 59  
 
performing a serial download 40  
planning switch configuration 17  
port mapping 10  
port mirroring 12  
port trunking 12  
Terminal Access Controller Access Control System  
Plus (TACACS+) 13  
TFTP, troubleshooting 56  
Trivial File Transfer Protocol (TFTP) 12  
troubleshooting 51  
R
U
redundancy 8, 10, 15  
upgrading the switch 25  
redundant crosslinks 10  
redundant images in firmware 15  
redundant paths to server bays 10  
regulatory compliance notices 27, 28  
Remote Authentication Dial-in User Service  
(RADIUS) 13  
V
VLANs, troubleshooting 55, 56  
X
replacing an existing switch 25  
replacing the switch 25  
XModem 14  
RJ-45 pin specification 50  
RJ-45, standard connector 50  
runtime switching software, default settings 31  
S
Secure Copy (SCP) 14  
Secure Shell (SSH) 14  
security features 18  
serial console interface, troubleshooting 52, 53  
serial download, performing 40  
Simple Network Management Protocol (SNMP) 12  
SNMP interface, troubleshooting 54  
SNMP Manager Software 46  
SNMP MIBs support 46  
SNMP MIBs, supported 47  
SNMP traps, supported 47  
Spanning Tree Protocol (STP) 11  
specifications, environmental 38  
specifications, performance 39  
specifications, physical 38  
specifications, technical 30  
speed, auto-negotiation of 15  
SSH, troubleshooting 54  
store and forward switching scheme 12  
supported SNMP MIBs 47  
supported SNMP traps 47  
supported technologies 10  
switch redundancy 8  
switch self-test, troubleshooting 53  
T
technical specifications 30  
Telnet, troubleshooting 53  
Index 60  

Whirlpool Acs602xt User Manual
Soleus Air Air Conditioner Sg Ttw 14hc User Manual
Schumacher Sc 2500a User Manual
Samsung Aw1403m User Manual
MAKITA UC4041A User Manual
LG LW1022IVSM User Manual
HP 5550 User Manual
DISHLEX DX 203 User Manual
CANON POWERSHOT SX510 HS User Manual
BLACK DECKER GC2400 User Manual