H3C ETH682i User manual

ETH682i Mezz Network Adapter
User Guide
New H3C Technologies Co., Ltd.
https://www.h3c.com/en/
Document version: 6W100-20230218

Copyright © 2023, New H3C Technologies Co., Ltd. and its licensors
All rights reserved
No part of this manual may be reproduced or transmitted 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 user guide describes the specifications, supported features, and configuration methods for
ETH682i Mezz network adapters.
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.
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 [e-mail].
We appreciate your comments.

i
Contents
Safety information··························································································1
General operating safety····································································································································1
Electrical safety··················································································································································1
ESD prevention··················································································································································1
Configuring the network adapter····································································1
Viewing mapping relations between network adapter ports and ICM internal ports ··········································1
Viewing network adapter port information in the operating system····································································1
Linux operation systems ····························································································································1
Windows operating systems ······················································································································2
Installing and removing a network adapter driver in the operating system························································3
Linux operating systems ····························································································································3
Windows operating systems ······················································································································5
Configuring PXE·················································································································································8
Configuring iSCSI···············································································································································9
Configuring iSCSI boot·······························································································································9
Configuring iSCSI SAN····························································································································16
Configuring FCoE·············································································································································23
Configuring FCoE boot·····························································································································23
Configuring FCoE SAN····························································································································28
Configuring NPAR············································································································································37
Configuring SR-IOV ·········································································································································40
Configuring advanced features························································································································43
Configuring VLAN (802.1Q VLAN)···········································································································43
Configuring bonding (Linux)·····················································································································44
Configuring teaming (Windows)···············································································································46
Configuring TCP offloading······················································································································48
Appendix A Specifications and features························································1
Network adapter view·········································································································································1
Specifications·····················································································································································1
Product specifications································································································································1
Technical specifications·····························································································································2
Features·····························································································································································2
Feature compatibility··································································································································2
Feature description ····································································································································3
Appendix B Hardware and software compatibility·········································1
Compatible blade servers ··································································································································1
Compatible ICMs················································································································································2
Network adapters and ICM compatibility····································································································2
Network adapter and ICM interconnection·································································································3
Networking applications·····································································································································5
Appendix C Acronyms··················································································1

1
Safety information
To avoid bodily injury or device damage, read the following information carefully before you operate
the network adapter.
General operating safety
To avoid bodily injury or damage to the device, follow these guidelines when you operate the network
adapter:
•
Only H3C authorized or professional engineers are allowed to install or replace the network
adapter.
•
Before installing or replacing the network adapter, stop all services, power off the blade server,
and then remove the blade server.
•
When disassembling, transporting, or placing the blade server, do not use excessive force.
Make sure you use even force and move the device slowly.
•
Place the blade server on a clean, stable workbench or floor for servicing.
•
To avoid being burnt, allow the blade server and its internal modules to cool before touching
them.
Electrical safety
Clear the work area of possible electricity hazards, such as ungrounded chassis, missing safety
grounds, and wet work area.
ESD prevention
Electrostatic charges that build up on people and other conductors might damage or shorten the
lifespan of the network adapter.
Preventing electrostatic discharge
To prevent electrostatic damage, follow these guidelines:
•
Transport or store the network adapter in an antistatic bag.
•
Keep the network adapters in antistatic bags until they arrive at an ESD-protected area.
•
Place the network adapter on an antistatic workbench before removing it from its antistatic bag.
•
Install the network adapter immediately after you remove it from its antistatic bag.
•
Avoid touching pins, leads, or circuitry.
•
Put away the removed network adapter in an antistatic bag immediately and keep it secure for
future use.
Grounding methods to prevent electrostatic discharge
The following are grounding methods that you can use to prevent electrostatic discharge:
•
Wear an ESD wrist strap and make sure it makes good skin contact and is reliably grounded.
•
Take adequate personal grounding measures, including wearing antistatic clothing and static
dissipative shoes.
•
Use conductive field service tools.
•
Use a portable field service kit with a folding static-dissipating work mat.

1
Configuring the network adapter
The figures in this section are for illusion only.
Viewing mapping relations between network
adapter ports and ICM internal ports
To view the mapping relations between the network adapter ports and ICM internal ports, log in to
OM and access the Blade Servers > Port Mapping page.
Viewing network adapter port information in the
operating system
This section describes how to view the network adapter port information in the operating system. It
uses CentOS 7.5 and Windows Server 2016 as examples.
Linux operation systems
1. Execute the lspci | grep QL41000 command to view PCI device information for the
ETH682i network adapter.
The system can recognize a minimum of two PCI devices for each network adapter. If FCoE
offload and iSCSI offload are enabled, more storage-related PCI devices can be recognized.
Figure 1 Viewing PCI device information
Some network adapters (for example, ETH681i and ETH682i) use chips of the same model. If
such network adapters are used, first execute the lspci -vvvnn -s BUS |grep Product
command to identify the exact model of the target network adapter. The BUS argument
represents the network adapter bus number.
Figure 2 Identifying the network adapter model
If the network adapter is enabled with NPAR, the output from the lspci | grep QLogic
command displays 16 PCI devices.

2
Figure 3 Command output for a network adapter enabled with NPAR
2. Execute the ifconfig -a command to verify that the two network adapter ports are
recognized. The port names are determined by the operating system naming rule. If no ports
are recognized, install the most recent driver and try again. For more information, see "Installing
and removing a network adapter driver in the operating system."
Figure 4 Viewing information about network adapter ports
Windows operating systems
1. Open Network Connections and verify that the ETH682i network adapters can be displayed
correctly.

3
Figure 5 Viewing network adapters
2. If the network adapter is not displayed, open Device Manager, and examine if an Ethernet
controller exists in the Network adapters > Other devices window.
If an Ethernet controller exists, an error has occurred on the driver. Install the most recent
driver and try again. For more information, see "Installing and removing a network adapter
driver in the operating system."
If no Ethernet controllers exist, verify that the network adapter is installed securely.
Figure 6 Viewing network adapters
Installing and removing a network adapter driver
in the operating system
The driver used by the network adapter and the installation method for the driver varies by operating
system. This section uses CentOS 7.5 and Windows Server 2016 as examples.
Linux operating systems
1. Execute the modinfo qede command to view the current driver version.

4
Figure 7 Viewing the driver version
2. If the driver is an .rpm file, run the executable file and install the driver directly.
a. Copy the RPM driver file (for example, kmod-qlgc-fastlinq-8.38.2.0-1.rhel7u5.x86_64.rpm)
to the operating system.
b. Execute the rpm -ivh file_name.rpm command to install the driver.
Figure 8 Installing the driver
c. After the installation finishes, restart the operating system to have the driver take effect.
d. Execute the modinfo qede or ethtool -i ethX command to verify that the driver
version is correct.
The ethX argument represents the port on the network adapter. You can also verify the
driver version by viewing network adapter port information in the operating system. For
more information, see "Viewing network adapter port information in the operating system."
Figure 9 Verifying the driver version
3. If the driver is a .tar.gz compressed file, you must compile it first.
a. Execute the tar -zxvf fastlinq-<ver>.tar.gz command to decompress the file.
b. Execute the cd fastlinq-<ver>command to enter the directory of the source file.

5
c. Execute the make install command to compile the file and install the driver.
Figure 10 Compiling the file and installing the driver
d. After the installation finishes, restart the operating system or execute the rmmod qede and
modprobe qede commands to have the driver take effect.
4. To remove the .rpm file, execute the rpm -e kmod-qlgc-fastlinq command. Restart the
operating system or execute the rmmod qede and modprobe qede commands to load the
old driver.
Windows operating systems
1. Verify the current driver for the network adapter.
a. Click the Start icon to enter the menu.
b. Select Control Panel > Hardware > Device Manager.
Figure 11 Opening Device Manager
c. Right click the port on the network adapter, and then select Properties > Driver.

6
Figure 12 Device Manager
2. Install the driver.
a. Obtain the driver from the H3C official website.
b. Double click the driver and then click Next >.
Figure 13 Installing the driver
c. After the installation finishes, restart the operating system to have the driver take effect.
d. Verify that the driver version has been updated.

7
Figure 14 Verifying the driver version
3. Remove the driver.
As a best practice, remove the driver from the Control Panel > Programs and Features
window. If no drivers are displayed in the window, remove the driver as follows:
a. Click the Start icon to enter the menu page.
b. Select Control Panel > Hardware > Device Manager.
c. Right click the network adapter whose driver is to be removed, select Properties > Driver,
and then click Uninstall.
Figure 15 Removing a driver

8
Configuring PXE
This section describes how to enable PXE on a network adapter in the BIOS. To use the PXE feature,
you must set up a PXE server. You can obtain the setup method for a PXE server from the Internet.
PXE boot is supported only in UEFI boot mode.
To configure PXE:
1. During startup of the server, press Delete or ESC as prompted to enter the BIOS Setup utility.
2. Enable PXE.
a. Click the Advanced tab, select Network Stack Configuration, and then press Enter.
Figure 16 The Advanced page
b. Set Ipv4 PXE Support and Ipv6 PXE Support to Enabled.
Figure 17 Enabling PXE in UEFI mode
3. Configure PXE for the network adapter.
a. Click the Advanced tab, select Network Adapter > Port Level Configuration, and then
press Enter.
Figure 18 Configuration page for the network adapter

9
b. Set Boot Mode to PXE.
Figure 19 Setting Boot Mode to PXE
4. Press F4 to save the configuration.
The server restarts automatically. During startup, press F12 at the POST phase to boot the
server from PXE.
Configuring iSCSI
The iSCSI feature must cooperate with a remote network storage device. The configuration methods
for network storage devices vary by device. For more information, see the related document for the
storage device. This document describes only configuration on the local server.
Configuring iSCSI boot
iSCSI boot is supported only in UEFI boot mode.
To configure iSCSI boot:
1. Enter the BIOS and select the network adapter port to be configured.

10
Figure 20 Selecting the network adapter port to be configured
2. Select Port Level Configuration.
Figure 21 Selecting Port Level Configuration
3. Set Boot Mode to iSCSI (SW) and iSCSI Offload to Enabled. Save the configuration and
restart the server.

11
Figure 22 Configuring iSCSI
4. Enter the BIOS. Click the Advanced tab and select iSCSI Configuration.
Figure 23 Selecting iSCSI Configuration
5. Configure the name of the iSCSI initiator. Select Add an Attempt, and then select the MAC
address of the network adapter port.
For how to identify the network adapter port, see "Viewing network adapter port information in
the operating system."
Choose the network adapter slot and port as required. For more information, see "Network
adapters and ICM compatibility."

12
Figure 24 Selecting Add an Attempt
Figure 25 Selecting the MAC address of the network adapter port
6. Set iSCSI Mode to Enabled. Configure iSCSI parameters and then select save.

13
Figure 26 Configuring iSCSI
7. Select Save Changes and Reset.
Figure 27 Saving the configuration and restarting the server
8. Install the operating system (for example, RHEL 7.5). Specify the network disk as the system
disk.
a. Press eto edit the setup parameters.