Solved

Configure physical switch ports for ESXi hosts

Posted on 2015-02-11
4
611 Views
Last Modified: 2015-02-23
I have 5 ESXi hosts and need to connect them to new Meraki core switches. The hosts connect via multiple 1Gbps ethernet cables to the core switches for user access.

Note: The hosts are on a fiber backbone that connect to QLogic FC switches, which connects to the SAN (so no iSCSI in my environment).

How do I configure the physical switch ports where the esxi hosts are connected?
Trunk or access?

If trunk, will I add every possible VLAN that the host can talk to?
If access, I assume it needs to be in the same VLAN as the vcenter server?

Do I need to change anything on the hosts, vcenter or vsphere once I move the hosts to the new switches?
0
Comment
Question by:Paul Wagner
  • 3
4 Comments
 
LVL 117

Assisted Solution

by:Andrew Hancock (VMware vExpert / EE MVE)
Andrew Hancock (VMware vExpert / EE MVE) earned 250 total points
Comment Utility
Yes, create a trunk, by adding multiple physical ports together, and then add all the VLANs to that trunk, and then make sure, you add the VLAN numbers to the virtual machine porrgroups.

You need to change the VLAN numbers on he virtual machine portggroups.
0
 
LVL 3

Author Comment

by:Paul Wagner
Comment Utility
@andrew hancock

virtual machine portgroups - Is that the VLAN I put each VLAN into by changing the NIC or are you talking about adding a virtual network with VLAN assignments to each physical NIC in the configuration tab for each host?
0
 
LVL 3

Accepted Solution

by:
Paul Wagner earned 0 total points
Comment Utility
So here's a problem I found:

Meraki forces a Native VLAN on each trunk port. (ie- allows vlans 1-20 but native will be 20)

If you have VMs that use VLAN 20, you'll have to make sure that VLAN tagging is blanked out (nothing on that line) in vSwitch properties. You can't tag them with VLAN 20 since the Meraki port already has a native vlan of 20. It's kind of like double tagging the packets.

All other VLANs are OK to leave tagged in vSwitch.
0
 
LVL 3

Author Closing Comment

by:Paul Wagner
Comment Utility
Andrew, you were partially right. The VMs that operated on the trunk port native vlan (physical switch) had to have their VLAN ID removed from the port group in the vSwitch or else all packets would be double tagged and the switch drop the packets. All other VLAN IDs worked fine.
0

Featured Post

Find Ransomware Secrets With All-Source Analysis

Ransomware has become a major concern for organizations; its prevalence has grown due to past successes achieved by threat actors. While each ransomware variant is different, we’ve seen some common tactics and trends used among the authors of the malware.

Join & Write a Comment

HOW TO: Install and Configure VMware vSphere Hypervisor 6.5 (ESXi 6.5), Step by Step Tutorial with screenshots. From Download, Checking Media, to Completed Installation.
In this article, I will show you HOW TO: Create your first Windows Virtual Machine on a VMware vSphere Hypervisor 6.5 (ESXi 6.5) Host Server, the Windows OS we will install is Windows Server 2016.
This video shows you how easy it is to boot from ISO images for virtual machines with the ISO images stored on a local datastore on the ESXi host.
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.

762 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

10 Experts available now in Live!

Get 1:1 Help Now