关于“Working with multiple VPC networks”的评价
评论
Dmitry B. · 评论about 3 years之前
scot r. · 评论about 3 years之前
Jean-Alain M. · 评论about 3 years之前
Supun M. · 评论about 3 years之前
Haritha M. · 评论about 3 years之前
Leon S. · 评论about 3 years之前
Harold O. · 评论about 3 years之前
Dhruv p. · 评论about 3 years之前
Joseph G. · 评论about 3 years之前
vikas t. · 评论about 3 years之前
Danilo R. · 评论about 3 years之前
Tulsi S. · 评论about 3 years之前
I do not know how I managed to pass the laboratory work
Maksim M. · 评论about 3 years之前
Felix M. · 评论about 3 years之前
Dipen V. · 评论about 3 years之前
Fanta D. · 评论about 3 years之前
Found some issues with the lab: the mynet-eu-vm server is not in the eu-west zone NAME: mynet-eu-vm ZONE: us-central1-f MACHINE_TYPE: n1-standard-1 PREEMPTIBLE: INTERNAL_IP: 10.128.0.2 EXTERNAL_IP: 35.192.90.73 STATUS: RUNNING Because of this in "Explore the network interface connectivity" section step 8 "To test connectivity to mynet-eu-vm's internal IP, run the following command, replacing mynet-eu-vm's internal IP" does work This commmand on vm-appliance shows a differnt output - sudo ifconfig student-03-866a4507f416@vm-appliance:~$ sudo ifconfig ens4: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1460 inet 172.16.0.3 netmask 255.255.255.255 broadcast 172.16.0.3 inet6 fe80::4001:acff:fe10:3 prefixlen 64 scopeid 0x20<link> ether 42:01:ac:10:00:03 txqueuelen 1000 (Ethernet) RX packets 521 bytes 128602 (125.5 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 469 bytes 53386 (52.1 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ens5: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1460 inet 10.130.0.3 netmask 255.255.255.255 broadcast 10.130.0.3 inet6 fe80::4001:aff:fe82:3 prefixlen 64 scopeid 0x20<link> ether 42:01:0a:82:00:03 txqueuelen 1000 (Ethernet) RX packets 7 bytes 2494 (2.4 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 15 bytes 2234 (2.1 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ens6: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1460 inet 10.128.0.4 netmask 255.255.255.255 broadcast 10.128.0.4 inet6 fe80::4001:aff:fe80:4 prefixlen 64 scopeid 0x20<link> ether 42:01:0a:80:00:04 txqueuelen 1000 (Ethernet) RX packets 4 bytes 2308 (2.2 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 15 bytes 2234 (2.1 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 36 bytes 3060 (2.9 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 36 bytes 3060 (2.9 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 Output under "Explore the network interface connectivity" section step 9 shows different output because of the network cards are named different. default via 172.16.0.1 dev ens4 10.128.0.0/20 via 10.128.0.1 dev ens6 10.128.0.1 dev ens6 scope link 10.130.0.0/24 via 10.130.0.1 dev ens5 10.130.0.1 dev ens5 scope link 172.16.0.0/24 via 172.16.0.1 dev ens4 172.16.0.1 dev ens4 scope link
Kirk D. · 评论about 3 years之前
mynet-eu-vm auto created by lab created in US zone
Phill F. · 评论about 3 years之前
VARDHI VINAY K. · 评论about 3 years之前
Jayesh P. · 评论about 3 years之前
Rahul B. · 评论about 3 years之前
Rahul B. · 评论about 3 years之前
eu-vm was in wrong location which prevented lab checks from completing correctly
Dave N. · 评论about 3 years之前
Doesn't work on task 2 and task 4 completion
Stephen J. · 评论about 3 years之前
Issues with LAB, it is unable to validate completion.
Anuraag V. · 评论about 3 years之前
我们无法确保发布的评价来自已购买或已使用产品的消费者。评价未经 Google 核实。