I am implementing a Hyper-V converged network (4 cluster nodes), however having an communications issue on the vNICs connected to my management switch.
The same issue on all 4 nodes. If anyone has any suggestions, I would appreciate it.
Each host has the following
- 8 physical NICS (NIC1-NIC8)
- NIC1 –a temporary management of IP of vLAN151
- NIC4 - spare
2 Teams (Configuration below)
- ManagementTeam – NIC6/7
- VirtualMachineTeam – NIC2/3/5/8
2 Virtual Switches
- Management Switch – 3 virtual NICs created for Management (vLAN151), Live Migration (vLAN152) & CSV traffic (vLAN153)
- Virtual Team Switch – no virtual NICs
1 Physical Switch Stack
- NICs 6/7 – ports trunked, vLAN 151, 152, 153 permitted
- NICs 2/3/5/8 – ports trunked, vLAN 400, 800, 71 permitted
I ran the following attached PS commands (without any errors) to create & configure Teams, Virtual Switches, Virtual NICs – per host.
# Create Management NIC TeamNew-NetLbfoTeam -Name "ManagementTeam" -TeamMembers "NIC6","NIC7" -TeamNicName "ManagementTeamNIC" -TeamingMode SwitchIndependent -LoadBalancingAlgorithm “TransportPorts”
# Create a Hyper-V Virtual Switch that binds to the NIC team
New-VMSwitch “Management Switch” –NetAdapterName “ManagementTeamNIC” –MinimumBandwidthMode Weight –AllowManagementOS $false
# Create a virtual NIC in the management operating system for Live Migration
Add-VMNetworkAdapter –ManagementOS –Name “LM” –SwitchName “Management Switch”
# Create a virtual NIC in the management operating system for Cluster/CSV
Add-VMNetworkAdapter –ManagementOS –Name “CSV” –SwitchName “Management Switch”
# Create a virtual NIC in the management operating system for Management
Add-VMNetworkAdapter –ManagementOS –Name “Management” –SwitchName “Management Switch”
# Assign a weight to Management
Set-VMNetworkAdapter –ManagementOS –Name “Management” –MinimumBandwidthWeight 10
# Assign a weight to Live Migration
Set-VMNetworkAdapter –ManagementOS –Name “LM” –MinimumBandwidthWeight 50
# Assign a weight to Cluster
Set-VMNetworkAdapter –ManagementOS –Name “CSV” –MinimumBandwidthWeight 40
# assign a VLAN to a virtual network adapters in the Management OS
Set-VMNetworkAdapterVlan –ManagementOS –VMNetworkAdapterName "Management" –Access –VlanId 151
Set-VMNetworkAdapterVlan –ManagementOS –VMNetworkAdapterName "LM" –Access –VlanId 152
Set-VMNetworkAdapterVlan –ManagementOS –VMNetworkAdapterName "CSV" –Access –VlanId 153
# Create Virtual Machine NIC Team
New-NetLbfoTeam -Name "VirtualMachineTeam" -TeamMembers "NIC2","NIC3","NIC5","NIC8" -TeamNicName "VMTeamNIC" -TeamingMode SwitchIndependent -LoadBalancingAlgorithm HyperVPort
# Create a Hyper-V Virtual Switch that binds to the NIC team
New-VMSwitch “Virtual Machine Switch” –NetAdapterName “VMTeamNIC” –AllowManagementOS $false
# Now configure IP addresses on NICs
Get-NetAdapter -Name "vEthernet (Management)" | New-NetIPAddress -IPAddress 172.16.151.5 -Defaultgateway 172.16.151.1 -Prefixlength 24
Get-NetAdapter -Name "vEthernet (Management)" | Set-DnsClientServerAddress -ServerAddresses ("137.191.4.194","137.191.4.43")
Get-NetAdapter -Name "vEthernet (CSV)" | New-NetIPAddress -IPAddress 172.16.153.5 -Prefixlength 24
Get-NetAdapter -Name "vEthernet (LM)" | New-NetIPAddress -IPAddress 172.16.152.5 -Prefixlength 24
Note - Cluster Node 1 has following IPs presented to the ManagementOS
NIC1 – 172.16.151.55/24 (temp management)
"vEthernet (Management)" - 172.16.151.5/24 -Defaultgateway 172.16.151.1
"vEthernet (CSV)" - 172.16.153.5/24
"vEthernet (LM)" - 172.16.152.5/24
Some of the testing results:
Ping 172.16.151.1 – Works Fine – Note, the system using the temp management IP 172.16.151.55 as the source
Ping 172.16.151.5 –S 172.16.151.5 – works fine
Ping 172.16.152.5 –S 172.16.152.5 – works fine
Ping 172.16.153.5 –S 172.16.153.5 – works fine
Ping 172.16.151.1 –S 172.16.151.5 – FAILS - so unable to ping the Default Gateway using
"vEthernet (Management)" as source IP.
Conclusion
Therefore it seems I can’t pass any traffic via the Virtual NICS & Management Virtual Switch. The physical Network Teams look ok. All the ports on the physical switch stack are UP.
Phyiscal ports are trunked and required vLANs permitted
