Creating a NIC Team and Virtual Adapters under Windows for Hyper-V in a VPR

This tutorial will explain how to create a bond interface, and virtual switches in a VPR Network.

Bonding or NIC Teaming is when you use both physical NICs to create a logical interface.

This allows us to have redundancy in case one of the NICs fail.

For more information on NIC Teaming, see the official Microsoft Documentation.

Requirements:

  • Hyper-V must already be installed on the host
  • You must have a KVM over IP or IPMI since we will completely reconfigure the network of the host
  • Your server must be in a VPR Network

Here are the steps:

Step 1 - Creating the Team interface

*** This step must be performed from a KVM over IP or IPMI ***

  • Open Server Manager and go to Local Server
  • In NIC Teaming, click the blue text to the right (Enabled or Disabled)

1.png

  • Under TEAMS, click on TASKS, and click New Team

2.png

  • Select both interfaces
    Make sure the properties are as follows:

Teaming Mode: LACP
Load Balancing Mode: Dynamic

2.1.png

Results:

3.png

Step 2 - Creating the Hyper-V Virtual Switch

  • Open up Hyper-V Manager and under actions, select Virtual Switch Manager
  • Create a new External Switch, give it the name vSwitch
  • Make sure that under External Network, the new Team Interface is selected
    Interface should be called "Microsoft Network Adapter Multiplexor Driver"

hv1.png

Step 3 - Creating Virtual Ethernet Adapters

  • Open up Powershell and type the following to create a Virtual Ether Adapters using our newly created vSwitch (create one for WAN and one for LAN)
Add-VMNetworkAdapter -ManagementOS -Name "Lan" -SwitchName "vSwitch"
Add-VMNetworkAdapter -ManagementOS -Name "Wan" -SwitchName "vSwitch"

vada.png

Note: if you have other VLANs assigned by iWeb during your delivery or you are in a VPR2 network, you can create a corresponding adapter for your nodes to be able to communicate with the subnet in that VLAN, if you do not need your Hyper-V node to connect to your LAN or other VLANs, you do not need to add the adapters, you can still have a working network in your VMs by tagging the VMs with the appropriate VLAN without adding an adapter on the host. 

VPR1:

  • Tag the provided VLAN on the LAN and WAN interface
Set-VMNetworkAdapterVlan -ManagementOS -VMNetworkAdapterName "LAN" -Access -VlanId 100
Set-VMNetworkAdapterVlan -ManagementOS -VMNetworkAdapterName "WAN" -Access -VlanId 3000

vlan100.png

  • We can now reconfigure the IPs of each subnet on each Virtual Adapters

VPR2:

Note: In VPR2 you can create 4,094 LAN VLANs, in this example, we will create 1 VLAN and assign 100, you can assign any VLAN ID from 1-4094 when creating your LAN network(s).

  • Tag the provided VLAN on the LAN interface ONLY
Set-VMNetworkAdapterVlan -ManagementOS -VMNetworkAdapterName "LAN" -Access -VlanId 100

vlan100.png

  • We can now configure the IPs of each subnet on each Virtual Adapters

Step 4 - Adding IP to the Interfaces

2019-11-29_15-41.png

2019-11-29_15-41_1.png

Step 5 - Adding the VLANs to the VMs

VPR 1.0

Right-click on your VM and go to "Settings..." In a VPR 1.0 you will need to tag the VLAN for the WAN and LAN network adapter in the settings for the VM.

WAN

Screenshot_from_2019-11-29_15-29-49.png

LAN

Screenshot_from_2019-11-29_15-30-06.png

 

VPR 2.0

In a VPR 2.0 you only need to tag the VLAN of the LAN interface, In order to have a WAN IP on your VM you will need to keep the VLAN ID option disabled in your VM settings.

WAN

Screenshot_from_2019-11-29_15-27-35.png

LAN

Screenshot_from_2019-11-29_15-28-51.png

You can now connect to your VMs console to configure your LAN or WAN IP.

 

 

 

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk