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.
Table 1 provides the operation guides on how to configure policy-based routes for Linux and Windows ECSs.
OS Type | Procedure |
|---|---|
Linux | Take an ECS running CentOS 8.0 (64-bit) as an example. Configuring Policy-based Routes for a Linux ECS with Multiple Network Interfaces |
Windows | Take an ECS running Windows Server 2012 (64-bit) as an example. Configuring Policy-based Routes for a Windows ECS with Multiple Network Interfaces |
Table 2 lists 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: 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:
ip route delete default
Exercise caution when deleting the default route because this operation will interrupt the network and result in SSH login failures.
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.