close

keyboard_arrow_left

Table of Contents Expand all

play_arrow Overview
play_arrow Configuring Switching Control Board Redundancy
- Understanding Switching Control Board Redundancy
- Configuring Switching Control Board Redundancy
play_arrow Configuring Bidirectional Forwarding Detection (BFD)
- Understanding How BFD Detects Network Failures
- Configuring BFD
play_arrow Configuring Routing Engine Redundancy
- Understanding Routing Engine Redundancy
- Configuring Routing Engine Redundancy
play_arrow Configuring Load Balancing
- Load Balancing on Aggregated Ethernet Interfaces
play_arrow Configuring Graceful Routing Engine Switchover (GRES)
play_arrow Configuring Ethernet Ring Protection Switching
- Understanding Ethernet Ring Protection Switching
- Configuring Ethernet Ring Protection Switching
play_arrow Configuring Nonstop Bridging
- Understanding Nonstop Bridging
- Configuring Nonstop Bridging
play_arrow Configuring Nonstop Active Routing (NSR)
- Understanding Nonstop Active Routing
- Configuring Nonstop Active Routing
play_arrow Configuring Graceful Restart
play_arrow Power Management Overview
play_arrow Configuring Virtual Router Redundancy Protocol (VRRP)
- Understanding VRRP
- Configuring VRRP
play_arrow Performing Unified In-Service Software Upgrade (ISSU)
play_arrow Performing Nonstop Software Upgrade (NSSU)
- Understanding Nonstop Software Upgrade on EX Series Switches
play_arrow Multinode High Availability
play_arrow Administration
play_arrow Verification Tasks
- Verifying Power Configuration and Use
play_arrow Troubleshooting
- Tracing Nonstop Active Routing Synchronization Events
- Troubleshooting the EX Series Redundant Power System Power On and Power Backup Issues
play_arrow Knowledge Base
- https://kb.juniper.net/

list Table of Contents

English

Upgrading Software on an EX6200 or EX8200 Standalone Switch Using Nonstop Software Upgrade (CLI Procedure)

date_range 20-Dec-24

arrow_backward

arrow_forward

You can use nonstop software upgrade (NSSU) to upgrade the software on standalone EX6200 or EX8200 switches with redundant Routing Engines. NSSU upgrades the software running on the Routing Engines and line cards with minimal traffic disruption during the upgrade. NSSU is supported on EX8200 switches running Junos OS Release 10.4 or later and on EX6200 switches running Junos OS Release 12.2 or later.

This topic covers:

Preparing the Switch for Software Installation

Before you begin software installation using NSSU:

(Optional) Configure line-card upgrade groups as described in Configuring Line-Card Upgrade Groups for Nonstop Software Upgrade. By default, an NSSU upgrades line cards one at a time to allow aggregated Ethernet links that have members on different line cards to remain up through the upgrade process. Configuring line-card upgrade groups reduces the time an upgrade takes because the line cards in each upgrade group are upgraded at the same time rather than sequentially.

Verify that the Routing Engines are running the same version of the software. Enter the following command:

content_copy zoom_out_map
{master}
user@switch> show version invoke-on all-routing-engines
re0:
--------------------------------------------------------------------------
Hostname: switch
Model: ex8208
JUNOS Base OS boot [11.3-20110429.1]
JUNOS Base OS Software Suite [11.3-20110429.1]
JUNOS Kernel Software Suite [11.3-20110429.1]
JUNOS Crypto Software Suite [11.3-20110429.1]
JUNOS Online Documentation [11.3-20110429.1]
JUNOS Enterprise Software Suite [11.3-20110429.1]
LC JUNOS Installation Software [11.3-20110429.1]
JUNOS Routing Software Suite [11.3-20110429.1]
JUNOS Web Management [11.3-20110429.1]

re1:
--------------------------------------------------------------------------
Hostname: switch
Model: ex8208
JUNOS Base OS boot [11.3-20110429.1]
JUNOS Base OS Software Suite [11.3-20110429.1]
JUNOS Kernel Software Suite [11.3-20110429.1]
JUNOS Crypto Software Suite [11.3-20110429.1]
JUNOS Online Documentation [11.3-20110429.1]
JUNOS Enterprise Software Suite [11.3-20110429.1]
LC JUNOS Installation Software [11.3-20110429.1]
JUNOS Routing Software Suite [11.3-20110429.1]
JUNOS Web Management [11.3-20110429.1]

If the Routing Engines are not running the same version of the software, use the request system software add command to upgrade the Routing Engine that is running the earlier software version.

Ensure that nonstop active routing (NSR) and graceful Routing Engine switchover (GRES) are enabled. To verify that they are enabled, you need to check only the state of nonstop active routing—if nonstop active routing is enabled, then graceful Routing Engine switchover is enabled.

