H3C UniServer BT716F User manual

H3C UniServer BT716F Straight-Through Module
User Guide
New H3C Technologies Co., Ltd.
http://www.h3c.com
Document version: 6W100-20230224

Copyright © 2023, New H3C Technologies Co., Ltd. and its licensors
All rights reserved
No part of this manual may be reproduced ortransmitted in any form or by any means without prior
written consent of New H3C Technologies Co., Ltd.
Trademarks
Except for the trademarks of New H3C Technologies Co., Ltd., any trademarks that may be
mentioned in this document are the property of their respective owners.
Notice
The information in this document is subject to change without notice. All contents in this document,
including statements, information, and recommendations,are believed to be accurate, but they are
presented without warranty of any kind, express or implied. H3C shall not be liable for technical or
editorial errors or omissions contained herein.
Environmental protection
This product has been designed to comply with the environmental protection requirements. The
storage, use, and disposal of this product must meet the applicable national laws and regulations.

Preface
This preface includes the following topics about the documentation:
•
Audience.
•
Conventions.
•
Documentation feedback.
Audience
This documentation is intended for:
•
Network planners.
•
Field technical support and servicing engineers.
•
Network administrators working with the server.
Conventions
The following information describes the conventions used in the documentation.
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.
{ x | y | ... }
Braces enclose a set of required syntax choices separated by vertical bars, from which
you select one.
[ x | y | ... ]
Square brackets enclose a set of optional syntax choices separated by vertical bars,
from which you select one or none.
{ x | y | ... } *
Asterisk marked braces enclose a set of required syntax choices separated by vertical
bars, from which you select a minimum of one.
[ x | y | ... ] *
Asterisk marked square brackets enclose optional syntax choices separated by vertical
bars, from which you select one choice, multiple choices, or none.
&<1-n> The argument or keyword and argument combination before the ampersand (&) sign
can be entered 1 to n times.
# A line that starts with a pound (#) sign is comments.
GUI conventions
Convention
Description
Boldface Window names, button names, field names, and menu items are in Boldface. For
example, the
New User
window opens; click
OK
.
> Multi-level menus are separated by angle brackets. For example, File > Create >
Folder.

Symbols
Convention
Description
WARNING!
An alert that calls attention to important information that if not understood or followed
can result in personal injury.
CAUTION:
An alert that calls attention to important information that if not understood or followed
can 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.
Network topology icons
Convention
Description
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 access
controller engine on a unified wired-WLAN switch.
Represents an access point.
Represents a wireless terminator unit.
Represents a wireless terminator.
Represents a mesh access point.
Represents omnidirectional signals.
Represents directional signals.
Represents a security product, such as a firewall, UTM, multiservice security
gateway, or load balancing device.
Represents a security module, such as a firewall, load balancing, NetStream, SSL
VPN, IPS, or ACG module.
Examples provided in this document
Examples in this document might use devices that differ from your device in hardware model,
configuration, or software version. It is normal that the port numbers, sample output, screenshots,
and other information in the examples differ from what you have on your device.
T
T
T
T

Documentation feedback
You can e-mail your comments about product documentation to [email protected]om.
We appreciate your comments.

i
Contents
1 Safety ···················································································································································1-1
1.1 Safety Information·····························································································································1-1
1.1.1 General Operating Safety·······································································································1-1
1.1.2 Electrical Safety······················································································································1-1
1.2 Safety Precautions····························································································································1-1
1.3 ESD Prevention·································································································································1-1
1.3.1 Preventing Electrostatic Discharge ························································································1-1
1.3.2 Grounding Methods to Prevent Electrostatic Discharge ························································1-2
2 About the BT716F Straight-Through Module·······················································································2-1
2.1 Product Overview······························································································································2-1
2.2 Specifications····································································································································2-1
2.3 Interface············································································································································2-2
2.3.1 Interface Numbering Rules·····································································································2-2
2.3.2 Description of Interfaces·········································································································2-3
2.4 Indicators···········································································································································2-5
2.5 Internal Connection···························································································································2-7
2.5.1 Connections Between Straight-Through Modules and Mezz NICs········································2-7
2.5.2 Internal Connections Between Straight-Through Modules and Blade Server Mezz NICs·····2-9
2.5.3 Internal Connection Between the Direct Module Interface and the Blade Server··················2-9
2.6 Logical Structure ·····························································································································2-15
2.7 Installation Guidelines·····················································································································2-16
2.8 Hardware Compatibility·····················································································································2-1
2.8.1 Compatibility Between Straight-Through Modules and Mezz NICs·······································2-1
2.8.2 Optical Modules······················································································································2-1
2.9 External Networking Connection·······································································································2-2
3 Replacing the ICM································································································································3-1
3.1 Scenario············································································································································3-1
3.2 Installation Tools·······························································································································3-1
3.3 Preparations······································································································································3-2
3.4 Replacement Procedure ···················································································································3-2
4 Powering On and Powering Off············································································································4-1
4.1 Powering On the Straight-Through Module ······················································································4-1

