Hi, I'm currently in a situation that I need to change the IPs for my proxmox nodes. For the reason that the current IP that we used is unfortunately conflicting on the weave network that we used as the bridge interface. So:
current IP:
proxmox01 - 10.2.4.1
proxmox02 - 10.2.4.2
NEW IP should be:
proxmox01 - 192.168.0.1
proxmox02 - 192.168.0.2
Now I've read in the manual that I can no longer change the node IP once the cluster is created (https://pve.proxmox.com/wiki/Proxmox_VE_4.x_Cluster), and the only option here is to re-setup the cluster (meaning re-installing it). My concern is I don't have an available node where I can move the guest VMs in proxmox01. Hence, I'm trying my luck if there's any workaround somehow.
As I read through the forums, it seems that this approach of changing/updating the IPs on the cluster nodes are doable before (https://forum.proxmox.com/threads/is-it-possible-to-change-ip-address-of-nodes-in-a-cluster.11288/).
I've looked further and I also found a way on how to update the corosync.conf in /etc/pve (https://pve.proxmox.com/wiki/Editing_corosync.conf) to make sure the cluster bindnetaddr will be updated to the new IP (192.168.0.1).
So these are the steps that I took so far:
- stop corosync
- brought down the bridge interface
- edit /etc/hosts file with the new IP
- edit /etc/network/interfaces with the new IP
- update /etc/pve/corosync.conf bindnetaddr IP
- bring up the bridge interface
- start corosync
So I was able to start corosync and restarted pve-cluster as well. However it seems that the two nodes are both unable to connect.
e.g.
-------
root@proxmox01:~# pvecm status
Quorum information
------------------
Date: Thu Sep 1 03:17:17 2016
Quorum provider: corosync_votequorum
Nodes: 1
Node ID: 0x00000001
Ring ID: 1/2320
Quorate: No
Votequorum information
----------------------
Expected votes: 2
Highest expected: 2
Total votes: 1
Quorum: 2 Activity blocked
Flags:
Membership information
----------------------
Nodeid Votes Name
0x00000001 1 192.168.0.1 (local)
-----
Looking through the logs and I found this in Proxmox02:
Sep 01 03:16:25 proxmox02.ewr1.getcadre.com corosync[3564]: [TOTEM ] A new membership (192.168.0.2:1864) was formed. Members left: 1
Sep 01 03:16:25 proxmox02.ewr1.getcadre.com corosync[3564]: [TOTEM ] Failed to receive the leave message. failed: 1
Sep 01 03:16:25 proxmox02.ewr1.getcadre.com corosync[3564]: [QUORUM] Members[1]: 2
Sep 01 03:16:25 proxmox02.ewr1.getcadre.com corosync[3564]: [MAIN ] Completed service synchronization, ready to provide service.
Sep 01 03:16:25 proxmox02.ewr1.getcadre.com corosync[3564]: [TOTEM ] A new membership (192.168.0.1:1868) was formed. Members joined: 1
Sep 01 03:16:26 proxmox02.ewr1.getcadre.com corosync[3564]: [TOTEM ] FAILED TO RECEIVE
Sep 01 03:16:26 proxmox02.ewr1.getcadre.com corosync[3564]: [TOTEM ] A new membership (192.168.0.2:1872) was formed. Members left: 1
Sep 01 03:16:26 proxmox02.ewr1.getcadre.com corosync[3564]: [TOTEM ] Failed to receive the leave message. failed: 1
Sep 01 03:16:26 proxmox02.ewr1.getcadre.com corosync[3564]: [QUORUM] Members[1]: 2
Sep 01 03:16:26 proxmox02.ewr1.getcadre.com corosync[3564]: [MAIN ] Completed service synchronization, ready to provide service.
Sep 01 03:16:26 proxmox02.ewr1.getcadre.com corosync[3564]: [TOTEM ] A new membership (192.168.0.1:1876) was formed. Members joined: 1
Sep 01 03:16:26 proxmox02.ewr1.getcadre.com corosync[3564]: [TOTEM ] FAILED TO RECEIVE
Sep 01 03:16:26 proxmox02.ewr1.getcadre.com corosync[3564]: [TOTEM ] A new membership (192.168.0.2:1880) was formed. Members left: 1
Sep 01 03:16:26 proxmox02.ewr1.getcadre.com corosync[3564]: [TOTEM ] Failed to receive the leave message. failed: 1
Sep 01 03:16:26 proxmox02.ewr1.getcadre.com corosync[3564]: [QUORUM] Members[1]: 2
Sep 01 03:16:26 proxmox02.ewr1.getcadre.com corosync[3564]: [MAIN ] Completed service synchronization, ready to provide service.
Sep 01 03:16:27 proxmox02.ewr1.getcadre.com corosync[3564]: [TOTEM ] A new membership (192.168.0.1:1884) was formed. Members joined: 1
Sep 01 03:16:27 proxmox02.ewr1.getcadre.com corosync[3564]: [TOTEM ] FAILED TO RECEIVE
Sep 01 03:16:27 proxmox02.ewr1.getcadre.com corosync[3564]: [TOTEM ] A new membership (192.168.0.2:1888) was formed. Members left: 1
Sep 01 03:16:27 proxmox02.ewr1.getcadre.com corosync[3564]: [TOTEM ] Failed to receive the leave message. failed: 1
----------
I think I missed something here, I didn't increase the config version number in totem (corosync.conf) as stated here -- https://pve.proxmox.com/wiki/Editing_corosync.conf
BUT before I repeat again the steps, I need to consult here if this is the proper way to change node IPs or is there anything else? or I really don't have any choice but to re-setup the cluster?
Thanks in advance!
current IP:
proxmox01 - 10.2.4.1
proxmox02 - 10.2.4.2
NEW IP should be:
proxmox01 - 192.168.0.1
proxmox02 - 192.168.0.2
Now I've read in the manual that I can no longer change the node IP once the cluster is created (https://pve.proxmox.com/wiki/Proxmox_VE_4.x_Cluster), and the only option here is to re-setup the cluster (meaning re-installing it). My concern is I don't have an available node where I can move the guest VMs in proxmox01. Hence, I'm trying my luck if there's any workaround somehow.
As I read through the forums, it seems that this approach of changing/updating the IPs on the cluster nodes are doable before (https://forum.proxmox.com/threads/is-it-possible-to-change-ip-address-of-nodes-in-a-cluster.11288/).
I've looked further and I also found a way on how to update the corosync.conf in /etc/pve (https://pve.proxmox.com/wiki/Editing_corosync.conf) to make sure the cluster bindnetaddr will be updated to the new IP (192.168.0.1).
So these are the steps that I took so far:
- stop corosync
- brought down the bridge interface
- edit /etc/hosts file with the new IP
- edit /etc/network/interfaces with the new IP
- update /etc/pve/corosync.conf bindnetaddr IP
- bring up the bridge interface
- start corosync
So I was able to start corosync and restarted pve-cluster as well. However it seems that the two nodes are both unable to connect.
e.g.
-------
root@proxmox01:~# pvecm status
Quorum information
------------------
Date: Thu Sep 1 03:17:17 2016
Quorum provider: corosync_votequorum
Nodes: 1
Node ID: 0x00000001
Ring ID: 1/2320
Quorate: No
Votequorum information
----------------------
Expected votes: 2
Highest expected: 2
Total votes: 1
Quorum: 2 Activity blocked
Flags:
Membership information
----------------------
Nodeid Votes Name
0x00000001 1 192.168.0.1 (local)
-----
Looking through the logs and I found this in Proxmox02:
Sep 01 03:16:25 proxmox02.ewr1.getcadre.com corosync[3564]: [TOTEM ] A new membership (192.168.0.2:1864) was formed. Members left: 1
Sep 01 03:16:25 proxmox02.ewr1.getcadre.com corosync[3564]: [TOTEM ] Failed to receive the leave message. failed: 1
Sep 01 03:16:25 proxmox02.ewr1.getcadre.com corosync[3564]: [QUORUM] Members[1]: 2
Sep 01 03:16:25 proxmox02.ewr1.getcadre.com corosync[3564]: [MAIN ] Completed service synchronization, ready to provide service.
Sep 01 03:16:25 proxmox02.ewr1.getcadre.com corosync[3564]: [TOTEM ] A new membership (192.168.0.1:1868) was formed. Members joined: 1
Sep 01 03:16:26 proxmox02.ewr1.getcadre.com corosync[3564]: [TOTEM ] FAILED TO RECEIVE
Sep 01 03:16:26 proxmox02.ewr1.getcadre.com corosync[3564]: [TOTEM ] A new membership (192.168.0.2:1872) was formed. Members left: 1
Sep 01 03:16:26 proxmox02.ewr1.getcadre.com corosync[3564]: [TOTEM ] Failed to receive the leave message. failed: 1
Sep 01 03:16:26 proxmox02.ewr1.getcadre.com corosync[3564]: [QUORUM] Members[1]: 2
Sep 01 03:16:26 proxmox02.ewr1.getcadre.com corosync[3564]: [MAIN ] Completed service synchronization, ready to provide service.
Sep 01 03:16:26 proxmox02.ewr1.getcadre.com corosync[3564]: [TOTEM ] A new membership (192.168.0.1:1876) was formed. Members joined: 1
Sep 01 03:16:26 proxmox02.ewr1.getcadre.com corosync[3564]: [TOTEM ] FAILED TO RECEIVE
Sep 01 03:16:26 proxmox02.ewr1.getcadre.com corosync[3564]: [TOTEM ] A new membership (192.168.0.2:1880) was formed. Members left: 1
Sep 01 03:16:26 proxmox02.ewr1.getcadre.com corosync[3564]: [TOTEM ] Failed to receive the leave message. failed: 1
Sep 01 03:16:26 proxmox02.ewr1.getcadre.com corosync[3564]: [QUORUM] Members[1]: 2
Sep 01 03:16:26 proxmox02.ewr1.getcadre.com corosync[3564]: [MAIN ] Completed service synchronization, ready to provide service.
Sep 01 03:16:27 proxmox02.ewr1.getcadre.com corosync[3564]: [TOTEM ] A new membership (192.168.0.1:1884) was formed. Members joined: 1
Sep 01 03:16:27 proxmox02.ewr1.getcadre.com corosync[3564]: [TOTEM ] FAILED TO RECEIVE
Sep 01 03:16:27 proxmox02.ewr1.getcadre.com corosync[3564]: [TOTEM ] A new membership (192.168.0.2:1888) was formed. Members left: 1
Sep 01 03:16:27 proxmox02.ewr1.getcadre.com corosync[3564]: [TOTEM ] Failed to receive the leave message. failed: 1
----------
I think I missed something here, I didn't increase the config version number in totem (corosync.conf) as stated here -- https://pve.proxmox.com/wiki/Editing_corosync.conf
BUT before I repeat again the steps, I need to consult here if this is the proper way to change node IPs or is there anything else? or I really don't have any choice but to re-setup the cluster?
Thanks in advance!