This tutorial will explain how to create a bond interface, and virtual switches in a VPR2.0 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.
- 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 2.0 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 Disabled
- Under TEAMS, click on TASKS, and click New Team
- Select both interfaces
Make sure the properties are as follows:
Teaming Mode: LACP
Load Balancing Mode: Dynamic
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
Step 3 - Creating Virtual Adapters
- Open up powershell and type the following to create a Virtual 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"
- Tag the provided VLAN on the LAN interface ONLY
Set-VMNetworkAdapterVlan -ManagementOS -VMNetworkAdapterName "LAN" -Access -VlanId 100
- We can now reconfigure the IPs of each subnet on each Virtual Adapters
Congratulations, you now have a functioning Hyper-V Host running with the network configuration of a VPR 2.0