It will even show you a nice report of progress and a summary when done. This will download the software package of the selected version and perform an in-place CPUSE upgrade of the Management machine. The easiest way to upgrade the Management is to go into the Gaia portal, into the CPUSE (software) page, then choose the desired version and click "upgrade". Your environment sounds pretty simple, so I'm not sure it's worth the effort to do a "migrate export", test it, install from ISO and export+import again. Multi-Version Cluster Upgrade involves explicitly telling the upgraded cluster member to sync with the older version, which allows ongoing connections to survive the failover with some limitations. Zero Downtime Upgrade involves upgrading one member, flipping over to it (which will cause loss of ongoing connections R80.30 and R80.40 firewalls can't sync normally), testing, then upgrading the other. Minimal Effort Upgrade involves an outage window where you shut both members down, upgrade them, then bring them both online at the new version. The installation and upgrade guide has a few. You're limited to application features of the lowest version (so in my case, R80.20), but you can use OS-level features of the new version (such as the new kernel and userspace, new filesystem, etc.)Īs for question 2, that's roughly how most cluster upgrades go. For example, I have an R80.20 management server managing some R80.40 firewalls. With a jumbo HFA (patch bundle), management versions can also manage some newer firewall versions. I think R80.40 management can manage back to R77, which is something like eight years of backwards compatibility. All management versions can manage a few earlier firewall versions. For your first question, yes, R80.40 management can manage R80.30 firewalls, and the firewalls won't care.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |