Export (0) Print
Expand All

Get Started with Hybrid Networking: Walkthrough Guide

Updated: November 1, 2013

Applies To: System Center 2012 R2

This step-by-step walkthrough shows you how to verify that your hybrid network solution is fully functional. You will verify that network virtualization is working correctly by using the Windows Server 2012 R2 multi-tenant gateway.

This document assumes that you have a basic understanding of Windows Network Virtualization and network virtualization gateways. For more information, see Hyper-V Network Virtualization Overview.

In this walkthrough, you'll learn:

  • How to move a virtual machine from the tenant network to the hosting provider network.

  • How to connect the tenant’s virtual machine to their own private virtual network.

  • How to test that the tenant still has network connectivity to the virtual machine that now resides on the hosting provider network.

Time requirements

60 minutes

Get help from others or provide feedback

If you have questions or feedback regarding the content of this document, post a message to the Microsoft Windows Server Platform Networking Forum.

Walkthrough steps

Prerequisites

Before you start this walkthrough, you must set up the infrastructure as described in the Evaluating System Center 2012 R2 with Windows Azure Pack guide at http://go.microsoft.com/fwlink/p/?LinkId=302336.

Step 1: Deploy the Tenant Virtual Machines

In this step, you will deploy the customer tenant virtual machines in the simulated data center environment. Contoso APP2 and Fabrikam APP2 will be deployed on WNVHOST2, where they will have a single connection to their respective tenant VM network. Although the virtual machines will have the same names and IP addresses, they will be securely isolated from each other while maintaining access to their respective on-premises domain environments over the Internet.

Create a virtual hard disk for the APP2 virtual machines

The next step will deploy new hosted virtual machines for each tenant named APP2. This procedure requires a generalized virtual hard disk stored in the VMM Library. If you already have a generalized Windows Server 2012 R2 VHD to use, name the VHD file Server2012R2Base.vhd, and copy it to the %SYSTEMDRIVE%\ProgramData\Virtual Machine Manager Library Files\VHDs directory on the WNVHOST2 server. For instruction on how to create a generalized hard disk file on WNVHOST2, see the Appendix section of this document.

To deploy the APP2 tenant virtual machines on WNVHOST2

  1. In Virtual Machine Manager Console, open the VMs and Services workspace.

  2. On the Home tab, in the Create group, click Create Virtual Machine. The Create Virtual Machine Wizard opens.

  3. On the Select Source screen, click Browse.

  4. Double-click Server2012R2Base.vhd to select it, and then click Next.

  5. Type Contoso APP2 for virtual machine name, and then click Next.

  6. On the Configure hardware screen, provide settings for memory, and then select the Network Adapter 1 setting in the console tree.

  7. Under Connectivity, select Connected to a VM network, and then click Browse.

  8. Select Contoso VM Network, and then click OK.

  9. Click Next.

  10. On the Select Destination screen, select Place the virtual machine on a host, and then click Next.

  11. On the Select Host screen, select WNVHOST2.corp.adatum.com, and then click Next.

  12. On the Configure Settings screen, click Next.

  13. Review the options on the Add properties screen, adjust the settings as needed, and then click Next.

  14. On the Summary page, select Start the virtual machine after deploying it, and then click Create.

  15. The Jobs dialog box appears. Ensure that the job has a status of Completed, and then close the dialog box.

  16. Verify that Contoso APP2 is now running on WNVHOST2.

  17. Right-click WNVHOST2, and then click Create Virtual Machine. The Create Virtual Machine Wizard starts.

  18. On the Select Source screen, click Browse.

  19. Double-click Server2012R2Base.vhd to select it, and then click Next.

  20. Type Fabrikam APP2 for virtual machine name, and then click Next.

  21. On the Configure hardware screen, provide settings for memory, and then select the Network Adapter 1 setting in the console tree.

  22. Under Connectivity, select Connected to a VM network, and then click Browse.

  23. Select Fabrikam VM Network, and then click OK.

  24. Click Next.

  25. On the Select Destination screen, select Place the virtual machine on a host, and then click Next.

  26. On the Select Host screen, select WNVHOST2.corp.adatum.com, and then click Next.

  27. On the Configure Settings screen, click Next.

  28. Review the options on the Add properties screen, adjust the settings as needed, and then click Next.

  29. On the Summary page, select Start the virtual machine after deploying it, and then click Create.

  30. The Jobs dialog box appears. Ensure that the job has a status of Completed, and then close the dialog box.

  31. Verify that Fabrikam APP2 is now running on WNVHOST2.

  32. Start an elevated Windows PowerShell window on WNVHOST2.

  33. Type Get-NetVirtualizationLookupRecord and press ENTER.

    The mapping of Customer and Provider addresses is shown. Note that both Contoso APP2 and Fabrikam APP2 virtual machines have the same CustomerAddress value of 10.0.1.100. The common Customer Addresses are isolated from one another by means of their unique CustomerID and VirtualSubnetID values. Note that each tenant network also has a virtualized instance of a gateway at the Customer Address of 10.0.1.1.

    There are two Provider Addresses, one for each tenant, automatically assigned by VMM in the 172.16.1.100-200 IP address range. These addresses were assigned by the DHCP extension running on WNVHOST2 from the Management IP Pool.

  34. Type Get-NetVirtualizationCustomerRoute and press ENTER. The gateway addresses that are assigned to each virtual machine correspond to the WNV Gateway-managed address of 10.254.254.2.

  35. Type Get-SCIPAddress and press ENTER. Information is displayed for each Provider Address and Customer Address allocated by the IP Pools defined in Virtual Machine Manager.

  36. Switch to the WNV Gateway host server WNVHOST3. From a Windows PowerShell prompt, run Get-NetVirtualizationLookupRecord and then run Get-NetVirtualizationCustomerRoute. Examine the mapping of Customer and Provider addresses that are published to the gateway server by the Virtual Machine Manager server WNVHOST2.

