Changing VLAN in VMware network

DP230
DP230 used Ask the Experts™
on
Dear Wizards, currently in our network, ESXi hosts are connected to Core switch on VLAN 55, then all the VMs inside the hosts are in that VLAN. If we like to configure trunk link between Core switch and ESXi hosts (so that VMs can be in different VLANs), what should we change ?
Many thanks!
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017
Commented:
Do you want to keep VLAN 55 or just change it ?

if you just want to change it from 55 to 44 (example), then replace the number 55 on the virtual machine portgroup, and also change the Cisco switch configuration from 55 to 44.

if you want to keep VLAN 55 and add a new VLAN...

You need to add

1. create a new virtual machine portgroup with the correct Tag Number to the existing vSwitch, the uplinks (physical nics) are connected to the Cisco switch.

2. You need to change all the VMs to this new portgroup.

3. Add new VLAN to Cisco switch configuration
DP230Network Administrator

Author

Commented:
Hi Andrew, yes I'd like to add more VLANs

But if we add a new port group to the existing v-switch, will it require any downtime? Since there is only one physical interface from ESXi host to the Core switch.

How about this plan? Will it require any downtime ?
- Connect one more physical interface from ESXi host to Core switch
- Configure that interface as TRUNK link from Cisco view
- Add a new vSwitch on that interface from VMware view
- Create a new virtual port group on that vSwitch
- Move VMs to that new port group and change their IPs so that VLANs are correct
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
But if we add a new port group to the existing v-switch,

No downtime required.

Since there is only one physical interface from ESXi host to the Core switch.

Single point of failure. Why one one, should be at least two physical interfaces.

How about this plan? Will it require any downtime ?
- Connect one more physical interface from ESXi host to Core switch
- Configure that interface as TRUNK link from Cisco view
- Add a new vSwitch on that interface from VMware view
- Create a new virtual port group on that vSwitch
- Move VMs to that new port group and change their IPs so that VLANs are correct

Any networking tampering of this magnitude can cause downtime, so my advice complete out of core hours.
Ensure you’re charging the right price for your IT

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

DP230Network Administrator

Author

Commented:
Hi Andrew, I setup a test system like this:

network_diagram.png
After installed the ESXi hypervisor, I setup the management network in VLAN 4095, IP address: 192.168.50.100

management_network.PNG
and connect 2 other cables from ESXi host to Access switch, however when I add a new vSwitch and new portgroup, the Active port is showing 0. Can you please suggest?

esxi_nic.PNG
AddUplink.PNG
zero_activePort.PNG
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
4095 is a special VLAN for ALL VLANs, your ESXi Management network should be in a VLAN.

did you create a virtual machine portgroup.
DP230Network Administrator

Author

Commented:
Hi, I created a new port group "Group#18" in the same vSwitch0, created a VM and assign to this port group but that VM could not go to Internet. Can you please advise?

portGroup.PNG
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
what is the configuration on the Cisco Trunk ?
DP230Network Administrator

Author

Commented:
Hi, if you are asking about the trunk connection between Access and Core switch, here it is:

trunk.PNG
Do I have to configure the network cable from Access switch to ESXi host as Trunk connection?
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
where are the commands, to configure the trunk the VLANS it has ?

all the links, need to be configured with the VLANs

normally you would create a static trunk with two ports, and configure all the VLANs down those trunks.
DP230Network Administrator

Author

Commented:
Hi, the trunk links already had all VLANs:

trunk.PNG

I got this screenshot from vsphere document.

vNIC.png
If I understood you correctly, vminc0,1,2 should be configure as Trunk link from Switch view, am I right?

In case of that, which VLAN should I configure for EXSi management? 4095 or specific number (ie: 50)?
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
I don't know which ports the server is connected to,  and you need to decide what Management VLAN the Management Interface should be in.

What is your Management VLAN ? is it 50, if it is, then 50 should be the VLAN number.
DP230Network Administrator

Author

Commented:
esxi_vSwitch.PNG
vm1.PNG
Yes you are correct, after changed all physical links to trunk configuration, Management vlan to 50, it worked!

Many thanks for your suggestions!
Andrew Hancock (VMware vExpert / EE Fellow)VMware and Virtualization Consultant
Fellow 2018
Expert of the Year 2017

Commented:
no problems.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial