Search:

I think you missed some key details from post 1.

eth5 is sync connected via cross over and fw2 locked up. As in nada on console which is why its strange that fw1 was in down standby state. I kind...

I don't think your problem is eth5 going down. I think the problem is the unknown state one of the firewall members entered because of what seems like might be a hardware issue.

I see 3 things you...

wow, never seen down / standby on clusterxl. Did you grab /var/log/messages* from both members after reboot? What was the last thing shown before the failure? $FWDIR/log/fwd.elg would be worth...