Elastic Network Interface

Operation Guide

Product Documentation

Copyright Notice

©2013-2026 Tencent Cloud. All rights reserved.

Copyright in this document is exclusively owned by Tencent Cloud. You must not reproduce, modify, copy or distribute in any way, in whole or in part, the contents of this document without Tencent Cloud's the prior written consent.

Trademark Notice

All trademarks associated with Tencent Cloud and its services are owned by the Tencent corporate group, including its parent, subsidiaries and affiliated companies, as the case may be. Trademarks of third parties referred to in this document are owned by their respective proprietors.

Service Statement

This document is intended to provide users with general information about Tencent Cloud's products and services only and does not form part of Tencent Cloud's terms and conditions. Tencent Cloud's products or services are subject to change. Specific products and services and the standards applicable to them are exclusively provided for in Tencent Cloud's applicable terms and conditions.

Contents

Operation Guide

Operations Overview

Last updated：2024-10-23 10:24:14

When using ENIs, you may have some questions about how to create and query ENIs, bind ENIs to and unbind ENIs from CVMs, and modify primary private IPs. This document describes some common operations for using ENIs and related products.

Common Operations

Creating an ENI
Binding to a CVM
Unbinding from a CVM
Setting Service Levels
Modifying Primary Private IPs
Viewing ENI Information
Deleting an ENI
Requesting Secondary Private IPs
Releasing Secondary Private IPs
Binding EIPs
Unbinding EIPs

Viewing ENI Information

Last updated：2024-10-23 10:24:13

1. Log in to the VPC Console.
2. Choose IP and ENI -> ENI in the left sidebar to go to the ENI list page.

3. Locate the ENI and click its ID/Name to enter the details page.


Creating an ENI

Last updated：2024-10-23 10:24:13

1. Log in to the VPC console.
2. Choose IP and ENI > ENI in the left sidebar to go to the ENI list page.
3. Select a region and a VPC, and click + New.
4. In the pop-up window, enter an ENI name, select the VPC and subnet to which the secondary ENI belongs, and assign a private IP to the ENI. To add a tag, click Advanced options.
Note:
You need to configure the security group for the secondary ENI separately. After creating the secondary ENI, please determine the security policy of the ENI based on your business situation and bind the security group to it. For details, see binding security groups.
"Automatic" and "Manual" are supported for IP assignment:
Automatic: The system will automatically assign a private IP available in the subnet CIDR block to the ENI.
Manual: You need to enter a private IP available in the subnet CIDR block.
A secondary ENI is configured with a primary IP by default. If you need multiple IPs, click Add a secondary IP to configure them.

5. Click OK.

Configuring Security Groups

Last updated：2026-03-13 10:38:09

The secondary ENI can be bound with one or more security groups, which implement access control on the in/outbound traffic of the ENI. You need to bind the security group to the created secondary ENI according to your business situation. The ENI can be bound with the same security groups as or different ones from the CVM instances. This document describes how to bind a security group to or unbind it from the secondary ENI.

Binding security groups

Prerequisites

You've created the security group(s) as instructed in Creating a security group.

Operation Guide

1. Log in to the ENI console.
2. Click the ID of the ENI to which the security group needs to be bound.
3. Click Bind in the Associate security group tab.
4. In the Configure security group pop-up interface, check your created security group(s), and click OK. When multiple security groups are bound, the higher the security group is, the higher its priority will be, and it will be matched earlier.

Unbinding security groups

Note:
It is recommended that you reserve at least one security group for an ENI.

Operation Guide

1. Log in to the ENI console.
2. Click the ID of the ENI from which the security group needs to be unbound.
3. In the ENI details page, click Associate security group tab, and then click Unbind in the operation column of the Bound security groups list.
4. In the pop-up window, click OK.

Binding and Configuring an ENI

Binding an ENI to a CVM

Last updated：2024-10-23 10:24:13

This document describes how to bind a secondary ENI to a CVM.
Note:
You need to configure the security group for the secondary ENI separately based on your business situation. With no security group bound, the ENI does not have access control on in/outbound traffic by default. To bind the security groups, see binding security groups.
For CVMs using CentOS 8.0, 7.8, 7.6, 7.5 or 7.4 images, install a tool before binding an ENI. The ENI information is automatically configured in the ENI file, and the routing policy is automatically delivered. For more details, see Configuring an ENI on a Linux CVM.
For CVMs using other images, bind an ENI to the CVM as instructed below. Then complete the ENI configuration by referring to Configuring an ENI on a Linux CVM or Configuring an ENI on a Windows CVM.

