VM networking setup

[vedaB]

Hi Team,

I am not strong at networking area.Can some one guide me on how to configure an appliance VM that  needs  needs two physical Ethernet ports on its own, one port for WAN (local SonicWall), the other port for LAN connect.

I have got one physical NIC connected to esxhost as of now.

Do i need to add one more physical nic to the esx and create a standard switch to make another uplink?

Thanks  & Regards

Veda

[Steven4x4]

First:

Open vSphere and connect to your ESXi Server.

Click the Configuration tab.

Click Networking.

By default you should usually have vSwitch0 which contains VM Network, Management Network and any VM's you've setup..

...You can keep this as the "LAN" side of your network, just note its called "VM Network" by default ---- You can rename it to "LAN" if you want.

Now to setup you WAN:

In the top right hand corner click "Add Networking..."

Click Next (with "Virtual Machine" Selected).

Select the Network Card you want to use for you WAN and click next. (Make sure you don't have both network cards selected).

For the "Network Label:" field - You will probably want to enter "WAN" or whatever you want to call your outside/internet network.

Click next until your finish.

You should now see vSwitch0 as describe above and vSwitch1 below it with the network label your provided.

Note the physical adapters on the side of each vSwitch should be different ... Example vSwitch0 should have vmnic0 and vSwitch1 should have vmnic1 or vice versa, but both network adapters should NOT be attached to the same vSwitch.

Adding the WAN to your Firewall:

Right click your Firewall VM

Click "Edit Settings".

1 Network Adapter should be show by default.

Click the "Add.." button (so we can add the second network adapter)

Select "Ethernet Adapter" and click Next.

You can keep the Adapter Type as "VMXNET 3" unless you prefer something different - its the default.

Now Make sure you now set the Network Connection to "WAN"  - (the vSwitch you just setup).

Then click next until your finished.

Then you'll boot up your Firewall and configure it accordingly..

PS.  --  I'm curious -  Is Sonic Wall Free for Home Use?

I currently use Sophos UTM Firewall in a VM in the configurations I just described.

[vedaB]

Hi Steve,

Thanks for your reply.I am trying to setup in prod environment  for our client. Currently I could see internet attached to the sonic wall(WAN )  which is acting as a gateway/firewall and this WAN connects in turn to the router LAN(LAN).

The requirement is to setup cloud bridge appliance(ova) on ESXi  with two physical nics.(one nic connected to LAN and other connected to WAN).

As of now i have connected ESXi to LAN (i.e vswitch0) and created cloud bridge appliance with one nic connected to vmnic0 .I have added another nic now that should point to WAN network.

setting up vswitch1 connecting to WAN is bit confusing for me at the moment. Since WAN in turn connects to the LAN network ,I am unsure how to set WAN connectivity to point to the vmnic1 now.

Please advise..

Do i need to make a WAN connection from sonicwall to ESX as vmnic1 to achieve this task?  or just add another physical NIC from LAN to ESXi will achieve this ?

Will it creates confusion to the existing gateway?

just as a summary i would like to know what should be the physical setup to make vmnic1 to the ESXi?

Thanks & Regards

Veda.

[Steven4x4]

I'm not familiar with "CloudBridge" -- So lets see if I can get a better understanding of what the requirements are...

I understand that you have SonicWall Firewall. This is a physical device. I'm assuming this directly connected to the internet and possibly has a router between it and the DMARK.

So what devices reside behind this firewall (along side of this CloudBridge)? Just the LAN? Regular internal PCs, Servers, Printers, and other network devices? Are any of these publicly accessible?

You have an ESXi server with 2 NICs. You have (or are going to have) a VM running on this CloudBridge software (I don't know if it is it's own OS, or if its software that gets installed on top of a Windows or Linux OS).

So this device needs to be apart of your LAN functioning like any other computer/server on the local network - right?

I'm not quite understanding the need for the 2 Network WAN and LAN for ClientBridge.

Does the ClientBridge need to be public accessible?

Does the ClientBridge need to be apart of the network - like a normal PC/Server would be (or does it need to be separate).

Does anything need to be connected behind the ClientBridge?