Hyper-V Virtual Ethernet Adapter - Create host vlan interface

[CAWJames]

Morning all,

 

I am playing around with our Hyper-V setup, toying with the idea of Starwind VSan on our Dell NX series storage servers coupled to our current Dell 740 hosts.

 

The VSan bit is fairly easy, and I have created an asynchronous replication between the 2 NX's(as one will go up the road and be part of DR, if I sign off on this properly)

 

I have used a VLAN to segregate iSCSI traffic away from the normal LAN, pushed 8Gbps while replicating, so that should be fine

 

Now, on the NX's, I just created a single NIC team, and added a second interface referencing the VLAN, works great. Obv will multipath 10Gbe ports at a later date.

 

On the 740's its differnet as I have my Hyper-V Virtual Ethernet Adapter referencing a 10Gbe NIC with no IP settings, then that is passed to Hyper-V, so they can use the existing VLAN's. This means I can't team the interface and do the same as the NX's(I don't think).

 

Anybody got any idea how I can work this to get a VLAN interface onto the 740's host interface? Or am I stuck with just using another NIC untagged to that VLAN from the switch? Which isn't a problem...if I was able to get to work to sort that out, but things as they are, not so easy!

 

Thanks

 

James

[FN-GM]

If I have understood correctly you would set the VLAN ID in the Hyper-V switch settings. In there is a setting to set the VLAN ID for host management.

[CAWJames]

Thanks, but setting it in the switch would remove the whole interface from our main VLAN, I want to add a separate interface referencing just one VLAN to the host, to use for iSCSI traffic. I think I am plumb out of luck on this one tbh, I think I need to run another fibre to the core, and untag there back into a separate NIC

[FN-GM]

I want to add a separate interface referencing just one VLAN to the host, to use for iSCSI traffic.

 

You could set the VLAN ID here: On the NIC go to Network Connections -> Properties-> Advance Tab and select the VLAN ID

 

https://www.ionos.com/help/server-cloud-infrastructure/setting-up-a-private-network-for-dedicated-servers-windows-server-2012-r2-2016-and-2019/

 

Sorry I am a little tried so might be totally misunderstanding.

[CAWJames]

That's fine nice to have some input. Those are great ideas, but only if I wanted to change the VLAN ID for the whole interface, I want to keep the main interface on one VLAN, and create a logical secondary adapter that is on another VLAN. Usually this is done by enabling Teaming with just the one NIC member, and then adding a logical interface to the team with the VLAN ID, thereby creating a separate adapter in the adapter settings which can be used by programs on the host. I think as I am effectively passing the physical NIC's direct to the Hypervisor, where an interface is created for the management and VM's, I have taken this option off the table. My only option at the moment, is to actually use a physical NIC untagged on the VLAN to pass in the iSCSI traffic, which would be my preferred course of action, but when in lockdown, I wanted a "quick and easy" way to test! Thanks anyway, and I know the feeling, I think I am working harder now than I do when in the building at work!!!

[FN-GM]

I am with you now. I can't see why I wouldn't be possible - its the whole point of 802.1q. But I don't know how to do it as I have never needed to.

 

Sorry I can't help.