Binding to a CVM

1. Log in to the VPC console.
2. Click IP and ENI > ENI in the left sidebar.
3. Locate the row of the desired ENI, and click More > Bind CVM in the Operation column.

Note:
You can also click the ENI ID to go to the details page, and click Bind CVM.
The ENI can be bound to the CVMs in the same availability zone as the ENI. For more model limits, see Use Limits.
4. In the pop-up window, select the target CVM and click OK.


Configuring an ENI on a Linux CVM

Last updated：2025-12-15 19:29:17

This document guides you to configure an ENI on a Linux CVM.
This document provides instructions on how to configure an ENI on two common server images: CentOS and Ubuntu.
Configuring an ENI on a CentOS CVM
Configuring an ENI on an Ubuntu CVM

Configuring an ENI on a CentOS CVM

Method 1: Tool-based configuration

Note:
This method is applicable to CentOS versions 8.0, 7.8, 7.6, 7.5, 7.4 and 7.2.
The nic-hotplug.tgz tool automatically creates the ENI configuration file and distributes the ENI route when an ENI is bound or the CVM is restarted.
If the CVM has already configured with ENIs, ensure that the routes of existing ENIs have been correctly configured before using the tool to configure a new one. If restart is acceptable to your business, you can restart the CVM as instructed in the step5 for the tool configuration to take effect on all ENIs.

Directions

1. Log in to the CVM and run the following command to download the nic-hotplug.tgz tool. 
wget https://iso-1255486055.cos.ap-guangzhou.myqcloud.com/nic-hotplug.tgz
2. Run the following command to decompress the file.
tar -zxvf nic-hotplug.tgz
3. Run the following commands to grant the execute permission and install the tool.
cd nic-hotplug
chmod +x ./install.sh
./install.sh
4. Bind an ENI, and then verify that the route of the new ENI eth1 has been distributed.
4.1 Run the ip rule show command. You can see that the policy-based route of the ENI eth1 has been added.



4.2 Run the ip route show table eth1 command to view the ENI eth1 route table.



5. 
(Optional)
If there are existing ENIs, you can restart the CVM via the console or running the reboot command. Then, the routes of all ENIs will be automatically distributed.
Restart CVM by running the command:




Method 2: Manual configuration

Note:
This approach is compatible with CentOS versions 8.0, 7.8, 7.6, 7.5, 7.4, and 7.2, as well as Rocky Linux 9.x series.
The configuration procedures for CentOS and Rocky Linux are analogous, with the only discrepancy lying in the commands used to restart the network service. For further details, please refer to the operational steps.

Prerequisites

You have bound an ENI to the CVM. For detailed directions, see Binding ENI to CVM.

Directions

1. Log in to the CVM as the administrator and run the following command to locate the ENI to be configured (IP not shown). As shown in the figure, the ENI to be configured is eth1.
ip addr



2. Run the following command to access the /etc/sysconfig/network-scripts/ folder.
cd /etc/sysconfig/network-scripts/
3. Create a configuration file such as ifcfg-eth1 for the new ENI.
3.1 Run the following command.
cp ifcfg-eth0 ifcfg-eth1
3.2 Run the following command to modify the configuration file.
vim ifcfg-eth1
3.3 Press i to switch to the edit mode and modify the configuration file as follows:
Note:
For the methods to view the IP address and subnet mask of the ENI, see the Appendix.
Mode 1: Statically manual IP configuration
DEVICE='eth1' # Enter the actual ENI name obtained in step 1.
NM_CONTROLLED='yes'
ONBOOT='yes'
IPADDR='192.168.1.62'  # Enter the actual IP address of the ENI.
NETMASK='255.255.255.192'  # Enter the actual subnet mask.
#GATEWAY='192.168.1.1'  # Enter the actual IP address of the gateway of the subnet where the ENI is located. In this example, because eth1 and eth0 are in the same subnet and the gateway has been defined, so the IP address will not be entered repeatedly here to avoid gateway conflict.
Mode 2: Dynamically acquire IP address
BOOTPROTO=dhcp     #Automatically acquire IP address
DEVICE=eth1        # Enter the name of the ENI to be configured
HWADDR=20:90:6F:63:98:CC    # Please replace it with the actual MAC address of the ENI
ONBOOT=yes
PERSISTENT_DHCLIENT=yes
TYPE=Ethernet
USERCTL=no
PEERDNS=no
DEFROUTE=no    # Determine whether to set the ENI as the default route. Do not set eth1 as the default route here for avoiding route conflict
3.4 Press Esc when you get to the last line of vim, enter wq!, and then press Enter to save and close the configuration file.
4. Run the following command to restart the network service for the configuration to take effect.
Note:
If you have configured DNS, the resolv.conf file may be reset after the network is restarted, and the DNS resolution may be affected.
CentOS
systemctl restart network
Rocky Linux
systemctl restart NetworkManager
5. Check and verify the IP configuration.
5.1 Run the following command to check the IP address.
ip addr
5.2 Confirm that the secondary ENI and its IP are visible, as shown below:



