Hi .
Proxmox is a terrific technology i need to handle.
First of all thank you all the staff and community for this great product ! It's awesome.
I need your help guys because i'm stuk at this point. I'm pretty sure you can help me and there's some obvious think i do not see.
I got a problem when joining a node into a cluster.
Here is the scheme :
oOP1 and oOP2 were joined years ago (long before i was hired in the company i guess proxmox < 5 )
Now we need to migrate oOP1 [10.17.254.3] and oOP2 [10.17.254.2] to OP1 [10.17.254.5] and OP2 [10.17.254.4] (new servers)
We planned to do a
Once Debian 10.5 installed and all Proxmox stack we did this on OP1 [10.17.254.5]
Here are the nodes
The last node we wanted to join with this command on OP2 :
For now the last node OP2 doesn't want to join the cluster and display this kind of errors :
When i look at
I can see nodes but with public IPs :
{
"nodename": "OP2",
"version": 514,
"cluster": { "name": "CLUSTER0", "version": 15, "nodes": 4, "quorate": 1 },
"nodelist": {
"oOP1": { "id": 2, "online": 1, "ip": "PUBLIC"},
"OP1": { "id": 3, "online": 1, "ip": "PUBLIC"},
"OP2": { "id": 4, "online": 1, "ip": "PUBLIC"},
"oOP2": { "id": 1, "online": 1, "ip": "PUBLIC"}
}
}
the
Can i change the
As manual says :
I can see when i do :
I know there is a trick to do it work properly. Unfortunately i'm pretty new to corosync/pve cluster management and work with my college was no synchronized we did this a little messy/quickly.
I can provide logs and more conf sure if it's needed . I was through such logs and conf thant i'ma little puzzled.
Thanks in advance.
Proxmox is a terrific technology i need to handle.
First of all thank you all the staff and community for this great product ! It's awesome.
I need your help guys because i'm stuk at this point. I'm pretty sure you can help me and there's some obvious think i do not see.
I got a problem when joining a node into a cluster.
Here is the scheme :
oOP1 and oOP2 were joined years ago (long before i was hired in the company i guess proxmox < 5 )
Now we need to migrate oOP1 [10.17.254.3] and oOP2 [10.17.254.2] to OP1 [10.17.254.5] and OP2 [10.17.254.4] (new servers)
We planned to do a
pvecm add to join the cluster to do migration quickly and easily... but...Once Debian 10.5 installed and all Proxmox stack we did this on OP1 [10.17.254.5]
pvecm add 10.17.254.3 -link0 10.17.254.5Here are the nodes
Code:
Nodeid Votes Name
0x00000001 1 10.17.254.2
0x00000002 1 10.17.254.3 (local)
0x00000003 1 10.17.254.5
0x00000004 1 10.17.254.4The last node we wanted to join with this command on OP2 :
pvecm add 10.17.254.2 -link0 10.17.254.5For now the last node OP2 doesn't want to join the cluster and display this kind of errors :
Code:
[QUORUM] This node is within the non-primary component and will NOT provide any services.
[KNET ] host: host: 1 has no active links
[TOTEM ] Token has not been received in 84 ms
[MAIN ] interface section bindnetaddr is used together with no delist. Nodelist one is going to be used.
[MAIN ] Please migrate config file to nodelist.
[KNET ] udp: Received ICMP error from 10.17.254.4: No route to host 10.17.254.5When i look at
/etc/pve/.membersI can see nodes but with public IPs :
{
"nodename": "OP2",
"version": 514,
"cluster": { "name": "CLUSTER0", "version": 15, "nodes": 4, "quorate": 1 },
"nodelist": {
"oOP1": { "id": 2, "online": 1, "ip": "PUBLIC"},
"OP1": { "id": 3, "online": 1, "ip": "PUBLIC"},
"OP2": { "id": 4, "online": 1, "ip": "PUBLIC"},
"oOP2": { "id": 1, "online": 1, "ip": "PUBLIC"}
}
}
the
/etc/pve/corosync.conf :
Code:
logging {
debug: on
to_syslog: yes
}
nodelist {
node {
name: OP1
nodeid: 3
quorum_votes: 1
ring0_addr: 10.17.254.5
}
node {
name: OP2
nodeid: 4
quorum_votes: 1
ring0_addr: 10.17.254.4
}
node {
name: oOP1
nodeid: 2
quorum_votes: 1
ring0_addr: 10.17.254.3
}
node {
name: oOP2
nodeid: 1
quorum_votes: 1
ring0_addr: 10.17.254.2
}
}
quorum {
provider: corosync_votequorum
}
totem {
cluster_name: CLUSTER0
config_version: 15
interface {
bindnetaddr: 10.17.254.2
ringnumber: 0
}
ip_version: ipv4
secauth: on
version: 2Can i change the
bindnetaddr line without breaking anything ? We have prod servers on oOP1 and oOP2.As manual says :
corosync.conf
Code:
bindnetaddr (udp only)
This specifies the network address the corosync executive should bind to when using udp.
bindnetaddr (udp only) should be an IP address configured on the system, or a network address.
For example, if the local interface is 192.168.5.92 with netmask 255.255.255.0, you should set bindnetaddr to 192.168.5.92 or 192.168.5.0. If the local interface is 192.168.5.92 with
netmask 255.255.255.192, set bindnetaddr to 192.168.5.92 or 192.168.5.64, and so forth.
This may also be an IPV6 address, in which case IPV6 networking will be used. In this case, the exact address must be specified and there is no automatic selection of the network in‐
terface within a specific subnet as with IPv4.
If IPv6 networking is used, the nodeid field in nodelist must be specified.I can see when i do :
watch -n1 pvecm status :
Code:
Votequorum information
----------------------
Expected votes: 4
Highest expected: 4
Total votes: 1
Quorum: 3 Activity blocked
Flags:I know there is a trick to do it work properly. Unfortunately i'm pretty new to corosync/pve cluster management and work with my college was no synchronized we did this a little messy/quickly.
I can provide logs and more conf sure if it's needed . I was through such logs and conf thant i'm
Thanks in advance.
