1. From the VMM console, start the Create Logical Network Wizard.
2. Input “GREVIP” as the name and optional description for this network and click Next.
3. On the Settings page, ensure you select One Connected Network. Optionally, you can also check Create a VM network with the same name box to allow virtual machines to access this logical network directly and the Managed by the Network Controller box then click Next.
4. On the Network Site panel, add the network site information for your VIP subnet. This should include the Host Group and subnet information for your VIP network.
5. Review the Summary information and complete the Logical Network wizard

1. Right-click the GRE VIP logical network in VMM and select Create IP Pool from the drop-down menu.
2. Input “IPPool-GRE” as the name and optional description for the IP Pool and ensure that the VIP network is selected for the logical network. Click Next.
3. Accept the default network site and click Next.
4. Choose a starting and ending IP address for your range. Important Use 31.30.30.2/24 as the range on the second addresses of your available subnet. For example, if your available subnet is from .1 to .254, start your range at .2
5. In the IP addresses reserved for load balancer VIPs box, type the IP addresses range in the subnet. This should match the range you used for starting and ending IP addresses.
6. You do not need to provide gateway, DNS or WINS information as this pool is used to allocate IP addresses for VIPs only via the network controller, so click Next to skip these screens.
7. Review the summary information and complete the wizard

1. In the ribbon at the top, click Import Template.
2. Browse to your service template folder, select EdgeServiceTemplate Generation2.xml and click Next.
3. This service template uses the following virtual machine configuration parameters. Update the parameters to reflect the your environment configuration. Configuration parameters:
4. Click Next.
5. On the Summary page, click Import.

1. Select the EdgeServiceTemplate Generation2.xml service template and click Configure Deployment to begin. Type a name and choose a destination for the service instance. The destination must map to a Host Group that contains the hosts configured previously for gateway deployment purposes.
2. In the Network Settings section, you must map the networks as MGMT
3. Click OK.
4. After you are done mapping the destination and network settings, Click OK.
5. The Deploy Service dialog appears. It is normal for the virtual machine instances to be initially red. Click Refresh Preview to automatically find suitable hosts for the virtual machine.
6. On the left side of the Configure Deployment window, there are several settings that you must configure. The table below summarizes each field:

1. Open the VMM console.
2. Select VMs and Services.
3. Click All Hosts and select the Services
4. Delete the failed Gateway Service instance.

1. Open the Fabric
2. Click Network Service to display the list of network services installed.
3. Right-click your network controller service and select Properties.
4. Click the Services tab and select the Gateway Manager Role in the services panel.
5. Find the Associated Service field under Service information and click Browse.
6. Select the gateway service instance you created earlier and click OK.
7. Select the Run As account that will be used by network controller to access the gateway virtual machines. This account should have admin privileges on the gateway VMs.
8. In GRE VIP subnet, select the VIP subnet that you created previously.
9. In Public IPv4 pool, select the Public IP Pool you configured during the SLB deployment.
10. Public IPv4 address, provide an IP address from the previous pool.
11. Configure the Gateway Capacity in Gateway Capacity 1000
12. Configure the number of reserved nodes for back-up in Nodes for reserved for failures field
13. You need to configure individual gateway virtual machines now. Click each gateway virtual machine and:
    1. Select the IPv4 Frontend Subnet. Transit
    2. Specify the local ASN. anything
    3. Optionally add the peering device info for the BGP peer
14. Click OK

