Monday, January 21, 2019

Trying to create a Hyper-V converged network, not getting anything but native VLAN traffic

Hi!

I'm setting up a three node Hyper-V cluster. I have two HP 1810-48g switches and an OPNsense firewall configured to allow all traffic to talk to each other.

On the HP switches, I untag the native VLAN 20 (My server network) and tag all of my other VLANs necessary for my cluster .

I expected Windows Server 2016 to be smart enough to route the traffic properly, however, I only get an IP (and traffic) on my native VLAN with static IPs (no DHCP on networks except 10, my client network, which is managed by my domain controller). So in other words, only my Management vNic works properly. All other nics state that they are "Identifying".

Here is the powershell code I used to create my network:

# "Converged-vNIC" is Team Name for NICs teaming. New-VMSwitch “Converged-vSW” -MinimumBandwidthMode weight -NetAdapterName “Converged-vNIC” -AllowManagementOS 0 Set-VMSwitch “Converged-vSw” -DefaultFlowMinimumBandwidthWeight 10 Add-VMNetworkAdapter -ManagementOS -Name “VMNetwork-vNIC” -SwitchName “Converged-vSW” Set-VMNetworkAdapter -ManagementOS -Name “VMNetwork-vNIC” -MinimumBandwidthWeight 10 Add-VMNetworkAdapter -ManagementOS -Name “Cluster-vNIC” -SwitchName “Converged-vSW” Set-VMNetworkAdapter -ManagementOS -Name “Cluster-vNIC” -MinimumBandwidthWeight 10 Add-VMNetworkAdapter -ManagementOS -Name “LiveMigration-vNIC" -SwitchName “Converged-vSW” Set-VMNetworkAdapter -ManagementOS -Name “LiveMigration-vNIC" -MinimumBandwidthWeight 10 Add-VMNetworkAdapter -ManagementOS -Name “iSCSI-vNIC” -SwitchName “Converged-vSW” Set-VMNetworkAdapter -ManagementOS -Name “iSCSI-vNIC” -MinimumBandwidthWeight 10 

This is a link to the tutorial I am using. Everything is accurate for my setup, except we are not using Starwind: https://www.youtube.com/watch?v=548cjgql2Wo

My Goal is to have the correct traffic flowing through all correct management interfaces as well as DMZ and VOIP traffic over the VMNetwork nic (The latter part will be acomplished in Hyper-V Manager with the VLAN tickbox. The default VLAN will be 20 of course).

I've been at this for a couple of days and can't seem to understand where the issue lies. I thank you all in advance for helping a total noob out!

-wrdz



No comments:

Post a Comment