Okay, back to zero.As I told you, we used dumb Linksys switch for cluster communication and it all worked for weekend and yesterday. And yesterday evening whole cluster is red again
Yesterday's log: http://pastebin.com/sLpnGgeS Pure corosync log: http://pastebin.com/TzyUdYaJ Bridge errors: http://pastebin.com/3ZgV7i5AThing is that I don't have a bridge with this name "bridge-id 8000.00:1e:e5:ac:db:fe.800e"
Service restart does not affect anything as usual. On 13.04.15 11:16, Sten Aus wrote:
Hi Token timeout did not make anything better nor worse. :)But now configured cluster VLAN directly to dumb Linksys switch (without VLANs), using 1G interfaces. And it's working - adding and deleting new and old nodes works like a charm.Network department have also debuged this scenario for a weeks now and no misconfiguration is found. But time is running out, so I guess our solution for now would be that all cluster communication goes to this dumb switch and all other networks come from 10G via switch mesh (NetExtreme and DELL switches).Thanks for your time and effort, if we get a solution or find a bug/mistake, I will let you know!All the best Sten _______________________________________________ pve-user mailing list pve-user@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ pve-user mailing list pve-user@pve.proxmox.com http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
