How Do I Configure Policy-Based Routes for an ECS with Multiple Network Interfaces?
Background
If a cloud server has multiple network interfaces, the primary network interface can communicate with external networks by default, but the extended network interfaces cannot. To enable extended network interfaces to communicate with external networks, you need to configure policy-based routes for these network interfaces.
Scenarios
This example describes how to configure policy-based routes for an ECS with two network interfaces. Figure 1 shows the networking.
- The primary and extended network interfaces on the source ECS are in different subnets of the same VPC.
- The source and destination ECSs are in different subnets of the same VPC, so the two ECSs can communicate with each other through primary network interfaces without configuring policy-based routes.
- After policy-based routes are configured for the two network interfaces of the source ECS, both the primary and extended network interfaces can be used to communicate with the destination ECS.
You can select a destination IP address based on service requirements. Before configuring policy-based routes, ensure that the source ECS can use its primary network interface to communicate with the destination ECS.
Figure 1 Networking of an ECS with two network interfaces
Operation Guide
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. |
Windows | Take an ECS running Windows Server 2012 (64-bit) as an example. |
- Background
- Scenarios
- Operation Guide