Implementing a Hub and Spoke using NCC recensioni
2462 recensioni
Silvio C. · Recensione inserita 11 mesi fa
Add more time to labs
Xiadani M. · Recensione inserita 11 mesi fa
Silvio C. · Recensione inserita 11 mesi fa
Kris B. · Recensione inserita 11 mesi fa
done
Abhinay K. · Recensione inserita 11 mesi fa
Luca A. · Recensione inserita 11 mesi fa
Last check is broken
Juho T. · Recensione inserita 11 mesi fa
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. · Recensione inserita 11 mesi fa
Roberto P. · Recensione inserita 11 mesi fa
Last lab checkpoint assessment failed to update to complete this lab
Tom H. · Recensione inserita 11 mesi fa
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. · Recensione inserita 11 mesi fa
Aman C. · Recensione inserita 11 mesi fa
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. · Recensione inserita 11 mesi fa
Adrian D. · Recensione inserita 11 mesi fa
Vimaldeep W. · Recensione inserita 11 mesi fa
Flávia F. · Recensione inserita 11 mesi fa
Maniesh P. · Recensione inserita 11 mesi fa
Doesn't work
Volodymyr S. · Recensione inserita 11 mesi fa
It is not clear how to accomplish the task "Please create the internal connection between `spoke1-vm` and `spoke2-vm`."
Alex L. · Recensione inserita 11 mesi fa
need more time
Bayu Rahmat K. · Recensione inserita 11 mesi fa
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. · Recensione inserita 11 mesi fa
Man L. · Recensione inserita 11 mesi fa
dizzy
Bayu Rahmat K. · Recensione inserita 11 mesi fa
There is a bug in the task retest connectivity: the error message is Please create the internal connection between `spoke1-vm` and `spoke2-vm`.
Carlos M. · Recensione inserita 11 mesi fa
task 5 is not getting completed
Upasna J. · Recensione inserita 11 mesi fa
Non garantiamo che le recensioni pubblicate provengano da consumatori che hanno acquistato o utilizzato i prodotti. Le recensioni non sono verificate da Google.