Procedure to Upgrade JUNOS on a Dual Routing Engin... https://supportportal.juniper.net/s/article/Procedure-to...

Home Knowledge Cases RMAs

Procedure to Upgrade JUNOS on a Dual Routing Engine

System
Article ID KB8911 Created 2006-09-13

Last Updated 2021-04-01

Description

This article details the procedure to perform a Junos OS upgrade on a dual Routing Engine system.

Symptoms

Performing a Junos OS upgrade on a system with dual Routing Engines requires the user to follow a speci�c
path dictated by the features and services that are enabled on the router.

Solution

Point to Note Before Upgrade

If graceful Routing Engine switchover (GRES) or nonstop active routing (NSR) is enabled when you
initiate a software installation, the software does not install properly. Make sure you deactivate GRES (if
it is enabled).

By default, NSR is disabled. If NSR is enabled, remove the nonstop-routing statement from the [edit
routing-options] hierarchy level to disable it. Also, make sure to disable nonstop-bridging from
the [edit protocols layer2-control] hierarchy, if it is enabled.

Note: The following instructions are also provided in the Technical Documentation under your speci�c
product and version of Junos OS.
Look for the section titled: Installing the Software Package on a Router with Redundant Routing Engines
Following is a brief overview of a dual Routing Engine (RE) upgrade process. Please read the procedure in its
entirety before attempting to upgrade a dual RE system.
Assumptions
1. Primary routing engine is RE0 and backup routing engine is RE1.
2. The code upgrade is going to be performed using a �le on the router (as opposed to it being on the
network).
3. It is always recommended to connect to the RE via console while performing an upgrade/reboot.
4. The procedure below also assumes that mirror-flash-on-disk is disabled on the router.

NOTE: If mirror-flash-on-disk was enabled and you disable it, the RE will need to be
rebooted.

1 of 9 25.05.2022, 18:42
Procedure to Upgrade JUNOS on a Dual Routing Engin... https://supportportal.juniper.net/s/article/Procedure-to...

Steps
1. Pre-stage code

Ensure that both RE0 and RE1 are code-staged with "jinstall" package to which the router needs to
be upgraded. Store the JUNOS install �le in the /var/tmp directory. Load it on the primary RE,
and copy it to the backup RE as follows:

1. Ensure that code is loaded on primary RE.

{MASTER}
lab@juniper-re0> file copy ftp://username:[email protected]/jinstall-7.3
/var/tmp/jinstall-7.3R2.9-domestic-signed.tgz

{MASTER}
lab@juniper-re0> file list detail /var/tmp/ | match 7.3R2.9

-rw-r--r-- 1 lab wheel 68360951 Jan 10 20:18 jinstall-7.3R2.9-domestic-signed.

2. Generate MD5 checksum on the downloaded �le. Compare this to the MD5 for the �le
available on Juniper's software download website and ensure that they are the same.

{MASTER}

lab@juniper-re0> file checksum md5 /var/tmp/jinstall-7.3R2.9-domestic-signed.t

MD5 (/var/tmp/jinstall-7.3R2.9-domestic-signed.tgz) = 2aeea107768bb1789aedbe45

3. Log in to the backup RE and copy the �le over from the primary RE (this might take a while
due to the size of the �le). It is highly recommended that you connect to the backup RE via
console, but in the absence of such a connection, one can telnet between REs.

{MASTER}
lab@juniper-re0> request routing-engine login re1
€
--- JUNOS 7.5-20060103.0 built 2006-01-03 08:15:55 UTC
{BACKUP}
lab@juniper-re1> file copy re0:/var/tmp/jinstall-7.3R2.9-domestic-signed.tgz r

{BACKUP}
lab@juniper-re1>

2 of 9 25.05.2022, 18:42
Procedure to Upgrade JUNOS on a Dual Routing Engin... https://supportportal.juniper.net/s/article/Procedure-to...