Verify network connectivity for the APP2 virtual machines

The Contoso APP2 and Fabrikam APP2 virtual machines are both hosted on the WNVHOST2 server. Although they share the same IP address, they are securely isolated from one another in the datacenter using network virtualization. Verify that these virtual machines have network connectivity to remote resources in their respective customer on-premises environments over the Internet through the multitenant site-to-site gateway running on WNVHOST3.

Step 2: Verify Connectivity on APP2

The Contoso APP2 and Fabrikam APP2 virtual machines are both hosted on the WNVHOST2 server. Although they use the same IP address, they are securely isolated from one another in the data center using network virtualization. Verify that these virtual machines have network connectivity to remote resources in their respective customer on-premises environments over the Internet through the multitenant site-to-site gateway running on WNVHOST3.

To test access to the Contoso domain from APP2 hosted on WNVHOST2

  1. On WNVHOST2, connect to the Contoso APP2 virtual machine.

  2. Complete the mini-setup process when starting the virtual machine for the first time, and then sign in as the local Administrator.

  3. From the Server Manager console Tools menu, click Windows PowerShell.

  4. In the Windows PowerShell window, type ipconfig /all to display the Windows IP configuration. Note that the address 10.0.1.100 was assigned automatically by the Virtual Machine Manager DHCP Server component running on WNVHOST2.

  5. In the Windows PowerShell window, type ping 10.0.0.2 and press ENTER to verify connectivity to the internal interface on Contoso EDGE1 through the datacenter physical network, the virtualization gateway, and the cross-premises VPN connection over the Internet. You should receive four replies from 10.0.0.2.

  6. Type ping 10.0.0.1 and press ENTER to verify connectivity to the remote DC1 server on the Contoso corpnet subnet. You should receive four replies from 10.0.0.1.

  7. Repeat the previous steps on the Fabrikam APP2 virtual machine to verify connectivity to the remote resources on the Fabrikam corpnet subnet.

You have now successfully demonstrated that you have two tenants, each connected to their own private virtual network at a hosting provider. A multi-tenant gateway connects both tenant’s networks via a site-to-site VPN tunnel.

Next steps

For more information about hybrid networking, see the Hybrid Cloud Multi-Tenant Networking Solution Guide.

Appendix

This appendix describes how to create a generalized virtual hard disk in Hyper-V.

To create a virtual hard disk on WNVHOST2

  1. From the Tools menu in Server Manager, click Hyper-V Manager. Expand Hyper-V Manager, and select WNVHOST2.

  2. In Hyper-V Manager console Actions pane, point to New, and then click Virtual Machine.

  3. The New Virtual Machine Wizard opens. Click Next.

  4. Name the new virtual machine Server2012R2Base.

  5. Select the checkbox for Store the virtual machine in a different location. Next to Location, type %SYSTEMDRIVE%\ProgramData\Virtual Machine Manager Library Files\VHDs\ and then click Next.

  6. Select Generation 1. Click Next.

  7. Assign 2048 MB of memory to allocate to the new virtual machine, and then click Next.

  8. On the Configure Networking page, click Next.

  9. On the Connect Virtual Hard Disk page, change the location to %SYSTEMDRIVE%\ProgramData\Virtual Machine Manager Library Files\VHDs\, and then click Next.

  10. On the Installation Options page, select the appropriate options to access the operating system setup media. To install from an ISO image file, select Install an operating system from a boot CD/DVD-ROM, and supply the path to the installation media file. Click Next.

  11. On the Summary page, click Finish.

  12. Start the Server2012R2Base virtual machine. Set appropriate language, time and keyboard options. Click Next.

  13. On the Windows Setup screen, click Install now.

  14. Select Windows Server 2012 R2 Datacenter (Server with a GUI) and then click Next.

  15. Accept the license terms, and then click Next.

  16. Click Custom: Install Windows only (advanced).

  17. On the Where do you want to install Windows page, click Drive 0 Unallocated Space.

  18. Click Next.

  19. Follow the instructions to complete the installation of Windows Server 2012 R2, specifying a strong password for the local Administrator account. Log on using the local Administrator account.

  20. Start C:\Windows\System32\Sysprep\Sysprep.exe

  21. In the System Preparation Tool dialog, select Enter System Out-of-Box Experience (OOBE). Select the Generalize checkbox, and under Shutdown Options, select Shutdown. Click OK.

  22. Sysprep will generalize the installation of Windows Server 2012 R2 and then shut down the virtual machine.

See also

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft