tionality. It is recommended to use the following names for each of the additional VMs: PVLAN190- 2 PVLAN190- 3 PVLAN190- It is advised to have all of these VMs on the same Hyper-V host unless your networking equipment has been configured with the same PVLANs and is PVLAN-capable. 21. Once the VMs have been deployed to the Hyper-V hosts, open a PowerShell console on the VMM server. Note that this does not need to be an elevated PowerShell console. 22. Once you have opened PowerShell, type in Enter-PSSession HYPVCH1 and press Enter (where HYPVCH1 is the name of the Hyper-V host where PVLAN190-1 is running). Implementing Network Isolation in Hyper-V 23. As in the previous recipe, you will see the PowerShell session change. Windows PowerShell Windows PowerShe II Copyright (C) 2013 Microsoft Corporation. All rights reserved. PS C:\Users\adminuser> Enter-PSSession HYPVCH1 [HYPVCH1]: PS C: :\Users\AdminUser\Documents> 24. The prefix [HYVCH1] indicates that any further PowerShell you execute in this console will be executed on HYPVCH1 until you exit the remote PowerShell session. 25. Enter the following PowerShell and press Enter: et-VMNetworkAdapterVlan -VMName PVLAN190-1 26. The following output will be returned: [HYPVCH1]: PS \Users\AdminUser\Documents> Get-UMNetworkAdapterVlan -VMName PULAN190-1 VMName VMNetworkAdapterName Mode VlanList PVLAN190-1 PVLAN190-1 Isolated 190,5 27. This shows the network adapter of PVLAN190-1 to be in isolated mode as expected. 28. Keep this PowerShell console open as it will be needed shortly. 29. Ensure that VMs PVLAN190-1 and PVLAN190-2 are on the same host and are running. 30. Navigate to the Fabric workspace and click on Logical Networks. 31. On the ribbon bar, click on Virtual Machines. Create IP Pool Services Create MAC Pool Virtual Machines Create Logical Create VM Create Create Overview Fabric Network Network Create VIP Template Logical Switch Resources . Resources Hosts Create 32. In the filter enter pvlan. Chapter 6 33. You should then see four VMs. Logical Network Information