Please help with routing and vlan as VM can not get on the internet

[air-wolf]

Folks, I really need some help on the routing an vlan.

The esx I have current in the subnet of 192.168.2.x sub mask 255.255.255.0 GW: 192.168.2.1 DNS:192.168.2.12 & 205.152.37.23

GW: 192.168.2.1

service console is 192.168.2.10

vmkernel is 192.168.2.7

esx have 2 nics:

one for a group of server without any vlan assigned to it for production using subnet 192.168.2.x without any vlan assigned.

I created a virtual swith (vswitch1) as vlan 10 and assigned esx physical second nic for subnet 10.0.0.x . This subnet vlan 10 is for testing and development purpose

I built a VM machine assigned vlan 10 nic within the ESX server and assigned the following IP to VM machine but I am unable to ping the outside world or get on internet.

IP: 10.0.0.9

submask: 255.255.255.0

GW: 192.168.2.1

DNS: 205.152.37.23

*_How can I get, the VM machine to able to get on the internet? I have vm machine in the none vlan of subnet 192.168.2.x get on the internet w/o any problem._ *

[AndreTheGiant]

Do you have the same VLAN ID also in your physical switches?

Andre

**if you found this or any other answer useful please consider allocating points for helpful or correct answers

[weinstein5]

What you need is a router that can route traffic between your vlan and the gateway on the 192.168.2 network - also on your physical switch did you define the vlane id?

If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful

[air-wolf]

actually, on the physical switch there is no define on vlan at all.

so I must have a physical router and vlan id define in the switch? I thought, we can using the ESX vswitch to do the routing and vlan.

[AndreTheGiant]

ESX is not able to handle the routing for your VMs.

And VLAN ID is just a tag. It must be the same on each switch, and you must enable the port of your physical switches to permit this ID.

Andre

**if you found this or any other answer useful please consider allocating points for helpful or correct answers

[Lightbulb]

If you just want to setup a test envoroment in ESX you could use a virtual router

Check out this DOC on using vyatta router for this very pupose

http://communities.vmware.com/docs/DOC-9617

[air-wolf]

ah, thanks i give that a try and see how is turn out as I just don't see why I should need a physical router/switch for this as everything is virtual in the esx.

[weinstein5]

As Andre pointed out - natively ESX does support routing - the virtual switches are layer two devices and so therefore can not route - you can create a VM that will act as a router - FreeSCO is a Linux based router that works within a VM - either way you will need to configure your physical switch to handle the vlan tag -

If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful

[Lightbulb]

I was just thinking that if the poster just wants an internal "test" network there is no need for a seperate VLAN per se as an Internal only switch could hosts the VMs on the 10.0.0.x network and be linked to a vswitch that has an uplink with the production network using a routing applience. This pretty easy to do and no physical switch or VLAN configs are needed.