Virtual Networking in SonicWall NSv

03/26/2020 39 10810

DESCRIPTION:

This article details the steps involved in setting up a Virtual Network, with the SonicWall NSv deployed between the Virtual Machines and the Internet.

RESOLUTION:

Typically, the SonicWall NSv is deployed between your internal network and a network with Internet access, therefore the Interfaces connected to your LAN network (X0, for example) would be mapped to the vswitch port of your LAN network, and the WAN Interface (X1, for example) would be mapped to the vswitch port of your WAN network.

NOTE: The default WAN Interface, SONICOS_X1 is set to DHCP by default and HTTPS management is enabled. The default LAN Interface, SONICOS_X0 is set to 192.168.168.168/24 by default.

In this article, the SonicWall NSv would be deployed between a Windows Server and the Internet. Both the NSv and the Windows Server are already deployed in VMware ESXi 6.5 with default networking configurations.

Environment: VMware vSphere Web Client 6.5, Windows Server 2016, SonicWall NSv. 

 By default, all the network adapters would be using the default VM Network in both the NSv and the Windows Server.

SonicWall NSv's Network Adaptors: 

  NOTE: Each Network Adapter (1-8) corresponds to Interfaces X0-X7 on the NSv. 

Windows Server's Network Adapter: 

 The VM Network's topology (Under the Networking section in vSphere Web Client) would look like this: 

 In a Physical Network, in order to connect devices to the X0 interface of the SonicWall, the devices need to be connected to a switch, and then to X0. The same topology applies to Virtual Networks as well. Currently, both the Windows Server and the NSv are connected to the same Virtual Switch, and out to the Internet. Another Virtual Switch is needed to connect the Windows Server to X0 of the NSv.

A new Virtual Switch can be created under the Networking section of ESXi as follows: 

 A Port Group is a essentially group of ports on a vSwitch, created to provide logical segmentation. A Port Group connects to a vSwitch, and a vSwitch connects to a physical network interface. In this case, Port Group "X0" is added and assigned to the Virtual Switch. 

 To connect to a network, a device must have a network interface controller (NIC) or network adapter, installed. The network adapter enables the device to interface with a network. 

So, the Port Group "X0" is assigned to the Network Adapter 1 (X0 Interface) of the NSv and the Network Adapter of the Windows Server. 

SonicWall NSv's Network Adaptors: 

 Windows Server's Network Adapter: 

 Now, the Windows Server would be in the same subnet as X0 of the NSv. The topology of the new Virtual Switch would be as follows: 

 With the Windows Server configured to obtain an IP address automatically, DHCP is enabled on the SonicWall for Interface X0 to confirm that the Windows Server obtains a lease. 

TIP: Configuring the DHCP Server on the SonicWall

 The Current DHCPv4 Leases on the SonicWall now includes a lease for the Windows Server, assigned from the X0 Interface. 

 Pinging 8.8.8.8 from the Windows Server now shows the packets ingressing on X0, translated to X1 IP and egressing via X1. 

 Similarly, Virtual Switches can be added to network adapters on the NSv and virtual machines in your network to configure your Virtual Network.  

TIP: Further reading for ESXi Networking Configurations: Create a vSphere Standard Switch, Edit a Standard Switch Port Group, About vSphere Networking