4. Generate MD5 checksum on the �le in the backup RE, and compare it to the checksum
generated on the �le in the primary RE in step ‘1.2’ above. Con�rm that the checksum values
are the same.

{BACKUP}
lab@juniper-re1> file checksum md5 /var/tmp/jinstall-7.3R2.9-domestic-signed.t
MD5 (/var/tmp/jinstall-7.3R2.9-domestic-signed.tgz) = 2aeea107768bb1789aedbe45

2. Con�guration Modi�cations

1. Disable Graceful Switchover: THIS IS AN EXTREMELY IMPORTANT STEP IN THE DUAL RE

UPGRADE PROCESS . Skipping this step can potentially result in the control plane and
forwarding plane having two different JUNOS versions. Please make sure either chassis
graceful-switchover is not enabled in the con�guration, or if it is enabled, disable or
deactivate that part of the con�guration. You will �nd this command under following
hierarchy - [ chassis redundancy graceful-switchover] .

{MASTER}[edit]
lab@juniper-re0# show chassis redundancy
inactive: graceful-switchover {
enable;
}

2. Disable failover of REs on loss of keepalive/disk: This step is not necessary if you are
performing the upgrade using option 5.1 below. Please review the document in its entirety
and decide on the upgrade procedure in order to determine the applicability of this step.
Please make sure either chassis redundancy failover is not enabled in the
con�guration, or if it is enabled, deactivate that part of the con�guration. You will �nd this
command under following hierarchy - [chassis redundancy failover] .

{MASTER}[edit]
lab@juniper-re0# show chassis redundancy
inactive: failover {
on-loss-of-keepalives;
on-disk-failure;
}

3 of 9 25.05.2022, 18:42
Procedure to Upgrade JUNOS on a Dual Routing Engin... https://supportportal.juniper.net/s/article/Procedure-to...

3. Saving Con�guration: If you are using the routing engines as primary and hot backup REs,
then use commit synchronize command to ensure that the same con�guration �le is
saved on both routing engines. Note that if chassis redundancy is deactivated or
deleted in the con�guration, the routing engines will no longer work in an automatic failover
mode. An example output:

{MASTER}
lab@juniper-re0> configure
Entering configuration mode

{MASTER}[edit]
lab@juniper-re0# commit check
configuration check succeeds

{MASTER}[edit]
lab@juniper-re0# commit synchronize
re0:
configuration check succeeds
re1:
commit complete
re0:
commit complete

[edit]
lab@juniper-re0# quit
Exiting configuration mode

lab@juniper-re0> request routing-engine login other-routing-engine

€
--- JUNOS 7.5-20060103.0 built 2006-01-03 08:15:55 UTC
lab@juniper-re1>

3. Backup File System

1. Back-up the currently running and active �le system by issuing the request system snapshot
command on both primary as well as backup REs (assuming that both systems have two
pieces of storage media each).

lab@juniper> request system snapshot

Copying / to /altroot.. (this may take a few minutes)

Copying /config to /altconfig.. (this may take a few minutes)
The following filesystems were archived: / /config

4 of 9 25.05.2022, 18:42
Procedure to Upgrade JUNOS on a Dual Routing Engin... https://supportportal.juniper.net/s/article/Procedure-to...

2. There are other checks and pieces of information that should be collected from the system.
A summary of these commands is available online on Juniper’s website in the Network
Operations Guide's section titled "Before You Upgrade JUNOS Software" (see link to section
in the "Related Links" section below).

4. Perform Junos OS upgrade on backup RE

1. Once again, it is highly recommended that you connect to RE1 via console, but in the
absence of such a connection, one can telnet between REs by using the following command
–

lab@juniper-re0> request routing-engine login re1

2. Once connected, use the "jinstall" package to perform upgrade on RE1. For instance:

lab@juniper-re1> request system software add /var/tmp/jinstall-7.3R2.9-domesti

