Add trunking and VLAN IDs to a network with no VLAN tagging set

Hi

I currently have a 3 host cluster VSphere 4 ESXi with two vswitches. vSwitch0 has the VM network and the service console. vSwitch1 is for vMotion. I would like to enable VLAN trunking at the physical Cisco Switch Port and then set vSwitch0 to VLAN ID 17.

My question is how do I go about this properly?

Can you change all the physical ports to Trunk without loss of network connectivity for the VMs?

What happens when all the three hosts vSwitch0 NICs are set to Trunk and there is no VLAN ID set in VLAN ID at the Port Group Properties?

What happens you set the Port Group VLAN ID?

I am guessing you stick a host in maintenance mode (to get all the vms off via DRS). Change the physical NIC (which are part of the VM Network) ports to Trunk mode, add allowed VLANs and because the service console is on the same network probably best to do this from the physical console.

Then on the same host add in the VLAN IDs required into the Port Group. vMotion one test box back to new configured host to check network connectivity and if that works repeat on the other hosts.

Is this right way?

Thanks
herbieheadhuntersAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Tech_StigCommented:
These are the steps I take when converting a single network esx box to a multiple network box.

 - Free up one physical NIC (if NICs are teamed on another vswitch, remove one, etc)
 - Create a new vswitch and add the new nic that you previously freed up.
 - Create a new Virtual Machine port group for each VLAN that needs to be on this box (or at least on this vswitch) Make sure to assign the proper VLAN ID to each port group. Also, make sure to name it something useful (i.e. Prod_VLAN17, etc)
 - Next create a new service console on the new vswitch and assign the proper VLAN ID to this.
 - If you haven't already identified the physical nic and physical port used on your switch, do so now.
 - Set your port on the cisco switch to be a trunk port and allow the proper vlans
 - Test access to your new service console. (note, this should not be the same IP as the old service console. The ip can be changed later if need be.)
 - if everything works, move over one VM at a time and test. Do so by editing the nic settings and select the VM_Network
 - Once everything is moved off the old vswitch you can remove the remaining adapters, service console, and delete the vswitch. Then configure the ports on the cisco switch and add the adapters to the new vswitch.

The only thing I haven't done is do this on a cluster. I'm sure that this would work, the trick is I'm sure that everything needs to be the same (Virtual Port groups named the same across boxes). Also, I would configure the vswitch and all the port groups BEFORE moving any VMs to the new network.


Q: Can you change all the physical ports to Trunk without loss of network connectivity for the VMs?
A: Yes with the above method.

Q: What happens when all the three hosts vSwitch0 NICs are set to Trunk and there is no VLAN ID set in VLAN ID at the Port Group Properties?
A: Only machines\service console in the default vlan network will reach it's destination.

Q: What happens you set the Port Group VLAN ID?
it's just like setting the "switchport access vlan x" setting on a switch. Only difference is that you can have multiple VMs connected to that port group.


0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
vmwarun - ArunCommented:
In order to see Tagged VLAN Frames, you need to set VLAN ID to 4095 on the Port Group.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
VMware

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.