1. Open System Center Virtual Machine Manager (SCVMM) Console Double-click the Virtual Machine Manager Console icon on the Desktop. Click “Connect”
2. Open Tenant VM Network property Select “Client VMs and Services” in the bottom-left hand side of the VMM console Click on “VM Networks” Right Click the VM Network you created in Exercise 1, step 4 (E.g. “CONTOSO”) Select “Properties” from the popup menu after your right click.
3. Setup the VPN connectivity Select “Connectivity” from the left navigation tabs. Check “Connect to another network through a VPN tunnel” Leave “Enable Border Gateway Protocol (BGP)” unchecked Check “Connect directly to an additional logical network” Select the “Direct routing” radio button. Make sure the Gateway Service is selected as “SingleNodeNCService” Don’t click “OK” for now.
4. Setup VPN Connections Select “VPN Connections” from the left navigation tabs In the subnet text field; enter 10.254.254.0/29 (this is a rarely used range) Click on “Add” and choose “Add IPsec tunnel” In the “Name” text input, Give the IPSEC tunnel a name (eg. “IPSEC-VMM”) In the “Remote endpoint” field,  input “50.50.50.1”—this is the IP of the remote site that was pre-created for this exercise Do not check “Limit bandwidth available for this VPN connection” Click on “Authentication” Select the first radio button option, “Authenticate using the following credentials” For “Run As account:”, click on “Browse” Select “IPSECACCOUNT” as the “Run As” account, then click “OK” Create an “IPSECACCOUNT” as the “Run As” account; please do not make your own account. chose any username, but you have to use "User@123" as the password Click on “Routes” Click on the “Add” button to add a subnet In the Subnet text field, input “60.60.60.0/24” which is configured in the remote site Click “OK”. This may take a few seconds to complete.
5. Make sure the VMM job is finished Click on “Jobs” in the bottom-left hand side of the VMM console Make sure the running jobs have finished successfully (all running jobs should have a “Completed” status)

1. Go to Remote VM
2. Right click Windows Start Menu , select Run and type “rrasmgmt.msc” to open the “Routing and Remote Access” menu.
3. Right click Network Interface and select “New Demand-dial interface…”
4. Type “IPSEC-S2S” as the name and click “Next”
5. Select “Connect using virtual private network (VPN)”. Then click “Next”
6. In the VPN type, select “IKEV2” , and click “Next”
7. Input “40.40.40.20” as the VIP of the gateway service
8. Check “Route IP packets on this interface”, Click “Next”
9. Input “192.168.1.0/24” as the Subnet of the Tenant VM Network you will connect to. Click “Next”.
10. Click Next on the Dial-out Credentials
11. Click Finish
12. Right click on the created remote router to Open its “Properties”
13. In the options tab page, select “Persistent connection” as the connection type and click “OK”.
14. Establish the S2S VPN connection After you have logged in to the remote site gateway, double click the shortcut “RRAS Management Console” on the desktop to open it. In the left menu of the RRAS Management Console, click on “Network interfaces” Right click on “Remote Router” Click “Property” -> “Security” In the “Key” input text field, remove all the existing stars “*****” there. Input “User@123” And click OK. Right click on “Remote Router” Click “Connect” After a short delay around 5-6 seconds, you will see the Remote Router Connection State change from “Disconnected” to “Connected”. Now the S2SVPN is connected.
15. Validate the S2S VPN connection Select the VMM console (it should be minimized in the taskbar) Click on “VM and Services” in the bottom-left hand side of the VMM console Click on “All hosts” In the right VMs window, locate your first created VM - “VM1” Right click on the VM and select “Connect or View” Choose “Connect via Console” The Virtual Machine viewer window will now appear Click on the “Ctrl-Alt-Del” (button in upper left-hand corner) then use “.\Administrator” as the username and “!!123abc” as the password to login Press the Windows key and type “Internet Explorer” then press Enter to open the browser In the launched Internet Explorer window, input https://60.60.60.1 in the address bar and press Enter You should see a “Congratulations!” web page.
16. You have now finished the IPSEC S2S VPN successfully!

