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>

docs/esw/umn/PARAMETERS.txt

@@ -0,0 +1,3 @@
+version=""
+language="en-us"
+type=""

docs/esw/umn/UgChangeHistory.html

@@ -0,0 +1,52 @@
+<a name="UgChangeHistory"></a><a name="UgChangeHistory"></a>
+
+<h1 class="topictitle1">Change History</h1>
+<div id="body0000001216067188">
+<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="UgChangeHistory__table5447141110445" frame="border" border="1" rules="all"><thead align="left"><tr id="UgChangeHistory__row13448111184419"><th align="left" class="cellrowborder" valign="top" width="33.58%" id="mcps1.3.1.1.3.1.1"><p id="UgChangeHistory__p444816119441">Released on</p>
+</th>
+<th align="left" class="cellrowborder" valign="top" width="66.42%" id="mcps1.3.1.1.3.1.2"><p id="UgChangeHistory__p11448141174412">Description</p>
+</th>
+</tr>
+</thead>
+<tbody><tr id="UgChangeHistory__row1449122791120"><td class="cellrowborder" valign="top" width="33.58%" headers="mcps1.3.1.1.3.1.1 "><p id="UgChangeHistory__p15019278115">2026-01-26</p>
+</td>
+<td class="cellrowborder" valign="top" width="66.42%" headers="mcps1.3.1.1.3.1.2 "><p id="UgChangeHistory__p18931154841115">This release incorporates the following changes:</p>
+<p id="UgChangeHistory__p16931174815115">Modified the content title and font in <a href="esw_pd_0004.html">Enterprise Switch Advantages</a>.</p>
+<p id="UgChangeHistory__p4851650201112">Modified the enterprise switch specifications in <a href="esw_pd_0011.html">Enterprise Switch Specifications</a>.</p>
+<p id="UgChangeHistory__p101087362135">Added the description that the VPC configured here is the VPC selected during the enterprise switch creation in <a href="esw_qs_0004.html">Step 1: Use Direct Connect or VPN to Communicate at Layer 3</a>.</p>
+</td>
+</tr>
+<tr id="UgChangeHistory__row662420472229"><td class="cellrowborder" valign="top" width="33.58%" headers="mcps1.3.1.1.3.1.1 "><p id="UgChangeHistory__p156251247182216">2026-01-15</p>
+</td>
+<td class="cellrowborder" valign="top" width="66.42%" headers="mcps1.3.1.1.3.1.2 "><p id="UgChangeHistory__p3743124016236">This release incorporates the following changes:</p>
+<p id="UgChangeHistory__p97021530102410">Added <a href="esw_pd_0011.html">Enterprise Switch Specifications</a>.</p>
+</td>
+</tr>
+<tr id="UgChangeHistory__row162426171931"><td class="cellrowborder" valign="top" width="33.58%" headers="mcps1.3.1.1.3.1.1 "><p id="UgChangeHistory__p12143111916312">2025-12-25</p>
+</td>
+<td class="cellrowborder" valign="top" width="66.42%" headers="mcps1.3.1.1.3.1.2 "><p id="UgChangeHistory__p131433191639">This release incorporates the following changes:</p>
+<p id="UgChangeHistory__p1242920361238">Modified the screenshots in section <a href="esw_ug_0002.html">Creating an Enterprise Switch</a>.</p>
+</td>
+</tr>
+<tr id="UgChangeHistory__row1536316488414"><td class="cellrowborder" valign="top" width="33.58%" headers="mcps1.3.1.1.3.1.1 "><p id="UgChangeHistory__p23637489415">2025-12-18</p>
+</td>
+<td class="cellrowborder" valign="top" width="66.42%" headers="mcps1.3.1.1.3.1.2 "><p id="UgChangeHistory__p1036334811418">This release incorporates the following changes:</p>
+<p id="UgChangeHistory__p133078591844">Added <a href="esw_pd_0005.html">Functions</a>.</p>
+</td>
+</tr>
+<tr id="UgChangeHistory__row13816145561215"><td class="cellrowborder" valign="top" width="33.58%" headers="mcps1.3.1.1.3.1.1 "><p id="UgChangeHistory__p118162555124">2025-11-21</p>
+</td>
+<td class="cellrowborder" valign="top" width="66.42%" headers="mcps1.3.1.1.3.1.2 "><p id="UgChangeHistory__p143114017151">This release incorporates the following changes:</p>
+<p id="UgChangeHistory__p19319014152">Modified the enterprise switch specifications and added screenshots in section <a href="esw_ug_0002.html">Creating an Enterprise Switch</a>.</p>
+</td>
+</tr>
+<tr id="UgChangeHistory__row3448411154414"><td class="cellrowborder" valign="top" width="33.58%" headers="mcps1.3.1.1.3.1.1 "><p id="UgChangeHistory__p644819118445">2025-09-30</p>
+</td>
+<td class="cellrowborder" valign="top" width="66.42%" headers="mcps1.3.1.1.3.1.2 "><p id="UgChangeHistory__p544891124414">This issue is the first official release.</p>
+</td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+

docs/esw/umn/esw_faq_0001.html

@@ -0,0 +1,15 @@
+<a name="esw_faq_0001"></a><a name="esw_faq_0001"></a>
+
+<h1 class="topictitle1">FAQs</h1>
+<div id="body5485596"></div>
+<div>
+<ul class="ullinks">
+<li class="ulchildlink"><strong><a href="esw_faq_0002.html">What Switches Can Connect to Enterprise Switches?</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="esw_faq_0003.html">Why Is the Layer 2 Connection in the Not Connected State Even After Its Configuration Is Complete?</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="esw_faq_0005.html">Why Is Communication Between the Cloud and On-premises Servers Unavailable Even When the Layer 2 Connection Status Is Connected?</a></strong><br>
+</li>
+</ul>
+</div>
+

docs/esw/umn/esw_faq_0002.html

