Elastic Compute Service:Configure a secondary ENI

Obtain the information of the ENI in the ECS console (recommended)

1. Log on to the ECS console.

2. In the left-side navigation pane, choose Network & Security > Elastic Network Interfaces.

3. In the top navigation bar, select the region and resource group to which the resource belongs.

4. On the Elastic Network Interfaces page, find the ENI whose information you want to obtain and view its primary private IP address and MAC address in the IP Address and MAC Address columns.

Obtain the information of the ENI from instance metadata

1. Connect to the Linux instance.

   For more information, see Connect to a Linux instance by using a password or key.

2. Run the following commands in sequence to obtain the information of the ENI.

   • Obtain the MAC addresses of the ENIs that are bound to the instance.

     curl http://100.100.100.200/latest/meta-data/network/interfaces/macs/

     Note

     The MAC addresses of ENIs are required to obtain the primary private IP addresses, subnet masks, and gateway addresses of the ENIs.

   • Obtain the primary private IP address of the specified ENI.

     curl http://100.100.100.200/latest/meta-data/network/interfaces/macs/00:16:3e:19:**:**/primary-ip-address

   • Obtain the subnet mask of the specified ENI.

     curl http://100.100.100.200/latest/meta-data/network/interfaces/macs/00:16:3e:19:**:**/netmask

   • Obtain the gateway address of the specified ENI.

     curl http://100.100.100.200/latest/meta-data/network/interfaces/macs/00:16:3e:19:**:**/gateway

The following figure shows the sample command output. In the command output, 00:16:3e:16:**:** is the MAC address of the primary ENI and 00:16:3e:0f:**:** is the MAC address of the secondary ENI.

CentOS 6, CentOS 7, RedHat, or Alibaba Cloud Linux 2 (network-scripts)

If your instance runs an Alibaba Cloud Linux 2, CentOS 6, CentOS 7, or Red Hat operating system and uses the network-scripts network service, you can install the multi-nic-util tool to have ENIs bound to the instance automatically configured. You can also manually modify the ENI configuration files to configure the ENIs. Take note of the following items:

Method 1: Use the multi-nic-util tool to have a secondary ENI automatically configured (recommended)

1. Run the following commands to download and install the multi-nic-util tool:

wget https://image-offline.oss-cn-hangzhou.aliyuncs.com/multi-nic-util/multi-nic-util-0.6.tgz && \
tar -zxvf multi-nic-util-0.6.tgz && \
cd multi-nic-util-0.6 && \
bash install.sh

2. Run the following command to restart the ENI service:

   sudo systemctl restart eni.service

Method 2: Manually modify the configuration file of a secondary ENI to configure the secondary ENI

1. Run the following command to open the configuration file of the secondary ENI:

vi /etc/sysconfig/network-scripts/ifcfg-eth1

2. Press the I key to enter Insert mode, and add the information of the secondary ENI to the configuration file. Then, press the Esc key to exit Insert mode and enter :wq to save and close the file.

   Example of the ENI information to add to the configuration file:

   DEVICE=eth1  # Specify the name of the ENI that you want to configure. 
   BOOTPROTO=dhcp
   ONBOOT=yes
   TYPE=Ethernet
   USERCTL=yes
   PEERDNS=no
   IPV6INIT=no
   PERSISTENT_DHCLIENT=yes
   HWADDR=00:16:3e:0f:**:**  # Use the obtained MAC address of the ENI. 
   DEFROUTE=no  # Specify that the ENI is not the default route. To prevent the default route of the ECS instance from being changed when you run the ifup command to start the secondary ENI, do not set eth1 as the default route.

3. Run one of the following commands to restart the network service:

   • Versions earlier than CentOS 7 and RedHat 7, such as CentOS 6 and RedHat 6:

   sudo service network restart

   • CentOS 7 or later, RedHat 7 or later, and Alibaba Cloud Linux 2:

   sudo systemctl restart network

Alibaba Cloud Linux 2 (systemd-networkd)

If your instance runs an Alibaba Cloud Linux 2 operating system and uses the systemd-networkd network service, you must manually modify the ENI configuration file to configure an ENI.

1. Run the following command to open the configuration file of the secondary ENI:

   vi /etc/systemd/network/60-eth1.network

