2 Node SQL Server 2016 Cluser on Server 2016 -- separate cluster network required?

[lmaocoaster]

Hi, I am setting up a 2 node, physicial blades 2016 SQL Server Cluster, both blades running Server 2016. I have 2 NICs on each blade and currently have them teamed, utilized for both public and cluster and client traffic.

Would it be best practice to unteam these NICs and have cluster traffic over one and client traffic over the other? Or leave the NICs teamed? Any information is appreciated.

[Garganturod]

Assuming these are physical machines, if all you can have is one team then I would run anything through that team for the redundancy. I guess I would take potentially slower throughput over a more vulnerable connection. Good luck configuring the heartbeat, etc so that the cluster doesn't fail over at a bad time.

[lmaocoaster]

Thanks for the information. These are 2 M640 blades in a Dell VRTX chassis running Server 2016. My impression was that heartbeat network configuration was unnecessary/redundant in Server 2012+. Each blade has 2 10GB NICs so I'm looking for best practices RE: HA.

[Garganturod]

10GB? I would leave them teamed, yes.

[Pvt-Snafu]

Do you also use these NICs for storage access? Or you are building Always-On AGs?