@@ -0,0 +1,12 @@
+<a name="esw_faq_0002"></a><a name="esw_faq_0002"></a>
+
+<h1 class="topictitle1">What Switches Can Connect to Enterprise Switches?</h1>
+<div id="body1589441955226"><div class="p" id="esw_faq_0002__p27051185226">The following lists some switch models that support the VXLAN function.<ul id="esw_faq_0002__esw_qs_0007_ul799415552562"><li id="esw_faq_0002__esw_qs_0007_li137091656102117">Huawei switches: Huawei CE58, CE68, CE78, and CE88 series switches, such as CE6870, CE6875, CE6881, CE6863, and CE12800 switches</li><li id="esw_faq_0002__esw_qs_0007_li11691428791">Switches of other vendors: Cisco Nexus 9300 and H3C S6520 series switches</li></ul>
+</div>
+</div>
+<div>
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a href="esw_faq_0001.html">FAQs</a></div>
+</div>
+</div>
+

docs/esw/umn/esw_faq_0003.html

@@ -0,0 +1,15 @@
+<a name="esw_faq_0003"></a><a name="esw_faq_0003"></a>
+
+<h1 class="topictitle1">Why Is the Layer 2 Connection in the Not Connected State Even After Its Configuration Is Complete?</h1>
+<div id="body1589441955226"><div class="p" id="esw_faq_0003__p12651363415">Possible causes and solutions:<ol id="esw_faq_0003__ol165133617413"><li id="esw_faq_0003__li128615251756">The VXLAN tunnel of your data center is not properly configured.<p id="esw_faq_0003__p46001227455"><a name="esw_faq_0003__li128615251756"></a><a name="li128615251756"></a>Log in to the switch of your data center and check its tunnel configurations. For details, see <a href="esw_qs_0007.html">Step 4: Configure a Tunnel Gateway in Your Data Center</a>.</p>
+</li><li id="esw_faq_0003__li07839241377">The Direct Connect or VPN connection fails.<p id="esw_faq_0003__p88561042125020"><a name="esw_faq_0003__li07839241377"></a><a name="li07839241377"></a>Check the Direct Connect or VPN connection configurations.</p>
+
+</li></ol>
+</div>
+</div>
+<div>
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a href="esw_faq_0001.html">FAQs</a></div>
+</div>
+</div>
+

docs/esw/umn/esw_faq_0005.html

@@ -0,0 +1,13 @@
+<a name="esw_faq_0005"></a><a name="esw_faq_0005"></a>
+
+<h1 class="topictitle1">Why Is Communication Between the Cloud and On-premises Servers Unavailable Even When the Layer 2 Connection Status Is Connected?</h1>
+<div id="body1589441955226"><p id="esw_faq_0005__p939833523218"><strong id="esw_faq_0005__b028120387918">Possible cause:</strong> The VXLAN tunnel of your data center is not properly configured.</p>
+<p id="esw_faq_0005__p82031659111910"><strong id="esw_faq_0005__b135751912164511">Solution:</strong></p>
+<p id="esw_faq_0005__p145957218315">Log in to the switch of your data center and check its tunnel configurations. For details, see <a href="esw_qs_0007.html">Step 4: Configure a Tunnel Gateway in Your Data Center</a>.</p>
+</div>
+<div>
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a href="esw_faq_0001.html">FAQs</a></div>
+</div>
+</div>
+

docs/esw/umn/esw_pd_0001.html

@@ -0,0 +1,27 @@
+<a name="esw_pd_0001"></a><a name="esw_pd_0001"></a>
+
+<h1 class="topictitle1">Service Overview</h1>
+<div id="body15047603"></div>
+<div>
+<ul class="ullinks">
+<li class="ulchildlink"><strong><a href="esw_pd_0002.html">What Is an Enterprise Switch?</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="esw_pd_0004.html">Enterprise Switch Advantages</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="esw_pd_0005.html">Functions</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="esw_pd_0011.html">Enterprise Switch Specifications</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="esw_pd_0003.html">How Enterprise Switches Work</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="esw_pd_0007.html">Permissions</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="esw_pd_0006.html">Notes and Constraints</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="esw_pd_0008.html">Region and AZ</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="esw_pd_0009.html">Working with Other Services</a></strong><br>
+</li>
+</ul>
+</div>
+

docs/esw/umn/esw_pd_0002.html

@@ -0,0 +1,16 @@
+<a name="esw_pd_0002"></a><a name="esw_pd_0002"></a>
+
+<h1 class="topictitle1">What Is an Enterprise Switch?</h1>
+<div id="body8662426"><p id="esw_pd_0002__p1434656191912">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.</p>
+<p id="esw_pd_0002__p1556310591179">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.</p>
+<p id="esw_pd_0002__p11091926164418">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.</p>
+<p id="esw_pd_0002__p205011457123010">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.</p>
+<div class="msonormal" id="esw_pd_0002__en-us_topic_0228866524_p55186561">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. <a href="#esw_pd_0002__fig7806391364">Figure 1</a> 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.<div class="fignone" id="esw_pd_0002__fig7806391364"><a name="esw_pd_0002__fig7806391364"></a><a name="fig7806391364"></a><span class="figcap"><b>Figure 1 </b>Layer 2 networking</span><br><span><img class="eddx" id="esw_pd_0002__image15801139183615" src="en-us_image_0000001355818125.png"></span></div>
+</div>
+</div>
+<div>
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a href="esw_pd_0001.html">Service Overview</a></div>
+</div>
+</div>
+

docs/esw/umn/esw_pd_0004.html

@@ -0,0 +1,50 @@
+<a name="esw_pd_0004"></a><a name="esw_pd_0004"></a>
+
+<h1 class="topictitle1">Enterprise Switch Advantages</h1>
+<div id="body0000001261009417"><p id="esw_pd_0004__p2317141894">Generally, you may use <em id="esw_pd_0004__i15655933124417"><strong id="esw_pd_0004__b0609132584413">VPN or Direct Connect</strong></em> 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 <a href="#esw_pd_0004__section11172133819576">Constraints on Layer 3 Networking Between an On-Premises Data Center and the Cloud (Without Enterprise Switches)</a>.</p>
+<p id="esw_pd_0004__p143314191"><em id="esw_pd_0004__i182721474443"><strong id="esw_pd_0004__b14264134634418">Enterprise switches</strong></em> 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 <a href="#esw_pd_0004__section102921112145814">Advantages of Layer 2 Networking Between an On-Premises Data Center and the Cloud (Using an Enterprise Switch)</a>.</p>
+<div class="section" id="esw_pd_0004__section11172133819576"><a name="esw_pd_0004__section11172133819576"></a><a name="section11172133819576"></a><h4 class="sectiontitle">Constraints on Layer 3 Networking Between an On-Premises Data Center and the Cloud (Without Enterprise Switches)</h4><p id="esw_pd_0004__p1474818136577"><a href="#esw_pd_0004__fig36161843104515">Figure 1</a> shows the Layer 3 networking between on-premises data centers and VPCs using VPN or Direct Connect. <a href="#esw_pd_0004__table127411948151510">Table 1</a> describes the pain points.</p>
+<div class="fignone" id="esw_pd_0004__fig36161843104515"><a name="esw_pd_0004__fig36161843104515"></a><a name="fig36161843104515"></a><span class="figcap"><b>Figure 1 </b>Layer 3 networking</span><br><span><img class="eddx" id="esw_pd_0004__image176161143194510" src="en-us_image_0000001355941949.png"></span></div>
+
+<div class="tablenoborder"><a name="esw_pd_0004__table127411948151510"></a><a name="table127411948151510"></a><table cellpadding="4" cellspacing="0" summary="" id="esw_pd_0004__table127411948151510" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Layer 3 networking description</caption><tbody><tr id="esw_pd_0004__row47411048101519"><th class="firstcol" valign="top" width="17.03%" id="mcps1.3.3.4.2.3.1.1"><p id="esw_pd_0004__p15741148191516">Description</p>
+</th>
+<td class="cellrowborder" valign="top" width="82.97%" headers="mcps1.3.3.4.2.3.1.1 "><p id="esw_pd_0004__p6118307432">VPN or Direct Connect allows the communication between on-premises data centers and VPCs at Layer 3 through routes.</p>
+</td>
+</tr>
+<tr id="esw_pd_0004__row974119485156"><th class="firstcol" valign="top" width="17.03%" id="mcps1.3.3.4.2.3.2.1"><p id="esw_pd_0004__p748924712588">Pain Points</p>
+</th>
+<td class="cellrowborder" valign="top" width="82.97%" headers="mcps1.3.3.4.2.3.2.1 "><ul id="esw_pd_0004__ul1687671216505"><li id="esw_pd_0004__li5242129179">The CIDR blocks of the on-premises data center and the VPC that are used for communication cannot overlap.<p id="esw_pd_0004__p137011101179"><a name="esw_pd_0004__li5242129179"></a><a name="li5242129179"></a>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&amp;M costs.</p>
+</li><li id="esw_pd_0004__li9591111611176">Workloads in a subnet have to be migrated together, and cloud and on-premises workloads in the same subnet cannot communicate with each other.<p id="esw_pd_0004__p1689124819170"><a name="esw_pd_0004__li9591111611176"></a><a name="li9591111611176"></a>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.</p>
+</li></ul>
+</td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+<div class="section" id="esw_pd_0004__section102921112145814"><a name="esw_pd_0004__section102921112145814"></a><a name="section102921112145814"></a><h4 class="sectiontitle">Advantages of Layer 2 Networking Between an On-Premises Data Center and the Cloud (Using an Enterprise Switch)</h4><p id="esw_pd_0004__p4649101914410">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 <a href="#esw_pd_0004__table1674110377231">Table 2</a>.</p>
+<div class="fignone" id="esw_pd_0004__fig1133018214519"><span class="figcap"><b>Figure 2 </b>Layer 2 networking diagram</span><br><span><img class="eddx" id="esw_pd_0004__image7945155812219" src="en-us_image_0000002424302708.png"></span></div>
+
+<div class="tablenoborder"><a name="esw_pd_0004__table1674110377231"></a><a name="table1674110377231"></a><table cellpadding="4" cellspacing="0" summary="" id="esw_pd_0004__table1674110377231" frame="border" border="1" rules="all"><caption><b>Table 2 </b>Layer 2 networking description</caption><tbody><tr id="esw_pd_0004__row37411037122310"><th class="firstcol" valign="top" width="17.03%" id="mcps1.3.4.4.2.3.1.1"><p id="esw_pd_0004__p474113722319">Description</p>
+</th>
+<td class="cellrowborder" valign="top" width="82.97%" headers="mcps1.3.4.4.2.3.1.1 "><p id="esw_pd_0004__p38811545104316">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.</p>
+</td>
+</tr>
+<tr id="esw_pd_0004__row16742103711237"><th class="firstcol" valign="top" width="17.03%" id="mcps1.3.4.4.2.3.2.1"><p id="esw_pd_0004__p147421373238">Advantages</p>
+</th>
+<td class="cellrowborder" valign="top" width="82.97%" headers="mcps1.3.4.4.2.3.2.1 "><ul id="esw_pd_0004__ul174223717231"><li id="esw_pd_0004__li1474253717239">The CIDR blocks of the on-premises data center and the VPC that are used for communication can overlap.<p id="esw_pd_0004__p1057491111245"><a name="esw_pd_0004__li1474253717239"></a><a name="li1474253717239"></a>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.</p>
+</li><li id="esw_pd_0004__li674293722315">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.<p id="esw_pd_0004__p3742237172314"><a name="esw_pd_0004__li674293722315"></a><a name="li674293722315"></a>Workloads can be seamlessly migrated to the cloud to prevent any loss caused by cloud migration.</p>
+</li></ul>
+</td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+</div>
+<div>
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a href="esw_pd_0001.html">Service Overview</a></div>
+</div>
+</div>
+

docs/esw/umn/esw_pd_0005.html

