检测到您已登录华为云国际站账号,为了您更好的体验,建议您访问国际站服务网站 https://www.huaweicloud.com/intl/zh-cn
不再显示此消息
Verify the network connectivity between VPCs. ping IP address of the ECS To verify the network connectivity between vpc-demo-01 and vpc-demo-02, log in to ecs-demo-01 and run the following command: ping 172.16.1.137 If information similar to the following is displayed, the two VPCs
Create an ECS in each VPC. In this example, the ECSs are used to verify the communications between the VPC and the on-premises data center. The ECS quantity and configuration are for reference only. For details, see Purchasing a Custom ECS.
To delete an ECS, refer to How Can I Delete or Restart an ECS? Step 4: Attach Global DC Gateway DGW-B02 to the Enterprise Router Create a global DC gateway DGW-B02. For details, see Creating a Global DC Gateway.
Scenarios Traffic cannot be forwarded from a VPC to the enterprise router that it is attached to if you set the destination of a route in the VPC route table to 0.0.0.0/0 and: An ECS in the VPC has an EIP bound. Refer to solution 1.
Create an ECS in each of the three regions. For details, see Purchasing a Custom ECS. Create a central network and add the enterprise routers to the central network as attachments. Create a central network and add the enterprise routers to the central network as attachments.
In the route tables of the VPCs, add routes for traffic to route through the enterprise router. 4 Verifying Network Isolation and Connectivity Log in to an ECS and run the ping command to verify the network isolation and connectivity.
Add SNAT rules for the VPCs to the NAT gateway. 4 Verifying Network Connectivity Log in to an ECS and run the ping command to verify the network connectivity. Parent topic: Allowing VPCs to Share an EIP to Access the Internet Using Enterprise Router and NAT Gateway
ECS An ECS is deployed in the VPC to verify communications between the cloud and the on-premises data center. If you have multiple ECSs associated with different security groups, you need to add rules to the security groups to allow network access.
ECS An ECS is deployed in the VPC to verify communications between the cloud and the on-premises data center. If you have multiple ECSs associated with different security groups, you need to add rules to the security groups to allow network access.
Log in to the ECS and run the ping command to verify connectivity through the Direct Connect connection. Create a Direct Connect connection in region B and verify the connectivity by referring to 1.
Table 8 ECS details ECS Name Image VPC Subnet Security Group Private IP Address ecs-demo-01 Public image: EulerOS 2.5 64-bit vpc-demo-01 subnet-demo-01 sg-demo (general-purpose web server) 192.168.1.99 ecs-demo-02 vpc-demo-02 subnet-demo-02 172.16.1.137 Parent topic: Setting Up a
Table 10 ECS details ECS Name Image VPC Subnet Security Group Private IP Address ecs-isolation-01 Public image: CentOS 7.5 64-bit vpc-isolation-01 subnet-isolation-01 sg-demo (general-purpose web server) 10.1.0.134 ecs-isolation-02 vpc-isolation-02 subnet-isolation-02 10.2.0.215 ecs-isolation
ECS 3 Create an ECS in each VPC to verify network connectivity. Name: Set it based on site requirements. In this example, the names are as follows: Region A: ECS-A Region B: ECS-B Region C: ECS-C Image: Select an image based on site requirements.
ECS 2 An ECS is required in each VPC for verifying connectivity. Name: Set this parameter based on site requirements. In this example, the two ECSs are named ECS-A and ECS-B. Image: Select an image based on site requirements.
Before/During migration Table 7 ECS details ECS VPC Subnet Private IP Address Image Security Group ECS Is Used to Phase ecs-A01 VPC-A subnet-A01 172.16.0.139 Public image: CentOS 8.2 64bit sg-demo (general-purpose web server) Run your workloads.
In the subnet of each VPC, create an ECS for verifying communications by running the ping command. Delete the routes used for verifying communications. Step 5: Perform the Migration and Delete the Cloud Connection Remove the VPCs from the cloud connection one by one.
ECS 2 Configure the two ECSs as follows: ECS Name: Set it as needed. In this example, the ECSs are named ECS-01 and ECS-02. ECS flavor: Set it as need. Ensure that the flavor can meet service requirements. Image: Set it as needed.
During migration After migration ECS 1 An ECS is required to verify connectivity. ECS Name: Set it based on site requirements. In this example, ECS-X is used. Image: Select an image based on site requirements. In this example, a public image (CentOS 8.2 64bit) is used.
Traffic cannot be forwarded from a VPC to its attached enterprise router if the destination of a route with an enterprise router as the next hop is set to 0.0.0.0/0 in the VPC route table and if: An ECS in the VPC has an EIP bound.
To delete an ECS, refer to How Can I Delete or Restart an ECS? Delete the three verification subnets. In this example, delete subnet-A02, subnet-B02, and subnet-C02 that are listed in Table 5. To delete a subnet, see Deleting a Subnet.