Page 1
ETH681i Mezz Network Adapter User Guide New H3C Technologies Co., Ltd. https://www.h3c.com/en/ Document version: 6W100-20230213...
Page 2
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.
Page 3
Preface This user guide describes the specifications, supported features, and configuration methods for ETH681i Mezz network adapters. This preface includes the following topics about the documentation: • Audience. • Conventions. • Documentation feedback. Audience This documentation is intended for: •...
Page 4
Symbols Convention Description An alert that calls attention to important information that if not understood or followed WARNING! can result in personal injury. An alert that calls attention to important information that if not understood or followed CAUTION: can result in data loss, data corruption, or damage to hardware or software. An alert that calls attention to essential information.
Page 5
Documentation feedback You can e-mail your comments about product documentation to info@h3c.com. We appreciate your comments.
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 ICMs ······························································ 1 Viewing the identification status of network adapter ports in the operating system ··········································· 1 Linux operation systems ····························································································································...
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.
Execute the command to view PCI device information for the lspci | grep QL41000 ETH681i network adapter. The system can identify a minimum of two PCI devices for each network adapter, which corresponds to two network adapter ports. Figure 1 Viewing PCI device information Execute the command to verify that the two network adapter ports are identified.
| grep QL41000 Figure 3 Information about a network adapter enabled with NPAR Windows operating systems Open Network Connections and verify that the Qlogic FastLinQ QL41202H network adapters can be displayed correctly. This indicates that the ETH681i network adapter has been identified.
Figure 4 Viewing network adapters 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 ...
Page 11
Figure 6 Viewing the driver version Installing the driver 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 Verifying the driver version If the driver is a .tar.gz compressed file, you must compile it first. a. Execute the t command to decompress the file. ar -zxvf fastlinq-<ver>.tar.gz b. Execute the command to enter the directory of the source file. cd fastlinq-<ver>...
Page 13
Figure 10 Opening Device Manager Right click the port on the network adapter, and then select Properties > Driver. Figure 11 Device Manager Installing the driver Obtain the driver from the H3C official website. Double click the driver and then click Next >.
Page 14
Figure 12 Installing the driver After the installation finishes, restart the operating system to have the driver take effect. Verify that the driver version has been updated. Figure 13 Verifying the driver version Uninstalling the driver. Click the Start icon to enter the menu page. Select Control Panel >...
Figure 14 Removing a driver 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. To configure PXE: During startup of the server, press Delete or ESC as prompted to enter the BIOS Setup utility.
b. Set Boot Mode to PXE. Figure 17 Setting Boot Mode to PXE 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.
Page 17
Figure 18 Selecting iSCSI Configuration Configure the IQN, select Add an Attempt, and select a network port based on the MAC address. NOTE: Select the correct mezzanine network adapter slot and port number. For more information, see "Feature compatibility." Figure 19 Mezzanine network adapter configuration Set iSCSI Mode to Enabled.
Page 18
Figure 20 Configuring iSCSI On the Save&Exit screen, select Save Changes and Reset. Figure 21 Saving the configuration and restarting the server Install the operating system (for example, RHEL 7.5). Specify the system disk as the network disk. a. Press e to edit the setup parameters.
Page 19
Figure 22 Pressing e to edit the setup parameters b. Enter the ip=ibft string after quiet, and then press Ctrl-x. Figure 23 Adding the ip=ibft string c. Click INSTALLATION DESTINATION.
Page 20
Figure 24 Clicking INSTALLATION DESTINATION d. On the page that opens, click Add a disk… to add a network disk. Figure 25 Adding a network disk e. Select the target network disk, and click Done at the upper left corner. The network disk is now specified as the system disk.
You can continue to install the operating system. Configuring iSCSI SAN This document uses Windows and RHEL 7.5 as examples to describe how to configure iSCSI SAN for the network adapter. Windows operating systems Assign an IP address to the network interface on the network adapter that connects to the iSCSI network storage device.
Page 22
Figure 29 Configuring the name of the iSCSI initiator c. Click the Discovery tab and click Discover Portals to add the address information about the peer device (network storage device). Figure 30 Adding the address information about the peer device d.
Page 23
Figure 31 Connecting the target Adding the network disk. Before adding the network disk, make sure the related configuration has been completed on the network storage device. a. Open Control Panel, and then select Hardware > Device Manager > Storage controllers. Right click the iSCSI adapter, and then select Scan for hardware changes.
Page 24
Figure 33 Disk Management c. Right click the disk name, and then select Online. Figure 34 Bringing the disk online d. Right click the disk name, and then select Initialize Disk.
Page 25
Figure 35 Initializing the disk e. Right click the Unallocated area to assign a volume to the disk as prompted. Figure 36 Assigning a volume to the disk...
Page 26
Figure 37 Volume assignment completed Open This PC, and verify that the new volume has been added. Figure 38 Verifying the new volume Red Hat systems Before configuring iSCSI SAN, make sure the iSCSI client software package has been installed on the server.
Page 27
Figure 39 Configuring the local IP address Execute the command in the /etc/iscsi directory to view the cat initiatorname.iscsi IQN of the local iSCSI initiator. If no IQN is specified, use the command to specify one manually. Figure 40 Configuring the name of the local iSCSI initiator Execute the command to probe the iscsiadm -m -discovery -t st -p target-ip...
Execute the command to mount the disk. mount Figure 45 Mounting the disk Configuring NPAR Enter the BIOS, click the Advanced tab, and select NIC-ETH681i-Mb-2x25G. Return to the previous screen, select Partitioning Mode, and change the mode from Default to NPAR.
Figure 48 Configuring PF parameters Save the configuration and restart the server. Configuring SR-IOV Enter the BIOS Setup utility. Select Advanced > PCI Subsystem Settings, and then press Enter. Figure 49 Advanced screen Select SR-IOV Support and set it to Enabled. Press ESC until you return to the BIOS Setup main screen.
Page 31
Select Socket Configuration > IIO Configuration > Intel@ VT for Directed I/O (VT-d), and then press Enter. Figure 51 Socket Configuration screen Select Intel@ VT for Directed I/O (VT-d) and set it to Enable. Press ESC until you return to the BIOS Setup main screen.
Page 32
Figure 54 Enabling IOMMU After you enter the operating system, execute the command to verify dmesg | grep IOMMU that IOMMU is enabled. Figure 55 Verifying that IOMMU is enabled Execute the command echo NUM > /sys/class/net/ethX/device/sriov_numvfs to assign a specified number of VFs to a PF port. argument represents the number of VFs to be assigned.
Figure 57 Creating a VM 11. On the New Virtual Machine page, add a virtual NIC as instructed by the callouts in Figure Figure 58 Adding a virtual NIC 12. Install the vNIC driver and execute the ifconfig ethVF hw ether xx:xx:xx:xx:xx:xx command to configure an MAC address for the vNIC.
Execute the command ip link add link ethX name ethX.id type vlan id id to create a VLAN interface on a physical port. The argument represents the physical port ethX name. The argument represents the VLAN ID. Execute the – command to verify that the VLAN interface has been d link show ethX.id created successfully.
Page 35
Figure 61 Configuring bond0 Edit the configuration file for a slave interface. Execute the command and vi ifcfg-ethX add the following information to the configuration file: ONBOOT=yes MASTER=bond0 SLAVE=yes For other slave interfaces to be added to bond0, repeat this step. Figure 62 Editing the configuration file for a slave interface Execute the command to restart the network service and have...
Figure 64 Viewing information about bond0 Figure 65 Viewing information about the network adapter (1) Figure 66 Viewing information about the network adapter (2) Configuring teaming (Windows) Open Server Manager, and then select Local Server > NIC Teaming > Disabled to enter the NIC Teaming page.
Page 37
Figure 67 Entering the NIC Teaming page Select TASKS > New Team to create a team. Figure 68 Creating a team Configure the team name and select the network adapters to be added to the team. Select Additional properties, configure the properties, and then click OK. Team creation in Switch Independent mode takes a long time.
Figure 69 Configuring a new team After team creation finishes, you can view the network adapter 111 on the Network Connections page. Figure 70 Viewing the new network adapter Configuring TCP offloading TCP offloading is a TCP acceleration technology. On a high speed Ethernet, for example, 10-GE Ethernet, processing TCP/IP packet headers consumes great CPU resources.
Page 39
Offload allocates some data processing work (for example, fragmentation and reassembly) which should be done by the operating system to the NIC hardware to reduce CPU resource consumption and enhance processing performance. Features related to TCP are as follows: • TCP segmentation offload (TSO)—Segments TCP packets.
It supports NIC and iSCSI applications. Figures in this section are for illustration only. Network adapter view The ETH681i mezzanine network adapter can be applied to 2-processor half-width, 2-processor full-width, and 4-processor full-width B16000 blade servers. For the installation positions of the network adapter, see "Compatible blade...
NPAR NPAR divides network adapter ports into multiple partitions based on the number of PFs. Each port on the ETH681i network adapter can be divided into eight partitions and a network adapter can be divided into 16 partitions. SR-IOV Both ports on the network adapter support SR-IOV.
Page 43
The network adapter supports 0 to 96 VFs for each PF. VLAN (802.1Q VLAN) Each port on the network adapter supports a maximum of 4094 VLANs. A network adapter only transmits packets, and does not tag or untag packets. The VLAN ID is in the range of 1 to 4094 and is assigned by the operating system.
Page 44
direction. If a large amount of traffic goes to the same destination address, the traffic will be sent by the same physical NIC. • Hyper-V port mode—Transmits data out of different physical NICs bound to virtual NICs on a per-virtual NIC basis, instead of a per-VM basis. This mode has higher efficiency if compared with the address hash mode.
Figure 75 Network adapter installation positions on a 2-processor full-width blade server Figure 76 Network adapter installation positions on a 2-processor full-width blade server Compatible ICMs Network adapters and ICM compatibility The network adapter supports the following ICMs:...
• H3C UniServer BX1010E • H3C UniServer BT616E • H3C UniServer BT1004E Network adapter and ICM interconnection Network adapters connect to ICMs through the mid plane. The mapping relations between a network adapter and ICMs depend on the blade server on which the network adapter resides. For installation...
Networking applications As shown in Figure 80, the network adapters are connected to the ICMs. Each internal port of the ICMs support 25GE service applications, and the external ports are connected to the Internet to provide Internet access for the blade server on which the network adapter resides. Figure 80 Mezzanine network and ICM interconnection...
Appendix C Acronyms Acronym Full name Fiber Channel FCoE Fiber Channel Over Ethernet iSCSI Internet Small Computer System Interface NCSI Network Controller Sideband Interface NPAR NIC Partitioning PCIe Peripheral Component Interconnect Express Physical Function Preboot Execute Environment RDMA Remote Direct Memory Access RoCE RDMA over Converged Ethernet Storage Area Network...
Need help?
Do you have a question about the ETH681i and is the answer not in the manual?
Questions and answers