This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Puzzling High-Availibility log

We have two UTMs configured in High Availability mode. Thinks seem to be working OK for now.

We're getting this pretty much continuously in our High-Availability log.

2016:03:10-00:00:05 perimeter1-2 ha_daemon[4301]: id="38A3" severity="debug" sys="System" sub="ha" seq="S:  394 05.320" name="Netlink: Found link beat on eth2 again!"
2016:03:10-00:00:05 perimeter1-2 ha_daemon[4301]: id="38A1" severity="warn" sys="System" sub="ha" seq="S:  395 05.320" name="All monitored interfaces with link again!"
2016:03:10-00:00:05 perimeter1-2 ha_daemon[4301]: id="38A0" severity="info" sys="System" sub="ha" seq="S:  396 05.320" name="state change UNLINKED(1) -> ACTIVE(0)"
2016:03:10-00:00:05 perimeter1-1 ha_daemon[4275]: id="38A0" severity="info" sys="System" sub="ha" seq="M:  968 05.880" name="Node 2 changed state: UNLINKED(1) -> ACTIVE(0)"
2016:03:10-00:00:06 perimeter1-2 ha_daemon[4301]: id="38A3" severity="debug" sys="System" sub="ha" seq="S:  397 06.442" name="Netlink: Lost link beat on eth2!"
2016:03:10-00:00:09 perimeter1-2 ha_daemon[4301]: id="38A1" severity="warn" sys="System" sub="ha" seq="S:  398 09.443" name="No link on interface eth2"
2016:03:10-00:00:09 perimeter1-2 ha_daemon[4301]: id="38A0" severity="info" sys="System" sub="ha" seq="S:  399 09.443" name="state change ACTIVE(0) -> UNLINKED(1)"
2016:03:10-00:00:09 perimeter1-1 ha_daemon[4275]: id="38A0" severity="info" sys="System" sub="ha" seq="M:  969 09.884" name="Node 2 changed state: ACTIVE(0) -> UNLINKED(1)"

Does this imply a bad network cable, bad switch or something else?



This thread was automatically locked due to age.
Parents Reply Children
No Data