Solved

VLAN will not work on ESX server

Posted on 2008-10-27
9
2,109 Views
Last Modified: 2012-05-07
I created a new port group attached to vSwitch1 with a VLAN ID of 4.  I have a guest machine that I moved from VLAN 3 to this new port group.  The guest machine can not talk to ANY computer on it's network although it can ping itself.  I get a "destination unreachable" when I try to ping anything else. If I move the guest back to VLAN 3 and redo the static IP everything works fine.

I've got VMWare ESX Server v3.5 and an HP Procurve 2848 switch.  I want to have multiple VLAN's on the ESX server. I have 3 NICS in a Link Aggregation Group with VLAN tagging enabled.  All servers virtual and physical on VLAN 3 can talk to each other and VLAN 2 no problemo.  The new VLAN 4 simply does not work!  The only other device on VLAN 4 is my router.  I can ping that router from any machine virtual or physical EXCEPT from the machine in this new port group (VLAN4)

I ran "esxcfg-vswitch -l" and everything looked perfect.  I've rebooted the host to no avail.
0
Comment
Question by:damien1234
[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
  • 5
  • 4
9 Comments
 
LVL 22

Assisted Solution

by:65td
65td earned 400 total points
ID: 22820900
Ensure the port on the switch side is set up correctly for VLAN4.

Has this document been reviewed:
http://www.vmware.com/pdf/esx3_vlan_wp.pdf

0
 
LVL 1

Author Comment

by:damien1234
ID: 22821947
I have an untagged port on VLAN4 connected to the router.  The only real difference between Vlan4 and Vlan3 is the Link aggregation group connected to the ESX server is on VLAN3, but it is tagged.
0
 
LVL 22

Expert Comment

by:65td
ID: 22822141
Is there an available nic to test with?
0
Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

 
LVL 1

Author Comment

by:damien1234
ID: 22822319
Yeah... I suppose I could remove one of the NIC's, create a new Vswitch and port group, and have all that live exclusively on VLAN4.  I was also thinking about moving another VM to the VLAN4 portgroup and testing whether the two VM's can ping each other.
0
 
LVL 22

Expert Comment

by:65td
ID: 22824149
Just a thought, take one nic and use it for testing vlan4 and ensure that vlan can communicate with the rest of the network.

Moving a VM would be quick enough, I almost think they will ping each other.
0
 
LVL 1

Author Comment

by:damien1234
ID: 22831759
When I added another VM they could ping each other.  After I took a NIC and put this VM by itself everything worked fine.  I rebuilt the trunk (Link Aggregation Group) and added it to VLAN 3.  I did notice something funny in the switch though.  I can make a trunk and tag the trunk ports and join them to VLAN3, BUT the trunk also shows up as untagged in the default_vlan 1.  How can it be tagged and live on vlan3 AND be untagged and live on Vlan 1?  Is this default behaviour for the HP Procurve 2848?  I have installed the most recent firmware and I am following instructions created by HP regarding the creation of Link Aggregates and VLAN trunking.
0
 
LVL 22

Expert Comment

by:65td
ID: 22833295
Unfortunately we use cisco switches, so I'm not sure about the HP stuff.
0
 
LVL 1

Author Comment

by:damien1234
ID: 22835482
I made the assumption this was default behaviour which led me to the question "Do I need to specifically grant a link aggregate group rights on a VLAN?"  So I created a dummy group called TRK5.  I created a dummy VLANs 5 & 6.  I joined TRK5 to BOTH VLANS.  Now TRK5 shows up as a tagged port under each vlan in the switches GUI.  It also explains why the aggregate groups show up under the default vlan since that is usually used for various switch business.  Tonight I will test this setup on my real vlans and see if it works..... I have a feeling it will.
0
 
LVL 1

Accepted Solution

by:
damien1234 earned 0 total points
ID: 22836876
Success!  A Link Aggregration Group (LAG) (HP calls them trunks) on a procurve switch must be added to every VLAN for which it will receive traffic despite the fact that the ports are tagged for any given VLAN.  Additionally each trunk (LAG) is automatically set to "No" for each VLAN created or configured and must be manually changed to "Tagged" or "Untagged".  This must be done from the console.
0

Featured Post

NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

Question has a verified solution.

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

HOW TO: Upload an ISO image to a VMware datastore for use with VMware vSphere Hypervisor 6.5 (ESXi 6.5) using the vSphere Host Client, and checking its MD5 checksum signature is correct.  It's a good idea to compare checksums, because many installat…
Giving access to ESXi shell console is always an issue for IT departments to other Teams, or Projects. We need to find a way so that teams can use ESXTOP for their POCs, or tests without giving them the access to ESXi host shell console with a root …
Advanced tutorial on how to run the esxtop command to capture a batch file in csv format in order to export the file and use it for performance analysis. He demonstrates how to download the file using a vSphere web client (or vSphere client) and exp…
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.

739 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