Table 1 lists the hardware to be used in typical networking modes. If there are multiple models in a cell, the hardware of these models is appropriate for this configuration.

Table 1 Hardware compatibility

Configuration example	Hardware compatibility
Configuration example	NIC	Interconnection module	External switch	Backend storage
Example: Configuring Ethernet services (switch module)	· ETH521i · ETH522i · ETH561i · ETH640i · ETH681i · ETH682i	· BX720EF · BX720E · BX1010E · BX1020EF	Ethernet switch	-
Example: Configuring Ethernet services (pass-through module)	· ETH521i · ETH522i · ETH561i · ETH640i · ETH681i · ETH682i	· BT616E · BT1004E	Ethernet switch	-
Example:P Configuring Ethernet services (monitor link)	· ETH521i · ETH522i · ETH561i · ETH640i · ETH681i · ETH682i	· BX720EF · BX720E · BX1010E · BX1020EF	Ethernet switch	-

The configuration examples were created and verified in a lab environment, and all the devices were started with the factory default configuration. When you are working on a live network, make sure you understand the potential impact of every command on your network.

The following information is provided based on the assumption that you have basic knowledge of Ethernet, port aggregation features, H3C blade servers, interconnect modules, and Windows/Linux/ESXi/CAS operating systems.

The following information mainly describes the procedure for configuring the blade server chassis. As a best practice, configure external network settings as needed.

Example: Configuring Ethernet services

Network requirement

As shown in Figure 1, the blade server and interconnect modules are installed in the H3C B16000 blade server chassis. The blade server is installed in slot 12, two interconnect modules are installed in slot 1 and slot 4, and the mezzanine card is installed in the mezzanine card slot 1 of the blade server. The XGE 1/1/9 port of each of the two interconnect modules is connected to the XGE 1/0/49 and XGE 1/0/50 ports of the Ethernet switch.

In this example, the following devices and modules are used: mezzanine card (NIC-ETH561i-Mb-4*10G, "ETH561i"), aggregation interconnect module (BX720E), Ethernet switch (H3C switch).

Figure 1 Example: Configuring Ethernet services

Analysis

· To improve the reliability of external links, you need to aggregate the links over the uplink port on the interconnect module and the downlink port on the aggregation switch.

· To improve the reliability of internal links in the blade server chassis, you need to configure the bonding function under the OS to bind Port 3 and Port 4 of the mezzanine card to a logic port. In this example, the bonding function adopts the active/standby mode.

· In this example, the bonding function adopts the active/standby mode, indicating that either Port 3 or Port 4 on the mezzanine card receives and sends the traffic, while the other serves as the backup. Therefore, you do not need to aggregate the links over the XGE 1/0/24 internal ports of the two interconnect module. If the bonding function uses other modes, you need to aggregate the links over the internal ports of the two interconnect modules.

· As a best practice, disable the STP function of the internal ports on the interconnect modules, to prevent the rebooting or plugging in/out of the blade server from causing the STP of the interconnect modules to start calculating and resulting in short disconnection of external ports on the interconnect modules.

Software versions used

This example was created and verified on SWITCH_SYS-1.00.11 and OM-1.00.11 versions.

Configuration precautions

Make sure that the OS can recognize the ETH561i network adapter correctly. If it cannot, install the network adapter driver according to the ETH561i Mezzanine Card Module User Guide.

Configuration procedure

Querying port information

Query the correspondence among mezzanine cards, internal ports of interconnect modules, and network adapters under the OS according to "Querying port relations."

It can be learned that:

· In this example, Port 3 and Port 4 of mezzanine card 1 are used and are named ens5f2 and ens5f3 under the OS, respectively.

· Ten-gigabitethernet 1/0/24 ports of interconnect modules 1 and 4 are used in this example.

Configuring the mezzanine card

The following information describes the procedure for configuring Linux and Windows operating systems on the blade server.

Procedure for configuring Linux

NOTE:

The following information provides the procedure for configuring the bonding function under Red Hat 7.5.

1. Configure the bonding function of ens5f2 and ens5f3 ports

a. Execute the nmtui command to start the network adapter configuration tool that comes with the system.

[root@localhost]# nmtui

