Hyper-v Private VLANs

Anton.P 0 Reputation points
2023-04-16T19:20:00.5366667+00:00

Hi, im trying to get Private vlan to work in hyper-v with little success. Normally when i have this requirement i use Esxi where this has been a nobrainer as long as i remember..

Anyway according to Docs this should work and looking at traffic on testclient i see traffic from primary vlan but nothing comes back from privatevlan.

This works with equipment all over for physical devices but not for our hyper-v hosts.

Aruba Switch is configured like:

  private-vlan primary
  private-vlan isolated 120

VM configured like:

Set-VMNetworkAdapterVlan -VMName "W11 | TESTCLIENT" -PrimaryVlanId 20 -Isolated -SecondaryVlanId 120

As stated looking at wireshark i see broadcasts from vlan 20 on the client but nothing comes back.

Ports to host's are full trunks..

Do i need to change something with the vmswitch ?

There are very little information about this looking on the net.

Windows for business | Windows Client for IT Pros | Storage high availability | Virtualization and Hyper-V
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Limitless Technology 44,766 Reputation points
    2023-04-17T14:14:51.8366667+00:00

    Hello there, Have you noticed anything in the event viewer? Hyper-V has the capability of supporting the following Private VLAN port types: Promiscuous: This type of port is permitted to communicate to any other port within a PVLAN including Isolated and Community Isolated: This type of port is only permitted to communicate to Promiscuous ports within a PVLAN and cannot communicate other Isolated ports or Community ports Community: This type of port is permitted to communicate with any other Promiscuous or Community port within the PVLAN Hope this resolves your Query !! --If the reply is helpful, please Upvote and Accept it as an answer--


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.