Server 2022 Hyper-V SET/SIT Teaming with Nexus

[Rene Mueller]

Dear all,

we use Server 2022 with Hyper-V, managed by SCVUMM. Server Team setup SET Teaming for this Server which means Server itselfs manages and takes care of the Teaming (mode Switch embeeded Teaming with in Dynamic mode). On the Nexus switches which are setup with a vPC link, I configured a trunk port which carries the vlans. I did this on both Nexus switches. No Port-channel. this works so far and I can see that both team member connected switchports shows traffic and mac addresses in mac address table. However, as soon as I reboot one Nexus switch or just shut down one of of the Team member NIC ports, the Server gets in trouble and running virtual machines crashes. On the other hand, if I just disable a nic on Windows OS, Teaming still works for Hyper-V with no crash. I also recognized one more strange behavior, when I disable a NIC on Server OS, the nexus Switch still shows the port as "connect". no log entry. Whenver I enable this port on the server again, the Nexus switch now recognize it and shows log entries like line protocol down and up. 

[balaji.bandi]

Post the configuration of the Nexus side both the side configuration.

below example guide provide you for the Server vPC config ;

https://www.balajibandi.com/?p=618

[Rene Mueller]

Hi, thanks for your answer. However, we don't use LACP. Switch Independent Teaming is configured on the Server site. 

[eduardo-npereira]

Hello my friend,
Did you get any solution? I'm testing Hyper-V using Nexus switches without LACP configuration, and when I have two ports at the same time on the SET switch and when I restart the server it seems to me that it's causing a kind of loop in the network.

[Rene Mueller]

It seems that we got this fixed. I followed the examples on:

Cisco Nexus Recommended Practices

Configured vpc orphan-port suspend aswell as spanning tree port-type on the ports.