Solved

Configure physical switch ports for ESXi hosts

Posted on 2015-02-11
4
792 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
4 Comments
 
LVL 120

Assisted Solution

by:Andrew Hancock (VMware vExpert / EE MVE^2)
Andrew Hancock (VMware vExpert / EE MVE^2) earned 250 total points
ID: 40604140
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 5

Author Comment

by:Paul Wagner
ID: 40604182
@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 5

Accepted Solution

by:
Paul Wagner earned 0 total points
ID: 40613329
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 5

Author Closing Comment

by:Paul Wagner
ID: 40625341
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

Report: Liquid Web beats Amazon, Rackspace & More

A study by performance analyst firm Cloud Spectator finds that Liquid Web beats rivals Amazon, Rackspace and DigitalOcean when it comes to website and cloud application performance.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

For many of us, the  holiday season kindles the natural urge to give back to our friends, family members and communities. While it's easy for friends to notice the impact of such deeds, understanding the contributions of businesses and enterprises i…
Arrow Electronics was searching for a KVM  (Keyboard/Video/Mouse) switch that could display on one single monitor the current status of all units being tested on the rack.
Teach the user how to install log collectors and how to configure ESXi 5.5 for remote logging Open console session and mount vCenter Server installer: Install vSphere Core Dump Collector: Install vSphere Syslog Collector: Open vSphere Client: Config…
This video shows you how to use a vSphere client to connect to your ESX host as the root user. Demonstrates the basic connection of bypassing certification set up. Demonstrates how to access the traditional view to begin managing your virtual mac…

751 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