Link to home
Start Free TrialLog in
Avatar of DP230
DP230Flag for United Kingdom of Great Britain and Northern Ireland

asked on

Changing VLAN in VMware network

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!
ASKER CERTIFIED SOLUTION
Avatar of Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of DP230

ASKER

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
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.
Avatar of DP230

ASKER

Hi Andrew, I setup a test system like this:

User generated image
After installed the ESXi hypervisor, I setup the management network in VLAN 4095, IP address: 192.168.50.100

User generated image
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?

User generated image
User generated image
User generated image
4095 is a special VLAN for ALL VLANs, your ESXi Management network should be in a VLAN.

did you create a virtual machine portgroup.
Avatar of DP230

ASKER

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?

User generated image
what is the configuration on the Cisco Trunk ?
Avatar of DP230

ASKER

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

User generated image
Do I have to configure the network cable from Access switch to ESXi host as Trunk connection?
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.
Avatar of DP230

ASKER

Hi, the trunk links already had all VLANs:

User generated image

I got this screenshot from vsphere document.

User generated image
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)?
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.
Avatar of DP230

ASKER

User generated image
User generated image
Yes you are correct, after changed all physical links to trunk configuration, Management vlan to 50, it worked!

Many thanks for your suggestions!