request vmhost software in-service-upgrade
语法
request vmhost software in-service-upgrade package-name < no-old-master-upgrade> < reboot> < verbose>
描述
执行统一不中断服务的软件升级 (ISSU)。统一的 ISSU 使您能够从一个 Junos OS 版本和主机操作系统版本升级到另一个版本,而不会中断控制平面,并将流量中断降至最低。对于统一的 ISSU,必须启用平滑路由引擎切换 (GRES) 和不间断活动路由 (NSR)。
从 Junos OS 18.2R1 版开始,MX10003 路由器支持使用命令进行 request vmhost software in-service-upgrade
统一不中断服务的软件升级 (ISSU)。MX10003 不支持使用 请求系统软件不中断服务升级 命令升级仅 Junos OS 映像。
在MX10003路由器上:
MACsec MIC (JNP-MIC1-MACSEC) 不支持 ISSU。
配置了 1 千兆以太网模式的接口不支持 ISSU。如果在 1 千兆以太网模式下执行 ISSU 升级,则行为是意外的,并且可能会丢失流量。
计时协议(如精确时间协议和同步以太网)、MACsec 协议和 BBE 协议不支持 ISSU。如果已启用这些协议,则在启用 ISSU 后它将不起作用。
MAC 统计信息(使用 show interfaces broad 命令检索)在 ISSU 期间重置,这意味着 MAC 统计信息在 ISSU 之后不会提供正确的统计信息。
选项
package-name | 要从中安装软件包或捆绑包的位置。例如:
|
no-old-master-upgrade | (可选)如果包含该 |
reboot | (可选)在 ISSU 之后自动重新启动前主(新备份)路由引擎。如果未在命令中包含该 |
verbose | (可选)(MX 系列)使用此选项可在升级期间显示守护程序相关信息。 |
其他信息
以下条件适用于统一 ISSU:
并非每个平台都支持统一 ISSU。有关受支持平台的列表,请参阅 统一 ISSU 系统要求。
在某些路由设备上的统一 ISSU 期间,不受支持的 PIC 会重新启动。
在统一 ISSU 期间,设备上运行的任何不受支持的协议都会导致数据包丢失。
在统一 ISSU 期间,您无法在某些路由设备上使任何 PIC 联机或使其脱机。
所需权限级别
维护
示例输出
请求 VMhost 软件不中断服务升级
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. ... ...
示例输出
详细请求 VMhost 软件不中断服务升级
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 ... ...
发布信息
在 Junos OS 15.1F3 版中引入的命令。
Junos OS 18.2R1 版中为 MX 系列路由器引入的选项。
PTX3000路由器支持路由和控制板 RCBPTX。