diff --git a/docs/esw/umn/UgChangeHistory.html b/docs/esw/umn/UgChangeHistory.html index 23d3aa1fb..bd647686c 100644 --- a/docs/esw/umn/UgChangeHistory.html +++ b/docs/esw/umn/UgChangeHistory.html @@ -8,12 +8,21 @@ -

2026-01-26

+

2026-03-09

+ +

This release incorporates the following changes:

+

Modified the description of refreshing the page to view the deletion result in Procedure.

+

Added the reference link to Table 1 System-defined permissions for VPC in Enterprise Switch Permissions.

+ + +

2026-01-26

This release incorporates the following changes:

Modified the content title and font in Enterprise Switch Advantages.

Modified the enterprise switch specifications in Enterprise Switch Specifications.

Added the description that the VPC configured here is the VPC selected during the enterprise switch creation in Step 1: Use Direct Connect or VPN to Communicate at Layer 3.

+

Added the description of refreshing the page to view the deletion result in Procedure.

+

Adapted the documentation based on version 25.6.0.

2026-01-15

diff --git a/docs/esw/umn/en-us_image_0000002524317984.png b/docs/esw/umn/en-us_image_0000002524317984.png new file mode 100644 index 000000000..d8f9804a8 Binary files /dev/null and b/docs/esw/umn/en-us_image_0000002524317984.png differ diff --git a/docs/esw/umn/en-us_image_0000002524317986.png b/docs/esw/umn/en-us_image_0000002524317986.png new file mode 100644 index 000000000..d8f9804a8 Binary files /dev/null and b/docs/esw/umn/en-us_image_0000002524317986.png differ diff --git a/docs/esw/umn/en-us_image_0000002524477976.png b/docs/esw/umn/en-us_image_0000002524477976.png new file mode 100644 index 000000000..d8f9804a8 Binary files /dev/null and b/docs/esw/umn/en-us_image_0000002524477976.png differ diff --git a/docs/esw/umn/en-us_image_0000002555437361.png b/docs/esw/umn/en-us_image_0000002555437361.png new file mode 100644 index 000000000..d8f9804a8 Binary files /dev/null and b/docs/esw/umn/en-us_image_0000002555437361.png differ diff --git a/docs/esw/umn/en-us_image_0000002555437385.png b/docs/esw/umn/en-us_image_0000002555437385.png new file mode 100644 index 000000000..d8f9804a8 Binary files /dev/null and b/docs/esw/umn/en-us_image_0000002555437385.png differ diff --git a/docs/esw/umn/en-us_image_0000002555437887.png b/docs/esw/umn/en-us_image_0000002555437887.png new file mode 100644 index 000000000..d8f9804a8 Binary files /dev/null and b/docs/esw/umn/en-us_image_0000002555437887.png differ diff --git a/docs/esw/umn/en-us_image_0000002555557291.png b/docs/esw/umn/en-us_image_0000002555557291.png new file mode 100644 index 000000000..d8f9804a8 Binary files /dev/null and b/docs/esw/umn/en-us_image_0000002555557291.png differ diff --git a/docs/esw/umn/en-us_image_0000002555557853.png b/docs/esw/umn/en-us_image_0000002555557853.png new file mode 100644 index 000000000..d8f9804a8 Binary files /dev/null and b/docs/esw/umn/en-us_image_0000002555557853.png differ diff --git a/docs/esw/umn/esw_pd_0002.html b/docs/esw/umn/esw_pd_0002.html index d4c0769fb..9b0d61716 100644 --- a/docs/esw/umn/esw_pd_0002.html +++ b/docs/esw/umn/esw_pd_0002.html @@ -5,7 +5,7 @@

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
+
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
@@ -14,3 +14,10 @@
+ + \ No newline at end of file diff --git a/docs/esw/umn/esw_pd_0003.html b/docs/esw/umn/esw_pd_0003.html index 7f6eaac8d..ce2d61b76 100644 --- a/docs/esw/umn/esw_pd_0003.html +++ b/docs/esw/umn/esw_pd_0003.html @@ -2,7 +2,7 @@

How Enterprise Switches Work

Figure 1 illustrates how an enterprise switch works. Table 1 describes the working principles in more detail.

