리뷰 Implementing a Hub and Spoke using NCC개
리뷰 2541개
bad instructions on how to add spokes. will not give me credit for the connection between spoke1 and spoke2. i can ping both. but when I attempt the check mark to verify, it fails.
T.J. Y. · 12개월 전에 리뷰됨
The lab is wrong, the name of the VMs needs to be hub-vm , hub-vm1 and hub-vm2
Giovanni A. · 12개월 전에 리뷰됨
ZHIJUN C. · 12개월 전에 리뷰됨
Jairo M. · 12개월 전에 리뷰됨
Silvio C. · 12개월 전에 리뷰됨
Add more time to labs
Xiadani M. · 12개월 전에 리뷰됨
Silvio C. · 12개월 전에 리뷰됨
Kris B. · 12개월 전에 리뷰됨
done
Abhinay K. · 12개월 전에 리뷰됨
Luca A. · 12개월 전에 리뷰됨
Last check is broken
Juho T. · 12개월 전에 리뷰됨
Instructions needs updating as they do not match the GCP portal. Also, when checking my progress, my connectivity tests were not passing on the lab, even though i was getting successful pings. It may be because i named my spokes differently to the instructions
James K. · 12개월 전에 리뷰됨
Roberto P. · 12개월 전에 리뷰됨
Last lab checkpoint assessment failed to update to complete this lab
Tom H. · 12개월 전에 리뷰됨
The lab cannot be completed at present. In Step 5, it is asking for us to create the internal connection between the two spoke VMs, but does not give the information on how to complete that. I verified that the two VMs could ping each other, but the step will not mark itself complete. Also, in the firewall rules created when the lab is provisioned, one of the rules indicates it should be on spoke2, but is actually assigned to the spoke1-vpc.
Michael M. · 12개월 전에 리뷰됨
Aman C. · 12개월 전에 리뷰됨
Was unable to complete the lab despite being able to ping from each spoke VM to the other because I kept receiving the same error when I went to verify the last objective: "Please create the internal connection between 'spoke1-vm' and 'spoke2-vm'." Pings were successful in both directions.
Melissa S. · 12개월 전에 리뷰됨
Adrian D. · 12개월 전에 리뷰됨
Vimaldeep W. · 12개월 전에 리뷰됨
Flávia F. · 12개월 전에 리뷰됨
Maniesh P. · 12개월 전에 리뷰됨
Doesn't work
Volodymyr S. · 12개월 전에 리뷰됨
It is not clear how to accomplish the task "Please create the internal connection between `spoke1-vm` and `spoke2-vm`."
Alex L. · 12개월 전에 리뷰됨
need more time
Bayu Rahmat K. · 12개월 전에 리뷰됨
The lab instructions seem wrong/outdatet? Task 3: Test connectivity Now try to reach spoke2-vm (from SSH spoke2-vm) "Notice how the ping fails. This should execute and display 100% packet loss. Press Ctrl+C to stop the command." Why should this fail if I'm pinging from SSH spoke2-vm spoke2-vm istelf? The ping works, 0% packet loss. Task 6. Explore the Network Topology Tool is pretty pointless/shows nothing the tasks seems no longer match the GUI/available options (there is no "Hover over an entity to display the Expand icon")
Susanne L. · 12개월 전에 리뷰됨
Google은 게시된 리뷰가 제품을 구매 또는 사용한 소비자에 의해 작성되었음을 보증하지 않습니다. 리뷰는 Google의 인증을 거치지 않습니다.