HP 6127XLG Blade Switch Series

Installation Guide

Part number: 797699-001

Document version: 5W100-20150602
Legal and notice information

© Copyright 2015 Hewlett-Packard Development Company, L.P.

No part of this documentation may be reproduced or transmitted in any form or by any means without
prior written consent of Hewlett-Packard Development Company, L.P.
The information contained herein is subject to change without notice.
HEWLETT-PACKARD COMPANY MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS
MATERIAL, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR A PARTICULAR PURPOSE. Hewlett-Packard shall not be liable for errors contained
herein or for incidental or consequential damages in connection with the furnishing, performance, or
use of this material.
The only warranties for HP products and services are set forth in the express warranty statements
accompanying such products and services. Nothing herein should be construed as constituting an
additional warranty. HP shall not be liable for technical or editorial errors or omissions contained
herein.
Contents

Installing the blade switch ··········································································································································· 1 

Preparing for installation ·················································································································································· 1 
Installing and removing the blade switch ······················································································································· 1 
Installing the blade switch ······································································································································· 2 
Removing the blade switch······································································································································ 3 
Connecting the blade switch to the network ·················································································································· 3 
Precautions ································································································································································ 3 
Connecting the optical fibers ·································································································································· 3 

Accessing the blade switch for the first time ·············································································································· 5 

Logging in through the OA module ································································································································ 5 
Logging in through the console port ······························································································································· 5 
Setting up the configuration environment ·············································································································· 6 
Setting terminal parameters····································································································································· 6 
Configuring the blade switch ··········································································································································· 7 
Configuring an authentication method ·················································································································· 7 
Configuring the basic network settings ·················································································································· 7 
Configuration example ············································································································································ 8 

Setting up an IRF fabric ··············································································································································· 9 

Planning IRF fabric setup ·················································································································································· 9 
Determining the number of IRF member devices ···································································································9 
Identifying the master switch and planning IRF member IDs ··············································································· 9 
Planning IRF topology and connections ················································································································· 9 
Configuring basic IRF settings······································································································································· 10 
Connecting the physical IRF ports ································································································································ 10 
Accessing the IRF fabric to verify the configuration ··································································································· 10 

Troubleshooting ·························································································································································· 12 

Troubleshooting methods··············································································································································· 12 
Collecting log and operating information ··················································································································· 12 
Collecting common log messages ······················································································································· 13 
Collecting diagnostic log messages ···················································································································· 13 
Collecting operating statistics ······························································································································ 14 
Failures at startup ··························································································································································· 15 
No display on the configuration terminal ··········································································································· 15 
Garbled display on the configuration terminal ·································································································· 15 
Failures during operation ·············································································································································· 16 
IRF member device failure ············································································································································· 16 
Software upgrade failure ·············································································································································· 17 
Hardware failures ·························································································································································· 17 
Interface failure······························································································································································· 18 

Support and other resources ····································································································································· 19 

Contacting HP ································································································································································ 19 
Subscription service ·············································································································································· 19 
Related information ························································································································································ 19 
Documents ······························································································································································ 19 
Websites································································································································································· 19 
Conventions ···································································································································································· 20 

i
Appendix Technical specifications ··························································································································· 22 
Front view········································································································································································ 22 
Port numbering ······························································································································································· 23 
LEDs ················································································································································································· 24 
Ports ················································································································································································· 24 
Console port ·························································································································································· 24 
SFP+ port ································································································································································ 25 
QSFP+ port ···························································································································································· 26 
Cables ············································································································································································· 27 
Fiber connector ······················································································································································ 28 
SFP+ cable ····························································································································································· 28 
QSFP+ cable ·························································································································································· 29 
QSFP+ to SFP+ cable ············································································································································ 29 

Index ··········································································································································································· 30 

ii
Installing the blade switch

The HP 6127XLG Blade Switch Series includes the models in Table 1.

Table 1 HP 6127XLG Blade Switch Series models

Product code HP description RMN Alias

787635-B21 HP 6127XLG Ethernet Blade Switch HSTNS-BC65-N HP 6127XLG

HP 6127XLG Ethernet Blade Switch with

787635-B22 HSTNS-BC65-N HP 6127XLG TAA
TAA

IMPORTANT:
For regulatory identification purposes, the switches are assigned regulatory model numbers (RMNs).
These regulatory numbers should not be confused with the marketing names HP 6127XLG and HP
6127XLG TAA, or the product codes 787635-B21 and 787635-B22.

You can install the blade switch in the HP BladeSystem c7000 enclosure. The installation position in the
enclosure in this document is only for illustration. For more information, see HP BladeSystem Enclosure
Setup and Installation Guide.

Preparing for installation

WARNING!
• The blade switch is Class 1 laser device. Do not stare into any fiber ports when the blade switch has
power. The laser light emitted from the optical fiber might hurt your eyes.
• To avoid any equipment damage or bodily injury caused by improper use, follow the enclosure safety
recommendations. For more information, see HP BladeSystem Enclosure Setup and Installation Guide.

CAUTION:
Take ESD measures to avoid damaging the components. For more information, see HP BladeSystem
Enclosure Setup and Installation Guide.

Installing and removing the blade switch

IMPORTANT:
• Do not use excessive force during the installation and removal processes.
• Remove the cables before removing the blade switch.
• If the blade switch does not install easily, make sure it is correctly oriented.
• To prevent dust from entering the system, install the interconnect blank into the interconnect bay after
removing the blade switch.

