Drive it with your mouse, your finger, or just use the arrow keys.
Use Learn mode to learn the demo. The orange boxes show where to click.
Use Present mode to hide the orange boxes and notes.
Use Autoplay mode to make it play like a movie. Hit the Esc key to stop.
Click a Shortcut to jump to a specific part of the demo.
This part of the lab is presented as a Hands-on Labs Interactive Simulation. This will allow you to experience steps which are too time-consuming or resource intensive to do live in the lab environment. In this simulation, you can use the software interface as if you are interacting with a live environment.
The orange boxes show where to click, and the left and right arrow keys can also be used to move through the simulation in either direction.
vRealize Network Insight contains a list of predefined system events (system problems and system changes) for which one can receive automated email notifications every four hours.
In this lab, diagnose an anomaly identified by vRealize Network Insight, address the issue in vSphere Web Client and archive the notification once resolved.
The natural search feature will recommend text.
This will highlight all problems identified by vRealize Network Insight.
The focus will be on the "DLR networks unreachable from NSX Edge or external router" event.
Explore the details and refer to Message: “DLR: brownsville-houston-ldr networks are not reachable from Router: sanjose-austin-ldr due to a routing issue”
This means that there is a routing issue between brownsville-houston-ldr and sanjose-austin-ldr.
Focus on the two recommendations:
Next explore in detail to understand the configuration of brownsville-houston-ldr and sanjose-austin-ldr.
There are three interfaces i.e.
To resolve this routing issue, create two internal interfaces on sanjose-austin-ldr.
Under settings, in ‘interfaces’ section:
This completes the routing change required to address the problem identified by vRealize Network Insight.
Note that the problem has now dimmed, showing that the issue has now been resolved.
Look for the 'DLR networks unreachable from NSX Edge or external router' problem.
Under the Router Interfaces Section the following two entries now exist.
Note brownsville-vnic wth IP address of 172.16.13.2 and houston-vnic with IP address of 172.16.14.2
This simluation demonstrates that vRealize Network Insight can help identify and address NSX Day 2 Operations.
The simulation is now complete. You can continue the Advanced NSX Management & Operations Lab!
To return to the lab, click the link in the top right corner or close this browser tab.