5.3 If the IP address is incorrectly configured, perform the following checks:
5.3.1 Verify the configuration file. Reconfigure the file if needed.
5.3.2 Confirm whether the network service has restarted. You can run the following command to restart the network for the configuration to take effect.
systemctl restart network
6. Configure the routing policy based on actual needs.
7. After the preceding configuration, the Linux image still sends packets from the primary ENI by default. In this case, you can configure policy-based routing to specify the ENI through which packets are sent and returned.
7.1 Creat
e two route
tables.
echo "10 t1" >> /etc/iproute2/rt_tables    #Replace “10” with the actual route ID and “t1” with the actual route table name.
echo "20 t2" >> /etc/iproute2/rt_tables   #Replace “20” with the actual route ID and “t2” with the actual route table name.
7.2 Add default routes for both route tables in the following two ways.
Configure a temporary policy-based route, which needs to be re-configured after restarting the network. Run the following command.
ip route add default dev eth0 via 192.168.1.1 table 10   #Replace “192.168.1.1” with the subnet gateway of the primary ENI.
ip route add default dev eth1 via 192.168.1.1 table 20   #Replace “192.168.1.1” with the subnet gateway of the secondary ENI.
Note:
For gateway details, see Viewing the gateway.
Configure a permanent policy-based route, which can be saved in the configuration file. The following operations use CentOS 7.8 as an example.
7.2.1 Edit the configuration file "route-ENI name" (such as route-eth0) under the directory "/etc/sysconfig/network-scripts/". 
vim /etc/sysconfig/network-scripts/route-eth0    # Edit the route-eth0 file
7.2.2 Add a line of command: `default dev [ENI name, such as eth0] via [the gateway of the ENI, such as 192.168.1.1] table [code of the policy-based route table, such as 10]`. For example,
default dev eth0 via 192.168.1.1 table 10        # Add a default gateway for route table 10 in the route-eth0 file
7.2.3 Press "ESC", and enter " wq!" to save and exit. Then follow the same operation to configure the route-eth1 file.
vim /etc/sysconfig/network-scripts/route-eth0    # Edit the route-eth1 file
default dev eth0 via 192.168.1.1 table 20        # Add a default gateway for route table 20 in the route-eth0 file
7.2.4 Restart the network for the configuration to take effect.
systemctl restart network
7.3 Configure a policy-based routing policy.
ip rule add from 192.168.1.5 table 10     #Enter the actual IP address of the primary ENI.
ip rule add from 192.168.1.62 table 20     #Enter the actual IP address of the secondary ENI.
8. After completing the configuration, you can ping the private IP of a CVM that is in the same subnet. If the pinging succeeds, the configuration is correct. If no other CVM exists, you can bind the private IP of the secondary ENI to a public IP and then ping the public IP.

Configuring ENI on an Ubuntu CVM

1. Log in to the CVM as the administrator and run the following command to locate the ENI to be configured (IP not shown). As shown in the figure, the ENI to be configured is eth1.
ip addr

2. Run the following command to access the /etc/network/ folder.
cd /etc/network/
3. Modify the configuration file “interfaces”.
3.1 Run the following command to switch to the "root" account and modify the configuration file.
sudo su
vim interfaces
3.2 Press i to switch to the edit mode and add the following content to the configuration file.
Note:
For the methods to view the IP address and subnet mask of the ENI, see the Appendix.
auto eth1 # Enter the actual ENI name obtained in step 1.
iface eth1 inet static # Enter the actual ENI name obtained in step 1.
address 172.21.48.3 # Enter the actual IP address of the ENI.
netmask 255.255.240.0 # Enter the actual subnet mask.
3.3 Press Esc when you come to the last line of vim, enter wq!, and then press Enter to save and close the configuration file.
4. Restart the ENI eth1.
4.1 Run the following commands to switch to the “root” account and install ifupdown.
sudo su
apt install ifupdown
4.2 Turn off the ENI eth1.
ifdown eth1
4.3 Start the ENI eth1.
ifup eth1
5. Check and verify the IP configuration.
5.1 Run the following command to check the IP address.
ip addr
5.2 Confirm that the secondary ENI and its IP are visible, as shown below:



