Welcome to Hyper-V Network Virtualization Cookbook. This book is an end-to-end introduction on how to implement Hyper-V Network Virtualization (HNV) on Microsoft Windows Server 2012 R2 Hyper-V using System Center 2012 R2 Virtual Machine Manager.
The purpose of this book is to help you get familiar with the components of Hyper-V Network Virtualization and the options available to you. It is assumed that you are familiar with Windows Server 2012 R2 and want to understand how to implement HNV.
Software-defined Networks (SDN) are networks decoupled from the traditional physical hardware. SDN allows IT and network administrators to react to changing business requirements faster as it removes the requirement to amend the physical infrastructure. Microsoft's implementation of SDN uses the NVGRE protocol, which is referred to as Hyper-V Network Virtualization.
Chapter 1, Installing Virtual Machine Manager, shows you how to install Virtual Machine Manager (VMM), which is a critical component of HNV. This chapter discusses the components required for VMM and how to configure them correctly.
Chapter 2, Configuring Networks for Hyper-V Network Virtualization, teaches you the required configurations in VMM for Logical Networks, Virtual Machine Networks (VM Networks), IP Pools, and virtual machines.
Chapter 3, Creating the Gateway for Virtual Machine Communications, demonstrates how to create an HNV gateway and connect it to VM Networks.
Chapter 4, IP Address Management Integration with VMM for Hyper-V Network Virtualization, demonstrates how to integrate IPAM with VMM.
Chapter 5, Windows Server Gateway Configuration, goes deeper into the capabilities of the Windows Server gateway, showing you how to use the different options for gateways—including Network Address Translation and Direct Routing.
Chapter 6, Implementing Network Isolation in Hyper-V, discusses how to implement traditional networking in Hyper-V with regards to VLANs and PVLANs.
Chapter 7, Network Access Control Lists, details the options available to Hyper-V administrators for securing their virtual machines. For example, how to control what can access a VM on a specific port and how the Hyper-V Extensible Switch can be used here.
Appendix A, VM Templates, will discuss the Virtual Machine Templates, which are created using the Convert-WindowsImage.ps1 PowerShell script.
Appendix B, Planning the Virtual Machine Manager, will help you with the preparation and planning of the Virtual Machine Manager.
The hardware and software requirements are covered in the following sections.
To complete all of the recipes in this book, you will need five computers capable of running Windows Server 2012 R2 Hyper-V each with at least 8 GB RAM. Please ensure that your hardware meet the minimum requirements for Windows Server 2012 R2 and for Hyper-V. Please refer to the TechNet article at http://technet.microsoft.com/en-us/library/jj647784 for more details.
In addition, you will need a switch capable of IEEE 802.1q VLANs. The following diagram shows you how the hardware should be connected:
In addition, you will need some shared storage for the Management Hosts and Tenant Hosts to be able to create Hyper-V clusters. The NAT Device / Firewall does not have to offer DHCP addresses, as System Center 2012 R2 Virtual Machine Manager will be responsible for distributing IP addresses for use on this network by Hyper-V Network Virtualization.
All of the recipes in this book are based on the following software:
Windows Server 2012 R2
System Center 2012 R2 Virtual Machine Manager
SQL Server 2012 SP1 Enterprise Edition
It is advisable to ensure that you install the latest Update Rollup available for all products. Microsoft is continually refining the products involved, and it is highly recommended that you have the latest updates installed, the exception being SQL Server 2012. It is advised to install the latest Cumulative Update of Service Pack 1 and not to install Service Pack 2.
The Fully Qualified Domain Name for the Active Directory domain in this book is ad.demo.com and the NetBIOS name is DEMO. The functional levels of the Forest and Domain are both Windows Server 2012 R2.
You do not require SQL Server 2012 SP1 Enterprise Edition for Hyper-V Network Virtualization. However, it offers the AlwaysOn High Availability Group function, which offers significantly faster failover in the event of a SQL Server failure. System Center 2012 includes a license for SQL Server 2012 Standard Edition, which is sufficient for most installations.
The target audience of this book is Network and Virtualization administrators who are responsible for architecting their infrastructure. The recipes in this book will demonstrate how to implement HNV. The ultimate goal of this book is to provide a sound understanding of how HNV can be implemented and the components involved.
This book contains the following sections:
This section tells us what to expect in the recipe, and describes how to set up any software or any preliminary settings needed for the recipe.
This section usually consists of a brief and detailed explanation of what happened in the previous section.
It consists of additional information about the recipe in order to make the reader more anxious about the recipe.
In this book, you will find a number of styles of text that distinguish between different kinds of information. Here are some examples of these styles, and an explanation of their meaning.
Code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles are shown as follows: "Enter the FQDN of the IPAM server; in this case, DEMO-IPAM01.ad.demo.com."
A block of code is set as follows:
Set-PSDrive AD: $VMMInstallAccount = Get-ADUser -Identity Install_VMM
When we wish to draw your attention to a particular part of a code block, the relevant lines or items are set in bold:
$logicalNetwork = Get-SCLogicalNetwork -ID "f69abe75-0e94-42a9-b86a-6d48c4010c1a"Any command-line input or output is written as follows:
Install-WindowsFeature –Name IPAM -IncludeManagementTools
New terms and important words are shown in bold. Words that you see on the screen, in menus or dialog boxes for example, appear in the text like this: "Click on the Utilization Trend tab."
Feedback from our readers is always welcome. Let us know what you think about this book—what you liked or may have disliked. Reader feedback is important for us to develop titles that you really get the most out of.
To send us general feedback, simply send an e-mail to <[email protected]>, and mention the book title via the subject of your message.
If there is a topic that you have expertise in and you are interested in either writing or contributing to a book, see our author guide on www.packtpub.com/authors.
Now that you are the proud owner of a Packt book, we have a number of things to help you to get the most from your purchase.
You can download the example code files for all Packt books you have purchased from your account at http://www.packtpub.com. If you purchased this book elsewhere, you can visit http://www.packtpub.com/support and register to have the files e-mailed directly to you.
Although we have taken every care to ensure the accuracy of our content, mistakes do happen. If you find a mistake in one of our books—maybe a mistake in the text or the code—we would be grateful if you would report this to us. By doing so, you can save other readers from frustration and help us improve subsequent versions of this book. If you find any errata, please report them by visiting http://www.packtpub.com/submit-errata, selecting your book, clicking on the Errata Submission Form link, and entering the details of your errata. Once your errata are verified, your submission will be accepted and the errata will be uploaded on our website, or added to any list of existing errata, under the Errata section of that title. Any existing errata can be viewed by selecting your title from http://www.packtpub.com/support.
To view the previously submitted errata, go to https://www.packtpub.com/books/content/support and enter the name of the book in the search field. The required information will appear under the Errata section.
Piracy of copyright material on the Internet is an ongoing problem across all media. At Packt, we take the protection of our copyright and licenses very seriously. If you come across any illegal copies of our works, in any form, on the Internet, please provide us with the location address or website name immediately so that we can pursue a remedy.
Please contact us at <[email protected]> with a link to the suspected pirated material.
We appreciate your help in protecting our authors, and our ability to bring you valuable content.
You can contact us at <[email protected]> if you are having a problem with any aspect of the book, and we will do our best to address it.