@@ -0,0 +1,21 @@
+<a name="esw_pd_0005"></a><a name="esw_pd_0005"></a>
+
+<h1 class="topictitle1">Functions</h1>
+<div id="body0000001261411407"><div class="section" id="esw_pd_0005__section18792101325014"><h4 class="sectiontitle">Enterprise Switches</h4><p id="esw_pd_0005__p1434656191912">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.</p>
+<div class="fignone" id="esw_pd_0005__fig145961291613"><span class="figcap"><b>Figure 1 </b>Layer 2 networking</span><br><span><img class="eddx" id="esw_pd_0005__esw_pd_0002_image15801139183615" src="en-us_image_0000001355818125.png"></span></div>
+<p id="esw_pd_0005__p380075317168">For details, see <a href="esw_ug_0001.html">Enterprise Switches</a>.</p>
+</div>
+<div class="section" id="esw_pd_0005__section7829126125311"><h4 class="sectiontitle">Layer 2 Connections</h4><p id="esw_pd_0005__p73765919132">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.</p>
+<p id="esw_pd_0005__p61611249141710">After an enterprise switch is created, you need to create a Layer 2 connection.</p>
+<p id="esw_pd_0005__p1640916119172">For details, see <a href="esw_ug_0007.html">Creating a Layer 2 Connection</a>.</p>
+</div>
+<div class="section" id="esw_pd_0005__section1548119188016"><h4 class="sectiontitle">Monitoring</h4><p id="esw_pd_0005__p873614478016">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.</p>
+<p id="esw_pd_0005__p873618473013">For details, see <a href="esw_ug_0013.html">Cloud Eye Monitoring</a>.</p>
+</div>
+</div>
+<div>
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a href="esw_pd_0001.html">Service Overview</a></div>
+</div>
+</div>
+

docs/esw/umn/esw_pd_0006.html

@@ -0,0 +1,69 @@
+<a name="esw_pd_0006"></a><a name="esw_pd_0006"></a>
+
+<h1 class="topictitle1">Notes and Constraints</h1>
+<div id="body0000001216769502"><div class="section" id="esw_pd_0006__section1872102219473"><h4 class="sectiontitle">Quota Limits</h4>
+<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="esw_pd_0006__table14258125544512" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Quota limits</caption><thead align="left"><tr id="esw_pd_0006__row20258115594513"><th align="left" class="cellrowborder" valign="top" width="42.26%" id="mcps1.3.1.2.2.4.1.1"><p id="esw_pd_0006__p17258105504510">Resource</p>
+</th>
+<th align="left" class="cellrowborder" valign="top" width="12.989999999999998%" id="mcps1.3.1.2.2.4.1.2"><p id="esw_pd_0006__p1625814553453">Default Quota</p>
+</th>
+<th align="left" class="cellrowborder" valign="top" width="44.75%" id="mcps1.3.1.2.2.4.1.3"><p id="esw_pd_0006__p16258175564514">Where to Increase Quota</p>
+</th>
+</tr>
+</thead>
+<tbody><tr id="esw_pd_0006__row6258105504515"><td class="cellrowborder" valign="top" width="42.26%" headers="mcps1.3.1.2.2.4.1.1 "><p id="esw_pd_0006__p52581755164511">Maximum number of enterprise switches per account</p>
+</td>
+<td class="cellrowborder" valign="top" width="12.989999999999998%" headers="mcps1.3.1.2.2.4.1.2 "><p id="esw_pd_0006__p152581655184512">5</p>
+</td>
+<td class="cellrowborder" valign="top" width="44.75%" headers="mcps1.3.1.2.2.4.1.3 "><p id="esw_pd_0006__p42415156232">Contact customer service to increase the quota.</p>
+</td>
+</tr>
+<tr id="esw_pd_0006__row1984092014441"><td class="cellrowborder" valign="top" width="42.26%" headers="mcps1.3.1.2.2.4.1.1 "><p id="esw_pd_0006__p384052044414">Maximum number of VPCs that can be associated with an enterprise switch</p>
+</td>
+<td class="cellrowborder" valign="top" width="12.989999999999998%" headers="mcps1.3.1.2.2.4.1.2 "><p id="esw_pd_0006__p284062017447">1</p>
+</td>
+<td class="cellrowborder" valign="top" width="44.75%" headers="mcps1.3.1.2.2.4.1.3 "><p id="esw_pd_0006__p102331023124517">Increasing the quota is not allowed.</p>
+</td>
+</tr>
+<tr id="esw_pd_0006__row1997595215487"><td class="cellrowborder" valign="top" width="42.26%" headers="mcps1.3.1.2.2.4.1.1 "><p id="esw_pd_0006__p7975165284819">Maximum number of Layer 2 connections supported by each subnet</p>
+</td>
+<td class="cellrowborder" valign="top" width="12.989999999999998%" headers="mcps1.3.1.2.2.4.1.2 "><p id="esw_pd_0006__p1497520526482">1</p>
+</td>
+<td class="cellrowborder" valign="top" width="44.75%" headers="mcps1.3.1.2.2.4.1.3 "><p id="esw_pd_0006__p4976165294819">Increasing the quota is not allowed.</p>
+</td>
+</tr>
+<tr id="esw_pd_0006__row2047552917235"><td class="cellrowborder" valign="top" width="42.26%" headers="mcps1.3.1.2.2.4.1.1 "><p id="esw_pd_0006__p1517033016274">Maximum number of Layer 2 connections supported by each <span class="parmname" id="esw_pd_0006__parmname36596385272"><b>small</b></span> enterprise switch</p>
+</td>
+<td class="cellrowborder" valign="top" width="12.989999999999998%" headers="mcps1.3.1.2.2.4.1.2 "><p id="esw_pd_0006__p124880517238">1</p>
+</td>
+<td class="cellrowborder" valign="top" width="44.75%" headers="mcps1.3.1.2.2.4.1.3 "><p id="esw_pd_0006__p9488105110236">Increasing the quota is not allowed.</p>
+</td>
+</tr>
+<tr id="esw_pd_0006__row15197820112312"><td class="cellrowborder" valign="top" width="42.26%" headers="mcps1.3.1.2.2.4.1.1 "><p id="esw_pd_0006__p2333114633419">Maximum number of Layer 2 connections supported by each <span class="parmname" id="esw_pd_0006__parmname13333204623411"><b>medium</b></span> enterprise switch</p>
+</td>
+<td class="cellrowborder" valign="top" width="12.989999999999998%" headers="mcps1.3.1.2.2.4.1.2 "><p id="esw_pd_0006__p86561129102315">3</p>
+</td>
+<td class="cellrowborder" valign="top" width="44.75%" headers="mcps1.3.1.2.2.4.1.3 "><p id="esw_pd_0006__p965615297231">Increasing the quota is not allowed.</p>
+</td>
+</tr>
+<tr id="esw_pd_0006__row1162716271456"><td class="cellrowborder" valign="top" width="42.26%" headers="mcps1.3.1.2.2.4.1.1 "><p id="esw_pd_0006__p194651324123518">Maximum number of Layer 2 connections supported by each <span class="parmname" id="esw_pd_0006__parmname184652024183516"><b>large</b></span> enterprise switch</p>
+</td>
+<td class="cellrowborder" valign="top" width="12.989999999999998%" headers="mcps1.3.1.2.2.4.1.2 "><p id="esw_pd_0006__p166271627134520">6</p>
+</td>
+<td class="cellrowborder" valign="top" width="44.75%" headers="mcps1.3.1.2.2.4.1.3 "><p id="esw_pd_0006__p16627527134516">Increasing the quota is not allowed.</p>
+</td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+<div class="section" id="esw_pd_0006__section998420261486"><h4 class="sectiontitle">Constraints</h4><ul id="esw_pd_0006__ul32711434736"><li id="esw_pd_0006__li7329133183011">Enterprise switches cannot forward untrusted unicast, broadcast, and multicast (except VRRP) packets from your data center to the cloud or IPv6 packets.</li><li id="esw_pd_0006__li1278425112610">On-premises servers cannot use advanced network functions on the cloud, such as VPC Peering, Route Table, ELB, and NAT Gateway.</li><li id="esw_pd_0006__li37920224236">If you want to use a Direct Connect connection together with an enterprise switch, submit a service ticket to check whether your connection can interconnect with an enterprise switch. If your connection does not support this, contact technical support.</li><li id="esw_pd_0006__li65391242182214">If you want to use a VPN connection together with an enterprise switch, submit a service ticket to check whether your connection supports VXLAN interconnection with an enterprise switch. If your connection does not support this, contact technical support.</li><li id="esw_pd_0006__li2252163612201">If cloud and on-premises networks communicate with each other at Layer 2, the cloud subnet gateway address must be the same as the on-premises subnet gateway address. Otherwise, the on-premises subnet gateway address may conflict with the IP address of a cloud server, causing communication exceptions.</li><li id="esw_pd_0006__li1983313272914">Each enterprise switch allows up to 10,000 IP addresses to communicate at Layer 2, including a maximum of 1,000 on-premises IP addresses.</li><li id="esw_pd_0006__li6201163710118">To use an enterprise switch to connect cloud and on-premises networks at Layer 2, you are responsible for constructing the VXLAN network in your data center, such as preparing VXLAN switches, connecting physical networks, and connecting to Direct Connect or VPN.</li><li id="esw_pd_0006__li8166813768">Generally, a server determines the destination MAC address of a reply packet through ARP. However, some hosts or hardware devices (such as F5 load balancers) are configured to use the source MAC address of a request packet as the destination MAC address of its reply packet. If an enterprise switch is used for cloud and on-premises communications at Layer 3, a network disconnection may occur.<p id="esw_pd_0006__p6407614161"><a name="esw_pd_0006__li8166813768"></a><a name="li8166813768"></a>For example, an enterprise switch allows cloud and on-premises networks to communicate on 192.168.3.0/24. If the cloud server using an IP address in 192.168.2.2/24 accesses the on-premises server using an IP address in 192.168.3.3/24, the request packet on the cloud is sent to the on-premises server through the VPC route and then the enterprise switch. The reply packet from the on-premises server is sent back to the cloud through the route and Direct Connect or VPN. If the on-premises server is configured to use the source MAC address of a request packet as the destination MAC address of its reply packet, the destination MAC address of the reply packet is not the MAC address of gateway 192.168.3.0/24, but the source MAC address of the request packet, that is, the MAC address of the enterprise switch. In this case, the destination MAC address of the reply packet is incorrect and the network is disconnected.</p>
+</li><li id="esw_pd_0006__li17259538175316">If an enterprise switch uses the VXLAN protocol, the VXLAN protocol has a header of 50 bytes and the packet length increases. Your on-premises network devices that allow VXLAN packets should support jumbo frames (Ethernet frames whose MTU is greater than 1500 bytes). Otherwise, such packets cannot be transmitted.</li><li id="esw_pd_0006__li1458015239240">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. The following lists some switches that support the VXLAN function.<ul id="esw_pd_0006__ul431016992513"><li id="esw_pd_0006__esw_qs_0007_li137091656102117">Huawei switches: Huawei CE58, CE68, CE78, and CE88 series switches, such as CE6870, CE6875, CE6881, CE6863, and CE12800 switches</li><li id="esw_pd_0006__esw_qs_0007_li11691428791">Switches of other vendors: Cisco Nexus 9300 and H3C S6520 series switches</li></ul>
+</li></ul>
+</div>
+</div>
+<div>
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a href="esw_pd_0001.html">Service Overview</a></div>
+</div>
+</div>
+

docs/esw/umn/esw_pd_0008.html

