vpruthi/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
doc-exports/docs/ecs/umn/en-us_topic_0018073216.html
guoyanyan a810508850 ecs_umn_1109 
Reviewed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com>
Co-authored-by: guoyanyan <guoyanyan3@huawei.com>
Co-committed-by: guoyanyan <guoyanyan3@huawei.com>
2022-12-05 15:44:44 +00:00

6.7 KiB
Raw Permalink Blame History

Can Multiple EIPs Be Bound to an ECS?

Scenarios

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

If you really need to bind multiple EIPs to an ECS, you must manually configure routing policies, which requires high network skills. Exercise caution when performing this operation.

Configuration Example

Table 1 lists ECS configurations.

Table 1 ECS configurations

Parameter

Configuration

Name

ecs_test

Image

CentOS 6.5 64bit

EIP

2

Primary NIC

eth0

Secondary NIC

eth1

Example 1:

If you are required 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 are required 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: Network Configurations