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.

1. Log on to vRealize Network Insight UI by typing following credentials.

• Username: admin@local
• Password: VMware1!

2. Click Login
3. Click in ‘Search Your Data Center’ field in the vRealize Network Insight main console, type prob.

The natural search feature will recommend text.

4. Click on Problem.
5. Click the magnifying glass to search.

This will highlight all problems identified by vRealize Network Insight.

6. Click on scrollbar to scroll down.

The focus will be on the "DLR networks unreachable from NSX Edge or external router" event.

7. Click on ‘+’ icon to expand the notification.

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:

• Recommendation 1: Check the routes on the router connected to the uplink of the NSX Edge router.
• Recommendation 2: Route to reach the distributed logical router should exist on the router connected to the uplink of the NSX Edge.

Next explore in detail to understand the configuration of brownsville-houston-ldr and sanjose-austin-ldr.

8. Click brownsville-houston-ldr and select ‘open link in a new window'.
9. Click on sanjose-austin-ldr  and select ‘open link in a new window'.
10. Click on VRF 'brownsville-houston-ldr' tab and focus on Router Interfaces.

There are three interfaces i.e.

• brownsville-vnic IP Addresses 172.16.13.1
• houston-vnic IP Addresses 172.16.14.1
• uplink-brownsville-houston-ldr IP Addresses 192.168.101.3

11. Click on  VRF 'sanjose-austin-ldr' tab and focus on Router Interfaces
12. Click scrollbar down. Notice there are three interfaces which excludes subnets for houston-vnic i.e. 172.16.14.x range and brownsville-vnic 172.16.13.x range.
13. Click scrollbar up.

To resolve this routing issue, create two internal interfaces on sanjose-austin-ldr.

14. Click on ‘X’ on VRF 'sanjose-austin-ldr' tab to close.
15. Click on ‘X’ on VRF 'brownsville-houston-ldr ' tab to close.
16. Click on Networking and Security.
17. Click NSX Edges.
18. Click on sanjose-austin-ldr.

Under settings, in ‘interfaces’ section:

19. Click vnic3
20. Click the Edit
21. In the ‘Edit NSX Edge Interface’, type houston-vnic, leave the type as Internal.
22. Click Select next to ‘connected to’
23. Click houston-vxlan (5002) logical switch.
24. Click OK.
25. Click on the ‘+’ sign under 'Configure Subnets'.
26. Click in 'Primary IP Address', type the primary IP address as 172.16.14.2.
27. Click in 'Subnet Prefix Length' field, type 24.
28. Click OK.
29. Click on  vnic4.
30. Click the Edit.
31. Click in Name field in the ‘Edit NSX Edge Interface’, type brownsville-vnic, leave the 'Type' as 'Internal'.
32. Click Select next to ‘Connected to’.
33. Click brownsville-vxlan (5003) logical switch.
34. Click OK
35. Click in 'Primary IP Address', type the primary IP address as 172.16.13.2.
36. Click in 'Subnet Prefix Length' field, type 24.
37. Click OK.

This completes the routing change required to address the problem identified by vRealize Network Insight.

38. Click on Problem - VMware vRealize Network Insight UI tab.

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.

39. Click on ‘+’ icon to expand the notification.
40. Click on sanjose-austin-ldr and select Open Link in a New Tab.
41. Click on second tab VMware vRealize Network Insight.
42. Click on Jump to current time. The screen will refresh.

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

43. Click on problem -vRealize Network Insight tab.
44. Click on '-' (minus button) to collapse the event details.
45. Click on Archive
46. Click Save, which archives this event.

This simluation demonstrates that vRealize Network Insight can help identify and address NSX Day 2 Operations.