Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 5 subscribers
  • Views 6699 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

UTM HA master unlinked after upgrade to 9.5 - not able to deactivate HA on master

Björn-Bastian Behnke

Hi, 

i upgraded the master UTM from 9.413-4 to 9.500-9. After the reboot the master became unlinked from the slave running 9.413-4.

I read alot and the only solution seems to reconfigure the HA by disabling it, resetting the slave and then reconfigure it.

This is not working, i get the message box warning me that the slave is beeing factory reset when continuing but the HA is still active.

I manually reseted the slave and kicked the dead node from the cluster but i am not able to deactivate the HA. Has anyone an idea to get HA working again?



This thread was automatically locked due to age.
Parents
  • 0

    Hi, Björn-Bastian, and welcome to the UTM Community!

    I don't understand what you mean that you Up2Dated the Master.  Normally, the Master Up2Dates the Slave, reboots it, syncs to it and then fails over to it.  After that, the former Master is then the Slave and it is Up2Dated.

    In any case, your next step is to turn High Availability "Off" on the Master.  This should cause the Slave to do a Factory Reset (I think you said you did a Factory Reset already) and power down.  If you can't get HA to "Off" on the 'Configuration' tab after you physically powered the Slave node off, then you have other problems and I would get a ticket open with Sophos Support if you have a paid license.

    You should have to do no configuration of the Slave.  Just re-enable HA on the Master and power the old Slave node up again.  The Master will see it and sync the Configuration to it.

    If that didn't work, you will need to re-image the Slave from ISO.  Any luck with any of that?

    Cheers - Bob

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

    Hi, Björn-Bastian, and welcome to the UTM Community!

    I don't understand what you mean that you Up2Dated the Master.  Normally, the Master Up2Dates the Slave, reboots it, syncs to it and then fails over to it.  After that, the former Master is then the Slave and it is Up2Dated.

    In any case, your next step is to turn High Availability "Off" on the Master.  This should cause the Slave to do a Factory Reset (I think you said you did a Factory Reset already) and power down.  If you can't get HA to "Off" on the 'Configuration' tab after you physically powered the Slave node off, then you have other problems and I would get a ticket open with Sophos Support if you have a paid license.

    You should have to do no configuration of the Slave.  Just re-enable HA on the Master and power the old Slave node up again.  The Master will see it and sync the Configuration to it.

    If that didn't work, you will need to re-image the Slave from ISO.  Any luck with any of that?

    Cheers - Bob

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