5.3 If the IP address is incorrectly configured, perform the following checks:
5.3.1 Verify the configuration file. Reconfigure the file if needed.
5.3.2 Confirm whether the ENI has restarted. You can run the following commands to restart ENI for the configuration to take effect.
ifdown eth1
ifup eth1
6. Configure the routing policy based on actual needs.
Note:
After the preceding configuration, the Linux image still sends packets from the primary ENI by default. In this case, you can configure policy-based routing to specify the ENI through which packets are sent and returned. A temporary static route is configured accordingly. You need to reconfigure a route after restarting the network.
6.1 Run the following c
ommands to c
reate two route tables.
echo "10 t1" >> /etc/iproute2/rt_tables   #Replace “10” with the actual route ID and “t1” with the actual route table name.
echo "20 t2" >> /etc/iproute2/rt_tables  #Replace “20” with the actual route ID and “t2” with the actual route table name.
6.2 Run the following commands to add default routes for both route tables.
ip route add default dev eth0 via 172.21.48.1 table 10   #Replace “172.21.48.1” with the subnet gateway of the primary ENI.
ip route add default dev eth1 via 172.21.48.1 table 20   #Replace “172.21.48.1” with the subnet gateway of the secondary ENI.
Note:
For gateway details, see Viewing the gateway.
7. Run the following commands to configure policy-based routing.
ip rule add from 172.21.48.11 table 10   #Enter the actual IP address of the primary ENI.
ip rule add from 172.21.48.3 table 20    #Enter the actual IP address of the secondary ENI.
8. After completing the configuration, you can ping the private IP of a CVM that is in the same subnet. If the pinging succeeds, the configuration is correct. If no other CVM exists, you can bind the private IP of the secondary ENI to a public IP and then ping the public IP.

Appendix

Viewing the IP address of an ENI

1. Log in to the VPC console.
2. Choose IP and ENI > ENI in the left sidebar to go to the ENI list page.
3. Click the ID of the target ENI to go to its details page.
4. Select the IPv4 address management tab to view the IP address of the ENI, which is the private IP.

Viewing the subnet mask of an ENI

1. Log in to the VPC console.
2. Choose IP and ENI > ENI in the left sidebar to go to the ENI list page.
3. Click the ID of the target ENI to go to its details page, where you can view the subnet mask of the ENI. As shown in the following figure, the CIDR bits of the subnet are /20, which means that the subnet mask of the ENI is 255.255.240.0. The relationship between the CIDR bits and the subnet mask is described in the following table:
CIDR Bits
Subnet Mask
/28
255.255.255.240
/27
255.255.255.224
/26
255.255.255.192
/25
255.255.255.128
/24
255.255.255.0
/23
255.255.254.0
/22
255.255.252.0
/21
255.255.248.0
/20
255.255.240.0
/19
255.255.224.0
/18
255.255.192.0
/17
255.255.128.0
/16
255.255.0.0

Viewing the gateway

If you haven’t made any changes, the gateway is the first IP address in the subnet IP range. For example, if the subnet IP range is 192.168.0.0/24, the gateway is 192.168.0.1. If you are not sure about the subnet IP range of the ENI, please follow the steps below:
1. Log in to the VPC console.
2. Choose IP and ENI > ENI in the left sidebar to go to the ENI list page.
3. Click the ID of the target ENI to go to its details page, where you can view the subnet where the ENI resides. As shown in the figure below, the first IP address in the subnet IP range is 10.0.1.1.




Configuring an ENI on a Windows CVM

Last updated：2024-10-23 10:24:14

Note:
The following operations use Windows 2012 as an example.

Directions

Windows provided with DHCP