b. Select Edit a connection to edit the network connection, as shown in Figure 2.

Figure 2 Selecting Edit a connection

c. Select Add to add a new network connection, select the type of connection as Bond, and click Create, as shown in Figure 3.

Figure 3 Adding a "bond" connection

d. As shown in Figure 4, set Profile name and Device.

Figure 4 Setting the bond connection

e. Under the BOND Slaves option, select Add and add ens5f2 and ens5f3 slave ports, as shown in Figure 5.

Figure 5 Adding slave ports

f. Set Mode to Active Backup and set the IP address according to the service environment. In this example, the service traffic is transmitted through the VLAN port connected to the bond port. Therefore, set the static IP address of the bond master port to 0.0.0.0/0, as shown in Figure 6.

Figure 6 Setting network parameters

g. Return to the homepage of the nmtui tool, select Add to add a new network connection, select the type of connection as VLAN, and click Create, as shown in Figure 7.

Figure 7 Adding a VLAN port

h. As shown in Figure 8, set Profile name, Device and VLAN id, and configure the IP address of the service network. This example uses the VLAN ID of 2 and the static IP address 100.1.1.2/24.

Figure 8 Setting the IP address of the VLAN slave port connected to the bond port

i. Then, press Esc to return to the configuration screen.

2. Execute the systemctl restart network command to restart the network service.

[root@localhost]# systemctl restart network

3. Execute the ifconfig command to view the Bond1 and Bond1.2 configurations as shown in Figure 9 and Figure 10. Note that the physical addresses of the aggregation port and the two physical network adapters are the same in the active/standby mode.

Figure 9 Viewing the network adapter configuration (I)

Figure 10 Viewing the network adapter configuration (II)

Procedure for configuring Windows

NOTE:

The following information provides the procedure for configuring NIC teaming function on the Windows Server. The Windows Server 2016 is used as an example.

1. Check the correspondence of network adapter ports.

Query the correspondence among mezzanine cards, internal ports of interconnect modules, and network adapters of the OS according to "Querying port relations." In this example, Port 3 and Port 4 of mezzanine card 1 are used and are named Ethernet4 and Ethernet6 under the OS, respectively.

2. Configure the teaming.

a. As shown in Figure 11, click Disabled in Server Manager > Local Server > NIC Teaming to open the configuration screen of NIC Teaming.

Figure 11 Opening the configuration screen of NIC Teaming

b. As shown in Figure 12, click TASKS > NEW Team to create a team.

Figure 12 Creating a team

c. As shown in Figure 13, set the team name and select the network adapter that you want to add to the team, set the appropriate properties in Additional properties, and click OK to create the team.

TIP:

· For descriptions of team properties, see Mezzanine Card User Guide.

· The creation of a team in the Switch Independent mode is slow. Please wait patiently.

Figure 13 Setting the new team

d. As shown in Figure 14, you can see that the state has changed to Enabled. You can also see a new network port named NIC-Team. Click this port to enter the network connection configuration screen.

Figure 14 Viewing the NIC teaming

e. As shown in Figure 15, right-click the network port named NIC-Team and select Properties.

Figure 15 Setting the NIC-Team

f. As shown in Figure 16, set the IP address of the port named NIC-Team. The IP address of 100.1.1.2/24 is used in this example.

Figure 16 Setting the IP address

g. As shown in Figure 17, run the cmd command, and execute the ipconfig -all command in the Windows PowerShell screen. You can see that the IP has been configured.

Figure 17 Confirming the IP address of the port

h. VLAN separation exists in this example. You need to configure VLAN ID for all physical ports (Ethernet4 and Ethernet6) joined the team. Here we use the configuration of Ethernet4 as an example to describe the configuration process. In the Network Connections screen, right-click the network port named Ethernet4 and select Properties, as shown in Figure 18.

Figure 18 Setting the physical port in the team

i. As shown in Figure 19, in the pop-up dialog box, select Configure, enter the Advanced tab, select VLAN ID in the Property drop-down menu, and fill in the added VLAN tag in the Value box. In this example, the value of 2 is used.

Figure 19 Setting the VLAN ID

j. Configure the Ethernet6 port according to the above methods.

Configuring the interconnect module

Interconnecting interconnect modules and mezzanine cards

# Create VLAN 2.

[H3C] vlan2

[H3C-vlan2]quit

# Configure the mode of the Ten-GigabitEthernet 1/0/24 port to trunk and allow VLAN 2 to pass.

[H3C] interface Ten-GigabitEthernet 1/0/24

[H3C-Ten-GigabitEthernet1/0/24] port link-type trunk

[H3C-Ten-GigabitEthernet1/0/24] port trunk permit vlan 2

[H3C-Ten-GigabitEthernet1/0/24] undo port trunk permit vlan 1

[H3C-Ten-GigabitEthernet1/0/24] undo stp enable

[H3C-Ten-GigabitEthernet1/0/24] quit

# Configure the mode of the Ten-GigabitEthernet 2/0/24 port to trunk and allow VLAN 2 to pass.

[H3C] interface Ten-GigabitEthernet 2/0/24

[H3C-Ten-GigabitEthernet2/0/24] port link-type trunk

[H3C-Ten-GigabitEthernet2/0/24] port trunk permit vlan 2

[H3C-Ten-GigabitEthernet2/1/24] undo port trunk permit vlan 1

[H3C-Ten-GigabitEthernet1/0/24] undo stp enable

[H3C-Ten-GigabitEthernet2/0/24] quit

Interconnecting interconnect modules and aggregation switches

# Create a layer-2 aggregation port, add the physical ports to the aggregation group, and allow VLAN 2 to pass.

[H3C] interface Bridge-Aggregation 10

[H3C-Bridge-Aggregation10]

[H3C] interface Ten-GigabitEthernet 1/1/9

[H3C-Ten-GigabitEthernet1/1/9] port link-aggregation group 10

[H3C-Ten-GigabitEthernet1/1/9] quit

[H3C] interface Ten-GigabitEthernet 2/1/9

[H3C-Ten-GigabitEthernet2/1/9] port link-aggregation group 10

[H3C-Ten-GigabitEthernet2/1/9] quit

[H3C] int Bridge-Aggregation 10

[H3C-Bridge-Aggregation10] port link-type trunk

[H3C-Bridge-Aggregation10] port trunk permit vlan 2

[H3C-Bridge-Aggregation10] undo port trunk permit vlan 1

[H3C-Bridge-Aggregation10] quit

# Save the configuration.

[H3C] save

The current configuration will be written to the device. Are you sure? [Y/N]:y

Please input the file name(*.cfg)[flash:/startup.cfg]

(To leave the existing filename unchanged, press the enter key):

Configuring the aggregation switch

# Create VLAN 2.

[H3C] vlan2

[H3C-vlan2]quit

# Create a layer-2 aggregation port, add the physical ports to the aggregation group, and allow VLAN 2 to pass.

[H3C] int Bridge-Aggregation 10

[H3C-Bridge-Aggregation10]

[H3C] interface Ten-GigabitEthernet 1/0/49

[H3C-Ten-GigabitEthernet1/0/49] port link-aggregation group 10

[H3C-Ten-GigabitEthernet1/0/49] quit

[H3C] interface Ten-GigabitEthern 1/0/50

[H3C-Ten-GigabitEthernet1/0/50] port link-aggregation group 10

[H3C-Ten-GigabitEthernet1/0/50] quit

[H3C] int Bridge-Aggregation 10

[H3C-Bridge-Aggregation10] port link-type trunk

[H3C-Bridge-Aggregation10] port trunk permit vlan 2

[H3C-Bridge-Aggregation10] undo port trunk permit vlan 1

[H3C-Bridge-Aggregation10] quit

# You can view the information about the aggregation port and confirm that the aggregation port has been created.

[H3C] display link-aggregation verbose Bridge-Aggregation 10

Loadsharing Type: Shar -- Loadsharing, NonS -- Non-Loadsharing

Port Status: S -- Selected, U -- Unselected, I -- Individual

Port: A -- Auto port, M -- Management port, R -- Reference port

Flags: A -- LACP_Activity, B -- LACP_Timeout, C -- Aggregation,

