Table 19: Routing Engine Status Before Upgrading - Juniper EX9200 Features Manual

High Availability Feature Guide for EX9200 Switches
Step-by-Step
Procedure
194
user@host>
Upgrading and Rebooting Both Routing Engines Automatically
In this procedure, both Routing Engines automatically reboot. Rebooting both Routing
Engines automatically is the most common scenario. Variations to this procedure are
described in other sections.
Table 19 on page 194 shows the Routing Engine status prior to starting the unified ISSU.

Table 19: Routing Engine Status Before Upgrading

RE0
Master
Old software version installed
Old software version running
To upgrade and reboot both Routing Engines automatically:
Copy the Junos OS software package to the device by using the
1.
ftp://username@hostname.net/filename /var/tmp/filename
We recommend that you copy the package to the
large file system on the hard disk.
{master}
user@host> file copy
ftp://myid@myhost.mydomain.net/jinstall64-14.1R4.10-domestic-signed.tgz
/var/tmp/jinstall64-14.1R4.10-domestic-signed.tgz
BEST PRACTICE:
for your device, record the md5 checksum. After downloading the
software package to your device, confirm that it is not modified in any
way by using the
about verifying the md5 checksum, see
http://kb.juniper.net/InfoCenter/index?page=content&id=KB17665
On the master Routing Engine, start the upgrade by using the
2.
in-service-upgrade package-name reboot
NOTE: Do not try running any additional commands until after the
Connection closed
{master}
RE1
Backup
Old software version installed
Old software version running
/var/tmp
When you access the Download Software web page
file checksum md5 command. For more information
command.
message is displayed and your session is disconnected.
Copyright © 2017, Juniper Networks, Inc.
file copy
command.
directory, which is a
.
request system software