Implémentation d'une topologie en étoile à l'aide de NCC avis

Pablo R. · Examiné il y a 8 mois

Mohammed O. · Examiné il y a 8 mois

Sriram P. · Examiné il y a 8 mois

Prashant Y. · Examiné il y a 8 mois

Muhammed Shafi K. · Examiné il y a 8 mois

Mykola L. · Examiné il y a 8 mois

Alansarang M. · Examiné il y a 8 mois

Chuck Y. · Examiné il y a 8 mois

Sandiep K. · Examiné il y a 8 mois

Javier G. · Examiné il y a 8 mois

Bikram S. · Examiné il y a 8 mois

Lucas d. · Examiné il y a 8 mois

Jialiang G. · Examiné il y a 8 mois

Nico M. · Examiné il y a 8 mois

Vivesh T. · Examiné il y a 8 mois

Vivesh T. · Examiné il y a 8 mois

CHANG LI L. · Examiné il y a 8 mois

Fabian B. · Examiné il y a 8 mois

تمام

محمد ه. · Examiné il y a 8 mois

Felix M. · Examiné il y a 8 mois

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. · Examiné il y a 8 mois

Ricardo Daniel T. · Examiné il y a 8 mois

Christian M. · Examiné il y a 8 mois

Brad B. · Examiné il y a 8 mois

Nurhavid Y. · Examiné il y a 8 mois