The following lists some switch models that support the VXLAN function.
- Huawei switches: Huawei CE58, CE68, CE78, and CE88 series switches, such as CE6870, CE6875, CE6881, CE6863, and CE12800 switches
- Switches of other vendors: Cisco Nexus 9300 and H3C S6520 series switches
+
+
Possible causes and solutions:
- The VXLAN tunnel of your data center is not properly configured.
Log in to the switch of your data center and check its tunnel configurations. For details, see Step 4: Configure a Tunnel Gateway in Your Data Center.
+ - The Direct Connect or VPN connection fails.
Check the Direct Connect or VPN connection configurations.
+
+
+
+
Possible cause: The VXLAN tunnel of your data center is not properly configured.
+
Solution:
+
Log in to the switch of your data center and check its tunnel configurations. For details, see Step 4: Configure a Tunnel Gateway in Your Data Center.
+
Enterprise switches enable Layer 2 networking for VPCs, helping you to connect cloud and on-premises networks that are highly reliable, in a large scale, and of high performance.
+
Currently, enterprise switches only support Layer 2 connection gateways (L2CGs). An L2CG is a virtual tunnel gateway that can work with Direct Connect or VPN to establish network communications between cloud and on-premises networks at Layer 2. The gateway allows you to migrate workloads in data centers or private clouds to the cloud without changing subnets and IP addresses.
+
VPN or Direct Connect only allows cloud and on-premises networks to communicate with each other at Layer 3 and the CIDR blocks of the networks that are used for communication cannot overlap.
+
If the cloud and on-premises networks overlap and need to communicate with each other, you can use an enterprise switch to enable communication between them at Layer 2.
+
An enterprise switch is a tunnel gateway of a VPC and corresponds to the tunnel gateway of your data center. It can work together with Direct Connect or VPN to enable communications between a VPC and your on-premises data center at Layer 2.
Figure 1 shows the networking diagram. You need to connect a VPC subnet to the enterprise switch and specify the enterprise switch to establish a connection with the tunnel gateway of your on-premises data center so that the VPC subnet can communicate with the data center subnet at Layer 2.
Figure 1 Layer 2 networking
+
+
Figure 1 illustrates how an enterprise switch works. Table 1 describes the working principles in more detail.
+
Figure 1 Networking
+
+
Table 1 Working principlesNo.
+ |
+Action
+ |
+Description
+ |
+
|---|
+
+1
+ |
+Enable the local and remote tunnel subnets to communicate at Layer 3.
+ |
+- Plan resources on and off the cloud. For details, see Table 2.
- Use Direct Connect or VPN to enable the local (Subnet-tunnel-L01) and remote (Subnet-tunnel-R01) tunnel subnets to communicate at Layer 3.
+ |
+
+2
+ |
+Create an enterprise switch and specify a tunnel subnet.
+ |
+Create an enterprise switch, set the local tunnel subnet to Subnet-tunnel-L01, and the local tunnel IP address to 192.168.100.101.
+ |
+
+3
+ |
+Create a Layer 2 connection.
+ |
+Create a Layer 2 connection to enable the local Layer 2 connection subnet (Subnet-layer-L01) and the remote VXLAN switch to communicate at Layer 2.
+Configure the following parameters:
+
+ |
+
+4
+ |
+Configure a tunnel gateway in the on-premises data center.
+ |
+Configure a tunnel gateway on the remote VXLAN switch to establish a VXLAN tunnel for the remote Layer 2 connection subnet (Subnet-layer-R01).
+ |
+
+
+
+
+
+
Table 2 Resource detailsResource
+ |
+Cloud (Local)
+ |
+On Premises (Remote)
+ |
+
|---|
+
+Layer 2 connection subnet
+ |
+VPC subnet
+ |
+Subnet-layer-L01: 192.168.0.0/24
+ |
+On-premises subnet
+ |
+Subnet-layer-R01: 192.168.0.0/24
+ |
+
+ECS
+ |
+- ECS-layer-L01-A: 192.168.0.50
- ECS-layer-L01-B: 192.168.0.51
+ |
+On-premises server
+ |
+- VM-layer-R01-A: 192.168.0.60
- VM-layer-R01-B: 192.168.0.61
+ |
+
+Active and standby interface IP addresses
+ |
+- Active interface IP address: 192.168.0.7
- Standby interface IP address: 192.168.0.8
+ |
+-
+ |
+-
+ |
+
+Tunnel subnet
+ |
+VPC subnet
+ |
+Subnet-tunnel-L01: 192.168.100.0/24
+ |
+On-premises subnet
+ |
+Subnet-tunnel-R01: 200.51.51.0/24
+ |
+
+Tunnel IP address
+ |
+192.168.100.101
+ |
+Tunnel IP address
+ |
+200.51.51.100
+ |
+
+Tunnel VNI
+ |
+10001
+ |
+
+
+
+
+
Layer 2 Connection Subnets
Layer 2 connection subnets include a local Layer 2 connection subnet and a remote Layer 2 connection subnet. They are used for communications at Layer 2.
+
- Local Layer 2 connection subnet: a VPC subnet, for example, Subnet-layer-L01
- Remote Layer 2 connection subnet: an on-premises subnet, for example, Subnet-layer-R01
+
Constraints
- The local and remote Layer 2 connection subnets can overlap, but the IP addresses of the servers that need to communicate in the local and remote subnets must be different. Otherwise, the communication fails.
- A VPC subnet that has been used by a Layer 2 connection cannot be used by any other Layer 2 connections or enterprise switches.
+
+
+
Tunnel Subnets
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.
- Local tunnel subnet: a VPC subnet, for example, Subnet-tunnel-L01
- Remote tunnel subnet: an on-premises subnet, for example, Subnet-tunnel-R01
+
+
Constraints
+
- Ensure that the local and remote tunnel subnets can communicate at Layer 3 over VPN or Direct Connect before you use an enterprise switch to allow communication at Layer 2.
- 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.
+
+
Layer 2 Connections
After an enterprise switch is created, you need to create a Layer 2 connection to enable the local Layer 2 connection subnet and the remote VXLAN switch to communicate with each other at Layer 2.
+
Constraints
- Each Layer 2 connection connects a local and a remote Layer 2 connection subnet. Each enterprise switch supports a maximum of six Layer 2 connections.
- The Layer 2 connections of an enterprise switch can share a tunnel IP address, but their tunnel VNIs must be unique. A tunnel VNI is the identifier of a tunnel.
- If a Layer 2 connection connects a local Layer 2 connection subnet to an enterprise switch, the local Layer 2 connection subnet must have two IP addresses reserved as active and standby interface IP addresses. The two IP addresses cannot be used by any local resources and must be different from the IP addresses in the remote Layer 2 connection subnet.
+
+
+
Active and Standby Interface IP Addresses
If a Layer 2 connection connects a local Layer 2 connection subnet to an enterprise switch, the local Layer 2 connection subnet must have two IP addresses reserved as active and standby interface IP addresses.
+
+
Tunnel IP Addresses
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.
+
- Local tunnel IP address: in the local tunnel subnet. In this example, the local tunnel subnet is Subnet-tunnel-L01, and the tunnel IP address is 192.168.100.101.
- Remote tunnel IP address: in the remote tunnel subnet. In this example, the remote tunnel subnet is Subnet-tunnel-R01, and the tunnel IP address is 200.51.51.100.
+
+
Tunnel VNIs
Tunnel VNIs are used to uniquely identify the VXLAN tunnels between an on-premises data center and an enterprise switch.
+
For the same VXLAN tunnel, the on-premises data center and the cloud must use the same tunnel VNI.
+
+
Generally, you may use VPN or Direct Connect to enable communications between on-premises data centers and VPCs at Layer 3. However, this may require network reconstruction, delay cloud migration, and cause service interruptions. For details, see Constraints on Layer 3 Networking Between an On-Premises Data Center and the Cloud (Without Enterprise Switches).
+
Enterprise switches allow communications between on-premises data centers and VPCs at Layer 2, helping you dynamically and smoothly migrate workloads to the cloud. For details, see Advantages of Layer 2 Networking Between an On-Premises Data Center and the Cloud (Using an Enterprise Switch).
+
Constraints on Layer 3 Networking Between an On-Premises Data Center and the Cloud (Without Enterprise Switches)
Figure 1 shows the Layer 3 networking between on-premises data centers and VPCs using VPN or Direct Connect. Table 1 describes the pain points.
+
Figure 1 Layer 3 networking
+
+
Table 1 Layer 3 networking descriptionDescription
+ |
+VPN or Direct Connect allows the communication between on-premises data centers and VPCs at Layer 3 through routes.
+ |
+
|---|
+Pain Points
+ |
+- The CIDR blocks of the on-premises data center and the VPC that are used for communication cannot overlap.
On-premises workloads communicate with each other using IP addresses instead of domain names. If the CIDR blocks of the on-premises data center and the VPC that are used for communication overlap, the on-premises network needs to be reconstructed before the cloud migration, which prolongs the cloud migration period, interrupts businesses, and increases O&M costs.
+ - Workloads in a subnet have to be migrated together, and cloud and on-premises workloads in the same subnet cannot communicate with each other.
Dozens of different workloads are deployed on each subnet of the on-premises data center. If workloads are migrated by subnet, business continuity cannot be ensured.
+
+ |
+
|---|
+
+
+
+
+
Advantages of Layer 2 Networking Between an On-Premises Data Center and the Cloud (Using an Enterprise Switch)
To handle the pain points of cloud migration at Layer 3, you can use enterprise switches to allow the communication between on-premises data centers and VPCs at Layer 2. For details about the advantages of enterprise switches, see Table 2.
+
Figure 2 Layer 2 networking diagram
+
+
Table 2 Layer 2 networking descriptionDescription
+ |
+Enterprise switches establish a Layer 2 network between on-premises data centers and VPCs based on the Layer 3 network established by VPN or Direct Connect.
+ |
+
|---|
+Advantages
+ |
+- The CIDR blocks of the on-premises data center and the VPC that are used for communication can overlap.
An enterprise switch allows the network of the on-premises data center to remain unchanged even if the data center and the VPC have overlapping CIDR blocks.
+ - Workloads can be migrated to the cloud on a server basis, and cloud and on-premises workloads in the same subnet can communicate with each other.
Workloads can be seamlessly migrated to the cloud to prevent any loss caused by cloud migration.
+
+ |
+
|---|
+
+
+
+
+
Enterprise Switches
Enterprise switches support Layer 2 connection gateways (L2CGs) now. An L2CG is a virtual tunnel gateway that can work with Direct Connect or VPN to establish network communications between cloud and on-premises networks at Layer 2. The gateway allows you to migrate workloads in data centers or private clouds to the cloud without changing subnets and IP addresses.
+
Figure 1 Layer 2 networking
+
For details, see Enterprise Switches.
+
+
Layer 2 Connections
A Layer 2 connection enable a local Layer 2 connection subnet and a remote VXLAN switch to communicate at Layer 2. Each Layer 2 connection connects a local and a remote Layer 2 connection subnet.
+
After an enterprise switch is created, you need to create a Layer 2 connection.
+
For details, see Creating a Layer 2 Connection.
+
+
Monitoring
Cloud Eye lets you keep a close eye on the performance and resource utilization of enterprise switches, ensuring enterprise switch reliability and availability. You can also configure Cloud Eye to alert you of any potential issues in enterprise switches in real time.
+
For details, see Cloud Eye Monitoring.
+
+
If you need to assign different permissions to employees in your enterprise to control their access to your enterprise switches, you can use Identity and Access Management (IAM) for fine-grained permissions management. IAM provides functions such as identity authentication, permissions management, and access control.
+
With IAM, you can create IAM users and assign permissions to the users to control their access to specific resources.
+
If your account does not need individual IAM users for permissions management, skip this section.
+
IAM can be used free of charge. You pay only for the resources in your account. For more information about IAM, see "Service Overview" in the Identity and Access Management User Guide.
+
Enterprise Switch Permissions
By default, new IAM users do not have any permissions assigned. You need to add them to one or more groups and attach roles to these groups so that these users can inherit permissions from the groups and perform specified operations on cloud services.
+
Enterprise Switch is a project-level service deployed and accessed in specific physical regions. You need to select a project for which the permissions will be granted. If you select All projects, the permissions will be granted for all the projects. You need to switch to the authorized region before accessing Enterprise Switch.
+
Enterprise Switch uses the same system permissions as VPC. Table 1 lists all the system-defined roles and policies supported by VPC. This VPC role is dependent on other roles. When assigning VPC roles to users, you need to also assign dependent roles for the VPC permissions to take effect.
+
+
Table 1 System-defined permissions for VPCPolicy Name
+ |
+Description
+ |
+Policy Type
+ |
+Dependencies
+ |
+
|---|
+
+VPC FullAccess
+ |
+Full permissions for VPC.
+ |
+System-defined policy
+ |
+To use the VPC flow log function, users must also have the LTS ReadOnlyAccess permission.
+ |
+
+VPC ReadOnlyAccess
+ |
+Read-only permissions on VPC.
+ |
+System-defined policy
+ |
+None
+ |
+
+VPC Administrator
+ |
+Most permissions on VPC, excluding creating, modifying, deleting, and viewing security groups and security group rules.
+To be granted this permission, users must also have the Tenant Guest and Server Administrator permission.
+ |
+System-defined role
+ |
+Tenant Guest and Server Administrator policies, which must be attached in the same project as VPC Administrator.
+ |
+
+
+
+
+
Table 2 lists the common operations supported by system-defined identity policies for Enterprise Switch.
+
+
Table 2 Common operations supported by system-defined identity policiesOperation
+ |
+VPC ReadOnlyAccess
+ |
+VPC Administrator
+ |
+VPC FullAccess
+ |
+Tenant Guest
+ |
+
|---|
+
+Creating an enterprise switch
+ |
+Not supported
+ |
+Supported
+ |
+Not supported
+ |
+Not supported
+ |
+
+Modifying an enterprise switch
+ |
+Not supported
+ |
+Supported
+ |
+Not supported
+ |
+Not supported
+ |
+
+Deleting an enterprise switch
+ |
+Not supported
+ |
+Supported
+ |
+Not supported
+ |
+Not supported
+ |
+
+Viewing an enterprise switch
+ |
+Not supported
+ |
+Supported
+ |
+Not supported
+ |
+Supported
+ |
+
+Creating a Layer 2 connection
+ |
+Not supported
+ |
+Supported
+ |
+Not supported
+ |
+Not supported
+ |
+
+Modifying a Layer 2 connection
+ |
+Not supported
+ |
+Supported
+ |
+Not supported
+ |
+Not supported
+ |
+
+Deleting a Layer 2 connection
+ |
+Not supported
+ |
+Supported
+ |
+Not supported
+ |
+Not supported
+ |
+
+Viewing a Layer 2 connection
+ |
+Not supported
+ |
+Supported
+ |
+Not supported
+ |
+Supported
+ |
+
+Viewing specifications
+ |
+Not supported
+ |
+Supported
+ |
+Not supported
+ |
+Supported
+ |
+
+Viewing quotas
+ |
+Not supported
+ |
+Supported
+ |
+Not supported
+ |
+Supported
+ |
+
+Viewing the AZ
+ |
+Not supported
+ |
+Supported
+ |
+Not supported
+ |
+Supported
+ |
+
+Binding a virtual IP address
+ |
+Not supported
+ |
+Supported
+ |
+Not supported
+ |
+Not supported
+ |
+
+Unbinding a virtual IP address
+ |
+Not supported
+ |
+Supported
+ |
+Not supported
+ |
+Not supported
+ |
+
+
+
+
+
+
Concept
A region and availability zone (AZ) identify the location of a data center. You can create resources in a specific region and AZ.
+
- A region is a physical data center, which is completely isolated to improve fault tolerance and stability. The region that is selected during resource creation cannot be changed after the resource is created.
- An AZ is a physical location where resources use independent power supplies and networks. A region contains one or more AZs that are physically isolated but interconnected through internal networks. Because AZs are isolated from each other, any fault that occurs in one AZ will not affect others.
+
Figure 1 shows the relationship between regions and AZs.
+
Figure 1 Regions and AZs
+
+
Selecting a Region
You are advised to select a region close to you or your target users. This helps ensure low access latency.
+
+
Selecting an AZ
When deploying resources, consider your applications' requirements on disaster recovery (DR) and network latency.
+
- For high DR capability, deploy resources in different AZs within the same region.
- For lower network latency, deploy resources in the same AZ.
+
+
Regions and Endpoints
Before you use an API to call resources, specify its region and endpoint. For more details, see Regions and Endpoints.
+
+
Figure 1 illustrates how an enterprise switch works with other cloud services.
+
Figure 1 Interactions between an enterprise switch and other cloud services
+
+
Table 1 Interactions between an enterprise switch and other cloud servicesService
+ |
+Interaction
+ |
+
|---|
+
+Virtual Private Cloud (VPC)
+ |
+VPCs can use enterprise switches to communicate with on-premises data centers at Layer 2.
+ |
+
+Direct Connect
+ |
+Direct Connect or VPN allows the communication between on-premises data centers and VPCs at Layer 3. Based on the Layer 3 network, enterprise switches establish a Layer 2 network between on-premises data centers and VPCs.
+ |
+
+Virtual Private Network (VPN)
+ |
+VPN allows the communication between on-premises data centers and VPCs at Layer 3. Based on the Layer 3 network, enterprise switches establish a Layer 2 network between on-premises data centers and VPCs.
+ |
+
+Identity and Access Management (IAM)
+ |
+With IAM, you can assign different permissions to different users to control their access to enterprise switch resources.
+ |
+
+
+
+
+
Three enterprise switch specifications are supported: basic, enhanced, and standard. For details, see Table 1.
+
+
Table 1 SpecificationsSpecifications
+ |
+Maximum Bandwidth
+ |
+Maximum PPS
+ |
+Connected Subnets
+ |
+
|---|
+
+Basic
+ |
+3 Gbit/s
+ |
+500,000
+ |
+1
+ |
+
+Standard
+ |
+5 Gbit/s
+ |
+1,000,000
+ |
+3
+ |
+
+Enhanced
+ |
+10 Gbit/s
+ |
+2,000,000
+ |
+6
+ |
+
+
+
+
+
Enterprise switches establish a Layer 2 network between on-premises data centers and VPCs based on the Layer 3 network established by VPN or Direct Connect. Figure 1 shows the configuration process of enterprise switches.
+
Figure 1 Enterprise switch configuration flowchart
+
+
Table 1 Process descriptionNo.
+ |
+Step
+ |
+Description
+ |
+
|---|
+
+1
+ |
+Step 1: Use Direct Connect or VPN to Communicate at Layer 3
+ |
+An enterprise switch establishes a Layer 2 network based on a Layer 3 network between an on-premises data center and a VPC. This section describes how to create a Direct Connect or VPN connection between an on-premises data center and a VPC at Layer 3.
+ |
+
+2
+ |
+Step 2: Create an Enterprise Switch
+ |
+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.
+ |
+
+3
+ |
+Step 3: Create a Layer 2 Connection
+ |
+After an enterprise switch is created, you need to create a Layer 2 connection to enable the local Layer 2 connection subnet and the remote VXLAN switch to communicate at Layer 2.
+ |
+
+4
+ |
+Step 4: Configure a Tunnel Gateway in Your Data Center
+ |
+This section describes how to configure the tunnel gateway on a VXLAN tunnel switch of an on-premises data center.
+ |
+
+
+
+
+
Scenarios
An enterprise switch establishes a Layer 2 network based on a Layer 3 network between an on-premises data center and a VPC. This section describes how to create a Direct Connect or VPN connection between an on-premises data center and a VPC at Layer 3.
+
+
+
+
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.
+
+
+
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. - On the console homepage, 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 switchParameter
+ |
+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.
+ |
+-
+ |
+
+
+
+
- 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.
+
+
Scenarios
After an enterprise switch is created, you need to create a Layer 2 connection to enable the local Layer 2 connection subnet and the remote VXLAN switch to communicate at Layer 2.
+
+
Notes and Constraints
- Each Layer 2 connection connects a local and a remote Layer 2 connection subnet. Each enterprise switch supports a maximum of six Layer 2 connections.
- The Layer 2 connections of an enterprise switch can share a tunnel IP address, but their tunnel VNIs must be unique. A tunnel VNI is the identifier of a tunnel.
- If a Layer 2 connection connects a local Layer 2 connection subnet to an enterprise switch, the local Layer 2 connection subnet must have two IP addresses reserved as active and standby interface IP addresses. The two IP addresses cannot be used by any local resources and must be different from the IP addresses in the remote Layer 2 connection subnet.
+
+
Procedure
- Log in to the management console.
- Click
in the upper left corner and select the desired region and project. - On the console homepage, choose Network > Enterprise Switch.
The Enterprise Switch page is displayed.
+ - Click the name of the target enterprise switch.
The enterprise switch details page is displayed.
+
- In the lower right part of the enterprise switch details page, click Create Connection.
The page for creating a Layer 2 connection is displayed.
Figure 1 Creating a Layer 2 connection
+
- Configure the parameters as prompted. For details, see Table 1.
+
Table 1 Parameters for creating a Layer 2 connectionParameter
+ |
+Description
+ |
+Example Value
+ |
+
|---|
+
+Enterprise Switch
+ |
+Name of the enterprise switch. You do not need to set this parameter.
+ |
+l2cg-01
+ |
+
+VPC
+ |
+VPC that is associated with the enterprise switch, which is the VPC that the local tunnel subnet belongs to. You do not need to set this parameter.
+ |
+vpc-01
+ |
+
+Layer 2 Connection Subnet
+ |
+Mandatory
+Select the layer 2 connection subnet in the VPC. This Layer 2 connection subnet is used to communicate with the Layer 2 connection subnet in an on-premises data center at Layer 2.
+- The local and remote Layer 2 connection subnets can overlap, but the IP addresses of the servers that need to communicate in the local and remote subnets must be different. Otherwise, the communication fails.
- A VPC subnet that has been used by a Layer 2 connection cannot be used by any other Layer 2 connections or enterprise switches.
+ |
+subnet-02
+ |
+
+Interface IP Address
+ |
+Mandatory
+IP addresses in the VPC subnet that are connected to the enterprise switch, including active and standby interface IP addresses. The IP addresses can be automatically assigned or manually specified.
+ |
+Automatically assign
+ |
+
+Remote Access Information > Tunnel VNI
+ |
+Mandatory
+Network identifier of the VXLAN tunnel used by an on-premises data center to connect to an enterprise switch, which is used to uniquely identify the VXLAN. For the same VXLAN tunnel, the on-premises data center and the cloud must use the same tunnel VNI.
+ |
+10001
+ |
+
+Remote Access Information > Tunnel IP Address
+ |
+Mandatory
+IP address of the VXLAN tunnel used by the on-premises data center to connect to the enterprise switch.
+ |
+192.168.2.11
+ |
+
+Remote Access Information > Tunnel Port
+ |
+Port number of the VXLAN tunnel used by the on-premises data center to connect to the enterprise switch. Port 4789 is used by default. You do not need to set this parameter.
+ |
+4789
+ |
+
+Name
+ |
+Mandatory
+Enter the name of the Layer 2 connection. The name: - Must contain 1 to 64 characters.
- Can contain letters, digits, underscores (_), hyphens (-), and periods (.).
+ |
+l2conn-01
+ |
+
+
+
+
- Click Create.
This operation takes 20 to 60 seconds to complete. If the status is Not connected or Connected, the Layer 2 connection is created.
+
+
+
Scenarios
This section describes how to configure the tunnel gateway on a VXLAN tunnel switch of an on-premises data center.
+
The following uses CE6850 and H3C S6520 series switches as examples. To check more configurations, see the product documentation of the corresponding switch.
+
+
+
Notes and Constraints
If you use an enterprise switch to connect your on-premises data center to the cloud, the switches of your data center must support the VXLAN function. If high reliability is required, the VXLAN switches need to be deployed in disaster recovery mode.
+
The following lists some switch models that support the VXLAN function.
- Huawei switches: Huawei CE58, CE68, CE78, and CE88 series switches, such as CE6870, CE6875, CE6881, CE6863, and CE12800 switches
- Switches of other vendors: Cisco Nexus 9300 and H3C S6520 series switches
+
+
+
Networking Example
In this example, the Layer 2 subnet gateway and the VXLAN tunnel are on different switches.
+
The tunnel IP address on the cloud is 10.0.6.3, the tunnel IP address of the tunnel switch on the on-premises data center is 2.2.2.2, and the tunnel VNI is 5010.
+
Figure 1 Layer 2 subnet gateway and VXLAN tunnel on different switches
+
+
Procedure (CE6850 Switches)
Configure the tunnel switch of your data center to divert the traffic of the VLAN corresponding to the Layer 2 subnet to the tunnel.
+
Currently, most CE series switches do not support forwarding of encapsulated VXLAN packets through Layer 3 sub-interfaces. Layer 3 sub-interfaces cannot be used by VXLAN uplinks (connected to enterprise switches). Instead, VLAN interfaces can be used.
+
+
- Log in to the tunnel switch and run the system-view command to switch to the system view.
- Switch to the loopback 0 interface view and configure the tunnel IP address.
Example:
+interface loopback 0
+ip address 2.2.2.2 255.255.255.255
+
- Use the quit command to exit the interface view and return to the system view.
- Switch to the bridge domain (BD) view and configure the VXLAN VNI for the BD.
Example:
+bridge-domain 10
+vxlan vni 5010
+ - Use the quit command to exit the BD view and return to the system view.
- Create a Layer 2 sub-interface and use the sub-interface to divert traffic from the VLAN at Layer 2 to the tunnel.
Example:
+interface 10ge 1/0/2.1 mode l2
+encapsulation dot1q vid 100
+bridge-domain 10
+
- Use the interface nve command to create an NVE interface, switch to the NVE interface view, and configure the IP address (2.2.2.2) for the source VTEP of the VXLAN tunnel.
Example:
+interface nve1
+source 2.2.2.2
+
- Use the vni command in the NVE interface view to configure an ingress replication list for VNI 5010.
Example:
+vni 5010 head-end peer-list 10.0.6.3
+ - Check the VXLAN configuration status in the system view:
display vxlan vni 5010 verbose
+Figure 2 VXLAN configuration status
+If the value of State is up, the tunnel status is normal.
+
+
+
Procedure (H3C S6520 Switches)
Establish a VXLAN tunnel between a VXLAN switch and an enterprise switch, associate the VXLAN tunnel with a VXLAN, so that Layer 2 packets from VMs can be encapsulated into IP packets and then sent to the enterprise switch. Configure Ethernet service instances and matching rules on downlink interfaces of a VXLAN switch to identify the VXLAN that packets belong to.
+
- Configure the switch to work in VXLAN mode.
Save the configuration, and restart the switch. (Skip this step if the switch is already working in VXLAN mode.)
+Example:
+<SwitchA> system-view
+[SwitchA] switch-mode 1
+Reboot device to make the configuration take effect.
+[SwitchA] quit
+<SwitchA> reboot
+Start to check configuration with next startup configuration file, please wait..
+.......DONE!
+Current configuration may be lost after the reboot, save current configuration?
+[Y/N]:y
+This command will reboot the device. Continue? [Y/N]:y
+
- Create a tunnel interface and configure an IP address for the interface.
Create a loopback interface and configure an IP address for the loopback interface as the remote IP address of the VXLAN tunnel.
+Example:
+[SwitchA] interface loopback 0
+[SwitchA-LoopBack0] ip address 2.2.2.2 32
+ For a new interface IP address (including the loopback interface IP address) of the VXLAN switch, check whether there is a route to direct traffic from the IP address to the tunnel subnet of the enterprise switch. If there is no such a route, configure one on the VXLAN switch. The VXLAN switch can be an aggregation switch or a core switch. Select a switch based on the network plan.
+
+ - Create a VXLAN.
- Enable L2VPN.
Example:
+<SwitchA> system-view
+[SwitchA] l2vpn enable
+ - Enable Layer 2 forwarding for the VXLAN tunnel.
Example:
+[SwitchA] undo vxlan ip-forwarding
+ - Create the VSI vpna and VXLAN 5010.
Example:
+[SwitchA] vsi vpna
+[SwitchA-vsi-vpna] vxlan 5010
+[SwitchA-vsi-vpna-vxlan5010] quit
+[SwitchA-vsi-vpna] quit
+ The VXLAN ID must be the same as the tunnel VNI in remote access information configured during Layer 2 connection creation in Table 1.
+
+
+ - Create a VXLAN tunnel.
Create a VXLAN tunnel (Tunnel1) to the enterprise switch.
+Example:
+[SwitchA] interface tunnel 1 mode vxlan
+[SwitchA-Tunnel1] source 2.2.2.2
+[SwitchA-Tunnel1] destination 10.0.6.3
+[SwitchA-Tunnel1] quit
+
- Associate the VXLAN with the VXLAN tunnel.
On the VXLAN switch, associate the VXLAN tunnel (Tunnel1) with VXLAN 5010.
+Example:
+[SwitchA] vsi vpna
+[SwitchA-vsi-vpna] vxlan 5010
+[SwitchA-vsi-vpna-vxlan5010] tunnel 1
+[SwitchA-vsi-vpna-vxlan5010] quit
+[SwitchA-vsi-vpna] quit
+ - A maximum of six Layer 2 connections can be created on an enterprise switch. Each connection corresponds to a VXLAN. Multiple VXLANs can be associated with the same VXLAN tunnel, such as, Tunnel1.
- A VXLAN switch can connect to multiple enterprise switches. In this case, you can associate multiple VXLAN tunnels, for example, Tunnel1 and Tunnel2, with the same VXLAN.
+
+
- Configure an Ethernet service instance to match frames and associate the instance with the VSI.
Create Ethernet service instance 1000 on Bridge-Aggregation1 of the VXLAN switch to match frames of VLAN 100 and associate the instance with VSI vpna (VXLAN 5010).
+Example:
+[SwitchA] Bridge-Aggregation 1
+[SwitchA-Bridge-Aggregation1] port link-type trunk
+[SwitchA-Bridge-Aggregation1] service-instance 1000
+[SwitchA-Bridge-Aggregation1-srv1000] encapsulation s-vid 100
+[SwitchA-Bridge-Aggregation1-srv1000] xconnect vsi vpna
+[SwitchA-Bridge-Aggregation1-srv1000] quit
+[SwitchA-Bridge-Aggregation1] quit
+ The method for creating Ethernet service instances on physical Ethernet interfaces of switches is similar.
+
+ - Check the status of the VXLAN tunnel interface.
- The status of the VXLAN tunnel interface is Up.
Example:
+[SwitchA]display interface Tunnel 1
+Tunnel1
+Current state: UP
+Line protocol state: UP
+Description: Tunnel1 Interface
+Bandwidth: 64 kbps
+Maximum transmission unit: 1464
+Internet protocol processing: Disabled
+Last clearing of counters: 17:19:44 Fri 01/18/2013
+Tunnel source 2.2.2.2, destination 10.0.6.3
+Tunnel protocol/transport UDP_VXLAN/IP
+Last 300 seconds input rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec
+Last 300 seconds output rate: 0 bytes/sec, 0 bits/sec, 0 packets/sec
+Input: 0 packets, 0 bytes, 4 drops
+Output: 0 packets, 0 bytes, 0 drops
+
+- Check the VSI information. The VXLAN tunnel associated with the VXLAN and the Ethernet service instance associated with the VSI are in Up status.
Example:
+[SwitchA]display l2vpn vsi verbose
+VSI Name: vnpa
+VSI Index : 1
+VSI State : Up
+MTU : 1500
+Bandwidth : -
+Broadcast Restrain : -
+Multicast Restrain : -
+Unknown Unicast Restrain: -
+MAC Learning : Enabled
+MAC Table Limit : -
+MAC Learning rate : -
+Drop Unknown : -
+Flooding : Enabled
+Statistics : Disabled
+VXLAN ID : 5010
+Tunnels:
+Tunnel Name Link ID State Type Flood proxy
+Tunnel1 0x5000001 UP Manual Disabled
+ACs:
+AC Link ID State Type
+BAGG1 srv1000 0 Up Manual
+
+
+
+
Scenarios
Assume that there is an ECS (ecs-demo-01) running in the local subnet and an ECS (ecs-demo-02) running in the remote subnet with the IP address of 10.1.1.105. You can follow this section to log in to ecs-demo-01 and verify the network connectivity between VPCs.
+
+
Procedure
- Log in to the ECS.
- Run the following command on the ECS:
ping <private-IP-address-of-the-ECS>
+To verify the network connectivity between vpc-01 and vpc-02, log in to ecs-demo-01 and run the following command:
+ping 10.1.1.105
+If information similar to the following is displayed, the two VPCs can communicate with each other.
+
+ - Repeat 1 to 2 to verify the connectivity between other VPCs.
+
+
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.
+
+
+
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.
- On the console homepage, 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 switchParameter
+ |
+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.
+ |
+-
+ |
+
+
+
+
- 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.
+
+
Scenarios
This section describes how to view basic information about an enterprise switch.
+
+
Procedure
- Log in to the management console.
- Click
in the upper left corner and select the desired region and project. - On the console homepage, choose Network > Enterprise Switch.
The Enterprise Switch page is displayed.
+ - Click the name of the target enterprise switch.
You can view the basic information about the enterprise switch.
+
+
Figure 1 Basic information about the enterprise switch
+
+
Scenarios
This section describes how to change the name of an enterprise switch.
+
+
Procedure
- Log in to the management console.
- Click
in the upper left corner and select the desired region and project. - On the console homepage, choose Network > Enterprise Switch.
The Enterprise Switch page is displayed.
+ - Click the name of the target enterprise switch.
The enterprise switch details page is displayed.
+ - Click
next to the enterprise switch name and enter a new name. - Click
.
+
+
Scenarios
You can delete an enterprise switch to release resources and reduce costs if it is no longer required.
+
+
Notes and Constraints
An enterprise switch with Layer 2 connections associated cannot be deleted. To delete such an enterprise switch, delete the Layer 2 connections first. For details, see Deleting a Layer 2 Connection.
+
+
Procedure
- Log in to the management console.
- Click
in the upper left corner and select the desired region and project. - On the console homepage, choose Network > Enterprise Switch.
The Enterprise Switch page is displayed.
+ - Click the name of the target enterprise switch.
The enterprise switch details page is displayed.
+
- In the upper right corner of the enterprise switch details page, click Delete.
A confirmation dialog box is displayed.
+ - Click OK.
This operation takes 10 to 60 seconds to complete.
+
+
+
Scenarios
After an enterprise switch is created, you need to create a Layer 2 connection to enable the local Layer 2 connection subnet and the remote VXLAN switch to communicate at Layer 2.
+
+
Notes and Constraints
- Each Layer 2 connection connects a local and a remote Layer 2 connection subnet. Each enterprise switch supports a maximum of six Layer 2 connections.
- The Layer 2 connections of an enterprise switch can share a tunnel IP address, but their tunnel VNIs must be unique. A tunnel VNI is the identifier of a tunnel.
- If a Layer 2 connection connects a local Layer 2 connection subnet to an enterprise switch, the local Layer 2 connection subnet must have two IP addresses reserved as active and standby interface IP addresses. The two IP addresses cannot be used by any local resources and must be different from the IP addresses in the remote Layer 2 connection subnet.
+
+
Procedure
- Log in to the management console.
- Click in the upper left corner and select the desired region and project.
- On the console homepage, choose Network > Enterprise Switch.
The Enterprise Switch page is displayed.
+ - Click the name of the target enterprise switch.
The enterprise switch details page is displayed.
+
- In the lower right part of the enterprise switch details page, click Create Connection.
The page for creating a Layer 2 connection is displayed.
Figure 1 Creating a Layer 2 connection
+
- Configure the parameters as prompted. For details, see Table 1.
+
Table 1 Parameters for creating a Layer 2 connectionParameter
+ |
+Description
+ |
+Example Value
+ |
+
|---|
+
+Enterprise Switch
+ |
+Name of the enterprise switch. You do not need to set this parameter.
+ |
+l2cg-01
+ |
+
+VPC
+ |
+VPC that is associated with the enterprise switch, which is the VPC that the local tunnel subnet belongs to. You do not need to set this parameter.
+ |
+vpc-01
+ |
+
+Layer 2 Connection Subnet
+ |
+Mandatory
+Select the layer 2 connection subnet in the VPC. This Layer 2 connection subnet is used to communicate with the Layer 2 connection subnet in an on-premises data center at Layer 2.
+- The local and remote Layer 2 connection subnets can overlap, but the IP addresses of the servers that need to communicate in the local and remote subnets must be different. Otherwise, the communication fails.
- A VPC subnet that has been used by a Layer 2 connection cannot be used by any other Layer 2 connections or enterprise switches.
+ |
+subnet-02
+ |
+
+Interface IP Address
+ |
+Mandatory
+IP addresses in the VPC subnet that are connected to the enterprise switch, including active and standby interface IP addresses. The IP addresses can be automatically assigned or manually specified.
+ |
+Automatically assign
+ |
+
+Remote Access Information > Tunnel VNI
+ |
+Mandatory
+Network identifier of the VXLAN tunnel used by an on-premises data center to connect to an enterprise switch, which is used to uniquely identify the VXLAN. For the same VXLAN tunnel, the on-premises data center and the cloud must use the same tunnel VNI.
+ |
+10001
+ |
+
+Remote Access Information > Tunnel IP Address
+ |
+Mandatory
+IP address of the VXLAN tunnel used by the on-premises data center to connect to the enterprise switch.
+ |
+192.168.2.11
+ |
+
+Remote Access Information > Tunnel Port
+ |
+Port number of the VXLAN tunnel used by the on-premises data center to connect to the enterprise switch. Port 4789 is used by default. You do not need to set this parameter.
+ |
+4789
+ |
+
+Name
+ |
+Mandatory
+Enter the name of the Layer 2 connection. The name: - Must contain 1 to 64 characters.
- Can contain letters, digits, underscores (_), hyphens (-), and periods (.).
+ |
+l2conn-01
+ |
+
+
+
+
- Click Create.
This operation takes 20 to 60 seconds to complete. If the status is Not connected or Connected, the Layer 2 connection is created.
+
+
+
Scenarios
This section describes how to view the basic information and topology of a Layer 2 connection, including the local and remote Layer 2 connection subnets, and local and remote tunnel IP addresses.
+
+
Procedure
- Log in to the management console.
- Click
in the upper left corner and select the desired region and project. - On the console homepage, choose Network > Enterprise Switch.
The Enterprise Switch page is displayed.
+ - Click the name of the target enterprise switch.
The enterprise switch details page is displayed.
+ - In the lower part of the enterprise switch details page, view the basic information and topology of a Layer 2 connection.
Figure 1 Basic information about the Layer 2 connection
+
+
+
Scenarios
This section describes how to change the name of a Layer 2 connection.
+
+
Procedure
- Log in to the management console.
- Click
in the upper left corner and select the desired region and project. - On the console homepage, choose Network > Enterprise Switch.
The Enterprise Switch page is displayed.
+ - Click the name of the target enterprise switch.
The enterprise switch details page is displayed.
+ - In the lower part of the enterprise switch details page, locate the Layer 2 connection.
- Click
next to the Layer 2 connection name and enter a new name. - Click
.
+
+
Scenarios
You can delete a Layer 2 connection if it is not needed anymore.
+
+
Notes and Constraints
Layer 2 connections to be deleted cannot be in the Creating status.
+
+
Procedure
- Log in to the management console.
- Click
in the upper left corner and select the desired region and project. - On the console homepage, choose Network > Enterprise Switch.
The Enterprise Switch page is displayed.
+ - Click the name of the target enterprise switch.
The enterprise switch details page is displayed.
+ - In the lower part of the enterprise switch details page, locate the Layer 2 connection.
- Click Delete Connection.
A confirmation dialog box is displayed.
+ - Click OK.
This operation takes 10 to 30 seconds to complete.
+
+
+
This section describes how to use IAM to implement fine-grained permissions control for your enterprise switch resources. With IAM, you can:
- Create IAM users for employees based on the organizational structure of your enterprise. Each IAM user has their own security credentials, providing access to enterprise switch resources.
- Grant only the permissions required for users to perform a specific task.
+
+
If your account does not require individual IAM users, skip over this section.
+
Figure 1 shows the procedure for granting permissions.
+
Prerequisites
You have learned about the permissions supported by Enterprise Switch and choose policies or roles according to your requirements. Enterprise Switch uses the same system permissions as VPC. For details, see Permissions.
+
+
Process Flow
Figure 1 Process for granting Enterprise Switch permissions
+
- Create a user group and assign permissions.
Create a user group on the IAM console, and assign the Tenant Guest policy to the group.
+ - Create a user and add the user to the user group.
Create a user on the IAM console and add the user to the group created in 1.
+ - Log in and verify permissions.
Click Service List and choose Enterprise Switch. Then click Create in the upper right corner. If the enterprise switch fails to be created, the Tenant Guest permission has taken effect.
+
+
+
Description
This section describes metrics reported by enterprise switches to Cloud Eye as well as their namespaces, metrics, and dimensions. You can use the Cloud Eye management console or APIs to obtain the metrics and alarms generated for enterprise switches.
+
+
+
Monitoring Metrics
With Cloud Eye, you can monitor the network status of enterprise switches.
+
+
Table 1 Enterprise switch metricsID
+ |
+Name
+ |
+Description
+ |
+Value Range
+ |
+Unit
+ |
+Conversion Rule
+ |
+Monitored Object (Dimension)
+ |
+Monitoring Interval (Raw Data)
+ |
+
|---|
+
+outbound bandwidth
+ |
+Outbound Bandwidth
+ |
+Network traffic per second going out of the enterprise switch
+ |
+≥ 0
+ |
+bit/s
+ |
+1024 (IEC)
+ |
+instance_id
+ |
+1 minute
+ |
+
+inbound bandwidth
+ |
+Inbound Bandwidth
+ |
+Network traffic per second going into the enterprise switch
+ |
+≥ 0
+ |
+bit/s
+ |
+1024 (IEC)
+ |
+instance_id
+ |
+1 minute
+ |
+
+outbound traffic
+ |
+Outbound Traffic
+ |
+Network traffic going out of the enterprise switch
+ |
+≥ 0
+ |
+byte
+ |
+1024 (IEC)
+ |
+instance_id
+ |
+1 minute
+ |
+
+inbound traffic
+ |
+Inbound Traffic
+ |
+Network traffic going into the enterprise switch
+ |
+≥ 0
+ |
+byte
+ |
+1024 (IEC)
+ |
+instance_id
+ |
+1 minute
+ |
+
+outbound pps
+ |
+Outbound PPS
+ |
+Packets per second going out of the enterprise switch
+ |
+≥ 0
+ |
+pps
+ |
+N/A
+ |
+instance_id
+ |
+1 minute
+ |
+
+inbound pps
+ |
+Inbound PPS
+ |
+Packets per second going into the enterprise switch
+ |
+≥ 0
+ |
+pps
+ |
+N/A
+ |
+instance_id
+ |
+1 minute
+ |
+
+
+
+
+
+
Dimensions
The metric measurement dimension of an enterprise switch is instance_id.
+
+
Key
+ |
+Value
+ |
+
|---|
+
+instance_id
+ |
+Enterprise switch ID.
+ |
+
+
+
+
+
+
Scenarios
This section describes how to view metrics for an enterprise switch.
+
+
Procedure
- Log in to the management console.
- Click
in the upper left corner and select the desired region and project. - In the upper left corner of the page, click
to open the service list and choose Management & Deployment > Cloud Eye. - In the navigation pane on the left, choose Cloud Service Monitoring > Enterprise Switch.
- Locate the enterprise switch and click View Metric in the Operation column.
The metrics are displayed.
+ - View the metrics.
+
+