关于“Configuring VPC Network Peering”的评价

Danial D. · 已于 about 3 years前审核

Tomas B. · 已于 about 3 years前审核

Andrés C. · 已于 about 3 years前审核

Timo M. · 已于 about 3 years前审核

Ashutosh S. · 已于 about 3 years前审核

Darshana A. · 已于 about 3 years前审核

Julien L. · 已于 about 3 years前审核

ercan h. · 已于 about 3 years前审核

Anand R. · 已于 about 3 years前审核

Andrez L. · 已于 about 3 years前审核

alaa h. · 已于 about 3 years前审核

Clara S. · 已于 about 3 years前审核

Manish K. · 已于 about 3 years前审核

Edward R. · 已于 about 3 years前审核

Trung D. · 已于 about 3 years前审核

Yasin Y. · 已于 about 3 years前审核

Amisha k. · 已于 about 3 years前审核

Gabriel T. · 已于 about 3 years前审核

Dinesh R. · 已于 about 3 years前审核

Ravishanker A. · 已于 about 3 years前审核

BO-REN C. · 已于 about 3 years前审核

Wei Man Y. · 已于 about 3 years前审核

Task 1. Explore connectivity between non-peered VPC networks Explore the connectivity between mynetwork and privatenet On the VM instances page, click Columns, and then select Network. There is no place where one can read "Columns" except in a hover message. Please include an icon that the reader can search for, otherwise this becomes very hard to find. -------------------------------------- Task 2. Configure VPC network peering Create peering 2-1 2. Click Create peering connection. Should be Create connection -------------------------------------- Task 3. Verify private communication between peered VPC networks Verify routes between networks In the Cloud Console, on the Navigation menu (), click VPC network > Routes. Notice that there is a route for each subnet in mynetwork with peering-1-2 as the Next hop. Similarly, notice that there is a route for each subnet in privatenet with peering-2-1 as the Next hop. Nothing was found. The routes are visible when one clicks into each of the peering networks.

Fidel B. · 已于 about 3 years前审核

John M. · 已于 about 3 years前审核

Robert F. · 已于 about 3 years前审核