Internal vSwitch routing

[domw001]

I have 2 internal vswitches: one services a 192. network the other services a 172. network. Neither switch has been assigned to a physical NIC.

Does vSphere have any native features that make it possible to route between the 2 networks.

Or is there a simple configuration that may allow this to work.

The solution does not require NAT.

Many thanks

[f10]

In internal vSwitch acts like a Layer 2 switch hence the VM's connected to one vSwitch can communicate with another, however if you want the VM's to communicate across two vSwitch in the same or across different ESX hosts we need to connect uplinks/physical adapters which would connect to an external switch and then route the packet.

Hope this helps !

If you found this or other information useful, please consider awarding points for "Correct" or "Helpful".

f10.

VCP3, VCP4, HPCP, HP UX CSA

[domw001]

I thought as much.

I just wondered if the vSwitch possibly had some rarely-used L3 feature available.

Thanks anyway

[KrishK]

There is no such feature in VMware (Not Sure) .But still you can try this.

1. Assign Two vNics to a VM.

2. Place one vNic in 192 N/W and other in 172 N/W.

3. Make static Routes in the VM's guest OS between these two networks to and fro.

4. Use gateways as the IP's given in these VM's.

Also there are applications (Checkpoint) available which can be installed in Guest OS to route the traffic between VLAN's.

[kac2]

this can be done with a virtual router such as Vyatta or FreeSCO. FreeSCO is much easier to get up and running quickly

[AndreTheGiant]

Welcome to the community.

The right solution is use an external router (/firewall) or a VM (or a Virtual Appliance) with the same function.

But there is also an unsupported mode that works only with the full ESX: if you enable IP routing in the service console, and you add a COS interface on each vSwitch it act as a router for you... And if you add new NAT rule in the iptables configuration can also act as a firewall.

Andre