rs | Select-Object Name, VMNetwork, IPv4Addresses, MACAddress 45. This will show you a list of the VMs that are currently deployed, the VM Network they are attached to, the IP address(es) assigned, and the MAC address. VMNetwork IPv4Addresses MACAddress Tenant A VM1 Tenant A {10.0.0.2} 00:1D:D8:B7:1C:04 Tenant VM2 Tenant {10.0.0.2} 00:1D:D8:B7:1C:0B Tenant VM1 Tenant {10.0.0.3} 00:1D:D8:B7:1C:06 46. As you can see in the output of the PowerShell, you can see that Tenant A -VM1 and Tenant B - VM2 have the same IP address but different MAC addresses. How it works. Each VM Network is assigned its own Virtual Subnet ID by VMM, which is then passed down to the Hyper-V servers. As the VM Networks were instructed to use Hyper-V Network Virtualization within the Logical Network "Provider Address", they were instructed to allow VM Networks to use network virtualization. Every time a packet is sent from a VM on either the Tenant A or Tenant B VM Network, it is encapsulated within an NVGRE packet. The following diagram shows how the packet is encapsulated. It has been taken from http://msdn.microsoft. com/en-us/library/windows/hardware/dn144775 (v=vs 85) . aspx. Packet from Virtual Machine IP Header TCP user data Header Packet from Hyper-V Host Provider Provider IP IP Header TCP user data header Header Creating the Gateway for Virtual Machine Communications In this chapter, we will cover the following recipes: Creating a Logical Network, Port Profiles, and Logical Switches for external access Creating a Hyper-V Network Virtualization gateway manually Creating a Hyper-V Network Virtualization gateway with a Service Template Introduction HNV requires the use of gateways that understand the Network Virtualization using Generic Routing Encapsulation (NVGRE) protocol and what is being asked of it. Microsoft has implemented the gateway functionality within Windows Server 2012 R2, and it is extremely efficient to connect VM Networks to HNV gateways by using VMM. Creating the Gateway for Virtual Machine Communications If you have f