If the CVM is provided with DHCP, you can view its secondary ENI and IP by following steps below without any further configuration:
1. Log in to the CVM, and select Control Panel -> Network and Internet -> Network and Sharing Center to check the secondary ENI that has been automatically obtained.
2. Click the “Ethernet 2” secondary ENI to view its information.
3. In the Ethernet 2 Status pop-up window, click Properties.
4. In the Ethernet 2 Properties pop-up window, double-click Internet Protocol Version 4 (TCP/IPv4).
5. In the Internet Protocol Version 4 (TCP/IPv4) pop-up window, you can see Obtain an IP address automatically is selected, so there is no need to enter one.
6. Return to the Ethernet 2 Status pop-up window and click Details. As shown in the figure below, DHCP is enabled and the IP automatically obtained is displayed.

DHCP not set

If the CVM is not provided with DHCP, you need to configure the private IP by following the steps below:
1. Log in to the ENI console and bind the ENI to a CVM.
2. Log in to the CVM and select Control Panel -> Network and Internet -> Network and Sharing Center.
3. Click to edit the “Ethernet 2” secondary ENI.
4. In the Ethernet 2 Status pop-up window, click Properties.
5. In the Ethernet 2 Properties pop-up window, double-click Internet Protocol Version 4 (TCP/IPv4).
6. In the Internet Protocol Version 4 (TCP/IPv4) pop-up window, enter the actual IP and click OK.
7. In the Ethernet 2 Properties pop-up window, click OK to complete the configuration.
8. In the Ethernet 2 Status pop-up window, click Details. As shown in the figure below, DHCP is disabled and the IP manually entered is displayed.
9. Ping the private address of a CVM that is in the same subnet. If the pinging succeeds, the configuration is correct. If no other CVM exists, you can bind the private IP address of the secondary ENI to a public IP address and then ping the public IP address.

Setting Service Level

Last updated：2024-10-23 10:24:13

You can specify different service level for different ENIs. When bandwidth congestion occurs, this can ensure that the key services with high priority be forwarded first. There are four service levels, Gold, Silver, Bronze and Default, ranking by priority for traffic forwarding. You can keep it as Default for general usage.
Note:
The service level defaults to "Default".
ENI is a private network resource. The service level is only applied to underlying traffic service and is irrelevant to the billing.

Directions

1. Log in to the VPC console.
2. Choose IP and ENI > ENI in the left sidebar to go to the ENI list page.
3. Locate the target ENI. Click More > Set service level in the Operation column.
4. Choose a service level from the drop-down list. Click OK.
5. To set the same service level for multiple ENIs, you can select multiple ENIs and click Set service level at the top.
6. Click OK.

Deleting an ENI

Last updated：2024-10-23 10:24:13

You can delete an ENI that is not bound to a CVM.
Note:
When an ENI is deleted, its associated private IPs, EIPs, and security groups are automatically unbound.
You can only delete ENIs that are not associated with CVMs.
The primary ENI is deleted when the CVM is deleted.
1. Log in to the VPC console.
2. Choose IP and ENI > ENI in the left sidebar to go to the ENI list page.
3. Locate the row of the desired ENI and click Delete in the "Operation" column.

4. In the pop-up window, click OK.

Unbinding from a CVM

Last updated：2024-10-23 10:24:13

1. Log in to the VPC console.
2. Choose IP and ENI > ENI in the left sidebar to go to the ENI list page.
3. Locate the target ENI, and click More > Unbind from the CVM in the Operation column.
Note:
You can also click the ENI ID to go to the details page, and click Unbind from the CVM.

4. In the pop-up window, click OK.
Note:
When an EIP is unbound, an idle is incurred. Release unused EIPs to avoid unnecessary costs.


Binding Secondary Private IP Addresses

Last updated：2024-10-23 10:24:14

To bind multiple IP addresses to a single ENI, you can apply for secondary private IP addresses for the ENI as follows:

Step 1. Assign a Private IP

1. Log in to the VPC console.
2. Choose IP and ENI > ENI in the left sidebar to go to the ENI list page.
3. Locate the ENI instance for which you want to request a secondary private IP, and then click on its ID/Name to go to its details page.
4. Click the IPv4 Address Management tab, and check the primary private IPs that have been bound.

5. Click Assign Private IP and select Auto or Enter manually for Assign IP in the pop-up window.
Note:
If you select Enter manually, make sure that the private IP address you enter is within the subnet IP range and is not a reserved IP address of the system. For example, if the subnet IP range is 10.0.0.0/24, the entered private IP address should be within 10.0.0.2 - 10.0.0.254.


Step 2. Configure the Secondary Private IP

Follow the steps below to log in to the CVM that is bound with the ENI and configure the secondary private IP to make it effective:

Linux CVM instances

