JUniper SRX Upgrade - Options
JUniper SRX Upgrade - Options
JUniper SRX Upgrade - Options
Procedure steps:
1. Load the JunOS Software package on the device - KB20955
2. Verify the Health of the Cluster (This is an important step and the cluster
needs to be certified healthy before proceeding with In-Service Software
Upgrade) - KB20956
3. Create backup of the current configuration and set the rescue config -
KB20957
4. Start the In-Service Software Upgrade - KB20958
5. KB15376 - ISSU Hidden commands that can be used during ISSU testing
Step 1. Load the JunOS Software package on the device - KB20955
http://www.juniper.net/support/downloads/?p=srx1400#sw
http://www.juniper.net/support/downloads/?p=srx3400#sw
http://kb.juniper.net/InfoCenter/index?
page=content&id=KB21476&actp=search
- Check for available space on devices in order to be able to load the new
image
In cases where not enough space is available refer to the following:
o Step 6 of the Software Installation Preparation section of KB16652 -
SRX Getting Started - JunOS Software Installation has tips on checking
the flash size and purging unused files
o KB17365 - Freeing Up Space in Dual Root Partitions on SRX Branch
Devices
o If you cannot free up enough space, then refer to KB19466 - Common
and safest files to remove in order to increase the system storage OR
use CLI Installation Method 2 or 3 below (basically using the no-copy
option when image is stored remotely on FTP/USB)
For Branch devices (FWLFGW here) look for /cf/var partition usage.
For High-End devices (FWLFTE & FWLBKE here) look for /var/ partition
usage.
Additionally look for the location of JunOS images loaded on device used in
previous upgrades (if not cleaned-up) by using file list detail <path> | match
junos-srx.*domestic.tgz$ where path is usually /cf/var/tmp for Branch and
/var/tmp for High-End devices
o FWLFGW (srx240h)
o FWLFTE (srx1400)
o FWLBKE (srx3400)
- Once enough free space is available, load the image on devices (copy image
with WinSCP from rebound CEP to node0 of each cluster then copy it from
node0 to node1 with command file copy /<local-path>/<imagexyz.tgz>
node1:/<remote-path>) and perform and MD5 checksum (KB19931
Using the MD5checksum to Verify the Integrity of the JUNOS OS been pushed
into the Juniper Device) to ensure the transferred image is not truncated or
corrupted
o FWLFGW
o FWLFTE
o FWLBKE
- There are several ways of making sure to have a backup of the active
configuration
o Make sure to log your ssh terminal session and then issue these
commands:
show configuration | display set | no-more
show configuration | no-more
o Create a rescue configuration
For Branch SRX Series its possible to load the Rescue config using the reset
button as well: http://www.juniper.net/techpubs/en_US/release-
ndependent/junos/topics/task/operational/reset-config-button-srx240-using.html
o Retrieve available configurations from the local default location
The procedure starts from node0 and consists of only one command (assuming
pre-requisites are being met) as stated at the following Juniper TechLibrary link
http://www.juniper.net/documentation/en_US/junos12.1x46/topics/task/operation
al/chassis-cluster-upgrading-from-local-build-with-icu.html :