Deployed a new hyper-v server a few weeks ago and during install I read that the old way of NIC teaming does not work anymore for vswitches inside of a hyper-v. It was replaced with SET Teams that need to be set up in powershell. Cool, no biggie I think to myself. I got all that figured out and a SET team set up with 4 physical NICs and one "SET team".
Now for background I am a network engineer at a small hospital, not much of a sysadmin. And our sysadmin here is... for the lack of a nicer term, unexperienced, despite working here for 12 years. So much of this has been me researching and stabbing in the dark.
Now for the issue:
The hyper-v host works fine. no issues there at all. It uses the SET team (switch embedded teaming), and is set for vlan tagging on vlan 2 (SET teaming is weird compared to old NIC teaming I guess, where you cannot do "dynamic" and use port channels, it only works with switch independent teaming, hence needing to tag the management vlan).
The VM is running windows server 2019 (IPAM server), vlan 2 tagged, IP is correct and gateway is also correct. It connects to the network, and can ping (with caveats). see below:
Reply from 10.0.2.124: bytes=32 time=1ms TTL=255
Request timed out.
Request timed out.
Request timed out.
Reply from 10.0.2.124: bytes=32 time=1ms TTL=255
Reply from 10.0.2.124: bytes=32 time=1ms TTL=255
Reply from 10.0.2.124: bytes=32 time=1ms TTL=255
Request timed out.
Request timed out.
Reply from 10.0.2.124: bytes=32 time=1ms TTL=255
Reply from 10.0.2.124: bytes=32 time=1ms TTL=255
Reply from 10.0.2.124: bytes=32 time=1ms TTL=255
Request timed out.
Reply from 10.0.2.124: bytes=32 time=1ms TTL=255
Reply from 10.0.2.124: bytes=32 time=1ms TTL=255
Reply from 10.0.2.124: bytes=32 time=1ms TTL=255
Reply from 10.0.2.124: bytes=32 time=1ms TTL=255
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 10.0.2.124: bytes=32 time=1ms TTL=255
Reply from 10.0.2.124: bytes=32 time=1ms TTL=255
Request timed out.
Reply from 10.0.2.124: bytes=32 time<1ms TTL=255
10.0.2.124 is our gateway for this network (the old network guy insisted on making all the gateways .124, i guess to confuse everyone? not sure)
I lose connectivity to this machine randomly and sometimes for a minute or so at a time. it appears to be somewhat frequent.
I cannot for the life of me figure out what could be causing this. I admit I do not know much about SET teaming and the sysadmin side of things, but our network config is correct.
Any help is appreciated. This is killing me.
verified network config, verified SET team config (from what I can tell), ran hours of pings and nothing resolved, changed gateways, changed masks
