ER UMN 20240910 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:
Qin Ying, Fan 2024-09-18 11:58:39 +00:00 committed by zuul
parent ec0b45029f
commit 4aac5cfe88
8 changed files with 391 additions and 298 deletions

File diff suppressed because it is too large Load Diff

File diff suppressed because it is too large Load Diff

View File

@ -8,7 +8,19 @@
</th> </th>
</tr> </tr>
</thead> </thead>
<tbody><tr id="UgChangeHistory__row113721429165218"><td class="cellrowborder" valign="top" width="34%" headers="mcps1.3.1.1.3.1.1 "><p id="UgChangeHistory__p9372162945218">2024-08-31</p> <tbody><tr id="UgChangeHistory__row725819203541"><td class="cellrowborder" valign="top" width="34%" headers="mcps1.3.1.1.3.1.1 "><p id="UgChangeHistory__p725932018545">2024-09-18</p>
</td>
<td class="cellrowborder" valign="top" width="66%" headers="mcps1.3.1.1.3.1.2 "><p id="UgChangeHistory__p14447236105415">Modified the following content:</p>
<p id="UgChangeHistory__p1487803025415">Modified the figure name of scheme 1 in <a href="er_01_0129.html">Selecting a Networking Scheme</a>.</p>
</td>
</tr>
<tr id="UgChangeHistory__row20212719112216"><td class="cellrowborder" valign="top" width="34%" headers="mcps1.3.1.1.3.1.1 "><p id="UgChangeHistory__p192131319102212">2024-09-10</p>
</td>
<td class="cellrowborder" valign="top" width="66%" headers="mcps1.3.1.1.3.1.2 "><p id="UgChangeHistory__p94521127142213">Modified the following content:</p>
<p id="UgChangeHistory__p1145210279227">Added <a href="er_01_0129.html">Selecting a Networking Scheme</a>.</p>
</td>
</tr>
<tr id="UgChangeHistory__row113721429165218"><td class="cellrowborder" valign="top" width="34%" headers="mcps1.3.1.1.3.1.1 "><p id="UgChangeHistory__p9372162945218">2024-08-31</p>
</td> </td>
<td class="cellrowborder" valign="top" width="66%" headers="mcps1.3.1.1.3.1.2 "><p id="UgChangeHistory__p3607104211526">Modified the following content:</p> <td class="cellrowborder" valign="top" width="66%" headers="mcps1.3.1.1.3.1.2 "><p id="UgChangeHistory__p3607104211526">Modified the following content:</p>
<p id="UgChangeHistory__p178086281530">Deleted the description that flow logs support VPN in <a href="er_01_0005.html">Functions</a>, <a href="er_01_0108.html">Flow Log Overview</a>, and <a href="er_01_0109.html">Creating a Flow Log</a>.</p> <p id="UgChangeHistory__p178086281530">Deleted the description that flow logs support VPN in <a href="er_01_0005.html">Functions</a>, <a href="er_01_0108.html">Flow Log Overview</a>, and <a href="er_01_0109.html">Creating a Flow Log</a>.</p>

Binary file not shown.

After

Width:  |  Height:  |  Size: 34 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 49 KiB

View File

@ -8,6 +8,8 @@
<div> <div>
<ul class="ullinks"> <ul class="ullinks">
<li class="ulchildlink"><strong><a href="er_01_0129.html">Selecting a Networking Scheme</a></strong><br>
</li>
<li class="ulchildlink"><strong><a href="er_01_0061.html">Using an Enterprise Router to Enable Communications Between VPCs in the Same Region</a></strong><br> <li class="ulchildlink"><strong><a href="er_01_0061.html">Using an Enterprise Router to Enable Communications Between VPCs in the Same Region</a></strong><br>
</li> </li>
</ul> </ul>

View File

