Network Configuration

You will create six subnets to simulate the following:

1.   The Internet, referred to as the Internet subnet (131.107.0.0/24).

2.   An intranet, referred to as the Hosternet subnet (192.168.0.1/24) connected to the Internet subnet via a second network adapter on the WNV Gateway server WNVHOST3.

3.   An intranet, referred to as the Contoso Corpnet subnet (10.0.0.0/24), separated from the Internet subnet by Contoso EDGE1.

4.   An intranet, referred to as the Fabrikam Corpnet subnet (10.0.0.0/24), separated from the Internet subnet by Fabrikam EDGE1.

5.   A Windows Network Virtualization virtual network, referred to as the Contoso VM Network (10.0.1.0/24), hosted on the simulated hoster datacenter servers WNVHOST1 and WNVHOST2.

6.   A Windows Network Virtualization virtual network, referred to as the Fabrikam VM Network (10.0.1.0/24), hosted on the simulated hoster datacenter servers WNVHOST1 and WNVHOST2.

Computers on each subnet connect using a physical hub, switch, or virtual switch. See the following figure for the configuration of the Windows Server 2012 R2 Hyper-V Network Virtualization with System Center 2012 VMM R2 test lab.

 

This document describes how to build out the Windows Server 2012 R2 Hyper-V Network Virtualization with System Center 2012 R2 in six sections:

·      Steps for configuring the Hosternet subnet (WNVHOST1, WNVHOST2)

·      Steps for configuring the Internet subnet (INET1 on WNVHOST4, and WNVHOST3)

·      Steps for configuring the Contoso Corpnet subnet (DC1, APP1, and EDGE1 on WNVHOST4)

·      Steps for configuring the Fabrikam Corpnet subnet (DC1, APP1, and EDGE1 on WNVHOST4)

·      Steps for installing and configuring System Center 2012 Virtual Machine Manager R2 (WNVHOST2)

·      Steps for implementing and testing Windows Network Virtualization (Contoso APP1 and APP2, Fabrikam APP1 and APP2)

This evaluation demonstrates operation of Windows Network Virtualization in a simulated hoster datacenter using Hyper-V virtualization and System Center 2012 Virtual Machine Manager R2. Simulated on-premises customer networks are used to demonstrate access to hosted cloud resources over a simulated Internet connection. The two customer networks share the same computer names and IP addresses to demonstrate the secure isolation provided by Windows Network Virtualization.

Hardware Requirements for Networking

The following are the minimum required components of this evaluation:

·      The VHD for Windows Server® 2012 R2 Preview.

·      The Windows Assessment and Deployment Kit (ADK) 8.1 source files. Windows ADK is available at the Microsoft Download Center at http://go.microsoft.com/fwlink/p/?LinkId=263698. To install the Windows ADK on a computer that does not have Internet access, first download the installer files. Next, copy the installer files to the offline computer. Then you can run ADKSetup.exe using either the GUI or the command line.

·      The VHD for Microsoft SQL Server 2012.

·      The VHD for System Center 2012 R2 Virtual Machine Manager.

Important

Run Windows Update on all computers or virtual machines either during the installation or immediately after installing the operating systems. After running Windows Update, you can isolate your physical or virtual test lab from your production network.

You must be logged on as a member of the Domain Admins group or a member of the local Administrators group on each computer to complete the tasks described in this guide.

Steps for Configuring the Hosternet Subnet

There are two steps to setting up the Hosternet subnet of the Windows Server 2012 R2 Hyper-V Network Virtualization with System Center 2012 VMM R2 Test Lab.

1.   Configure WNVHOST1.

2.   Configure WNVHOST2.

Configure WNVHOST1

WNVHOST1 is a physical server configured as a Windows Server 2012 R2 Hyper-V host, Domain Controller and DNS Server for the simulated hoster datacenter domain, corp.adatum.com, connected to a shared physical switch used to simulate a hoster datacenter connection. WNVHOST1 configuration consists of the following:

1.   Install the operating system

2.   Configure TCP/IP

3.   Rename the computer

4.   Configure WNVHOST1 as a DC and DNS server for corp.adatum.com

5.   Create a user account for User1

6.   Install the Hyper-V server role

7.   Create a Hyper-V external virtual switch to simulate a connection to Hosternet

Configure WNVHOST2

WNVHOST2 is a physical server configured as a Windows Server 2012 R2 Hyper-V host, SQL server, and System Center 2012 Virtual Machine Manager, connected to a shared physical switch used to simulate a hoster datacenter connection (Hosternet). WNVHOST2 configuration consists of the following:

1.   Install the operating system

2.   Configure TCP/IP

3.   Rename the computer and join the corp.adatum.com domain

4.   Install the Hyper-V server role

5.   Create a virtual switch