ired. The NVGRE protocol contains the provider's address information, including the Virtual Subnet ID, and the packet within contains the tenant information. This is how the gateway is able to keep data isolated and ensure that even with overlapping subnets, the data is returned to the requesting virtual machine. Chapter 3 The manual process allows you to get familiar with the requirements of an HNV gateway. However, the process can be time consuming and it can be refined using a Service Template. Creating a Hyper-V Network Virtualization gateway with a Service Template As we saw in the previous recipe, there is not too much involved in the actual deployment of an HNV gateway. The only required roles/features within the Virtual Machine are: DirectAccess and VPN Routing It is possible to leverage the Service Template feature within VMM to rapidly provision HNV gateways. However, these gateways will not be available immediately after deployment. This is because they still need to be added to VMM as a Network Service and to the required VM Network(s) as NAT, or Direct Routing and gateways. Getting ready You need to have a VM template to use as a basis for the Service Template. The VM template that has been used in previous recipes should be sufficient, provided it is Windows Server 2012 R2 Standard or Datacenter edition with a GUI. (Server Core editions of Windows Server 2012 R2 are not currently supported for use as an HNV gateway.) How to do it... The following diagram shows the high-level steps involved in this recipe: Overview of Recipe: Actions: Creation of single tiered Service Template for deploying a VM capable of being a Hyper-V Network Virtualization Gateway Information on where to obtain a prebuilt Service Template to create a highly available Network Virtualization Gateway service Creating the Gateway for Virtual Machine Communications Now, you need to perform the following steps: 1. Open the VMM console. 2. Navigate to Library I Templates I Service Templates. Right-click on Service Templates and click o