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
- 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 and 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.
Operation Guide
Table 1 provides the operation guides on how to configure policy-based routes for Linux and Windows ECSs.
|
OS Type |
IP Address Version |
Procedure |
|---|---|---|
|
Linux |
IPv4 |
Take an ECS running CentOS 8.0 (64-bit) as an example. Configuring Policy-based Routes for a Linux ECS with Multiple Network Interfaces (IPv4/IPv6) |
|
IPv6 |
||
|
Windows |
IPv4 |
Take an ECS running Windows Server 2012 (64-bit) as an example. Configuring Policy-based Routes for a Windows ECS with Multiple Network Interfaces (IPv4/IPv6) |
|
IPv6 |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot
