hello,
upgrading an a/p cluster should work like you stated: as you can only interact with the active cluster member, upgrading is done internally by the FGT master. First, when the config is synched, the master transfers the firmware image onto the slave, the slave reboots and assumes the master role. Then, the prior master is upgraded and rebooted. Depending on your settings, the prior master either is promoted to master again or the cluster is left as is.
At no point an active internet connection is needed.
If you' ve tried to upgrade, and the upgrade didn' t succeed, then please post the error message(s) you' ve got.
Best practice says:
1.
reboot the cluster BEFORE upgrading (to eliminate possible memory leaks).
2. if you want the master to stay master, set it' s HA priority higher than the slave' s. With both priorities equal you avoid one reboot thus maximizing uptime.
3. In ancient times, upgrading a cluster was best done by splitting it up, doing it member by member and re-forming the cluster afterwards. That is unnecessary today, from FortiOS 4.2 and younger on.
Ede Kernel panic: Aiee, killing interrupt handler!