3. Once the software is added on RE1, reboot it. Connection to RE1 will be lost.

lab@juniper-re1> request system reboot

Reboot the system ? [yes,no] (no) yes

*** FINAL System shutdown message from lab@juniper-re1 ***

System going down IMMEDIATELY

Shutdown NOW!
Reboot consistency check bypassed - jinstall 7.3R2.9 will complete installatio
[pid 8007]

lab@juniper-re1> rlogin: connection closed.

lab@juniper-re0>

4. One can either watch RE1 boot up via console, or issue the show chassis routing-
engine to con�rm that it is up and running. Following is an example of the show
chassis routing-engine output when both REs are up and running:

5 of 9 25.05.2022, 18:42
Procedure to Upgrade JUNOS on a Dual Routing Engin... https://supportportal.juniper.net/s/article/Procedure-to...

lab@juniper-re0> show chassis routing-engine

Routing Engine status:
Slot 0:
Current state Master
Election priority Master (default)
Temperature 36 degrees C / 96 degrees F
CPU temperature 38 degrees C / 100 degrees F
DRAM 2048 MB
Memory utilization 20 percent
CPU utilization:
User 3 percent
Background 0 percent
Kernel 0 percent
Interrupt 0 percent
Idle 96 percent
Model RE-4.0
Serial ID P11123904753
Start time 2006-10-16 11:17:12 CEST
Uptime 4 hours, 5 minutes, 40 seconds
Load averages: 1 minute 5 minute 15 minute
0.00 0.00 0.00
Routing Engine status:
Slot 1:
Current state Backup
Election priority Backup (default)
Temperature 37 degrees C / 98 degrees F
CPU temperature 39 degrees C / 102 degrees F
DRAM 2048 MB
Memory utilization 15 percent
CPU utilization:
User 0 percent
Background 0 percent
Kernel 3 percent
Interrupt 1 percent
Idle 96 percent
Model RE-4.0
Serial ID P11123904734
Start time 2006-10-16 11:53:55 CEST
Uptime 3 hours, 28 minutes, 44 seconds

5. Perform Junos OS upgrade on primary RE

Going ahead, there are a couple of options available to complete the installation of JUNOS on the
primary RE. Below is a description of these options:

1. Least downtime, Manual Switchovers

6 of 9 25.05.2022, 18:42
Procedure to Upgrade JUNOS on a Dual Routing Engin... https://supportportal.juniper.net/s/article/Procedure-to...

a. Once RE1 has come up after the upgrade, switchover the primary role from RE0 to RE1.
Note that this step will cause a hit. There will be some downtime as the forwarding plane will
be reset and the new �rmware will be loaded on to it.

lab@juniper-re0> request chassis routing-engine master switch

warning: Traffic will be interrupted while the PFE is re-initialized
Toggle mastership between routing engines ? [yes,no] (no) yes

Resolving mastership...
Complete. The other routing engine becomes the master.

b. Log into RE1, and con�rm that the hardware and routing protocols have failed over
correctly (compare with the outputs collected in step 3.2).
c. On a session to RE0, use the "jinstall" package to perform upgrade. For instance:

lab@juniper-re0> request system software add /var/tmp/jinstall-7.3R2.9-domesti

d. Once the software is added on RE0, reboot it. Connection to RE0 will be lost.

lab@juniper-re0> request system reboot

Reboot the system ? [yes,no] (no) yes

*** FINAL System shutdown message from lab@juniper-re0 ***

System going down IMMEDIATELY

Shutdown NOW!
Reboot consistency check bypassed - jinstall 7.3R2.9 will complete installatio
[pid 9065]

e. Log back into RE1 (preferably via console), and con�rm that RE0 has booted up using the
show chassis routing-engine command.
f. Proceed to step 6.

2. More downtime, No Switchover

