Help Center/ Enterprise Switch/ User Guide/ Layer 2 Connections/ Creating a Layer 2 Connection
Updated on 2024-09-09 GMT+08:00
View PDF
Share

Creating a Layer 2 Connection

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

  1. Go to the Enterprise Switch page.

    Locate the enterprise switch that you want to create a Layer-2 connection.

  1. In the lower right part of the enterprise switch details page, click Create Connection.

    The page for creating a Layer 2 connection is displayed.

  2. Configure the parameters as prompted. For details, see Table 1.
    Table 1 Parameters for creating a Layer-2 connection

    Parameter

    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, that 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 a Layer 2 connection cannot be used by any other Layer 2 connections or enterprise switches.

    subnet-01

    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.

    -

    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
  3. 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.

Parent topic: Layer 2 Connections