Correcting link0 ips

jackiedon

Member
Dec 16, 2019
6
0
6
34
We have a problem with link0 addresses across the cluster - some nodes joined the cluster with correct IPs from the LAN, but some have used the Public IP as link0.

And every time we add a new node to the cluster, the cluster fails, we have to correct IPs manually in the Corosync.conf file.

But the link0 address stays the same in Web UI, we have no way of correcting that.

Can anyone advise whether this can be done on a running cluster?
 

Attachments

  • west.png
    west.png
    65.2 KB · Views: 5
Please post the output of cat /etc/pve/corosync.conf as well as pvecm status and pvecm nodes.
 
logging {
debug: off
to_syslog: yes
}

nodelist {
node {
name: iofXXXXXX
nodeid: 2
quorum_votes: 1
ring0_addr: 10.5.5.102
}
node {
name: iofXXXXXX
nodeid: 1
quorum_votes: 1
ring0_addr: 10.5.5.101
}
node {
name: iofXXXXXX
nodeid: 5
quorum_votes: 1
ring0_addr: 107.xxx.xx.xxx
}
node {
name: iofXXXXXX
nodeid: 6
quorum_votes: 1
ring0_addr: 10.5.5.106
}
node {
name: iofXXXXXX
nodeid: 7
quorum_votes: 1
ring0_addr: 107.xxx.xx.xxx
}
node {
name: iofXXXXXX
nodeid: 4
quorum_votes: 1
ring0_addr: 104.xxx.xx.xxx
}
node {
name: iofXXXXXX
nodeid: 3
quorum_votes: 1
ring0_addr: 107.xxx.xx.xxx
}
}

quorum {
provider: corosync_votequorum
}

totem {
cluster_name: westusazc1
config_version: 17
interface {
linknumber: 0
}
ip_version: ipv4-6
link_mode: passive
secauth: on
version: 2
}
 
pvecm status
Cluster information
-------------------
Name: westusazc1
Config Version: 17
Transport: knet
Secure auth: on

Quorum information
------------------
Date: Wed Sep 9 11:56:14 2020
Quorum provider: corosync_votequorum
Nodes: 6
Node ID: 0x00000002
Ring ID: 1.369e
Quorate: Yes

Votequorum information
----------------------
Expected votes: 7
Highest expected: 7
Total votes: 6
Quorum: 4
Flags: Quorate

Membership information
----------------------
Nodeid Votes Name
0x00000001 1 10.5.5.101
0x00000002 1 10.5.5.102 (local)
0x00000003 1 10.5.5.103
0x00000004 1 10.5.5.104
0x00000005 1 10.5.5.105
0x00000006 1 10.5.5.106
 
pvecm nodes

Membership information
----------------------
Nodeid Votes Name
1 1 ioXXX0
2 1 ioXXX13 (local)
3 1 ioXXX9b
4 1 ioXXX2b
5 1 ioXXX47
6 1 ioXXX50
 
we have tried changing values in Corosync.conf, but they get Re-written every time. I think there is some internal Proxmox database that keeps the values in it.
 
You have to bump the config_version at the same time you modify anything else in the file. So change all the IPs that need to be changed and bump the config_version and then save the file.
Also make sure you're editing /etc/pve/corosync.conf and not /etc/corosync/corosync.conf as the /etc/corosync file is overwritten with the /etc/pve one once the cluster is running.
 
  • Like
Reactions: jackiedon

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!