ii
4.2 Powering Off the Straight-Through Module ······················································································4-1
5 Checking the Straight-Through Module·······························································································5-1
5.1 Checking Port Status of Straight-Through Module Through OM Modules·······································5-1
5.1.2 Viewing through the OM CLI··································································································5-2
6 Configuring the Straight-Through Module····························································································6-1
6.1 Changing the Port Rate ····················································································································6-1
6.2 Common Operations·························································································································6-1
6.2.1 Logging into the OM Web·······································································································6-1
6.2.2 Logging In to the CLI of OM Module ······················································································6-3
7 Firmware Upgrade································································································································7-1

1-1
1 Safety
1.1 Safety Information
To avoid personal injury or damage to the device, read the following information carefully before
you operate the device. Safety precautions in actual operation include but are not limited to safety
information mentioned in this document.
1.1.1 General Operating Safety
•
Only H3C authorized or professional engineers are allowed to operate the device.
•
Keep the device clean and dust-free. Do not place it in a humid place or allow liquids to enter
it.
•
Before powering on the device, ensure that the blade enclosure is securely grounded.
•
To maintain sufficient heat dissipation, use filler panels on idle slots.
1.1.2 Electrical Safety
•
Carefully check any potential hazards in the work area, for example, whether the ground is
wet and whether the blade enclosure is grounded or reliably grounded.
•
Do not work alone when performing live-line maintenance.
•
Do not touch the power supply directly or indirectly through conductive objects to prevent
electric shock.
1.2 Safety Precautions
•
When maintaining the device, place the device on a clean, stable table or floor.
•
To avoid personal injury from hot surfaces or internal components, allow the device and its
internal components to cool before touching them.
•
When using tools to maintain the device, follow the correct operation methods to avoid
damage to the personnel or device.
•
When connecting, testing or replacing optical fibers, do not look directly into the optical fiber
outlet to prevent the laser beam from hurting your eyes.
•
Gently and slowly transport or place the device with force evenly distributed.
1.3 ESD Prevention
1.3.1 Preventing Electrostatic Discharge
Electrostatic charges that build up on people and conductors damage or shorten the lifespan of the
main board and electrostatic-sensitive components.
To prevent electrostatic damage, follow these guidelines:

1-2
•
Transport or store the device in an ESD bag.
•
Place the device on a grounded table before taking it out of the ESD bag.
•
Avoid touching pins or circuitry of the device without taking any ESD prevention measures.
1.3.2 Grounding Methods to Prevent Electrostatic Discharge
When removing or installing the device, you can use one or multiple of the following grounding
methods to prevent electrostatic discharge:
•
Wear an ESD wrist strap and ensure that it is reliably grounded. Ensure that the ESD wrist
strap makes good skin contact and can be flexibly stretched out and draw back.
•
In the work areas, wear the ESD clothing and shoes.
•
Use conductive field service tools.
•
Use a portable field service kit with a folding ESD tool mat.

2-1
2 About the BT716F Straight-Through Module
Note
•Hardware images shown in this manual are for illustration purposes only. The actual product may
vary.
•The software UI may be updated from time to time. Please refer to the actual product UI.
•ICMs supported by the chassis are classified into switching modules and straight-through modules
(also known as cascading modules in some manuals). The BT716F is a type of straight-through
module. The ICM and straight-through module in this document refer to the BT716F straight-through
module.
2.1 Product Overview
H3C UniServer BT716F is a 16G/32G FC straight-through module for the H3C UniServer B16000
blade enclosure. It provides an external data interface, which enables direct connection of parallel
cables to the FC Mezz NIC port of the blade server at the front of the chassis.
Note
Different from the switching module, the straight-through module supports only the transparent
transmission of data between the blade servers andthe external network, but does not process the
data that pass through the straight-through module.
Figure 2-1 shows the appearance of the BT716F straight-through module.
Figure 2-1 Appearance of BT716F
2.2 Specifications
Table 2-1 describes the specifications of the straight-through module.
Table 2-1 Specifications
Category Item Description
Physical
specifications Dimensions (H × W × D) 27 mm × 491.6 mm × 296.5 mm

