In my previous NSX articles we covered installing and configuring NSX, We discussed deploying/configuring Transport Zones, Logical Switches, Logical Routers, Edge Gateways, and connecting the Logical and Edge Gateways. With all these completed we now have an environment that with the appropriate routes and transport traffic from our physical network to our logical networks that we deployed. The missing price is the routes. We could go and configure a bunch of static routes throughout all the NSX routers and our physical routers, but that wouldn’t be fun. It also wouldn’t be automated. In this post I am going to walk through configuring the NSX routers to use OSPF for route distribution.
This article builds on my previous article Deploying an Edger Gateway. In this article we are going to connect the Edge router we deployed in my previous post to the Logical Router we deployed in the post Deploying Logical Distributed Routers. In order to link these together we will need to deploy a Logical Switch to be used as a transit network between the Edge Gateway and the Logical Router.
Connecting the Logical and Edge Router
So far we have deployed (2) Logical Switches and (1) Distributed Logical Router and deployed a VM on to each logical switch. Our VM’s can communicate with each other across the Distributed Logical Router, but they can’t communicate to anything else. What we now need to do is deploy an Edge Gateway that we will configure to communicate upstream to the physical network and downstream to the logical network. Where we could technically just connect the Distributed Logical Router upstream to your physical network, it’s not really a best practice approach and it’s not a supported approach when integrating with vCAC.
NSX Logical Switches can be looked at as the equivalent of a virtual VLAN. They identify the networks that you will be connecting your virtual machines to that ride over your VXLAN Transport Zones. Each Logical Switch is assigned a Segment ID that is similar to a VLAN ID. The difference is the packet encapsulation. Each of the exercises I will be writing build on top of the previous. If you are reading this and are looking for the preceding articles click here.
During this walk-through you are going to configure (2) Logical Switches that we will use in a later article where we are going to configure Logical Routing. For this article we will only be configuring the Logical Switches.
In my previous article I walked through configuring Transport Zones. I’m going to be using the Desktop Cluster Transport Zone that I created in that article. I will be creating (2) Logical switches in the MoaC Lab Attached the Desktop-Transport-Zone.