-
Figure 1 Networking
+
Figure 1 Networking
@@ -140,3 +140,10 @@ + + \ No newline at end of file diff --git a/docs/esw/umn/esw_pd_0004.html b/docs/esw/umn/esw_pd_0004.html index 6013f3f99..cc97f278d 100644 --- a/docs/esw/umn/esw_pd_0004.html +++ b/docs/esw/umn/esw_pd_0004.html @@ -4,7 +4,7 @@

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
+
Figure 1 Layer 3 networking
Table 1 Working principles

No.
@@ -23,7 +23,7 @@

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
+
Figure 2 Layer 2 networking diagram
Table 1 Layer 3 networking description

Description
@@ -48,3 +48,10 @@ + + \ No newline at end of file diff --git a/docs/esw/umn/esw_pd_0005.html b/docs/esw/umn/esw_pd_0005.html index 223556724..f75d62dfe 100644 --- a/docs/esw/umn/esw_pd_0005.html +++ b/docs/esw/umn/esw_pd_0005.html @@ -2,10 +2,10 @@

Functions

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

+

Layer 2 Connections

A Layer 2 connection enables 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.

@@ -19,3 +19,10 @@
+ + \ No newline at end of file diff --git a/docs/esw/umn/esw_pd_0007.html b/docs/esw/umn/esw_pd_0007.html index a7366132a..5bc108346 100644 --- a/docs/esw/umn/esw_pd_0007.html +++ b/docs/esw/umn/esw_pd_0007.html @@ -5,7 +5,7 @@

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

diff --git a/docs/esw/umn/esw_pd_0009.html b/docs/esw/umn/esw_pd_0009.html index a1753e5b7..5c77d7b40 100644 --- a/docs/esw/umn/esw_pd_0009.html +++ b/docs/esw/umn/esw_pd_0009.html @@ -2,7 +2,7 @@

Working with Other Services

Figure 1 illustrates how an enterprise switch works with other cloud services.

-
Figure 1 Interactions between an enterprise switch and other cloud services
+
Figure 1 Interactions between an enterprise switch and other cloud services
Table 2 Layer 2 networking description

Description
@@ -40,3 +40,10 @@ + + \ No newline at end of file diff --git a/docs/esw/umn/esw_qs_0004.html b/docs/esw/umn/esw_qs_0004.html index a2d0878d9..27b6940e2 100644 --- a/docs/esw/umn/esw_qs_0004.html +++ b/docs/esw/umn/esw_qs_0004.html @@ -9,6 +9,8 @@

For details, see Configuring a Direct Connect Connection or Configuring a VPN Connection.

+

Enterprise Switch can work together with VPNs of classic and enterprise editions.

