Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

Upgrading Software on a Virtual Chassis and Mixed Virtual Chassis Using Nonstop Software Upgrade

• Preparing the Switch for Software Installation
• Upgrading the Software Using NSSU

Preparing the Switch for Software Installation

Before you begin software installation using NSSU:

• Ensure that the Virtual Chassis or mixed Virtual Chassis is configured correctly to support NSSU. Verify that:
  • The Virtual Chassis or mixed Virtual Chassis members are connected in a ring topology. A ring topology prevents the Virtual Chassis from splitting during an NSSU.
  • The Virtual Chassis or mixed Virtual Chassis master and backup are adjacent to each other in the ring topology. Adjacency permits the master and backup to always be in sync, even when the switches in linecard roles are rebooting.
  • The Virtual Chassis or mixed Virtual Chassis is preprovisioned so that the linecard role has been explicitly assigned to member switches acting in the linecard role. During an NSSU, the Virtual Chassis or mixed Virtual Chassis members must maintain their roles—the master and backup must maintain their master and backup roles (although mastership will change), and the other member switches must maintain their linecard roles.
  • A two-member Virtual Chassis has no-split-detection configured so that the Virtual Chassis does not split when an NSSU upgrades a member.
• Verify that the members are running the same version of the software:
  user@switch> show version

  If the Virtual Chassis or mixed Virtual Chassis members are not running the same version of the software, use the request system software add command to upgrade the software on the inconsistent members.

• Ensure that graceful Routing Engine switchover (GRES) is enabled.
• (Optional) Back up the system software—Junos OS, the active configuration, and log files—on each member to an external storage device with the request system snapshot command.

Upgrading the Software Using NSSU

1. Download the software package by following the procedure in the Downloading Software Files with a Browser section in Upgrading Software.
2. Copy the software package or packages to the Virtual Chassis or mixed Virtual Chassis. We recommend that you copy the file to the /var/tmp directory on the master.
3. Log in to the Virtual Chassis or mixed Virtual Chassis using the console connection or the virtual management Ethernet (VME) interface. Using a console connection allows you to monitor the progress of the master switch reboot.
4. Start the NSSU:
   • On a Virtual Chassis or mixed Virtual Chassis, enter:

     user@switch> request system software nonstop-upgrade force-host /var/tmp/package-name.tgz

     where package-name.tgz is, for example, jinstall-qfx-3-13.2X50-D15.3-domestic-signed.tgz.

   The switch displays status messages similar to the following messages as the upgrade executes:

   Chassis ISSU Check Done
   NSSU: Validating Image
   NSSU: Preparing Backup RE
   Installing image on other FPC's along with the backup
   
   Checking pending install on fpc1
   Pushing bundle to fpc1
   WARNING: A reboot is required to install the software
   WARNING:     Use the 'request system reboot' command immediately
   Completed install on fpc1
   
   Checking pending install on fpc2
   Pushing bundle to fpc2
   WARNING: A reboot is required to install the software
   WARNING:     Use the 'request system reboot' command immediately
   Completed install on fpc2
   
   Rebooting fpc1
   NSSU: Backup RE Prepare Done
   Waiting for Backup RE reboot
   GRES operational
   Initiating Chassis In-Service-Upgrade
   Chassis NSSU Started
   NSSU: Preparing Daemons
   NSSU: Daemons Ready for NSSU
   NSSU: Starting Upgrade for FRUs
   NSSU: Preparing for Switchover
   NSSU: Ready for Switchover
   Checking In-Service-Upgrade status
     Item           Status                  Reason
     FPC 0          Online
     FPC 1          Online
     FPC 2          Online (ISSU)
   Going to install image on master
   WARNING: A reboot is required to install the software
   WARNING:     Use the 'request system reboot' command immediately
   relinquish mastership
   NSSU: IDLE
   
   *** FINAL System shutdown message from user@switch ***
   
   System going down IMMEDIATELY
   
   
   Shutdown NOW!
   [pid 9336]
   

5. Log in after the reboot of the original master switch completes. To verify that the software on all Routing Engines in the Virtual Chassis or mixed Virtual Chassis members has been upgraded, enter the following command:
   user@switch> show version
6. To ensure that the resilient dual-root partitions feature operates correctly, copy the new Junos OS image into the alternate root partitions of all members:
   user@switch> request system snapshot slice alternate all-members

   Resilient dual-root partitions allow the switch to boot transparently from the alternate root partition if the system fails to boot from the primary root partition.