1
Installing the blade switch
1. Wear an ESD wrist strap and make sure it makes good skin contact and is reliably grounded.
2. Remove the interconnect blank from the slot.
Keep the removed interconnect blank for future use.
3. Unpack the blade switch.
4. Press the release tab (see callout 1 in Figure 1) and then pull the ejector lever to the open position
(see callout 2 in Figure 1).
Figure 1 Opening the ejector lever

5. Slide the blade switch into the interconnect bay (see callout 1 in Figure 2) until it touches the
backplane.
6. Push the ejector lever to the closed position. (See callout 2 in Figure 2).
Figure 2 Sliding the blade switch into the interconnect bay

2
 7. Verify that the Health LED is green after the blade switch starts up.
If the Health LED is not green, check the installation.
8. Choose correct cables to connect to the ports on the blade switch.
For more information about ports, see "Ports." For more information about cable installation, see
"Connecting the blade switch to the network."

Removing the blade switch

1. Wear an ESD wrist strap and make sure it makes good skin contact and is reliably grounded.
2. Press the release tab to open the ejector lever.
3. Pull the ejector lever outwards slowly to take out the blade switch.

Connecting the blade switch to the network

Precautions
• Make sure the fiber connector and fiber type match the transceiver module type.
• The fiber ports have shielded covers. Remove the shielded covers before using the fiber ports and
keep them safely. Fiber interfaces must be installed with shielded covers when they are not in use.
• Fiber connectors must be protected under safe and reliable outer packing, and be fitted with dust
caps. Fiber connectors must be installed with dust caps when they are not in use. Take care not to
scratch their end face. Replace the dust cap if it is loose or polluted.
• Before connecting a fiber, use dust free paper and absolute alcohol to clean the end face of the
fiber connector. You can brush the end face only in one direction. You also need to brush the end
face of the fiber port.
• Never bend or curve a fiber when connecting it.
• For the QSFP+ module, you do not need to differentiate between the transmitter (TX) and receiver
(RX) ports. For other types of transceiver modules, the Tx port on one end must connect to the RX port
on the other end.

Connecting the optical fibers

WARNING!
To avoid injury to your eyes, do not stare at the optical interfaces and optical fiber connectors when
connecting optical fibers.

You can install a transceiver module in a fiber port on the blade switch and then plug the fiber connector
to the transceiver module. For more information about installing the transceiver module, see Pluggable
SFP[SFP+][XFP] Transceiver Modules Installation Guide and Pluggable QSFP+ Transceiver
Modules/Cables Installation Guide.
To install a transceiver module into the port on the blade switch and the peer device:
1. Remove the dust cover of the fiber connector, and clean the end of the fiber connector.
2. Remove the dust plug of the transceiver module, plug one end of the optical fiber into the
transceiver module, and plug the other end into the transceiver module in the peer device.

3
 Figure 3 Using LC optical fiber connectors to connect transceiver modules

LC plug

SFP module

Figure 4 Using MPO optical fiber connectors to connect transceiver modules

MPO plug

QSFP+ module

3. Verify the port LEDs for correct connection.

For more information about LED status, see "LEDs."
After you connect the blade switch to the network, use the ping or tracert command to test network
connectivity. For more information about these two commands, see HP 6127XLG Blade Switch Series
Network Management and Monitoring Command Reference.

4
Accessing the blade switch for the first time

You can access the blade switch either by logging in through the OA module or through the console
port.

Logging in through the OA module

