VMware Cloud Community
register
Contributor
Contributor
Jump to solution

Adding VLANs to ESX

ESX 3.02

We currently use 1 subnet (VLAN 1) for all our production network traffic to our VMs. I need to add another subnet to our cluster & just wanted to get some confirmation I'm on the right track:

1. on Ethernet switch, change port connected to vmnic0 to allow trunking & add VLAN 2

2. on ESX host, change VLAN ID on vSwitch0 from * to 1.

3. on ESX host, create new vSwitch1 for VLAN ID 2.

4. on ESX host, assign new VMs using new subnet to vSwitch1.

Is that all there is to it?

TIA

0 Kudos
1 Solution

Accepted Solutions
dkfbp
Expert
Expert
Jump to solution

If you are using a trunk port you need to specify the vlan id. Do not use the *

Best regards

Frank Brix Pedersen

Best regards Frank Brix Pedersen blog: http://www.vfrank.org

View solution in original post

0 Kudos
6 Replies
TomHowarth
Leadership
Leadership
Jump to solution

you could also use port groups, this could be better for you as your appear to have limited pNICs in your host. seperate vSwitches will require seperate pNIC to the physical world

Tom Howarth

VMware Communities User Moderator

Tom Howarth VCP / VCAP / vExpert
VMware Communities User Moderator
Blog: http://www.planetvm.net
Contributing author on VMware vSphere and Virtual Infrastructure Security: Securing ESX and the Virtual Environment
Contributing author on VCP VMware Certified Professional on VSphere 4 Study Guide: Exam VCP-410
register
Contributor
Contributor
Jump to solution

thanks for the reply.

If I understand you correctly, I can only add another vSwitch if I have an unused NIC. I cannot assign 2 vSwitches to the same NIC?

0 Kudos
dkfbp
Expert
Expert
Jump to solution

Hi,

You cannot use two vswitches on one nic. What you described is allmost right. Just don't create another vswitch but create another portgroup on the existing vswitch with vlan id 2






Best regards

Frank Brix Pedersen

Best regards Frank Brix Pedersen blog: http://www.vfrank.org
0 Kudos
register
Contributor
Contributor
Jump to solution

that's great, thank you.

One last ?, does it matter if I leave the VLAN ID on the original vSwitch as *, or is it important I change it to specifiy 1.

0 Kudos
dkfbp
Expert
Expert
Jump to solution

If you are using a trunk port you need to specify the vlan id. Do not use the *

Best regards

Frank Brix Pedersen

Best regards Frank Brix Pedersen blog: http://www.vfrank.org
0 Kudos
register
Contributor
Contributor
Jump to solution

fyi-

I had to leave it as *. When I changed it to 1, I lost connectivity to all VMs on vSwitch0.

0 Kudos