Part 4: VMWare NSX Logical Switching and DLR Configuration

This post will cover the Logical switch creation and deploying DLR with control VM as we will use dynamic routing for routing between the DLR and Edge appliance.

To make it easy this series is split in to 5 parts.

Part-1 : VMWare NSX Manager 6.4.x Installation and Initial Configuration

Part 2: VMWare NSX 6.4.x Micro-Segmentation Configuration steps

Part 3: VMWare NSX Cluster preparation and Controllers Installation

Part 4: VMWare NSX Logical Switching and DLR Configuration

Part 5: VMWare NSX EDGE and OSPF Routing Configuration

Introduction

Below picture will clearly illustrates the scenario of the deployment.

 

Logical switch creation

Now as the VTEP’s are configured and VXLAN is working based on our previous post. Will create logical switches and DLR for logical switches gateway.

Navigate to vCenter web – Network and security – Logical switches – Click on + sign to add a new logical switch as shown below.

Provide the Name of the Logical switch and select the replication mode.

Web-LS

Similarly create 4 more logical switches as shown below.

  • Web-LS
  • App-LS
  • DB-LS
  • Transit-LS
  • HA-LS

The logical switches can be seen in the Distributed switch as well.

Deploy NSX DLR and Control VM

Next will deploy NSX DLR and Control VM.

Note: we no need to deploy control VM is static routes are in use. Control VM is required only if dynamic routing like OSPF and BGP is required.

Select NSX Edges – click on + sign

Select Logical Router – Provide Name and Host Name ( vm Name) – select deploy NSX edge appliance (control vm) – select enable HA if deploying for production- Next

If you want to use static routed between DLR and edge no need to deploy Edge appliance.

provide user name and password for edge appliance login , enable SSH

 

Next step Click on + Sign , select the resource pool information to deploy control VM ( edge appliance)

Review and next

Now we need to configure interfaces

Click on + sign under configure interfaces – Provide Name for uplink and connect to tranit-LS – provide IP for this interface as shown below and netmask.

Note: this transit interface will be connected on the other end with Edge appliance in next post. we are using IP 192.168.8.2 for this interface.

Similarly create 3 mote internal interfaces for web, app and DB. This will act as gateway for all the VM’s connected to that LS.

In my case web is 172.16.10.1 , App 172.16.20.1 and DB 172.16.30.1

Finally click on change at HA interface and select the HA-LS created before. No need to assign IP as NSX will assign internal IP range to it.

Now default gateway is the gateway address of my NSX EDGE which will be 192.168.8.1 ( this will configure in next post)

review and finish.

Now we can see that the DLR is deployed

On the DLR VM we can see that it is having all 4 interfaces and its IP’s assigned to it.

 

Hope this post is useful and in next post will configure NSX EDGE and routing.

Below are the complete list of posts part of the series

Part-1 : VMWare NSX Manager 6.4.x Installation and Initial Configuration

Part 2: VMWare NSX 6.4.x Micro-Segmentation Configuration steps

Part 3: VMWare NSX Cluster preparation and Controllers Installation

Part 4: VMWare NSX Logical Switching and DLR Configuration

Part 5: VMWare NSX EDGE and OSPF Routing Configuration

Hope this post is useful, please leave your comments and feedback.

Siva Sankar

Siva Sankar works as Solution Architect in Abu Dhabi with primary focus on SDDC, Automation,Network Virtualization, Digital Workspace, VDI, HCI and Virtualization products from VMWare, Citrix and Microsoft.

2 thoughts on “Part 4: VMWare NSX Logical Switching and DLR Configuration

  • July 27, 2019 at 7:20 pm
    Permalink

    hi
    could you please elaborate role of HA logical switch. what is its significance for HA. how this logical switch play a role in ha

    Reply
    • July 27, 2019 at 7:53 pm
      Permalink

      Dear

      HA logical switch is used for status exchange between the active and standby edge nodes. It doesn’t need a gateway as those info exchange will happen with internal ip range.

      Thanks
      Siva

      Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

Show Buttons
Hide Buttons