1. Right Click CONTOSO VM Network and click Connectivity.
2. Select Connect to another network through a VPN tunnel.
3. Select your Network Controller Service for the Gateway Device.
4. Select the VPN Connections
5. Click Add and then select GRE type connection.
6. Type a subnet as shown in the following diagram. This subnet is used to route packets out of the VM Network. This subnet does not need to be preconfigured in your datacenter.
7. Type a connection name. The name used in the example screenshot is GREVPN.
8. Type the IP address of the Remote endpoint: 50.50.50.1
9. Type the GRE key - 1234
10. Select the Routes
11. Add "60.60.60.1" to the Subnet and click OK
12. Click on “Fabric" on the left navigation
13. Click on "Network Service", and double click on the "Gateway Service" under "Network Controller Service"
14. Configure the Gateway Service Information as the following -
15. Then configure each of the Gateway node as the following with Local ASN : 65000, PEER IP Address: 10.10.10.1 and ASN 64623
16. Go to VMs and Services , click on All Hosts
17. Check each of the Gateway VM's Transit IP Address, you will need these IP addresses in the next steps.
18. Go to RRAS VM , open the PowerShell console
19. Run the following PowerShell to add BGPPeer for each of the gateway , the "PeerIPAddress" should be the IP address of the Gateway Node Transit IP you just found out in the previous step. When finished, run Get-BGPPeer to check if they are connected.
20. Go to Remote VM , open the PowerShell console
21. Run the following Powershell to add a new VPNInterface for GRE connection , when finished , use "Get-VPNS2SInterface" cmdlet to check the status and connectivity
22. Validate the GRE Connection Select the VMM console (it should be minimized in the taskbar) Click on “VM and Services” in the bottom-left hand side of the VMM console Click on “All hosts” In the right VMs window, locate your first created VM - “VM1” Right click on the VM and select “Connect or View” Choose “Connect via Console” The Virtual Machine viewer window will now appear Click on the “Ctrl-Alt-Del” (button in upper left-hand corner) then use “.\Administrator” as the username and “!!123abc” as the password to login Press the Windows key and type “Internet Explorer” then press Enter to open the browser In the launched Internet Explorer window, input https://60.60.60.1 in the address bar and press Enter You should see a “Congratulations!” web page.
23. You have now finished the GRE connection exercise successfully!

1. From the VMM console, start the Create logical network Wizard.
2. Input “Transit” as the name and optional description for this network and click Next.
3. On the Settings page, ensure you select One Connected Network. Check Create a VM network with the same name box to allow virtual machines to access this logical network directly and the Managed by the network controller box then click Next.
4. On the Network Site panel, add the network site information for your subnet.
5. Review the Summary information and complete the logical network wizard

1. Start the Create logical network Wizard.
2. Input “PrivateVIP” as the name and optional description for this network. Click Next.
3. On the Settings page, ensure you select One Connected Network. check Create a VM network with the same name box to allow virtual machines to access this logical network directly and the Managed by the network controller box then click Next.
4. On the Network Site panel, add the network site information for your Private VIP logical network.
5. Review the Summary information and complete the wizard.

1. Right-click the Private VIP logical network in VMM and select Create IP Pool from the drop down menu.
2. Input “IPPOOL-PRIVATEVIP” as the name and optional description for the IP Pool and ensure that the Private VIP logical network is selected for the logical network. Click Next.
3. Accept the default network site and click Next.
4. Input 20.20.0/27 as the IP range

5. In the IP addresses reserved for load balancer VIPs box, type the IP addresses range in the subnet. This should match the range you used for starting and ending IP addresses.
6. You do not need to provide gateway, DNS or WINS information as this pool is used to allocate IP addresses for VIPs only via the network controller, so click Next to skip these screens.
7. Review the summary information and complete the wizard.

1. Start the Create logical network Wizard.
2. Input “PublicVIP” as the name and optional description for this network and click Next.
3. On the Settings page, ensure you select One Connected Network. Check the Create a VM network with the same name box to allow virtual machines to access this logical network directly and the Managed by the network controller Also, select Public IP Address Network and then click Next.
4. On the Network Site panel, add the network site information for your Public VIP network. This should include the Host Group and subnet information for your Public VIP network.
5. Review the Summary information and complete the logical network wizard