1. Run the following command to configure the secondary private IP.
# For example, `ip addr add 10.0.0.2/24 dev eth0`
ip addr add Secondary private IP/CIDR bits dev eth0
2. Run the ip addr command to view the configured IPs, as shown below.



Windows CVM instances

1. Perform the f
ollowing steps t
o view the IP address, subnet mask, default gateway, and DNS server of the CVM instance.
2. On the desktop, select

in the lower-left corner and click

to open the Windows PowerShell window.
ipconfig /all
3. Record the IPv4 address, subnet mask, default gateway, and DNS server values that are displayed.
4. Select Control Panel > Network and Internet > Network and Sharing Center. Click Ethernet to modify its information.
5. In the Ethernet Status pop-up window, click Properties.
6. In the Ethernet Properties pop-up window, select Internet Protocol Version 4 (TCP/IPv4) and click Properties.
7. In the Internet Protocol Version 4 (TCP/IPv4) Properties pop-up window, specify the following information:
Parameter Name
Parameter Value
IP address
The IPv4 address obtained in step 1
Subnet mask
The subnet mask obtained in step 1
Default gateway
The default gateway obtained in step 1
Preferred DNS server
The DNS server obtained in step 1
Alternate DNS server
The alternate DNS server obtained in step 1. If the alternate DNS server is not given, ignore this parameter
8. Click Advanced to configure the secondary private IP address.
9. In the Advanced TCP/IP Settings pop-up window, click Add under the IP Addresses section.
10. In the TCP/IP Address pop-up window, enter the secondary private IP and the subnet mask obtained in step 1, and click Add.
11. In the Internet Protocol Version 4 (TCP/IPv4) pop-up window, click OK.
12. In the Ethernet Properties pop-up window, click OK to complete the configuration.
13. In the Ethernet Status pop-up window, click Details to view the configured IP addresses.

Releasing Secondary Private IP Addresses

Last updated：2024-10-23 10:24:13

Note:
Only a secondary IP address can be released from an ENI. The primary IP address cannot be released.
After a private IP address is unbound, the associated EIP will be unbound automatically.

Directions

1. Log in to the VPC Console.
2. Choose IP and ENI -> ENI in the left sidebar to go to the ENI list page.
3. Locate the ENI you want to release secondary private IPs, and click its ID/Name to go to the details page.
4. Click the IPv4 address management tab to view private IP addresses and EIPs that have been bound.

5. Locate the private IP address you want to release, and click Release under the Operation column.
6. Click OK in the pop-up window.



Binding EIPs

Last updated：2024-10-23 10:24:13

1. Log in to Virtual Private Cloud Console.
2. Choose IP and ENI > ENI in the left sidebar to go to the ENI list page.
3. Click the ID of the desired instance to enter its details page.
4. Click IPv4 Address Management in the tab to check existing private IPs.

5. Click Bind in the Bound Public IP column.

6. In the page that appears:
Select the desired EIP and click OK.
If no EIP is available, click Create at the top of the pop-up box to apply for one. For more information, refer to Applying for EIPs. After your application is approved, return to the page and click Refresh. You should see the EIP you applied for. Select it and click OK.



Unbinding EIPs

Last updated：2024-10-23 10:24:13

1. Log in to the VPC Console.
2. Click ENI in the left sidebar to enter the ENI list page.
3. Click the instance ID to enter the details page.
4. Click IPv4 Address Management in the tab to view private IPs and EIPs that have been bound.

5. Click Unbind in the row of the private IP.

6. Click OK in the pop-up window.

Modifying Primary Private IPs

Last updated：2024-10-23 10:24:13

This document describes how to modify the primary private IP of a CVM instance on the ENI console.
Note:
You can modify the primary private IP of the primary ENI, but not that of secondary ENIs.
Note that modifying the primary IP of the primary ENI will automatically restart the associated instance and cause business interruption for about 30 seconds.
The private IP can also be modified on the CVM console as instructed in Modifying Private IP Addresses.

Prerequisites

The primary ENI ID of the CVM instance has been obtained on the CVM console. For more information, see Query Instance Info.

Directions

1. Log in to the VPC console.
2. Choose IP and ENI > ENI in the left sidebar to go to the ENI list page.
3. Locate the ENI you want to modify the primary IP, and click its ID/Name to enter the details page.
4. Click the IPv4 address management tab, and check the primary private IPs that have been bound.

5. Locate the primary private IP you want to change, and click *Modify Primary IP under the Operation column.

6. Enter a new primary private IP in the pop-up window, and click OK.