forked from docs/doc-exports
ER UMN 20240206 version
Reviewed-by: Sarda, Priya <prsarda@noreply.gitea.eco.tsi-dev.otc-service.com> Co-authored-by: Qin Ying, Fan <fanqinying@huawei.com> Co-committed-by: Qin Ying, Fan <fanqinying@huawei.com>
This commit is contained in:
parent
8bbea6cef6
commit
c62a547174
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
@ -8,7 +8,31 @@
|
||||
</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody><tr id="UgChangeHistory__row77791443531"><td class="cellrowborder" valign="top" width="33.58%" headers="mcps1.3.1.1.3.1.1 "><p id="UgChangeHistory__p109701447635">2023-11-21</p>
|
||||
<tbody><tr id="UgChangeHistory__row2085920413119"><td class="cellrowborder" valign="top" width="33.58%" headers="mcps1.3.1.1.3.1.1 "><p id="UgChangeHistory__p98604418313">2024-02-22</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="66.42%" headers="mcps1.3.1.1.3.1.2 "><p id="UgChangeHistory__p46601253103114">Modified the following content:</p>
|
||||
<p id="UgChangeHistory__p1845445313114">Added the default ASN of enterprise routers in <a href="er_01_0064.html">Step 2: Create an Enterprise Router</a> and <a href="er_01_0069.html">Creating an Enterprise Router</a>.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="UgChangeHistory__row3572172018018"><td class="cellrowborder" valign="top" width="33.58%" headers="mcps1.3.1.1.3.1.1 "><p id="UgChangeHistory__p957210201309">2024-02-18</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="66.42%" headers="mcps1.3.1.1.3.1.2 "><p id="UgChangeHistory__p7709113212012">Modified the following content:</p>
|
||||
<ul id="UgChangeHistory__ul117090321703"><li id="UgChangeHistory__li470963218011">Modified the description of the <strong id="UgChangeHistory__b17711388299">Destination Type</strong> parameter in <a href="er_01_0067.html">Step 5: (Optional) Add Routes to VPC Route Tables</a>.</li><li id="UgChangeHistory__li11674617161018">Modified the table style and canceled cell combination of <a href="er_01_0011.html#er_01_0011__table133841251278">Table 2</a> in <a href="er_01_0011.html">How Enterprise Routers Work</a>.</li><li id="UgChangeHistory__li1120145481416">Modified the table style and canceled cell combination of <a href="er_01_0095.html#er_01_0095__table16962125143812">Table 3</a> in <a href="er_01_0095.html">Sharing Overview</a>.</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="UgChangeHistory__row9763134713136"><td class="cellrowborder" valign="top" width="33.58%" headers="mcps1.3.1.1.3.1.1 "><p id="UgChangeHistory__p1379785012130">2024-02-08</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="66.42%" headers="mcps1.3.1.1.3.1.2 "><p id="UgChangeHistory__p13797185019139">Modified the following content:</p>
|
||||
<ul id="UgChangeHistory__ul1797105071310"><li id="UgChangeHistory__li879745012135">Added the <strong id="UgChangeHistory__b176641452966">Destination Type</strong> parameter in <a href="er_01_0067.html">Step 5: (Optional) Add Routes to VPC Route Tables</a>.</li><li id="UgChangeHistory__li9772105914275">Modified the example ASN values of enterprise routers in <a href="er_01_0063.html">Step 1: Plan Networks and Resources</a>, <a href="er_01_0064.html">Step 2: Create an Enterprise Router</a>, and <a href="er_01_0123.html">How Do I Enable Two Attachments of an Enterprise Router to Learn Routes from Each Other?</a></li><li id="UgChangeHistory__li13838191810315">Changed the title of <a href="er_01_0062.html">Overview</a>.</li><li id="UgChangeHistory__li887313110435">Added constraints on the 100.64.x.x network segment in <a href="er_01_0006.html">Notes and Constraints</a>.</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="UgChangeHistory__row340881012461"><td class="cellrowborder" valign="top" width="33.58%" headers="mcps1.3.1.1.3.1.1 "><p id="UgChangeHistory__p540819107468">2024-02-05</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="66.42%" headers="mcps1.3.1.1.3.1.2 "><p id="UgChangeHistory__p10444827204610">Modified the following content:</p>
|
||||
<ul id="UgChangeHistory__ul4445127104613"><li id="UgChangeHistory__li12445162711467">Modified description about the <strong id="UgChangeHistory__b194502085313">ASN</strong> parameter in <a href="er_01_0069.html">Creating an Enterprise Router</a>.</li><li id="UgChangeHistory__li174451527144612">Added a note to <strong id="UgChangeHistory__b986983155614">Auto Add Routes</strong> in <a href="er_01_0070.html">Creating a VPC Attachment</a>.</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="UgChangeHistory__row77791443531"><td class="cellrowborder" valign="top" width="33.58%" headers="mcps1.3.1.1.3.1.1 "><p id="UgChangeHistory__p109701447635">2023-11-21</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="66.42%" headers="mcps1.3.1.1.3.1.2 "><p id="UgChangeHistory__p59701647532">Modified the following content:</p>
|
||||
<p id="UgChangeHistory__p1397012471637">Added a screenshot in <a href="er_01_0057.html">Viewing Quotas</a>.</p>
|
||||
|
@ -7,7 +7,7 @@
|
||||
|
||||
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="er_01_0004__table1550865410281" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Using enterprise routers in scenario 1</caption><tbody><tr id="er_01_0004__row1350835414280"><th class="firstcol" valign="top" width="15.2%" id="mcps1.3.2.3.2.3.1.1"><p id="er_01_0004__p750885417284">Customer Requirements</p>
|
||||
</th>
|
||||
<td class="cellrowborder" valign="top" width="84.8%" headers="mcps1.3.2.3.2.3.1.1 "><p id="er_01_0004__p1277120121287">Multiple service networks communicate or do not communicate with each other on the cloud but communicate with the on-premises data center. For example, an enterprise requires three VPCs for running their workloads on the public cloud, and the three VPCs (services A, B, and C) need to access public services in VPC 4 and the on-premises data center.</p>
|
||||
<td class="cellrowborder" valign="top" width="84.8%" headers="mcps1.3.2.3.2.3.1.1 "><p id="er_01_0004__p1277120121287">Multiple service networks communicate or do not communicate with each other on the cloud but communicate with the on-premises data center. Suppose you require three VPCs for running the workloads on the public cloud, and the three VPCs (services A, B, and C) need to access public services in VPC 4 and your on-premises data center.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="er_01_0004__row11508254152816"><th class="firstcol" valign="top" width="15.2%" id="mcps1.3.2.3.2.3.2.1"><p id="er_01_0004__p450815543282">Pain Points</p>
|
||||
|
@ -22,8 +22,8 @@
|
||||
</tr>
|
||||
<tr id="er_01_0005__row1266416023014"><td class="cellrowborder" valign="top" width="16%" headers="mcps1.3.2.2.4.1.1 "><p id="er_01_0005__p19664405306">Attachments</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="62%" headers="mcps1.3.2.2.4.1.2 "><p id="er_01_0005__p11851275416">You can add attachments to attach network instances to the enterprise router.</p>
|
||||
<div class="p" id="er_01_0005__p1345311719386">Different network instances are attached through different consoles.<ul id="er_01_0005__ul34263440379"><li id="er_01_0005__li75401451154719">VPCs are attached through the Enterprise Router console.</li><li id="er_01_0005__li1081572116435">Virtual gateways are attached through the Direct Connect console.</li></ul>
|
||||
<td class="cellrowborder" valign="top" width="62%" headers="mcps1.3.2.2.4.1.2 "><p id="er_01_0005__p11851275416">You can attach network instances to the enterprise router.</p>
|
||||
<div class="p" id="er_01_0005__p1345311719386">Network instances are attached to the enterprise router in different ways.<ul id="er_01_0005__ul34263440379"><li id="er_01_0005__li75401451154719">VPCs are attached to the enterprise router on the Enterprise Router console.</li><li id="er_01_0005__li1081572116435">Virtual gateways are attached through the Direct Connect console.</li></ul>
|
||||
</div>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="22%" headers="mcps1.3.2.2.4.1.3 "><p id="er_01_0005__p118482027121614"><a href="er_01_0019.html">Attachment Overview</a></p>
|
||||
|
@ -2,11 +2,11 @@
|
||||
|
||||
<h1 class="topictitle1">How Enterprise Routers Work</h1>
|
||||
<div id="body0000001181135395"><p id="er_01_0011__p3463123143319">You can attach your network connections to an enterprise router to quickly construct diversified networks and meet various service requirements. <a href="#er_01_0011__fig9264191913235">Figure 1</a> shows the process of using an enterprise router, including creating an enterprise router, adding attachments to the enterprise router, and configure routes.</p>
|
||||
<div class="p" id="er_01_0011__p38772262216">Currently, enterprise routers support the following attachments:<ul id="er_01_0011__ul15214385212"><li id="er_01_0011__li20521163815216"><strong id="er_01_0011__b12731114154810">VPC attachment</strong>: Attach VPCs from the same region as that of an enterprise router to the router.</li><li id="er_01_0011__li1920784732113"><strong id="er_01_0011__b8891777499">Virtual gateway attachment</strong>: Attach Direct Connect virtual gateways from the same region as that of an enterprise router to the router.</li></ul>
|
||||
<div class="p" id="er_01_0011__p38772262216">Enterprise routers support the following attachments:<ul id="er_01_0011__ul15214385212"><li id="er_01_0011__li20521163815216"><strong id="er_01_0011__b12731114154810">VPC attachment</strong>: Attach a VPC from the same region as that of an enterprise router.</li><li id="er_01_0011__li1920784732113"><strong id="er_01_0011__b8891777499">Virtual gateway attachment</strong>: Attach a Direct Connect virtual gateway from the same region as that of an enterprise router.</li></ul>
|
||||
</div>
|
||||
<div class="fignone" id="er_01_0011__fig9264191913235"><a name="er_01_0011__fig9264191913235"></a><a name="fig9264191913235"></a><span class="figcap"><b>Figure 1 </b>Processing of using an enterprise router</span><br><span><img class="eddx" id="er_01_0011__image22641119192316" src="en-us_image_0000001530148853.png"></span></div>
|
||||
<p id="er_01_0011__p1540261920214">The following describes how an enterprise router works.</p>
|
||||
<div class="fignone" id="er_01_0011__fig1520692752815"><span class="figcap"><b>Figure 2 </b>How an enterprise router works</span><br><span><img class="eddx" id="er_01_0011__image72061427132813" src="en-us_image_0000001529830673.png"></span></div>
|
||||
<p id="er_01_0011__p1540261920214"><a href="#er_01_0011__fig1520692752815">Figure 2</a> shows how an enterprise router works. <a href="#er_01_0011__table133841251278">Table 2</a> describes the traffic flows in detail if an enterprise router is used for networking.</p>
|
||||
<div class="fignone" id="er_01_0011__fig1520692752815"><a name="er_01_0011__fig1520692752815"></a><a name="fig1520692752815"></a><span class="figcap"><b>Figure 2 </b>How an enterprise router works</span><br><span><img class="eddx" id="er_01_0011__image72061427132813" src="en-us_image_0000001529830673.png"></span></div>
|
||||
|
||||
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="er_01_0011__table198114341557" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Network traffic flows</caption><thead align="left"><tr id="er_01_0011__row109249015716"><th align="left" class="cellrowborder" valign="top" width="7.5200000000000005%" id="mcps1.3.6.2.4.1.1"><p id="er_01_0011__p6699959192917">No.</p>
|
||||
</th>
|
||||
@ -39,35 +39,30 @@
|
||||
</table>
|
||||
</div>
|
||||
|
||||
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="er_01_0011__table3502174455013" frame="border" border="1" rules="all"><caption><b>Table 2 </b>Working principles of an enterprise router</caption><thead align="left"><tr id="er_01_0011__row350374412507"><th align="left" class="cellrowborder" valign="top" width="7.440744074407441%" id="mcps1.3.7.2.4.1.1"><p id="er_01_0011__p450317444508">No.</p>
|
||||
<div class="tablenoborder"><a name="er_01_0011__table133841251278"></a><a name="table133841251278"></a><table cellpadding="4" cellspacing="0" summary="" id="er_01_0011__table133841251278" frame="border" border="1" rules="all"><caption><b>Table 2 </b>Working principles of an enterprise router</caption><thead align="left"><tr id="er_01_0011__row03845251713"><th align="left" class="cellrowborder" valign="top" width="7.440744074407441%" id="mcps1.3.7.2.4.1.1"><p id="er_01_0011__p143845251717">No.</p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="24.002400240024002%" id="mcps1.3.7.2.4.1.2"><p id="er_01_0011__p175031844115017">Action</p>
|
||||
<th align="left" class="cellrowborder" valign="top" width="24.002400240024002%" id="mcps1.3.7.2.4.1.2"><p id="er_01_0011__p438417259714">Action</p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="68.55685568556855%" id="mcps1.3.7.2.4.1.3"><p id="er_01_0011__p175031344195011">Description</p>
|
||||
<th align="left" class="cellrowborder" valign="top" width="68.55685568556855%" id="mcps1.3.7.2.4.1.3"><p id="er_01_0011__p33844257710">Description</p>
|
||||
</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody><tr id="er_01_0011__row15031440505"><td class="cellrowborder" valign="top" width="7.440744074407441%" headers="mcps1.3.7.2.4.1.1 "><p id="er_01_0011__p5503144485010">1</p>
|
||||
<tbody><tr id="er_01_0011__row93841925274"><td class="cellrowborder" valign="top" width="7.440744074407441%" headers="mcps1.3.7.2.4.1.1 "><p id="er_01_0011__p33841225979">1</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="24.002400240024002%" headers="mcps1.3.7.2.4.1.2 "><p id="er_01_0011__p650320444506">Add <a href="#er_01_0011__section692619383113">attachments</a> to the enterprise router.</p>
|
||||
<td class="cellrowborder" valign="top" width="24.002400240024002%" headers="mcps1.3.7.2.4.1.2 "><p id="er_01_0011__p83849256715">Add <a href="#er_01_0011__section692619383113">attachments</a> to the enterprise router.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="68.55685568556855%" headers="mcps1.3.7.2.4.1.3 "><div class="p" id="er_01_0011__p19114734102712">Attach network instances to enterprise router 1 in region A.<ul id="er_01_0011__ul43111819281"><li id="er_01_0011__li4150103210431">Network instances from the same region<ul id="er_01_0011__ul92483364445"><li id="er_01_0011__li224916363445"><strong id="er_01_0011__b1159172255613">VPC attachments</strong>: VPC 1, VPC 2, and VPC 3</li><li id="er_01_0011__li124943694411"><strong id="er_01_0011__b45111376564">Virtual gateway attachment</strong>: Virtual gateway</li></ul>
|
||||
</li></ul>
|
||||
<td class="cellrowborder" valign="top" width="68.55685568556855%" headers="mcps1.3.7.2.4.1.3 "><p id="er_01_0011__p238482512718">Attach network instances to enterprise router 1 in region A.</p>
|
||||
<div class="p" id="er_01_0011__p1417281718913">Network instances from the same region<ul id="er_01_0011__ul33841625474"><li id="er_01_0011__li2038414251371"><strong id="er_01_0011__b1920053991">VPC attachments</strong>: VPC 1, VPC 2, and VPC 3</li><li id="er_01_0011__li1138416256719"><strong id="er_01_0011__b1584056596">Virtual gateway attachment</strong>: Virtual gateway</li></ul>
|
||||
</div>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="er_01_0011__row1050374415019"><td class="cellrowborder" valign="top" width="7.440744074407441%" headers="mcps1.3.7.2.4.1.1 "><p id="er_01_0011__p65031544195010">2</p>
|
||||
<tr id="er_01_0011__row4384152518711"><td class="cellrowborder" valign="top" width="7.440744074407441%" headers="mcps1.3.7.2.4.1.1 "><p id="er_01_0011__p43841225277">2</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="24.002400240024002%" headers="mcps1.3.7.2.4.1.2 "><p id="er_01_0011__p2029718271558">Associate the <a href="#er_01_0011__section131904714219">attachments</a> with the <a href="#er_01_0011__section14844328152418">route tables</a> of the enterprise router.</p>
|
||||
<p id="er_01_0011__p10503244155013">Each attachment can only be associated with one route table.</p>
|
||||
<td class="cellrowborder" valign="top" width="24.002400240024002%" headers="mcps1.3.7.2.4.1.2 "><ol id="er_01_0011__ol179627571185"><li id="er_01_0011__li7962257682">Associate the <a href="#er_01_0011__section131904714219">attachments</a> with the <a href="#er_01_0011__section14844328152418">route tables</a> of the enterprise router.<p id="er_01_0011__p1138432513717">Each attachment can only be associated with one route table.</p>
|
||||
</li><li id="er_01_0011__li64051227917">Create <a href="#er_01_0011__section134131541823">propagation</a> for the attachments to propagate the <a href="#er_01_0011__section11725172512435">routes</a> to the enterprise router's <a href="#er_01_0011__section14844328152418">route tables</a>.<p id="er_01_0011__p63851251371">You can create multiple propagation records for the same attachment.</p>
|
||||
</li></ol>
|
||||
</td>
|
||||
<td class="cellrowborder" rowspan="2" valign="top" width="68.55685568556855%" headers="mcps1.3.7.2.4.1.3 "><ul id="er_01_0011__ul44594391974"><li id="er_01_0011__li114591039574">Associate VPC 1 with the default route table of enterprise router 1 and create a propagation to propagate the routes learned from VPC 1 attachment to the default route table and custom route table of enterprise router 1.</li><li id="er_01_0011__li67831746183610">Associate VPC 2 with the custom route table of enterprise router 1 and create a propagation to propagate the routes learned from VPC 2 to the custom route table.</li><li id="er_01_0011__li63751815111520">Associate VPC 3 with the custom route table of enterprise router 1, and add static routes for VPC 3 to this custom route table.</li><li id="er_01_0011__li111772218386">Associate the Direct Connect virtual gateway with the default route table of enterprise router 1 and create a propagation to propagate the routes learned from the virtual gateway attachment to the default route table.</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="er_01_0011__row11503114465015"><td class="cellrowborder" valign="top" headers="mcps1.3.7.2.4.1.1 "><p id="er_01_0011__p9503114435011">3</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" headers="mcps1.3.7.2.4.1.2 "><p id="er_01_0011__p14150231559">Create <a href="#er_01_0011__section134131541823">propagation</a> for the attachments to propagate the <a href="#er_01_0011__section11725172512435">routes</a> to the enterprise router's <a href="#er_01_0011__section14844328152418">route tables</a>.</p>
|
||||
<p id="er_01_0011__p17503144145017">You can create multiple propagation records for the same attachment.</p>
|
||||
<td class="cellrowborder" valign="top" width="68.55685568556855%" headers="mcps1.3.7.2.4.1.3 "><ul id="er_01_0011__ul73848251775"><li id="er_01_0011__li33842251974">Associate VPC 1 with the default route table of enterprise router 1 and create a propagation to propagate the routes learned from VPC 1 attachment to the default route table and custom route table of enterprise router 1.</li><li id="er_01_0011__li17384122516711">Associate VPC 2 with the custom route table of enterprise router 1 and create a propagation to propagate the routes learned from VPC 2 to the custom route table.</li><li id="er_01_0011__li238472513710">Associate VPC 3 with the custom route table of enterprise router 1, and add static routes for VPC 3 to this custom route table.</li><li id="er_01_0011__li438514253712">Associate the Direct Connect virtual gateway with the default route table of enterprise router 1 and create a propagation to propagate the routes learned from the virtual gateway attachment to the default route table.</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
|
@ -3,7 +3,7 @@
|
||||
<h1 class="topictitle1">Viewing an Enterprise Router</h1>
|
||||
<div id="body0000001135381498"><div class="section" id="er_01_0016__section1631373542615"><h4 class="sectiontitle">Scenarios</h4><p id="er_01_0016__p81011826145410">This section describes how to view basic information about an enterprise router, including the AZs, default route table association and propagation, and creation time.</p>
|
||||
<p id="er_01_0016__p78035193299">You can also view other information about the enterprise router, including:</p>
|
||||
<ul id="er_01_0016__ul19520134293116"><li id="er_01_0016__li04013210324">Attachments, such as their name, type, and attached resources. For details, see <a href="er_01_0021.html">Viewing Details About an Attachment</a>.</li><li id="er_01_0016__li896495913334">Route tables, such as the default route table and custom route tables. For details, see <a href="er_01_0027.html">Viewing Route Tables</a>.</li><li id="er_01_0016__li87318156336">Tags. For details, see <a href="er_01_0053.html">Viewing a Tag</a>.</li></ul>
|
||||
<ul id="er_01_0016__ul19520134293116"><li id="er_01_0016__li04013210324">Attachments, such as their name, type, and attached resources. For details, see <a href="er_01_0021.html">Viewing an Attachment</a>.</li><li id="er_01_0016__li896495913334">Route tables, such as the default route table and custom route tables. For details, see <a href="er_01_0027.html">Viewing Route Tables</a>.</li><li id="er_01_0016__li87318156336">Tags. For details, see <a href="er_01_0053.html">Viewing a Tag</a>.</li></ul>
|
||||
</div>
|
||||
<div class="section" id="er_01_0016__section1776015016613"><h4 class="sectiontitle">Procedure</h4><ol id="er_01_0016__ol5288104816346"><li id="er_01_0016__li8554112155212"><span>Log in to the management console.</span></li><li id="er_01_0016__li18272154101917"><span>Click <span><img id="er_01_0016__er_01_0064_en-us_topic_0014250631_en-us_topic_0014250631_image1733511156361" src="en-us_image_0000001190483836.png"></span> in the upper left corner and select the desired region and project.</span></li><li id="er_01_0016__li13278035192013"><span>Click <strong id="er_01_0016__er_01_0064_b0877172561410">Service List</strong> and choose <strong id="er_01_0016__er_01_0064_b38631530121411">Networking</strong> > <strong id="er_01_0016__er_01_0064_b1949823361416">Enterprise Router</strong>.</span><p><p id="er_01_0016__er_01_0064_p131231735172115">The <strong id="er_01_0016__er_01_0064_b131401444138">Enterprise Router</strong> homepage is displayed.</p>
|
||||
</p></li><li id="er_01_0016__li6322510553"><span>Search for the target enterprise router by name.</span><p><p id="er_01_0016__p1919686114211">In addition to the information shown in the enterprise router list, you can go to <a href="#er_01_0016__li25751958135516">5</a> to view more details.</p>
|
||||
|
@ -3,7 +3,7 @@
|
||||
<h1 class="topictitle1">Deleting an Enterprise Router</h1>
|
||||
<div id="body0000001181500813"><div class="section" id="er_01_0017__section1631373542615"><h4 class="sectiontitle">Scenarios</h4><p id="er_01_0017__p157813402267">This section describes how to delete an enterprise router.</p>
|
||||
</div>
|
||||
<div class="section" id="er_01_0017__section1136663124119"><h4 class="sectiontitle">Notes and Constraints</h4><ul id="er_01_0017__ul437410101411"><li id="er_01_0017__li97197540254">An enterprise router that has attachments cannot be deleted. To delete such an enterprise router, delete its attachments first. For details, see <a href="er_01_0022.html">Deleting an Attachment</a>.</li><li id="er_01_0017__li6446124411415">An enterprise router that has route tables can be deleted directly.</li><li id="er_01_0017__li1637172784517">An enterprise router that is shared with other accounts can be deleted directly.</li><li id="er_01_0017__li1437132102711">Deleting an enterprise router will also delete all of its flow logs.</li></ul>
|
||||
<div class="section" id="er_01_0017__section1136663124119"><h4 class="sectiontitle">Notes and Constraints</h4><ul id="er_01_0017__ul437410101411"><li id="er_01_0017__li97197540254">An enterprise router that has attachments cannot be deleted. Delete the attachments first. For details, see <a href="er_01_0019.html">Attachment Overview</a>.</li><li id="er_01_0017__li6446124411415">An enterprise router that has route tables can be deleted directly.</li><li id="er_01_0017__li1637172784517">An enterprise router that is shared with other accounts can be deleted directly.</li><li id="er_01_0017__li1437132102711">Deleting an enterprise router will also delete all of its flow logs.</li></ul>
|
||||
</div>
|
||||
<div class="section" id="er_01_0017__section1776015016613"><h4 class="sectiontitle">Procedure</h4><ol id="er_01_0017__ol5288104816346"><li id="er_01_0017__li1233111618521"><span>Log in to the management console.</span></li><li id="er_01_0017__li18272154101917"><span>Click <span><img id="er_01_0017__er_01_0064_en-us_topic_0014250631_en-us_topic_0014250631_image1733511156361" src="en-us_image_0000001190483836.png"></span> in the upper left corner and select the desired region and project.</span></li><li id="er_01_0017__li13278035192013"><span>Click <strong id="er_01_0017__er_01_0064_b0877172561410">Service List</strong> and choose <strong id="er_01_0017__er_01_0064_b38631530121411">Networking</strong> > <strong id="er_01_0017__er_01_0064_b1949823361416">Enterprise Router</strong>.</span><p><p id="er_01_0017__er_01_0064_p131231735172115">The <strong id="er_01_0017__er_01_0064_b131401444138">Enterprise Router</strong> homepage is displayed.</p>
|
||||
</p></li><li id="er_01_0017__li6322510553"><span>Search for the target enterprise router by name.</span><p><div class="fignone" id="er_01_0017__fig2034013312252"><span class="figcap"><b>Figure 1 </b>Searching for an enterprise router</span><br><span><img id="er_01_0017__er_01_0016_image1553618920257" src="en-us_image_0000001674900098.png"></span></div>
|
||||
|
@ -10,13 +10,13 @@
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="er_01_0019.html">Attachment Overview</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="er_01_0070.html">Adding VPC Attachments to an Enterprise Router</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="er_01_0167.html">VPC Attachments</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="er_01_0168.html">Virtual Gateway Attachments</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="er_01_0093.html">Changing the Name of an Attachment</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="er_01_0021.html">Viewing Details About an Attachment</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="er_01_0022.html">Deleting an Attachment</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="er_01_0021.html">Viewing an Attachment</a></strong><br>
|
||||
</li>
|
||||
</ul>
|
||||
</div>
|
||||
|
@ -19,9 +19,9 @@
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="29.610000000000003%" headers="mcps1.3.1.2.2.6.1.2 "><p id="er_01_0019__p1434313312103">VPC</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="22.510000000000005%" headers="mcps1.3.1.2.2.6.1.3 "><p id="er_01_0019__p534314336105"><a href="er_01_0070.html">Adding VPC Attachments to an Enterprise Router</a></p>
|
||||
<td class="cellrowborder" valign="top" width="22.510000000000005%" headers="mcps1.3.1.2.2.6.1.3 "><p id="er_01_0019__p534314336105"><a href="er_01_0070.html">Creating a VPC Attachment</a></p>
|
||||
</td>
|
||||
<td class="cellrowborder" rowspan="2" valign="top" width="13.260000000000002%" headers="mcps1.3.1.2.2.6.1.4 "><p id="er_01_0019__p6343333141014"><a href="er_01_0021.html">Viewing Details About an Attachment</a></p>
|
||||
<td class="cellrowborder" rowspan="2" valign="top" width="13.260000000000002%" headers="mcps1.3.1.2.2.6.1.4 "><p id="er_01_0019__p6343333141014"><a href="er_01_0021.html">Viewing an Attachment</a></p>
|
||||
<p id="er_01_0019__p55675617234"></p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="18.000000000000004%" headers="mcps1.3.1.2.2.6.1.5 "><p id="er_01_0019__p934318339105"><a href="er_01_0072.html">Deleting a VPC Attachment</a></p>
|
||||
@ -31,7 +31,7 @@
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" headers="mcps1.3.1.2.2.6.1.2 "><p id="er_01_0019__p69351248242">Virtual gateway of Direct Connect</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" headers="mcps1.3.1.2.2.6.1.3 "><p id="er_01_0019__p3792529171610">Attach a virtual gateway to an enterprise router. For details, see <a href="https://docs.otc.t-systems.com/direct-connect/umn/getting_started/enabling_direct_connect/connecting_your_on-premises_data_center_to_the_cloud.html" target="_blank" rel="noopener noreferrer">Connecting Your On-Premises Data Center to the Cloud</a>.</p>
|
||||
<td class="cellrowborder" valign="top" headers="mcps1.3.1.2.2.6.1.3 "><p id="er_01_0019__p899852815114"><a href="er_01_0169.html">Creating a Virtual Gateway Attachment</a></p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" headers="mcps1.3.1.2.2.6.1.4 "><p id="er_01_0019__p1969201582411"><a href="er_01_0073.html">Deleting a Virtual Gateway Attachment</a></p>
|
||||
</td>
|
||||
|
@ -1,6 +1,6 @@
|
||||
<a name="er_01_0021"></a><a name="er_01_0021"></a>
|
||||
|
||||
<h1 class="topictitle1">Viewing Details About an Attachment</h1>
|
||||
<h1 class="topictitle1">Viewing an Attachment</h1>
|
||||
<div id="body0000001135305036"><div class="section" id="er_01_0021__section1631373542615"><h4 class="sectiontitle">Scenarios</h4><p id="er_01_0021__p1815312485110">This section describes how to view details about the attachments of an enterprise router, including the attachment name, attachment type, and attached resources.</p>
|
||||
<p id="er_01_0021__p78035193299">The methods for viewing details about different types of attachments are the same. This section uses a VPC attachment as an example.</p>
|
||||
</div>
|
||||
|
@ -4,7 +4,7 @@
|
||||
<div id="body0000001181302665"><div class="section" id="er_01_0028__section1631373542615"><h4 class="sectiontitle">Scenarios</h4><p id="er_01_0028__p49638505020">This section describes how to delete a route table of an enterprise router.</p>
|
||||
</div>
|
||||
<div class="section" id="er_01_0028__section1136663124119"><h4 class="sectiontitle">Notes and Constraints</h4><ul id="er_01_0028__ul59951969191"><li id="er_01_0028__li17995106191919">If a route table is used as the default association route table and/or default propagation route table, the route table cannot be deleted.<ul id="er_01_0028__ul3864750132118"><li id="er_01_0028__li11563855172017">If <strong id="er_01_0028__b169921541142112">Default Route Association</strong> is set to <strong id="er_01_0028__b1367914512118">Yes</strong> on the basic information page of the route table, the route table is used as the default association route table.</li><li id="er_01_0028__li18409151514213">Also, if <strong id="er_01_0028__b6310181510225">Default Route Propagation</strong> is set to <strong id="er_01_0028__b173111815112210">Yes</strong> on the basic information of the route table, the route table is used as the default propagation route table.</li></ul>
|
||||
<p id="er_01_0028__p1976513198529">To delete such a route table, disable <strong id="er_01_0028__b19671443133013">Default Route Association</strong> and <strong id="er_01_0028__b77591754133016">Default Route Propagation</strong> first. For details, see <a href="er_01_0013.html">Modifying an Enterprise Router</a>.</p>
|
||||
<p id="er_01_0028__p1976513198529">To delete such a route table, change <strong id="er_01_0028__b19671443133013">Default Route Association</strong> and <strong id="er_01_0028__b77591754133016">Default Route Propagation</strong> settings. For details, see <a href="er_01_0013.html">Modifying an Enterprise Router</a>.</p>
|
||||
</li><li id="er_01_0028__li1338001992316">A route table cannot be deleted if it contains an association or a propagation. You need to delete the association and propagation before deleting this route table.<ul id="er_01_0028__ul14353813244"><li id="er_01_0028__li1146164414236">For details about how to delete an association, see <a href="er_01_0033.html">Deleting an Association from a Route Table</a>.</li><li id="er_01_0028__li239795172317">For details about how to delete a propagation, see <a href="er_01_0038.html">Deleting a Propagation from a Route Table</a>.</li></ul>
|
||||
</li><li id="er_01_0028__li1982433202510">A route table can be deleted if it contains only static routes. Ensure that the routes are no longer required before deleting their route table.</li></ul>
|
||||
</div>
|
||||
|
@ -22,7 +22,7 @@
|
||||
<tbody><tr id="er_01_0031__row155661555145112"><td class="cellrowborder" valign="top" width="17.58175817581758%" headers="mcps1.3.3.2.7.2.1.2.4.1.1 "><p id="er_01_0031__p65701255175113">Attachment Type</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="59.94599459945994%" headers="mcps1.3.3.2.7.2.1.2.4.1.2 "><p id="er_01_0031__p18653105983416">Mandatory</p>
|
||||
<div class="p" id="er_01_0031__p18290848124616">Select an attachment type.<ul id="er_01_0031__ul19290124834615"><li id="er_01_0031__li75401451154719"><strong id="er_01_0031__b7751692310">VPC</strong></li><li id="er_01_0031__li18540105119474"><strong id="er_01_0031__b1584334517376">Virtual gateway</strong></li></ul>
|
||||
<div class="p" id="er_01_0031__p18290848124616">Select an attachment type.<ul id="er_01_0031__ul19290124834615"><li id="er_01_0031__li75401451154719"><strong id="er_01_0031__b7751692310">VPC</strong>: A VPC is attached to the enterprise router.</li><li id="er_01_0031__li18540105119474"><strong id="er_01_0031__b1584334517376">Virtual gateway</strong>: A Direct Connect virtual gateway is attached to the enterprise router.</li></ul>
|
||||
</div>
|
||||
<p id="er_01_0031__p16612593580">For more information, see <a href="er_01_0019.html">Attachment Overview</a>.</p>
|
||||
</td>
|
||||
|
@ -22,7 +22,7 @@
|
||||
<tbody><tr id="er_01_0036__row155661555145112"><td class="cellrowborder" valign="top" width="17.711771177117715%" headers="mcps1.3.3.2.7.2.1.2.4.1.1 "><p id="er_01_0036__p65701255175113">Attachment Type</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="61.996199619962%" headers="mcps1.3.3.2.7.2.1.2.4.1.2 "><p id="er_01_0036__p18653105983416">Mandatory</p>
|
||||
<div class="p" id="er_01_0036__p18290848124616">Select an attachment type.<ul id="er_01_0036__er_01_0031_ul19290124834615"><li id="er_01_0036__er_01_0031_li75401451154719"><strong id="er_01_0036__er_01_0031_b7751692310">VPC</strong></li><li id="er_01_0036__er_01_0031_li18540105119474"><strong id="er_01_0036__er_01_0031_b1584334517376">Virtual gateway</strong></li></ul>
|
||||
<div class="p" id="er_01_0036__p18290848124616">Select an attachment type.<ul id="er_01_0036__er_01_0031_ul19290124834615"><li id="er_01_0036__er_01_0031_li75401451154719"><strong id="er_01_0036__er_01_0031_b7751692310">VPC</strong>: A VPC is attached to the enterprise router.</li><li id="er_01_0036__er_01_0031_li18540105119474"><strong id="er_01_0036__er_01_0031_b1584334517376">Virtual gateway</strong>: A Direct Connect virtual gateway is attached to the enterprise router.</li></ul>
|
||||
</div>
|
||||
<p id="er_01_0036__p16612593580">For more information, see <a href="er_01_0019.html">Attachment Overview</a>.</p>
|
||||
</td>
|
||||
|
@ -36,7 +36,7 @@
|
||||
</tr>
|
||||
<tr id="er_01_0041__row197716484118"><td class="cellrowborder" valign="top" width="17.57175717571757%" headers="mcps1.3.2.2.7.2.1.2.4.1.1 "><p id="er_01_0041__p206617541916">Attachment Type</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="60.35603560356036%" headers="mcps1.3.2.2.7.2.1.2.4.1.2 "><ul id="er_01_0041__ul103054590257"><li id="er_01_0041__li530516594258">If <strong id="er_01_0041__b375339803">Blackhole Route</strong> is not enabled, you need to configure this parameter.</li><li id="er_01_0041__li8305135920258">If <strong id="er_01_0041__b449514192181">Blackhole Route</strong> is enabled, you do not need to configure this parameter.</li></ul>
|
||||
<td class="cellrowborder" valign="top" width="60.35603560356036%" headers="mcps1.3.2.2.7.2.1.2.4.1.2 "><ul id="er_01_0041__ul103054590257"><li id="er_01_0041__li530516594258">If <strong id="er_01_0041__b2096637790">Blackhole Route</strong> is not enabled, you need to configure this parameter.</li><li id="er_01_0041__li8305135920258">If <strong id="er_01_0041__b449514192181">Blackhole Route</strong> is enabled, you do not need to configure this parameter.</li></ul>
|
||||
<p id="er_01_0041__p126616541513"><strong id="er_01_0041__b5998182517515">VPC</strong>: Create a static route for a VPC attachment.</p>
|
||||
<p id="er_01_0041__p1266454817">For more information, see <a href="er_01_0019.html">Attachment Overview</a>.</p>
|
||||
</td>
|
||||
|
@ -2,18 +2,15 @@
|
||||
|
||||
<h1 class="topictitle1">Creating a User and Granting Permissions</h1>
|
||||
<div id="body0000001181465239"><p id="er_01_0046__p198079372297">This section describes how to use IAM to implement fine-grained permissions control for your Enterprise Router resources. With IAM, you can:</p>
|
||||
<ul id="er_01_0046__ul1848820457453"><li id="er_01_0046__li348974516454">Create IAM users for employees based on the organizational structure of your enterprise. Each IAM user has their own security credentials, providing access to Enterprise Router resources.</li><li id="er_01_0046__li11681126173515">Assign only the minimum permissions required for users to perform a given task.</li><li id="er_01_0046__li12185165313915">Entrust an account or a cloud service to perform professional and efficient O&M on your Enterprise Router resources.</li></ul>
|
||||
<p id="er_01_0046__p14662743155318">If your account does not require individual IAM users, skip over this section.</p>
|
||||
<ul id="er_01_0046__ul1848820457453"><li id="er_01_0046__li348974516454">Create IAM users for employees based on the organizational structure of your enterprise. Each IAM user has their own security credentials, providing access to Enterprise Router resources.</li><li id="er_01_0046__li11681126173515">Grant only the minimum permissions required for users to perform a given task.</li><li id="er_01_0046__li12185165313915">Entrust an account or a cloud service to perform professional and efficient O&M on your Enterprise Router resources.</li></ul>
|
||||
<p id="er_01_0046__p14662743155318">If your account does not require individual IAM users, skip this topic.</p>
|
||||
<p id="er_01_0046__p158501603165"><a href="#er_01_0046__fig208811382017">Figure 1</a> shows the procedure for granting permissions.</p>
|
||||
<div class="section" id="er_01_0046__section17723185741610"><h4 class="sectiontitle">Prerequisites</h4><p id="er_01_0046__p118441867285">You have learned about the permissions supported by Enterprise Router and choose policies or roles according to your requirements. For details, see <a href="er_01_0008.html">Permissions</a>.</p>
|
||||
<div class="section" id="er_01_0046__section17723185741610"><h4 class="sectiontitle">Prerequisites</h4><p id="er_01_0046__p118441867285">You have learned about Enterprise Router permissions that can be added to the user group. For details about the system permissions supported by enterprise routers, see <a href="er_01_0008.html">Permissions</a>.</p>
|
||||
<p id="er_01_0046__p16449113113213">For the permissions of other services, see <a href="https://docs.otc.t-systems.com/permissions/index.html" target="_blank" rel="noopener noreferrer">Permission Description</a>.</p>
|
||||
</div>
|
||||
<div class="section" id="er_01_0046__section1189416161520"><h4 class="sectiontitle">Process Flow</h4><div class="fignone" id="er_01_0046__fig208811382017"><a name="er_01_0046__fig208811382017"></a><a name="fig208811382017"></a><span class="figcap"><b>Figure 1 </b>Process for granting Enterprise Router permissions</span><br><span><img class="eddx" id="er_01_0046__image38811381905" src="en-us_image_0000001208553649.png"></span></div>
|
||||
<p id="er_01_0046__p91763301418"></p>
|
||||
<ol id="er_01_0046__ol10176191312813"><li id="er_01_0046__li10176121316284"><a name="er_01_0046__li10176121316284"></a><a name="li10176121316284"></a><a href="https://docs.otc.t-systems.com/usermanual/iam/iam_01_0030.html" target="_blank" rel="noopener noreferrer">Create a user group and assign permissions to it</a>.<p id="er_01_0046__p41762137286">Create a user group on the IAM console, and assign the <strong id="er_01_0046__b121119513910">ER ReadOnlyAccess</strong> permission to the group.</p>
|
||||
</li><li id="er_01_0046__li181761413162818"><a href="https://docs.otc.t-systems.com/usermanual/iam/iam_01_0031.html" target="_blank" rel="noopener noreferrer">Create an IAM user and add it to the user group</a>.<p id="er_01_0046__p16177613182816">Create a user on the IAM console and add the user to the group created in <a href="#er_01_0046__li10176121316284">1</a>.</p>
|
||||
</li><li id="er_01_0046__li1177513202816"><a href="https://docs.otc.t-systems.com/usermanual/iam/iam_01_0032.html" target="_blank" rel="noopener noreferrer">Log in</a> and verify permissions.<p id="er_01_0046__p1317741312289">Log in to the management console as the created user, switch to the authorized region, and verify that the user has only the <strong id="er_01_0046__b8968151801218">ER ReadOnlyAccess</strong> permission.</p>
|
||||
<ol type="a" id="er_01_0046__ol166981250112914"><li id="er_01_0046__li1069814506293">Click <strong id="er_01_0046__b9791728141215">Service List</strong> and choose <strong id="er_01_0046__b156864261316">Enterprise Router</strong>. Then click <strong id="er_01_0046__b16690191116136">Create Enterprise Router</strong> in the upper right corner. If the enterprise router fails to be created, the <strong id="er_01_0046__b10395132921315">ER ReadOnlyAccess</strong> permission has taken effect.</li><li id="er_01_0046__li9698125012915">Choose any other service in the <strong id="er_01_0046__b1934034011315">Service List</strong>. If a message appears indicating insufficient permissions to access the service, the <strong id="er_01_0046__b611151121319">ER ReadOnlyAccess</strong> permission has already taken effect.</li></ol>
|
||||
<ol id="er_01_0046__ol10176191312813"><li id="er_01_0046__li10176121316284"><a href="https://docs.otc.t-systems.com/usermanual/iam/iam_01_0030.html" target="_blank" rel="noopener noreferrer">Create a user group and assign permissions to it</a> (<strong id="er_01_0046__b121119513910">ER ReadOnlyAccess</strong> as an example).</li><li id="er_01_0046__li181761413162818"><a href="https://docs.otc.t-systems.com/usermanual/iam/iam_01_0031.html" target="_blank" rel="noopener noreferrer">Create an IAM user and add it to the user group</a>.</li><li id="er_01_0046__li1177513202816"><a href="https://docs.otc.t-systems.com/usermanual/iam/iam_01_0032.html" target="_blank" rel="noopener noreferrer">Log in</a> to the management console as the created user, switch to the authorized region, and verify that the user has only the <strong id="er_01_0046__b8968151801218">ER ReadOnlyAccess</strong> permission.<ol type="a" id="er_01_0046__ol166981250112914"><li id="er_01_0046__li1069814506293">Click <strong id="er_01_0046__b9791728141215">Service List</strong> and choose <strong id="er_01_0046__b156864261316">Enterprise Router</strong>. Then click <strong id="er_01_0046__b16690191116136">Create Enterprise Router</strong> in the upper right corner. If the enterprise router fails to be created, the <strong id="er_01_0046__b10395132921315">ER ReadOnlyAccess</strong> permission has taken effect.</li><li id="er_01_0046__li9698125012915">Choose any other service in the <strong id="er_01_0046__b1934034011315">Service List</strong>. If a message appears indicating insufficient permissions to access the service, the <strong id="er_01_0046__b611151121319">ER ReadOnlyAccess</strong> permission has already taken effect.</li></ol>
|
||||
</li></ol>
|
||||
</div>
|
||||
</div>
|
||||
|
@ -4,7 +4,7 @@
|
||||
<div id="body0000001135120504"></div>
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="er_01_0062.html">Quick Start</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="er_01_0062.html">Overview</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="er_01_0063.html">Step 1: Plan Networks and Resources</a></strong><br>
|
||||
</li>
|
||||
|
@ -1,7 +1,7 @@
|
||||
<a name="er_01_0062"></a><a name="er_01_0062"></a>
|
||||
|
||||
<h1 class="topictitle1">Quick Start</h1>
|
||||
<div id="body0000001197924817"><div class="section" id="er_01_0062__section116311314431"><h4 class="sectiontitle">Background</h4><p id="er_01_0062__p13141113818437">Four VPCs are created in region A on <span id="er_01_0062__text263320207459">public cloud</span> and they need to communicate with each other.</p>
|
||||
<h1 class="topictitle1">Overview</h1>
|
||||
<div id="body0000001197924817"><div class="section" id="er_01_0062__section116311314431"><h4 class="sectiontitle">Background</h4><p id="er_01_0062__p13141113818437">Four VPCs are created in region A on <span id="er_01_0062__text263320207459">the public cloud</span> and they need to communicate with each other.</p>
|
||||
<p id="er_01_0062__p1557115812548">You can create an enterprise router in region A and attach the four VPCs to the enterprise router. The enterprise router can route traffic among the VPCs so that they can communicate with each other.</p>
|
||||
<div class="fignone" id="er_01_0062__fig1034610281162"><span class="figcap"><b>Figure 1 </b>Communications among VPCs in the same region</span><br><span><img class="eddx" id="er_01_0062__image1934682813612" src="en-us_image_0000001295153022.png"></span></div>
|
||||
<div class="note" id="er_01_0062__note18353103217419"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="er_01_0062__p129847506387">This document describes how to use an enterprise router to quickly allow multiple VPCs in the same region to communicate with each other.</p>
|
||||
|
@ -151,7 +151,7 @@
|
||||
</thead>
|
||||
<tbody><tr id="er_01_0063__row1344013379228"><td class="cellrowborder" rowspan="4" valign="top" width="12.572514502900582%" headers="mcps1.3.3.2.2.1.1.2.8.1.1 "><p id="er_01_0063__p16934115313225">er-test-01</p>
|
||||
</td>
|
||||
<td class="cellrowborder" rowspan="4" valign="top" width="11.122224444888976%" headers="mcps1.3.3.2.2.1.1.2.8.1.2 "><p id="er_01_0063__p14840152816013">64512</p>
|
||||
<td class="cellrowborder" rowspan="4" valign="top" width="11.122224444888976%" headers="mcps1.3.3.2.2.1.1.2.8.1.2 "><p id="er_01_0063__p597073622511">64800</p>
|
||||
</td>
|
||||
<td class="cellrowborder" rowspan="4" valign="top" width="14.652930586117222%" headers="mcps1.3.3.2.2.1.1.2.8.1.3 "><p id="er_01_0063__p14934853142216">Enable</p>
|
||||
</td>
|
||||
|
@ -39,9 +39,10 @@
|
||||
</tr>
|
||||
<tr id="er_01_0064__row478341818565"><td class="cellrowborder" valign="top" width="17.741774177417742%" headers="mcps1.3.2.2.5.2.1.2.4.1.1 "><p id="er_01_0064__p127830184568">ASN</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="59.84598459845984%" headers="mcps1.3.2.2.5.2.1.2.4.1.2 "><p id="er_01_0064__p362984115920">Set the Autonomous System Number (ASN) for the cloud side of a Border Gateway Protocol (BGP) session. You cannot change it after the enterprise router is created.</p>
|
||||
<td class="cellrowborder" valign="top" width="59.84598459845984%" headers="mcps1.3.2.2.5.2.1.2.4.1.2 "><p id="er_01_0064__p362984115920">Enter an ASN based on your network plan. It cannot be changed after the enterprise router is created.</p>
|
||||
<p id="er_01_0064__p12673953163619">Default ASN: 64800</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="22.41224122412241%" headers="mcps1.3.2.2.5.2.1.2.4.1.3 "><p id="er_01_0064__p57831418105619">64512</p>
|
||||
<td class="cellrowborder" valign="top" width="22.41224122412241%" headers="mcps1.3.2.2.5.2.1.2.4.1.3 "><p id="er_01_0064__p597073622511">64800</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="er_01_0064__row14429124613579"><td class="cellrowborder" valign="top" width="17.741774177417742%" headers="mcps1.3.2.2.5.2.1.2.4.1.1 "><p id="er_01_0064__p1942934613577">Default Route Table Association</p>
|
||||
|
@ -25,10 +25,16 @@
|
||||
</tr>
|
||||
<tr id="er_01_0066__row478341818565"><td class="cellrowborder" valign="top" width="17.531753175317533%" headers="mcps1.3.2.2.7.2.1.2.4.1.1 "><p id="er_01_0066__p572912461383">Attachment Type</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="59.54595459545955%" headers="mcps1.3.2.2.7.2.1.2.4.1.2 "><ol type="a" id="er_01_0066__ol134874249109"><li id="er_01_0066__li10487324111020">Select <strong id="er_01_0066__b1727691382912">VPC</strong>. The type cannot be changed after the attachment is created.</li><li id="er_01_0066__li13442614107">Select the VPC to be attached to the enterprise router from the drop-down list. The VPC cannot be changed after the attachment is created.</li><li id="er_01_0066__li16172816121120">Select the subnet to be attached to the enterprise router from the drop-down list. The subnet cannot be changed after the attachment is created.<ul id="er_01_0066__ul082783282514"><li id="er_01_0066__er_01_0070_li45812148616">You can select any subnet in the VPC. All subnets in the same VPC can communicate with each other by default and the enterprise router can connect to the entire VPC.</li><li id="er_01_0066__er_01_0070_li35813141611">You are advised to select a subnet that is dedicated for connecting to the enterprise router. To ensure that the subnet has enough IP addresses for the system and the enterprise router, make the subnet mask /28 or smaller.</li></ul>
|
||||
</li></ol>
|
||||
<td class="cellrowborder" valign="top" width="59.54595459545955%" headers="mcps1.3.2.2.7.2.1.2.4.1.2 "><p id="er_01_0066__p148831414431">Select <strong id="er_01_0066__b53141557165011">VPC</strong>. The type cannot be changed after the attachment is created.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="22.922292229222922%" headers="mcps1.3.2.2.7.2.1.2.4.1.3 "><ul id="er_01_0066__ul148299190511"><li id="er_01_0066__li282971919516">Attachment Type: VPC</li><li id="er_01_0066__li17829819125116">VPC: vpc-demo-01</li><li id="er_01_0066__li1582914194515">Subnet: subnet-demo-01</li></ul>
|
||||
<td class="cellrowborder" valign="top" width="22.922292229222922%" headers="mcps1.3.2.2.7.2.1.2.4.1.3 "><p id="er_01_0066__p98955322434">VPC</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="er_01_0066__row1399263764213"><td class="cellrowborder" valign="top" width="17.531753175317533%" headers="mcps1.3.2.2.7.2.1.2.4.1.1 "><p id="er_01_0066__p1599263710422">Attached Resource</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="59.54595459545955%" headers="mcps1.3.2.2.7.2.1.2.4.1.2 "><ol type="a" id="er_01_0066__ol998313764312"><li id="er_01_0066__li13442614107">Select the VPC to be attached to the enterprise router from the drop-down list. The VPC cannot be changed after the attachment is created.</li><li id="er_01_0066__li99834714433">Select the subnet to be attached to the enterprise router from the drop-down list. The subnet cannot be changed after the attachment is created.</li></ol>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="22.922292229222922%" headers="mcps1.3.2.2.7.2.1.2.4.1.3 "><ul id="er_01_0066__ul0306192912436"><li id="er_01_0066__li17829819125116">VPC: vpc-demo-01</li><li id="er_01_0066__li1582914194515">Subnet: subnet-demo-01</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="er_01_0066__row166018445475"><td class="cellrowborder" valign="top" width="17.531753175317533%" headers="mcps1.3.2.2.7.2.1.2.4.1.1 "><p id="er_01_0066__p1733161344319">Auto Add Routes</p>
|
||||
|
@ -23,7 +23,14 @@
|
||||
</th>
|
||||
</tr>
|
||||
</thead>
|
||||
<tbody><tr id="er_01_0067__row155661555145112"><td class="cellrowborder" valign="top" width="17.501750175017502%" headers="mcps1.3.3.2.10.2.1.2.4.1.1 "><p id="er_01_0067__p984020445304">Destination</p>
|
||||
<tbody><tr id="er_01_0067__row16263115918580"><td class="cellrowborder" valign="top" width="17.501750175017502%" headers="mcps1.3.3.2.10.2.1.2.4.1.1 "><p id="er_01_0067__p797916211593">Destination Type</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="60.22602260226023%" headers="mcps1.3.3.2.10.2.1.2.4.1.2 "><p id="er_01_0067__p497915265917">The destination can only be <strong id="er_01_0067__b646712392715">IP address</strong>. You can set a single IP address or network segment.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="22.272227222722275%" headers="mcps1.3.3.2.10.2.1.2.4.1.3 "><p id="er_01_0067__p19797265919">IP address</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="er_01_0067__row155661555145112"><td class="cellrowborder" valign="top" width="17.501750175017502%" headers="mcps1.3.3.2.10.2.1.2.4.1.1 "><p id="er_01_0067__p984020445304">Destination</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="60.22602260226023%" headers="mcps1.3.3.2.10.2.1.2.4.1.2 "><p id="er_01_0067__p189168663117">The destination is used to route traffic from this VPC to other VPCs attached to the enterprise router. You can change it after the route is created.</p>
|
||||
<ul id="er_01_0067__ul278841163217"><li id="er_01_0067__li27881316321">Set the destination to the CIDR blocks of VPCs or their subnets that your VPC need to communicate with.</li><li id="er_01_0067__li6145165616545">Do not set the destination of a route (with an enterprise router as the next hop) to 0.0.0.0/0 in the VPC route table. If an ECS in the VPC has an EIP bound, the VPC route table will have a policy-based route with 0.0.0.0/0 as the destination, which has a higher priority than the route with the enterprise router as the next hop. In this case, traffic is forwarded to the EIP and cannot reach the enterprise router.</li></ul>
|
||||
|
@ -46,11 +46,13 @@
|
||||
<tr id="er_01_0069__row478341818565"><td class="cellrowborder" valign="top" width="18.221822182218222%" headers="mcps1.3.2.2.5.2.1.2.4.1.1 "><p id="er_01_0069__p127830184568">ASN</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="59.27592759275928%" headers="mcps1.3.2.2.5.2.1.2.4.1.2 "><p id="er_01_0069__p139111718359">Mandatory</p>
|
||||
<p id="er_01_0069__p1888805220424">An autonomous system is an IP network that is managed by an entity and has the same routing policy. On a BGP network, each autonomous system is assigned a unique ASN to differentiate them.</p>
|
||||
<p id="er_01_0069__p1278381895611">You can use the default ASN, or specify one from 64512 to 65534 or from 4200000000 to 4294967294.</p>
|
||||
<p id="er_01_0069__p1888805220424">An autonomous system is an IP network that is managed by an entity and has the same route policy. On a BGP network, each autonomous system is assigned a unique ASN to differentiate them.</p>
|
||||
<p id="er_01_0069__p1278381895611">Specify a dedicated ASN in the range of 64512-65534 or 4200000000-4294967294.</p>
|
||||
<p id="er_01_0069__p11385717556">Networks in the same region can be considered as an AS.</p>
|
||||
<p id="er_01_0069__p6732843366">When Direct Connect and Enterprise Router are used to set up a hybrid cloud network, it is recommended that you set the ASN of the enterprise router different from the BGP ASN of the Direct Connect virtual gateway. If there are multiple Direct Connect connections associated with the enterprise router and the connections do not work in load balancing or active/standby mode, set different BGP ASNs for the virtual gateways of these connections.</p>
|
||||
<p id="er_01_0069__p12673953163619">Default ASN: 64800</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="22.5022502250225%" headers="mcps1.3.2.2.5.2.1.2.4.1.3 "><p id="er_01_0069__p57831418105619">64512</p>
|
||||
<td class="cellrowborder" valign="top" width="22.5022502250225%" headers="mcps1.3.2.2.5.2.1.2.4.1.3 "><p id="er_01_0069__p57831418105619">64800</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="er_01_0069__row14429124613579"><td class="cellrowborder" valign="top" width="18.221822182218222%" headers="mcps1.3.2.2.5.2.1.2.4.1.1 "><p id="er_01_0069__p1942934613577">Default Route Table Association</p>
|
||||
|
@ -1,7 +1,7 @@
|
||||
<a name="er_01_0070"></a><a name="er_01_0070"></a>
|
||||
|
||||
<h1 class="topictitle1">Adding VPC Attachments to an Enterprise Router</h1>
|
||||
<div id="body0000001152745484"><div class="section" id="er_01_0070__section1776931281618"><h4 class="sectiontitle">Scenarios</h4><p id="er_01_0070__p8734113614438">This section describes how to attach VPCs to an enterprise router so that these VPCs can communicate with each other.</p>
|
||||
<h1 class="topictitle1">Creating a VPC Attachment</h1>
|
||||
<div id="body0000001152745484"><div class="section" id="er_01_0070__section1776931281618"><h4 class="sectiontitle">Scenarios</h4><p id="er_01_0070__p8734113614438">This section describes how to attach a VPC to an enterprise router so that the VPCs attached to the enterprise router can communicate with each other.</p>
|
||||
</div>
|
||||
<div class="section" id="er_01_0070__section292234514349"><h4 class="sectiontitle">Notes and Constraints</h4><ul id="er_01_0070__ul1460012431441"><li id="er_01_0070__li1600124317442">If you use the propagated routes of a VPC attachment, the route table of the enterprise router automatically learns the VPC CIDR block as the destination of routes. The CIDR block cannot be changed. To ensure that routes in the route table do not conflict, the CIDR blocks of all VPCs attached to the enterprise router cannot overlap. Otherwise, communication fails.</li><li id="er_01_0070__li1387055114412">If your existing VPCs have overlapping CIDR blocks, do not use propagated routes. Instead, manually add static routes to the route table of the enterprise router. The destination of the routes can be VPC subnet CIDR blocks or smaller ones.</li></ul>
|
||||
</div>
|
||||
@ -31,17 +31,27 @@
|
||||
<tr id="er_01_0070__row478341818565"><td class="cellrowborder" valign="top" width="17.37173717371737%" headers="mcps1.3.3.2.7.2.1.2.4.1.1 "><p id="er_01_0070__p572912461383">Attachment Type</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="59.67596759675967%" headers="mcps1.3.3.2.7.2.1.2.4.1.2 "><p id="er_01_0070__p47279463813">Mandatory</p>
|
||||
<ol type="a" id="er_01_0070__ol105931017131514"><li id="er_01_0070__li6593131721514">Select the attachment type. Select <strong id="er_01_0070__b8354205919294">VPC</strong>, indicating that the instance to be attached to the enterprise router is a VPC.<p id="er_01_0070__p199667351417">The methods for creating attachments vary depending on the attachment type. For details, see <a href="er_01_0019.html">Attachment Overview</a>.</p>
|
||||
</li><li id="er_01_0070__li12459103216151">Select the VPC to be attached to the enterprise router. You can enter a VPC name to quickly find the target VPC.</li><li id="er_01_0070__li2484143910155">Select a subnet in the selected VPC. You can enter a subnet name to quickly find the target subnet.<ul id="er_01_0070__ul12586144615"><li id="er_01_0070__li45812148616">You can select any subnet in the VPC. All subnets in the same VPC can communicate with each other by default and the enterprise router can connect to the entire VPC.</li><li id="er_01_0070__li35813141611">You are advised to select a subnet that is dedicated for connecting to the enterprise router. To ensure that the subnet has enough IP addresses for the system and the enterprise router, make the subnet mask /28 or smaller.</li></ul>
|
||||
<p id="er_01_0070__p1926182604115">Select <strong id="er_01_0070__b32171381791">VPC</strong>, indicating that a VPC is to be attached to the enterprise router.</p>
|
||||
<p id="er_01_0070__p199667351417">The methods for creating attachments vary depending on the attachment type. For details, see <a href="er_01_0019.html">Attachment Overview</a>.</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="22.952295229522953%" headers="mcps1.3.3.2.7.2.1.2.4.1.3 "><p id="er_01_0070__p123690426">VPC</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="er_01_0070__row184481211104110"><td class="cellrowborder" valign="top" width="17.37173717371737%" headers="mcps1.3.3.2.7.2.1.2.4.1.1 "><p id="er_01_0070__p10449811144113">Attached Resource</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="59.67596759675967%" headers="mcps1.3.3.2.7.2.1.2.4.1.2 "><p id="er_01_0070__p114491611134114">Mandatory</p>
|
||||
<ol type="a" id="er_01_0070__ol163081848174111"><li id="er_01_0070__li12459103216151">Select the VPC to be attached to the enterprise router. You can enter a VPC name to quickly find the target VPC.</li><li id="er_01_0070__li1430814812416">Select a subnet in the selected VPC. You can enter a subnet name to quickly find the target subnet.<ul id="er_01_0070__ul13084489415"><li id="er_01_0070__li45812148616">You can select any subnet in the VPC. All subnets in the same VPC can communicate with each other by default and the enterprise router can connect to the entire VPC.</li><li id="er_01_0070__li630810481414">You are advised to select a subnet that is dedicated for connecting to the enterprise router. To ensure that the subnet has enough IP addresses for the system and the enterprise router, make the subnet mask /28 or smaller.</li></ul>
|
||||
</li></ol>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="22.952295229522953%" headers="mcps1.3.3.2.7.2.1.2.4.1.3 "><ul id="er_01_0070__ul1665445612153"><li id="er_01_0070__li1465419564155">Attachment Type: VPC</li><li id="er_01_0070__li1041718134165">VPC: vpc-A</li><li id="er_01_0070__li104175133167">Subnet: subnet-A01</li></ul>
|
||||
<td class="cellrowborder" valign="top" width="22.952295229522953%" headers="mcps1.3.3.2.7.2.1.2.4.1.3 "><ul id="er_01_0070__ul1440115194218"><li id="er_01_0070__li1041718134165">VPC: vpc-A</li><li id="er_01_0070__li104175133167">Subnet: subnet-A01</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="er_01_0070__row1133413104312"><td class="cellrowborder" valign="top" width="17.37173717371737%" headers="mcps1.3.3.2.7.2.1.2.4.1.1 "><p id="er_01_0070__p1733161344319">Auto Add Routes</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="59.67596759675967%" headers="mcps1.3.3.2.7.2.1.2.4.1.2 "><p id="er_01_0070__p12456720164813">Optional</p>
|
||||
<ul id="er_01_0070__ul86638386510"><li id="er_01_0070__li3663143815113">Enable this option if you want to automatically add routes (with this enterprise router as the next hop and 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16 as the destinations) to all route tables of the selected VPC.</li><li id="er_01_0070__li125731058105114">Do not enable this option if an existing route in the VPC route tables has a destination set to 10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16 because the routes will fail to be added. After the attachment is created, manually <a href="er_01_0067.html">Step 5: (Optional) Add Routes to VPC Route Tables</a>.</li></ul>
|
||||
<div class="note" id="er_01_0070__note14807608109"><span class="notetitle"> NOTE: </span><div class="notebody"><p id="er_01_0070__p178071011102">This parameter is only displayed when a VPC attachment is created. It cannot be enabled after the VPC attachment is created.</p>
|
||||
</div></div>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="22.952295229522953%" headers="mcps1.3.3.2.7.2.1.2.4.1.3 "><p id="er_01_0070__p5331013124312">Enable</p>
|
||||
</td>
|
||||
@ -79,7 +89,7 @@
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="er_01_0018.html">Attachments</a></div>
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="er_01_0167.html">VPC Attachments</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
@ -3,7 +3,7 @@
|
||||
<h1 class="topictitle1">Deleting a VPC Attachment</h1>
|
||||
<div id="body0000001164805672"><div class="section" id="er_01_0072__section1631373542615"><h4 class="sectiontitle">Scenarios</h4><p id="er_01_0072__p49638505020">This section describes how to delete a VPC attachment from an enterprise router.</p>
|
||||
</div>
|
||||
<div class="section" id="er_01_0072__section1136663124119"><h4 class="sectiontitle">Notes and Constraints</h4><ul id="er_01_0072__ul1735610308459"><li id="er_01_0072__li77724113450">Deleting an attachment will also delete its associations, propagations, and propagated routes in the route table.</li><li id="er_01_0072__li1535693019457">After an attachment is deleted, the next hop of its related static routes will be <strong id="er_01_0072__b20132181251814">Blackhole</strong>. If the destination of a packet matches the blackhole route, the packet will be discarded.</li><li id="er_01_0072__li1437132102711">Deleting an attachment will also delete its flow logs.</li></ul>
|
||||
<div class="section" id="er_01_0072__section1136663124119"><h4 class="sectiontitle">Notes and Constraints</h4><ul id="er_01_0072__ul1735610308459"><li id="er_01_0072__li77724113450">Deleting an attachment will also delete its associations, propagations, and propagated routes in the route table.</li><li id="er_01_0072__li1535693019457">After an attachment is deleted, the next hop of its related static routes will be <strong id="er_01_0072__b20132181251814">Blackhole</strong>. If the destination of a packet matches the blackhole route, the packet will be discarded.</li><li id="er_01_0072__li1437132102711">If flow logging is enabled for an attachment, flow logging will be disabled, but collected flow logs will not be deleted.</li></ul>
|
||||
</div>
|
||||
<div class="section" id="er_01_0072__section1776015016613"><h4 class="sectiontitle">Procedure</h4><ol id="er_01_0072__ol5288104816346"><li id="er_01_0072__li777812273526"><span>Log in to the management console.</span></li><li id="er_01_0072__li18272154101917"><span>Click <span><img id="er_01_0072__er_01_0064_en-us_topic_0014250631_en-us_topic_0014250631_image1733511156361" src="en-us_image_0000001190483836.png"></span> in the upper left corner and select the desired region and project.</span></li><li id="er_01_0072__li13278035192013"><span>Click <strong id="er_01_0072__er_01_0064_b0877172561410">Service List</strong> and choose <strong id="er_01_0072__er_01_0064_b38631530121411">Networking</strong> > <strong id="er_01_0072__er_01_0064_b1949823361416">Enterprise Router</strong>.</span><p><p id="er_01_0072__er_01_0064_p131231735172115">The <strong id="er_01_0072__er_01_0064_b131401444138">Enterprise Router</strong> homepage is displayed.</p>
|
||||
</p></li><li id="er_01_0072__li6322510553"><span>Search for the target enterprise router by name.</span><p><div class="fignone" id="er_01_0072__fig2034013312252"><span class="figcap"><b>Figure 1 </b>Searching for an enterprise router</span><br><span><img id="er_01_0072__er_01_0016_image1553618920257" src="en-us_image_0000001674900098.png"></span></div>
|
||||
@ -15,7 +15,7 @@
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="er_01_0022.html">Deleting an Attachment</a></div>
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="er_01_0167.html">VPC Attachments</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
@ -4,12 +4,12 @@
|
||||
<div id="body0000001164965612"><div class="section" id="er_01_0073__section1631373542615"><h4 class="sectiontitle">Scenarios</h4><p id="er_01_0073__p49638505020">This section describes how to delete a virtual gateway attachment from an enterprise router.</p>
|
||||
</div>
|
||||
<div class="section" id="er_01_0073__section1136663124119"><h4 class="sectiontitle">Notes and Constraints</h4><ul id="er_01_0073__ul757994193211"><li id="er_01_0073__li64692363319">Deleting an attachment will also delete its associations, propagations, and propagated routes in the route table.</li></ul>
|
||||
<ul id="er_01_0073__ul1679761413318"><li id="er_01_0073__li18104216133112">Deleting an attachment will also delete its flow logs.</li></ul>
|
||||
<ul id="er_01_0073__ul1679761413318"><li id="er_01_0073__li18104216133112">If flow logging is enabled for an attachment, flow logging will be disabled, but collected flow logs will not be deleted.</li></ul>
|
||||
</div>
|
||||
<div class="section" id="er_01_0073__section6881739202716"><h4 class="sectiontitle">Procedure</h4><ol id="er_01_0073__ol421545315115"><li id="er_01_0073__li12578317523"><span>Log in to the management console.</span></li><li id="er_01_0073__li18272154101917"><span>Click <span><img id="er_01_0073__er_01_0064_en-us_topic_0014250631_en-us_topic_0014250631_image1733511156361" src="en-us_image_0000001190483836.png"></span> in the upper left corner and select the desired region and project.</span></li><li id="er_01_0073__li13278035192013"><span>Click <strong id="er_01_0073__er_01_0064_b0877172561410">Service List</strong> and choose <strong id="er_01_0073__er_01_0064_b38631530121411">Networking</strong> > <strong id="er_01_0073__er_01_0064_b1949823361416">Enterprise Router</strong>.</span><p><p id="er_01_0073__er_01_0064_p131231735172115">The <strong id="er_01_0073__er_01_0064_b131401444138">Enterprise Router</strong> homepage is displayed.</p>
|
||||
</p></li><li id="er_01_0073__li6322510553"><span>Search for the target enterprise router by name.</span><p><div class="fignone" id="er_01_0073__fig2034013312252"><span class="figcap"><b>Figure 1 </b>Searching for an enterprise router</span><br><span><img id="er_01_0073__er_01_0016_image1553618920257" src="en-us_image_0000001674900098.png"></span></div>
|
||||
</p></li><li id="er_01_0073__li25751958135516"><span>Go to the <strong id="er_01_0073__b1076115014102">Attachments</strong> tab using either of the following methods:</span><p><ul id="er_01_0073__ul1991183111311"><li id="er_01_0073__li14916391316">In the upper right corner of the enterprise router, click <strong id="er_01_0073__b106431841107">Manage Attachment</strong>.</li><li id="er_01_0073__li791113151319">Click the enterprise router name and click <span class="wintitle" id="er_01_0073__wintitle46198561012"><b>Attachments</b></span>.</li></ul>
|
||||
<div class="notice" id="er_01_0073__note206791356519"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="er_01_0073__p767812093014">A virtual gateway attachment cannot be directly deleted on the <strong id="er_01_0073__b6686103213426">Attachments</strong> page of the enterprise router.</p>
|
||||
<div class="notice" id="er_01_0073__note206791356519"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="er_01_0073__p767812093014">A virtual gateway attachment cannot be directly deleted on the <strong id="er_01_0073__b6686103213426">Attachments</strong> tab.</p>
|
||||
<p id="er_01_0073__p15679143512517">A virtual gateway attachment will be automatically deleted after you perform the following operations to delete the virtual gateway and its virtual interfaces.</p>
|
||||
</div></div>
|
||||
</p></li><li id="er_01_0073__li13291116195810"><span>Locate the target virtual gateway attachment and click the attached resource.</span><p><p id="er_01_0073__p4291116155817">Example: vgw-demo</p>
|
||||
@ -24,7 +24,7 @@
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="er_01_0022.html">Deleting an Attachment</a></div>
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="er_01_0168.html">Virtual Gateway Attachments</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
|
@ -4,7 +4,7 @@
|
||||
<div id="body0000001189461326"><div class="section" id="er_01_0092__section741934817414"><h4 class="sectiontitle"><strong id="er_01_0092__en-us_topic_0030598499_b842352706143619">Scenarios</strong></h4><p id="er_01_0092__en-us_topic_0030598499_p333055219577">After CTS is enabled, CTS starts recording operations on cloud resources. The CTS management console stores the last seven days of operation records.</p>
|
||||
<p id="er_01_0092__en-us_topic_0030598499_p3008599195238">This section describes how to query or export the last seven days of operation records on the management console.</p>
|
||||
</div>
|
||||
<div class="section" id="er_01_0092__section19713162125313"><h4 class="sectiontitle">Procedure</h4><ol id="er_01_0092__ol230112518524"><li id="er_01_0092__li1426075112165"><span>Log in to the management console.</span></li><li id="er_01_0092__li18272154101917"><span>Click <span><img id="er_01_0092__er_01_0064_en-us_topic_0014250631_en-us_topic_0014250631_image1733511156361" src="en-us_image_0000001190483836.png"></span> in the upper left corner and select the desired region and project.</span></li><li id="er_01_0092__li35053303017"><span>Click <strong id="er_01_0092__b58299302419">Service List</strong>. Under <strong id="er_01_0092__b1282915319246">Management & Governance</strong>, click <strong id="er_01_0092__b17829734249">Cloud Trace Service</strong>.</span><p><p id="er_01_0092__p822153210017">The <strong id="er_01_0092__b135559612416">Cloud Trace Service</strong> console is displayed.</p>
|
||||
<div class="section" id="er_01_0092__section19713162125313"><h4 class="sectiontitle">Procedure</h4><ol id="er_01_0092__ol230112518524"><li id="er_01_0092__li1426075112165"><span>Log in to the management console.</span></li><li id="er_01_0092__li18272154101917"><span>Click <span><img id="er_01_0092__er_01_0064_en-us_topic_0014250631_en-us_topic_0014250631_image1733511156361" src="en-us_image_0000001190483836.png"></span> in the upper left corner and select the desired region and project.</span></li><li id="er_01_0092__li35053303017"><span>Click <strong id="er_01_0092__b58299302419">Service List</strong>. Under <strong id="er_01_0092__b1282915319246">Management and Deployment</strong>, click <strong id="er_01_0092__b17829734249">Cloud Trace Service</strong>.</span><p><p id="er_01_0092__p822153210017">The <strong id="er_01_0092__b135559612416">Cloud Trace Service</strong> console is displayed.</p>
|
||||
</p></li><li id="er_01_0092__li1833018461016"><span>In the navigation pane on the left, choose <strong id="er_01_0092__b8465175712419">Trace List</strong>.</span><p><p id="er_01_0092__p163031850602">The <strong id="er_01_0092__b84235270610231">Trace List</strong> page is displayed.</p>
|
||||
</p></li><li id="er_01_0092__li1027454306"><span>Specify filters as needed.</span><p><p id="er_01_0092__p88062056709">The following filters are available:</p>
|
||||
<ul class="subitemlist" id="er_01_0092__ul653285112916"><li id="er_01_0092__li1772242117539"><strong id="er_01_0092__b4749449111519">Trace Source</strong>, <strong id="er_01_0092__b7749349191512">Resource Type</strong>, and <strong id="er_01_0092__b11749204912150">Search By</strong><ul id="er_01_0092__ul929919354150"><li id="er_01_0092__li091073331520">If you select <strong id="er_01_0092__b547154313301">Trace name</strong> for <strong id="er_01_0092__b194720436308">Search By</strong>, select a trace name.</li><li id="er_01_0092__li1091173319154">If you select <strong id="er_01_0092__b164900543312">Resource ID</strong> for <strong id="er_01_0092__b3490175410315">Search By</strong>, select or enter a resource ID.</li><li id="er_01_0092__li7911103310155">If you select <strong id="er_01_0092__b964418427321">Resource name</strong> for <strong id="er_01_0092__b16644042163216">Search By</strong>, select or enter a resource name.</li></ul>
|
||||
|
@ -61,7 +61,7 @@
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="er_01_0095__row1287310271812"><td class="cellrowborder" valign="top" headers="mcps1.3.2.2.2.2.4.1.1 "><p id="er_01_0095__p1268930132814">Adding attachments to an enterprise router</p>
|
||||
<p id="er_01_0095__p178385615318"><a href="er_01_0070.html">Adding VPC Attachments to an Enterprise Router</a></p>
|
||||
<p id="er_01_0095__p178385615318"><a href="er_01_0070.html">Creating a VPC Attachment</a></p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" headers="mcps1.3.2.2.2.2.4.1.2 "><p id="er_01_0095__p97371563510">Other users:</p>
|
||||
<ul id="er_01_0095__ul2023833516"><li id="er_01_0095__li11966212411">Can only create VPC attachments.</li><li id="er_01_0095__li1258153517">Can create attachments to the shared enterprise router only after the owner account accepts the attachment requests.<p id="er_01_0095__p129518228294"><a name="er_01_0095__li1258153517"></a><a name="li1258153517"></a>If <strong id="er_01_0095__b15766182133618">Auto Accept Shared Attachments</strong> is enabled, a request from a user for creating an attachment will be automatically accepted.</p>
|
||||
@ -69,7 +69,7 @@
|
||||
<p id="er_01_0095__p12962102310330">For details about the process for creating an attachment for an enterprise router in another account, see <a href="#er_01_0095__section169164232367">Sharing an Enterprise Router with Other Users</a>.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="er_01_0095__row198736271584"><td class="cellrowborder" valign="top" headers="mcps1.3.2.2.2.2.4.1.1 "><p id="er_01_0095__p487319271281"><a href="er_01_0021.html">Viewing Details About an Attachment</a></p>
|
||||
<tr id="er_01_0095__row198736271584"><td class="cellrowborder" valign="top" headers="mcps1.3.2.2.2.2.4.1.1 "><p id="er_01_0095__p487319271281"><a href="er_01_0021.html">Viewing an Attachment</a></p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" headers="mcps1.3.2.2.2.2.4.1.2 "><p id="er_01_0095__p1925364218">Other users:</p>
|
||||
<p id="er_01_0095__p96325461415">Cannot view the tags added of their attachments.</p>
|
||||
@ -95,7 +95,7 @@
|
||||
<div class="section" id="er_01_0095__section169164232367"><a name="er_01_0095__section169164232367"></a><a name="section169164232367"></a><h4 class="sectiontitle">Sharing an Enterprise Router with Other Users</h4><div class="p" id="er_01_0095__p105785114337">As the owner, you can share your enterprise router with other users. These other users can create attachments for your enterprise router.<ul id="er_01_0095__ul664122183418"><li id="er_01_0095__li18641224348">If <strong id="er_01_0095__b1221718531374">Auto Accept Shared Attachments</strong> is not enabled on your enterprise router, you must accept the attachment creation requests from other users.<div class="fignone" id="er_01_0095__fig10285152624918"><span class="figcap"><b>Figure 2 </b>Accepting or rejecting attachment creation requests</span><br><span><img class="eddx" id="er_01_0095__image20285162644919" src="en-us_image_0000001213710098.png"></span></div>
|
||||
<p id="er_01_0095__p76474917488"></p>
|
||||
|
||||
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="er_01_0095__table16962125143812" frame="border" border="1" rules="all"><caption><b>Table 3 </b>Process description</caption><thead align="left"><tr id="er_01_0095__row1962195183814"><th align="left" class="cellrowborder" valign="top" width="7.91%" id="mcps1.3.3.2.1.1.4.2.5.1.1"><p id="er_01_0095__p174322461427">No.</p>
|
||||
<div class="tablenoborder"><a name="er_01_0095__table16962125143812"></a><a name="table16962125143812"></a><table cellpadding="4" cellspacing="0" summary="" id="er_01_0095__table16962125143812" frame="border" border="1" rules="all"><caption><b>Table 3 </b>Process description</caption><thead align="left"><tr id="er_01_0095__row1962195183814"><th align="left" class="cellrowborder" valign="top" width="7.91%" id="mcps1.3.3.2.1.1.4.2.5.1.1"><p id="er_01_0095__p174322461427">No.</p>
|
||||
</th>
|
||||
<th align="left" class="cellrowborder" valign="top" width="24.990000000000002%" id="mcps1.3.3.2.1.1.4.2.5.1.2"><p id="er_01_0095__p1396316517382">Step</p>
|
||||
</th>
|
||||
@ -116,28 +116,22 @@
|
||||
</tr>
|
||||
<tr id="er_01_0095__row396313512383"><td class="cellrowborder" valign="top" width="7.91%" headers="mcps1.3.3.2.1.1.4.2.5.1.1 "><p id="er_01_0095__p19432184613421">2</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="24.990000000000002%" headers="mcps1.3.3.2.1.1.4.2.5.1.2 "><p id="er_01_0095__p16915195515411"><a href="er_01_0070.html">Adding VPC Attachments to an Enterprise Router</a></p>
|
||||
<td class="cellrowborder" valign="top" width="24.990000000000002%" headers="mcps1.3.3.2.1.1.4.2.5.1.2 "><p id="er_01_0095__p16915195515411"><a href="er_01_0070.html">Creating a VPC Attachment</a></p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="11.16%" headers="mcps1.3.3.2.1.1.4.2.5.1.3 "><p id="er_01_0095__p1273141354317">User</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="55.94%" headers="mcps1.3.3.2.1.1.4.2.5.1.4 "><p id="er_01_0095__p3610432184115">The user creates an attachment to the shared enterprise router. The attachment will be in the <strong id="er_01_0095__b1493310492563">Pending acceptance</strong> state because <strong id="er_01_0095__b467693716416">Auto Accept Shared Attachments</strong> is disabled on the enterprise router.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="er_01_0095__row096345173820"><td class="cellrowborder" rowspan="2" valign="top" width="7.91%" headers="mcps1.3.3.2.1.1.4.2.5.1.1 "><p id="er_01_0095__p144321346184218">3</p>
|
||||
<tr id="er_01_0095__row096345173820"><td class="cellrowborder" valign="top" width="7.91%" headers="mcps1.3.3.2.1.1.4.2.5.1.1 "><p id="er_01_0095__p144321346184218">3</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="24.990000000000002%" headers="mcps1.3.3.2.1.1.4.2.5.1.2 "><p id="er_01_0095__p13963205193817"><a href="er_01_0099.html">Accepting an Attachment Request</a></p>
|
||||
<td class="cellrowborder" valign="top" width="24.990000000000002%" headers="mcps1.3.3.2.1.1.4.2.5.1.2 "><ul id="er_01_0095__ul46939172143"><li id="er_01_0095__li6693617131411"><a href="er_01_0099.html">Accepting an Attachment Request</a></li><li id="er_01_0095__li46941417131410"><a href="er_01_0100.html">Rejecting an Attachment Request</a></li></ul>
|
||||
</td>
|
||||
<td class="cellrowborder" rowspan="2" valign="top" width="11.16%" headers="mcps1.3.3.2.1.1.4.2.5.1.3 "><p id="er_01_0095__p6740137434">Owner</p>
|
||||
<p id="er_01_0095__p4867106174314"></p>
|
||||
<td class="cellrowborder" valign="top" width="11.16%" headers="mcps1.3.3.2.1.1.4.2.5.1.3 "><p id="er_01_0095__p6740137434">Owner</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="55.94%" headers="mcps1.3.3.2.1.1.4.2.5.1.4 "><div class="p" id="er_01_0095__p7963356389">The owner accepts the attachment request. The attachment status changes from <strong id="er_01_0095__b36371820122815">Pending acceptance</strong> to <strong id="er_01_0095__b1573252332813">Creating</strong>.<ul id="er_01_0095__ul16239181310593"><li id="er_01_0095__li1723901313590">When the attachment status changes to <strong id="er_01_0095__b6227165572810">Normal</strong>, the attachment is successfully created.</li><li id="er_01_0095__li223916139596">When the attachment status changes to <strong id="er_01_0095__b63754163292">Failed</strong>, the attachment fails to be created. Contact customer service.</li></ul>
|
||||
</div>
|
||||
<td class="cellrowborder" valign="top" width="55.94%" headers="mcps1.3.3.2.1.1.4.2.5.1.4 "><ul id="er_01_0095__ul1710812021416"><li id="er_01_0095__li81081020111414">The owner accepts the attachment request. The attachment status changes from <strong id="er_01_0095__b36371820122815">Pending acceptance</strong> to <strong id="er_01_0095__b1573252332813">Creating</strong>.<ul id="er_01_0095__ul16239181310593"><li id="er_01_0095__li1723901313590">When the attachment status changes to <strong id="er_01_0095__b6227165572810">Normal</strong>, the attachment is successfully created.</li><li id="er_01_0095__li223916139596">When the attachment status changes to <strong id="er_01_0095__b63754163292">Failed</strong>, the attachment fails to be created. Contact customer service.</li></ul>
|
||||
<p id="er_01_0095__p1208163784215">After an attachment is created, you can perform <a href="er_01_0070.html#er_01_0070__section582517444316">Follow-up Procedure</a>.</p>
|
||||
</td>
|
||||
</tr>
|
||||
<tr id="er_01_0095__row184816914534"><td class="cellrowborder" valign="top" headers="mcps1.3.3.2.1.1.4.2.5.1.1 "><p id="er_01_0095__p134979105315"><a href="er_01_0100.html">Rejecting an Attachment Request</a></p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" headers="mcps1.3.3.2.1.1.4.2.5.1.2 "><p id="er_01_0095__p31023311986">The owner can also reject the attachment request. If the owner rejects the request, the attachment status changes from <strong id="er_01_0095__b17636195418409">Pending acceptance</strong> to <strong id="er_01_0095__b46373512403">Rejected</strong>, and the attachment fails to be created. If this happens, contact the owner.</p>
|
||||
</li><li id="er_01_0095__li109193041419">The owner can also reject the attachment request. If the owner rejects the request, the attachment status changes from <strong id="er_01_0095__b17636195418409">Pending acceptance</strong> to <strong id="er_01_0095__b46373512403">Rejected</strong>, and the attachment fails to be created. If this happens, contact the owner.</li></ul>
|
||||
</td>
|
||||
</tr>
|
||||
</tbody>
|
||||
@ -166,7 +160,7 @@
|
||||
</tr>
|
||||
<tr id="er_01_0095__row6826418115018"><td class="cellrowborder" valign="top" width="7.91%" headers="mcps1.3.3.2.1.2.3.2.5.1.1 "><p id="er_01_0095__p5826121817509">2</p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="24.990000000000002%" headers="mcps1.3.3.2.1.2.3.2.5.1.2 "><p id="er_01_0095__p145813507517"><a href="er_01_0070.html">Adding VPC Attachments to an Enterprise Router</a></p>
|
||||
<td class="cellrowborder" valign="top" width="24.990000000000002%" headers="mcps1.3.3.2.1.2.3.2.5.1.2 "><p id="er_01_0095__p145813507517"><a href="er_01_0070.html">Creating a VPC Attachment</a></p>
|
||||
</td>
|
||||
<td class="cellrowborder" valign="top" width="11.16%" headers="mcps1.3.3.2.1.2.3.2.5.1.3 "><p id="er_01_0095__p19826171875012">User account</p>
|
||||
</td>
|
||||
|
@ -1,7 +1,7 @@
|
||||
<a name="er_01_0111"></a><a name="er_01_0111"></a>
|
||||
|
||||
<h1 class="topictitle1">Disabling a Flow Log</h1>
|
||||
<div id="body0000001411069857"><div class="section" id="er_01_0111__section3349201118719"><h4 class="sectiontitle">Scenarios</h4><p id="er_01_0111__p256933413116">This section describes how to disable a flow log. After a flow log is disabled, the enterprise router will not send log information to LTS.</p>
|
||||
<div id="body0000001411069857"><div class="section" id="er_01_0111__section3349201118719"><h4 class="sectiontitle">Scenarios</h4><p id="er_01_0111__p256933413116">If flow logging is disabled, no flow logs will be collected in the next log collection period. Collected flow logs can still be viewed.</p>
|
||||
</div>
|
||||
<div class="section" id="er_01_0111__section1915523172312"><h4 class="sectiontitle">Procedure</h4><ol id="er_01_0111__ol5288104816346"><li id="er_01_0111__li197361536533"><span>Log in to the management console.</span></li><li id="er_01_0111__li18272154101917"><span>Click <span><img id="er_01_0111__er_01_0064_en-us_topic_0014250631_en-us_topic_0014250631_image1733511156361" src="en-us_image_0000001190483836.png"></span> in the upper left corner and select the desired region and project.</span></li><li id="er_01_0111__li13278035192013"><span>Click <strong id="er_01_0111__er_01_0064_b0877172561410">Service List</strong> and choose <strong id="er_01_0111__er_01_0064_b38631530121411">Networking</strong> > <strong id="er_01_0111__er_01_0064_b1949823361416">Enterprise Router</strong>.</span><p><p id="er_01_0111__er_01_0064_p131231735172115">The <strong id="er_01_0111__er_01_0064_b131401444138">Enterprise Router</strong> homepage is displayed.</p>
|
||||
</p></li><li id="er_01_0111__li6322510553"><span>Search for the target enterprise router by name.</span><p><div class="fignone" id="er_01_0111__fig2034013312252"><span class="figcap"><b>Figure 1 </b>Searching for an enterprise router</span><br><span><img id="er_01_0111__er_01_0016_image1553618920257" src="en-us_image_0000001674900098.png"></span></div>
|
||||
|
@ -1,7 +1,7 @@
|
||||
<a name="er_01_0112"></a><a name="er_01_0112"></a>
|
||||
|
||||
<h1 class="topictitle1">Enabling a Flow Log</h1>
|
||||
<div id="body0000001360989546"><div class="section" id="er_01_0112__section3349201118719"><h4 class="sectiontitle">Scenarios</h4><p id="er_01_0112__p256933413116">This section describes how to enable a flow log. After a flow log is enabled, the enterprise router will send log information to LTS.</p>
|
||||
<div id="body0000001360989546"><div class="section" id="er_01_0112__section3349201118719"><h4 class="sectiontitle">Scenarios</h4><p id="er_01_0112__p256933413116">If flow logging is enabled, flow logs will be collected from the next log collection period.</p>
|
||||
</div>
|
||||
<div class="section" id="er_01_0112__section1915523172312"><h4 class="sectiontitle">Procedure</h4><ol id="er_01_0112__ol5288104816346"><li id="er_01_0112__li197361536533"><span>Log in to the management console.</span></li><li id="er_01_0112__li18272154101917"><span>Click <span><img id="er_01_0112__er_01_0064_en-us_topic_0014250631_en-us_topic_0014250631_image1733511156361" src="en-us_image_0000001190483836.png"></span> in the upper left corner and select the desired region and project.</span></li><li id="er_01_0112__li13278035192013"><span>Click <strong id="er_01_0112__er_01_0064_b0877172561410">Service List</strong> and choose <strong id="er_01_0112__er_01_0064_b38631530121411">Networking</strong> > <strong id="er_01_0112__er_01_0064_b1949823361416">Enterprise Router</strong>.</span><p><p id="er_01_0112__er_01_0064_p131231735172115">The <strong id="er_01_0112__er_01_0064_b131401444138">Enterprise Router</strong> homepage is displayed.</p>
|
||||
</p></li><li id="er_01_0112__li6322510553"><span>Search for the target enterprise router by name.</span><p><div class="fignone" id="er_01_0112__fig2034013312252"><span class="figcap"><b>Figure 1 </b>Searching for an enterprise router</span><br><span><img id="er_01_0112__er_01_0016_image1553618920257" src="en-us_image_0000001674900098.png"></span></div>
|
||||
|
@ -126,7 +126,7 @@
|
||||
</table>
|
||||
</div>
|
||||
</div>
|
||||
<ol id="er_01_0122__ol121313101995"><li id="er_01_0122__li16131141018917"><span>Create a transit VPC, attach it to the enterprise router, and associate the transit VPC with the default route table of the enterprise router.</span><p><ul id="er_01_0122__ul193100200515"><li id="er_01_0122__li153101120157">The subnet of the transit VPC cannot overlap with that of the service VPC. Otherwise, the VPC peering connection to be created in <a href="#er_01_0122__li14564823993">2</a> cannot take effect.</li><li id="er_01_0122__li857815211918">The transit VPC cannot have the following situations. Otherwise, the default route (0.0.0.0/0) to be configured in <a href="#er_01_0122__li92642018194217">3</a> cannot forward traffic.<ul id="er_01_0122__ul5520529699"><li id="er_01_0122__er_01_0129_li17652438103917">An ECS in the VPC has an EIP bound.</li><li id="er_01_0122__er_01_0129_li0652153843918">The VPC is being used by ELB, NAT Gateway, VPC Endpoint, or DCS.</li></ul>
|
||||
<ol id="er_01_0122__ol121313101995"><li id="er_01_0122__li16131141018917"><span>Create a transit VPC, attach it to the enterprise router, and associate the transit VPC with the default route table of the enterprise router.</span><p><ul id="er_01_0122__ul193100200515"><li id="er_01_0122__li153101120157">The subnet of the transit VPC cannot overlap with that of the service VPC, or the VPC peering connection to be created in <a href="#er_01_0122__li14564823993">2</a> cannot take effect.</li><li id="er_01_0122__li857815211918">The transit VPC cannot have the following situations. Otherwise, the default route (0.0.0.0/0) to be configured in <a href="#er_01_0122__li92642018194217">3</a> cannot forward traffic.<ul id="er_01_0122__ul5520529699"><li id="er_01_0122__er_01_0129_li17652438103917">An ECS in the VPC has an EIP bound.</li><li id="er_01_0122__er_01_0129_li0652153843918">The VPC is being used by ELB, NAT Gateway, VPC Endpoint, or DCS.</li></ul>
|
||||
</li></ul>
|
||||
</p></li><li id="er_01_0122__li14564823993"><a name="er_01_0122__li14564823993"></a><a name="li14564823993"></a><span>Create a VPC peering connection between the service VPC and transit VPC.</span><p><div class="notice" id="er_01_0122__note1544825513456"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="er_01_0122__p3448185517457">You do not need to add routes for the VPC peering connection. For details about the routes to be added, see <a href="#er_01_0122__li92642018194217">3</a>.</p>
|
||||
</div></div>
|
||||
|
@ -2,7 +2,7 @@
|
||||
|
||||
<h1 class="topictitle1">How Do I Enable Two Attachments of an Enterprise Router to Learn Routes from Each Other?</h1>
|
||||
<div id="body0000001496365977"><p id="er_01_0123__p19941110172418">If you want two attachments of an enterprise router to learn routes from each other, the router and each attachment must have a unique ASN. In this way, the enterprise router advertises the learned route information between the attachments.</p>
|
||||
<div class="p" id="er_01_0123__p141572513497">If you want two virtual gateways attached to the same enterprise router to learn routes from each other, their ASNs can be as follows:<ul id="er_01_0123__ul121577513493"><li id="er_01_0123__li71574516496">Enterprise router: 64512</li><li id="er_01_0123__li5158751174920">Virtual gateway attachment A: 64513 (BGP ASN of virtual gateway A)</li><li id="er_01_0123__li1335151513514">Virtual gateway attachment B: 64515 (BGP ASN of virtual gateway B)</li></ul>
|
||||
<div class="p" id="er_01_0123__p141572513497">If you want two virtual gateways attached to the same enterprise router to learn routes from each other, their ASNs can be as follows:<ul id="er_01_0123__ul121577513493"><li id="er_01_0123__li71574516496">Enterprise router: 64800</li><li id="er_01_0123__li5158751174920">Virtual gateway attachment A: 64513 (BGP ASN of virtual gateway A)</li><li id="er_01_0123__li1335151513514">Virtual gateway attachment B: 64515 (BGP ASN of virtual gateway B)</li></ul>
|
||||
</div>
|
||||
<div class="note" id="er_01_0123__note181322582618"><img src="public_sys-resources/note_3.0-en-us.png"><span class="notetitle"> </span><div class="notebody"><p id="er_01_0123__p91327572612">VPC attachments do not support route learning.</p>
|
||||
</div></div>
|
||||
|
@ -1,12 +1,16 @@
|
||||
<a name="er_01_0022"></a><a name="er_01_0022"></a>
|
||||
<a name="er_01_0167"></a><a name="er_01_0167"></a>
|
||||
|
||||
|
||||
<h1 class="topictitle1">VPC Attachments</h1>
|
||||
|
||||
<div id="body0000001834973921"><p id="er_01_0167__p8060118"></p>
|
||||
</div>
|
||||
|
||||
<h1 class="topictitle1">Deleting an Attachment</h1>
|
||||
<div id="body0000001181424563"></div>
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="er_01_0072.html">Deleting a VPC Attachment</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="er_01_0070.html">Creating a VPC Attachment</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="er_01_0073.html">Deleting a Virtual Gateway Attachment</a></strong><br>
|
||||
<li class="ulchildlink"><strong><a href="er_01_0072.html">Deleting a VPC Attachment</a></strong><br>
|
||||
</li>
|
||||
</ul>
|
||||
|
21
docs/er/umn/er_01_0168.html
Normal file
21
docs/er/umn/er_01_0168.html
Normal file
@ -0,0 +1,21 @@
|
||||
<a name="er_01_0168"></a><a name="er_01_0168"></a>
|
||||
|
||||
|
||||
<h1 class="topictitle1">Virtual Gateway Attachments</h1>
|
||||
|
||||
<div id="body0000001788724212"><p id="er_01_0168__p8060118"></p>
|
||||
</div>
|
||||
|
||||
<div>
|
||||
<ul class="ullinks">
|
||||
<li class="ulchildlink"><strong><a href="er_01_0169.html">Creating a Virtual Gateway Attachment</a></strong><br>
|
||||
</li>
|
||||
<li class="ulchildlink"><strong><a href="er_01_0073.html">Deleting a Virtual Gateway Attachment</a></strong><br>
|
||||
</li>
|
||||
</ul>
|
||||
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="er_01_0018.html">Attachments</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
14
docs/er/umn/er_01_0169.html
Normal file
14
docs/er/umn/er_01_0169.html
Normal file
@ -0,0 +1,14 @@
|
||||
<a name="er_01_0169"></a><a name="er_01_0169"></a>
|
||||
|
||||
<h1 class="topictitle1">Creating a Virtual Gateway Attachment</h1>
|
||||
<div id="body0000001788929482"><div class="section" id="er_01_0169__section123961658161"><h4 class="sectiontitle">Scenarios</h4><p id="er_01_0169__p74879521162">Attach a Direct Connect virtual gateway to an enterprise router to set up a hybrid cloud network using Direct Connect and Enterprise Router.</p>
|
||||
</div>
|
||||
<div class="section" id="er_01_0169__section1849592314912"><h4 class="sectiontitle">Procedure</h4><p id="er_01_0169__p2051892151">Attach a virtual gateway to an enterprise router. For details, see <a href="https://docs.otc.t-systems.com/direct-connect/umn/getting_started/enabling_direct_connect/connecting_your_on-premises_data_center_to_the_cloud.html" target="_blank" rel="noopener noreferrer">Connecting Your On-Premises Data Center to the Cloud</a>.</p>
|
||||
</div>
|
||||
</div>
|
||||
<div>
|
||||
<div class="familylinks">
|
||||
<div class="parentlink"><strong>Parent topic:</strong> <a href="er_01_0168.html">Virtual Gateway Attachments</a></div>
|
||||
</div>
|
||||
</div>
|
||||
|
Loading…
x
Reference in New Issue
Block a user