VMWare VMXNET VLAN Tagging not working, or is it?

I have a server that operates in a VOIP VLAN.  We are virtualizing this server but don't have a physical NIC to devote solely to VOIP traffic on the ESXi server it is going to be running on.  Therefore we need to be able to tag the traffic on the virtual NIC of this VM to go out of the main "LAN" configured NIC of the VMware host server (ESXi box).

As the E1000 driver has no place in its advanced NIC settings (configuring now from the VM side here, which is a 2008R2SP1 server) we've installed a VMXNET3 adapter and set its VLAN ID field to the VLAN ID, in this case "100".  

Now we have 2 problems:  
1)  The network is being recognized as "Public" (love how a "Server OS" would ever think that it is on a "Public" network.)
2)  It can't ping anything on this VLAN, nor can it receive pings from other devices on this VLAN.

This leads me to conclude that this obviously isn't connected to the proper VLAN via the tagging.  The vSwitch this server is connecting to is setup to be just a standard vSwitch for LAN traffic, nothing exciting there.  The Procurve physical switch this is connecting to is accepting tagged packets for this port for the proper domain.

As this issue really only could be related to the either: the vNIC, the vSwitch or the physical switch I'm willing to go over any configuration in any of these areas.

All questions welcome, thanks in advance.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Paul SolovyovskySenior IT AdvisorCommented:
VLAN tagging is done on the vswitch.  You will need to enable the physical switch as a trunk port and create virtual machine port groups on the vswitch that are defined by the VLAN that's associated with it.  You will then need to configure the vswitch with IP HASH so that it can properly send packets to each vlan that is associated with the the virtual machine.

Is this the only VM in the environment and/or being stored on the ESXi host?

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ChocolateRainAuthor Commented:
Is that going to be a problem if this is the same NIC and vSwitch associated with the Management network?
Paul SolovyovskySenior IT AdvisorCommented:
not at all.  Just need to configure a port group for the management network, assign a vlan to it --also enable ip hash on the management network group as well, otherwise there may be an issue I've seen in a VMWare KB.  Create a second port group for the virtual machine network and assing the port group a vlan id as well.  Enable vswitch with ip hash and enable switch for trunking.
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

Paul SolovyovskySenior IT AdvisorCommented:
Another option is to install a network card which are inexpensive these days and save all the hassle.  Just assign the vlan on the physical switch attach to vswitch and all the VMs are on that vlan via bridging..
ChocolateRainAuthor Commented:
Ok so now I've added those VLANs to the default vSwitch (the one entitled LAN) as you recommended.  It works great with one 2008R2 server and is totally not working with the other.  I removed the VMXNET3 vNIC's tagging and just associated it with the proper VLAN through VMWare by pointing it to the correct VLAN in the vSwitch.

I've tried both the VMXNET3 and the E1000 vNIC with the VM that isn't working, neither to any avail.  See the screenshots below.

Paul SolovyovskySenior IT AdvisorCommented:
Is your physical switch configured with trunking on the port connected to the ESX hsot?  Is the vswitch configured for IP HASH?
ChocolateRainAuthor Commented:
Yes, they are both on the same host server and connected to the same vSwitch and same physical ports from that vSwitch to the Procurve switch which the configuration of that looks like the following:
Paul SolovyovskySenior IT AdvisorCommented:
OK, so you have VLANs.  Have you created a Port Group for trunking?

You need to assign a port (or two if you have the nics) to a port group.  Set up the port group to trunk (do not use LACP).  This will allow it to pass more than 1 vlan on the interface.  Otherwise you can only do static vlans per port and it's not going to work.  Show me the interface list.
ChocolateRainAuthor Commented:
Not sure where to config the trunk on the vSphere side.

Paul SolovyovskySenior IT AdvisorCommented:
There's some work involved.  You need to configure the physical switch correctly then you need to configure the vswitch0 correctly (put the VM Network on VLAN 0 as well.  Youw will also need to go into the management port group and confiugre ip hash, otherwise you'll lose conenctivty as well as setting it for vlan 0 (if that's where you have you network on).

It may be a good idea to get a consultant in to do this for you as it will ensure that you get it working correctly.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.