@@ -0,0 +1,22 @@
+<a name="esw_pd_0008"></a><a name="esw_pd_0008"></a>
+
+<h1 class="topictitle1">Region and AZ</h1>
+<div id="body8662426"><div class="section" id="esw_pd_0008__en-us_topic_0184026189_section388255972712"><h4 class="sectiontitle">Concept</h4><p id="esw_pd_0008__en-us_topic_0184026189_p212716216381">A region and availability zone (AZ) identify the location of a data center. You can create resources in a specific region and AZ.</p>
+<ul id="esw_pd_0008__en-us_topic_0184026189_ul86578533460"><li id="esw_pd_0008__en-us_topic_0184026189_li14657175334618">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.</li><li id="esw_pd_0008__en-us_topic_0184026189_li45875020473">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.</li></ul>
+<p id="esw_pd_0008__en-us_topic_0184026189_p1479174514614"><a href="#esw_pd_0008__en-us_topic_0184026189_fig8747114281212">Figure 1</a> shows the relationship between regions and AZs.</p>
+<div class="fignone" id="esw_pd_0008__en-us_topic_0184026189_fig8747114281212"><a name="esw_pd_0008__en-us_topic_0184026189_fig8747114281212"></a><a name="en-us_topic_0184026189_fig8747114281212"></a><span class="figcap"><b>Figure 1 </b>Regions and AZs</span><br><span><img class="vsd" id="esw_pd_0008__en-us_topic_0184026189_image12748194211128" src="en-us_image_0184026531.png"></span></div>
+</div>
+<div class="section" id="esw_pd_0008__en-us_topic_0184026189_section67281149192216"><h4 class="sectiontitle">Selecting a Region</h4><p id="esw_pd_0008__en-us_topic_0184026189_p68521454132212">You are advised to select a region close to you or your target users. This helps ensure low access latency.</p>
+</div>
+<div class="section" id="esw_pd_0008__en-us_topic_0184026189_section193971112578"><h4 class="sectiontitle">Selecting an AZ</h4><p id="esw_pd_0008__en-us_topic_0184026189_p859161416717">When deploying resources, consider your applications' requirements on disaster recovery (DR) and network latency.</p>
+<ul id="esw_pd_0008__en-us_topic_0184026189_ul157203571473"><li id="esw_pd_0008__en-us_topic_0184026189_li7720175710711">For high DR capability, deploy resources in different AZs within the same region.</li><li id="esw_pd_0008__en-us_topic_0184026189_li109763595719">For lower network latency, deploy resources in the same AZ.</li></ul>
+</div>
+<div class="section" id="esw_pd_0008__en-us_topic_0184026189_section1110135820407"><h4 class="sectiontitle">Regions and Endpoints</h4><p id="esw_pd_0008__en-us_topic_0184026189_p361784821111">Before you use an API to call resources, specify its region and endpoint. For more details, see <a href="https://docs.otc.t-systems.com/regions-and-endpoints/index.html" target="_blank" rel="noopener noreferrer">Regions and Endpoints</a>.</p>
+</div>
+</div>
+<div>
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a href="esw_pd_0001.html">Service Overview</a></div>
+</div>
+</div>
+

docs/esw/umn/esw_pd_0009.html

@@ -0,0 +1,42 @@
+<a name="esw_pd_0009"></a><a name="esw_pd_0009"></a>
+
+<h1 class="topictitle1">Working with Other Services</h1>
+<div id="body0000001216774310"><p id="esw_pd_0009__p11106151123614"><a href="#esw_pd_0009__fig1646103555616">Figure 1</a> illustrates how an enterprise switch works with other cloud services.</p>
+<div class="fignone" id="esw_pd_0009__fig1646103555616"><a name="esw_pd_0009__fig1646103555616"></a><a name="fig1646103555616"></a><span class="figcap"><b>Figure 1 </b>Interactions between an enterprise switch and other cloud services</span><br><span><img class="eddx" id="esw_pd_0009__image1546111357560" src="en-us_image_0000001302704672.png"></span></div>
+
+<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="esw_pd_0009__table19761133618416" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Interactions between an enterprise switch and other cloud services</caption><thead align="left"><tr id="esw_pd_0009__row1476193616413"><th align="left" class="cellrowborder" valign="top" width="40.83%" id="mcps1.3.3.2.3.1.1"><p id="esw_pd_0009__p376173612413">Service</p>
+</th>
+<th align="left" class="cellrowborder" valign="top" width="59.17%" id="mcps1.3.3.2.3.1.2"><p id="esw_pd_0009__p1776117366418">Interaction</p>
+</th>
+</tr>
+</thead>
+<tbody><tr id="esw_pd_0009__row137616361348"><td class="cellrowborder" valign="top" width="40.83%" headers="mcps1.3.3.2.3.1.1 "><p id="esw_pd_0009__p19761113614416">Virtual Private Cloud (VPC)</p>
+</td>
+<td class="cellrowborder" valign="top" width="59.17%" headers="mcps1.3.3.2.3.1.2 "><p id="esw_pd_0009__p15761123618412">VPCs can use enterprise switches to communicate with on-premises data centers at Layer 2.</p>
+</td>
+</tr>
+<tr id="esw_pd_0009__row876212361414"><td class="cellrowborder" valign="top" width="40.83%" headers="mcps1.3.3.2.3.1.1 "><p id="esw_pd_0009__p676216361146">Direct Connect</p>
+</td>
+<td class="cellrowborder" valign="top" width="59.17%" headers="mcps1.3.3.2.3.1.2 "><p id="esw_pd_0009__p352251811141">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.</p>
+</td>
+</tr>
+<tr id="esw_pd_0009__row145218184149"><td class="cellrowborder" valign="top" width="40.83%" headers="mcps1.3.3.2.3.1.1 "><p id="esw_pd_0009__p3522141812149">Virtual Private Network (VPN)</p>
+</td>
+<td class="cellrowborder" valign="top" width="59.17%" headers="mcps1.3.3.2.3.1.2 "><p id="esw_pd_0009__p1028972342620">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.</p>
+</td>
+</tr>
+<tr id="esw_pd_0009__row157628361248"><td class="cellrowborder" valign="top" width="40.83%" headers="mcps1.3.3.2.3.1.1 "><p id="esw_pd_0009__p10762203610411">Identity and Access Management (IAM)</p>
+</td>
+<td class="cellrowborder" valign="top" width="59.17%" headers="mcps1.3.3.2.3.1.2 "><p id="esw_pd_0009__p889720562242">With IAM, you can assign different permissions to different users to control their access to enterprise switch resources.</p>
+</td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+<div>
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a href="esw_pd_0001.html">Service Overview</a></div>
+</div>
+</div>
+

docs/esw/umn/esw_pd_0011.html

