{"id":1614,"date":"2024-11-11T20:19:26","date_gmt":"2024-11-11T18:19:26","guid":{"rendered":"https:\/\/www.shukko.com\/x3\/?p=1614"},"modified":"2024-11-11T20:27:29","modified_gmt":"2024-11-11T18:27:29","slug":"proxmox-change-ip-of-a-cluster-node","status":"publish","type":"post","link":"https:\/\/www.shukko.com\/x3\/2024\/11\/11\/proxmox-change-ip-of-a-cluster-node\/","title":{"rendered":"Proxmox Change IP of a cluster node"},"content":{"rendered":"\n

Ok, I have this figured out and the result is largely why I started this thread – every procedure I have found is incomplete or has major assumptions that may not be obvious. So, future Googlers, here is the deal. Do this is in this order on the respective nodes.<\/p>\n\n\n\n

NODE = the node that is getting the new IP.
CLUSTER = all other Proxmox nodes that will maintain quorum and can talk to one another throughout this procedure.
ONE CLUSTER = any one single node within CLUSTER<\/p>\n\n\n\n

On NODE<\/p>\n\n\n\n

1. Edit \/etc\/pve\/corosync.conf.
2. Update the IP for NODE.
3. Increment<\/p>\n\n\n\n

Code:<\/p>\n\n\n\n

config_version:<\/code><\/pre>\n\n\n\n
This change should push out a new corosync.conf to all nodes in CLUSTER. Confirm all nodes in CLUSTER have the new \/etc\/pve\/corosync.conf. At this point the cluster will be broken. If you run<\/p>\n\n\n\n
Code:<\/p>\n\n\n\n
 pvecm status<\/code><\/pre>\n\n\n\n
on the NODE, you will see it can’t find the rest of the nodes in the cluster. If you run<\/p>\n\n\n\n
Code:<\/p>\n\n\n\n
 pvecm status<\/code><\/pre>\n\n\n\n
on CLUSTER you will see they can all see each other but NODE is missing.<\/p>\n\n\n\n
Still on NODE
1. Edit \/etc\/network\/interfaces and update the IP to the desired IP.
2. Edit \/etc\/hosts and update the IP to the new IP.
3.<\/p>\n\n\n\n
Code:<\/p>\n\n\n\n
ifdown vmbr0; ifup vmbr0<\/code><\/pre>\n\n\n\n
to get your interface to have the new static IP. Change “vmbr0” to the name of your interface.
4. Restart corosync and pve-cluster.<\/p>\n\n\n\n
Code:<\/p>\n\n\n\n
systemctl restart corosync<\/code><\/pre>\n\n\n\n
Code:<\/p>\n\n\n\n
systemctl restart pve-cluster<\/code><\/pre>\n\n\n\n
On CLUSTER
1. Restart corosync on EVERY member of CLUSTER.<\/p>\n\n\n\n
Code:<\/p>\n\n\n\n
systemctl restart corosync<\/code><\/pre>\n\n\n\n
At this point<\/p>\n\n\n\n
Code:<\/p>\n\n\n\n
pvecm status<\/code><\/pre>\n\n\n\n
should show all nodes as being in the cluster, good quorum, and NODE has its proper IP. Be patient as this can take a minute. To be extra sure, run<\/p>\n\n\n\n
Code:<\/p>\n\n\n\n
cat \/etc\/pve\/.members<\/code><\/pre>\n\n\n\n
on NODE and this should show all the correct IPs.<\/p>\n\n\n\n
Additional cleanup.<\/p>\n\n\n\n
On NODE:<\/p>\n\n\n\n
1. Optional: Edit \/etc\/issue. Update to the new IP on NODE. This ensures the console login screen shows the right IP.
2. Edit \/etc\/pve\/storage.cfg and update any references to the old NODE IP – likely only an issue if you run PVE and PBS next to each other.
3. Optional: Edit \/etc\/pve\/priv\/known_hosts and update the IP of NODE.<\/p>\n\n\n\n
Other weirdness: In this process I have found sometimes VMs and containers lose their network connection and need to be rebooted. I haven’t found a good way to avoid this or fix it beyond a VM\/CT reboot. If anyone has an idea to make this 100% zero downtime (or near zero downtime), let me know and I’ll add that step.<\/p>\n\n\n\n
second one<\/p>\n\n\n\n
different writer<\/p>\n\n\n\n
<\/p>\n\n\n\n
Stop the cluster services<\/h1>\n\n\n\n
systemctl stop pve-cluster
systemctl stop corosync<\/p>\n\n\n\n
Mount the filesystem locally<\/h1>\n\n\n\n
pmxcfs -l<\/p>\n\n\n\n
Edit the network interfaces file to have the new IP information<\/h1>\n\n\n\n
vi \/etc\/network\/interfaces<\/p>\n\n\n\n
Replace any host entries with the new IP addresses<\/h1>\n\n\n\n
vi \/etc\/hosts<\/p>\n\n\n\n
Edit the corosync file and replace the old IPs with the new IPs for any changed hosts<\/h1>\n\n\n\n
BE SURE TO INCREMENT THE config_version: x LINE BY ONE TO ENSURE THE CONFIG IS NOT OVERWRITTEN<\/h1>\n\n\n\n
vi \/etc\/pve\/corosync.conf<\/p>\n\n\n\n
Edit the known hosts file to have the new IP(s)<\/h1>\n\n\n\n
\/etc\/pve\/priv\/known_hosts<\/p>\n\n\n\n
If using ceph, edit the ceph configuration file to reflect the new network<\/h1>\n\n\n\n
(thanks u\/FortunatelyLethal)<\/h1>\n\n\n\n
:%s\/192.168.1.\/192.168.2.\/g <- vi command to replace all instances<\/h1>\n\n\n\n
vi \/etc\/ceph\/ceph.conf<\/p>\n\n\n\n
If you want to be granular\u2026 fix the IP in \/etc\/issue<\/h1>\n\n\n\n
vi \/etc\/issue<\/p>\n\n\n\n
Verify there aren’t any stragglers with the old IP hanging around<\/h1>\n\n\n\n
cd \/etc
grep -R ‘192.168.1.’ *
cd \/var
grep -R ‘192.168.1.’ *<\/p>\n\n\n\n
Reboot the system to cleanly restart all the networking and services<\/h1>\n\n\n\n
reboot<\/p>\n\n\n\n
Referenced pages:<\/h1>\n\n\n\n
– https:\/\/forum.proxmox.com\/threads\/change-cluster-nodes-ip-addresses.33406\/<\/h1>\n\n\n\n
– https:\/\/pve.proxmox.com\/wiki\/Cluster_Manager#_remove_a_cluster_node<\/h1>\n\n\n\n
<\/p>\n\n\n\n
<\/p>\n\n\n\n
third one:<\/p>\n\n\n\n
<\/p>\n\n\n\n
Change node\u2019s IP address #<\/a><\/h3>\n\n\n\n
    \n
  1. Update the node\u2019s IP address in the following files:\n