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

Firmware upgrade issues

Is there a preferred upgrade path / procedure for firmware? I seem to be having issues every time I upgrade, especially from anything in the 17.0/17.1 series to anything in the 17.5 series. The issues I have seen are:

  • HA auxiliary upgrades and reboots, but HA primary fails to reboot and gets stuck on the previous version
  • Upgrade appears to complete but HA is disabled after upgrade (a real pain if the unlicensed node is the one with all the config)
  • Upgrade completes but both HA devices decide they are primary
  • Upgrade completes but doesn't seem to work quite right until both HA devices are rebooted again

Under UTM9 I could reliably do a firmware upgrade pretty much whenever I wanted and there would only be a brief half second outage while the HA changeover happened. XG seems to be a lot more fragile.

I'm almost inclined to break HA, do the upgrade, then re-create HA, on the assumption that that might be more reliable. It's a heap more work though, and not without risk.

I haven't yet tried doing a pre-upgrade reboot of both nodes (some of the uptimes can get pretty big). Might that help?

Thanks

James



This thread was automatically locked due to age.
Parents
  • Hi you may want to wait until the next Release MR4 which is hopefully due this month to see if that fixes your problem. We have been dealing with issues involving HA failover since applying the a firmware update last September. We had problems ranging from the devices hanging on boot as well as some of the problems you mentioned including  WAF rules failing. This has been identified as GARP not being sent on failover.

Reply
  • Hi you may want to wait until the next Release MR4 which is hopefully due this month to see if that fixes your problem. We have been dealing with issues involving HA failover since applying the a firmware update last September. We had problems ranging from the devices hanging on boot as well as some of the problems you mentioned including  WAF rules failing. This has been identified as GARP not being sent on failover.

Children
No Data