Hi all,
Bit of a weird issue. I have a 3 node cluster, not sure how this happened but two of them are running 8.2.7 and one is running 8.3.2. They all have Mellanox Connect-X5 100G cards in them for corosync. My two nodes running 8.2.7 work just fine. The node running 8.3.2 can't ping the corosync0 IPs of the other two nodes if corosync0 is set to port 0 as the bridge port. On port 1, this works just fine. It *does* work on port 0 when the port is in promiscuous mode or if I comment out the "bridge-vlan-aware yes" line in /etc/network/interfaces for the corosync0 interface.
I can try reflashing the card but I'm very confused as to what could be happening because the configurations are identical except for the pve-manager and kernel versions. The cards are identical also, and they all use the same DACs. Any advice would be greatly appreciated, or if there's a way to reinstall an 8.2 ISO and upgrade to 8.2.7 on my bad node I can try that as well since all my containers are on the two good ones now.
Thank you!
Bit of a weird issue. I have a 3 node cluster, not sure how this happened but two of them are running 8.2.7 and one is running 8.3.2. They all have Mellanox Connect-X5 100G cards in them for corosync. My two nodes running 8.2.7 work just fine. The node running 8.3.2 can't ping the corosync0 IPs of the other two nodes if corosync0 is set to port 0 as the bridge port. On port 1, this works just fine. It *does* work on port 0 when the port is in promiscuous mode or if I comment out the "bridge-vlan-aware yes" line in /etc/network/interfaces for the corosync0 interface.
I can try reflashing the card but I'm very confused as to what could be happening because the configurations are identical except for the pve-manager and kernel versions. The cards are identical also, and they all use the same DACs. Any advice would be greatly appreciated, or if there's a way to reinstall an 8.2 ISO and upgrade to 8.2.7 on my bad node I can try that as well since all my containers are on the two good ones now.
Thank you!