see this TechNet article for trunking VLANs http://technet.microsoft.com/en-us/library/hh848475.aspx. Chapter 6 Understanding Private VLANs in Hyper-V and VMM, including the PowerShell cmdlets Private VLANs (PVLANs) divide a typical VLAN into sub-VLANs while maintaining the IP subnet and Layer 3 configuration. Each sub-VLAN can become its own isolation boundary based on the port type. 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 PVLANs separate traffic at Layer 2. The following diagram describes the port types: PVLAN Community Isolated cannot communicate Community Isolated can communicate can communicate Promiscuous Unfortunately System Center 2012 R2 Virtual Machine Manager only supports Isolated PVLANs. Implementing Network Isolation in Hyper-V Getting ready In this recipe you will be creating additional VLANs in VMM and will require a new VLAN ID and subnet. Additionally a PVLAN will be created. How to do it... The following diagram shows you the high-level steps involved in this recipe: Overview of Recipe: Prerequisites (not covered by this recipe): Determine which VLAN IDs to create in VMM Actions: Creation of a Logical Network for PVLAN Isolation Creating of a Logical Network Site with 1 VLAN Creating 1 VM Networks for VLAN Creating of 4 VMs in one of the VLAN Demonstrations of the variety of PLVAN in Hyper-V Now perform the following steps: 1. Open the VMM Console and navigate to Fabric I Networking I Logical Networks. You should have six Logical Networks listed, as shown in the following screenshot: Logical Networks and IP Pools (6) Network Compliance TAY External (NAT) Full