![]() ![]() the post by MikeLascha - "The "real" issue was that 802.1Q tagging was not enabled on the host NIC drivers. Pass vlan traffic tagged via virtual interface on a team which is odd!) It would appear that each physical network card has to have certain settings configured in order for it to correctly pass vlan tags from the virtual switch. I have however managed to get things working on the broadcom cards. Additionally although simalar to our problem, in our case VM's and the management vEthernet adapters do not get any network connectivity at any point when Thanks for the update info, I can confirm that the update is already installed on the server. I'm running all the windows updates on the box right now to see if anything changes. ![]() We have tried this on 3 different physical network cards (broadcom, intel and realtek) with the same results. If I create a team instead of a virtual switch on the physical interface, I can create multiple virtual adapters for all the vlans that are tagged on the switches physical port and each virtual adapter gets connectivity. I believe we also had the same problem the last time we tried tagging vm traffic as well but I can't yet test this. I have tried multiple vlans with the same effect. On the management OS then we no longer get any external connectivity. The management interface works fine and the traffic is going out untagged on the physical NIC as expected and has connectivity. I create a new virtual switch and allow management OS access with no vlan identifier. The test switch is a HP ProcurveĢ810 and i've triple checked all the vlan settings on the physical ports to make sure they are correct. We seem to be having an issue with VLANs when being tagged through the Hyper-V virtual switch. We're currently in the process of testing server 2012 Hyper-V before we upgrade our production cluster this summer. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |