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.
If you have followed all of the recipes so far in this book, you have a network that logically looks similar to the following diagram:
Adding a HNV gateway to this will allow the VMs within the currently declared VM Networks to communicate outside their VM Network. Within Windows Server 2012 R2, there are two possible implementations of the gateway:
- Network Address Translation (NAT): This is the traditional edge device implementation that allows VMs on the VM Networks to have Internet access and for inbound NAT translation rules. A NAT-based gateway can handle up to 50 VM Networks by default.
- Direct Routing: This acts in a traditional router sense connecting...