2-2
Category Item Description
Maximum
weight 3.35 kg
Power
consumption
Maximum
power
consumption 25 W
Environment
specifications
Temperature •Operating temperature: 5°C to 45°C
•Storage temperature: -40°C to 70°C
Humidity •Operating humidity: 8% to 90% (non-condensing)
•Storage humidity: 5% to 95% (non-condensing)
Altitude
•Operating altitude: -60 m to +5000 m (The allowed maximum
temperature decreases by 0.33 °C as the altitude increases by 100 m
from 900 m)
•Storage altitude: –60 m to +5000 m
2.3 Interface
This section describes numbering rules, positions, quantity, and other information about the
interfaces of the straight-through module, as well as the correspondence between interface and
blade server slot.
2.3.1 Interface Numbering Rules
The numbering rule of FC interfaces of the straight-through module is defined by "A/B/C".
•
A: Defaults to 1; cannot be edited.
•
B: Distinguishes between internal and external Ethernet interfaces. 0 indicates an internal
interface, and 1 indicates an external interface. Since a straight-through module does not
have any internal interfaces, this part in the number is 1.
•
C: Indicates the sequence numberof the interface onthe straight-through module; consistent
with the interface silk screen number on the panel.
For example, for an interface with a silk screen number "6" on the panel of the straight-through
module, the interface number is "1/1/6".

2-3
Figure 2-2 Interfaces
2.3.2 Description of Interfaces
Figure 2-3 shows the external interfaces on the panel of a straight-through module. Table 2-2 lists
details about the interfaces.

2-4
Figure 2-3 External interfaces
Table 2-2 Description of interfaces
No. Interface
Name Type Quan tity Interfaces Description
1
AMC serial port
RJ-45 1 - This serial port is used to access the AMC CLI. It is only used by
technical support engineers to display the status of the 32G FC
optical port or for maintenance. The baud rate of the serial port is
115200 bit/s.

2-5
2
16G/32G FC optical port SFP+
16 1 to 16 •Each port supports three rate
modes (auto/16G/32G). auto
(default mode) indicates that the
port is adaptive to the rate of the
optical module. The port rate can
be changed with the OM module.
For details, see 6.1 Changing the
Port Rate.
•Straight-through module
interfaces are in direct
correspondence to the blade
server. For details, see 2.5.3
Internal Connection Between the
Direct Module Interface and the
Blade Server.
•For the optical modules supported
by the interface, see 2.8.2 .
2.4 Indicators
Table 2-3 describes indicators of the straight-through module.

2-6
Figure 2-4 Indicators of the straight-through module
Indicators for different interfaces of the straight-through module are consistent-looking. Here we use one
indicator of interface as an example.
Table 2-3 Description of indicators
SN Name Color Status
1 UID指示灯（UID）蓝色
•Steady on blue: The UIDindicator isactivated (through the OM
module).
•灯灭：UID 指示灯未被激活
2 RUN指示灯（RUN）绿色
•Steady on green/off: The system is faulty.
•Blinking green (at a frequency of 4 Hz): The system is loading
data.
•Blinking green (at a frequency of 1 Hz): The system is running
normally.
3 Health指示灯（ ） 红/绿双色
•Steady on green: The straight-through module is running
normally.
•Blinking red (1 Hz): The straight-through module generates an
alarm.
•Off: The straight-through module is not powered on or in

2-7
SN Name Color Status
position.
4 Service port
indicator Green
•Blinking green (1 Hz): The port link is in either of the following
statuses:
•The port link is connected but no data is transmitted.
•The port link is connected and data transmission is in
progress.
•Off: The port link is not connected.
There are 16 service port indicators on the straight-through module panel, and they correspond to the interfaces
on the panel.
2.5 Internal Connection
To access a target blade server through the external interface of the straight-through module, you
need to know the following information:
•
Before installing a straight-through module or a Mezz NIC for a blade server, you need to
know the specific slot for installation. For details, see 2.5.1 Connections Between
Straight-Through Modules and Mezz NICs.
•
Before configuring the Mezz NIC for the blade server, you need to know the correspondence
between the port used by the Mezz NIC and the straight-through module. For details, see
2.5.2 .
•
Before accessing the blade server through the straight-through module, you need to know
how the connection between the interface of the straight-through module and the target
blade server. For details, see 2.5.3 .
2.5.1 Connections Between Straight-Through Modules and Mezz NICs
Table 2-4 describes connections between straight-through modules and Mezz NICs, helping you
accurately choose slots for installing the straight-through modules.
Table 2-4 Connections between straight-through modules and Mezz NICs
Model of Blade Server Maximum Number of
Supported Mezz NICs Connections Between Straight-Through Modules and Mezz NICs
H3C UniServer B5700 G5 3 See 2.5.1 1. Mode 1
H3C UniServer B5700 G3 3 See 2.5.1 1. Mode 1.
H3C UniServer B7800 G3 6 See 2.5.1 1. Mode 1.
H3C UniServer B5800 G3 3 See 2.5.1 2. Mode 2.
1. Mode 1
For blade servers that support up to three Mezz NICs, Figure 2-5 describes the internal connection
between the straight-through module and the Mezz NIC of the blade server. Where:
•
The onboard NIC is connected to the active and standby OM modules.
•
Mezz NIC 1 is connected to straight-through modules in slot 1 and slot 4.

