I am attempting to join two freshly built proxmox 2.1 hosts into a cluster, following the guide here. Establishing the first node in the cluster goes fine. I seem to be running into problems when attempting to add the second node. The pvecm add command results in:
I checked the status of the cluster on both nodes
vm-proxmox1
vm-proxmox2
Hmm. Quorum activity blocked.
Other forum posts suggest this to be an issue with multicast. Both of these nodes are connected via a Cisco Nexus 5k cluster in which I successfully host other multicast based applications, so my problem most likely isn't there. I began reading the Multicast notes wiki entry, where it is suggested to test multicast with ssmping. After installing the package on both hosts, I launched ssmpingd on the first node. On the second node, I executed the client side multicast ping:
No such device? So, I then tried to force the bridge device:
Wow, it works! Knowing that multicast communications work between these two nodes, could my problems with corosync have anything to do with it also not selecting the correct network interface? Is there anyway that I can force this? I would appreciate any pointers here.
Thanks.
Code:
Starting cluster:
Checking if cluster has been disabled at boot... [ OK ]
Checking Network Manager... [ OK ]
Global setup... [ OK ]
Loading kernel modules... [ OK ]
Mounting configfs... [ OK ]
Starting cman... [ OK ]
Waiting for quorum... Timed-out waiting for cluster
[FAILED]
waiting for quorum...
I checked the status of the cluster on both nodes
vm-proxmox1
Code:
root@vm-proxmox1:~# pvecm status
Version: 6.2.0
Config Version: 5
Cluster Name: proxmox-cl-1
Cluster Id: 1891
Cluster Member: Yes
Cluster Generation: 16
Membership state: Cluster-Member
Nodes: 1
Expected votes: 2
Total votes: 1
Node votes: 1
Quorum: 2 Activity blocked
Active subsystems: 1
Flags:
Ports Bound: 0
Node name: vm-proxmox1
Node ID: 1
Multicast addresses: 239.192.7.106
Node addresses: 10.3.106.1
vm-proxmox2
Code:
root@vm-proxmox2:~# pvecm status
Version: 6.2.0
Config Version: 5
Cluster Name: proxmox-cl-1
Cluster Id: 1891
Cluster Member: Yes
Cluster Generation: 4
Membership state: Cluster-Member
Nodes: 1
Expected votes: 2
Total votes: 1
Node votes: 1
Quorum: 2 Activity blocked
Active subsystems: 1
Flags:
Ports Bound: 0
Node name: vm-proxmox2
Node ID: 2
Multicast addresses: 239.192.7.106
Node addresses: 10.3.106.2
Hmm. Quorum activity blocked.
Other forum posts suggest this to be an issue with multicast. Both of these nodes are connected via a Cisco Nexus 5k cluster in which I successfully host other multicast based applications, so my problem most likely isn't there. I began reading the Multicast notes wiki entry, where it is suggested to test multicast with ssmping. After installing the package on both hosts, I launched ssmpingd on the first node. On the second node, I executed the client side multicast ping:
Code:
root@vm-proxmox2:~# asmping 239.192.7.106 10.3.106.1
Failed to join multicast group: No such device
errno=19
No such device? So, I then tried to force the bridge device:
Code:
root@vm-proxmox2:~# asmping -I vmbr2003 239.192.7.106 10.3.106.1
asmping joined (S,G) = (*,239.192.7.234)
pinging 10.3.106.1 from 10.3.106.2
unicast from 10.3.106.1, seq=1 dist=0 time=0.910 ms
unicast from 10.3.106.1, seq=2 dist=0 time=0.201 ms
unicast from 10.3.106.1, seq=3 dist=0 time=0.220 ms
unicast from 10.3.106.1, seq=4 dist=0 time=0.182 ms
^C
--- 10.3.106.1 statistics ---
4 packets transmitted, time 3756 ms
unicast:
4 packets received, 0% packet loss
rtt min/avg/max/std-dev = 0.182/0.378/0.910/0.307 ms
multicast:
0 packets received, 100% packet loss
Wow, it works! Knowing that multicast communications work between these two nodes, could my problems with corosync have anything to do with it also not selecting the correct network interface? Is there anyway that I can force this? I would appreciate any pointers here.
Thanks.