1. Right-click the Public VIP logical network in VMM and select Create IP Pool from the drop down menu.
2. Input name “IPPool-PUBLICVIP” and optional description for the IP Pool and ensure that the VIP network is selected for the logical network. Click Next.
3. Accept the default network site and click Next.
4. Choose a starting and ending IP address for your range.
5. In the IP addresses reserved for load balancer VIPs box, type the IP addresses range in the subnet. This should match the range you used for starting and ending IP addresses.
6. You do not need to provide gateway, DNS or WINS information as this pool is used to allocate IP addresses for VIPs only via the network controller, so click Next to skip these screens.
7. Review the summary information and complete the wizard

1. In the VMM console, navigate to Library.
2. In the top of the left pane, in the Templates section, select Service Templates.
3. In the ribbon at the top, click Import Template.
4. Browse to your service template directory, select the SLB Production Generation 2 VM.xml file and follow the prompts to import it.
5. This service template uses the following virtual machine configuration parameters. Update the parameters to reflect your environment configuration.

1. Select the SLB Production Generation 1 VM.xml service template and click Configure Deployment to begin. Type a name and optional destination for the service instance. The destination must map to a Host Group that contains the hosts configured previously.
2. In the Network Settings section, you must map the networks as follows.

1. Open the VMM console.
2. Select VMs and Services.
3. Click All Hosts and select the Services
4. Delete the failed SLB/MUX Service instance.

1. Click Services in the ribbon.
2. Verify that your SLB MUX service instance appears in the VM Network Information for Services
3. Right-click the SLB MUX service and select Properties from the menu.
4. Verify that the state is Deployed.

1. Open the Fabric
2. Click Network Service to display the list of network services installed.
3. Right-click the network controller service and select Properties.
4. In the Wizard, Select the Services tab, and then click Load Balancer Role.
5. Find the Associated Service field under Service information and click Browse.
6. Select the SLB/MUX service instance you created earlier and click OK
7. Choose the appropriate Run as Account
8. For the Management IP address, use the desired IP address from the Private VIP pool you created earlier.
9. Optionally specify the IP address ranges to be excluded from the outbound NAT.
10. Click the SLB/MUX instance listed under Load Balancer Role in the wizard.
11. Type the local ASN for your datacenter and details for the devices or BGP peers the SLB/MUX can peer with. You should use the Transit network for BGP peering. Do this for all three MUX.
12. When finished, press OK. Then Make sure associate service instance with fabric role.
13. Click on VMs and Services tab
14. Click on All Hosts, locate to the MUX
15. Check the Transit IP of each MUX , these IPs will be used in the next steps

1. Open RRAS VM
2. Open the PowerShell CMDLet and using the following scripts to create and configure the BGP router.
3. Run Get-bgppeer to verify the connection

1. Open System Center Virtual Machine Manager (SCVMM) Console If it’s already opened, just go back to the console.  If it’s not, double-click the Virtual Machine Manager Console icon on the Desktop. Click “Connect”
2. Open Create a VIP Template Wizard Click on “Fabric” in the bottom-left hand side of the VMM console Click on “VIP Templates” in the menu on the left-hand side Click “Create VIP Template” in the Ribbon menu
3. Specify VIP Template Name and Port Input “VIPTemplate” as the name and optionally a description for the VIP Template Specify the “Virtual IP port” (public facing) value of 80 and “Backend port” (on tenant VMs) value of 80 Click “Next”
4. Specify a Template Type Select “Specific template” and navigate to:
5. Manufacturer: “Microsoft”
6. Model: “Microsoft Network Controller” Click “Next”
7. Specify Protocol Options Select “Custom” protocol and type in value of TCP Click “Next”
8. Skip Specify Persistence Leave the “Enable Persistence” checkbox un-checked Click “Next”
9. Select a Load Balancing Method Click the drop-down to choose a load balancing method and select “Round Robin”. Click “Next”
10. Skip specify a health monitor Click “Next”
11. Confirm Settings and Create VIP Template Click “Finish” to Create the VIP Template Check in “jobs” to see if the task creation is finished.
12. Run the CreateTenantVIP PowerShell function Open the “Start menu” and right click on “Windows Powershell ISE” Choose “More” > “Run As Administrator” In the “Powershell ISE” window, select menu “File” > “New” Copy and Paste all the following script to the file
13. Save the file as Name “CreateVIP” Click the green arrow to “Run Script” The script may take a moment to run (the cursor in the PowerShell execution window will be inactive until the script is complete). Create a Tenant VIP Run the following command in the PowerShell execution window.
14. Validate Load Balanced VIP Open “Internet Explorer" Enter the IP address, “41.40.40.8” into the address bar You should now see the default Windows Server Welcome page
15. Congratulations! You just created an externally facing VIP that load balances across multiple VMs.

