I have not found where this is documented, but there are rules around minimum host versions for guests. It has rules to check that host version against the target guest version. , then…well…it gets messy.ĭuring the upgrade process, it checks the current host version. But if you do an upgrade using request system software add. If you do a format install from USB, it will make both versions the same. Upgrading the Host OS is not required for every software upgrade, as noted above.The Junos OS and Host OS versions do not need to be the same.Note: On QFX5100 and EX4600 switches, the Host OS is not upgraded automatically, so you must use the force-host option if you want the Junos OS and Host OS versions to be the same. The key here is that the guest version does not have to match the host version. But when you go to upgrade…it fails on the systems running the older host OS. The guest version is all that matters for forming a virtual chassis, so they don’t care about the host version mismatch. Juniper will not be under any obligation to keep any such Releases available for download after Release EOS.Huh. After Release EOS Juniper will not be under obligation to perform support services of any kind for any Releases under the applicable Version. Release EOS for Releases under a particular Version generally ranges between 6 and 12 months after the EOSE date for that Version. No further Releases will be developed or distributed for that Version. After Release EOSE Juniper will not be under obligation to perform any further software fixes, code changes. EOSE for Releases under a particular Version generally ranges between 9 and 36 months after first general availability of the initial Release under that Version. Juniper may modify those rules from time to time by posting on its public website.Įnd-of-Life milestones for Releases under one Version do not affect support commitments relating to Releases for other Versions. Instead, a product-specific Process Support Notification posted on Juniper’s public website at or before general availability of the first Release under the applicable software Version will specify rules for Release EOSE and Release EOS. The following guidelines govern EOSE and EOS for the software Releases under any particular Version (“Release EOSE” and “Release EOS”, respectively).Įnd of life milestone deadlines for Releases are not triggered by an EOLN. Releases within a particular Version generally have For example, Junos 12.2R1 through Junos 12.2R8 are all Releases under the same Version 12.2, whereas Junos 12.2R1 and Junos 12.3R1 are Releases under different Versions. Software Releases under a particular Version.Ī “Version” is a series of Releases of a particular software product with a common “x.y” denomination in the first two places of the Release identifier.Ī “Release,” on the other hand, is a particular image issued under a particular Version.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |