Sophos HA Configuration - After reboot one node says "Sophos Protection" on Display...no second in HA visible

Hello,

i'm fighting with my two SG430 nodes. I've shut down the slave and afterwards the master per web console. Then i booted the slave first (Does it matter?) and then the master second.

Now the old slave is master and working.  Apparently the second node "hangs" as i only see "Sophos protection" on the display. Also when pushing the four buttons does not change the display. The only led powered on is "Int". The other stay "grey" but where shortly blinking while the device was powered on.

In my Log i see the following information:

2020:10:14-14:05:28 node2 ha_mode[29271]: calling check
2020:10:14-14:05:28 node2 ha_mode[29271]: check: waiting for last ha_mode done
2020:10:14-14:05:28 node2 ha_mode[29271]: check_ha() role=MASTER, status=ACTIVE
2020:10:14-14:05:28 node2 ha_mode[29271]: check done (started at 14:00:14)
2020:10:14-14:05:33 node2 repctl[5291]: [i] recheck(1057): got ALRM: replication recheck triggered Setup_replication_done = 1
2020:10:14-14:05:33 node2 repctl[5291]: [i] recheck(1057): got ALRM: replication recheck triggered Setup_replication_done = 1
2020:10:14-14:10:48 node2 repctl[5291]: [i] recheck(1057): got ALRM: replication recheck triggered Setup_replication_done = 1
2020:10:14-14:10:48 node2 repctl[5291]: [i] recheck(1057): got ALRM: replication recheck triggered Setup_replication_done = 1
2020:10:14-14:14:00 node2 ha_daemon[5240]: id="38A0" severity="info" sys="System" sub="ha" seq="M: 141 59.496" name="Reading cluster configuration"
2020:10:14-14:14:02 node2 ha_daemon[5240]: id="38A0" severity="info" sys="System" sub="ha" seq="M: 142 14.695" name="Monitoring interfaces for link beat: eth1 eth0"
2020:10:14-14:20:16 node2 repctl[5291]: [i] recheck(1057): got ALRM: replication recheck triggered Setup_replication_done = 1

Does anyone know this problem?

Parents
  • Hallo,

    I wouldn't have first brought up the node that was shutdown first.  What changes happened on the prior Master after the prior Slave was shutdown?

    If doing Alex' suggestion doesn't give you the solution, does rebooting the Slave?  If not, you'll want to get a ticket open with Sophos Support, but they'll likely tell you to disable HA and then re-enable it, thus doing a factory reset of the unit.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Reply
  • Hallo,

    I wouldn't have first brought up the node that was shutdown first.  What changes happened on the prior Master after the prior Slave was shutdown?

    If doing Alex' suggestion doesn't give you the solution, does rebooting the Slave?  If not, you'll want to get a ticket open with Sophos Support, but they'll likely tell you to disable HA and then re-enable it, thus doing a factory reset of the unit.

    Cheers - Bob

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
Children
No Data