Change Cluster IP and network Node - Changement de l'adresse IP d'un cluster

B

BkBk

New Member
Aug 13, 2024
16
1
3
Hello,
I need to change proxmox server IP adress because we moved new plant.
Could you tell me how to proceed to avoid to break cluster already put in place ?
Could you tell me if it's possible to proceed step by step on proxmox server one by one.
IP cluster server will be change to 192.168.10.53 at the place 192.168.1.53 and all the node will be change also.
Have you any documentation or video that I found to explain step by step how to proceed.
Thank you very much for your help.
Boris

Bonjour,

Je vais devoir modifier l’adresse ip des serveurs Proxmox. Cependant, nous avons un Cluster proxmox déjà mis en place.

Pourriez vous svp nous indiquer comment procéder afin de ne pas casser ce qui a été mis en place et faire en sorte que le Cluster puisse continuer à fonctionner ?
Peut on changer l'adresse IP progressivement des serveurs proxmox et du cluster ?

En effet l’adresse IP de référence Cluster va changer en 192.168.10.53 au lieu de 192.168.1.53 ainsi que tous les autres noeux proxmox.
Existe une documentation ou une vidéo pour faire ce changement ?

Merci beaucoup pour votre aide et support
Boris

1755180105771.png


1755180203986.png
 
Last edited:
Hello,
I think you can start by adding the new IPs as [1] redundant links to the existing cluster. Then verify the setup as described in the documentation by temporarily disconnecting the old link on one node and ensuring that its status remains online while disconnected.

Once this is confirmed, you can proceed to move the VMs to the new IP ranges. In any case, it's [3][4] recommended to use a separate network for Corosync, as it requires consistent low latency. A dedicated 1 Gbit NIC is sufficient in most situations.

[5] As the final step, plan for the removal of the old IPs if necessary. Depending on your setup, the IPs will need to be changed in the following locations:
/etc/network/interfaces (on each node)
/etc/hosts (on each node)
/etc/pve/corosync.conf (only needs to be updated on one node)

Be sure to create a backup before making changes, so you can easily revert in case something goes wrong.

[1] https://pve.proxmox.com/pve-docs/chapter-pvecm.html#_adding_redundant_links_to_an_existing_cluster
[2] https://forum.proxmox.com/threads/change-cluster-nodes-ip-addresses.33406/
[3] https://pve.proxmox.com/pve-docs/chapter-pvecm.html#pvecm_cluster_requirements
[4] https://pve.proxmox.com/pve-docs/chapter-pvecm.html#_separate_cluster_network
[5] https://forum.proxmox.com/threads/change-cluster-nodes-ip-addresses.33406/
 
Hello,
Thank you very much for you help and support and all link documentation.
Boris
 
Always welcome.
I wanted to add one remark in case you are using HA (High Availability).
If you are using HA, it's better to stop it during this operation. The reason is that when a node hosting HA services loses Corosync quorum for around 60 seconds, it will fence itself so that its HA resources can be recovered on another node that still has quorum after 120 seconds.
Please refer to [6] for more information about fencing.

[6] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#ha_manager_fencing
 
You must log in or register to reply here.
Top Bottom