Step 2: Create an Enterprise Switch

Scenarios

This section describes how to create an enterprise switch. An enterprise switch allows Layer 2 communication between an on-premises data center and a VPC based on VPN.

Prerequisites

• You have planned the resources required both on the cloud and on premises. For details about resource planning, see How Enterprise Switches Work.
• An enterprise switch establishes a Layer 2 network based on a Layer 3 network between an on-premises data center and a VPC created by VPN. You need to create a VPN connection first by referring to Step 1: Use VPN to Communicate at Layer 3.

Notes and Constraints

• The switch in an on-premises data center must support VXLAN because the enterprise switch needs to establish a VXLAN tunnel to the data center at Layer 2.
• The local tunnel subnet must have three IP addresses reserved for the enterprise switch.

Procedure

1. Log in to the management console.
2. On the console homepage, choose Network > Enterprise Switch.

   The Enterprise Switch page is displayed.

3. In the upper right corner of the page, click Create.

   The page for creating an enterprise switch is displayed.

4. Configure the parameters as prompted. For details, see Table 1.

   Table 1 Parameters for creating an enterprise switch

   Parameter	Description
   Region	Mandatory Select the region nearest to you to ensure the lowest latency possible.
   Active AZ	Mandatory Select the AZ where the active node is deployed. Enterprise switches are deployed in active/standby mode. An active AZ carries traffic. You can set the AZ to the one where your ECSs that need to communicate with an on-premises data center are deployed to ensure quick and uninterrupted access to ECSs.
   Standby AZ	Mandatory Select the AZ where the standby node is deployed. Set the standby AZ to be different from the active AZ. A standby AZ is used for backup and disaster recovery.
   Specifications	Mandatory Currently, standard enterprise switches are supported.
   Tunnel Connection	Mandatory Tunnel connection between the enterprise switch and the on-premises data center at Layer 3. Select a connection type based on your needs. VPN: allows an on-premises data center and a VPC to communicate at Layer 3. Custom: Select another type of connection to allow an on-premises data center and a VPC to communicate at Layer 3.
   Connection Gateway	This parameter is mandatory if Tunnel Connection is set to VPN. Select a virtual gateway if you set Tunnel Connection to a VPN gateway if you set Tunnel Connection to VPN.
   VPC	Mandatory VPC that the enterprise switch belongs to. If Tunnel Connection is set to VPN, the VPC is set to the one that the VPN gateway belongs to by default.
   Tunnel Subnet	Mandatory Subnet of the VPC that the enterprise switch belongs to. It is the local tunnel subnet. Local and remote tunnel subnets communicate with each other at Layer 3 over VPN. Enterprise switches allow communications between cloud and on-premises networks at Layer 2 based on the Layer 3 network between tunnel subnets.
   Tunnel IP Address	Mandatory IP address in the local tunnel subnet, which can be automatically assigned or manually specified. If an enterprise switch establishes a VXLAN tunnel with an on-premises data center at Layer 2, each end of the VXLAN tunnel requires a tunnel IP address (the local and remote tunnel IP addresses). The two IP addresses must be different.
   Name	Mandatory Enter the name of the enterprise switch. The name: Must contain 1 to 64 characters. Can contain letters, digits, underscores (_), hyphens (-), and periods (.).
   Description	Optional Enter the description of the enterprise switch in the text box as required.

5. Click Create Now.
6. Confirm the enterprise switch information and click Submit.

   This operation takes 3 to 6 minutes to complete. If the status is Running, the enterprise switch is created.

Follow-Up Operations

After an enterprise switch is created, you need to create a Layer 2 connection and configure a remote tunnel gateway. For details, see Getting Started.