NSX-T Part 10: Configure N-S Routing

In the previous part, we have setup the T1 router and connected all the logical switches with its gateway configured on it. In this part after the Edges are deployed, we will be configuring the N-S routing for VMs to reach the external network.


We have just the T1 router currently available, now we will start with configuring the T0 router.



I have deployed it in Active-standy state as I will be using this setup for future deployment of PKS or Kubernetes.


Next, I connected the T1 router to T0 router.


As seen below, now the T1 router is connected to T0 router.


Next is to connect the Edges upstream to the VLAN network. In the previously setup, we had the VLAN-TZ setup and now we are first adding a VLAN backed logical switch for upstream connecting. As the lab is in a nested environment , VLAN 0 does fine 🙂


Quick summary of the T0 router below.


Next, is to connect the edges upstream with the VLAN logical switch and thus we need to configure the router ports on the T0 router on the below screen.


Below is the configuration output from the VYOS router which is being used for both my NSX-V and NSX-T environment.


Created a new Router port in the below screen, with the ip address used on the same L2 network


Similarly, we configured two router ports as we will be using BGP routing between the VYOS router and edges. We already know that on the standby edge , NSX automatically prepends the AS-Path to make it a less preferred route and thus no changes are required on the upstream router.


Below we do the BGP configuration .



Similarly, we configure the routing for each edge router port.


Next, is to advertise the T1 routes upstream which is the all connected routes.



Quick recap on the logical networks connected to T1.


Next step is to validate the routes on the Active Edge. Firstly, we get the logical router available.


Login to the specific T0 SR component (as SR is responsible for routing N-S)


Check the routes, and we see that upstream and NSX-V environment routes are learnt through the VYOS router.


Below is the neighbor summary of the VYOS router.


This completes the NSX-T setup configuration. In future, I am planning to upgrade this setup to NSX-T 2.4.x release , as there are additional features available on the same.

Hope, this 10 part series was helpful.


NSX-T Part9: Configure Edge Cluster

In this part continuing with the edges configuration, we will configure the edge cluster. Before we create a new edge cluster, an edge cluster profile needs to be used.

There is already a default profile which is available.


However, I created a new Edge Cluster Profile as I do not want to use the default one.



Then I created a new Edge cluster and added both the previously created Edges into the newly created edge cluster.





Post which we bind the edge cluster profile to the edge-cluster profile.


In next part , I will configure the logical routing.


NSX-T Part8: Configure Edge nodes

In the previous part , I got two Edge VM nodes deployed. In this part we will configure them to function as an edge node . The first step is to configure an Edge Uplink Profile.

Initially, I configured the Edge using the earlier created Overlay Uplink profile in which  there was an active and a standby uplink , and was getting the below error .


I had to quickly change that and only configure with one active uplink, posted this for all your information if you run into this issue.

Create a new Edge-Overlay uplink profile


Create a new Edge-VLAN uplink profile.


All the Uplink profiles which are created.


Create a new Transport Zone . As we had already created the Overlay Transport zone for configuring the logical switches, we just need to create a new VLAN-Transport zone.


Configured both the edge-node VMs as a Transport node. Added both the overaly and VLAN transport zone as part of the edge transport zones.


tswitch1 configured for overlay


tswitch2 , new switch created for VLAN outbound connectivity to physical wordl.


Similarly, I configured both the edges as Edge Transport node


In the next part, I will continue with the Edge-cluster configuration.



NSX-T Part7: Add NSX Edge VMs

In the previous part , we have setup the T1 router for the distributed routing (DR) . As said earlier, apart from DR there is a service router or SR component which is responsible for running network services such as firewall,NAT etc. The SR component will only get instantiated on an Edge.

In NSX-T , Edge can be an edge-VM or a bare-metal server edge. Both the type of edges can utilize the DPDK functionality of Intel Nics to use multiple fast-paths , thus  providing better performance. In this, part we will be deploying two Edge VM and using it in Active-Standby due to future integration’s with Kuberntes/PKS.

Click on Fabric > Nodes > Edges > Add Edge VM


We will be deploying the medium size. I had to increase the memory size on my ESXi VMS (as its a nested lab) to be able to run the Edge VMs.



On the DVS , the networks were created which I have shared in my earlier posts.

Management Interface – It is to access the VM

#1 : FastPath Interface 1 : Used for Overlay Tunnel network to receive geneve traffic from other Transport nodes

#2 : FastPath Interface 2: Edge Uplink : Used for Uplink connectivity towards the physical network or vyos router in this environment

#3 : FastPath Interface 3 : This can be used to connect to another physical network , I am not using this in my environment. However, for the deployment to proceed have chosen tunnel network.



Similarly , have deployed the 2nd Edge and connected the Uplink network to EdgeUplink1 .


After the edges are deployed, I have disconnected the #3, interfaces on the VM.


Both the edges are deployed.


Below are the Nic teaming policies on the DVS



In the next, part I will be configuring the edge node as a Transport node.