Before You Begin
l The cloud resource is not bound to another EIP.
l The bound EIP is not bound to another cloud resource.
Precautions
You do not have to shut the physical server down to bind an EIP. The binding relationship comes into effect immediately.
Operation Steps
1. In the console, click EIP in the service list.
2. Locate the EIP to bind in the EIP list and click Bind in the Operation column.
3. In the pop-up window, to bind a physical server, select One-to-one Mapping.
4. In the resource list that is displayed, select the physical server resource to bind and click OK to finish the binding operation.
5. After binding, in the console list, this EIP status becomes Bound.
Note:
If the bound EIP has a different billing mode or expiration date from the cloud resource, either of them may expire first, affecting the business operation. You must pay special attention to the expiration date of the resources in a yearly/monthly subscription mode, and renew your subscription to the resources before the expiration date. You must pay special attention to pay-as-you-go resources and top up your account when necessary to maintain sufficient balance in your account.
FAQs
Why cannot an EIP be bound to a physical server instance?
The following shows common reasons why an EIP cannot be bound to a physical server instance:
1. The EIP and the physical server instance are not in the same region.
2. The physical server instance has been assigned a fixed public IP address or bound to another EIP.
3. If the physical server instance is abnormal, only the running or stopped physical server instance can be bound to the EIP.