Log in to ask questions, share your expertise, or stay connected to content you value. Don’t have a login? Learn how to become a member.
I'm planning to upgrade from junos 20.2R3-S2 to 22.4R2-S1.6,
but is there a page that describes the upgrade path to 22.4R2-S1.6?
The details of how the upgrade version process work are found in the release notes for your final target version. In your case 22.4.
Check the section "Migration, upgrade, downgrade" under your platform in the notes. This will outline the maximum version jump requirements.
In general you can go directly from 2-3 major versions (the first number of the Junos). But the details are noted per platform in the release notes.
If you do have to do intermediate upgrades you need to repeat the process the same way. For example, if you were currently on Junos 18.2 and the oldest version supported for the new upgrade was 20.4. You would then go to the release notes for 20.4 and confirm the jump from 18.2 will work to there.
Wow, do I get the chance to correct the great Steve?! I'll probably make a complete fool out of myself, but in this particular case and with recent releases, the path is this:
20.4 (technically you could go to 21.1 or 21.2 (EEOL) but that won't decrease the amount of steps)
21.4 (this is an EEOL release, so you can go to 22.4 in one step)
Why on earth Juniper has not come up with a tool that gives you the upgrade path is beyond me. It should be easy enough, at least for mainstream hardware.
So, the theory behind this is (copy paste from the docs Steve posted):
We have two types of releases, standard EOL and EEOL:
Standard End of Life (EOL) releases have engineering support for twenty four months after the first general availability date and customer support for an additional six more months.
Extended End of Life (EEOL) releases have engineering support for thirty six months after the first general availability date and customer support for an additional six more months. [FB comment: what happens when a release has more than 36 months???]
To know this, you have to look it up and compare the lists and check the dates. NOT EVEn in the lists are the releases marked as EEOL. You NEED to look at the dates... Wow!!!
You can alway up-or downgrade three releases, like 20.1 to 20.4 or 20.1 to 19.2 (the version numbers are year.quarter, so 19.1 to 19.4 are quarters 1-4 year 2019).
IF you are on an EEOL release, you can also choose to up- or downgrade two EEOL steps. In the past that could be from 10.4 to 12.1X44 or 16.1 to 17.2, but in all releases from 19.4, all xx.2 and xx.4 releases are EEOL so there you can only skip an extra step and go from 19.4 to 20.4 to 21.4 to 22.4.
Summary, and my advice: If you are on 19.1 or higher, upgrade to the nearest xx.4 release to get to the EEOL releases. From there, go to 20.4 to 21.4 to 22.4.
If you are on older code, check the document more closely and you'll figure it out...or ask here :)
Related Question regarding upgrade from release 20 to 21 to 22 for Junos Fusion Provider Edge on dual REs. To minimize outages caused by satellite device reboots I am planning the following procedure:
Beginning state: RE0 and RE1 are both at 20.4R3-S7.2Logged in to RE0 [[Master] on console port.NSR & GRES deactivated.
Upgrade RE1 [Backup] 20.4R3-S7.2 to 21.4R3-S4Logged in to RE1 [Backup]UpgradeRE0 is Master
Upgrade the Satellite Device 20.4R3-S7.2 to 21.4R3-S4Logged in to RE0 [[Master]UpgradeReboot causes outage to connected satellite device circuitsRE0 is MasterChange mastership to RE1 and causes outage for all circuits.
Upgrade RE0 [Backup] 20.4R3-S7.2 to 21.4R3-S4 Logged in to RE0 [Backuo]UpgradeRE0 Reboots and causes RE0 to become master. Outage to connected satellite device circuits caused by mastership change.
Upgrade RE1 [Backup] 21.4R3-S4 to 22.2R3-S2Logged in to RE1 [Backup]Upgrade
Upgrade the Satellite Device 21.4R3-S4 to 22.2R3-S2Logged in to RE1 [Backup]Change mastership to RE1 and causes outage for all circuits.UpgradeRE1 Reboots. Outage to connected satellite device circuits caused by mastership change.Change mastership to RE1 and causes outage for all circuits.
Upgrade RE0 [Backup] 21.4R3-S4 to 22.2R3-S2Logged in to RE0 [Backup]UpgradeRE0 Reboots and causes RE0 to become master.
I have confirmed the upgrade path is correct, just requesting a review of the upgrade steps.
Support recommended the following
20.2R3-S2 > 20.4R3-S3.4 > 21.4R3-S4.9 > 22.4R2-S1.6