I just want to state this in advance - I'm not a networking engineer, but I'm trying to learn more about how hyper-v clustering should be built from the networking side.
We have a hyper-v cluster that was setup previously and we're trying to figure out why it was setup the way it was. It currently seems like it's setup with 10gig feeding into the supermicro frame switches, on which multiple VLANs are trunked. Then, in the hyper-v switch manager, those VLANs are broken out into their respective networks, and I believe this is how the hyper-v cluster node gets its network connection.
I don't know a whole lot about these supermicro frame switches, but I'm venturing to guess that I can break out the various VLANs into multiple networks at the hardware level so they appear to each of the nodes as physical adapters, and then those can be assigned appropriately to hyper-v, or I can break them out virtually using Hyper-v and the node gets it's connection from the virtual adapter.
So, is there a preferred way to go about this? My gut feeling is to break it out (if possible) before the nodes so that the nodes see separate adapters (management, hyper-v, client (trunked), storage, etc), and then we assign the respective adapters where they need to go instead of relying on the hyper-v service to break it out. Or, do we want to virtualize it all - is one way preferred or more stable?
I hope I got all the terminology right - I'm trying to learn this stuff so your help and patience is appreciated!!