used in the switch and what Virtual Port Profiles are available How it works The creation of the External (NAT) Logical Network will allow Hyper-V Network Virtualization Gateways to connect VMs to networks beyond the previously created Tenant A and Tenant B VM Networks. Scoping the External (NAT)_O Logical Network Site exclusively to the Gateway host group ensures that it will not be available to VMs on the core Hyper-V cluster. Creating a Hyper-V Network Virtualization gateway manually The HNV gateway is part of the Remote Access role in Windows Server 2012 R2. There is no specific subfeature within the Remote Access role that you can select. This recipe will show you how to create a Virtual Machine that is appropriate for using as a standalone HNV gateway. Creating the Gateway for Virtual Machine Communications Getting ready You will need to have created a Hyper-V host and added it to VMM within the Gateway host group. This Hyper-V host does not have to be domain joined; if you do not domain join the host, then ensure an appropriate Run As account has been added to VMM for it to manage the host. The existing VMM Run As account would not be suitable as it is a domain account. This Hyper-V host needs to have at least three NICs. The following diagram shows the logical structure: NVGRE Gateway Provider Converged NIC External Network Management (Direct Internet (VM Network Live Migration or behind NAT) access) Cluster To learn how to add a Hyper-V host to VMM, please visit http : // technet. microsoft.com/en-us/library/gg610646.aspx Also, you can visit http://technet.microsoft.com/library/dn423897.aspxfor Microsoft's hardware recommendations for the Windows Server Gateway host. Chapter 3 How to do it... The following diagram shows the high-level steps involved in this recipe: Overview of Recipe: Prerequisites (not covered by this recipe): Installation of a Hyper-V host for dedicated Gateway use (min. 3 physical NICs required) Adding of the Hyper-V host to VMM Actions: Configuration of the new Hyper-V host to be sui