@@ -0,0 +1,52 @@
+<a name="esw_pd_0011"></a><a name="esw_pd_0011"></a>
+
+<h1 class="topictitle1">Enterprise Switch Specifications</h1>
+<div id="body0000002541918383"><p id="esw_pd_0011__p165571291285">Three enterprise switch specifications are supported: <span class="parmname" id="esw_pd_0011__parmname19914720322"><b>basic</b></span>, <span class="parmname" id="esw_pd_0011__parmname1432523784114"><b>enhanced</b></span>, and <span class="parmname" id="esw_pd_0011__parmname983811510424"><b>standard</b></span>. For details, see <a href="#esw_pd_0011__table522920211611">Table 1</a>.</p>
+
+<div class="tablenoborder"><a name="esw_pd_0011__table522920211611"></a><a name="table522920211611"></a><table cellpadding="4" cellspacing="0" summary="" id="esw_pd_0011__table522920211611" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Specifications</caption><thead align="left"><tr id="esw_pd_0011__row72291620617"><th align="left" class="cellrowborder" valign="top" width="22.8040127232689%" id="mcps1.3.2.2.5.1.1"><p id="esw_pd_0011__p11180155510241">Specifications</p>
+</th>
+<th align="left" class="cellrowborder" valign="top" width="24.993883043797407%" id="mcps1.3.2.2.5.1.2"><p id="esw_pd_0011__p3818173011196">Maximum Bandwidth</p>
+</th>
+<th align="left" class="cellrowborder" valign="top" width="26.5231220944458%" id="mcps1.3.2.2.5.1.3"><p id="esw_pd_0011__p3817133051919">Maximum PPS</p>
+</th>
+<th align="left" class="cellrowborder" valign="top" width="25.67898213848789%" id="mcps1.3.2.2.5.1.4"><p id="esw_pd_0011__p118171230141915">Connected Subnets</p>
+</th>
+</tr>
+</thead>
+<tbody><tr id="esw_pd_0011__row9229921668"><td class="cellrowborder" valign="top" width="22.8040127232689%" headers="mcps1.3.2.2.5.1.1 "><p id="esw_pd_0011__p1626394319259">Basic</p>
+</td>
+<td class="cellrowborder" valign="top" width="24.993883043797407%" headers="mcps1.3.2.2.5.1.2 "><p id="esw_pd_0011__p127951226144515">3 Gbit/s</p>
+</td>
+<td class="cellrowborder" valign="top" width="26.5231220944458%" headers="mcps1.3.2.2.5.1.3 "><p id="esw_pd_0011__p55802201193">500,000</p>
+</td>
+<td class="cellrowborder" valign="top" width="25.67898213848789%" headers="mcps1.3.2.2.5.1.4 "><p id="esw_pd_0011__p95151140114412">1</p>
+</td>
+</tr>
+<tr id="esw_pd_0011__row8229172760"><td class="cellrowborder" valign="top" width="22.8040127232689%" headers="mcps1.3.2.2.5.1.1 "><p id="esw_pd_0011__p91804553243">Standard</p>
+</td>
+<td class="cellrowborder" valign="top" width="24.993883043797407%" headers="mcps1.3.2.2.5.1.2 "><p id="esw_pd_0011__p379692615453">5 Gbit/s</p>
+</td>
+<td class="cellrowborder" valign="top" width="26.5231220944458%" headers="mcps1.3.2.2.5.1.3 "><p id="esw_pd_0011__p145086539443">1,000,000</p>
+</td>
+<td class="cellrowborder" valign="top" width="25.67898213848789%" headers="mcps1.3.2.2.5.1.4 "><p id="esw_pd_0011__p135151940134414">3</p>
+</td>
+</tr>
+<tr id="esw_pd_0011__row12229112964"><td class="cellrowborder" valign="top" width="22.8040127232689%" headers="mcps1.3.2.2.5.1.1 "><p id="esw_pd_0011__p151801055162411">Enhanced</p>
+</td>
+<td class="cellrowborder" valign="top" width="24.993883043797407%" headers="mcps1.3.2.2.5.1.2 "><p id="esw_pd_0011__p354917151455">10 Gbit/s</p>
+</td>
+<td class="cellrowborder" valign="top" width="26.5231220944458%" headers="mcps1.3.2.2.5.1.3 "><p id="esw_pd_0011__p924565217445">2,000,000</p>
+</td>
+<td class="cellrowborder" valign="top" width="25.67898213848789%" headers="mcps1.3.2.2.5.1.4 "><p id="esw_pd_0011__p35151640134411">6</p>
+</td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+<div>
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a href="esw_pd_0001.html">Service Overview</a></div>
+</div>
+</div>
+

docs/esw/umn/esw_qs_0001.html

@@ -0,0 +1,21 @@
+<a name="esw_qs_0001"></a><a name="esw_qs_0001"></a>
+
+<h1 class="topictitle1">Getting Started</h1>
+<div id="body0000001216884436"></div>
+<div>
+<ul class="ullinks">
+<li class="ulchildlink"><strong><a href="esw_qs_0003.html">Quick Start</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="esw_qs_0004.html">Step 1: Use Direct Connect or VPN to Communicate at Layer 3</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="esw_qs_0005.html">Step 2: Create an Enterprise Switch</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="esw_qs_0006.html">Step 3: Create a Layer 2 Connection</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="esw_qs_0007.html">Step 4: Configure a Tunnel Gateway in Your Data Center</a></strong><br>
+</li>
+<li class="ulchildlink"><strong><a href="esw_qs_0008.html">Step 5: Verify Network Connectivity</a></strong><br>
+</li>
+</ul>
+</div>
+

docs/esw/umn/esw_qs_0003.html

