How to detach an elastic Nic from an instance when it is stopped or running

This article mainly introduces how to separate the elastic network card from the instance when the instance is in a stopped or running state. It is very detailed and has certain reference value. Interested friends must finish reading it.

Detach the elastic Nic from the instance

You can detach the secondary Nic from the instance, but not the primary Nic.

Limit

When detaching a secondary Nic from an instance, there are the following restrictions:

The secondary network card must be in a bound state.

The instance must be in a stopped or running state.

prerequisite

Your ENI must be attached to an instance. Before detaching an elastic Nic from an instance, the instance must be in a stopped or running state.

Operation steps

Follow these steps to detach the secondary Nic from the instance:

Log in to the ECS Management console.

In the left navigation bar, select Network and Security > Elastic Network Card.

Select the region.

Locate the bound Nic, and in the operation column, click unbind the instance.

In the unbind instance dialog box, after confirming the information, click OK.

Refresh the list, and when the status of the ENI is displayed as available, it indicates that the ENI has been successfully detached from the instance.

Subsequent operation

You can do the following for the available elastic NICs:

Attach an elastic Nic to another instance

Delete an elastic Nic

Modify the attributes of an elastic Nic

The above is how to separate all the contents of the elastic Nic from the instance when the instance is in a stopped or running state. Thank you for reading! Hope to share the content to help you, more related knowledge, welcome to follow the industry information channel!