- play_arrow Understanding How Virtual Chassis Provides Interchassis Redundancy
- play_arrow Understanding How a Virtual Chassis Works
- play_arrow Configuring a Virtual Chassis
- Configuring Interchassis Redundancy for MX Series 5G Universal Routing Platforms Using a Virtual Chassis
- Preparing for a Virtual Chassis Configuration
- Creating and Applying Configuration Groups for a Virtual Chassis
- Configuring Preprovisioned Member Information for a Virtual Chassis
- Configuring Enhanced IP Network Services for a Virtual Chassis
- Configuring Enhanced LAN Mode for a Virtual Chassis
- Enabling Graceful Routing Engine Switchover and Nonstop Active Routing for a Virtual Chassis
- Configuring Member IDs for a Virtual Chassis
- Configuring an MX2020 Member Router in an Existing MX Series Virtual Chassis
- Switching the Global Primary and Backup Roles in a Virtual Chassis Configuration
- Deleting Member IDs in a Virtual Chassis Configuration
- Example: Replacing a Routing Engine in a Virtual Chassis Configuration for MX Series 5G Universal Routing Platforms
- Deleting a Virtual Chassis Configuration for MX Series 5G Universal Routing Platforms
- Example: Deleting a Virtual Chassis Configuration for MX Series 5G Universal Routing Platforms
- Upgrading an MX Virtual Chassis SCB or SCBE to SCBE2
- play_arrow Configuring Virtual Chassis Ports to Interconnect Member Devices
- play_arrow Configuring Locality Bias to Conserve Bandwidth on Virtual Chassis Ports
- play_arrow Configuring Class of Service for Virtual Chassis Ports
- play_arrow Configuring Redundancy Mechanisms on Aggregated Ethernet Interfaces in a Virtual Chassis
- Redundancy Mechanisms on Aggregated Ethernet Interfaces in a Virtual Chassis
- Configuring Module Redundancy for a Virtual Chassis
- Configuring Chassis Redundancy for a Virtual Chassis
- Multichassis Link Aggregation in a Virtual Chassis
- Targeted Traffic Distribution on Aggregated Ethernet Interfaces in a Virtual Chassis
- Understanding Support for Targeted Distribution of Logical Interface Sets of Static VLANs over Aggregated Ethernet Logical Interfaces
- play_arrow Upgrading Junos OS in a Virtual Chassis Configuration for MX Series 5G Universal Routing Platforms by Rebooting the Routing Engines
- play_arrow Upgrading Junos OS in an MX Series Virtual Chassis by Performing a Unified In-Service Software Upgrade (ISSU)
- play_arrow Monitoring an MX Series Virtual Chassis
- Accessing the Virtual Chassis Through the Management Interface
- Verifying the Status of Virtual Chassis Member Routers or Switches
- Verifying the Operation of Virtual Chassis Ports
- Verifying Neighbor Reachability for Member Routers or Switches in a Virtual Chassis
- Verifying Neighbor Reachability for Hardware Devices in a Virtual Chassis
- Determining GRES Readiness in a Virtual Chassis Configuration
- Viewing Information in the Virtual Chassis Control Protocol Adjacency Database
- Viewing Information in the Virtual Chassis Control Protocol Link-State Database
- Viewing Information About Virtual Chassis Port Interfaces in the Virtual Chassis Control Protocol Database
- Viewing Virtual Chassis Control Protocol Routing Tables
- Viewing Virtual Chassis Control Protocol Statistics for Member Devices and Virtual Chassis Ports
- Verifying and Managing the Virtual Chassis Heartbeat Connection
- Inline Flow Monitoring for Virtual Chassis Overview
- Managing Files on Virtual Chassis Member Routers or Switches
- Virtual Chassis SNMP Traps
- Virtual Chassis Slot Number Mapping for Use with SNMP
- Example: Determining Member Health Using an MX Series Virtual Chassis Heartbeat Connection with Member Routers in the Same Subnet
- Example: Determining Member Health Using an MX Series Virtual Chassis Heartbeat Connection with Member Routers in Different Subnets
- play_arrow Tracing Virtual Chassis Operations for Troubleshooting Purposes
- Tracing Virtual Chassis Operations for MX Series 5G Universal Routing Platforms
- Configuring the Name of the Virtual Chassis Trace Log File
- Configuring Characteristics of the Virtual Chassis Trace Log File
- Configuring Access to the Virtual Chassis Trace Log File
- Using Regular Expressions to Refine the Output of the Virtual Chassis Trace Log File
- Configuring the Virtual Chassis Operations to Trace
- play_arrow Configuration Statements and Operational Commands
How to Use Sequential Upgrade in an MX Series Virtual Chassis
Sequential Upgrade Overview
Starting in Junos OS Release 20.1R1, MX Series Virtual Chassis configurations can use sequential upgrade to install new software releases with minimal network downtime. The sequential upgrade process is an alternative to unified in-service software upgrade (ISSU) that installs a new release and reboots each Virtual Chassis member router one at a time. While the upgrade installs on one member router, the other member router continues to operate and handle network operations. This lets you upgrade to a new release with minimal disruption to the network.
Use this document to learn about sequential upgrade, how it works, and how to initiate an sequential upgrade on MX Series Virtual Chassis configurations.
Benefits of Performing a Sequential Upgrade in a MX Series Virtual Chassis
Performing a sequential upgrade in an MX Series Virtual Chassis provides the following benefits:
Upgrades the Junos OS software package while maintaining subscriber sessions
Minimizes network downtime during software image upgrades
Avoids upgrading all Flexible PIC Concentrators (FPCs) and both chassis and at the same time
Sequential upgrade is an alternative to unified ISSU. Compared to ISSU, sequential upgrade offers the following benefits:
Easier troubleshooting. Sequential upgrade applies the upgrade to the backup router first, giving you a window to check on the success of the upgrade and troubleshoot if necessary
Ability to back out of an upgrade. With sequential upgrade, you can issue the
request virtual-chassis upgrade cancelcommand after the backup router is upgraded, giving you the flexibility to back out of an upgrade and roll back to the original software versionLower resource requirements for sequential upgrade
Prerequisites for Performing a Sequential Upgrade in a MX Series Virtual Chassis
Before you start a sequential upgrade in a two-member MX Series Virtual Chassis, make sure you do all of the following:
Ensure that all four Routing Engines in the Virtual Chassis (both Routing Engines in the primary router and both Routing Engines in the backup router) are running the same Junos OS software release.
For minimum traffic disruption, make sure that both member routers are configured with symmetric network interface configurations so traffic can continue to run on all interfaces after switching from the primary router to the backup router.
Ensure that your network is configured to enable moving all traffic from one member router to the other.
Back up the existing router configuration.
Verify that both graceful Routing Engine switchover (GRES) and nonstop active routing (NSR) are enabled.
Disable load throttling with the
set system services resource-monitor no-load-throttlecommand. This will allow subscriber logins during the upgrade process.Download the software release package you want to upgrade to from Juniper’s website at https://support.juniper.net/support/downloads/
Performing a Sequential Upgrade in a MX Series Virtual Chassis
To perform a sequential upgrade in an MX Series Virtual Chassis, follow these steps:
If you want to cancel the sequential upgrade process,
you can issue the request virtual-chassis upgrade cancel command on any Routing Engine after the Virtual Chassis backup router
is updated and before the Virtual Chassis primary router is updated.
After canceling the upgrade process, use the request system software
rollback command to rollback to the previously installed package,
if necessary.
How Sequential Upgrade Works in a MX Series Virtual Chassis
At a high level, the software performs the following
actions after you issue the request virtual-chassis upgrade protocol-backup package-name command to upgrade to a new Junos OS
software release in a two-member Virtual Chassis configuration:
After upgrading the Virtual Chassis backup router, the
next step is to issue the request virtual-chassis upgrade protocol-master package-name command from the backup router CLI
to initiate the upgrade process on Virtual Chassis primary router.
The software performs the same actions as listed in steps 1-7 above,
but for the primary router Routing Engines. After the primary router
Routing Engines reboot, the software performs the following actions:
Switches the role of the Virtual Chassis backup router to become the Virtual Chassis primary router.
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to determine if a feature is supported on your platform.