To log in to the blade switch through the HP BladeSystem Onboard Administrator (OA) module:
1. Use a serial cable to connect the terminal (for example, a PC) to the serial port of the OA module.
2. Turn on the PC, run a terminal emulator program (for example, Windows XP HyperTerminal) on
the PC, and set terminal parameters as follows:
{ Bits per second—9,600.
{ Data bits—8.
{ Parity—None.
{ Stop bits—1.
3. Press Enter and the login information appears.
4. Enter the username and password.
OA prompt information appears on the login interface.
5. Enter the connect interconnect <bay_number> command, where the bay number argument
specifies the slot number of the blade switch.
6. Press Enter.
When the command line prompt appears, you can configure the switch. For more information
about the configuration, see "Configuring the blade switch."

Logging in through the console port

When you access the blade switch through the console port, you must use a console cable (see Figure 5)
to connect a console terminal, for example, a PC, to the console port on the blade switch.
A console cable is an 8-core shielded cable, with a crimped RJ-45 connector at one end for connecting
to the console port of the blade switch, and a DB-9 female connector at the other end for connecting to
the serial port on the console terminal.
Figure 5 Console cable

5
 Table 2 Console port signaling and pinout

RJ-45 Signal DB-9 Signal

1 RTS 8 CTS

2 DTR 6 DSR

3 TXD 2 RXD

4 SG 5 SG

5 SG 5 SG

6 RXD 3 TXD

7 DSR 4 DTR

8 CTS 7 RTS

Setting up the configuration environment

To connect a terminal, for example, a PC, to the blade switch:
1. Plug the DB-9 female connector of the console cable in the serial port of the PC.
2. Plug the RJ-45 connector of the console cable in the console port of the blade switch.

IMPORTANT:
• Identify the mark on the console port and make sure that you are connecting to the correct port.
• Make sure a DB-9 female connector is available on the terminal. If not, prepare a converter.

Figure 6 Connecting a console port to a terminal

Setting terminal parameters

To configure and manage the switch through the console port, you must run a terminal emulator program,
HyperTerminal or PuTTY, on your configuration terminal. You can use the emulator program to connect a
network device, a Telnet site, or an SSH site. For more information about the terminal emulator programs,
see the user guides for these programs.
The following are the required terminal settings:

6
 • Bits per second—9,600.
• Data bits—8.
• Parity—None.
• Stop bits—1.
• Flow control—None.

Configuring the blade switch

By default, the switch does not authenticate console login users. To increase system security and enable
remote management:
• Configure a login authentication method, for example, Telnet, SSH, or NMS.
• Configure access services.

Configuring an authentication method

You can configure authentication on a user interface to control access to the switch.
Table 3 describes the Telnet login authentication methods available for a VTY user interface. For more
information about login authentication methods, see HP 6127XLG Blade Switch Series Fundamentals
Configuration Guide.
Table 3 Telnet login authentication methods

Authentication
Characteristics Application scenarios
method

Lab environments and extremely secure

None Easy to configure, insecure
network environments

Easy to configure, secure, providing flat user Environments that do not need granular
Password
management privilege management

Username and Complex to configure, secure, providing Environments where multiple operators
password hierarchical user management cooperate to manage the switch

Configuring the basic network settings

An HP 6127XLG or HP 6127XLG TAA blade switch without any configuration will continuously attempt to
obtain an IP address via DHCP. After obtaining an IP address, it downloads a configuration file based
on DHCP options 67 and 150. To use the auto-configuration feature, see HP 6127XLG Blade Switch
Series Fundamentals Configuration Guide.
The switch can perform basic data forwarding immediately after connecting to a network. To implement
more forwarding features, configure the basic network settings such as IP address, static route, and
VLAN. For more information, see HP 6127XLG Blade Switch Series Configuration Guides.

7
Configuration example
Configuring Telnet
# Enter system view.
<Sysname> system-view

# Enable the Telnet server.

[Sysname] telnet server enable

# Enter the user interface view VTY 0. The device supports 16 concurrent VTY users.
[Sysname] user-interface vty 0

# Enable password authentication on the user interface.

[Sysname-ui-vty0] authentication-mode password

# Set the password to hello.

[Sysname-ui-vty0] set authentication password cipher hello

# Set the user role to network-admin so Telnet users accessing VTY 0 can use all commands.
[Sysname-ui-vty0] user-role network-admin
[Sysname-ui-vty0] quit

Configuring the basic network settings

1. Specify an IP address:
# Create VLAN-interface 1.
[Sysname] interface vlan-interface 1
# Assign an IP address, for example, 192.168.0.1, to VLAN-interface 1.
[Sysname-Vlan-interface1] ip address 192.168.0.1 24
[Sysname-Vlan-interface1] quit
2. Configure a static route:
# Configure a static route, with the destination IP address 172.16.1.0 and the next hop IP address
192.168.0.2.
[Sysname] ip route-static 172.16.1.0 255.255.255.0 192.168.0.2
3. Configure a VLAN:
# Create VLAN 10 and enter its view.
[Sysname] vlan 10
[Sysname-vlan10]
# Assign GigabitEthernet 1/1/5 to VLAN 10.
[Sysname-vlan10] port gigabitethernet 1/1/5
[Sysname-vlan10] quit

8
Setting up an IRF fabric

You can use HP Intelligent Resilient Framework (IRF) technology to connect and virtualize HP 6127XLG
blade switches into a virtual switch called an "IRF fabric" or "IRF virtual device" for flattened network
topology, and high availability, scalability, and manageability.

Planning IRF fabric setup

Determining the number of IRF member devices
Choose HP 6127XLG blade switch models and identify the number of required IRF member switches,
depending on the user density and upstream bandwidth requirements. The switching capacity of an IRF
fabric equals the total switching capacities of all member switches.

Identifying the master switch and planning IRF member IDs

IRF member switches will automatically elect a master. You can affect the election result by assigning a
high member priority to the intended master switch. For more information about master election, see HP
6127XLG Blade Switch Series IRF Configuration Guide.
Determine which switch you want to use as the master for managing all member switches in the IRF fabric.
An IRF fabric has only one master switch. You configure and manage all member switches in the IRF
fabric at the command line interface of the master switch.
Prepare an IRF member ID assignment scheme. An IRF fabric uses member IDs to uniquely identify and
manage its members, and you must assign each IRF member switch a unique member ID.

Planning IRF topology and connections

You can create an IRF fabric in daisy chain topology, or more reliably, ring topology. In ring topology,
the failure of one IRF link does not cause the IRF fabric to split as in daisy chain topology. Rather, the IRF
fabric changes to a daisy chain topology without interrupting network services.
You connect the IRF member switches through IRF ports, the logical interfaces for the connections
between IRF member switches. Each IRF member switch has two IRF ports: IRF-port 1 and IRF-port 2. An
IRF port goes up when you bind the first member physical port to it.
When connecting IRF member switches, you must connect the physical ports of IRF-port 1 on one switch
to the physical ports of IRF-port 2 on its neighbor switch.
The following physical ports can be used for IRF connections:
• SFP+ ports and QSFP+ ports. For more information about the transceiver modules and cables
available for the SFP+ and QSFP+ ports, see Table 10, Table 11, Table 12, and Table 13.
• Crosslink ports. A crosslink port is an internal port on a switch that connects to the switch in the
adjacent horizontal interconnect bay in the C7000 enclosure. The HP 6127XLG or HP 6127XLG TAA
switch has four crosslink ports: Port 17, Port 18, Port 19, and Port 20. By default, the four ports are

9
 shut down to avoid loops. To create an IRF fabric on two switches by using crosslink ports, execute
the undo shutdown command to bring up the crosslink ports with the same number on the switches.
Figure 7 Connecting IRF member switches using crosslink ports

Configuring basic IRF settings

After you install the IRF member blade switches, power on the blade switches, and log in to each IRF
member blade switch (see HP 6127XLG Blade Switch Series Fundamentals Configuration Guide) to
configure their member IDs, member priorities, and IRF port bindings.
For more information about configuring basic IRF settings, see HP 6127XLG Blade Switch Series IRF
Configuration Guide.

Connecting the physical IRF ports

Connect the IRF member switches as planned.

NOTE:
Wear an ESD wrist strap when you connect cables or transceiver modules and fibers. For how to connect
them, see Pluggable SFP[SFP+][XFP] Transceiver Modules Installation Guide and Pluggable QSFP+
Transceiver Modules/Cables Installation Guide.

Accessing the IRF fabric to verify the configuration

To verify the basic functionality of the IRF fabric after you finish configuring basic IRF settings and
connecting IRF ports:
1. Log in to the IRF fabric through the console port of any member switch.
2. Create a Layer 3 interface, assign it an IP address, and make sure that the IRF fabric and the
remote network management station can reach each other.
3. Use Telnet, web, or SNMP to access the IRF fabric from the network management station. (See HP
6127XLG Blade Switch Series Fundamentals Configuration Guide.)
4. Verify that you can manage all member switches as if they were one node.
5. Display the running status of the IRF fabric by using the commands in Table 4.
Table 4 Displaying and maintaining IRF configuration and running status

Task Command

Display information about the IRF fabric display irf

Display all members’ configurations display irf configuration

10
 Task Command

Display topology information about the IRF fabric display irf topology

NOTE:
To avoid IP address collision and network problems, configure a minimum of one multi-active detection
(MAD) mechanism to detect the presence of multiple identical IRF fabrics and handle collisions. For more
information about MAD detection, see HP 6127XLG Blade Switch Series IRF Configuration Guide.

11
Troubleshooting

IMPORTANT:
To prevent configuration loss, save the configuration each time you finish configuring a feature. For
configuration recovery, regularly back up the configuration to a remote server

Troubleshooting methods
When your blade switch fails, you can use the following methods to troubleshoot the blade switch:
• At the CLI, use related commands to display system operating information, and locate the failures.
• Locate the failures according to the LED status on the blade switch. For more information, see
"LEDs."
• View the system and port operating state through the OA module on the enclosure. For more
information, see HP BladeSystem Enclosure Setup and Installation Guide.

NOTE:
If you cannot locate failures by following the guidelines in this chapter, contact HP Support.

Collecting log and operating information

IMPORTANT:
By default, the information center is enabled. If the feature is disabled, you must use the info-center enable
command to enable the feature for collecting log messages.

Table 5 shows the types of files that the system uses to store operating log and status information. You can
export these files by using FTP or TFTP.
In an IRF system, these files are stored on the master device. Multiple devices will have log files if
master/subordinate switchovers have occurred. You must collect log files from all these devices. To more
easily locate log information, use a consistent rule to categorize and name files. For example, save log
files to a separate folder for each member device, and include their slot numbers in the folder names.
Table 5 Log and operating information

Category File name format Content

Common log logfile.log Command execution and operational log messages.

Diagnostic log messages about device operation, including the

following items:
• Parameter settings used when an error occurs.
Diagnostic log diagfile.log
• Information about device startup errors.
• Handshaking information between member devices when a
communication error occurs.

12
 Category File name format Content

IMPORTANT:
Collecting operating statistics decreases system performances.
Current operation statistics for feature modules, including the
following items:
Operating • Device status.
file-basename.gz
statistics • CPU status.
• Memory status.
• Configuration status.
• Software entries.
• Hardware entries.

Collecting common log messages

1. Save the common log messages from the log buffer to a log file.
By default, the log file is saved in the logfile directory of the flash memory on each member device.
<Sysname> logfile save
The contents in the log file buffer have been saved to the file
flash:/logfile/logfile.log
2. Identify the log file on each member device:
# Display the log file on the master device.
<Sysname> dir flash:/logfile/
Directory of flash:/logfile
0 -rw- 21863 Jul 11 2013 16:00:37 logfile.log

524288 KB total (107944 KB free)

# Display the log file on each subordinate device:
<Sysname> dir slot2#flash:/logfile/
Directory of slot2#flash:/logfile
0 -rw- 21863 Jul 11 2013 16:00:37 logfile.log

524288 KB total (107944 KB free)

3. Transfer the files to the desired destination by using FTP or TFTP. (Details not shown.)

Collecting diagnostic log messages

1. Save the diagnostic log messages from the diagnostic log file buffer to a diagnostic log file.
By default, the diagnostic log file is saved in the diagfile directory of the flash memory on each
member device.
<Sysname> diagnostic-logfile save
The contents in the diagnostic log file buffer have been saved to the file
flash:/diagfile/diagfile.log
2. Identify the diagnostic log file on each member device:
# Display the diagnostic log file on the master device.

13
 <Sysname> dir flash:/diagfile/
Directory of flash:/diagfile
0 -rw- 161321 Jul 11 2013 16:16:00 diagfile.log

524288 KB total (107944 KB free)

# Display the diagnostic log file on each subordinate device:
<Sysname> dir slot2#flash:/diagfile/
Directory of slot2#flash:/diagfile
0 -rw- 161321 Jul 11 2013 16:16:00 diagfile.log

524288 KB total (107944 KB free)

# Transfer the files to the desired destination by using FTP or TFTP. (Details not shown.)

Collecting operating statistics

You can collect operating statistics by saving the statistics to a file or displaying the statistics on the
screen.
When you collect operating statistics, follow these guidelines:
• Log in to the device through a network port (if any) instead of the console port. Network ports are
faster than the console port.
• Do not execute commands during operating statistics collection.
• To ensure information completeness, HP recommends that you save the statistics to a file.
To collect operating statistics:
1. Disable pausing between screens of output if you want to display operating statistics on the screen.
Skip this step if you are saving statistics to a file.
<Sysname> screen-length disable
2. Collect operating statistics for multiple feature modules.
<Sysname> display diagnostic-information
Save or display diagnostic information (Y=save, N=display)? [Y/N] :
3. At the prompt, choose to save or display operating statistics:
# To save operating statistics, enter y at the prompt and then specify the destination file path.
Save or display diagnostic information (Y=save, N=display)? [Y/N] :y
Please input the file name(*.tar.gz)[flash:/diag.tar.gz] :flash:/diag.tar.gz
Diagnostic information is outputting to flash:/diag.tar.gz.
Please wait...
Save successfully.
<Sysname> dir flash:/
Directory of flash:
…
6 -rw- 898180 Jun 26 2013 09:23:51 diag.tar.gz

1021808 KB total (259072 KB free)

# To display operating statistics on the monitor terminal, enter n at the prompt.
Save or display diagnostic information (Y=save, N=display)? [Y/N] :n
……

14
Failures at startup
No display on the configuration terminal
Symptom
The configuration terminal does not have display when the blade switch is powered on.

Solution
To resolve the problem:
1. Verify that the blade switch is operating correctly.
2. Verify that the console port is connected to the correct serial port on the terminal.
3. Verify that the console cable is in good quality and is operating correctly.
4. If you use a converter to connect the terminal, a laptop, for example, and the console cable, make
sure the driver for the converter is installed.
5. Verify that the configuration terminal and the console port of the switch have the same settings. The
default setting for the console port are as follows:
{ Baud rate—9600.
{ Data bits—8.
{ Parity—None.
{ Stop bits—1.
{ Flow control—None.
{ Emulation—VT100.
If the console port settings change, change the terminal settings accordingly.
6. If the problem persists, contract HP Support.

Garbled display on the configuration terminal

Symptom
The configuration terminal displays garbled text when the blade switch is powered on.

Solution
To resolve the problem:
1. Verify that the configuration terminal and the console port of the switch have the same settings. The
default setting for the console port are as follows:
{ Baud rate—9600.
{ Data bits—8.
{ Parity—None.
{ Stop bits—1.
{ Flow control—None.
{ Emulation—VT100.
If the console port settings change, change the terminal settings accordingly.

15
 2. If the problem persists, contact HP Support.

Failures during operation

Symptom
A failure occurs when the blade switch is operating.

Solution
To resolve the problem:
1. Execute related commands at the CLI to display blade switch operating information and locate the
fault.
2. If a configuration error is found, re-configure the switch, perform configuration rollback, or restore
the factory-default settings.
For example, if an incorrect IP address is configured for an interface, you can use the undo ip
address command in interface view to delete the IP address and configure a new one.
If multiple configuration errors need to be rectified, you can perform configuration rollback to roll
back the switch to the specified configuration status without rebooting the switch. For more
information about configuration rollback, see HP 6127XLG Blade Switch Series Configuration
Guides and HP 6127XLG Blade Switch Series Command References.
3. If the problem persists, contact HP Support.

IRF member device failure

Symptom
An IRF member device fails and needs to be replaced.

Solution
To resolve the problem:
1. Prepare a device that is the same model as the failed one.
2. View the startup configuration file saved on an IRF member device that is operating correctly.
Record the IRF member ID of the failed device and how the IRF physical interfaces on the failed
device are bound to the IRF ports.
3. From the OA module on the enclosure, power off the failed device.
4. Record the cable connection positions on the failed device and remove all cables from the failed
device.
5. Install the new device in the enclosure. The device powers on automatically.
6. Log in to the new device. Configure IRF member ID and IRF port bindings on the new device based
on the recorded IRF configuration information of the failed device.
7. Install the modules and cables for the new device.
8. Activate the IRF port configuration on the new device. The device reboots automatically and joins
the IRF.
9. Verify that the new device is operating correctly by viewing the operating state of the new device
from the OA module in the enclosure.

16
 The new device automatically gets global and interface configuration of the failed device from the
IRF and performs the same network functions as the failed device.
10. If the problem persists, contact HP Support.

Software upgrade failure

Symptom
Software upgrade fails.

Solution
To resolve the problem:
1. Verify that the physical ports are connected correctly.
2. If you log in to the blade switch from the console port, verify that terminal parameters are set
correctly.
3. Verify that the information on the HyperTerminal is input correctly.
{ If software is upgraded using TFTP, verify that the IP address, the file name, and the assigned
working directory of the TFTP server are correct.
{ If software is upgraded using FTP, verify that the IP address, the file name and the assigned
working directory of the FTP server, FTP username and password are correct.
4. Verify that the FTP server or the TFTP server is operating correctly and the configuration is correct.
5. Verify that the flash has enough space to save the file to be downloaded.
6. Verify that the file for upgrade is suitable for the product and the file type is correct.
7. Verify that the system software image file and the BootWare file versions are correct. For the
software version matrix, see relevant Release Notes.
8. If the problem persists, contact HP Support.

Hardware failures
Symptom
The Health LED is not green.

Solution
To resolve the problem:
1. Verify that the enclosure is operating correctly.
2. Verify that the blade switch is installed securely. If not, pull out the blade switch and install it again.
3. Press the Reset button on the front panel of the blade switch. After the blade switch starts up, verify
that the Health LED is green.
4. If an idle interconnect bay is available on the enclosure, you can install the blade switch into it to
verify that the Health LED is green.
5. If the problem persists, contact HP Support.

17
Interface failure
Symptom
The LED for an interface connected to the network is off.

Solution
To resolve the problem:
1. Verify that the blade switch is operating correctly.
2. Verify the cable is connected correctly. For more information, see "Connecting the blade switch to
the network."
3. Use a cable in good condition to connect the interfaces. If the LED of the interface is on, replace
the original cable. If the LED is not on, verify that the interfaces at the two ends are operating
correctly. If they are not, replace the failed interfaces.
4. Verify that the speed and duplex settings of the interfaces at the two ends are the same.
5. If the problem persists, contact HP Support.

NOTE:
• If an interface is brought down by the shutdown command, use the undo shutdown command to bring
up the interface.
• When an interface fails, if the switch has an idle interface of the same type, you can connect the cable
to the idle interface.

18
Support and other resources

Contacting HP
For worldwide technical support information, see the HP support website:
http://www.hp.com/support
Before contacting HP, collect the following information:
• Product model names and numbers
• Technical support registration number (if applicable)
• Product serial numbers
• Error messages
• Operating system type and revision level
• Detailed questions

Subscription service
HP recommends that you register your product at the Subscriber's Choice for Business website:
http://www.hp.com/go/wwalerts
After registering, you will receive email notification of product enhancements, new driver versions,
firmware updates, and other product resources.

Related information
Documents
To find related documents, browse to the Manuals page of the HP Business Support Center website:
http://www.hp.com/support/manuals
• For related documentation, navigate to the Networking section, and select a networking category.
• For a complete list of acronyms and their definitions, see HP FlexNetwork Technology Acronyms.

Websites
• HP.com http://www.hp.com
• HP Networking http://www.hp.com/go/networking
• HP manuals http://www.hp.com/support/manuals
• HP download drivers and software http://www.hp.com/support/downloads
• HP software depot http://www.software.hp.com
• HP Education http://www.hp.com/learn

19
Conventions
This section describes the conventions used in this documentation set.

Command conventions

Convention Description

Boldface Bold text represents commands and keywords that you enter literally as shown.

Italic Italic text represents arguments that you replace with actual values.

[] Square brackets enclose syntax choices (keywords or arguments) that are optional.

Braces enclose a set of required syntax choices separated by vertical bars, from which
{ x | y | ... }
you select one.

Square brackets enclose a set of optional syntax choices separated by vertical bars, from
[ x | y | ... ]
which you select one or none.

Asterisk-marked braces enclose a set of required syntax choices separated by vertical

{ x | y | ... } *
bars, from which you select at least one.

Asterisk-marked square brackets enclose optional syntax choices separated by vertical

[ x | y | ... ] *
bars, from which you select one choice, multiple choices, or none.

The argument or keyword and argument combination before the ampersand (&) sign can
&<1-n>
be entered 1 to n times.

# A line that starts with a pound (#) sign is comments.

GUI conventions

Convention Description

Window names, button names, field names, and menu items are in bold text. For
Boldface
example, the New User window appears; click OK.

> Multi-level menus are separated by angle brackets. For example, File > Create > Folder.

Symbols

Convention Description

An alert that calls attention to important information that if not understood or followed can
WARNING
result in personal injury.

An alert that calls attention to important information that if not understood or followed can
CAUTION
result in data loss, data corruption, or damage to hardware or software.

IMPORTANT An alert that calls attention to essential information.

NOTE An alert that contains additional or supplementary information.

TIP An alert that provides helpful information.

20
Network topology icons

Represents a generic network device, such as a router, switch, or firewall.

Represents a routing-capable device, such as a router or Layer 3 switch.

Represents a generic switch, such as a Layer 2 or Layer 3 switch, or a router that supports
Layer 2 forwarding and other Layer 2 features.

Represents an access controller, a unified wired-WLAN module, or the switching engine

on a unified wired-WLAN switch.

Represents an access point.

  Represents a security product, such as a firewall, a UTM, or a load-balancing or security

card that is installed in a device.

Represents a security card, such as a firewall card, a load-balancing card, or a

NetStream card.

Port numbering in examples

The port numbers in this document are for illustration only and might be unavailable on your device.

21
Appendix Technical specifications

Table 6 Technical specifications

Item HP 6127XLG/HP 6127XLG TAA

Dimensions (H × W ×
27.9 × 192.8 × 267.7 mm (1.1 × 7.59 × 10.54 in)
D)

Weight ≤ 2 kg (4.41 lb)

Console port 1
(on the front panel) This port is used for directly logging in to the switch.

AUX port 1
(on the rear panel) This port can be accessed only through OA redirection.

Internal management
Ethernet port 1 × 100 Mbps port
(on the rear panel)

Internal downlink ports

16 × 10/20-GE port
(on the rear panel)

Internal crosslink ports

4 × 10-GE port
(on the rear panel)

External uplink ports • 4 × QSFP+ port

(on the front panel) • 8 × SFP+ port
Power consumption 120 W

Operating temperature 10°C to 35°C (50°F to 95°F)

Operating humidity
10% to 90%
(noncondensing)

Front view
Figure 8 Front view of the HP 6127XLG/HP 6127XLG TAA

(1) Health LED (2) Unit ID (UID) LED

22
 (3) Port LED (It indicates the operating status of the port with the same number) (4) Reset button
(5) Ports 5 to 12 (SFP+) (6) Console port
(7) Ports 1 to 4 (QSFP+)

Port numbering
The ports on the blade switch are numbered in the interface type A/B/C format:
• A—IRF member ID of the switch.
• B—Slot number. The slot number of the uplink ports on the front panel is 1. The slot number of the
downlink ports and crosslink ports on the rear panel is 0.
• C—Port number. See Figure 9.
Figure 9 Port numbers
External uplink port

12 11 10 9 8 7 6 5 4 3 2 1
SFP+ port QSFP+ port

6127XLG

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

Backplane

Internal downlink port Internal crosslink port

23
LEDs
Table 7 LED description

LED mark Status Description

Blue Switch ID selected.

UID
Off Switch ID not selected.

Green The blade switch has started properly.

Flashing yellow The blade switch is performing POST, or is faulty.

Off The blade switch is not powered on, or is faulty.

Steady green The port is operating at 10 Gbps.

Flashing green The port is sending or receiving data at 10 Gbps.

SFP+ Steady yellow The port is operating at 1 Gbps.

Flashing yellow The port is sending or receiving data at 1 Gbps.

Off No link is present on the port.

Steady green The port is operating at 40 Gbps.

Flashing green The port is sending or receiving data at 40 Gbps.

QSFP+ Steady yellow The port is operating at 10 Gbps.

Flashing yellow The port is sending or receiving data at 10 Gbps.

Off No link is present on the port.

Ports
Console port
The HP 6127XLG or HP 6127XLG TAA blade switch has one console port on its front panel.
Table 8 Console port specifications

Item Specification

Connector type RJ-45

Compliant standard EIA/TIA-232

Transmission baud rate 9600 bps (default) to 115200 bps

• Provides connection to an ASCII terminal.
Services • Provides connection to the serial port of a local PC or a remote terminal running
terminal emulation program.

24
SFP+ port
The HP 6127XLG or HP 6127XLG TAA blade switch has eight SFP+ ports. They accept supported SFP
transceiver modules, SFP+ modules, or SFP+ cables.
Table 9 1000 Mbps SFP transceiver modules

Multimode
Central Fiber Max
Product fiber modal
Module description wavelength diameter transmission
code bandwidth
(nm) (μm) distance
(MHz × km)

550 m (1804.46
500
ft)
50/125
500 m (1640.42
400
HP X120 1G SFP LC SX ft)
JD118B 850
Transceiver 275 m (902.23
200
ft)
62.5/125
220 m (721.78
160
ft)

10 km (6.21
9/125 N/A
miles)

HP X120 1G SFP LC LX 500 550 m (1804.46

JD119B 1310 50/125
Transceiver 400 ft)

550 m (1804.46
62.5/125 500
ft)

HP X125 1G SFP LC LH40 40 km (24.86

JD061A 1310 9/125 N/A
1310nm Transceiver miles)

HP X120 1G SFP LC LH40 40 km (24.86

JD062A 1550 9/125 N/A
1550nm Transceiver miles)

HP X125 1G SFP LC LH70 70 km (43.50

JD063B 1550 9/125 N/A
Transceiver miles)

HP X120 1G SFP RJ45 T Category-5 100 m (328.08

JD089B N/A N/A
transceiver twisted pair ft)

Table 10 10 Gbps SFP+ transceiver modules

Multimode
Central Fiber
Product fiber modal Maximum transmission
Description wavelength diameter
code bandwidth distance
(nm) (μm)
(MHz × km)

2000 300 m (984.25 ft)

50/125 500 82 m (269.03 ft)

HP X130 10G
JD092B SFP+ LC SR 850 400 66 m (216.54 ft)
Transceiver
200 33 m (108.27 ft)
62.5/125
160 26 m (85.3 ft.)

25
 Multimode
Central Fiber
Product fiber modal Maximum transmission
Description wavelength diameter
code bandwidth distance
(nm) (μm)
(MHz × km)

160

HP X130 10G
JD094B SFP+ LC LR 1310 9/125 N/A 10 km (6.21 miles)
Transceiver

Table 11 SFP+ cables

Product code Cable description Cable length

JD095C HP X240 10G SFP+ SFP+ 0.65m DA Cable 0.65 m (2.13 ft)

JD096C HP X240 10G SFP+ SFP+ 1.2m DA Cable 1.2 m (3.94 ft)

JD097C HP X240 10G SFP+ SFP+ 3m DA Cable 3 m (9.84 ft)

JG081C HP X240 10G SFP+ SFP+ 5m DA Cable 5 m (16.40 ft)

NOTE:
• The transceiver modules and cables available for the blade switch are subject to change over time. For
the most up-to-date list of transceiver modules and cables, consult your HP sales representative or
technical support engineer.
• For the transceiver module and cable specifications, see HP Comware-Based Devices Transceiver
Modules User Guide.

QSFP+ port
The HP 6127XLG or HP 6127XLG TAA blade switch supports QSFP+ modules and QSFP+ cables on the
QSFP+ ports.
Table 12 QSFP+ transceiver modules

Central Fiber Modal

Product Fiber Transmission
HP description wavelen diamete bandwidth
code mode distance
gth (nm) r (μm) (MHz*km)

2000 100 m (328.08 ft)

HP X140 40G QSFP+
JG325B 850 MMF 50/125
MPO SR4 Transceiver
4700 150 m (492.12 ft)

HP X140 40G QSFP+ 2000 300 m (984.25 ft)

JG709A MPO MM 850nm CSR4 850 MMF 50/125
300m Transceiver 4700 400 m (1312.33 ft)

26
 Central Fiber Modal
Product Fiber Transmission
HP description wavelen diamete bandwidth
code mode distance
gth (nm) r (μm) (MHz*km)

Four
lanes:
HP X140 40G QSFP+
LC LR4 SM 10km • 1271
JG661A SMF 9/125 N/A 10 km (6.21 miles)
1310nm Transceiver • 1291
Module • 1311
• 1331

Table 13 QSFP+ cables

Product code Cable description Cable length

HP X240 40G QSFP+ QSFP+ 1m Direct Attach Copper

JG326A 1 m (3.28 ft)
Cable

HP X240 40G QSFP+ QSFP+ 3m Direct Attach Copper

JG327A 3 m (9.84 ft)
Cable

HP X240 40G QSFP+ QSFP+ 5m Direct Attach Copper

JG328A 5 m (16.40 ft)
Cable

HP X240 40G QSFP+ to 4x10G SFP+ 1m Direct Attach

JG329A 1 m (3.28 ft)
Copper Splitter Cable

HP X240 40G QSFP+ to 4x10G SFP+ 3m Direct Attach

JG330A 3 m (9.84 ft)
Copper Splitter Cable

HP X240 40G QSFP+ to 4x10G SFP+ 5m Direct Attach

JG331A 5 m (16.40 ft)
Copper Splitter Cable

NOTE:
• The transceiver modules and cables available for the blade switch are subject to change over time. For
the most up-to-date list of transceiver modules and cables, consult your HP sales representative or
technical support engineer.
• For the transceiver module and cable specifications, see HP Comware-Based Devices Transceiver
Modules User Guide.

Cables
Figure 10 Cables

Cable Applicable port Description

Connecting a transceiver module and a fiber

Fiber connector SFP+/QSFP+ ports
cable

SFP+ cable SFP+ ports Connecting SFP+ ports

QSFP+ cable QSFP+ ports Connecting QSFP+ ports

27
 Cable Applicable port Description

QSFP+ port at one end, and Connecting QSFP+ ports at one end and SFP+
QSFP+ to SFP+ cable
SFP+ port at the other ports at the other

Fiber connector
Fiber connectors are indispensable passive components in an optical fiber communication system. They
allow the removable connection between optical channels, which makes the optical system debugging
and maintenance more convenient and the transit dispatching of the system more flexible. Figure 11
and Figure 12 show the MPO and LC connectors supported by the switch.
Figure 11 MPO connector

Figure 12 LC connector

SFP+ cable
You can use SFP+ cables to connect the SFP+ ports. The SFP+ cables available for the switch series are
10 G SFP+ Cu cables, as shown in Figure 13.
Figure 13 SFP+ cable

(1) Connector (2) Pull latch

28
QSFP+ cable
You can use QSFP+ cables to connect the QSFP+ ports.
Figure 14 QSFP+ cable

(1) Connector (2) Pull latch

QSFP+ to SFP+ cable

A QSFP+ to SFP+ cable is a cable with one QSFP+ module at one end and four SFP+ modules at the
other end.
Figure 15 QSFP+ to SFP+ cable

(1) QSFP+ connector (2) QSFP+ pull latch

(3) SFP+ connector (4) SFP+ pull latch

29
Index

ACFHILPRST
A Installing and removing the blade switch,1
Interface failure,18
Accessing the IRF fabric to verify the configuration,10
IRF member device failure,16
C
L
Cables,27
LEDs,24
Collecting log and operating information,12
Logging in through the console port,5
Configuring basic IRF settings,10
Logging in through the OA module,5
Configuring the blade switch,7
Connecting the blade switch to the network,3 P
Connecting the physical IRF ports,10 Planning IRF fabric setup,9
Contacting HP,19 Port numbering,23
Conventions,20 Ports,24
F Preparing for installation,1

Failures at startup,15 R
Failures during operation,16 Related information,19
Front view,22 S
H Software upgrade failure,17
Hardware failures,17 T
I Troubleshooting methods,12

30