vpruthi/doc-exports
1
0
Fork 0
forked from docs/doc-exports
Code Pull Requests Activity
doc-exports/docs/vpc/umn/vpc_faq_0069.html
Qin Ying, Fan 662ede2c6b VPC UMN 20240105 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>
2024-04-18 12:13:40 +00:00

178 lines
22 KiB
HTML
Raw Blame History

<a name="vpc_faq_0069"></a><a name="vpc_faq_0069"></a>
<h1 class="topictitle1">Why Did Communication Fail Between VPCs That Were Connected by a VPC Peering Connection?</h1>
<div id="body1484554994281"><div class="section" id="vpc_faq_0069__section1634617652519"><h4 class="sectiontitle">Symptom</h4><p id="vpc_faq_0069__p196661683255">After a VPC peering connection is created, the local and peer VPCs cannot communicate with each other.</p>
</div>
<div class="section" id="vpc_faq_0069__section75881452162511"><h4 class="sectiontitle">Troubleshooting</h4><p id="vpc_faq_0069__p17987205213470">The issues here are described in order of how likely they are to occur.</p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="vpc_faq_0069__table11639162722113" frame="border" border="1" rules="all"><caption><b>Table 1 </b>Possible causes and solutions</caption><thead align="left"><tr id="vpc_faq_0069__row563912711214"><th align="left" class="cellrowborder" valign="top" width="7.5200000000000005%" id="mcps1.3.2.3.2.4.1.1"><p id="vpc_faq_0069__p1471215418281">No.</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="48.22%" id="mcps1.3.2.3.2.4.1.2"><p id="vpc_faq_0069__p17639192710215">Possible Cause</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="44.26%" id="mcps1.3.2.3.2.4.1.3"><p id="vpc_faq_0069__p1063918274214">Solution</p>
</th>
</tr>
</thead>
<tbody><tr id="vpc_faq_0069__row2335836114016"><td class="cellrowborder" valign="top" width="7.5200000000000005%" headers="mcps1.3.2.3.2.4.1.1 "><p id="vpc_faq_0069__p7712754122812">1</p>
</td>
<td class="cellrowborder" valign="top" width="48.22%" headers="mcps1.3.2.3.2.4.1.2 "><p id="vpc_faq_0069__p333673644013">Overlapping CIDR blocks of local and peer VPCs</p>
<ul id="vpc_faq_0069__ul1492885019417"><li id="vpc_faq_0069__li3615610421">All their subnet CIDR blocks overlap.</li><li id="vpc_faq_0069__li8928350174116">Some of their subnet CIDR blocks overlap.</li></ul>
</td>
<td class="cellrowborder" valign="top" width="44.26%" headers="mcps1.3.2.3.2.4.1.3 "><p id="vpc_faq_0069__p133663617406">Refer to <a href="#vpc_faq_0069__section18800459153612">Overlapping CIDR Blocks of Local and Peer VPCs</a>.</p>
</td>
</tr>
<tr id="vpc_faq_0069__row2576154144320"><td class="cellrowborder" valign="top" width="7.5200000000000005%" headers="mcps1.3.2.3.2.4.1.1 "><p id="vpc_faq_0069__p177125541285">2</p>
</td>
<td class="cellrowborder" valign="top" width="48.22%" headers="mcps1.3.2.3.2.4.1.2 "><p id="vpc_faq_0069__p1257664204314">Incorrect route configuration for the local and peer VPCs</p>
<ul id="vpc_faq_0069__ul74674784615"><li id="vpc_faq_0069__li546711713464">No routes are added.</li><li id="vpc_faq_0069__li9392201564615">Incorrect routes are added.</li><li id="vpc_faq_0069__li41435142594">Destinations of the routes overlap with that configured for Direct Connect or VPN connections.</li></ul>
</td>
<td class="cellrowborder" valign="top" width="44.26%" headers="mcps1.3.2.3.2.4.1.3 "><p id="vpc_faq_0069__p19576942430">Refer to <a href="#vpc_faq_0069__section582181993814">Incorrect Route Configuration for Local and Peer VPCs</a>.</p>
</td>
</tr>
<tr id="vpc_faq_0069__row76394277211"><td class="cellrowborder" valign="top" width="7.5200000000000005%" headers="mcps1.3.2.3.2.4.1.1 "><p id="vpc_faq_0069__p271215411286">3</p>
</td>
<td class="cellrowborder" valign="top" width="48.22%" headers="mcps1.3.2.3.2.4.1.2 "><div class="p" id="vpc_faq_0069__p6639112762113">Incorrect network configuration<ul id="vpc_faq_0069__ul65498812292"><li id="vpc_faq_0069__li55491687297">The security group rules of the ECSs that need to communicate deny inbound traffic from each other.</li><li id="vpc_faq_0069__li8848116172915">The firewall of the ECS NIC blocks traffic.</li><li id="vpc_faq_0069__li8880103315297">The <span id="vpc_faq_0069__text1069773815538">firewall</span><span id="vpc_faq_0069__text669813845314"></span> rules of the subnets connected by the VPC peering connection deny inbound traffic.</li><li id="vpc_faq_0069__li13621641182913">Check the policy-based routing configuration of an ECS with multiple NICs.</li></ul>
</div>
</td>
<td class="cellrowborder" valign="top" width="44.26%" headers="mcps1.3.2.3.2.4.1.3 "><p id="vpc_faq_0069__p1063962762110">Refer to <a href="#vpc_faq_0069__section157663413717">Incorrect Network Configuration</a>.</p>
</td>
</tr>
<tr id="vpc_faq_0069__row1063915276211"><td class="cellrowborder" valign="top" width="7.5200000000000005%" headers="mcps1.3.2.3.2.4.1.1 "><p id="vpc_faq_0069__p10712105418284">4</p>
</td>
<td class="cellrowborder" valign="top" width="48.22%" headers="mcps1.3.2.3.2.4.1.2 "><p id="vpc_faq_0069__p11639102752118">ECS network failure</p>
</td>
<td class="cellrowborder" valign="top" width="44.26%" headers="mcps1.3.2.3.2.4.1.3 "><p id="vpc_faq_0069__p96391627162120">Refer to <a href="#vpc_faq_0069__section8357923710">ECS Network Failure</a>.</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
<div class="section" id="vpc_faq_0069__section18800459153612"><a name="vpc_faq_0069__section18800459153612"></a><a name="section18800459153612"></a><h4 class="sectiontitle">Overlapping CIDR Blocks of Local and Peer VPCs</h4><p id="vpc_faq_0069__p2066214561946">If the CIDR blocks of VPCs connected by a VPC peering connection overlap, the connection may not take effect due to route conflicts.</p>
<div class="tablenoborder"><table cellpadding="4" cellspacing="0" summary="" id="vpc_faq_0069__table187875614582" frame="border" border="1" rules="all"><caption><b>Table 2 </b>Overlapping CIDR blocks of local and peer VPCs</caption><thead align="left"><tr id="vpc_faq_0069__row1878796145819"><th align="left" class="cellrowborder" valign="top" width="27.650000000000002%" id="mcps1.3.3.3.2.4.1.1"><p id="vpc_faq_0069__p1278718611582">Scenario</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="39.32%" id="mcps1.3.3.3.2.4.1.2"><p id="vpc_faq_0069__p017495214101">Description</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="33.03%" id="mcps1.3.3.3.2.4.1.3"><p id="vpc_faq_0069__p2997550103915">Solution</p>
</th>
</tr>
</thead>
<tbody><tr id="vpc_faq_0069__row129717127812"><td class="cellrowborder" valign="top" width="27.650000000000002%" headers="mcps1.3.3.3.2.4.1.1 "><p id="vpc_faq_0069__p129718121186">VPCs with overlapping CIDR blocks also include subnets that overlap.</p>
</td>
<td class="cellrowborder" valign="top" width="39.32%" headers="mcps1.3.3.3.2.4.1.2 "><p id="vpc_faq_0069__p3203944188">As shown in <a href="#vpc_faq_0069__fig465519155457">Figure 1</a>, the CIDR blocks of VPC-A and VPC-B overlap, and all their subnets overlap.</p>
<ul id="vpc_faq_0069__ul979554148"><li id="vpc_faq_0069__li2775510140">Overlapping CIDR blocks of VPC-A and VPC-B: 10.0.0.0/16</li><li id="vpc_faq_0069__li1056019566148">Overlapping CIDR blocks of Subnet-A01 in VPC-A and Subnet-B01 in VPC-B: 10.0.0.0/24</li><li id="vpc_faq_0069__li03611913181618">Overlapping CIDR blocks of Subnet-A02 in VPC-A and Subnet-B02 in VPC-B: 10.0.1.0/24</li></ul>
</td>
<td class="cellrowborder" valign="top" width="33.03%" headers="mcps1.3.3.3.2.4.1.3 "><p id="vpc_faq_0069__p20298912485">VPC-A and VPC-B cannot be connected using a VPC peering connection.</p>
<p id="vpc_faq_0069__p162992528356">Replan the network.</p>
</td>
</tr>
<tr id="vpc_faq_0069__row1013214509219"><td class="cellrowborder" valign="top" width="27.650000000000002%" headers="mcps1.3.3.3.2.4.1.1 "><p id="vpc_faq_0069__p091517282815">Two VPCs have overlapping CIDR blocks but some of their subnets do not overlap.</p>
</td>
<td class="cellrowborder" valign="top" width="39.32%" headers="mcps1.3.3.3.2.4.1.2 "><p id="vpc_faq_0069__p1417515241011">As shown in <a href="#vpc_faq_0069__fig098452131910">Figure 2</a>, the CIDR blocks of VPC-A and VPC-B overlap, and some of their subnets overlap.</p>
<ul id="vpc_faq_0069__ul8798161232118"><li id="vpc_faq_0069__li15798131212215">Overlapping CIDR blocks of VPC-A and VPC-B: 10.0.0.0/16</li><li id="vpc_faq_0069__li279861202116">Overlapping CIDR blocks of Subnet-A01 in VPC-A and Subnet-B01 in VPC-B: 10.0.0.0/24</li><li id="vpc_faq_0069__li127981124215">CIDR blocks of Subnet-A02 in VPC-A and Subnet-B02 in VPC-B do not overlap.</li></ul>
</td>
<td class="cellrowborder" valign="top" width="33.03%" headers="mcps1.3.3.3.2.4.1.3 "><ul id="vpc_faq_0069__ul153823213277"><li id="vpc_faq_0069__li1057011358272">A VPC peering connection cannot connect the entire VPCs,<p id="vpc_faq_0069__p89991749163614"><a name="vpc_faq_0069__li1057011358272"></a><a name="li1057011358272"></a>VPC-A and VPC-B.</p>
</li><li id="vpc_faq_0069__li1322218564361">A connection can connect their subnets (Subnet-A02 and Subnet-B02) that do not overlap. For details, see <a href="#vpc_faq_0069__fig920231311415">Figure 3</a>.</li></ul>
</td>
</tr>
</tbody>
</table>
</div>
<div class="fignone" id="vpc_faq_0069__fig465519155457"><a name="vpc_faq_0069__fig465519155457"></a><a name="fig465519155457"></a><span class="figcap"><b>Figure 1 </b>Networking diagram (IPv4)</span><br><span><img class="eddx" id="vpc_faq_0069__en-us_topic_0000001252180225_image42928328228" src="en-us_image_0000001818982898.png"></span></div>
<div class="fignone" id="vpc_faq_0069__fig098452131910"><a name="vpc_faq_0069__fig098452131910"></a><a name="fig098452131910"></a><span class="figcap"><b>Figure 2 </b>Networking diagram (IPv4)</span><br><span><img class="eddx" id="vpc_faq_0069__en-us_topic_0000001252180225_image255332305613" src="en-us_image_0000001818983474.png"></span></div>
<p id="vpc_faq_0069__p165794588313">If CIDR blocks of VPCs overlap and some of their subnets overlap, you can create a VPC peering connection between their subnets with non-overlapping CIDR blocks. <a href="#vpc_faq_0069__fig920231311415">Figure 3</a> shows the networking diagram of connecting Subnet-A02 and Subnet-B02. <a href="#vpc_faq_0069__table45541823135611">Table 3</a> describes the routes required.</p>
<div class="fignone" id="vpc_faq_0069__fig920231311415"><a name="vpc_faq_0069__fig920231311415"></a><a name="fig920231311415"></a><span class="figcap"><b>Figure 3 </b>Networking diagram (IPv4)</span><br><span><img class="eddx" id="vpc_faq_0069__en-us_topic_0000001252180225_image15706103625817" src="en-us_image_0000001818823702.png"></span></div>
<div class="tablenoborder"><a name="vpc_faq_0069__table45541823135611"></a><a name="table45541823135611"></a><table cellpadding="4" cellspacing="0" summary="" id="vpc_faq_0069__table45541823135611" frame="border" border="1" rules="all"><caption><b>Table 3 </b>Routes required for the VPC peering connection between Subnet-A02 and Subnet-B02</caption><thead align="left"><tr id="vpc_faq_0069__row055419239568"><th align="left" class="cellrowborder" valign="top" width="16.49%" id="mcps1.3.3.8.2.5.1.1"><p id="vpc_faq_0069__p1455422345614">Route Table</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="13.83%" id="mcps1.3.3.8.2.5.1.2"><p id="vpc_faq_0069__p14554152316561">Destination</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="14.46%" id="mcps1.3.3.8.2.5.1.3"><p id="vpc_faq_0069__p14554223135612">Next Hop</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="55.22%" id="mcps1.3.3.8.2.5.1.4"><p id="vpc_faq_0069__p155541523165611">Description</p>
</th>
</tr>
</thead>
<tbody><tr id="vpc_faq_0069__row1455482312561"><td class="cellrowborder" valign="top" width="16.49%" headers="mcps1.3.3.8.2.5.1.1 "><p id="vpc_faq_0069__p1655412315614">VPC-A route table</p>
</td>
<td class="cellrowborder" valign="top" width="13.83%" headers="mcps1.3.3.8.2.5.1.2 "><p id="vpc_faq_0069__p1655492317562">10.0.2.0/24</p>
</td>
<td class="cellrowborder" valign="top" width="14.46%" headers="mcps1.3.3.8.2.5.1.3 "><p id="vpc_faq_0069__p1955462345610">Peering-AB</p>
</td>
<td class="cellrowborder" valign="top" width="55.22%" headers="mcps1.3.3.8.2.5.1.4 "><p id="vpc_faq_0069__p455418237569">Add a route with the CIDR block of Subnet-B02 as the destination and Peering-AB as the next hop.</p>
</td>
</tr>
<tr id="vpc_faq_0069__row1755414233562"><td class="cellrowborder" valign="top" width="16.49%" headers="mcps1.3.3.8.2.5.1.1 "><p id="vpc_faq_0069__p5554162375618">VPC-B route table</p>
</td>
<td class="cellrowborder" valign="top" width="13.83%" headers="mcps1.3.3.8.2.5.1.2 "><p id="vpc_faq_0069__p19554112385615">10.0.1.0/24</p>
</td>
<td class="cellrowborder" valign="top" width="14.46%" headers="mcps1.3.3.8.2.5.1.3 "><p id="vpc_faq_0069__p05548232568">Peering-AB</p>
</td>
<td class="cellrowborder" valign="top" width="55.22%" headers="mcps1.3.3.8.2.5.1.4 "><p id="vpc_faq_0069__p10554192385617">Add a route with the CIDR block of Subnet-A02 as the destination and Peering-AB as the next hop.</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
<div class="section" id="vpc_faq_0069__section582181993814"><a name="vpc_faq_0069__section582181993814"></a><a name="section582181993814"></a><h4 class="sectiontitle">Incorrect Route Configuration for Local and Peer VPCs</h4><p id="vpc_faq_0069__p1452315752712"><a href="vpc_peering_0004.html">Viewing Routes Configured for a VPC Peering Connection</a>. <a href="#vpc_faq_0069__table513212558272">Table 4</a> lists the items that you need to check.</p>
<div class="tablenoborder"><a name="vpc_faq_0069__table513212558272"></a><a name="table513212558272"></a><table cellpadding="4" cellspacing="0" summary="" id="vpc_faq_0069__table513212558272" frame="border" border="1" rules="all"><caption><b>Table 4 </b>Route check items</caption><thead align="left"><tr id="vpc_faq_0069__row81331655122720"><th align="left" class="cellrowborder" valign="top" width="42.870000000000005%" id="mcps1.3.4.3.2.3.1.1"><p id="vpc_faq_0069__p1113395520273">Item</p>
</th>
<th align="left" class="cellrowborder" valign="top" width="57.13%" id="mcps1.3.4.3.2.3.1.2"><p id="vpc_faq_0069__p17133105515279">Solution</p>
</th>
</tr>
</thead>
<tbody><tr id="vpc_faq_0069__row01339553271"><td class="cellrowborder" valign="top" width="42.870000000000005%" headers="mcps1.3.4.3.2.3.1.1 "><p id="vpc_faq_0069__p213319559276">Check whether routes are added to the route tables of the local and peer VPCs.</p>
</td>
<td class="cellrowborder" valign="top" width="57.13%" headers="mcps1.3.4.3.2.3.1.2 "><p id="vpc_faq_0069__p1313317553278">If routes are not added, add routes by referring to:</p>
<ul id="vpc_faq_0069__ul08091742155017"><li id="vpc_faq_0069__li1743373611537"><a href="en-us_topic_0046655037.html">Creating a VPC Peering Connection with Another VPC in Your Account</a></li></ul>
</td>
</tr>
<tr id="vpc_faq_0069__row15133105513279"><td class="cellrowborder" valign="top" width="42.870000000000005%" headers="mcps1.3.4.3.2.3.1.1 "><div class="p" id="vpc_faq_0069__p9133555102712">Check the destinations of routes added to the route tables of the local and peer VPCs.<ul id="vpc_faq_0069__ul6653144162312"><li id="vpc_faq_0069__li7653114402315">In the route table of the local VPC, check whether the route destination is the CIDR block, subnet CIDR block, or related private IP address of the peer VPC.</li><li id="vpc_faq_0069__li01476487239">In the route table of the peer VPC, check whether the route destination is the CIDR block, subnet CIDR block, or related private IP address of the local VPC.</li></ul>
</div>
</td>
<td class="cellrowborder" valign="top" width="57.13%" headers="mcps1.3.4.3.2.3.1.2 "><p id="vpc_faq_0069__p5635141015518">If the route destination is incorrect, modify it by referring to <a href="vpc_peering_0007.html">Modifying Routes Configured for a VPC Peering Connection</a>.</p>
</td>
</tr>
<tr id="vpc_faq_0069__row165315527139"><td class="cellrowborder" valign="top" width="42.870000000000005%" headers="mcps1.3.4.3.2.3.1.1 "><p id="vpc_faq_0069__p95315527137">Destinations of the routes overlap with that configured for Direct Connect or VPN connections.</p>
</td>
<td class="cellrowborder" valign="top" width="57.13%" headers="mcps1.3.4.3.2.3.1.2 "><p id="vpc_faq_0069__p1529249191513">Check whether any of the VPCs connected by the VPC peering connection also has a VPN or Direct Connect connection connected. If they do, check the destinations of their routes.</p>
<p id="vpc_faq_0069__p10531252181313">If the destinations of the routes overlap, the VPC peering connection does not take effect. In this case, replan the network connection.</p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
<div class="section" id="vpc_faq_0069__section157663413717"><a name="vpc_faq_0069__section157663413717"></a><a name="section157663413717"></a><h4 class="sectiontitle">Incorrect Network Configuration</h4><ol id="vpc_faq_0069__ol98342048101511"><li id="vpc_faq_0069__li0835104881518">Check whether the security group rules of the ECSs that need to communicate with each other are correctly configured. For details, see <a href="vpc_SecurityGroup_0011.html">Viewing the Security Group of an ECS</a>.<ul id="vpc_faq_0069__ul163257179476"><li id="vpc_faq_0069__li10325517134712">If the ECSs are associated with the same security group, you do not need to check their rules.</li><li id="vpc_faq_0069__li96460451498">If the ECSs are in different security groups, you need to add inbound rules to allow access from the peer security group. For details, see <a href="en-us_topic_0081124350.html">Security Group Configuration Examples</a>.</li></ul>
</li><li id="vpc_faq_0069__li95729191219">Check whether the firewall of the ECS NIC blocks traffic.<p id="vpc_faq_0069__p61417551514"><a name="vpc_faq_0069__li95729191219"></a><a name="li95729191219"></a>If the firewall blocks traffic, configure the firewall to allow inbound traffic.</p>
</li><li id="vpc_faq_0069__li14331104812131">Check whether <span id="vpc_faq_0069__text198671340175310">firewall</span><span id="vpc_faq_0069__text20868134014531"></span> rules of the subnets connected by the VPC peering connection deny inbound traffic.<p id="vpc_faq_0069__p12762134910137">If the <span id="vpc_faq_0069__text7238343185316">firewall</span><span id="vpc_faq_0069__text1239114312537"></span> rules deny inbound traffic, configure the rules to allow the traffic.</p>
</li><li id="vpc_faq_0069__li16837194812151">If an ECS has more than one NIC, check whether correct policy-based routing has been configured for the ECS and packets with different source IP addresses match their own routes from each NIC.<div class="p" id="vpc_faq_0069__p19408612102519"><a name="vpc_faq_0069__li16837194812151"></a><a name="li16837194812151"></a>If an ECS has two NICs (eth0 and eth1):<ul id="vpc_faq_0069__ul671521311254"><li id="vpc_faq_0069__li10358111862518">IP address of eth0: 192.168.1.10; Subnet gateway: 192.168.1.1</li><li id="vpc_faq_0069__li524916312258">IP address of eth1: 192.168.2.10; Subnet gateway: 192.168.2.1</li></ul>
</div>
<div class="p" id="vpc_faq_0069__p02360484266">Command format:<ul id="vpc_faq_0069__ul91913372254"><li id="vpc_faq_0069__li1519173792520"><strong id="vpc_faq_0069__b19244455132515">ping -l</strong> <em id="vpc_faq_0069__i1921985118252">IP address of eth0 Subnet gateway address of eth0</em></li><li id="vpc_faq_0069__li14537113912253"><strong id="vpc_faq_0069__b815253317272">ping -l</strong> <em id="vpc_faq_0069__i121531033162712">IP address of eth1 Subnet gateway address of eth1</em></li></ul>
</div>
<div class="p" id="vpc_faq_0069__p14347336152610">Run the following commands:<ul id="vpc_faq_0069__ul142332722618"><li id="vpc_faq_0069__li1442372792619"><strong id="vpc_faq_0069__b1042317277265">ping -I 192.168.1.10 192.168.1.1</strong></li><li id="vpc_faq_0069__li84230274262"><strong id="vpc_faq_0069__b8423027112618">ping -I 192.168.2.10 192.168.2.1</strong></li></ul>
</div>
<p id="vpc_faq_0069__p1183710481159">If the network communication is normal, the routes of the NICs are correctly configured.</p>
</li></ol>
</div>
<div class="section" id="vpc_faq_0069__section8357923710"><a name="vpc_faq_0069__section8357923710"></a><a name="section8357923710"></a><h4 class="sectiontitle">ECS Network Failure</h4><ol id="vpc_faq_0069__ol979184314323"><li id="vpc_faq_0069__li11900104112544">Log in to the ECS.</li><li id="vpc_faq_0069__li1380154317328">Check whether the ECS NIC has an IP address assigned.<ul id="vpc_faq_0069__ul18966145595019"><li id="vpc_faq_0069__li7966255195014">Linux ECS: Use the <strong id="vpc_faq_0069__b7894173712286">ifconfig</strong> or <strong id="vpc_faq_0069__b74611340112815">ip address</strong> command to view the IP address of the NIC.</li><li id="vpc_faq_0069__li1496695515016">Windows ECS: In the search box, enter <strong id="vpc_faq_0069__b86051420153014">cmd</strong> and press <strong id="vpc_faq_0069__b1983920228305">Enter</strong>. In the displayed command prompt, run the <strong id="vpc_faq_0069__b564617515303">ipconfig</strong> command.</li></ul>
</li><li id="vpc_faq_0069__li158119432325">Check whether the subnet gateway of the ECS can be pinged.<ol type="a" id="vpc_faq_0069__ol1820193319555"><li id="vpc_faq_0069__li1522294415579">In the ECS list, click the ECS name.<p id="vpc_faq_0069__p737044525716"><a name="vpc_faq_0069__li1522294415579"></a><a name="li1522294415579"></a>The ECS details page is displayed.</p>
</li><li id="vpc_faq_0069__li1698224775718">On the ECS details page, click the hyperlink of VPC.<p id="vpc_faq_0069__p76947501576"><a name="vpc_faq_0069__li1698224775718"></a><a name="li1698224775718"></a>The <strong id="vpc_faq_0069__b15344104103417">Virtual Private Cloud</strong> page is displayed.</p>
</li><li id="vpc_faq_0069__li122862053155717">In the VPC list, locate the target VPC and click the number in the <strong id="vpc_faq_0069__b1643815543510">Subnets</strong> column.<p id="vpc_faq_0069__p239273315912">The <strong id="vpc_faq_0069__b1433316717352">Subnets</strong> page is displayed.</p>
</li><li id="vpc_faq_0069__li10424957125914">In the subnet list, click the subnet name.<p id="vpc_faq_0069__p9910161405"><a name="vpc_faq_0069__li10424957125914"></a><a name="li10424957125914"></a>The subnet details page is displayed.</p>
</li><li id="vpc_faq_0069__li1845013565616">Click the <strong id="vpc_faq_0069__b07911337103520">IP Addresses</strong> tab and view the gateway address of the subnet.</li><li id="vpc_faq_0069__li212012213218">Check whether the gateway communication is normal:<p id="vpc_faq_0069__p94523712312"><a name="vpc_faq_0069__li212012213218"></a><a name="li212012213218"></a><strong id="vpc_faq_0069__b149941957938">ping</strong> <em id="vpc_faq_0069__i938940447">Subnet gateway address</em></p>
<p id="vpc_faq_0069__p27684311319">Example command: <strong id="vpc_faq_0069__b518855493617">ping 172.17.0.1</strong></p>
</li></ol>
</li></ol>
</div>
</div>
<div>
<div class="familylinks">
<div class="parentlink"><strong>Parent topic:</strong> <a href="faq_peer_0000.html">VPC Peering Connections</a></div>
</div>
</div>
View Git Blame Copy Permalink