NCC を使用してハブ アンド スポークを実装する のレビュー

Lomovoy Mykola · 約1年前にレビュー済み

Ma Alansarang · 約1年前にレビュー済み

Yang Chuck · 約1年前にレビュー済み

Kurmi Sandiep · 約1年前にレビュー済み

González Javier · 約1年前にレビュー済み

Singh Bikram · 約1年前にレビュー済み

de Brito Rodrigues dos Santos Lucas · 約1年前にレビュー済み

Gao Jialiang · 約1年前にレビュー済み

Meyerdiercks Nico · 約1年前にレビュー済み

Tyagi Vivesh · 約1年前にレビュー済み

Tyagi Vivesh · 約1年前にレビュー済み

LIN CHANG LI · 約1年前にレビュー済み

Bruna Fabian · 約1年前にレビュー済み

تمام

هايل علي محمد · 約1年前にレビュー済み

Mugambi Felix · 約1年前にレビュー済み

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).

Limantoro Julian · 約1年前にレビュー済み

Terriquez Rodriguez Ricardo Daniel · 約1年前にレビュー済み

Martinez Salda�a Christian · 約1年前にレビュー済み

Bussie Brad · 約1年前にレビュー済み

Yulianto Nurhavid · 約1年前にレビュー済み

Ruban Ranjith · 約1年前にレビュー済み

wei kai · 約1年前にレビュー済み

NGUYEN Binh · 約1年前にレビュー済み

Jaishankar Harine · 約1年前にレビュー済み

Luban Safwan · 約1年前にレビュー済み