D -- Synchronization, E -- Collecting, F -- Distributing,

G -- Defaulted, H -- Expired

Aggregate Interface: Bridge-Aggregation10

Aggregation Mode: Static

Loadsharing Type: Shar

Management VLANs: None

Port Status Priority Oper-Key

XGE1/0/49 U 32768 1

XGE1/0/50 S 32768 1

# Create a VLAN port and set the IP address of the port to 100.1.1.1/24.

[H3C] interface vlan 2

[H3C-Vlan-interface2] ip address 100.1.1.1 255.255.255.0

[H3C-Vlan-interface2] quit

# Check the status of VLAN 2 port and confirm that the port is UP.

[H3C-Vlan-interface2]display interface vlan 2 brief

Brief information on interfaces in route mode:

Link: ADM - administratively down; Stby - standby

Protocol: (s) - spoofing

Interface Link Protocol Primary IP Description

Vlan2 UP UP 100.1.1.1

# Save the configuration.

[H3C] save

The current configuration will be written to the device. Are you sure? [Y/N]:y

Please input the file name(*.cfg)[flash:/startup.cfg]

(To leave the existing filename unchanged, press the enter key):

Verifying the configuration

In the OS of the blade server, ping VLAN 2 port on the aggregation switch. Verify that the port can be pinged successfully.

[root@localhost]# ping 100.1.1.2

PING 100.1.1.2(100.1.1.2) 56(84) bytes of data.

64bytes from 100.1.1.2: icmp_seq=1 ttl=255 time=0.808 ms

64bytes from 100.1.1.2: icmp_seq=2 ttl=255 time=0.691 ms

64bytes from 100.1.1.2: icmp_seq=3 ttl=255 time=0.732 ms

64bytes from 100.1.1.2: icmp_seq=4 ttl=255 time=0.679 ms

64bytes from 100.1.1.2: icmp_seq=5 ttl=255 time=0.710 ms

Example: Configuring Ethernet services (pass-through module)

Network requirement

As shown in Figure 20, the blade server and Ethernet pass-through modules are installed in the H3C B16000 blade server chassis. The blade server is installed in slot 3, two Ethernet pass-through modules are installed in slot 1 and slot 4, and the mezzanine card is installed in the mezzanine card slot 1 of the blade server. The XGE 1/1/3 port of each of the two Ethernet pass-through modules is connected to the XGE 1/0/1 or XGE 1/0/2 port of the Ethernet switch.

In this example, the following devices and modules are used: blade server (H3C UniServer B5700 G3), mezzanine card (NIC-ETH522i-Mb-2*10G, "ETH522i"), Ethernet pass-through module (H3C UniServer BT616E), and Ethernet switch (H3C S6800).

In this example, the Red Hat Enterprise Linux 7.5 is installed on the blade server.

The following requirements are expected to be met:

The OS on the blade server can access the external H3C switch, and can still communicate correctly when any pass-through module fails.

Figure 20 Example: Configuring Ethernet service (Ethernet pass-through module)

Analysis

· Before configuration, you need to query the correspondence between the mezzanine card, the external port of the pass-through module, and the mezzanine card port displayed under the OS, to ensure that the correct ports are configured and facilitate the verification after configuration.

· To improve the reliability of internal links of the blade server, you need to configure the bonding function (adopting the active/standby mode) on the mezzanine card ports to bind Port 1 and Port 2 of the mezzanine card to a logic port, so that the blade server can access external networks through the other pass-through module when a pass-through module fails.

· In this example, the bonding function adopts the active/standby mode, indicating that either Port 1 or Port 2 on the mezzanine card receives and sends the traffic, while the other serves as the backup. Therefore, you do not need to aggregate the two links on the switch used to connect the blade server. If the bonding function uses other modes, you need to configure the settings related to the bond mode on the two links.

· In this example, the service traffic between the blade server and the switch is transmitted through the VLAN port. Therefore, you need to configure relevant settings related to VLAN and VLAN ports on the blade server and the switch.

Configuration precautions

Make sure that the blade server's OS can recognize the ETH522i network adapter correctly. If it cannot, install the network adapter driver. For details, see ETH522i Mezzanine Card Module User Guide.