ESW UMN 20251117 version

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>
This commit is contained in:
2026-02-02 15:03:38 +00:00
committed by zuul
parent b662a89e70
commit 03e77f3e5b
85 changed files with 2933 additions and 0 deletions

View File

@ -0,0 +1,96 @@
<a name="esw_ug_0007"></a><a name="esw_ug_0007"></a>
<h1 class="topictitle1">Creating a Layer 2 Connection</h1>
<div id="body8662426"><div class="section" id="esw_ug_0007__section58516512444"><h4 class="sectiontitle">Scenarios</h4><p id="esw_ug_0007__p39941441191">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.</p>
</div>
<div class="section" id="esw_ug_0007__section943919266467"><h4 class="sectiontitle">Notes and Constraints</h4><ul id="esw_ug_0007__ul1940419218205"><li id="esw_ug_0007__esw_pd_0003_li6479184113290">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.</li><li id="esw_ug_0007__esw_pd_0003_li13479104119290">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.</li><li id="esw_ug_0007__esw_pd_0003_li1150515917135">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.</li></ul>
</div>
<div class="section" id="esw_ug_0007__section157779324467"><h4 class="sectiontitle">Procedure</h4><ol id="esw_ug_0007__ol16180165352717"><li id="esw_ug_0007__li136721200154">Log in to the management console.</li></ol><ol start="2" id="esw_ug_0007__ol1158164217346"><li id="esw_ug_0007__li4507204020171">Click <span><img id="esw_ug_0007__en-us_topic_0118498823_image338921514480" src="en-us_image_0000002007168462.png"></span> in the upper left corner and select the desired region and project.</li><li id="esw_ug_0007__li20507134015170">On the console homepage, choose <strong id="esw_ug_0007__b16161840941"><span id="esw_ug_0007__text13161154013413">Network</span><span id="esw_ug_0007__text171612401443"></span></strong> &gt; <strong id="esw_ug_0007__b216144018416">Enterprise Switch</strong>.<p class="msonormal" id="esw_ug_0007__p17227719152010">The <strong id="esw_ug_0007__b690512135318">Enterprise Switch</strong> page is displayed.</p>
</li><li class="msonormal" id="esw_ug_0007__li674581611388">Click the name of the target enterprise switch.<p id="esw_ug_0007__p107268382301"><a name="esw_ug_0007__li674581611388"></a><a name="li674581611388"></a>The enterprise switch details page is displayed.</p>
</li></ol><ol start="5" id="esw_ug_0007__ol1233924923818"><li id="esw_ug_0007__li1053682214527">In the lower right part of the enterprise switch details page, click <strong id="esw_ug_0007__b183453154511">Create Connection</strong>.<div class="p" id="esw_ug_0007__p19356825105215">The page for creating a Layer 2 connection is displayed.<div class="fignone" id="esw_ug_0007__fig66971451181312"><span class="figcap"><b>Figure 1 </b>Creating a Layer 2 connection</span><br><span><img id="esw_ug_0007__image7697851101320" src="en-us_image_0000002516237194.png"></span></div>
</div>
</li><li id="esw_ug_0007__li515516418471">Configure the parameters as prompted. For details, see <a href="#esw_ug_0007__en-us_topic_0228866532_table37675406">Table 1</a>.
<div class="tablenoborder"><a name="esw_ug_0007__en-us_topic_0228866532_table37675406"></a><a name="en-us_topic_0228866532_table37675406"></a><table cellpadding="4" cellspacing="0" summary="" id="esw_ug_0007__en-us_topic_0228866532_table37675406" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Parameters for creating a Layer 2 connection</caption><thead align="left"><tr id="esw_ug_0007__en-us_topic_0228866532_row19509166"><th align="left" class="cellrowborder" valign="top" width="16.48%" id="mcps1.3.3.4.2.2.2.4.1.1"><p id="esw_ug_0007__en-us_topic_0228866532_p36738639"><strong id="esw_ug_0007__b1962492218471">Parameter</strong></p>
</th>
<th align="left" class="cellrowborder" valign="top" width="61.77%" id="mcps1.3.3.4.2.2.2.4.1.2"><p id="esw_ug_0007__en-us_topic_0228866532_p6031802"><strong id="esw_ug_0007__b76351623134712">Description</strong></p>
</th>
<th align="left" class="cellrowborder" valign="top" width="21.75%" id="mcps1.3.3.4.2.2.2.4.1.3"><p id="esw_ug_0007__p03782045144816"><strong id="esw_ug_0007__b46041824184719">Example Value</strong></p>
</th>
</tr>
</thead>
<tbody><tr id="esw_ug_0007__en-us_topic_0228866532_row35107966"><td class="cellrowborder" valign="top" width="16.48%" headers="mcps1.3.3.4.2.2.2.4.1.1 "><p id="esw_ug_0007__p7191101245410">Enterprise Switch</p>
</td>
<td class="cellrowborder" valign="top" width="61.77%" headers="mcps1.3.3.4.2.2.2.4.1.2 "><p id="esw_ug_0007__en-us_topic_0228866532_p30392459">Name of the enterprise switch. You do not need to set this parameter.</p>
</td>
<td class="cellrowborder" valign="top" width="21.75%" headers="mcps1.3.3.4.2.2.2.4.1.3 "><p id="esw_ug_0007__p033541891814">l2cg-01</p>
</td>
</tr>
<tr id="esw_ug_0007__en-us_topic_0228866532_row10177686"><td class="cellrowborder" valign="top" width="16.48%" headers="mcps1.3.3.4.2.2.2.4.1.1 "><p id="esw_ug_0007__en-us_topic_0228866532_p19086203">VPC</p>
</td>
<td class="cellrowborder" valign="top" width="61.77%" headers="mcps1.3.3.4.2.2.2.4.1.2 "><p id="esw_ug_0007__en-us_topic_0228866532_p22307299">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.</p>
</td>
<td class="cellrowborder" valign="top" width="21.75%" headers="mcps1.3.3.4.2.2.2.4.1.3 "><p id="esw_ug_0007__p15335141813186">vpc-01</p>
</td>
</tr>
<tr id="esw_ug_0007__en-us_topic_0228866532_row10968764"><td class="cellrowborder" valign="top" width="16.48%" headers="mcps1.3.3.4.2.2.2.4.1.1 "><p id="esw_ug_0007__en-us_topic_0228866532_p16054720">Layer 2 Connection Subnet</p>
</td>
<td class="cellrowborder" valign="top" width="61.77%" headers="mcps1.3.3.4.2.2.2.4.1.2 "><p id="esw_ug_0007__p19137184372318">Mandatory</p>
<p id="esw_ug_0007__en-us_topic_0228866532_p26948909">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.</p>
<ul id="esw_ug_0007__ul1366419494324"><li id="esw_ug_0007__esw_pd_0003_li48073460714">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.</li><li id="esw_ug_0007__esw_pd_0003_li38072461477">A VPC subnet that has been used by a Layer 2 connection cannot be used by any other Layer 2 connections or enterprise switches.</li></ul>
</td>
<td class="cellrowborder" valign="top" width="21.75%" headers="mcps1.3.3.4.2.2.2.4.1.3 "><p id="esw_ug_0007__p18335101831816">subnet-02</p>
</td>
</tr>
<tr id="esw_ug_0007__en-us_topic_0228866532_row49967046"><td class="cellrowborder" valign="top" width="16.48%" headers="mcps1.3.3.4.2.2.2.4.1.1 "><p id="esw_ug_0007__en-us_topic_0228866532_p20798924">Interface IP Address</p>
</td>
<td class="cellrowborder" valign="top" width="61.77%" headers="mcps1.3.3.4.2.2.2.4.1.2 "><p id="esw_ug_0007__p581014992315">Mandatory</p>
<p id="esw_ug_0007__en-us_topic_0228866532_p29420684">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.</p>
</td>
<td class="cellrowborder" valign="top" width="21.75%" headers="mcps1.3.3.4.2.2.2.4.1.3 "><p id="esw_ug_0007__p11379154513485">Automatically assign</p>
</td>
</tr>
<tr id="esw_ug_0007__en-us_topic_0228866532_row4482025"><td class="cellrowborder" valign="top" width="16.48%" headers="mcps1.3.3.4.2.2.2.4.1.1 "><p id="esw_ug_0007__p736603331118">Remote Access Information &gt; Tunnel VNI</p>
</td>
<td class="cellrowborder" valign="top" width="61.77%" headers="mcps1.3.3.4.2.2.2.4.1.2 "><p id="esw_ug_0007__p515365932519">Mandatory</p>
<p id="esw_ug_0007__en-us_topic_0228866532_p48848201">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.</p>
</td>
<td class="cellrowborder" valign="top" width="21.75%" headers="mcps1.3.3.4.2.2.2.4.1.3 "><p id="esw_ug_0007__p113799458485">10001</p>
</td>
</tr>
<tr id="esw_ug_0007__en-us_topic_0228866532_row36980629"><td class="cellrowborder" valign="top" width="16.48%" headers="mcps1.3.3.4.2.2.2.4.1.1 "><p id="esw_ug_0007__p14101478126">Remote Access Information &gt; Tunnel IP Address</p>
</td>
<td class="cellrowborder" valign="top" width="61.77%" headers="mcps1.3.3.4.2.2.2.4.1.2 "><p id="esw_ug_0007__p041784268">Mandatory</p>
<p id="esw_ug_0007__en-us_topic_0228866532_p57840791">IP address of the VXLAN tunnel used by the on-premises data center to connect to the enterprise switch.</p>
</td>
<td class="cellrowborder" valign="top" width="21.75%" headers="mcps1.3.3.4.2.2.2.4.1.3 "><p id="esw_ug_0007__p19807139263">192.168.2.11</p>
</td>
</tr>
<tr id="esw_ug_0007__en-us_topic_0228866532_row50805071"><td class="cellrowborder" valign="top" width="16.48%" headers="mcps1.3.3.4.2.2.2.4.1.1 "><p id="esw_ug_0007__p18410134715129">Remote Access Information &gt; Tunnel Port</p>
</td>
<td class="cellrowborder" valign="top" width="61.77%" headers="mcps1.3.3.4.2.2.2.4.1.2 "><p id="esw_ug_0007__en-us_topic_0228866532_p21099428">Port number of the VXLAN tunnel used by the on-premises data center to connect to the enterprise switch. Port <strong id="esw_ug_0007__b5220191464917">4789</strong> is used by default. You do not need to set this parameter.</p>
</td>
<td class="cellrowborder" valign="top" width="21.75%" headers="mcps1.3.3.4.2.2.2.4.1.3 "><p id="esw_ug_0007__p11379194511488">4789</p>
</td>
</tr>
<tr id="esw_ug_0007__en-us_topic_0228866532_row55677130"><td class="cellrowborder" valign="top" width="16.48%" headers="mcps1.3.3.4.2.2.2.4.1.1 "><p id="esw_ug_0007__en-us_topic_0228866532_p13553692">Name</p>
</td>
<td class="cellrowborder" valign="top" width="61.77%" headers="mcps1.3.3.4.2.2.2.4.1.2 "><p id="esw_ug_0007__p18653105983416">Mandatory</p>
<div class="p" id="esw_ug_0007__p18290848124616">Enter the name of the Layer 2 connection. The name:<ul id="esw_ug_0007__ul19290124834615"><li id="esw_ug_0007__li429094814465">Must contain 1 to 64 characters.</li><li id="esw_ug_0007__li2049371295513">Can contain letters, digits, underscores (_), hyphens (-), and periods (.).</li></ul>
</div>
</td>
<td class="cellrowborder" valign="top" width="21.75%" headers="mcps1.3.3.4.2.2.2.4.1.3 "><p id="esw_ug_0007__p2379245184812">l2conn-01</p>
</td>
</tr>
</tbody>
</table>
</div>
</li><li id="esw_ug_0007__li527317355518">Click <strong id="esw_ug_0007__b1951211151113">Create</strong>.<p id="esw_ug_0007__p12483203965111">This operation takes 20 to 60 seconds to complete. If the status is <strong id="esw_ug_0007__b17771958152511">Not connected</strong> or <strong id="esw_ug_0007__b1077145810259">Connected</strong>, the Layer 2 connection is created.</p>
</li></ol>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="esw_ug_0006.html">Layer 2 Connections</a></div>
</div>
</div>