Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 4 replies
  • Answers 2 answers
  • Subscribers 6 subscribers
  • Views 10937 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

Update slave node

Ebin A

Slave node was reset and now added back to HA, however slave node is not syncing properly to master. 

Slave node in HA is showing status "up2date".

Master node firmware version is 9.403.  Slave node firmware version is 9.358

Please give me suggestions on how to upgrade Slave to same firmware as Master node.



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

    Hi,

     

    am i right, that you're trying to build an active/passive cluster with 2 utm's that have a different version?

    I think this isn't working. Have you tried to update the slave utm first to 9.403 and then build a cluster.

    Disable the cluster, reset the slave node, update this, and rebuild the cluster (automatic configuration -> ha active/passive (machine with the highest uptime will be master!))

    You can disable the automatic update search and upload the up2date packed manually http://ftp.astaro.de/UTM/v9/up2date/

     

    edit: i see that there is no update package from 9.358 to 9.403, maybe that's the problem why your automatic update isn't working.
    My suggestion, first update your master utm from 9.403 to 9.404 and then update your slave from 9.358 to 9.404. 
    After that, rebuild your cluster

     

    Regards

  • 0 in reply to logan517

    Hi, 

    I had  disabled the HA, reset the slave node, and tried to update the slave first. However slave is not getting firmware updated.  

    I had uploaded the firmware using the sophos utm 9 and when applying the firmware it shows that is it successful and it goes for a reboot, when it comes up it is in same firmware version 9.358. Please suggest on how to update it.

     

  • 0 in reply to Ebin A

    Hey Abin.

    Any reason for you to stick with such an old version? We are on 9.414-2 (don't use this version if you use AD SSO) or 9.502-4 by now.

    Logan already pointed out that you won't be able to match your UTM versions to form a cluster as there is no longer an upgrade path from 9.358-3 to 9.403. Your only option is to upgrade your 9.358-3 to 9.404-5 with the file from here and upgrade your master from 9.403 to 9.404-5 before creating the cluster. 

    Now, I have no idea why your slave would not upgrade to 9.404-5 as long as you are using the file I mentioned above. I would reimage de device and start from scratch just to be sure. Are you using an appliance os is this a software install?

    Regards,

    Giovani

  • 0 in reply to giomoda

    Hi Giovani,

    Thank you. I was able to upgrade from 9.353 to 9.404-5

Reply Children
No Data
Unfiltered HTML