2-8
•
Mezz NIC 2 is connected to straight-through modules in slot 2 and slot 5.
•
Mezz NIC 3 is connected to straight-through modules in slot 3 and slot 6.
Figure 2-5 Connections between straight-through modules and blade server Mezz NICs (1)
2. Mode 2
For blade servers that support up to six Mezz NICs, Figure 2-6 describes the internal connection
between the straight-through module and the Mezz NIC of the blade server. Where:
•
The onboard NIC is connected to the active and standby OM modules.
•
Mezz NIC 1 and Mezz NIC 4 are connected to straight-through modules in slot 1 and slot 4.
•
Mezz NIC 2 and Mezz NIC 5 are connected to straight-through modules in slot 2 and slot 5.
•
Mezz NIC 3 and Mezz NIC 6 are connected to straight-through modules in slot 3 and slot 6.
Mezz1
Mezz2
Mezz3
12
LOM P1
LOM P2
2
3
1
6
5
4
Blade ICM
Mid-plane
Embedded
OM

2-9
Figure 2-6 Connections between straight-through modules and blade server Mezz NICs (2)
2.5.2 Internal Connections Between Straight-Through Modules and Blade Server Mezz
NICs
When configuring the Mezz NIC of the blade server, you need to specify the connection between
the Mezz NIC port and the straight-through module. For details, contact Technical Support.
2.5.3 Internal Connection Between the Direct Module Interface and the Blade Server
Table 2-5 shows the connections between external interfaces of the straight-through module and
the blade servers.
Mezz1
Mezz2
Mezz3
Mezz4
Mezz5
Mezz6
1
4
2
3
5
6
12
LOM P1
LOM P2
Blade ICM
Mid-plane
OM
Embedded

2-10
Table 2-5 Correspondence between external interfaces of the straight-through module and the
blade servers
Model of Blade Server Maximum Number of
Supported Mezz NICs
Correspondence between external
interfaces of the straight-through module and
the blade servers
Half-width single-height blade
server 3
See 2.5.3 1. Correspondence between
external interfaces of the straight-through
module and the half-width single-height
blade server.
Full-width single-height blade
server
6
See 2.5.3 2. Correspondence between
external interfaces of straight-through
module and full-width single-height blade
server (supports up to 6 Mezz NICs).
3
See 2.5.3 3. Correspondence between
external interfaces of straight-through
module and full-width single-height blade
server (supports up to 3 Mezz NICs).
When both full-width single-height blade servers and half-width single-height blade servers are used in a blade
enclosure, check the corresponding external interface of the straight-through module according to the actual
blade server type configured in each slot.
1. Correspondence between external interfaces of the straight-through module and the half-width
single-height blade server
Figure 2-3 shows the 16 FC interfaces on the straight-through module panel, which are numbered
from 1 to 16. Figure 2-7 shows the 16 slots of the half-width single-height blade server installed in
the front slots of the blade server chassis. The slots are numbered 1 to 16.
Figure 2-7 Numbering of slots for the half-width single-height blade server

2-11
As shown in Figure 2-8, when the half-width single-height blade server is installed in the front slots
of the chassis, the external interfaces of the straight-through module have one-to-one
correspondence with the 16 blade servers. That is, port 1 is connected to blade server 1, and users
can access blade server 1 through port 1; port 2 is connected to blade server 2, and users can
access blade server 2 through port 2; and so on.
Note
•For the correspondence between the straight-through modules connected to different slots and the
blade server Mezz NICs, see 2.5.1 Connections Between Straight-Through Modules and Mezz
NICs.
•For details about blade server Mezz NIC ports that are connected to straight-through modules,
contact Technical Support.
Figure 2-8 Internal connections between external interfaces of straight-through module and
half-width single-height blade server
2. Correspondence between external interfaces of straight-through module and full-width
single-height blade server (supports up to 6 Mezz NICs)
Figure 2-3 shows the 16 FC interfaces on the straight-through module panel, which are numbered
from 1 to 16. Figure 2-9 shows the slots for the 8 full-width single-height blade servers installed in
the front slots of the blade server chassis. They are numbered 1, 3, 5, 7, 9, 11, 13, and 15.
ICM
Front
Port 1
Port 2
Port 3
……
Port 4
Port 13
Port 14
Port 15
Port 16
Blade1
Blade3
Blade2
Blade4
Blade13
Blade15
Blade14
Blade16
……
Mid-plane Enclosure