To verify that nonstop active routing is enabled, execute the following command:
```
{master}
user@switch> show task replication
        Stateful Replication: Enabled
        RE mode: Master

    Protocol                Synchronization Status
    OSPF                    Complete
    RIP                     Complete
    PIM                     Complete
    RSVP                    Complete
```
If nonstop active routing is not enabled (Stateful Replication is Disabled), see Configuring Nonstop Active Routing on Switches for information on how to enable it.
(Optional) Enable nonstop bridging (NSB). Enabling NSB ensures that all NSB-supported Layer 2 protocols operate seamlessly during the Routing Engine switchover that is part of the NSSU.
(Optional) Back up the system software on each Routing Engine to an external storage device with the request system snapshot command.

Upgrading Both Routing Engines Using NSSU

This procedure describes how to upgrade both Routing Engines using NSSU. When the upgrade completes, both Routing Engines are running the new version of the software, and the backup Routing Engine is the new primary Routing Engine.

To upgrade both Routing Engines using NSSU:

Download the software package.
Copy the software package to the switch. We recommend that you use FTP to copy the file to the /var/tmp directory.
Log in to the primary Routing Engine using the console connection. You can perform an NSSU from the management interface, but a console connection allows you to monitor the progress of the primary Routing Engine reboot.

Install the new software package:

content_copy zoom_out_map
{master}
user@switch> request system software nonstop-upgrade reboot
 /var/tmp/package-name-m.nZx-distribution.tgz

where package-name-m.nZx-distribution.tgz is, for example, jinstall-ex-8200-10.4R1.5-domestic-signed.tgz.

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

content_copy zoom_out_map
Chassis ISSU Check Done
ISSU: Validating Image
ISSU: Preparing Backup RE
Pushing bundle to re1
WARNING: A reboot is required to install the software
WARNING:     Use the 'request system reboot' command immediately
Backup upgrade done
Rebooting Backup RE

Rebooting re1
ISSU: Backup RE Prepare Done
Waiting for Backup RE reboot
GRES operational
Initiating Chassis In-Service-Upgrade
Chassis ISSU Started
ISSU: Preparing Daemons
ISSU: Daemons Ready for ISSU
ISSU: Starting Upgrade for FRUs
ISSU: Preparing for Switchover
ISSU: Ready for Switchover
Checking In-Service-Upgrade status
  Item           Status                  Reason
  FPC 0          Online (ISSU)               
  FPC 1          Online (ISSU)               
  FPC 2          Online (ISSU)                 
  FPC 3          Offline                 Offlined by CLI command
  FPC 4          Online (ISSU)                 
  FPC 5          Online (ISSU)               
  FPC 6          Online (ISSU)               
  FPC 7          Online (ISSU)               
Resolving mastership...
Complete. The other routing engine becomes the master.
ISSU: RE switchover Done
ISSU: Upgrading Old Master RE
WARNING: A reboot is required to install the software
WARNING:     Use the 'request system reboot' command immediately
ISSU: Old Master Upgrade Done
ISSU: IDLE

 
*** FINAL System shutdown message from user@switch *** 
System going down IMMEDIATELY          

Shutdown NOW!
[pid 2635]

Note:

If you omit the reboot option in this step when using an EX8200 switch, you must manually reboot the original primary Routing Engine with the request system reboot command for the upgrade to complete.

The original primary Routing Engine reboots automatically after updating the new primary Routing Engine when an NSSU is used to upgrade an EX6200 switch with dual Routing Engines.

content_copy zoom_out_map
{backup}
user@switch> show version invoke-on all-routing-engines
re0:
------------------------------------------------------------------
Hostname: switch
Model: ex8208
JUNOS Base OS boot [12.1-20111229.0]
JUNOS Base OS Software Suite [12.1-20111229.0]
JUNOS Kernel Software Suite [12.1-20111229.0]
JUNOS Crypto Software Suite [12.1-20111229.0]
JUNOS Online Documentation [12.1-20111229.0]
JUNOS Enterprise Software Suite [12.1-20111229.0]
LC JUNOS Installation Software [12.1-20111229.0]
JUNOS Routing Software Suite [12.1-20111229.0]
JUNOS Web Management [12.1-20111229.0]

re1:
------------------------------------------------------------------
Hostname: switch
Model: ex8208
JUNOS Base OS boot [12.1-20111229.0]
JUNOS Base OS Software Suite [12.1-20111229.0]
JUNOS Kernel Software Suite [12.1-20111229.0]
JUNOS Crypto Software Suite [12.1-20111229.0]
JUNOS Online Documentation [12.1-20111229.0]
JUNOS Enterprise Software Suite [12.1-20111229.0]
LC JUNOS Installation Software [12.1-20111229.0]
JUNOS Routing Software Suite [12.1-20111229.0]
JUNOS Web Management [12.1-20111229.0]

