We have a project with a customer to create a Hyper-V Cluster with 3 hosts.
They are all prepped with one 4 port copper network card and one 2 port fiber card.
The idea is to have Cluster heartbeat and Live migration traffic on the fiber cables and all other traffic on the copper cables.
We have no fiber switch available so the fiber is connected directly between the hosts, one cable between each host in a triangle.
My initial thought was to create a SET team on the 2 fiber ports on each host and attach 2 virtual cards on each, one for Cluster and one for Live Migration.
But now I have realized this might not work at all.
You'll have to correct me if I'm wrong here but both fiber ports won't be active at the same time on the SET team, leading to connection issues to the host with the not active connection connected.
Another thought I had was to maybe not have a SET team at all and instead create 2 Vnet adapters for each function (Cluster and Live Migration). And then have 1 of them to one of the fiber ports and the other to the second fiber port.
This will create more Virtual adapters on the host, allocate more IP addresses and create a bit more complex setup to maintain. But might be needed to solve this issue?
How would we design this in the best way when we have no fibre switch to use?
On this link is a visio diagram showing the setup: https://imgur.com/egTOgBx