• Software Defined Networking (SDN)
• Plan a Software Defined Network Infrastructure.
• Deploy a Software Defined Network infrastructure using VMM

• A Physical machine with Dual-Socket: 8 - 16 Physical Cores, 128G RAM, 175GB local disk, 300GB HD for VM storage (can be on File Server)
• Windows Server 2016 Data Center with 9D Update
• SQL Server 2014
• Windows Assessment and Deployment Kit
• SCVMM 2016
• SCVMM Templates for SDN Deployment

• Remote: Public, Private
• RRAS: 3 VNIC connect to SDN, one NIC connects to Public
• SCVMM, HOST01, HOST02, HOST03 and HOST04: SDN

• Rename computer name as “RRAS”
• Install “Active Directory Domain Services” Role and configure the RRAS server as the DC. Create a root domain – “SDN.LAB”
• Install “DNS Server” role, and configure the DNS
• Install “Remote Access” Role
• Create an Active Directory security group for network controller management - SDNMGMT You need to create an Active Directory security group for network controller management. The group should be a Domain Local group. Members of this group will be able to create, delete, and update the deployed network controller configuration. You need to create at least one user account that is a member of this group and have access to its credentials.
• Create an Active Directory security group for network controller clients - SDNCLIENT You need to create an Active Directory security group for network controller clients. The group should be a Domain Local group. Once the network controller is deployed, any members of this group will have permissions to communicate with the network controller via REST based interface. You need to create at least one user account that is a member of this group. After the network controller is deployed, VMM can be configured to use this user's account credentials to establish communication with the network controller.

• Rename computer Name as “HOST01 – HOST04”
• Join VMs to the SDN.LAB domain.
• Enable Hyper-V role on the VM, do not use Hyper-V to create VSwitch based on the VNIC.

• Rename computer Name as “SCVMM”
• Join VM to the SDN.LAB domain.
• Install .Net Framework V3.5 feature from Server Manager
• Install Windows Assessment and deployment kit (ADK)j
• Install SQL Server 2014
• Install SCVMM

• Rename VM Name as “Remote”
• Install Remote Access role
• Install IIS, change the default page of the default website to something meaningful, such as the HTML page with the content can show the page is on the remote host.

• MGMT – Management network routes off-cloud to other management subnets
• Transit Network routes off-cloud to external client subnets
• HVN Provider network only routes to other HNV Provider subnets in the cloud.

Add HOST01 – HOST04 to SCVMM

1. Open VMM Console, click “Fabric” and click on the “Servers > All Hosts”.
2. Right click the “All Hosts” and select “Add Hyper-V Hosts and Clusters”

1. Open the Fabric workspace in the VMM Console, expand Networking and select the Logical Networks
2. Right-click the Logical Network node and select Create Logical Network.
3. Specify “MGMT” as the name and optional Description for this network. Click Next.
4. On the Settings page, be sure to select One Connected Network, since all Management networks need to have routing and connectivity between all hosts in that network. Check the Create a VM Network with the same name to automatically create a VM Network for your Management network. Click Next.
5. In the Network Site panel, click Add to add a new network site. Select the host group for the hosts that will be managed by the network controller. Insert your management network IP subnet information. This network should already exist and be configured in your physical switch. Click Next when you are ready to proceed.
6. Review the Summary information and click Finish to complete.

