Related Manuals for H3C ETH521i
Summary of Contents for H3C ETH521i
- Page 1 ETH521i Mezz Network Adapter User Guide New H3C Technologies Co., Ltd. https://www.h3c.com/en/ Document version: 6W100-20230224...
- 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 ETH521i 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.
-
Page 6: Table Of Contents
Configuring TCP offloading ······················································································································ 39 FAQs ············································································································· 1 iSCSI boot cannot be used to install H3C CAS ································································································· 1 Port goes down after the network adapter speed is set to 1 Gbps ···································································· 1 Virtual port created through NPAR configuration cannot be switched to FCoE mode ······································· 1 Appendix A Specifications and features ························································... -
Page 7: Safety Information
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. -
Page 8: Configuring The Network Adapter
Linux operation systems Execute the command to view PCI device information for the lspci | grep BCM57840 ETH521i network adapter. The four PCI devices represent the four ports of the network adapter. Figure 1 Viewing PCI device information Execute the... -
Page 9: Windows Operating Systems
Figure 3 Command output for a network adapter enabled with NPAR Windows operating systems Open Network Connections and verify that the Qlogic 57840 adapters can be displayed correctly, which indicates that the ETH521i network adapters are installed correctly. Figure 4 Viewing network adapters... -
Page 10: Installing And Removing A Network Adapter Driver In The Operating System
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: Windows Operating Systems
d. Execute the – command to verify that the driver modinfo bnx2x ethtool i ethX version is correct. argument represents the port on the network adapter. ethX Figure 8 Verifying the driver version If the driver is a .tar.gz compressed file, you must compile it first. a. - Page 12 Right click the port on the network adapter, and then select Properties > Driver. Figure 11 Device Manager Install the driver. a. Obtain the driver from the H3C official website. b. Double click the driver and then click Next >.
- Page 13 Figure 12 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. Figure 13 Verifying the driver version Remove the driver. a. Click the Start icon to enter the menu page. b.
-
Page 14: Configuring Pxe
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. -
Page 15: Configuring Iscsi
b. Set Legacy Boot Protocol to PXE. Figure 17 Enabling PXE in legacy mode 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. - Page 16 Figure 18 Pressing e to edit the setup parameters b. Enter the ip=ibft string after quiet, and then press Ctrl-x. Figure 19 Adding the ip=ibft string c. Click INSTALLATION DESTINATION.
- Page 17 Figure 20 Clicking INSTALLATION DESTINATION d. On the page that opens, click Add a disk… to add a network disk. Figure 21 Adding a network disk e. Select the target network disk, and click Done at the upper left corner. Figure 22 Selecting the target network disk f.
-
Page 18: Configuring Iscsi San
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 19 Figure 25 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 26 Adding the address information about the peer device d.
- Page 20 Figure 27 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 21 Figure 29 Disk Management c. Right click the disk name, and then select Online. Figure 30 Bringing the disk online d. Right click the disk name, and then select Initialize Disk.
- Page 22 Figure 31 Initializing the disk e. Right click the Unallocated area to assign a volume to the disk as prompted. Figure 32 Assigning a volume to the disk...
- Page 23 Figure 33 Volume assignment completed Access This PC and verify that the new volume has been added. Figure 34 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 24 Figure 35 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 36 Configuring the name of the local iSCSI initiator Execute the –...
-
Page 25: Configuring Fcoe
Figure 39 Viewing the newly-added network disks NOTE: In this example, two volumes have been created on the storage server so that two network disks are added. Execute the command to format the newly-added disks. mkfs Figure 40 Formatting a newly-added disk Execute the command to mount the disk. - Page 26 Click Policy Management > Policy Application. In Policy Application List, select a compute node slot, specify a network policy, and click Apply. In the dialog box that opens, click OK. Install the operating system (for example, RHEL 7.5) and specify the network disk as the system disk.
- Page 27 Figure 44 Clicking INSTALLATION DESTINATION a. Click Add a disk to add a network disk. Figure 45 Adding a network disk e. On the page that opens, select the target network disk, and then click Done in the upper left corner.
-
Page 28: Configuring Fcoe San
Configuring FCoE SAN This document uses Windows, RHEL 7.5, and CAS E0706 as examples to describe how to configure FCoE SAN for the network adapter. Windows operating systems Configure FCoE on the FCoE storage device and switching fabric modules and make sure the FCoE link is unblocked. - Page 29 Right click the disk name and select Online. Figure 49 Making the disk online Right click the disk name and select Initialize Disk. Figure 50 Initializing the disk Right click the Unallocated area and assign a volume to the disk as prompted.
- Page 30 Figure 51 Assigning a volume to the disk Volume assignment has finished. Figure 52 Volume assignment completed Access This PC and verify that the new volume has been added.
- Page 31 Figure 53 Verifying the new volume Red Hat systems Configure FCoE on the FCoE storage device and switching fabric modules and make sure the FCoE link is unblocked. For how to configure FCoE on a switching fabric module, see the related command reference and configuration guide.
- Page 32 Figure 56 Creating and copying a configuration file for the FCoE port Execute the command to edit and save the configuration file. Make sure the vi cfg-ethM value of the FCOE_ENABLE field is yes and the value of the DCB_REQUIRED field is no. Figure 57 Editing the configuration file Execute the command to set...
- Page 33 Configure FCoE on the FCoE storage device and ICMs and make sure the FCoE link is unblocked. For how to configure FCoE on an ICM, see the related command reference and configuration guide and H3C UniServer B16000 Configuration Examples. Access the operating system through KVM or remote login.
- Page 34 Figure 62 Selecting Local Command Shell If you access the operating system through remote login (for example, SSH), connect to the CLI of the operating system. Execute the commands to enable the service fcoe start service lldpad start FCoE and LLDP services, respectively. Figure 63 Enabling the FCoE and LLDP services Execute the commands to verify...
- Page 35 Figure 65 Creating and copying a configuration file for the FCoE port Execute the command to edit and save the configuration file. Make sure the vi cfg-ethM value of the FCOE_ENABLE field is yes and the value of the DCB_REQUIRED field is no. Figure 66 Editing the configuration file Execute the command to set...
-
Page 36: Configuring Npar
Figure 69 Verifying that a subinterface for ethM has been created 10. Execute the command to view the newly-added network disk. lsblk Before viewing the newly-added network disk, make sure the related configuration has been finished on the network storage device. Figure 70 Viewing the newly-added network disk 11. - Page 37 Figure 71 Advanced screen Select SR-IOV Support and set it to Enabled. Press ESC until you return to the BIOS Setup main screen. Figure 72 Setting SR-IOV Support to Enabled Select Socket Configuration > IIO Configuration > Intel@ VT for Directed I/O (VT-d), and then press Enter.
- Page 38 Figure 75 Configuring Multi-Function Mode During startup, press E. Press the arrow keys to turn pages. Add intel_iommu=on to the specified position to enable IOMMU. Press Ctrl-x to continue to start the server. Figure 76 Enabling IOMMU After you enter the operating system, execute the command to verify dmesg | grep IOMMU that IOMMU is enabled.
- Page 39 Figure 78 Assigning VFs to a PF port 10. Execute the virt-manager command to run the VM manager. Select File > New Virtual Machine to create a VM. Figure 79 Creating a VM 11. On the New Virtual Machine page, add a virtual NIC as instructed by the callouts in Figure Figure 80 Adding a virtual NIC 12.
-
Page 40: Configuring Advanced Features
Configuring advanced features Configuring VLAN Configuring 802.1Q VLAN This section uses RHEL 7.5 as an example. To configure 802.1Q VLAN in the operating system: Execute the command to load the 802.1Q module. modprobe 8021q Execute the command ip link add link ethX name ethX.id type vlan id id to create a VLAN interface on a physical port. - Page 41 of a port on the network adapter. For example, if a network adapter has four ports, you can switch to the network adapter by specifying any of the four port numbers. Enable QinQ. a. Execute the command to uninstall the driver. rmmod bnx2x b.
-
Page 42: Configuring Bonding (Linux)
b. Set QINQ VLAN mode to QINQ and configure the port VLAN ID and VLAN priority for the virtual NIC. Figure 85 Configuring QinQ in NPAR mode Configuring bonding (Linux) This section uses RHEL 7.5 as an example to describes how to configure bonding in mode 6. To configure bonding in mode 6: Execute the command in the /etc/sysconfig/network-scripts/ directory to... - Page 43 Figure 86 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 87 Editing the configuration file for a slave interface Execute the command to restart the network service and have...
-
Page 44: Configuring Teaming (Windows)
Figure 89 Viewing information about bond0 Figure 90 Viewing information about the network adapter (1) Figure 91 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 45 Figure 92 Entering the NIC Teaming page Select TASKS > New Team to create a team. Figure 93 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.
-
Page 46: Configuring Tcp Offloading
Figure 94 Configuring a new team After team creation finishes, you can view network adapter OneTeam on the Network Connections page. Figure 95 Viewing the new network adapter Configuring TCP offloading Execute the – command to view the support and enabling state for the ethtool k ethx offload features. - Page 47 Figure 96 Viewing the support and enabling state for the offload features Execute the – command to enable or disable an offload ethtool K ethX feature on/off feature. The argument represents the port name of the network adapter. The ethx feature argument represents the offload feature name.
-
Page 48: Faqs
H3C CAS Symptom When iSCSI boot is used to install H3C CAS on a mirrored storage volume for the blade server, the system can identify the storage IQN but cannot access the storage during disk selection. -
Page 49: Appendix A Specifications And Features
It supports applications such as NIC, iSCSI, and FCoE to help realize network convergence. Figures in this section are for illustration only. Network adapter view The ETH521i network adapter can be applied to 2-processor half-width, 2-processor full-width, and 4-processor full-width blade servers. For the installation positions of the network adapter, see "Compatible blade servers."... -
Page 50: Technical Specifications
Duplex mode Full duplex 802.1p, 802.1q, 802.3ad, 802.3ae, 802.3x, 802.1Qbb, 802.1Qaz, Standards 802.1Qau Technical specifications Table 2 ETH521i Mezz network adapter technical specifications Category Item Specifications Dimensions (H 25.05 × 61.60 × 95.00 mm (0.99 × 2.43 × 3.74 in) Physical ×... -
Page 51: Feature Description
Feature Supported √* (Only in UEFI mode) FCoE Boot √ iSCSI √* (Only in UEFI mode) iSCSI Boot √ SR-IOV √* VMDq √* Multiple Rx Queues (RSS) √* TCP/IP Stateless Offloading √* TCP/IP Offload Engine (TOE) Wake-on-LAN × RDMA × √... - Page 52 Each physical port on the ETH521i network adapter can be divided into two PFs and the entire network adapter can be divided into eight PFs. SR-IOV All the four ports on the network adapter support SR-IOV. SR-IOV allows users to integrate network hardware resources and multiple VMs to operate on the integrated hardware.
- Page 53 ARP negotiation. The bonding driver intercepts the ARP replies sent by the local device and changes the source MAC address into a unique MAC address of a backup device in bonding, allowing different peers to communicate with different MAC addresses. This mode is used commonly.
-
Page 54: Appendix B Hardware And Software Compatibility
For operating systems compatible with the network adapter, contact Technical Support. Compatible blade servers Table 4 Compatible blade servers Blade server model Blade server type Network adapter slots Applicable slots H3C UniServer B5700 2-processor half-width Mezz1, Mezz2, Mezz3 H3C UniServer B5800 2-processor full-width Mezz1, Mezz2, Mezz3 H3C UniServer B7800... - Page 55 Figure 99 Network adapter installation positions on a 2-processor half-width blade server Figure 100 Network adapter installation positions on a 2-processor full-width blade server...
-
Page 56: Compatible Icms
Figure 101 Network adapter installation positions on a 4-processor full-width blade server Compatible ICMs Network adapters and ICM compatibility For information about ICM and mezzanine network adapter compatibility, contact Technical Support. Network adapter and ICM interconnection For details about ICM and mezzanine network adapter connections, contact Technical Support. Network adapters connect to ICMs through the mid plane. - Page 57 Figure 102 Network adapter and ICM mapping relations (2-processor half-width or full-width blade server) LOM P1 LOM P2 Embedded Mezz1 Mid-plane Mezz2 Mezz3 Blade For network adapters installed in a 4-processor full-width blade server, their mapping relations with ICMs are as shown in Figure 103.
- Page 58 Figure 103 Network adapter and ICM mapping relations (4-processor full-width blade server) LOM P1 LOM P2 Embedded Mezz1 Mid-plane Mezz2 Mezz3 Mezz4 Mezz5 Mezz6 Blade...
-
Page 59: Networking Applications
Figure 104 ICM slots Networking applications As shown in Figure 105, the network adapters are connected to the ICMs. Each internal port of the ICMs support 10GE 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 105 Mezzanine network and ICM interconnection... -
Page 60: Appendix C Acronyms
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 Storage Area Network SR-IOV Single Root I/O Virtualization...
Need help?
Do you have a question about the ETH521i and is the answer not in the manual?
Questions and answers