@ -1,7 +1,7 @@
<a name="er_01_0108"></a><a name="er_01_0108"></a> <a name="er_01_0108"></a><a name="er_01_0108"></a>
<h1 class="topictitle1">Flow Log Overview</h1> <h1 class="topictitle1">Flow Log Overview</h1>
<div id="body0000001360830006"><div class="section" id="er_01_0108__section7844839143310"><h4 class="sectiontitle">What Is a Flow Log?</h4><p id="er_01_0108__p115211435163713">Log Tank Service (LTS) can record flow logs for enterprise routers. A flow log records traffic of attachments on enterprise routers in real time. These logs allow you to monitor the network traffic of attachments and analyze network attacks, improving your O&amp;M efficiency.</p> <div id="body0000001360830006"><div class="section" id="er_01_0108__section7844839143310"><h4 class="sectiontitle">What Is a Flow Log?</h4><p id="er_01_0108__p115211435163713">Log Tank Service (LTS) can record flow logs for enterprise routers. A flow log records traffic of attachments on enterprise routers in real time. These logs allow you to monitor the network traffic of attachments and analyze network attacks, improving the O&amp;M efficiency.</p>
<div class="p" id="er_01_0108__p89092664318">Flow logs can capture traffic of the following types of attachments:<ul id="er_01_0108__ul960733916551"><li id="er_01_0108__li954813791613">VPC</li><li id="er_01_0108__li6607113918550">Virtual gateway</li></ul> <div class="p" id="er_01_0108__p89092664318">Flow logs can capture traffic of the following types of attachments:<ul id="er_01_0108__ul960733916551"><li id="er_01_0108__li954813791613">VPC</li><li id="er_01_0108__li6607113918550">Virtual gateway</li></ul>
</div> </div>
</div> </div>

View File

@ -0,0 +1,52 @@
<a name="er_01_0129"></a><a name="er_01_0129"></a>
<h1 class="topictitle1">Selecting a Networking Scheme</h1>
<div id="body0000001604237205"><div class="p" id="er_01_0129__p19227015191120">You can use enterprise routers to build a central network and to simplify the network architecture. There are two typical schemes to use Enterprise Router together with Direct Connect to allow an on-premises data center to access multiple VPCs.<div class="fignone" id="er_01_0129__fig16662957112716"><a name="er_01_0129__fig16662957112716"></a><a name="fig16662957112716"></a><span class="figcap"><b>Figure 1 </b>Networking for allowing an on-premises data center to access two service VPCs directly (scheme 1)</span><br><span><img class="eddx" id="er_01_0129__en-us_topic_0000001135431190_image1666295742715" src="en-us_image_0000001557627546.png"></span></div>
<div class="fignone" id="er_01_0129__fig536751734919"><a name="er_01_0129__fig536751734919"></a><a name="fig536751734919"></a><span class="figcap"><b>Figure 2 </b>Networking for allowing an on-premises data center to access two service VPCs over a transit VPC (scheme 2)</span><br><span><img class="eddx" id="er_01_0129__image5799551196" src="en-us_image_0000001607947069.png"></span></div>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="er_01_0129__table1627218240236" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Comparison between the two schemes</caption><thead align="left"><tr id="er_01_0129__row1927232416231"><th align="left" class="cellrowborder" valign="top" width="8.871572006593738%" id="mcps1.3.1.3.2.5.1.1"><p id="er_01_0129__p15884143417476">Scheme</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="34.4822418702233%" id="mcps1.3.1.3.2.5.1.2"><p id="er_01_0129__p22726240239">Networking Architecture</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="33.47819571407163%" id="mcps1.3.1.3.2.5.1.3"><p id="er_01_0129__p142721244232">Network Path Description</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="23.167990409111347%" id="mcps1.3.1.3.2.5.1.4"><p id="er_01_0129__p129341257145017">Remarks</p>
</th>
</tr>
</thead>
<tbody><tr id="er_01_0129__row827212245239"><td class="cellrowborder" valign="top" width="8.871572006593738%" headers="mcps1.3.1.3.2.5.1.1 "><p id="er_01_0129__p1088423424710">Scheme 1</p>
</td>
<td class="cellrowborder" valign="top" width="34.4822418702233%" headers="mcps1.3.1.3.2.5.1.2 "><p id="er_01_0129__p202723249233">In <a href="#er_01_0129__fig16662957112716">Figure 1</a>:</p>
<p id="er_01_0129__p4272112432315">Two service VPCs (VPC-A and VPC-B) and the Direct Connect virtual gateway are attached to an enterprise router.</p>
</td>
<td class="cellrowborder" valign="top" width="33.47819571407163%" headers="mcps1.3.1.3.2.5.1.3 "><ul id="er_01_0129__ul0635592294"><li id="er_01_0129__li22796495291">The enterprise router enables the two VPCs to communicate with each other.</li><li id="er_01_0129__li7133131942915">Direct Connect enables the on-premises data center to access the cloud, and the enterprise router connects the on-premises data center to both VPCs.</li></ul>
</td>
<td class="cellrowborder" rowspan="2" valign="top" width="23.167990409111347%" headers="mcps1.3.1.3.2.5.1.4 "><p id="er_01_0129__p1382118311553">For details, see <a href="#er_01_0129__section125661717185015">How Do I Select a Networking Scheme?</a></p>
</td>
</tr>
<tr id="er_01_0129__row42721124142314"><td class="cellrowborder" valign="top" headers="mcps1.3.1.3.2.5.1.1 "><p id="er_01_0129__p18884203414475">Scheme 2</p>
</td>
<td class="cellrowborder" valign="top" headers="mcps1.3.1.3.2.5.1.2 "><p id="er_01_0129__p17226482614">In <a href="#er_01_0129__fig536751734919">Figure 2</a>:</p>
<p id="er_01_0129__p1527292452314">The two service VPCs (VPC-A and VPC-B) are not attached to the enterprise router. Instead, a transit VPC (VPC-Transit) is used. The transit VPC and the Direct Connect virtual gateway are attached to the enterprise router.</p>
</td>
<td class="cellrowborder" valign="top" headers="mcps1.3.1.3.2.5.1.3 "><ul id="er_01_0129__ul839811401338"><li id="er_01_0129__li5398174083320"> Each service VPC is connected to the transit VPC over a VPC peering connection.</li><li id="er_01_0129__li11956244103315">Direct Connect enables the on-premises data center to access the cloud, and the enterprise router connects the on-premises data center to the two service VPCs.</li></ul>
</td>
</tr>
</tbody>
</table>
</div>
</div>
<div class="section" id="er_01_0129__section125661717185015"><a name="er_01_0129__section125661717185015"></a><a name="section125661717185015"></a><h4 class="sectiontitle">How Do I Select a Networking Scheme?</h4><div class="p" id="er_01_0129__p51791713596">In scheme 1, the service VPCs are directly attached to the enterprise router. In scheme 2, a transit VPC is used and attached to the enterprise router. Each service VPC is connected to the transit VPC over a VPC peering connection. Compared with scheme 1, scheme 2 costs less and eliminates some constraints, as detailed below:<ul id="er_01_0129__ul18491182543918"><li id="er_01_0129__li36527386391">Scheme 2 frees you from the following constraints that scheme 1 has on attaching service VPCs to an enterprise router:<ul id="er_01_0129__ul265213823912"><li id="er_01_0129__li96521538163917">If a service VPC is used by ELB, VPC Endpoint, NAT Gateway (private NAT gateways), or DCS, contact customer service to confirm the service compatibility and preferentially use a transit VPC for networking.</li><li id="er_01_0129__li8652738113919">Traffic cannot be forwarded from a VPC to the enterprise router if you set the destination of a route in the VPC route table to 0.0.0.0/0 and:<ul id="er_01_0129__ul465283814396"><li id="er_01_0129__li17652438103917">An ECS in the VPC has an EIP bound.</li><li id="er_01_0129__li0652153843918">The VPC is being used by ELB (either dedicated or shared load balancers), NAT Gateway, VPC Endpoint, and DCS.</li></ul>
</li></ul>
</li></ul>
</div>
</div>
<div class="notice" id="er_01_0129__note1575518598413"><span class="noticetitle"><img src="public_sys-resources/notice_3.0-en-us.png"> </span><div class="noticebody"><p id="er_01_0129__p18117754913">If you still want to use scheme 1 to attach service VPCs to an enterprise router, contact customer service to evaluate the feasibility.</p>
</div></div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="er_01_0059.html">Getting Started</a></div>
</div>
</div>