1. Right-click the Management logical network in VMM and select Create IP Pool from the drop down menu.
2. Provide a name and optional description for the IP Pool and ensure that the Management network is selected for the logical network. Click Next.
3. On the Network Site panel, select the subnet that this IP address pool will service. Click Next.
4. On the IP Address range panel, type the starting and ending IP addresses. Important Don't use the first three IP addresses of your available subnet. For example, if your available subnet is from .1 to .254, start your range at .4 or greater. In IP addresses to be reserved for other uses, type one of the IP addresses from the specified range. This is the IP address that you will later use as the REST IP of the network controller Service. Click Next.
5. Next, configure the default gateway address.
6. Optionally configure DNS information.
7. Optionally configure WINS server information, but this is generally not required. Click Next.
8. Review the summary information and click Finish to complete the wizard.

1. Click Create Logical Switch on the ribbon in the VMM Console.
2. Review the Getting Started information and click Next.
3. Provide a “MGMT-LSWITCH” as the name and optional Description. For the Uplink mode, be sure to select No Uplink Team. Click Next.
4. For Minimum Bandwidth mode, choose the default option. Click Next.
5. Uncheck all the switch extensions in the Extensions This is a crucial step as selecting any of the switch extensions at this stage may block network controller on-boarding later.

1. Use the defaults for Load Balancing algorithm and Teaming Mode.
2. Make sure you select all the network sites that are part of the Management logical network you created. Leave the Load Balancing Algorithm as Host Default, and Teaming Mode as Switch Independent.
3. Select the Uplink Port Profile you created and click New virtual network adapter. This adds a host virtual network adapter (vNIC) to your logical switch and uplink port profile, so when you add the logical switch to your hosts, the vNICs get added automatically.
4. Provide a name for the vNIC. Verify that the Management VM network is listed under the Connectivity
5. Select This network adapter will be used for host management and then select Inherit connection settings from the host adapter. This allows you to take the vNIC adapter settings from the adapter that already exists on the host.
6. If you created a port classification and virtual port profile earlier, you can select it now.
7. Click Next.
8. Review the Summary information and click Finish to complete the wizard.

1. Click VMs and Services
2. Right click on HOST machine under “All Hosts” group
3. Click on “Virtual Switches” on the left and click on “New Virtual Switch” then Choose the Logical Switch you just created
4. Click on New Virtual Network Adapter to also create a VNIC

1. In VMM, navigate to Library.
2. In the top of the left pane, in the Templates section, select Service Templates.
3. In the ribbon at the top, click Import Template.
4. Browse to your service template folder, select the Network Controller Standalone Generation 2 VM.xml file and follow the prompts to import it.
5. The service template uses the following virtual machine configuration parameters. Update the parameters for your environment as you import the service template.

1. Select the network controller service template and click Configure Deployment to begin. You must type a Service name “NCService” and select a destination for the service instance. The destination must map to a Host Group that contains Windows Server RTM hosts and that is going to be managed by network controller.
2. On the left side of the Configure Deployment window, there are several settings that you must configure. The table below summarizes each field's values.

1. Navigate to the Fabric Node in the VMM console.
2. Right-click the Network Service icon under Networking and click Add Network Service.
3. The Add Network Service Wizard Click Next.
4. Input “NCService” as your network controller Network Service name. Then Click Next.
5. Select Microsoft for the manufacturer and for model select Microsoft network controller. Click Next.
6. On the Credentials tab, provide the RunAs account you want to use to configure the Network Service. This should be the same account that you included in the network controller Clients group. Click Next SERVERURL=https://SingleNodeNC.SDN.LAB;servicename=NCService
7. On the Review Certificates page, a connection is made to the network controller virtual machine to retrieve the certificate. Verify that the certificate shown is the one you expect. Ensure you select the These certificates have been reviewed and can be imported to the trusted certificate storebox check box. Click Next.
8. On the next screen, click Scan Provider to connect to your service and list the properties and their status. This is also a good test of whether or not the service was created correctly, and that you"re using the right connect string to connect to it. Examine the results, and ensure that the property isNetworkController = true is set. When it completes successfully click Next.
9. Configure the Host Group in VMM that your network controller will manage. Click Next.
10. Click Finish to complete the Add Network Service Wizard. When the service has been added to VMM, you should see it appear in the Network Services list in the VMM Console, and it should look similar to the following:

1. Start the Create Logical Network Wizard.
2. Type a “HNV” as the name and optional description for this network. Click Next.
3. On the Settings page, verify that One Connected Network is selected, since all HNV Provider networks need to have routing and connectivity between all hosts in that network. Ensure you check Allow new VM networks created on this logical network to use network virtualization. You will also see a new setting: Managed by the network controller. Ensure you check this box, and then click Next.

1. Right-click the HNV Provider logical network in VMM and select Create IP Pool from the drop down menu.
2. Provide a name and optional description for the IP Pool and ensure that the HNV Provider logical network is selected for the logical network. Click Next.
3. On the Network Site panel, you need to select the subnet that this IP address pool will service. If you have more than one subnet as part of your HNV Provider network, you need to create a static IP address pool for each subnet. If you have only one site (for example, like the sample topology) then you can just click Next.
4. On the IP Address range panel, configure the starting and ending IP address. Click Next Important Don't use the first three IP addresses of your available subnet. For example, if your available subnet is from .1 to .254, start your range at .4 or greater.
5. Next, configure the default gateway address. Click Insert next to the Default gateways box, type the address and use the default metric. Click Next.
6. Optionally configure DNS information, but this is generally not required.
7. Optionally configure WINS server information, but this is generally not required. Click Next.
8. Review the summary information and click Finish to complete the wizard.
9. As part of network controller on-boarding, the switch that you deployed on the hosts for the Management logical network connectivity was converted to an SDN switch. This switch can now be used to deploy a network controller managed network including the HNV Provider logical network. Ensure you select the network site corresponding to the HNV Provider logical network in the uplink port profile settings for the Management logical switch.

1. Open System Center Virtual Machine Manager (SCVMM) Console Double-click the Virtual Machine Manager Console icon on the Desktop Leave default login settings as-is with Server name: localhost:8100| Click “Connect”
2. Open the VM Networks and IP Pools Pane Click on “VMs and Services” in the bottom-left hand side of the console Click on “VM Networks” in the “VMs and Services” Pane Click “VM Networks” in the Ribbon menu
3. Open Create VM Network Wizard Click “Create VM Network” in Ribbon menu
4. Configure VM Network Name and Description Input “CONTOSO” as the name for the virtual network you are creating Optionally, provide a description for the virtual network Make sure Logical network is set to HNV Click “Next”
5. Select Isolation Leave the default radio button selection; “Isolate using Hyper-V network virtualization” Leave the default IP address protocol for both the VM and logical network as IPv4 Click “Next”
6. Create VM Subnets Click “Add” button Enter a “Subnet1” as the name for the first VM Subnet Enter the subnet (IP Prefix) – 192.168.1.0/24 – for the first VM subnet. You need to make sure to use 192.168.1.0/24 as your first subnet. Click “Add” button again Enter a name for the second VM Subnet (E.g. “Subnet2”) Enter a subnet for the second VM subnet (E.g. 192.168.2.0/24) Click “Next”
7. Skip Connectivity Section We will not be providing external connectivity for this virtual network through a VPN tunnel, direct routing, or NAT in this exercise. Click “Next”
8. Create VM Network Click the View Script button to see the SCVMM PowerShell script used to create this network Click “Finish”
9. Create an IP Pool Right-click the Virtual Network you just created and select “Create IP Pool"
10. 10.Specify the IP Address Pool Name and VM Subnet Note: You will be creating a separate IP Pool for each VM Subnet Input “Pool1” in the Pool name and optionally provide a description Ensure the VM Network listed is the VM Network you just created Select the first “Subnet1” you created Click “Next”
11. Specify an IP Address Range No action is necessary on this page. Click Next. Leave the Starting and Ending IP addresses as the default There is no need to reserve an IP addresses for VIPs or other use
12. Specify a Gateway No action is necessary on this page. Click Next. The lowest IP address in the subnet is the default gateway – this will be chosen automatically if field is left blank.
13. Skip Specify a DNS server Click “Next”
14. Skip Specify a WINS server Click “Next”
15. Create First VM Subnet’s IP Pool Click “Finish” to confirm settings and create the IP Pool
16. Create Second VM Subnet’s IP Pool Input “Pool2” as the second pool name Repeat steps 9 – 15, for your second VM Subnet - Subnet2
17. Create a Virtual Machine Click “All Hosts” in the “VMs and Services” pane on the left-hand side of the screen Click “VMs” icon in the Ribbon menu Click, “Create Virtual Machine” and select “Create Virtual Machine” from the Ribbon menu
18. Select the source for the new Virtual Machine Use the default option “Use an existing virtual machine, …” and click “Browse” Navigate down to the sys-prep Windows Server 2016 VHD you copied to the SCVMM template library in “VHDX TYPE” section and click it, then select “OK” Click “Next”
19. Specify Virtual Machine Identity Input “VM1” as the name for the virtual machine and optionally enter a description. Make sure “Generation 2” is selected. Please leave “Turn on shielding support in the virtual machine after deploying it” unchecked. Click “Next”
20. Configure Hardware Under “Compatibility,” click the “Hyper-V” profile Under “General” in the left menu pane, select “Processor” and ensure “number of processors” is set to 2. Maintain default settings of 2 processors and 2048 MB of memory Under “Network Adapters,” select “Network Adapter 1” On the right-hand side of the window under “Connectivity,” select “Connected to a VM network”. Browse to the “CONTOSO” VM Network you previously created – Select a VM Subnet attached to the “Subnet1” subnet you previously created Click “Next”
21. Place the virtual machine on a host Click “Next” to skip “Select Destination” step. Choose the first recommended host on which to deploy this virtual machine Particularly if you are completing this step for the second time (after reaching step 26 of this exercise), feel free to select a different Hyper-V host – assuming it is recommended with three or more stars - to spread out the VM deployments. Click “Next”
22. Skip Configure Settings Click “Next”
23. Skip Add Properties Section Select the “Start the virtual machine after deploying it” checkbox. Click “Next”
24. Confirm Settings and Deploy VM Select the “Start the virtual machine after deploying it” checkbox Click “Create” It will take a few minutes to create the virtual machine. Check the Jobs pane to see when deployment is complete.
25. Create another Virtual Machine Repeat Steps 17 – 25 above with a different VM Name “VM2” and different Subnet “Subnet2” For this exercise, please do not create more than two VMs as physical memory and CPU is limited
26. Open a console session to the VMs Check the Virtual Machine State for your VMs. If the status says “Stopped”, then right click on the VM, and click “Power On”. Check the Status of your VMs. After the status of each of your Virtual Machines has changed to “Running” (as opposed to “Creating…”), select “VMs and Services” in the bottom-left hand side of the VMM console Click on “All Hosts” in the “VMs and Services” pane Click on “VMs” in the Ribbon menu Right-click any one of the VMs you just deployed and select “Connect or View” => “Connect via Console” Login with password, you setup for the VMs
27. Validate Virtual Network Connectivity in each of your created VMs Upon logging in, you may see a Networks pane on the right side. Click on “No”, although it does not matter what you pick. Right-click the Windows Icon in the Start Menu and click on a “Command prompt (Admin)”. Type “ipconfig” and press “Enter” Record the IP Address of the VM. Open a Console Session in another VM (open console using instructions in Step 26) and open its command prompt. Ping the first VM from the second VM (or vice-versa). You should receive several replies.
28. Config Firewall policy on both VM1 and VM2 to allow them to Ping each other. Run- New-NetFirewallRule -DisplayName “Allow ICMPv4-In” -Protocal ICMPv4
29. Login VM1 one, open CMD to ping VM2 IP to see if it works.
30. Congratulations! You just attached two of your VMs on different subnets to a virtual network. And they can route between each other. In a larger organization, you can create separate virtual networks for different apps and tenants, and they will be completely isolated from each other.