Configuring the Gateway in the Network Management Zone

Context

In the virtualization solution for a large or midsize campus network, after the software (including iMaster NCE-Campus software) is installed on servers, you need to configure the gateway in the network management zone. During the configuration, ensure that each network plane of each software server cluster can communicate. Additionally, ensure that each software component can communicate with the campus network.

This section describes how to configure the gateway in the network management zone. If the network management zone where the software (including iMaster NCE-Campus software) is deployed is a data center network, refer to the data center network solution for the networking on the server side and the gateway configuration.

In Figure 4-2, Huawei S6730-H series switches set up a stack to function as the gateway in the network management zone. iMaster NCE-Campus adopts dual network planes and needs to communicate with the device management subnet of the underlay network as well as the user service subnet of the overlay network. The configuration procedure is as follows.

Figure 4-2 Configuring the gateway in the network management zone

Procedure

1. Configure the gateway interface and IP address for each network plane of iMaster NCE-Campus.
   • Two NICs of the server bond in active-backup mode. One NIC interface within the bond is in the active state, and the other is in the backup state. All data is transmitted through the NIC interface in active mode.
     1. Create a VLAN, and add the physical ports connecting the servers to the VLAN of the corresponding network plane in access mode. The following command example adds XGE1/0/1 to VLAN 101.

        <Switch> system-view
        [Switch] vlan batch 101
        [Switch] interface xgigabitethernet 1/0/1
        [Switch-XGigabitEthernet1/0/1] port link-type access
        [Switch-XGigabitEthernet1/0/1] port default vlan 101
        [Switch-XGigabitEthernet1/0/1] quit

     2. Create a VLANIF interface and assign an IP address to it. The following command example creates VLANIF 101.

        [Switch] interface vlanif 101
        [Switch-Vlanif101] ip address 172.16.1.254 24
        [Switch-Vlanif101] quit

   • Two NICs of the server bond in load balancing mode. The two NIC interfaces transmit data packets based on the specified hash policy.
     1. Create an Eth-Trunk interface, and add physical ports connecting the servers to the Eth-Trunk interface. The following command example creates Eth-Trunk 1.

        <Switch> system
        [Switch] vlan batch 101
        [Switch] interface eth-trunk 1
        [Switch-Eth-Trunk1] trunkport gigabitethernet 1/0/1 2/0/1
        [Switch-Eth-Trunk1] quit

     2. Create a VLAN, and add the Eth-Trunk interface to the VLAN of the corresponding network plane in access mode. The following command example adds Eth-Trunk 1 to VLAN 101.

        [Switch] vlan batch 101
        [Switch] interface eth-trunk 1
        [Switch-Eth-Trunk1] port link-type access
        [Switch-Eth-Trunk1] port default vlan 101
        [Switch-Eth-Trunk1] quit

     3. Create a VLANIF interface and assign an IP address to it. The following command example creates VLANIF 101.

        [Switch] interface vlanif 101
        [Switch-Vlanif101] ip address 172.16.1.254 24
        [Switch-Vlanif101] quit

2. Configure the interfaces and VLANs for interconnecting with the core switch, create VLANIF interfaces, and assign IP addresses to the VLANIF interfaces. The underlay network is isolated from the overlay network on the core switch. Therefore, two VLANs are needed for the interconnection between the gateway in the network management zone and the core switch.

   [Switch] vlan batch 20 30
   [Switch] interface eth-trunk 3
   [Switch-Eth-Trunk3] trunkport gigabitethernet 1/1/0/1 2/1/0/1
   [Switch-Eth-Trunk3] port link-type trunk
   [Switch-Eth-Trunk3] port trunk allow-pass vlan 20 30
   [Switch-Eth-Trunk3] quit
   [Switch] interface vlanif 20
   [Switch-Vlanif20] ip address 172.16.20.1 24
   [Switch-Vlanif20] quit
   [Switch] interface vlanif 30
   [Switch-Vlanif30] ip address 172.16.30.1 24
   [Switch-Vlanif30] quit

3. Configure a static route destined for the device management subnet.

   [Switch] ip route-static 192.168.100.0 24 172.16.20.254

4. Configure a static route destined for the user service subnet.

   [Switch] ip route-static 10.1.0.0 16 172.16.30.254