Description

This article explains a scenario where a QFX Virtual Chassis reports upgrade or switchover validation errors after an in-service software upgrade (ISSU) command is attempted.

Symptoms

  • A QFX Virtual Chassis may initially show that graceful switchover is ready:

 

{master:0}

user@switch> request chassis routing-engine master switch check

Switchover Ready

 

  • After attempting ISSU validation or an ISSU-related command, the operation may fail.

 

Example:

 

{master:0}

user@switch> request system software in-service-upgrade validate

ISSU: Validating Image

Fetching package ...

error: File does not exist: /var/root/validate

error: Couldn't retrieve package /var/root/validate

error: Failed to download package: /var/root/validate

error: aborting ISSU

error: ISSU Aborted

 

  • A subsequent switchover validation may report that the standby Routing Engine is not ready or that the other Routing Engine is not present:

 

{master:0}

user@switch> request chassis routing-engine master switch check

error: Failed to get kernel replication error information from Standby Routing Engine.

Standby Routing Engine is not ready for graceful switchover.

error: Command aborted. The other RE is not present.

 

  • In some cases, the upgrade attempt may also fail with a message similar to:

user@switch> request system software nonstop-upgrade force-host no-validate /var/tmp/<jinstall package.tgz>

error: Backup RE not running

Solution

 

For QFX Virtual Chassis environments, ISSU should not be used as the software upgrade method. Virtual Chassis software upgrades should be performed using Nonstop Software Upgrade (NSSU), if the platform and release path support NSSU. If NSSU is not supported or is not desirable for the specific upgrade path, use the manual QFX Virtual Chassis upgrade procedure.

In some cases, after ISSU is attempted on a Virtual Chassis, the backup Routing Engine or backup member may no longer be seen as ready for graceful switchover. This can result in errors during ISSU validation, NSSU validation, or Routing Engine switchover checks.

 

  • Do not use ISSU to upgrade a QFX Virtual Chassis.
  • First, confirm that the device is operating as a Virtual Chassis:

{master:0}

user@switch> show virtual-chassis status

  • Confirm the status of the routing engines:

{master:0}

user@switch> show chassis routing-engine

 

  • Confirm switchover and replication status:

{master:0}

user@switch> request chassis routing-engine master switch check

{master:0}

user@switch> show database-replication summary

{master:0}

user@switch> show task replication

{backup:1}

user@switch> show system switchover >>> only works from backup

 

  • If the Virtual Chassis and the target release path support NSSU, use NSSU:

{master:0}

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

 

  • For a two-member Virtual Chassis, ensure that no-split-detection is configured when required:

{master:0}

user@switch> configure

user@switch# set virtual-chassis no-split-detection

user@switch# commit

 

  • If NSSU is not supported for the current and target release combination, use the manual QFX Virtual Chassis upgrade procedure instead.

 > Upgrading Two-Member QFX Series Virtual Chassis | Juniper Networks

 

  • If ISSU was already attempted and the backup member is no longer ready for switchover, recover the backup member before retrying the supported upgrade method. In many cases, rebooting the backup member restores the expected standby/backup state:

 

{master:0}

user@switch> request system reboot member <backup-member-id>

 

  • After the backup member returns online, validate the Virtual Chassis state again:

 

{master:0}

user@switch> show virtual-chassis

{master:0}

user@switch> show chassis fpc

{master:0}

user@switch> request chassis routing-engine master switch check

{master:0}

user@switch> show database-replication summary

{master:0}

user@switch> show task replication

 

  • Once the Virtual Chassis is healthy, proceed with NSSU if supported, or use the manual QFX Virtual Chassis upgrade procedure.

Modification History

2026-06-05 : Article Created

Related Information

see >


Upgrading Two-Member QFX Series Virtual Chassis | Juniper Networks