Hello Friends, We have completed all 9 parts and by now you should have your entire NSX-T 3.0 env up and running. This post will specifically focus on testing the env that we have deployed in this series.
NSX-T 3.0 Series: Part1-NSX-T Manager Installation
NSX-T 3.0 Series: Part2-Add additional NSX-T Manger & Configure VIP
NSX-T 3.0 Series: Part3-Add a Compute Manager (vCenter Server)
NSX-T 3.0 Series: Part4-Create Transport Zones & Uplink Profiles
NSX-T 3.0 Series: Part5-Configure NSX on Host Transport Nodes
NSX-T 3.0 Series: Part6-Depoy Edge Transport Nodes & Create Edge Clusters
NSX-T 3.0 Series: Part7-Add a Tier-0 gateway and configure BGP routing
NSX-T 3.0 Series: Part8-Add a Tier-1 gateway
NSX-T 3.0 Series: Part9-Create Segments & attach to T1 gateway
NSX-T 3.0 Series: Part10-Testing NSX-T Environment
This is how our logical topology looks like after the deployment.
All topologies in the NSX-T env can be found on NSX Manager UI.
Log into NSX Manager VIP >Networking >Networking Topology
You can filter to check specific object. Like I have filtered it for HR segment.
Export it to have a closer look.
Let’s verify north-south routing in the environment. We need to verify if the HR segment network shows as BGP learned route from 172.27.11.10 & 172.27.12.10 on respective TOR (VyOS) switches.
‘10.10.70.0’ network learned from ‘172.27.11.10’ and this is our Edge uplink1.
‘10.10.70.0’ network learned from ‘172.27.12.10’ and this is our Edge uplink2.
All good. We see the network on our TOR, which means our routing is working perfectly fine. Now, any network that gets added to NSX-T env will show up on TOR and should be reachable from TOR. Let’s check the connectivity from TOR.
Voila, we are able to ping the gateway of HR segment from both TOR. End to End (North-South) routing working as expected.
IF you don’t see newly created HR segment network on the TOR, then you have to check if the route is reaching till your Tier-0 router.
Log into edge03.dtaglab.local via putty.
Enable SSH from the console if you are not able to connect.
We need to connect to Service Router of Tier-0 to check further details. Note that the VRF ID for Tier-0 Service Router is ‘1’
We see ’10.10.70.0/24’ network as t1c (Tier-1 Connected). That means, route is reaching till Edge. If its not, you know what to troubleshoot.
Next, if route is on the Edge and not on the TOR, then you need to check BGP neighborship.
‘get bgp neighbor’
I see BGP state = Established for both BGP neighbor. (172.27.11.1 & 172.27.12.1). If not, then you need to recheck your BGP neighbor settings in NSX manager. Use ‘’traceroute’ command from vrf’s and edge to trace the packet.
That’s it for this series. I hope you enjoyed reading blogs from this series.
Happy Learning. 😊
Are you looking out for a lab to practice VMware products..? If yes, then click here to know more about our Lab-as-a-Service (LaaS).
Subscribe here to receive emails for new posts on this website.