Buying an Enterprise Switch

Scenarios

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

Prerequisites

• Before using enterprise switches, plan resources on and off the cloud by referring to section "How Enterprise Switches Work" in the Enterprise Switch User Guide.
• An enterprise switch set up a Layer 2 network based on a Layer 3 network between an on-premises data center and a VPC. You need to create a Direct Connect or VPN connection first by referring to section "Step 1: Use VPN to Communicate at Layer 3" in Enterprise Switch Getting Started.

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. Go to the Buy Enterprise Switch page.
2. Configure the parameters as prompted. For details, see Table 1.

   Table 1 Parameters for creating an enterprise switch

   Parameter	Description	Example Value
   Billing Mode	Mandatory An enterprise switch can be billed on a pay-per-use basis. Pay-per-use is a postpaid payment mode. Your enterprise switch is billed by the second but settled by the hour. If the usage is less than an hour, you are billed based on the actual duration consumed.	Pay-per-use
   Region	Mandatory Select the region nearest to you to ensure the lowest latency possible.	EU-Dublin
   Active AZ	Mandatory Enterprise switches are deployed in active/standby mode. Select the AZ where the active node is deployed. 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.	AZ1
   Standby AZ	Mandatory Enterprise switches are deployed in active/standby mode. Select the AZ where the standby node is deployed. A standby AZ is used for backup and disaster recovery. The standby AZ must be different from the active AZ.	AZ2
   Specifications	Mandatory Currently, the following enterprise switch specifications are supported: Small Maximum Bandwidth: 3 Gbit/s Maximum PPS: 500,000 Connected Subnets: 1 Medium Maximum Bandwidth: 5 Gbit/s Maximum PPS: 1,000,000 Connected Subnets: 3 Large Maximum Bandwidth: 10 Gbit/s Maximum PPS: 2,000,000 Connected Subnets: 6 The specifications cannot be changed after the enterprise switch is created. NOTICE: The supported enterprise switch specifications vary by region. See the supported specifications on the console.	Large
   VPC	Mandatory VPC that the enterprise switch belongs to.	vpc-01
   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 Direct Connect or VPN. Enterprise switches allow communications between cloud and on-premises networks at Layer 2 based on the Layer 3 network between tunnel subnets.	subnet-01
   Local 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.	Automatically assign IP address
   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 (.).	esw-01
   Description	Optional Enter the description of the enterprise switch in the text box as required.	-

3. Click Next.
4. On the displayed page, 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 Enterprise Switch Getting Started.