fanqinying
a2e28c7623
Reviewed-by: Hajba, László Antal <laszlo-antal.hajba@t-systems.com> Co-authored-by: fanqinying <fanqinying@huawei.com> Co-committed-by: fanqinying <fanqinying@huawei.com>
13 KiB
Creating 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 or Direct Connect.
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 Direct Connect or VPN connection first by referring to Step 1: Use Direct Connect or VPN to Communicate at Layer 3.
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
- Log in to the management console.
- Click
in the upper left corner and select the desired region and project. - Click
in the upper left corner of the page to open the service list and choose Network > Enterprise Switch.The Enterprise Switch page is displayed.
- In the upper right corner of the page, click Create.
The page for creating an enterprise switch is displayed.
- Configure the parameters as prompted. For details, see Table 1.Figure 1 Purchasing an enterprise switch
Table 1 Parameters for creating an enterprise switch Parameter
Description
Example Value
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.
AZ1
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.
AZ2
Specifications
Mandatory
Currently, the following enterprise switch specifications are supported:- Basic
- Maximum Bandwidth: 3 Gbit/s
- Maximum PPS: 500,000
- Connected Subnets: 1
- Standard
- Maximum Bandwidth: 5 Gbit/s
- Maximum PPS: 1,000,000
- Connected Subnets: 3
- Enhanced
- Maximum Bandwidth: 10 Gbit/s
- Maximum PPS: 2,000,000
- Connected Subnets: 6
Basic
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.
-
- Basic
- Click Next.
- 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 Getting Started.