Help Center/ Elastic IP/ User Guide (Ally Region)/ FAQs/ EIP/ Can Multiple EIPs Be Bound to an ECS?
Updated on 2026-01-05 GMT+08:00
View PDF
Share

Can Multiple EIPs Be Bound to an ECS?

Scenarios

Multiple EIPs can be bound to an ECS, but this operation is not recommended.

If an ECS has multiple network interfaces attached and you want to bind multiple EIPs to this ECS, you need to configure policy-based routes for these network interfaces so that these extension network interfaces can communicate with external networks. For details, see Configuration Example.

Operation Guide

Table 1 provides the operation guides on how to configure policy-based routes for Linux and Windows ECSs.

Table 1 Operation instructions on how to configure policy-based routes

OS Type

Procedure

Linux

Take an ECS running CentOS 8.0 (64-bit) as an example.

For details, see section Configuring Policy-based Routes for a Linux ECS with Multiple Network Interfaces under Configuring Policy-based Routes for an ECS with Multiple Network Interfaces in the Virtual Private Cloud Best Practices.

Windows

Take an ECS running Windows Server 2012 (64-bit) as an example.

For details, see section Configuring Policy-based Routes for a Windows ECS with Multiple Network Interfaces under Configuring Policy-based Routes for an ECS with Multiple Network Interfaces in the Virtual Private Cloud Best Practices.

Configuration Example

Table 2 lists ECS configurations.

Table 2 ECS configurations

Parameter

Configuration

Name

ecs_test

Image

CentOS 6.5 64bit

EIP

2

Primary NIC

eth0

Secondary NIC

eth1

Example 1:

If you intend to access public network 11.11.11.0/24 through standby NIC eth1, perform the following operations to configure a route:
  1. Log in to the ECS.
  2. Run the following command to configure a route:

    ip route add 11.11.11.0/24 dev eth1 via 192.168.2.1

    In the preceding command, 192.168.2.1 is the gateway IP address of standby NIC eth1.

Example 2:

Based on example 1, if you intend to enable routing for default public network traffic through standby NIC eth1, perform the following operations to configure a route:

  1. Log in to the ECS.
  2. Run the following command to delete the default route:

    ip route delete default

    Exercise caution when deleting the default route because this operation will interrupt the network and result in SSH login failures.

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

    ip route add 0.0.0.0/0 dev eth1 via 192.168.2.1

    In the preceding command, 192.168.2.1 is the gateway IP address of standby NIC eth1.

Parent topic: EIP