request vmhost software in-service-upgrade
Syntax
request vmhost software in-service-upgrade package-name < no-old-master-upgrade> < reboot> < verbose>
Description
Perform a unified in-service software upgrade (ISSU). A unified ISSU enables you to upgrade from one Junos OS release and host OS release to another with no disruption on the control plane and with minimal disruption of traffic. For an unified ISSU, graceful Routing Engine switchover (GRES) and nonstop active routing (NSR) must be enabled.
Starting inJunos OS Release 18.2R1, MX10003 routers support
unified in-service software upgrade (ISSU) using request vmhost
software in-service-upgrade command. MX10003 does not support
upgrading Junos OS only image using request
system software in-service-upgrade command.
On MX10003 routers:
ISSU is not supported on MACsec MIC (JNP-MIC1-MACSEC).
ISSU is not supported for the interfaces that are configured with 1-Gigabit Ethernet mode. If ISSU upgrade is carried out in 1-Gigabit Ethernet mode, then the behavior is unexpected and traffic loss can be expected.
ISSU is not supported on timing protocols (like, Precision Time Protocol and Synchronous Ethernet), MACsec protocols, and BBE protocols. If these protocols are already enabled, then it will not work after ISSU is enabled.
The MAC statistics (retrieved using show interfaces extensive command) are reset during ISSU which means that the MAC statistics does not provide the correct statistics after ISSU.
Options
| package-name | Location from which the software package or bundle is to be installed. For example:
|
| no-old-master-upgrade | (Optional) When the |
| reboot | (Optional) Automatically
reboot the former primary (new backup) Routing Engine after the ISSU.
If you don not include the |
| verbose | (Optional) (MX Series) Use this option to display the daemon related information during the upgrade. |
Additional Information
The following conditions apply to unified ISSU:
Unified ISSU is not supported on every platform. For a list of supported platforms, see Unified ISSU System Requirements.
Unsupported PICs are restarted during a unified ISSU on certain routing devices.
During a unified ISSU, any unsupported protocols running on the device causes packet loss.
During a unified ISSU, you cannot bring any PICs online or take them offline on certain routing devices.
Required Privilege Level
maintenance
Sample Output
request vmhost software in-service-upgrade
user@host> request vmhost software in-service-upgrade /var/tmp/junos-vmhost-install-ptx-x86-64-15.1F5.6.tgz reboot Chassis ISSU Check Done [Feb 24 01:12:09]: Starting VMHOST ISSU [Feb 24 01:12:09]:ISSU: Validating Image FPC 2 will be offlined (In-Service-Upgrade not supported) FPC 11 will be offlined (In-Service-Upgrade not supported) MIC 11/0 will be offlined (In-Service-Upgrade not supported) Do you want to continue with these actions being taken ? [yes,no] (no) yes Junos Validation begin. Procedure will take few minutes. ... ...
Sample Output
request vmhost software in-service-upgrade verbose
user@host> request vmhost software in-service-upgrade verbose
...
...
Oct 26 15:20:02 [INFO ] Verified py-extensions signed by PackageDevelopmentEc_2017 method ECDSA256+SHA256
Oct 26 15:20:02 [INFO ] Adding py-extensions-x86-32-20171024.002108_builder_release_174_throttle ...
Oct 26 15:20:02 [INFO ] Verified vrr-mx signed by PackageDevelopmentEc_2017 method ECDSA256+SHA256
Oct 26 15:20:02 [INFO ] NOTICE: 'pending' set will be activated at next reboot...
Oct 26 15:20:02 [INFO ] [Oct 26 02:36:10]:ISSU: Installing package /var/tmp/junos-install-mx-x86-64-17.4-20171024.0.tgz on re1 done
Oct 26 15:20:02 [INFO ] [Oct 26 02:36:10]:ISSU: Rebooting Backup RE
Oct 26 15:20:02 [INFO ]
Oct 26 15:20:02 [INFO ] Rebooting re1
Oct 26 15:20:02 [INFO ] [Oct 26 02:36:11]:ISSU: Backup RE Prepare Done
Oct 26 15:20:02 [INFO ] [Oct 26 02:36:11]:ISSU: Waiting for Backup RE reboot
Oct 26 15:20:02 [INFO ] [Oct 26 02:39:26]:ISSU: Backup RE reboot done. Backup RE is up
Oct 26 15:20:02 [INFO ] [Oct 26 02:39:26]:ISSU: Waiting for Backup RE state synchronization
Oct 26 15:20:02 [INFO ] [Oct 26 02:39:51]:ISSU: Backup RE state synchronization done
Oct 26 15:20:02 [INFO ] [Oct 26 02:39:51]:ISSU: GRES operational
Oct 26 15:20:02 [INFO ] [Oct 26 02:40:52]: "Initiating Chassis In-Service-Upgrade"
Oct 26 15:20:02 [INFO ] Chassis ISSU Started
Oct 26 15:20:02 [INFO ] [Oct 26 02:40:57]:ISSU: Preparing Daemons
Oct 26 15:20:02 [INFO ] [Oct 26 02:40:57]: Daemon [rpd] transitioned to READY state
Oct 26 15:20:02 [INFO ] [Oct 26 02:40:57]: Daemon [lfmd] transitioned to READY state
Oct 26 15:20:02 [INFO ] [Oct 26 02:40:57]: Daemon [l2cpd] transitioned to READY state
Oct 26 15:20:02 [INFO ] [Oct 26 02:40:57]: Daemon [smid] transitioned to READY state
Oct 26 15:20:02 [INFO ] [Oct 26 02:40:57]: Daemon [bfdd] transitioned to READY state
Oct 26 15:20:02 [INFO ] [Oct 26 02:41:17]:ISSU: Daemons Ready for ISSU
Oct 26 15:20:02 [INFO ] [Oct 26 02:41:17]: Daemon [apsd] transitioned to READY state
Oct 26 15:20:02 [INFO ] [Oct 26 02:41:22]:ISSU: Offline Incompatible FRUs
Oct 26 15:20:02 [INFO ] [Oct 26 02:41:27]:ISSU: Starting Upgrade for FRUs
Oct 26 15:20:02 [INFO ] [Oct 26 02:41:27]: [FPC 1] None -> Prepare
Oct 26 15:20:02 [INFO ] [Oct 26 02:41:48]: [FPC 1] Prepare -> Ready for Reboot
Oct 26 15:20:02 [INFO ] [Oct 26 02:41:52]: [FPC 1] Ready for Reboot -> Reboot
Oct 26 15:20:02 [INFO ] [Oct 26 02:42:01]: [FPC 1] Reboot -> Blob Resync
Oct 26 15:20:02 [INFO ] [Oct 26 02:42:28]: [FPC 1] Blob Resync -> Ready Software State Sync
Oct 26 15:20:02 [INFO ] [Oct 26 02:42:32]: [FPC 1] Ready Software State Sync -> Software State Sync
Oct 26 15:20:02 [INFO ] [Oct 26 02:44:02]: [FPC 1] Software State Sync -> Ready Hardware State Sync
Oct 26 15:20:02 [INFO ] [Oct 26 02:44:02]: [FPC 1] Ready Hardware State Sync -> Hardware State Sync
Oct 26 15:20:02 [INFO ] [Oct 26 02:47:07]: [FPC 1] Hardware State Sync -> Reconnected
Oct 26 15:20:02 [INFO ] [Oct 26 02:47:07]:ISSU: FRU Upgrade Done
Oct 26 15:20:02 [INFO ] [Oct 26 02:47:07]:ISSU: Preparing for Switchover
Oct 26 15:20:02 [INFO ] [Oct 26 02:47:07]: Daemon [lfmd] transitioned to SWITCHOVER_READY state
Oct 26 15:20:02 [INFO ] [Oct 26 02:47:07]: Daemon [rpd] transitioned to SWITCHOVER_READY state
Oct 26 15:20:02 [INFO ] [Oct 26 02:47:07]: Daemon [l2cpd] transitioned to SWITCHOVER_READY state
Oct 26 15:20:02 [INFO ] [Oct 26 02:47:07]: Daemon [smid] transitioned to SWITCHOVER_READY state
Oct 26 15:20:02 [INFO ] [Oct 26 02:47:07]: Daemon [bfdd] transitioned to SWITCHOVER_READY state
Oct 26 15:20:02 [INFO ] [Oct 26 02:47:27]: Daemon [apsd] transitioned to SWITCHOVER_READY state
Oct 26 15:20:02 [INFO ] [Oct 26 02:47:29]: Checking In-Service-Upgrade status
Oct 26 15:20:02 [INFO ] Item Status Reason
Oct 26 15:20:02 [INFO ] FPC 1 Online (ISSU)
Oct 26 15:20:02 [INFO ] Resolving mastership...
Oct 26 15:20:02 [INFO ] Complete. The other routing engine becomes the master.
Oct 26 15:20:02 [INFO ] [Oct 26 02:47:30]:ISSU: RE switchover Done
Oct 26 15:20:02 [INFO ] [Oct 26 02:47:30]:ISSU: Upgrading Old Master RE
Oct 26 15:20:02 [INFO ] Verified junos-install-mx-x86-64-17.4-20171024.0 signed by PackageDevelopmentEc_2017 method ECDSA256+SHA256
Oct 26 15:20:02 [INFO ] Verified manifest signed by PackageDevelopmentEc_2017 method ECDSA256+SHA256
...
...
Release Information
Command introduced in Junos OS Release 15.1F3.
Option introduced in Junos OS Release 18.2R1 for the MX Series routers.
PTX3000 router supports the Routing and Control Board, RCBPTX.