Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2125
  • Last Modified:

VLAN will not work on ESX server

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
damien1234
Asked:
damien1234
  • 5
  • 4
2 Solutions
 
65tdCommented:
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
 
damien1234Author Commented:
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
 
65tdCommented:
Is there an available nic to test with?
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
damien1234Author Commented:
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
 
65tdCommented:
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
 
damien1234Author Commented:
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
 
65tdCommented:
Unfortunately we use cisco switches, so I'm not sure about the HP stuff.
0
 
damien1234Author Commented:
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
 
damien1234Author Commented:
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

How to Use the Help Bell

Need to boost the visibility of your question for solutions? Use the Experts Exchange Help Bell to confirm priority levels and contact subject-matter experts for question attention.  Check out this how-to article for more information.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now