2. Press the I key to enter Insert mode, and add the information of the secondary ENI to the configuration file. Then press the Esc key to exit Insert mode and enter :wq to save and closet the file.

   You can assign a dynamic or static IP address to the secondary ENI. You can use one of the following methods based on your requirements. The following section provides an example of the ENI information to add to the configuration file:

   • Assign a dynamic IP address to the secondary ENI by using Dynamic Host Configuration Protocol (DHCP).

     [Match]
     Name=eth1 # Specify the name of the ENI that you want to configure. 
     
     [Network]
     DHCP=yes
     
     [DHCP]
     UseDNS=yes

   • Assign a static IP address to the secondary ENI.

     [Match]
     Name=eth1 # Specify the name of the ENI that you want to configure. 
     
     [Network]
     Address=192.168.**.*2/24 # Specify the static IP address and subnet mask to be assigned.

     Note

     In the preceding example, 192.168.**.*2 is the primary private IP address and the /24 subnet mask bit corresponds to the 255.255.255.0 subnet mask.

3. Run the following command to restart the network service:

   sudo systemctl restart systemd-networkd

Ubuntu or Debian

If your instance runs a Ubuntu or Debian operating system, you must modify the configuration file of the secondary ENI based on the image version.

• Ubuntu 14.04, Ubuntu 16.04, or Debian

  1. Run the following command to open the configuration file of the secondary ENI:

     vi /etc/network/interfaces

  2. Press the I key to enter Insert mode, and add the information of the secondary ENI to the configuration file. Then press the Esc key to exit Insert mode and enter :wq to save and close the file.

     Example of the ENI information to add to the configuration file:

     auto eth0
     iface eth0 inet dhcp
     
     auto eth1  # Specify the name of the ENI that you want to configure. 
     iface eth1 inet dhcp

     Note

     The eth0 primary ENI is configured in the same configuration file as the eth1 secondary ENI. You must add the information of the primary ENI to the configuration file.

  3. Run one of the following commands to restart the network service:

     • Ubuntu 14.04:

       sudo service networking restart

     • Ubuntu 16.04 and Debian:

       sudo systemctl restart networking

     The configurations of the secondary ENI take effect regardless of whether the following alert notification appears. You can run the ip address show command to check whether the IP address of the secondary ENI can be recognized.

• Ubuntu 18.04

  1. Run the following command to open the configuration file of the secondary ENI:

  vi /etc/netplan/eth1-netcfg.yaml

  2. Press the I key to enter Insert mode, and add the information of the secondary ENI to the configuration file. Then press the Esc key to exit Insert mode and enter :wq to save and close the file.

     Note

     When you modify the configuration file, take note of the following items:

     • The configuration file is in the YAML format. Follow the YAML syntax rules when you configure the file.

     • Use spaces for indentation in YAML files. Tabs are not supported.

     • We recommend that you copy information from the default /etc/netplan/99-netcfg.yaml configuration file to prevent format issues.

     Example of the ENI information to add to the configuration file:

     network:
       version: 2
       renderer: networkd
       ethernets:
         eth1:
           dhcp4: yes
           dhcp6: no

  3. Run the following command for the configurations to take effect:

  netplan apply

SUSE or openSUSE

If your instance runs a SUSE or openSUSE operating system, you must manually modify the ENI configuration file to configure the secondary ENI.

1. Run the following command to open the configuration file of the secondary ENI:

   vi /etc/sysconfig/network/ifcfg-eth1

2. Press the I key to enter Insert mode, and add the information of the secondary ENI to the configuration file. Then press the Esc key to exit Insert mode and enter :wq to save and close the file.

   In the following example, a dynamic IP address is assigned to the secondary ENI by using DHCP.

   BOOTPROTO='dhcp4'
   STARTMODE='auto'
   USERCONTROL='no'

3. Run one of the following commands to restart the network service:

   • Versions earlier than SUSE Linux Enterprise Server 12 and openSUSE 13.2:

     sudo service network restart

   • SUSE Linux Enterprise Server 12 or later, and openSUSE 13.2 or later:

     sudo systemctl restart network

Configure routes for a secondary ENI bound to an instance that runs an Alibaba Cloud Linux 2 or CentOS 7 operating system

