Hello Friends,
my question today is revolving around Failoverclustering (which is sitting, in our case, on top of a S2D deployment). Everything is working fine in that regard.
Next week we will get new switches and I plan to trunk/lacp both SFP+ ports on the servers (at the moment only one SFP+ port of every server is connected to the switch) and connect them to the new switches.
Iam aware how trunking/lacp works on the powershell, thats not the problem. What I fear is the connectivity of the failovercluster itself. When I have to dissolve the Hyper-V Virtual Ethernet Adapter to form a new LACP, so I can create a new Virtual Adapter on top of the LACP, the failovercluster will lose the only management interface.
When I look into the Failovercluster MMC Snap-In under "Network" I can see my interfaces, but I dont see any buttons to add interfaces and declare them as management network (my idea was to use the copper ports of the server nic to create a temporary management interface until I have built the LACP/virtual adapter and integrate them as the primary management interface).
So the question remains: can I add (maybe through powershell) additional interfaces as management to the failovercluster or do I actually have to dissolve the whole cluster and build anew?
Thanks in advance.
Best Regards,
Constantin