Friday, October 1, 2021

Hyper-V Guest VLAN Connectivity Issue - Or lack there of

This is my first Hyper-V Guest that I have tried to run strictly in a VLAN. I"m trying to create a backup server to run off of my 10G Server / Storage switch. This is my Environment:

  • X3 Dell R440 Win 2019 Servers in Failover Cluster with 4 Port 10G NIC
    • 10G NIC 1&2 Teamed VLAN4 for Storage 10.4.0.1X/24
  • FreeNas JBOD 10G Teamed Dual NIC VLAN4 10.4.0.10/24
  • Dell T340 Win 2019 with Dual 10G NIC Teamed No VLAN Assignment 10.4.0.20/24
  • Synology 12 Bay NAS with Dual 10G NIC Teamed VLAN 4 10.4.0.30/24
  • X 2 Netgear XS716E Prosafe
    • 10GSwitch01
    • Port 1, 2, 3, 4, 16 - Tagged VLAN4
    • ClusterServer and JBOD Connected to Ports 1-4
    • 10GSwitch02
    • Port 1, 2, 3, 4, 16 - Tagged VLAN4
    • ClusterServer and JBOD Connected to Ports 1-4
    • Port 11, 12, 13, 14 - Untagged VLAN4
    • BackupServer and NAS Connected to Ports 11-14

From the BareMetal T340 I can ping all IT assets, from the installed Hyper-V Guest I cannot ping anything including the Hyper-V Host

This is what I have tried:

  • Set VLAN4 in the 10GVSwitch - breaks the BareMetal Connection to the other network assets
  • Set VLAN4 in the Hyper-v Guest NIC through the Hyper-V Manager
  • Set VLAN4 for in the Windows Network Properties in the Hyper-V Guest
  • Set Ports on switch to Tagged VLAN4
  • Ran PowerShell command to set VM Adapter as untagged (Get-VM VMGuest | Set-VMNetworkAdapterVlan -Untagged)
  • Set Port on switch as Trunk

Why? 2 reasons - I don't want this backup on my main network for obvious RansomWare reasons and secondly we have about 120 TB of data and growing that needs to be backed up and it bogs the network down when the backups run.

Help me Obiwan, you are my only hope!!



No comments:

Post a Comment