Cluster not green

L

Leo David

Well-Known Member
Apr 25, 2017
115
6
58
46
Hello everyone,
I am struggling with a PVE5 cluster that won't came up. I suspect to be a multicast issue, or missconfiguration. The servers are configured with bonding/lacp , and i was wondering that this can cause the problem - multicast not being passed. Below, the interface configuration of on of the servers:

auto lo
iface lo inet loopback

iface eno1 inet manual

iface eno2 inet manual

auto bond0
iface bond0 inet manual
slaves eno1 eno2
bond_miimon 100
bond_mode 802.3ad
bond miimon 100

auto vmbr0
iface vmbr0 inet static
address 10.32.129.68
netmask 255.255.255.240
gateway 10.32.129.65
bridge_ports bond0
bridge_stp off
bridge_fd 0
bridge_vlan_aware yes

Is there something wrong with this configuration ? Quorum is not met, each node is only "seeing" itself, although the quorum needs to go up to 4 nodes now.

Thank you very much !
 
omping -c 600 -i 1 results:

proxmox4 : unicast, xmt/rcv/%loss = 600/600/0%, min/avg/max/std-dev = 0.100/0.145/0.295/0.031
proxmox4 : multicast, xmt/rcv/%loss = 600/260/56% (seq>=2 56%), min/avg/max/std-dev = 0.100/0.160/0.308/0.038

proxmox1 : unicast, xmt/rcv/%loss = 600/600/0%, min/avg/max/std-dev = 0.100/0.146/0.233/0.024
proxmox1 : multicast, xmt/rcv/%loss = 600/258/57%, min/avg/max/std-dev = 0.101/0.151/0.253/0.030

I rest my case... :(

The thing is that the switch is not under my administration, and i have been told that multicast has been enabled.
I just want to exclude the posibilitty that the lacp mode for bonding can cause this issue, and therefore still blame on this Juniper switch configuration.
Any thoughts on this ?

Thank you very much !
 
Thank you Wolfgang,

I will try the unicast setup, if multicast will still be an unusuable option...
 
You must log in or register to reply here.
Top Bottom