Will go through the process of upgrading the Junos version on an EX-Series switch with a Virtual Chassis or a Single Routing Engine using the Command Line Interface (CLI). Specifically, we'll demonstrate this process for an EX3400 series switch, but the steps are applicable to several other EX Series models as well.
This procedure can be used to upgrade the following switches or Virtual Chassis:
EX2200 switch
EX2300 switch
EX3200 switch
EX3300 switch
EX3400 switch
EX4100 switch
EX4200 switch
EX4300 switch
EX4500 switch
EX4550 switch
EX6200 switch (single Routing Engine upgrade only)
EX8200 switch (single Routing Engine upgrade only)
All Virtual Chassis except EX8200 Virtual Chassis
Pre-Task
Before you begin the upgrade process, ensure that you've completed the following pre-task steps:
Download the Firmware: Download the desired Junos OS firmware version from the official Juniper Networks support page and copy it onto a USB stick formatted with FAT32.
Backup Configuration: Take a backup of the device's configuration using the CLI. You can use below commands to back up your configuration.
show configuration | no-more
show configuration | display set | no-more
show configuration | display set | save /var/tmp/CONFIG-dd/mm/yyyy.txt
Create a Snapshot: Make a snapshot of the existing Junos configuration using show system snapshot and request system snapshot.
Disk Space Validation and Cleanup: Validate the available disk space on the device using show system storage and run request system storage cleanup to free up space if necessary.
Health Check: Perform a health check on the Juniper device by examining SNMP logs, log time settings, hardware status, system status, interface status, route summary, and other relevant parameters. Use the provided CLI commands to gather this information.
#SNMP logs
run show snmp health-monitor alarms | no-more
run show snmp health-monitor logs | no-more
#Log Time
set cli timestamp
set cli screen-width 200
show ntp associations no-resolve | no-more
show ntp status no-resolve | no-more
## Hardware Status
show chassis hardware | no-more
show chassis hardware clei-models | no-more
show chassis hardware detail | no-more
show chassis fpc detail | no-more
show chassis fpc pic-status | no-more
show chassis environment | no-more
show chassis routing-engine | no-more
show version invoke-on all-routing-engines | no-more
## Based on Platform
show chassis fabric reachability | no-more
show chassis fabric fpcs | no-more
show chassis fabric plane | no-more
show chassis fabric plane-location | no-more
show chassis fabric summary | no-more
## System Status
show chassis alarms | no-more
show system alarms | no-more
show system commit | no-more
show system core-dumps | no-more
## Interfaces Status
show arp no-resolve expiration-time | no-more
show interfaces diagnostics optics | no-more
show interfaces redundancy | no-more
show interfaces terse | match “up up” | count | no-more
show interfaces terse | match down | count | no-more
show interfaces terse | match down | no-more
show interfaces descriptions | match up | count | no-more
show interfaces descriptions | match down | count | no-more
show interface terse | no-more
show interfaces extensive | no-more
## Route Summary
show krt queue | no-more
show route summary | no-more
show route forwarding-table summary | no-more
## LACP
show lacp interfaces | no-more
show ppm adjacencies detail | no-more
## BFD
show bfd session detail | no-more
show bfd session extensive | no-more
show ppm adjacencies detail | no-more
## VRRP
show vrrp | no-more
## LDP
show ldp interface | no-more
show ldp neighbor | no-more
show ldp session | no-more
## VLAN and IRB
show vlans |no-more
show interfaces irb terse |no-more
## Storage
show system storage invoke-on all-routing-engines | no-more
## Configuration backup and RSI
show system commit | no-more
show configuration | no-more
show configuration | display set | no-more
request support information | no-more
## SLM/SLC
show log messages | no-more
show log chassisd | no-more
Upgrade Steps
Here is an example of upgrading the Junos on an EX3400 switch to 20.4R3-S4
Step 1: Mounting the USB Stick
1.1. Enter shell mode: start shell.
1.2. Identify USB device: Type ls /dev/da* and press ENTER to list available storage devices. (Do not plug in the USB stick yet.)
Step 2: Plugging in the USB Stick
2.1. Plug in the USB stick.
2.2. Identify USB device: Type ls /dev/da* and press Enter. Note the new folder /dev/da1s1. This represents the USB stick. It may differ, but this is the most common.
Step 3: Creating a Mount Point
3.1. Create a directory for mounting: Type mkdir /var/tmp/usb and press ENTER.
3.2. Mount the USB stick: Type mount_msdosfs /dev/da1s1 /var/tmp/usb and press ENTER.
Step 4: Copying Junos from USB to Mount Point
4.1. Copy the Junos package from the USB stick to the mount point: Type cp /var/tmp/usb/jinstall-ex-2200-12.3R12-S21-domestic-signed.tgz /var/tmp and press ENTER.
Step 5: Verifying MD5 Checksum
5.1. Exit shell mode by cli
5.2. Calculate the MD5 checksum for the copied file: Run the following CLI command: file checksum md5 /var/tmp/jinstall-ex-2200-12.3R12-S21-domestic-signed.tgz. Ensure that the calculated MD5 value matches the MD5 value provided by Juniper.
Step 6: Installing the New Package on the Switch
6.1. Install the new Junos package on the switch: Run the following CLI command: request system software add /var/tmp/jinstall-ex-2200-12.3R12-S21-domestic-signed.tgz.
Step 7: Reloading the Switch
7.1. Reload the switch to apply the changes: Run the following CLI command: request system reboot.
After the reboot, it's essential to verify that the upgrade was successful:
Check the Version: Run the following CLI commands to check the new version:
show version
show system information
In case any issues arise after the upgrade, you can roll back to the previous version:
Run the following CLI command to initiate a rollback:
request system software rollback
