Virtual Networking in SonicWall NSv
03/26/2020
44 People found this article helpful
443,615 Views
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.
![](upload/images/sonicwall/090180405257922.png)
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:
![](upload/images/sonicwall/090180405701874.png)
The VM Network's topology (Under the Networking section in vSphere Web Client) would look like this:
![Image](https://sonicwall.rightanswers.com/portal/app/portlets/results/onsitehypermedia/090180405725150.png?linkToken=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJzb25pY3dhbGwiLCJleHAiOjE3NTY2MTAzMzQsImlhdCI6MTcyNTA3NDMzNH0.u4JaCcR6RvDDajVs8iPZ97dC8GoTl_GHSaceCbDLME8)
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.
v and the Network Adapter of the Windows Server.
SonicWall NSv's Network Adaptors:
![Image](https://sonicwall.rightanswers.com/portal/app/portlets/results/onsitehypermedia/090180406348379.png?linkToken=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJzb25pY3dhbGwiLCJleHAiOjE3NTY2MTAzMzQsImlhdCI6MTcyNTA3NDMzNH0.u4JaCcR6RvDDajVs8iPZ97dC8GoTl_GHSaceCbDLME8)
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:
![Image](https://sonicwall.rightanswers.com/portal/app/portlets/results/onsitehypermedia/090180406200832.png?linkToken=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJzb25pY3dhbGwiLCJleHAiOjE3NTY2MTAzMzQsImlhdCI6MTcyNTA3NDMzNH0.u4JaCcR6RvDDajVs8iPZ97dC8GoTl_GHSaceCbDLME8)
TIP: Configuring the DHCP Server on the SonicWall
![Image](https://sonicwall.rightanswers.com/portal/app/portlets/results/onsitehypermedia/090180405540699.png?linkToken=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJzb25pY3dhbGwiLCJleHAiOjE3NTY2MTAzMzQsImlhdCI6MTcyNTA3NDMzNH0.u4JaCcR6RvDDajVs8iPZ97dC8GoTl_GHSaceCbDLME8)
Pinging 8.8.8.8 from the Windows Server now shows the packets ingressing on X0, translated to X1 IP and egressing via X1.
![Image](https://sonicwall.rightanswers.com/portal/app/portlets/results/onsitehypermedia/090180405321797.png?linkToken=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJzb25pY3dhbGwiLCJleHAiOjE3NTY2MTAzMzQsImlhdCI6MTcyNTA3NDMzNH0.u4JaCcR6RvDDajVs8iPZ97dC8GoTl_GHSaceCbDLME8)
TIP: Further reading for ESXi Networking Configurations: Create a vSphere Standard Switch, Edit a Standard Switch Port Group, About vSphere Networking
Related Articles
Categories