All Products
Search

This Product

    Cloud Enterprise Network:Connect multiple VPCs using scenario-based networking

    Document Center

    Cloud Enterprise Network:Connect multiple VPCs using scenario-based networking

    Last Updated:Jun 02, 2026

    Quickly create a Cloud Enterprise Network (CEN) instance and connect VPCs across regions with the scenario-based networking tool.

    Note

    Scenario-based networking supports full-mesh connectivity for VPCs across multiple regions within the same account. It automates CEN configurations: creating the CEN instance, transit router instances, VPC connections, cross-region connections, associated forwarding, and route learning.

    Example

    image

    In this example, three VPCs exist: VPC1 and VPC2 in China (Hangzhou), and VPC3 in China (Shanghai). The scenario-based networking tool establishes full-mesh connectivity among them. The following table lists the VPC configurations.

    Parameter

    VPC1

    VPC2

    VPC3

    Region

    China (Hangzhou)

    China (Hangzhou)

    China (Shanghai)

    CIDR block

    10.0.0.0/16

    172.16.0.0/16

    192.168.0.0/16

    vSwitch1

    Zone J, 10.0.0.0/24

    Zone J, 172.16.0.0/24

    Zone M, 192.168.0.0/24

    vSwitch2

    Zone K, 10.0.1.0/24

    Zone K, 172.16.1.0/24

    Zone N, 192.168.1.0/24

    IP address of the test ECS instance

    ECS1: 10.0.0.1

    ECS2: 172.16.0.1

    ECS3: 192.168.0.1
    Important

    Network planning requirements:

    • CIDR blocks of connected VPCs must not overlap.

    • For zone-level disaster recovery in a multi-zone region, create vSwitches in at least two zones.

    Procedure

    Step 1: Create networking configurations

    1. Log on to the Cloud Enterprise Network console. On the CEN Instance page, click Create CEN Instance.

    2. In the Create CEN Instance dialog box, select Create Scenario-specific CEN (Recommended). For Scenario, select VPC Interconnection and then click Create.

    3. On the Configure Networking Settings page, on the New Region tab, add the following configurations:

      • Region: Select China (Hangzhou).

      • Zone: Select Zone J and Zone K.

      • VPC:

        • For VPC, select VPC 1 and its two corresponding vSwitches.

        • Click Add VPC. For VPC, select VPC2 and its two corresponding vSwitches.

    4. Click + next to the China (Hangzhou) tab to add networking configurations in a new region. The name of the selected region appears on the new tab.

      • Region: Select China (Shanghai).

      • Zone: Select Zone M and Zone N.

      • VPC: For VPC Instance, select VPC3 and its two corresponding vSwitches.

      • Click Next.

    Step 2: Confirm networking configurations and fees

    On the Confirm Networking Settings and Fees page, review the resources to be created and their fees. This may take a few minutes.

    The page shows a network topology for VPC1 (10.0.0.0/16), VPC2 (172.16.0.0/16), and VPC3 (192.168.0.0/16). In the Fee Details table, new transit router route tables and the CEN instance are free of charge. Existing VPCs and vSwitches are marked as Existing Product and incur no additional fees.

    After confirming, click Start Deployment.

    Step 3: Start the deployment

    The deployment takes about 10 minutes.

    Click View CEN Instance to view the created resources. The VPCs are now interconnected through CEN.

    After deployment, the CEN instance status changes to Available. Two Transit Router Enterprise Edition instances are created—one in China (Hangzhou) with three connections and one in China (Shanghai) with two connections—both with Available status.

    Step 4: Test the connectivity

    Note

    Ensure security group rules for all three ECS instances allow ICMP traffic. You can Query security group rules and Add security group rules as needed.

    Inbound rules must include: Protocol = All ICMP (IPv4), Port Range = -1/-1, Authorization Object = 0.0.0.0/0 (all IPv4 addresses).

    Log on to ECS1 and ping ECS2:

    ping 172.16.0.1

    Log on to the ECS instance in VPC1 and run the following command to verify connectivity with VPC2 (172.16.0.1 is the destination IP): 

    ping 172.16.0.1
    Successful output: 
    PING 172.16.0.1 (172.16.0.1) 56(84) bytes of data.
64 bytes from 172.16.0.1: icmp_seq=1 ttl=63 time=0.589 ms
64 bytes from 172.16.0.1: icmp_seq=2 ttl=63 time=0.379 ms
64 bytes from 172.16.0.1: icmp_seq=3 ttl=63 time=0.369 ms

--- 172.16.0.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2033ms
rtt min/avg/max/mdev = 0.369/0.445/0.589/0.104 ms

    A successful ping confirms VPC1-VPC2 connectivity. Repeat for VPC1-VPC3 and VPC2-VPC3.

    Related topics