Corosync 3 issue

[Purwanto]

I currently use Proxmox 5.4. I plan to upgrade to Proxmox 6. First I upgraded the Corosync service to Corosync 3. But after Corosync was successfully upgraded on all nodes, my Proxmox cluster became abnormal. If I restart Corosync on one of the nodes, the cluster becomes an error. To be normal again, I have to stop and start Corosync on all nodes manually. Things like this do not happen while still using Corosync 2. There is always a message that one of the hosts is down, even though the host is on and normal.

Jun 06 10:08:32 vmindo17 corosync[21853]:   [KNET  ] link: host: 2 link: 0 is down
Jun 06 10:08:32 vmindo17 corosync[21853]:   [KNET  ] host: host: 2 (passive) best link: 0 (pri: 1)
Jun 06 10:08:32 vmindo17 corosync[21853]:   [KNET  ] host: host: 2 has no active links
Jun 06 10:08:37 vmindo17 corosync[21853]:   [KNET  ] rx: host: 2 link: 0 is up
Jun 06 10:08:37 vmindo17 corosync[21853]:   [KNET  ] host: host: 2 (passive) best link: 0 (pri: 1)
Jun 06 10:08:39 vmindo17 corosync[21853]:   [TOTEM ] Token has not been received in 363 ms

does anyone experience the same thing here?
Please help me

 

[Purwanto]

is it okay if I change the corosync configuration (/etc/pve/corosync.conf) ?

transport: udp
secauth: off