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.