Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 6 subscribers
  • Views 11465 views
  • Users 0 members are here
Options
Suggested
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

Configure HA. Not monitoring eth3?

JSinclair

I recently had to unconfigure HA between two SG 430s because of an issue with postgresql. I am now trying to reconfigure HA but I'm not getting link lights when I connect the cables. The cables are connected to eth3, but the live log says it's "Monitoring interfaces for link beat: eth1". I tried disabling link monitoring on eth1, but got "Found no interfaces in /etc/ha/lbeat_interfaces for link beat monitoring". I had rebooted the Slave UTM and briefly saw link lights with the log "Netlink: Found link beat on eth3 again!", but the immediately went off and "Netlink: Lost link beat on eth3!" was logged. 



This thread was automatically locked due to age.
  • 0
    I would disconnect the Slave, do a Factory Reset, power it down and reconnect all the cables. In the master, disable and then enable HA. Power up the Slave. Any luck?

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0
    Sometimes a re-image is better than a factory reset. If the appliance was powered on more then 30 day ago, the factory trial license is expired and ha is no longer working.
    Remember to check, if ha is set on "automatic" with an ha interface defined. The bigger appliances does not have a dedicated ha-port (usually eth3) defined, so the factory default is ha = off. On newer versions there is an lcd menu entry for ha interface, i think.

    good luck!

     

    Sophos Certified Architect (UTM + XG)

  • 0
    I talked with Support and ended up manually setting the sync ports to eth4, as eth3 was not working. Factory reset didn't help in this case.
  • 0 in reply to JSinclair
    Yep, that was going to be the next suggestion.

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0
    The flexi port modules are not activated by default like the "onboard" ports.
    Factory reset does not activate them.

    I found 2 ways to solve:
    1. Import a backup of the HA master before booting
    2. log in to the default 102.168.0.1, do a minimal setup, activate eth3 and reboot.
Unfiltered HTML