To verify that the line cards that were online before the upgrade are online after the upgrade, log in to the primary Routing Engine and enter the show chassis nonstop-upgrade command:

content_copy zoom_out_map
{backup}
user@switch> request routing-engine login master

{master}
user@switch> show chassis nonstop-upgrade
  Item           Status                  Reason
  FPC 0          Online (ISSU)              
  FPC 1          Online (ISSU)               
  FPC 2          Online (ISSU)                  
  FPC 3          Offline                 Offlined by CLI command 
  FPC 4          Online (ISSU)                 
  FPC 5          Online (ISSU)               
  FPC 6          Online (ISSU)               
  FPC 7          Online (ISSU)               

If you want to make re0 the primary Routing Engine again, enter the following command:
```
{master}
user@switch> request chassis routing-engine master switch
Toggle mastership between routing engines ? [yes,no] (no) yes
```
You can verify that re0 is the primary Routing Engine by executing the show chassis routing-engine command.
To ensure that the resilient dual-root partitions feature operates correctly, execute the following command to copy the new Junos OS image into the alternate root partition on each Routing Engine:
```
user@switch> request system snapshot slice alternate routing-engine both
```
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.

Upgrading One Routing Engine Using NSSU (EX8200 Switch Only)

This procedure describes how to upgrade one of the Routing Engines using NSSU on an EX8200 switch. When the upgrade completes, the backup Routing Engine is running the new software version and is the new primary. The original primary Routing Engine, now the backup Routing Engine, continues to run the previous software version.

Note:

NSSU always upgrades the software on both Routing Engines on an EX6200 switch. Therefore, you cannot upgrade software on one Routing Engine using NSSU on an EX6200 switch.

To upgrade one Routing Engine using NSSU:

Download the software package.
Copy the software package to the switch. We recommend that you use FTP to copy the file to the /var/tmp directory.
Log in to the primary Routing Engine.

Request an NSSU. On an EX8200 switch, specify the no-old-master-upgrade option when requesting the NSSU:

content_copy zoom_out_map
{master}
user@switch> request system software nonstop-upgrade 
no-old-master-upgrade /var/tmp/package-name-m.nZx-distribution.tgz

where package-name-m.nZx-distribution.tgz is, for example, jinstall-ex-8200-10.4R2.5-domestic-signed.tgz.

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

content_copy zoom_out_map
Chassis ISSU Check Done
ISSU: Validating Image
ISSU: Preparing Backup RE
Pushing bundle to re1
WARNING: A reboot is required to install the software
WARNING:     Use the 'request system reboot' command immediately
Backup upgrade done
Rebooting Backup RE

Rebooting re1
ISSU: Backup RE Prepare Done
Waiting for Backup RE reboot
GRES operational
Initiating Chassis In-Service-Upgrade
Chassis ISSU Started
ISSU: Preparing Daemons
ISSU: Daemons Ready for ISSU
ISSU: Starting Upgrade for FRUs
ISSU: Preparing for Switchover
ISSU: Ready for Switchover
Checking In-Service-Upgrade status
  Item           Status                  Reason
  FPC 0          Online (ISSU)              
  FPC 1          Online (ISSU)               
  FPC 2          Online (ISSU)                  
  FPC 3          Offline                 Offlined by CLI command 
  FPC 4          Online (ISSU)                 
  FPC 5          Online (ISSU)               
  FPC 6          Online (ISSU)               
  FPC 7          Online (ISSU)               
Resolving mastership...
Complete. The other routing engine becomes the master.
ISSU: RE switchover Done
Skipping Old Master Upgrade
ISSU: IDLE

When the upgrade is complete, the original primary Routing Engine (re0) becomes the backup Routing Engine.

To verify that the original backup Routing Engine (re1) has been upgraded, enter the following command:

content_copy zoom_out_map
{backup}
user@switch> show version invoke-on all-routing-engines
re0:
----------------------------------------------------------------------
Hostname: switch
Model: ex8208
JUNOS Base OS boot [11.3-20110429.1]
JUNOS Base OS Software Suite [11.3-20110429.1]
JUNOS Kernel Software Suite [11.3-20110429.1]
JUNOS Crypto Software Suite [11.3-20110429.1]
JUNOS Online Documentation [11.3-20110429.1]
JUNOS Enterprise Software Suite [11.3-20110429.1]
LC JUNOS Installation Software [11.3-20110429.1]
JUNOS Routing Software Suite [11.3-20110429.1]
JUNOS Web Management [11.3-20110429.1]

