Change failover Cluster hyperV IP ( management and Heartbeat use the same network)

Question

Hello ,

I have a Cluster Hyper V 2019 with 4 nodes .what are the steps the change the ip address of the cluster and nodes ?

the VMs are connected via external vswitch directly to a physical switch

the heartbeat network and management network use the same network team

i assume that when changing the ip address of first node to the new ip all VMs on node1 will be migrated automatically to another node ....

Please provide a detailed action plan to this change properly

Regards

Answer 1

Hello APTOS,

Thank you for your question and for reaching out with your question today.

Changing the IP address of a Hyper-V cluster and its nodes requires careful planning and execution to ensure minimal disruption to the cluster and its virtual machines. Here's a detailed action plan to change the IP address of a Hyper-V cluster and its nodes:

1. Preparations:
   - Take a backup or snapshot of the cluster nodes and virtual machines to ensure data safety.
   - Notify users or stakeholders about the planned IP address change and any potential downtime or disruptions.
   - Document the current IP configuration of the cluster, including IP addresses, subnet masks, gateways, DNS settings, and any other relevant network settings.
   - Identify the new IP addresses you want to assign to the cluster and its nodes.
   - Verify that the new IP addresses are within the same subnet as the existing IP addresses to avoid changing the network topology.

2. Move VMs off the node:
   - Before changing the IP address of a node, it is recommended to evacuate the virtual machines (VMs) from that node to minimize disruption.
   - Use Live Migration or Quick Migration to move the VMs from the node you are going to change the IP address of to another node in the cluster.
   - Verify that all VMs have been successfully migrated to another node and are functioning correctly.

3. Change IP address of the first node:
   - On the first node of the cluster, change the IP address by following these steps:
     - Go to the Network and Sharing Center on the node.
     - Select the network adapter used for cluster communication and management.
     - Open its properties and change the IP address, subnet mask, gateway, and DNS settings to the new values.
     - Apply the changes and ensure the network connectivity is restored.

4. Update cluster IP address:
   - After changing the IP address of the first node, update the cluster IP address to reflect the new IP address of the node:
     - Open Failover Cluster Manager on any node of the cluster.
     - Connect to the cluster, right-click on the cluster name, and select "Properties."
     - In the "Cluster Core Resources" section, select the "IP Address" tab.
     - Update the IP address field with the new IP address of the first node.
     - Apply the changes and verify that the cluster IP address has been updated successfully.

5. Verify cluster functionality:
   - Ensure the cluster resources, such as the shared storage and virtual machine configuration, are accessible and functioning correctly.
   - Validate the cluster to ensure that the configuration is correct and there are no issues after the IP address change.

6. Repeat steps 3-5 for the remaining nodes:
   - Change the IP address of each remaining node in the cluster one by one, following the same steps outlined in step 3.
   - Update the cluster IP address to reflect the new IP address of each node, as described in step 4.
   - Verify the functionality of the cluster after each node's IP address has been changed.

7. Update network settings for VMs and virtual switches:
   - After changing the IP addresses of all cluster nodes, update the network settings for the VMs and virtual switches:
     - Open the Hyper-V Manager on each node.
     - Go to the settings of each VM and update the network adapters' IP settings to match the new network configuration.
     - Verify the connectivity and functionality of the VMs after the IP settings have been updated.

8. Update DNS records and other network-dependent configurations:
   - Update any DNS records, DHCP scopes, firewall rules, or other network-dependent configurations that reference the old IP addresses of the cluster and its nodes.
   - Update any monitoring or management tools that rely on the IP addresses of the cluster and its nodes.

9. Test and monitor:
   - Test the cluster

I used AI provided by ChatGPT to formulate part of this response. I have verified that the information is accurate before sharing it with you.

If the reply was helpful, please don’t forget to upvote or accept as answer.

Best regards.

Answer 2

Hello @Limitless Technology ,

I thank you for your detailed answer .I forgot to mention that the new IPs are will be not on the same subnet ..could maitain the same Action Plan ?

Thanks