VMware Cloud Community
blvsupport
Contributor
Contributor
Jump to solution

Create a VM in a different VLAN from the ESX Server

Is it possible to create a VM in a different VLAN (Exemple: 192.168.80.5) if my esx server is in another VLAN (Exemple: 192.168.10.206)

Thanks for helping

Reply
0 Kudos
1 Solution

Accepted Solutions
bhadzik
Enthusiast
Enthusiast
Jump to solution

You need to use 802.1q vlan tagging. Here is a Whitewater about it.

http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=http--wwwv...

Much more efficient that physical nics, because you can have many vlans on the same physical cable. When you create a virtual machine network, that is what the field for vlan is used for.

You need to have compatible switches, but most managed switches can do it.

View solution in original post

Reply
0 Kudos
6 Replies
khughes
Virtuoso
Virtuoso
Jump to solution

what we do is have 2 of 6 physical nic ports dedicated to our dmz with our ESX host on the production network. on the esx hosts, we create a dmz vSwitch and assign those vmnics to that switch and then attach the VM's to the dmz network.

Unless I'm missing something, yes it can be done

-- Kyle "RParker wrote: I guess I was wrong, everything CAN be virtualized "
Reply
0 Kudos
blvsupport
Contributor
Contributor
Jump to solution

My physical esx server have thow nic presently

One for my network and the other is for Vmotion

So i would have to installed a new nic? Is it correct ?

Thanks

Reply
0 Kudos
khughes
Virtuoso
Virtuoso
Jump to solution

I don't think you have to install another nic into your server, we just dedicated a couple physical nics to the dmz for security reasons and governing regulations and felt more comfertable with it that way. I can't tell you the exact steps if it can be done without a separate vmnic for that network, it was just a lot easier for us to manage and configure with its own physical vmnic port.

-- Kyle "RParker wrote: I guess I was wrong, everything CAN be virtualized "
bhadzik
Enthusiast
Enthusiast
Jump to solution

You need to use 802.1q vlan tagging. Here is a Whitewater about it.

http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=http--wwwv...

Much more efficient that physical nics, because you can have many vlans on the same physical cable. When you create a virtual machine network, that is what the field for vlan is used for.

You need to have compatible switches, but most managed switches can do it.

Reply
0 Kudos
khughes
Virtuoso
Virtuoso
Jump to solution

what bhadzik said is correct thats what i faintly remembered but didn't want to throw out there without being sure.

-- Kyle "RParker wrote: I guess I was wrong, everything CAN be virtualized "
Reply
0 Kudos
blvsupport
Contributor
Contributor
Jump to solution

Thanks all for your help

Il take a look at that document

Reply
0 Kudos