+
  • Submit a service ticket to check whether your Direct Connect or VPN connection supports VXLAN interconnection with an enterprise switch. If your connection does not support this, contact technical support.
    • diff --git a/docs/esw/umn/esw_qs_0005.html b/docs/esw/umn/esw_qs_0005.html index 5dbe476ab..640123ed7 100644 --- a/docs/esw/umn/esw_qs_0005.html +++ b/docs/esw/umn/esw_qs_0005.html @@ -7,11 +7,11 @@

    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. Click in the upper left corner and select the desired region and project.
    3. On the console homepage, choose Network > Enterprise Switch.

      The Enterprise Switch page is displayed.

      +

      Procedure

      1. Log in to the management console.
      2. Click in the upper left corner and select the desired region and project.
      3. 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.

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

        The page for creating an enterprise switch is displayed.

        -
      5. Configure the parameters as prompted. For details, see Table 1.
        Figure 1 Purchasing an enterprise switch
        +
      6. Configure the parameters as prompted. For details, see Table 1.
        Figure 1 Purchasing an enterprise switch
        -
    Table 1 Interactions between an enterprise switch and other cloud services

    Service
    Table 1 Parameters for creating an enterprise switch

    Parameter

    +
    @@ -115,3 +115,10 @@ + + \ No newline at end of file diff --git a/docs/esw/umn/esw_qs_0006.html b/docs/esw/umn/esw_qs_0006.html index de46b30f4..4455728f1 100644 --- a/docs/esw/umn/esw_qs_0006.html +++ b/docs/esw/umn/esw_qs_0006.html @@ -7,9 +7,9 @@

    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. Log in to the management console.
    1. Click in the upper left corner and select the desired region and project.
    2. On the console homepage, choose Network > Enterprise Switch.

      The Enterprise Switch page is displayed.

      +

      Procedure

      1. Log in to the management console.
      1. Click in the upper left corner and select the desired region and project.
      2. 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.

      3. Click the name of the target enterprise switch.

        The enterprise switch details page is displayed.

        -
      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.
        Figure 1 Creating 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.
        Figure 1 Creating a Layer 2 connection
      2. Configure the parameters as prompted. For details, see Table 1.
    Table 1 Parameters for creating an enterprise switch

    Parameter

    Description
    Table 1 Parameters for creating a Layer 2 connection

    Parameter

    @@ -97,3 +97,10 @@ + + \ No newline at end of file diff --git a/docs/esw/umn/esw_qs_0007.html b/docs/esw/umn/esw_qs_0007.html index 096e0c3cf..eface1d30 100644 --- a/docs/esw/umn/esw_qs_0007.html +++ b/docs/esw/umn/esw_qs_0007.html @@ -11,7 +11,7 @@

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

    @@ -32,7 +32,7 @@
    1. 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

    2. Check the VXLAN configuration status in the system view:

      display vxlan vni 5010 verbose

      -
      Figure 2 VXLAN configuration status
      +
      Figure 2 VXLAN configuration status

      If the value of State is up, the tunnel status is normal.

    @@ -144,3 +144,10 @@ BAGG1 srv1000 0 Up Manual
    + + \ No newline at end of file diff --git a/docs/esw/umn/esw_qs_0008.html b/docs/esw/umn/esw_qs_0008.html index e2e3fd498..76e5c923c 100644 --- a/docs/esw/umn/esw_qs_0008.html +++ b/docs/esw/umn/esw_qs_0008.html @@ -7,7 +7,7 @@

    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.
    • @@ -17,3 +17,10 @@ + + \ No newline at end of file diff --git a/docs/esw/umn/esw_ug_0002.html b/docs/esw/umn/esw_ug_0002.html index 3c292e65b..fab113566 100644 --- a/docs/esw/umn/esw_ug_0002.html +++ b/docs/esw/umn/esw_ug_0002.html @@ -7,11 +7,11 @@

    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. Click in the upper left corner and select the desired region and project.
    3. On the console homepage, choose Network > Enterprise Switch.

      The Enterprise Switch page is displayed.

      +

      Procedure

      1. Log in to the management console.
      2. Click in the upper left corner and select the desired region and project.
      3. 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.

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

        The page for creating an enterprise switch is displayed.

        -
      5. Configure the parameters as prompted. For details, see Table 1.
        Figure 1 Purchasing an enterprise switch
        +
      6. 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

        +
        @@ -115,3 +115,10 @@ + + \ No newline at end of file diff --git a/docs/esw/umn/esw_ug_0003.html b/docs/esw/umn/esw_ug_0003.html index 6fad93c0b..eea95a6bd 100644 --- a/docs/esw/umn/esw_ug_0003.html +++ b/docs/esw/umn/esw_ug_0003.html @@ -3,10 +3,10 @@

        Viewing Details of an Enterprise Switch

        Scenarios

        This section describes how to view basic information about an enterprise switch.

        -

        Procedure

        1. Log in to the management console.
        1. Click in the upper left corner and select the desired region and project.
        2. On the console homepage, choose Network > Enterprise Switch.

          The Enterprise Switch page is displayed.

          +

          Procedure

          1. Log in to the management console.
          1. Click in the upper left corner and select the desired region and project.
          2. 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.

          3. 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
          +
          Figure 1 Basic information about the enterprise switch
        @@ -15,3 +15,10 @@
        + + \ No newline at end of file diff --git a/docs/esw/umn/esw_ug_0004.html b/docs/esw/umn/esw_ug_0004.html index 8c88a8f11..273d21b1a 100644 --- a/docs/esw/umn/esw_ug_0004.html +++ b/docs/esw/umn/esw_ug_0004.html @@ -3,7 +3,7 @@

        Modifying an Enterprise Switch

        Scenarios

        This section describes how to change the name of an enterprise switch.

        -

        Procedure

        1. Log in to the management console.
        1. Click in the upper left corner and select the desired region and project.
        2. On the console homepage, choose Network > Enterprise Switch.

          The Enterprise Switch page is displayed.

          +

          Procedure

          1. Log in to the management console.
          1. Click in the upper left corner and select the desired region and project.
          2. 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.

          3. Click the name of the target enterprise switch.

            The enterprise switch details page is displayed.

          4. Click next to the enterprise switch name and enter a new name.
          5. Click .
          @@ -14,3 +14,10 @@
        + + \ No newline at end of file diff --git a/docs/esw/umn/esw_ug_0005.html b/docs/esw/umn/esw_ug_0005.html index 7eda27d4c..7c28faf3b 100644 --- a/docs/esw/umn/esw_ug_0005.html +++ b/docs/esw/umn/esw_ug_0005.html @@ -5,10 +5,10 @@

        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

        1. Log in to the management console.
        1. Click in the upper left corner and select the desired region and project.
        2. On the console homepage, choose Network > Enterprise Switch.

          The Enterprise Switch page is displayed.

          +

          Procedure

          1. Log in to the management console.
          1. Click in the upper left corner and select the desired region and project.
          2. 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.

          3. Click the name of the target enterprise switch.

            The enterprise switch details page is displayed.

          1. In the upper right corner of the enterprise switch details page, click Delete.

            A confirmation dialog box is displayed.

            -
          2. Click OK.

            This operation takes 10 to 60 seconds to complete.

            +
          3. Click OK.

            This operation takes 10 to 60 seconds to complete. If the Delete button is staying inactive after the Layer 2 connections are deleted, refresh the page.

        @@ -18,3 +18,10 @@ + + \ No newline at end of file diff --git a/docs/esw/umn/esw_ug_0007.html b/docs/esw/umn/esw_ug_0007.html index eb2a7aecc..b701a8097 100644 --- a/docs/esw/umn/esw_ug_0007.html +++ b/docs/esw/umn/esw_ug_0007.html @@ -5,9 +5,9 @@

        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. Log in to the management console.
        1. Click in the upper left corner and select the desired region and project.
        2. On the console homepage, choose Network > Enterprise Switch.

          The Enterprise Switch page is displayed.

          +

          Procedure

          1. Log in to the management console.
          1. Click in the upper left corner and select the desired region and project.
          2. 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.

          3. Click the name of the target enterprise switch.

            The enterprise switch details page is displayed.

            -
          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.
            Figure 1 Creating 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.
            Figure 1 Creating a Layer 2 connection
          2. Configure the parameters as prompted. For details, see Table 1.
        Table 1 Parameters for creating an enterprise switch

        Parameter

        Description
        Table 1 Parameters for creating a Layer 2 connection

        Parameter

        @@ -94,3 +94,10 @@ + + \ No newline at end of file diff --git a/docs/esw/umn/esw_ug_0008.html b/docs/esw/umn/esw_ug_0008.html index bb26e8e4b..4f78f5acb 100644 --- a/docs/esw/umn/esw_ug_0008.html +++ b/docs/esw/umn/esw_ug_0008.html @@ -3,9 +3,9 @@

        Viewing Details of a Layer 2 Connection

        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

        1. Log in to the management console.
        1. Click in the upper left corner and select the desired region and project.
        2. On the console homepage, choose Network > Enterprise Switch.

          The Enterprise Switch page is displayed.

          +

          Procedure

          1. Log in to the management console.
          1. Click in the upper left corner and select the desired region and project.
          2. 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.

          3. Click the name of the target enterprise switch.

            The enterprise switch details page is displayed.

            -
          4. 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
            +
          5. 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
        @@ -15,3 +15,10 @@
        + + \ No newline at end of file diff --git a/docs/esw/umn/esw_ug_0009.html b/docs/esw/umn/esw_ug_0009.html index ad77f26c5..f4b9466c1 100644 --- a/docs/esw/umn/esw_ug_0009.html +++ b/docs/esw/umn/esw_ug_0009.html @@ -3,7 +3,7 @@

        Modifying a Layer 2 Connection Name

        Scenarios

        This section describes how to change the name of a Layer 2 connection.

        -

        Procedure

        1. Log in to the management console.
        2. Click in the upper left corner and select the desired region and project.
        3. On the console homepage, choose Network > Enterprise Switch.

          The Enterprise Switch page is displayed.

          +

          Procedure

          1. Log in to the management console.
          2. Click in the upper left corner and select the desired region and project.
          3. 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.

          4. Click the name of the target enterprise switch.

            The enterprise switch details page is displayed.

          5. In the lower part of the enterprise switch details page, locate the Layer 2 connection.
          6. Click next to the Layer 2 connection name and enter a new name.
          7. Click .
          @@ -14,3 +14,10 @@
        + + \ No newline at end of file diff --git a/docs/esw/umn/esw_ug_0010.html b/docs/esw/umn/esw_ug_0010.html index 5b1303e6c..27a635c28 100644 --- a/docs/esw/umn/esw_ug_0010.html +++ b/docs/esw/umn/esw_ug_0010.html @@ -5,7 +5,7 @@

        Notes and Constraints

        Layer 2 connections to be deleted cannot be in the Creating status.

        -

        Procedure

        1. Log in to the management console.
        1. Click in the upper left corner and select the desired region and project.
        2. On the console homepage, choose Network > Enterprise Switch.

          The Enterprise Switch page is displayed.

          +

          Procedure

          1. Log in to the management console.
          1. Click in the upper left corner and select the desired region and project.
          2. 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.

          3. Click the name of the target enterprise switch.

            The enterprise switch details page is displayed.

          4. In the lower part of the enterprise switch details page, locate the Layer 2 connection.
          5. Click Delete Connection.

            A confirmation dialog box is displayed.

          6. Click OK.

            This operation takes 10 to 30 seconds to complete.

            @@ -18,3 +18,10 @@
        + + \ No newline at end of file diff --git a/docs/esw/umn/esw_ug_0015.html b/docs/esw/umn/esw_ug_0015.html index 2479a193a..73695c130 100644 --- a/docs/esw/umn/esw_ug_0015.html +++ b/docs/esw/umn/esw_ug_0015.html @@ -3,7 +3,7 @@

        Viewing Metrics

        Scenarios

        This section describes how to view metrics for an enterprise switch.

        -

        Procedure

        1. Log in to the management console.
        2. Click in the upper left corner and select the desired region and project.
        3. In the upper left corner of the page, click to open the service list and choose Management & Deployment > Cloud Eye.
        4. In the navigation pane on the left, choose Cloud Service Monitoring > Enterprise Switch.
        5. Locate the enterprise switch and click View Metric in the Operation column.

          The metrics are displayed.

          +

          Procedure

          1. Log in to the management console.
          2. Click in the upper left corner and select the desired region and project.
          3. In the upper left corner of the page, click to open the service list and choose Management & Deployment > Cloud Eye.
          4. In the navigation pane on the left, choose Cloud Service Monitoring > Enterprise Switch.
          5. Locate the enterprise switch and click View Metric in the Operation column.

            The metrics are displayed.

          6. View the metrics.
        @@ -13,3 +13,10 @@
        + + \ No newline at end of file diff --git a/docs/esw/umn/public_sys-resources/imageclose.gif b/docs/esw/umn/public_sys-resources/imageclose.gif new file mode 100644 index 000000000..3a3344af4 Binary files /dev/null and b/docs/esw/umn/public_sys-resources/imageclose.gif differ diff --git a/docs/esw/umn/public_sys-resources/imageclosehover.gif b/docs/esw/umn/public_sys-resources/imageclosehover.gif new file mode 100644 index 000000000..8699d5e36 Binary files /dev/null and b/docs/esw/umn/public_sys-resources/imageclosehover.gif differ diff --git a/docs/esw/umn/public_sys-resources/imagemax.gif b/docs/esw/umn/public_sys-resources/imagemax.gif new file mode 100644 index 000000000..99c07dc25 Binary files /dev/null and b/docs/esw/umn/public_sys-resources/imagemax.gif differ diff --git a/docs/esw/umn/public_sys-resources/imagemaxhover.gif b/docs/esw/umn/public_sys-resources/imagemaxhover.gif new file mode 100644 index 000000000..d01d77d6e Binary files /dev/null and b/docs/esw/umn/public_sys-resources/imagemaxhover.gif differ diff --git a/docs/esw/umn/public_sys-resources/macFFBgHack.png b/docs/esw/umn/public_sys-resources/macFFBgHack.png new file mode 100644 index 000000000..ec811470c Binary files /dev/null and b/docs/esw/umn/public_sys-resources/macFFBgHack.png differ