Question on ESXi VLAN Networking

Posted on 2011-04-21
Last Modified: 2012-08-14
We have a Dell M1000e enclosure housing several M710 blades, that we are in the process of setting up vSphere ESXi  4.1 upon.

We have created Etherchannel trunks that go from our core switch (Cisco 4500) to the blade switch (Cisco 3130G), and can ping the maintenance ports and the VMotion ports (VLAN IDs 50 and 60 respectfully). However we can not reach a test server we have bulit on the first ESXi  host, which had an IP address on the subnet (VLAN ID 1) like the rest of the network..

It is our understanding that the VLAN ID 1 is dropped if it is our Native VLAN ID, which is what we originally had tried to use for the VM Network so It was moved to VLAN 10 and we find now can ping it from the blade switch, so that looks to be the first step in establishing communications. However how would we go about not causing ourselves a lot of pain attempting to bring the rest of existing network onboard with this change? Are we missing something very basic here that we are overlooking?

Thanks in advance!

Question by:j2luce
    LVL 16

    Expert Comment

    Using native/default VLAN is not a recommended configuration

    Configuring Network Switches for VLAN Tagging (

    Sample VLAN configs

    Author Comment

    So in order to solve this. WHat I initially thought was correct. We will need to reset the core switches to NOT use the default VLAN, but whatever VLAN we would select to run the ESXi on?.
    LVL 16

    Expert Comment

    the management network interfaces should be on the same VLAN as the vCenter server and maybe any other systems that will monitor the hosts.  Some shops just have a "server" VLAN that management traffic is on and that is fine in most situations, too..
    LVL 3

    Expert Comment

    I am doing a similar setup so it should be possible. Im not familiar with the M1000e.

    Have you tried using DHCP in the interface on the VM? Do this till everything works.

    The vlan tagging is dropped on the native VLAN. It is recommended that you do not use the native vlan for regular traffic. There is extra communication between switches on the native VLAN. of course VLAN 1 is native by default. You can change the native to any other VLAN you chose and leave your current VLAN 1 and IP scheme alone, or you can create a new VLAN for client/server traffic(I prefer to separate these) and change the VLAN 1 IP settings to the new VLAN and change your switch ports to the new VLAN. Or you can just leave it how it is, which is the exact same way I do it.

    The first step is to make sure that the ESXi host is getting the VLAN 1 network. How did you do this? An access port on VLAN 1? A trunk that allows VLAN 1?

    Next, look in ESXi and make sure that it is taking VLAN 1. I haven't trunked to a ESXi box, but could help you with it if thats what you did. If it's an access port, just make sure it shows in the networking tab of the host, set as DHCP for testing. Also rename the network from the default name.

    Then make sure that you are setting the network card to the correct VM Network. You can find this in the VM settings under the first tab IIRC.

    Let me know if this helped.

    LVL 3

    Accepted Solution

    Just for any one reading this, you change your native VLAN on trunk ports. You must do this on both switches.


    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    Why You Should Analyze Threat Actor TTPs

    After years of analyzing threat actor behavior, it’s become clear that at any given time there are specific tactics, techniques, and procedures (TTPs) that are particularly prevalent. By analyzing and understanding these TTPs, you can dramatically enhance your security program.

    This article is focussed on erradicating the confusion with slash notations. This article will help you identify and understand the purpose and use of slash notations. A deep understanding of this will help you identify networks quicker especially w…
    In the world of WAN, QoS is a pretty important topic for most, if not all, networks. Some WAN technologies have QoS mechanisms built in, but others, such as some L2 WAN's, don't have QoS control in the provider cloud.
    Teach the user how to convert virtaul disk file formats and how to rename virtual machine files on datastores. Open vSphere Web Client: Review VM disk settings: Migrate VM to new datastore with a thick provisioned (lazy zeroed) disk format: Rename a…
    Teach the user how to use configure the vCenter Server storage filters Open vSphere Web Client:  Navigate to vCenter Server Advanced Settings: Add the four vCenter Server storage filters: Review the advanced settings: Modify the values of the four v…

    794 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

    15 Experts available now in Live!

    Get 1:1 Help Now