We have a 3 host node cluster on HyperV
The networking on each host is set up as follows:
1. 2 x 2 port 10GB NIC
2. 1 x quad port 1GB NIC
3. 4 x onboard 1G NIC
Each host is set up as follows (settings taken from the Networks settings in the Failover Cluster Manager & the individual machine settings):
A. All 10GB NICs (#1 above) are used for communication to an Equallogic SAN for cluster shared volumes and ISCI traffic through a dedicated SAN switch (Cluster use is disabled)
B. Quad port NIC (#2 above) does not show up in Failover Cluster Manager and is used for VM general traffic (all four in a team to the 48-port main server switch)
C. 4 onboard NICS (#3 above) are also wired into a 48-port main server switch and set to:
1. Host management (Cluster use allowed, hosts / clients are allowed to connect). IP range is 10.1.1.22/23/24 subnet 10.1.0.0/23
2. “Live Migration”: (Cluster use allowed, hosts / clients are not allowed to connect). IP range is 172.16.0.9/10/11 subnet 18.104.22.168/29
3. “Heartbeat”: (Cluster use allowed, hosts / clients are not allowed to connect). IP range is 172.16.0.1/2/3 subnet 22.214.171.124/29
4. “Backup Heartbeat and Live Migration”: (Cluster use allowed, hosts / clients are not allowed to connect). IP range is 172.16.0.17/18/19 subnet 126.96.36.199/29
Note that the VM traffic and cluster traffic are on the same physical switch (B & C above)
We now want to move the cluster internal traffic (C2, C3 & C4 above) to a new switch so there is no contention with the VM general traffic and to save ports for additional hosts. i.e. we want to take the nine cables (3 x 3 hosts) and plug them into a new switch dedicated to cluster traffic.
My questions are:
1. Is there anything that really tells Hyper-V that one network is for heartbeats and one is for live migration traffic? Or are they just labels and Hyper-V figures it out based on whether the network allows cluster traffic or not?
2. Do we need to schedule downtime to do this?
Can we move one network at a time using the following process:
I. Take the first cluster network, change the setting so the network does not allow cluster traffic in the Failover Cluster Manager
II. Move the cables to the new switch
III. Re-enable cluster traffic
IV. Repeat for the other two networks
Do we need to stop and start cluster services to do this? If so, we might as well schedule downtime as that will initiate a mass Live Migration, right?
3. Is there another way to do this without downtime?