When you issue the request system software in-service-upgrade command with the no-old-master-upgrade option, the system upgrades and reboots only the new master Routing Engine. To upgrade the new backup (former master) Routing Engine, you must issue the request system software add command.
To perform a unified ISSU using the request system software in-service-upgrade package-name no-old-master-upgrade commands, complete the following steps:
user@host>file copy ftp://username:prompt@ftp.hostname.net/filename/var/tmp/filename
{backup}
user@host> show version invoke-on all-routing-engines
re0: -------------------------------------------------------------------------- Hostname: host Model: m320 JUNOS Base OS boot [9.0-20071211.2] JUNOS Base OS Software Suite 9.0-20071211.2] JUNOS Kernel Software Suite [9.0-20071211.2] JUNOS Crypto Software Suite [9.0-20071211.2] JUNOS Packet Forwarding Engine Support (M/T Common) [9.0-20071211.2] JUNOS Packet Forwarding Engine Support (M320) [9.0-20071211.2] JUNOS Online Documentation [9.0-20071211.2] JUNOS Routing Software Suite [9.0-20071211.2] re1: -------------------------------------------------------------------------- Hostname: host1 Model: m320 JUNOS Base OS boot [9.0-20071211.2] JUNOS Base OS Software Suite [9.0-20071211.2] JUNOS Kernel Software Suite [9.0-20071211.20] JUNOS Crypto Software Suite [9.0-20071211.2] JUNOS Packet Forwarding Engine Support (M/T Common) [9.0-20071211.2] JUNOS Packet Forwarding Engine Support (M320) [9.0-20071211.2] JUNOS Online Documentation [9.0-20071211.2] JUNOS Routing Software Suite [9.0-20071211.2]
{master}
user@host> request system software in-service-upgrade
/var/tmp/jinstall-9.0-20080116.2-domestic-signed.tgz no-old-master-upgrade
ISSU: Validating Image
ISSU: Preparing Backup RE
Pushing bundle to re1
Checking compatibility with configuration
Initializing...
Using jbase-9.0-20080116.2
Verified manifest signed by PackageProduction_9_0_0
Using /var/tmp/jinstall-9.0-20080116.2-domestic-signed.tgz
Verified jinstall-9.0-20080116.2-domestic.tgz signed by PackageProduction_9_0_0
Using jinstall-9.0-20080116.2-domestic.tgz
Using jbundle-9.0-20080116.2-domestic.tgz
Checking jbundle requirements on /
Using jbase-9.0-20080116.2.tgz
Verified manifest signed by PackageProduction_9_0_0
Using jkernel-9.0-20080116.2.tgz
Verified manifest signed by PackageProduction_9_0_0
Using jcrypto-9.0-20080116.2.tgz
Verified manifest signed by PackageProduction_9_0_0
Using jpfe-9.0-20080116.2.tgz
Using jdocs-9.0-20080116.2.tgz
Verified manifest signed by PackageProduction_9_0_0
Using jroute-9.0-20080116.2.tgz
Verified manifest signed by PackageProduction_9_0_0
Hardware Database regeneration succeeded
Validating against /config/juniper.conf.gz
mgd: commit complete
Validation succeeded
Installing package '/var/tmp/jinstall-9.0-20080116.2-domestic-signed.tgz' ...
Verified jinstall-9.0-20080116.2-domestic.tgz signed by PackageProduction_9_0_0
Adding jinstall...
Verified manifest signed by PackageProduction_9_0_0
WARNING: This package will load JUNOS 9.0-20080116.2 software.
WARNING: It will save JUNOS configuration files, and SSH keys
WARNING: (if configured), but erase all other files and information
WARNING: stored on this machine. It will attempt to preserve dumps
WARNING: and log files, but this can not be guaranteed. This is the
WARNING: pre-installation stage and all the software is loaded when
WARNING: you reboot the system.
Saving the config files ...
NOTICE: uncommitted changes have been saved in /var/db/config/juniper.conf.pre-install
Installing the bootstrap installer ...
WARNING: A REBOOT IS REQUIRED TO LOAD THIS SOFTWARE CORRECTLY. Use the
WARNING: 'request system reboot' command when software installation is
WARNING: complete. To abort the installation, do not reboot your system,
WARNING: instead use the 'request system software delete jinstall'
WARNING: command as soon as this operation completes.
Saving package file in /var/sw/pkg/jinstall-9.0-20080116.2-domestic-signed.tgz ...
Saving state for rollback ...
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: Backup RE Prepare Done
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 Online (ISSU)
FPC 5 Online (ISSU)
Resolving mastership...
Complete. The other routing engine becomes the master.
ISSU: RE switchover Done
Skipping Old Master Upgrade
ISSU: IDLE
{backup}
user@host