1. Run the following command to query the route information:

   route -n

   Sample command outputs:

   • The following command output shows only the route information of the eth0 primary ENI. No routes are configured for the eth1 secondary ENI. You must perform the subsequent operations to configure routes for the secondary ENI.

   • The following command output shows the route information of both the eth0 primary ENI and the eth1 secondary ENI. You do not need to perform subsequent operations to configure routes for the secondary ENI. If the configured routes do not meet your requirements, you can modify the route configurations.

2. Run the following commands to configure the default route:

   ip -4 route add default via 192.168.**.253 dev eth1 metric 1001 && \
   ip -4 route add default via 192.168.**.253 dev eth1 table 1001 && \
   ip -4 rule add from 192.168.**.*2 lookup 1001

   Note

   You can run the preceding commands to add the default route for the eth1 secondary ENI, create a route table, and then attach a routing policy to the table. In this example, a route table named table 1001 is created. We recommend that you keep the name of the route table the same as the metric value in the default route of the ENI. 192.168.**.253 is the gateway address and 192.168.*.*2 is the primary private IP address of the eth1 secondary ENI. Replace the parameter values with the actual values.

3. Run the following commands to query the created route table and routing policy:

   ip route list table 1001 && \
   ip rule list

   The following command output shows that the route table and routing policy are created.

4. Configure routes to automatically update on instance startup.

   After you configure routes for the eth1 secondary ENI, you must configure the routes to automatically update on instance startup. Otherwise, the routes become invalid after the instance is restarted.

   1. Run the following command to open the /etc/rc.local file:

      vim /etc/rc.local

   2. Press the I key to enter Insert mode, add the following content, press the Esc key to exit Insert mode, and then enter :wq to save and close the file.

      ip -4 route add default via 192.168.**.253 dev eth1 metric 1001
      ip -4 route add default via 192.168.**.253 dev eth1 table 1001
      ip -4 rule add from 192.168.**.*2 lookup 1001

   3. Run the following command to grant execute permissions on the /etc/rc.local file:

      sudo chmod +x /etc/rc.local

Configure routes for a secondary ENI bound to an instance that runs a CentOS 8 operating system

1. Run the following command to query the route information:

   route -n

   The following command output shows the route information of both the eth0 primary ENI and the eth1 secondary ENI.

2. Create a script for configuring routes.

   1. Run the following command to create and open the /home/route.sh file:

      vi /home/route.sh

   2. Press the I key to enter Insert mode, add the following content, press the Esc key to exit Insert mode, and then enter :wq to save and close the file.

      Note

      The following sample script shows how to create a route table and attach a routing policy to the route table for the eth1 secondary ENI. In this example, a route table named table 1001 is created, 192.168.**.253 is the gateway address, and 192.168.*.*2 is the primary private IP address of the eth1 secondary ENI.

      #!/bin/bash
      
      i=0
      while true; do
              /usr/sbin/ip -4 route add default via 192.168.**.253 dev eth1 table 1001
              if [ $? -eq 0 ]; then
                      break
          fi
              sleep 3
              let i++
              if [ $i -gt 10 ]; then
                      exit -1
              fi
      done
      
      i=0
      while true; do
              /usr/sbin/ip -4 rule add from 192.168.**.*2 lookup 1001
              if [ $? -eq 0 ]; then
                      break
          fi
              sleep 3
              let i++
              if [ $i -gt 10 ]; then
                      exit -1
              fi
      done

3. Run the following command to configure the default route:

   sh /home/route.sh

4. Run the following commands to query the created route table and routing policy:

   ip route list table 1001 && \
   ip rule list

   A command output similar to the following one is returned.

5. Configure routes to automatically update on instance startup.

   After you perform the preceding steps to configure routes for the eth1 secondary ENI, you must perform the following steps to configure the routes to automatically update on instance startup. Otherwise, the routes become invalid after the instance is restarted.

   1. Run the following command to open the /etc/rc.local file:

      vim /etc/rc.local

   2. Press the I key to enter Insert mode, add the following content, press the Esc key to exit Insert mode, and then enter :wq to save and close the file.

      sh /home/route.sh

   3. Run the following command to grant execute permissions on the /etc/rc.local file:

      sudo chmod +x /etc/rc.local