Once RE1 has come up, perform JUNOS upgrade on RE0 (without switching the primary
role to RE1). Please note that RE0 will also need to be rebooted in order to complete the
JUNOS installation, at which point, the system will not pass traf�c until it comes back up and
all the processes stabilize. In this case, the router is down for a longer duration than the one
encountered during switchovers in option 5.1.

7 of 9 25.05.2022, 18:42
Procedure to Upgrade JUNOS on a Dual Routing Engin... https://supportportal.juniper.net/s/article/Procedure-to...

a. Use the "jinstall" package to perform upgrade on RE0. For example:

lab@juniper-re0> request system software add jinstall-7.3R2.9-domestic-signed.

b. Once the software is successfully added on to the primary RE, reboot it.

lab@juniper-re0> request system reboot Reboot the system ? [yes,no] (no) yes

c. Con�rm that RE0 comes back up (watch the RE reboot via console) and all
protocols/processes stabilize before shifting traf�c back on to the system (compare with the
outputs collected in step 3.2).
d. Proceed to step 6.

6. Revert con�guration changes

1. Once the upgrade on both routing engines is done successfully, be sure to reverse all
con�guration changes performed in step 2. Ensure that both REs have the same con�guration
�les at the end of this by issuing a commit synchronize . Ensure that the commit
synchronize command is issued from the primary routing engine.
2. If the current primary is RE1, but needs to be RE0, the primary role needs to be switched.
Please ensure that the chassis redundancy section of the con�g contains the
graceful-switchover enable command before switching the primary role.

{MASTER}
lab@juniper-re1> show configuration chassis redundancy
graceful-switchover {
enable;
}

{MASTER}
lab@juniper-re1> request chassis routing-engine master switch
Toggle mastership between routing engines ? [yes,no] (no) yes

Resolving mastership...
Complete. The other routing engine becomes the master.

{BACKUP}
lab@juniper-re1>
Message from syslogd@juniper-re0 cfeb at Jan 10 22:19:02 ...
juniper-re0 cfeb RDP: Remote side reset connection: rdp.(scb:7178).(serverRouter:ch
Message from syslogd@juniper-re0 cfeb at Jan 10 22:19:02 ...
juniper-re0 cfeb CM: ALARM SET: (Major) RE chassis socket closed abruptly
Message from syslogd@juniper-re0 cfeb at Jan 10 22:19:03 ...
juniper-re0 cfeb RDP: Remote side reset connection: rdp.(scb:7179).(serverRouter:pf

{BACKUP}
lab@juniper-re1>

7. Post Install

8 of 9 25.05.2022, 18:42
Procedure to Upgrade JUNOS on a Dual Routing Engin... https://supportportal.juniper.net/s/article/Procedure-to...

Once suf�cient time has passed to determine the stability of the new �rmware, back-up the
currently running and active �le system by once again issuing the request system snapshot
command on both primary as well as backup REs (assuming that both systems have two pieces of
storage media each).

lab@juniper> request system snapshot

Copying / to /altroot.. (this may take a few minutes)
Copying /config to /altconfig.. (this may take a few minutes)
The following filesystems were archived: / /config

People also viewed

Modi�cation History
2022-04 Security Bulletin: Junos OS Evolved: Speci�c packets reaching the RE lead to a counter
over�ow and
2020-05-04: eventually
Added a noteaabout
crashsoftware
(CVE-2022-22195)
not installing properly if GRES and NSR are enabled
2021-03-24: Updated the article terminology to align with Juniper's Inclusion & Diversity initiatives
2022-04 Security Bulletin: Junos OS and Junos OS Evolved: The rpd CPU spikes to 100% after a
Related Information
malformed ISIS TLV has been received (CVE-2022-22196)

• Installing Software on Routing Devices

Was this article helpful? 1 0

AFFECTED PRODUCT SERIES / FEATURES
Choose a general reason

-- Choose a general reason --

Description

Please, leave us some feedback...

Submit

9 of 9 25.05.2022, 18:42