Case study: I am seeking help as I am attempting to test the .1Q functionality of Microsoft Virtual PC (only). What I have done is connected a PC w 1gig NIC configured for .1Q tagging and connected it to a Cat 3750 trunk port. I configured 3 VLAN (one per virtual environment) and I created a loopback interface to ping too.
Problem: PING not successful. I am able to see the VLAN tagged on the 3750 and when I show ARP on the 3750 I do see the MAC of the Virtual PC with the correct VLANID but the switch will not route the packet to the LO int. Hence, PING failure. I tried with both no routing and with EIGRP both, to no avail.
Attached is a diagram with info, the IOS is LAN IP not sure version but there are no other config’s on the 3750 it is clean fresh out of the box. I have to use this set as I am limited additional devices due to security policies.
Any suggestions or recommendation would be greatly appreciated. I am leaning towards Microsoft VM the root cause but just not sure. The ping should route and respond.
Now that I think about it, (we did our testing on Fri) we never did set up the virtual pc's we started with just trying to get the PC itself ping either the vlan (default gateway ip) or the lo int ip. Both to no avail. One question I thought of is I am wondering if there is a issue with facing a trunk port and a NIC interface together, and something getting scrambled in the middle? In most cases one would not interface a trk to a pc it would be an access port. Could this fact be an issue, that you can think of? Microsoft PC is a 2007 application no one really does what I am attempting to do, in this fashion most enterprise environments would use a VMware 4.0 Hypervisor but we have a fire-wire requirement and VMware does not support fire-wire interfaces at this time. Your help is greatly appreciated!
Had a quick trawl through technet and google and i can't find any mention of virtual PC supporting 802.1q. I can find mention of something called HyperV which seems to be used for server virtualisation and this can support 802.1q tagging.
If your NIC supports 802.1q tagging and for this you need to check the NIC vendor support site then i don't think your issue is with the NIC or the 3750, assuming they have been configured properly but rather with the virtual PC software. It may be worth posting a question on technet to see if they know if virtual PC works with 802.1q tagging.