re1:
----------------------------------------------------------------------
Hostname: switch
Model: ex8208
JUNOS Base OS boot [12.1-20111229.0]
JUNOS Base OS Software Suite [12.1-20111229.0]
JUNOS Kernel Software Suite [12.1-20111229.0]
JUNOS Crypto Software Suite [12.1-20111229.0]
JUNOS Online Documentation [12.1-20111229.0]
JUNOS Enterprise Software Suite [12.1-20111229.0]
LC JUNOS Installation Software [12.1-20111229.0]
JUNOS Routing Software Suite [12.1-20111229.0]
JUNOS Web Management [12.1-20111229.0]

To verify that the line cards that were online before the upgrade are online after the upgrade, log in to the new primary Routing Engine and enter the show chassis nonstop-upgrade command:

content_copy zoom_out_map
{backup}
user@switch> request routing-engine login master

--- JUNOS 12.1-20111229.0 built 2011-12-29 04:12:22 UTC
{master}
user@switch> show chassis nonstop-upgrade
  Item           Status                  Reason
  FPC 0          Online               
  FPC 1          Online                
  FPC 2          Online                   
  FPC 3          Offline                 Offlined by CLI command 
  FPC 4          Online                  
  FPC 5          Online                
  FPC 6          Online                
  FPC 7          Online                
 

To ensure that the resilient dual-root partitions feature operates correctly, copy the new Junos OS image into the alternate root partition of the Routing Engine:
```
user@switch> request system snapshot slice alternate
```
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.

Upgrading the Original Primary Routing Engine (EX8200 Switch Only)

This procedure describes how to upgrade the original primary Routing Engine after you have upgraded the original backup Routing Engine as described in Upgrading One Routing Engine Using NSSU (EX8200 Switch Only) for an EX8200 switch.

Log in to the current primary Routing Engine (re1).
Enter configuration mode and disable nonstop active routing:
```
{master}[edit]
user@switch# delete routing-options nonstop-routing
```

Deactivate graceful Routing Engine switchover and commit the configuration:

content_copy zoom_out_map
{master}[edit]
user@switch# deactivate chassis redundancy graceful-switchover

{master}[edit]
user@switch# commit

Log in to the current backup Routing Engine (re0) using a console connection.
Request a software installation:
```
user@switch> request system software add reboot /var/tmp/package-name-m.nZx-distribution.tgz 
```
Note:
When you use NSSU to upgrade only one Routing Engine, the installation package is not automatically deleted from /var/tmp, leaving the package available to be used to upgrade the original primary Routing Engine.
After the upgrade completes, log in to the current primary Routing Engine (re1) and enter CLI configuration mode.

Re-enable nonstop active routing and graceful Routing Engine switchover:

content_copy zoom_out_map
[edit]
user@switch# activate chassis redundancy graceful-switchover

[edit]
user@switch# set routing-options nonstop-routing

[edit]
user@switch# commit

To ensure that the resilient dual-root partitions feature operates correctly, exit the CLI configuration mode and copy the new Junos OS image into the alternate root partition of the Routing Engine:
```
user@switch> request system snapshot slice alternate
```
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.
(Optional) To return control to the original primary Routing Engine (re0), enter the following command:
```
{master}
user@switch> request chassis routing-engine master switch
 Toggle mastership between routing engines ? [yes,no] (no) yes
```
You can verify that re0 is the primary Routing Engine by executing the show chassis routing-engine command.

arrow_backward PREVIOUS Multinode High Availability Monitoring Options

NEXT arrow_forward Upgrading Software on an EX8200 Virtual Chassis Using Nonstop Software Upgrade (CLI Procedure)

High Availability User Guide

ON THIS PAGE

Upgrading Software on an EX6200 or EX8200 Standalone Switch Using Nonstop Software Upgrade (CLI Procedure)

Preparing the Switch for Software Installation

Upgrading Both Routing Engines Using NSSU

Upgrading One Routing Engine Using NSSU (EX8200 Switch Only)

Upgrading the Original Primary Routing Engine (EX8200 Switch Only)

Stay in touch

Helped me install or use the product
Accelerated my deployment

Discuss the product with a co-worker
Make a purchase inquiry

High Availability User Guide

ON THIS PAGE

Upgrading Software on an EX6200 or EX8200 Standalone Switch Using Nonstop Software Upgrade (CLI Procedure)

Preparing the Switch for Software Installation

Upgrading Both Routing Engines Using NSSU

Upgrading One Routing Engine Using NSSU (EX8200 Switch Only)

Upgrading the Original Primary Routing Engine (EX8200 Switch Only)

Related Documentation

Stay in touch