Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 27 subscribers
  • Views 4584 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

Updating XG310 HA pair from 17.3 to 17.5 caused factory reset

ken9000

Updated an HA pair from 17.3 to 17.5. The primary updated fine but the passive box stopped responding to pings. Turns out it completely factory reset and became a DHCP server on 172.x.x.x Not a good morning. The XG platform continues to disappoint.



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

    Did this with XG210-HA last week. Everything worked fine on both systems.

    Regards, Jelle

    Sophos XG210-HA (SFOS 18.0.4) on SG210 appliances with Sandstorm and 1x AP55
    Sophos Central with Intercept X Advanced, Device Encryption, Phish Threat, Mobile Control Advanced

    If a post solves your question use the 'This helped me' link.

Reply
  • 0

    Did this with XG210-HA last week. Everything worked fine on both systems.

    Regards, Jelle

    Sophos XG210-HA (SFOS 18.0.4) on SG210 appliances with Sandstorm and 1x AP55
    Sophos Central with Intercept X Advanced, Device Encryption, Phish Threat, Mobile Control Advanced

    If a post solves your question use the 'This helped me' link.

Children
No Data
Cookie Information Banner