Implementing a Hub and Spoke using NCC Reviews

Chuck Y. · Reviewed 13 days ago

Sandiep K. · Reviewed 13 days ago

Javier G. · Reviewed 14 days ago

Bikram S. · Reviewed 14 days ago

Lucas d. · Reviewed 14 days ago

Jialiang G. · Reviewed 14 days ago

Nico M. · Reviewed 14 days ago

Vivesh T. · Reviewed 14 days ago

Vivesh T. · Reviewed 14 days ago

昶立 . · Reviewed 14 days ago

Fabian B. · Reviewed 15 days ago

تمام

محمد ه. · Reviewed 15 days ago

Felix M. · Reviewed 15 days ago

The lab does a really bad job at introducing: - How to manage a hub-and-spoke topology with NCC - The Network Topology tool # The NCC is very opaque and "hub-vpc" is completely left out The lab begins with 3 separate VPCs but hub-vpc ends up never connecting to anything. After clearing step 5 and ensuring both VMs on the spokes can ping each other, SSH-ing to hub-vm and pinging to either spokes through internal IP yields no pingbacks. While this should be obvious because hub-vpc was not a hub nor a spoke in the NCC creation process, one wonders why the "hub-vpc" misnomer and why was it even created here. Also, it is not obvious how I could use NCC to manage traffic for the supposed hub-and-spoke topology. I checked the list of available VPCs through the Cloud console and there was no additional network to manage. There was the "hub-vpc" but that, as mentioned above, was completely detached from the topology. # The Network Topology tool has no data By the time I begin task 6, there was no data on Network Topology. Maybe I am supposed to create more traffic myself so I spammed more pings on the two spoke but after some 2 minutes of trying, the Topology stayed blank. While this might be the 1-hour data block limitation, it would be nice to have something here to explore during the lab. Maybe some more steps to generate some more noise during the previous tasks? Extra: One of the firewall rule supposed for spoke2-vpc is assigned to spoke1-vpc instead (specifically the app-allow-ssh-rdp-spoke2). This does not affect anything of course, because the `app-allow-icmp-spoke2` also allows ssh (of which its spoke1 counterpart has it properly configured to only allow icmp).

Julian L. · Reviewed 15 days ago

Ricardo Daniel T. · Reviewed 15 days ago

Christian M. · Reviewed 16 days ago

Brad B. · Reviewed 16 days ago

Nurhavid Y. · Reviewed 16 days ago

Ranjith R. · Reviewed 16 days ago

kai w. · Reviewed 16 days ago

Binh N. · Reviewed 16 days ago

Harine J. · Reviewed 16 days ago

Safwan L. · Reviewed 16 days ago

Ricardo Daniel T. · Reviewed 16 days ago

Manikanda Nagarajan M. · Reviewed 17 days ago