HP 6125XLG User manual

HP 6125XLG Blade Switch
Installation Guide
Part number: 5998-3713a
Document version: 6W103-20150327

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.

i
Contents
Installing the blade switch ··········································································································································· 1
Preparing for installation ··················································································································································1
Installing and removing the blade switch·······················································································································1
Installing the blade switch ·······································································································································1
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

ii
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

1
Installing the blade switch
The HP 6125XLG switches can be installed into 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.
IMPORTANT:
For regulatory identification purposes, the HP 6125XLG Blade Switch is assigned a regulatory model
number (RMN) HSTNS-BC59-N. This re
g
ulatory number should not be confused with the marketin
g
name
HP 6125XLG.
Preparing for installation
W
ARNING!
•The blade switches are Class 1 laser devices. 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.
Installing the blade switch
1. Wear an ESD wrist strap and make sure it makes good skin contact and is well grounded.
2. Remove the interconnect blank from the slot.
Keep the removed interconnect blank for future use.
3. Unpack the blade switch.

2
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
7. Verify that the Health LED is green after the blade switch starts up.
Otherwise, check the installation.
8. Choose proper 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."

3
Removing the blade switch
1. Wear an ESD wrist strap and make sure it makes good skin contact and is well 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. Fiber
interfaces must be installed with shielded covers when they are not in use. Keep them safely.
•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
W
ARNING!
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.

4
Figure 3 Using LC optical fiber connectors to connect transceiver modules
Figure 4 Using MPO optical fiber connectors to connect transceiver modules
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 6125XLG Blade Switch Network
Management and Monitoring Command Reference.
LC plug
SFPmodule
MPO plug
QSFP+ module

5
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

6
Table 1 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:

7
•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 2 describes the Telnet login authentication methods available for a VTY user interface. For more
information about login authentication methods, see HP 6125XLG Blade Switch Fundamentals
Configuration Guide.
Table 2 Telnet login authentication methods
Authentication
method Characteristics Application scenarios
None Easy to configure, insecure Lab environments and extremely secure
network environments
Password Easy to configure, secure, providing flat user
management
Environments that do not need granular
privilege management
Username and
password
Complex to configure, secure, providing
hierarchical user management
Environments where multiple operators
cooperate to manage the switch
Configuring the basic network settings
An HP 6125XLG blade switch without any configuration will continuously attempt to obtain an IP address
via DHCP and then download a configuration file based on DHCP options 67 and 150. To use the
auto-configuration feature, see HP 6125XLG Blade Switch 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 6125XLG Blade Switch Configuration Guides.

8
NOTE:
•You can use shortcut keys to break out of the configuration file download attempt. The shortcut keys var
y
by software versions. Use Ctrl+D for Release 2403 and later versions and Ctrl+C for versions earlier
than Release 2403.
•A save command to store a configuration file will prevent the switch from seeking a configuration file
after future reboots.
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

9
Setting up an IRF fabric
You can use HP Intelligent Resilient Framework (IRF) technology to connect and virtualize HP 6125XLG
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 6125XLG 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
6125XLG Blade Switch 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 9, Table 10, Table 11, and Table 12.
•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 6125XLG switch has four
crosslink ports: Port 17, Port 18, Port 19, and Port 20. By default, the four ports are shut down to

10
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 6125XLG Blade Switch Fundamentals Configuration Guide) to configure
their member IDs, member priorities, and IRF port bindings.
For more information about configuring basic IRF settings, see HP 6125XLG Blade Switch IRF
Configuration Guide.
Connecting the physical IRF ports
Connect the IRF member switches as planned.
NOTE:
W
ear an ESD wrist strap when you connect cables or transceiver modules and fibers. For how to connec
t
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
6125XLG Blade Switch 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 3.
Table 3 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

11
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 6125XLG Blade Switch IRF Configuration Guide .

12
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 HP 6125XLG 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 4 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 4 Log and operating information
Category File name format Content
Common log logfile.log Command execution and operational log messages.

13
Category File name format Content
Diagnostic log diagfile.log
Diagnostic log messages about device operation, including the
following items:
•Parameter settings used when an error occurs.
•Information about device startup errors.
•Handshaking information between member devices when a
communication error occurs.
Operating
statistics file-basename.gz
IMPORTANT:
Collecting operating statistics decreases system performances.
Current operation statistics for feature modules, including the
following items:
•Device status.
•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.

14
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.
<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 yat 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:

15
…
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 nat the prompt.
Save or display diagnostic information (Y=save, N=display)? [Y/N] :n
……
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.

16
{Data bits—8.
{Parity—None.
{Stop bits—1.
{Flow control—None.
{Emulation—VT100.
If the console port settings change, change the terminal settings accordingly.
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 6125XLG Blade Switch Configuration Guides
and HP 6125XLG Blade Switch 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.