@@ -0,0 +1,52 @@
+<a name="esw_qs_0003"></a><a name="esw_qs_0003"></a>
+
+<h1 class="topictitle1">Quick Start</h1>
+<div id="body0000001216449550"><p id="esw_qs_0003__p1745541117459">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. <a href="#esw_qs_0003__fig11967172194610">Figure 1</a> shows the configuration process of enterprise switches.</p>
+<div class="fignone" id="esw_qs_0003__fig11967172194610"><a name="esw_qs_0003__fig11967172194610"></a><a name="fig11967172194610"></a><span class="figcap"><b>Figure 1 </b>Enterprise switch configuration flowchart</span><br><span><img class="eddx" id="esw_qs_0003__image7968202184617" src="en-us_image_0000001355402245.png"></span></div>
+
+<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="esw_qs_0003__table1766082613110" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Process description</caption><thead align="left"><tr id="esw_qs_0003__row176607263119"><th align="left" class="cellrowborder" valign="top" width="9%" id="mcps1.3.3.2.4.1.1"><p id="esw_qs_0003__p466014261116">No.</p>
+</th>
+<th align="left" class="cellrowborder" valign="top" width="28.999999999999996%" id="mcps1.3.3.2.4.1.2"><p id="esw_qs_0003__p1566092618117">Step</p>
+</th>
+<th align="left" class="cellrowborder" valign="top" width="62%" id="mcps1.3.3.2.4.1.3"><p id="esw_qs_0003__p12660162611118">Description</p>
+</th>
+</tr>
+</thead>
+<tbody><tr id="esw_qs_0003__row186601926181116"><td class="cellrowborder" valign="top" width="9%" headers="mcps1.3.3.2.4.1.1 "><p id="esw_qs_0003__p6660126111115">1</p>
+</td>
+<td class="cellrowborder" valign="top" width="28.999999999999996%" headers="mcps1.3.3.2.4.1.2 "><p id="esw_qs_0003__p1281061232716"><a href="esw_qs_0004.html">Step 1: Use Direct Connect or VPN to Communicate at Layer 3</a></p>
+</td>
+<td class="cellrowborder" valign="top" width="62%" headers="mcps1.3.3.2.4.1.3 "><p id="esw_qs_0003__p0660162681111">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.</p>
+</td>
+</tr>
+<tr id="esw_qs_0003__row96601626191113"><td class="cellrowborder" valign="top" width="9%" headers="mcps1.3.3.2.4.1.1 "><p id="esw_qs_0003__p2660152661116">2</p>
+</td>
+<td class="cellrowborder" valign="top" width="28.999999999999996%" headers="mcps1.3.3.2.4.1.2 "><p id="esw_qs_0003__p188582236515"><a href="esw_qs_0005.html">Step 2: Create an Enterprise Switch</a></p>
+</td>
+<td class="cellrowborder" valign="top" width="62%" headers="mcps1.3.3.2.4.1.3 "><p class="msonormal" id="esw_qs_0003__p1066017260112">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.</p>
+</td>
+</tr>
+<tr id="esw_qs_0003__row106601826131116"><td class="cellrowborder" valign="top" width="9%" headers="mcps1.3.3.2.4.1.1 "><p id="esw_qs_0003__p14660112620112">3</p>
+</td>
+<td class="cellrowborder" valign="top" width="28.999999999999996%" headers="mcps1.3.3.2.4.1.2 "><p id="esw_qs_0003__p48096124279"><a href="esw_qs_0006.html">Step 3: Create a Layer 2 Connection</a></p>
+</td>
+<td class="cellrowborder" valign="top" width="62%" headers="mcps1.3.3.2.4.1.3 "><p id="esw_qs_0003__p169884325122">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>
+</td>
+</tr>
+<tr id="esw_qs_0003__row13660102681116"><td class="cellrowborder" valign="top" width="9%" headers="mcps1.3.3.2.4.1.1 "><p id="esw_qs_0003__p2066042681114">4</p>
+</td>
+<td class="cellrowborder" valign="top" width="28.999999999999996%" headers="mcps1.3.3.2.4.1.2 "><p id="esw_qs_0003__p2080841272718"><a href="esw_qs_0007.html">Step 4: Configure a Tunnel Gateway in Your Data Center</a></p>
+</td>
+<td class="cellrowborder" valign="top" width="62%" headers="mcps1.3.3.2.4.1.3 "><p id="esw_qs_0003__p435323243114">This section describes how to configure the tunnel gateway on a VXLAN tunnel switch of an on-premises data center.</p>
+</td>
+</tr>
+</tbody>
+</table>
+</div>
+</div>
+<div>
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a href="esw_qs_0001.html">Getting Started</a></div>
+</div>
+</div>
+

docs/esw/umn/esw_qs_0004.html

@@ -0,0 +1,20 @@
+<a name="esw_qs_0004"></a><a name="esw_qs_0004"></a>
+
+<h1 class="topictitle1">Step 1: Use Direct Connect or VPN to Communicate at Layer 3</h1>
+<div id="body0000001217407018"><div class="section" id="esw_qs_0004__section5495544163011"><h4 class="sectiontitle">Scenarios</h4><p id="esw_qs_0004__p442231065716">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.</p>
+</div>
+<div class="section" id="esw_qs_0004__section548252701111"><h4 class="sectiontitle">Prerequisites</h4><p id="esw_qs_0004__p338512339115">Before using enterprise switches, plan resources on and off the cloud by referring to <a href="esw_pd_0003.html">How Enterprise Switches Work</a>.</p>
+</div>
+<div class="section" id="esw_qs_0004__section4276153533115"><h4 class="sectiontitle">Procedure</h4><ol id="esw_qs_0004__ol1319817715323"><li id="esw_qs_0004__li619887133212">Create a Direct Connect or VPN connection.<p id="esw_qs_0004__p689415219488"><a name="esw_qs_0004__li619887133212"></a><a name="li619887133212"></a>Select the VPC (vpc-01) where the enterprise switch is created in <a href="esw_qs_0005.html">Step 2: Create an Enterprise Switch</a>.</p>
+<p id="esw_qs_0004__p42392404326"></p>
+<p id="esw_qs_0004__p10614149103110"></p>
+<p id="esw_qs_0004__p1721425313320">For details, see <a href="https://docs.otc.t-systems.com/direct-connect/umn/getting_started/enabling_direct_connect/index.html#dc-02-0200" target="_blank" rel="noopener noreferrer">Configuring a Direct Connect Connection</a> or <a href="https://docs.otc.t-systems.com/virtual-private-network/umn/getting_started/index.html" target="_blank" rel="noopener noreferrer">Configuring a VPN Connection</a>.</p>
+</li><li id="esw_qs_0004__li1221718101113">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.</li></ol>
+</div>
+</div>
+<div>
+<div class="familylinks">
+<div class="parentlink"><strong>Parent topic:</strong> <a href="esw_qs_0001.html">Getting Started</a></div>
+</div>
+</div>
+