Cluster gives log errors "corosync[31302]: [TOTEM ] Incoming packet has different crypto type

H

hefferbub

Member
Sep 11, 2010
28
0
21
I have two servers running PVE 4.1 and I just made them into a cluster. Everything seems to work fine, but I see in syslog on both systems corosync-related error messages every second or so:

Jan 6 15:14:58 vs2 corosync[31302]: [TOTEM ] Incoming packet has different crypto type. Rejecting
Jan 6 15:14:58 vs2 corosync[31302]: [TOTEM ] Received message has invalid digest... ignoring.
Jan 6 15:14:58 vs2 corosync[31302]: [TOTEM ] Invalid packet data
​
Any idea what is going on? How can I fix it?

FYI, I do have a third server that is not part of the cluster that is running an older version (PVE 3.0-20), in case that is likely to be an issue.

Thanks!
 
Actually, I stand corrected. The log errors are coming from the machine running PVE 3.0. Please ignore...
 
hefferbub said:
Actually, I stand corrected. The log errors are coming from the machine running PVE 3.0. Please ignore...
Click to expand...

you should enable igmp snooping on your network switch to avoid mutlicast packets from other cluster coming to theses nodes.

(also be carefull to not use same clustername, because the multicast address is generated from clustername)
 
You must log in or register to reply here.
Top Bottom