The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Cisco ASR 1000 Series Aggregation Services Routers support In-Service Software Upgrades (ISSU) procedure to upgrade software. The ISSU-using-install-cmds-for-ASR1k feature introduces a new method of software upgrade process by using the install command for Dual RP and Dual IOS routers on Cisco ASR 1000 Series Aggregation Services Routers.
Configure Stateful Switchover (SSO) and ensure that the standby supervisor is in the hot state.
Enable autoboot when using the install command so that the device is automatically reloaded with the configuration registry using the boot system command.
Simultaneous upgrade of hardware and software is not supported. One upgrade operation can only be performed at a time.
Minimum Disruptive Restart (MDR) and linecard-delay functionality are not supported on for consolidated platforms.
Effective with Cisco IOS XE Fuji 16.7.1, a new method of software upgrade process is available for Cisco ASR 1000 Aggregation Services Routers. You can use the install command for Dual RP and Dual IOS routers on Cisco ASR 1000 Series Routers by enabling the ISSU-using-install-cmds-for-ASR1k feature. This feature upgrades the software without files names for Dual RP and Dual IOS routers thereby enhancing the system to intelligently handle packages for Dual RP and Dual IOS routers in the Cisco ASR 1000 Series family. This feature also enables each model in the Cisco ASR 1000 Series to handle packages depending on the slot type and uses APIs to provision and identify ELC, SIP, and ESP on the devices.
When performing software process upgrade for consolidated platforms (Cisco ASR 1001-X Router, Cisco ASR 1001-HX Router, Cisco ASR 1002-X Router, and Cisco ASR 1002-HX Router), you can defer the RP upgrade as the last step to a maintenance window to minimize disruption during normal operating hours.
The ISSU-using-install-cmds-for-ASR1k feature includes the following software upgrade modes:
Super Package install—Applicable to Dual RP
Sub-package install—Applicable to Dual RP
Sub-package install—Applicable to 4RU or consolidated platforms on Dual IOSD
Depending on the choice of commands, there are different options to upgrade the software for each of the above mode on CIsco ASR 1000 Series. The ways to upgrade the software are as follows:
Super Package Upgrade—Step-by-step
Super Package Upgrade—One step
Sub Package Upgrade—Step-by-step
Sub Package Upgrade—One step
Dual IOSD
The following table provides information about the number of workflows for Dual RP and Dual IOS devices onn Cisco ASR 1000 Series Routers.
|
Cisco ASR 1000 Device Type |
Image Mode |
Workflows |
|---|---|---|
|
Dual RP |
Consolidated |
|
|
Dual RP |
Subpackage |
|
|
Dual IOS |
Subpackage |
|
Perform software upgrade process during a maintenance window.
Do not enable new features during software upgrade process because new features might require change in configurations.
Super package upgrade can be performed either in a single step or multiple steps. The sequence is as follows:
Copy image to standby RP.
Load a new software version on standby RP.
Wait for the standby RP to be active with the new software.
Run version on the active RP. This switches over the active RP, thereby running the new software on the new active RP while the new standby RP has the old software.
Perform upgrades during a maintenance window.
Restart the new standby to be up with new software.
The following table provides information about the commands used for super package upgrade process before and after Cisco IOS XE Fuji 16.7.1.
|
ISSU Command Before Cisco IOS XE Fuji 16.7.1 |
ISSU Command After Cisco IOS XE Fuji 16.7.1 |
|---|---|
|
copy tftp: URL-to-target-location |
install add file tftp/ftp/flash/disk:*.bin |
|
issu loadversion rp 1 file stby-harddisk: target image |
install activate location standby |
|
issu runversion |
redundancy force-switchover |
|
issu acceptversion |
install abort-timer stop |
|
issu commitversion |
Not required |
|
hw-module slot R0 reload |
Not required |
|
Not applicable |
install activate location standby |
|
Not applicable |
install commit |
|
ISSU Command Before Cisco IOS XE Fuji 16.7.1 |
ISSU Command After Cisco IOS XE Fuji 16.7.1 |
|---|---|
|
request platform software package install node file bootflash [interface-module-delay [mdr]] |
install add file tftp/ftp/flash/disk:*.bin activate issu [linecard-delay seconds] commit |
|
Work Flow # |
Use Case |
|---|---|
|
3-Step |
This workflow involves three steps—add, activate, and commit. After activation, all cards are upgraded to new software version except that the software is not committed automatically but must be performed manually via the install commit command. The advantage of this approach is the system can be rolled back to a previous software version. The system automatically rolls back if the roll back timer is not stopped using the install abort-timer-stop command. If the roll back timer is stopped, the new software version could be run on the device for any duration and then roll back to the previous version. The upgrade time is faster because this workflow involves two reloads only. |
|
5-Step |
There are three reloads involved in this workflow. In this workflow, the upgraded software is available on the active RP for sometime allowing you to validate the software before committing the upgrade. In addition to this the rollback to previous version is much faster because there is already an earlier version of the software on the standby RP. |
|
1-Step |
This workflow helps in optimization and saving a reload. You cannot roll back as the upgrade is committed automatically. |
The subpackage upgrade can be performed in either a single step or using multiple steps. This document discusses both methodologies. The sequence for a subpackage upgrade is as follows:
The following table provides information about different commands used for super package upgrade before and after Cisco IOS XE Fuji 16.7.1.
|
ISSU Command Before Cisco IOS XE Fuji 16.7.1 |
ISSU Command After Cisco IOS XE Fuji 16.7.1 |
|---|---|
|
show version show version active-rp installed dir filesystem: directory show platform show redundancy-states |
Similar |
|
copy running-configuration startup-configuration |
Similar |
|
mkdir URL-to-directory-name |
Not required |
|
copy tftp: URL-to-target-location |
Not required |
|
request platform software package expand file URL-to-consolidated-package |
install add tftp/ftp/flash/disk:*.bin |
|
dir URL-to-consolidated-package |
Not required |
|
copy tftp: URL-to-target-location |
install add tftp/ftp/flash/disk:*.bin |
|
issu loadversion rp standby-RP file URL-to-standby-file-system: asr1000rp* version *.pkg force |
install activate location standby |
|
hw-module slot standby-RP reload |
Not required. Optionally, use the install activate location standby command. |
|
issu loadversion rp active-RP file URL-to-active-file-system: asr1000rpx6-{sipbase,sipspa}* version *.pkg slot SIP-slot-number force |
install activate locationslot |
|
issu loadversion rp active-RP file URL-to-active-file-system:asr1000rpx86-{elcbase,elcspa}* version *.pkg slot ELC-slot-number force |
install activate locationslot |
|
issu commitversion |
Not required. Optionally, use the install auto abort-time stop command. |
|
issu loadversion rp active-RP file URL-to-active-file-system : asr1000rp2-esp* version *.pkg slot active-ESP-slot |
install activate location esp standby |
|
issu commitversion |
Not required. Optionally, use the install auto abort-time stop command. |
|
issu loadversion rp active-RP file URL-to-active-file-system : asr1000rp2-esp* version *.pkg slot active-ESP-slot |
install activate location esp active |
|
issu commitversion |
Not required. Optionally, use the install auto abort-time stop command. |
|
Not applicable. |
redundancy force-switchover |
|
issu loadversion rp active-RP file URL-to-active-file-system:asr1000rp2* version *.pkg force |
install activate location standby (triggers action per redundancy force-switchover command) |
|
issu commitversion |
install commit |
|
show version active-RPprovisioned show version active-RPinstalled |
Similar |
|
redundancy force-switchover |
Not required because it has been executed earlier. |
|
request platform software package clean |
Not required. Included in the install commit command. |
|
Work Flow # |
Use Case |
|---|---|
|
3-Step |
This workflow involves three steps—add, activate, and commit. After activation, all cards are upgraded to new software version except that the software is not committed automatically but must be performed manually through the install commit command. The advantage of this approach is the system can be rolled back to a previous software version. The system automatically rolls back if the roll back timer is not stopped using the install abort-timer-stop command. If the roll back timer is stopped, the new software version could be run on the device for any duration and then roll back to the previous version. The upgrade time is faster because this workflow involves two reloads only. |
|
8-Step |
There are three reloads involved in this workflow. In this workflow, the upgraded software is available on the active RP for sometime allowing you to validate the software before committing the upgrade. In addition to this the rollback to previous version is much faster as we have already previous version of the software running as standby RP. |
|
1-Step |
This workflow helps in optimization and saving a reload. You cannot roll back as the upgrade is committed automatically. |
If a device crashes during an ISSU upgrade, the device will return to the initial state before the start of an ISSU operation. During an ISSU upgrade, a single fault scenario is handled and system is restored to the original state. The double faults may or may not restore the system back to the original state.
The system can be rolled back before a commit.A device can be rolled back to the initial stage by using the install abort issu command or after the expiry of the rollback timer before the install commit command is used. If the install commit command is used, no rollback is allowed. Rollback involves the following steps:
If the roll back timer is not stopped by using the install abort stop-timer command, the device rolls back to an older software version on expiry of the rollback timer. The default value of the rollback timer is 120 minutes.
The rollback timer value can be set via the install activate location standby auto-abort-timer seconds command.
The Install: Auto Upgrade for ASR1k feature detects mismatched software versions on the standby route processor (RP) and synchronizes the software version on the standby route processor with active route processor. The synchronization occurs by copying the software version from the active RP to the standby RP and upgrading the software version on the standby RP.
This feature is enabled by default. If disabled, you can enable this feature through software auto-upgrade enable or install autoupgrade commands in the global configuration mode and privileged EXEC mode, respectively.
Auto upgrade works in subpackage mode only. If the device is in bundle mode, neither does auto upgrade work, nor can you execute the install autoupgrade command. If a route processor with bundle boot image is added to a modular device, the route processor is converted to install mode to synchronize with the active RP.
 Note |
When a standby RP has a software version different than the active RP, the standby RP is synchronized with the software on active RP even if the software version on standby RP is newer than the software on active RP. |
By enabling the install autoupgrade command in privileged EXEC mode the older image is selected and deleted without any intervention. The Install: Auto Upgrade for ASR1k feature is independent of ISSU and is disabled during ISSU process because there would be a temporary state of version mismatch between the active and standby RPs when ISSU process is in progress. Similarly, when auto upgrade is performed on the standby RP, ISSU process cannot triggered. The two processes are mutually exclusive.
After ISSU process is complete, auto upgrade is reenabled as configured before the ISSU process. In other words, this feature disables itself during ISSU process and reactivates itself after ISSU process.
The device must be booted with the consolidated image.
| Command or Action | Purpose | |||
|---|---|---|---|---|
| Step 1 |
enable Example: |
Enables privileged EXEC mode.
|
||
| Step 2 |
install add file {bootflash: | flash: | ftp: | http: | https: | rcp: | scp: | tftp: | webui: } Example: |
Downloads the image into the bootflash. The image is copied to the boot directory (boot_dir), the location where Route Processors (RPs) are booted. |
||
| Step 3 |
install activate issu [linecard-delay seconds ] Example: |
Provisions the standby RP with the new software and reloads with the new software version.
|
||
| Step 4 |
install commit Example: |
Saves the configuration, performs the necessary clean up, enables the new software as permanent (removing the older version of the software) and stops the rollback timer.
|
Perform this task to upgrade the software on consolidated platforms, such as, Cisco ASR 1001-X Router, Cisco ASR 1001-HX Router, Cisco ASR 1002-X Router, and Cisco ASR 1002-HX Router.
The device must be booted with the consolidated image.
| Command or Action | Purpose | |||
|---|---|---|---|---|
| Step 1 |
enable Example: |
Enables privileged EXEC mode.
|
||
| Step 2 |
install add file {bootflash: | flash: | ftp: | http: | https: | rcp: | scp: | tftp: | webui: } Example: |
Downloads the image into the bootflash. The image is copied to the boot directory (boot_dir), the location where Route Processors (RPs) are booted. |
||
| Step 3 |
install activate location standby Example: |
Installs the software on the standby RP and reloads the device.
|
||
| Step 4 |
redundancy force-switchover Example: |
Enables the standby RP to assume the role of the active RP. |
||
| Step 5 |
install activate location standby Example: |
Installs the software on the standby RP and reloads the device.
|
||
| Step 6 |
install commit Example: |
Saves the configuration, performs the necessary clean up, enables the new software as permanent (removing the older version of the software) and stops the rollback timer.
|
Perform this task to upgrade the software on consolidated platforms, such as, Cisco ASR 1001-X Router, Cisco ASR 1001-HX Router, Cisco ASR 1002-X Router, and Cisco ASR 1002-HX Router.
The device must be booted with the consolidated image.
| Command or Action | Purpose | |
|---|---|---|
| Step 1 |
enable Example: |
Enables privileged EXEC mode.
|
| Step 2 |
install add file {bootflash: | flash: | ftp: | http: | https: | rcp: | scp: | tftp: | webui: } activate issu [linecard-delay seconds ] commit Example: |
Enables the standby RP with new software and triggers the standby RP to become active RP with new software version.
|
Perform this task to upgrade the software on Dual RP devices.
The device must be booted with the consolidated image.
| Command or Action | Purpose | |||
|---|---|---|---|---|
| Step 1 |
enable Example: |
Enables privileged EXEC mode.
|
||
| Step 2 |
install add file {bootflash: | flash: | ftp: | http: | https: | rcp: | scp: | tftp: | webui: } Example: |
Downloads the image into the bootflash. The image is copied to the boot directory (boot_dir), the location where Route Processors (RPs) are booted. |
||
| Step 3 |
install activate issu [linecard-delay seconds ] Example: |
Provisions the standby RP with the new software and reloads with the new software version.
|
||
| Step 4 |
install commit Example: |
Saves the configuration, performs the necessary clean up, enables the new software as permanent (removing the older version of the software) and stops the rollback timer.
|
Perform this task to upgrade the software on Dual RP devices.
The device must be booted with the packages mode.
| Command or Action | Purpose | |||
|---|---|---|---|---|
| Step 1 |
enable Example: |
Enables privileged EXEC mode.
|
||
| Step 2 |
install add file {bootflash: | flash: | ftp: | http: | https: | rcp: | scp: | tftp: | webui: } Example: |
Downloads the image into the bootflash. The image is copied to the boot directory (boot_dir), the location where Route Processors (RPs) are booted. |
||
| Step 3 |
install activate location standby Example: |
Installs the software on the standby RP and reloads the device.
|
||
| Step 4 |
install activate location linecard [linecard-delay seconds ] Example: |
Installs the software on the standby RP and makes the new software as permanent. Any reboot after the commit will boot with new software.
|
||
| Step 5 |
install activate location esp standby Example: |
Loads the standby embedded services processors (ESP) cards with the packages.
|
||
| Step 6 |
install activate location esp active Example: |
Loads the active embedded services processors (ESP) cards with the packages.
|
||
| Step 7 |
redundancy force-switchover Example: |
Enables the standby RP to assume the role of the active RP. |
||
| Step 8 |
install activate location standby Example: |
Installs the software on the standby RP and reloads the device.
|
||
| Step 9 |
install commit Example: |
Saves the configuration, performs the necessary clean up, enables the new software as permanent (removing the older version of the software) and stops the rollback timer.
|
Perform this task to upgrade the software on Dual RP devices.
The device must be booted with the consolidated image.
| Command or Action | Purpose | |
|---|---|---|
| Step 1 |
enable Example: |
Enables privileged EXEC mode.
|
| Step 2 |
install add file {bootflash: | flash: | ftp: | http: | https: | rcp: | scp: | tftp: | webui: } activate issu [linecard-delay seconds ] commit Example: |
Enables the standby RP with new software and triggers the standby RP to become active RP with new software version.
|
Perform this task to upgrade the software on Cisco ASR 1001-X Router, Cisco ASR 1001-HX Router, Cisco ASR 1002-X Router, and Cisco ASR 1002-HX Router.
Note |
Perform this task during maintenance window to minimize the traffic loss. Cisco ASR 1001-X Router and Cisco ASR 1002-X Router has sipspa and sipbase, while Cisco ASR 1001-HX Router and Cisco 1002-HX Router has elcbase elcspa. |
Cisco ASR 1001-HX Router and Cisco ASR 1002-HX Router must be booted with the consolidated image.
| Command or Action | Purpose | |||
|---|---|---|---|---|
| Step 1 |
enable Example: |
Enables privileged EXEC mode.
|
||
| Step 2 |
install add file {bootflash: | flash: | ftp: | http: | https: | rcp: | scp: | tftp: | webui: } Example: |
Downloads the image into the bootflash. The image is copied to the boot directory (boot_dir), the location where Route Processors (RPs) are booted. |
||
| Step 3 |
install activate location standby Example: |
Installs the software on the standby RP and reloads the device.
|
||
| Step 4 |
redundancy force-switchover Example: |
Enables the standby RP to assume the role of the active RP.
|
||
| Step 5 |
install activate location standby Example: |
Installs the software on the standby RP and reloads the device.
|
||
| Step 6 |
install commit Example: |
Saves the configuration, performs the necessary clean up, enables the new software as permanent (removing the older version of the software) and stops the rollback timer.
|
Perform this task to upgrade the software on Cisco ASR 1004 Router.
Note |
Perform this task during maintenance window to minimize the traffic loss. |
The device must be booted with the consolidated image.
| Command or Action | Purpose | |||
|---|---|---|---|---|
| Step 1 |
enable Example: |
Enables privileged EXEC mode.
|
||
| Step 2 |
install add file {bootflash: | flash: | ftp: | http: | https: | rcp: | scp: | tftp: | webui: } Example: |
Downloads the image into the bootflash. The image is copied to the boot directory (boot_dir), the location where Route Processors (RPs) are booted. |
||
| Step 3 |
install activate location standby Example: |
Installs the software on the standby RP and reloads the device.
|
||
| Step 4 |
redundancy force-switchover Example: |
Enables the standby RP to assume the role of the active RP.
|
||
| Step 5 |
install activate location standby Example: |
Installs the software on the standby RP and reloads the device.
|
||
| Step 6 |
install activate location [linecard slot ] Example: |
Upgrades SPA interface processor (SIP) and shared port adapter (SPA), Ethernet line card (ELC) and SPA subpackages for each SIP or ELC on the device.
|
||
| Step 7 |
install activate location esp active Example: |
Loads the active embedded services processors (ESP) cards with the packages. The following message appears:
|
||
| Step 8 |
install commit Example: |
Saves the configuration, performs the necessary clean up, enables the new software as permanent (removing the older version of the software) and stops the rollback timer.
|
The ISSU progress can be tracked via the show issu state detail command. This command also displays the remaining duration in rollback timer. The following is a sample output of the show issu state detail command.
Device# show issu state detail
--- Starting local lock acquisition on R1 ---
Finished local lock acquisition on R1
Operation type: One-shot ISSU
Install type : Image installation using ISSU
Current state : Activated state
Last operation: Commit
Completed operations:
Operation Start time
-------------------------------------------------------
Activate location standby R1 2017-09-28:11:37:29
Activate location active R0 2017-09-28:11:43:30
Switchover 2017-09-28:11:45:09
Commit 2017-09-28:11:51:25
State transition: Added -> Standby activated -> Active switched-over -> Activated
Auto abort timer: inactive
Running image: flash:packages.conf
Operating mode: sso, terminal state reached
| Command or Action | Purpose | |
|---|---|---|
| Step 1 |
enable Example: |
Enables privileged EXEC mode.
|
| Step 2 |
install autoupgrade Example: |
Initiates autoupgrades on all standy RPs. |
| Command or Action | Purpose | |
|---|---|---|
| Step 1 |
enable Example: |
Enables privileged EXEC mode.
|
| Step 2 |
configure terminal Example: |
Enters global configuration mode. |
| Step 3 |
software auto-upgrade Example: |
Enables auto upgrade and specifies the location of the software to install during auto upgrade. |
| Step 4 |
end Example: |
Exits global configuration mode and returns to privileged EXEC mode. |
|
Related Topic |
Document Title |
|---|---|
|
Cisco IOS commands |
http://www.cisco.com/en/US/docs/ios/mcl/allreleasemcl/all_book.html |
|
Description |
Link |
|---|---|
|
The Cisco Support and Documentation website provides online resources to download documentation, software, and tools. Use these resources to install and configure the software and to troubleshoot and resolve technical issues with Cisco products and technologies. Access to most tools on the Cisco Support and Documentation website requires a Cisco.com user ID and password. |
The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.|
Feature Name |
Releases |
Feature Information |
|---|---|---|
|
Install: Auto Upgrade for ASR1k |
Cisco IOS XE Fuji 16.8.1 |
The Install: Auto Upgrade for ASR1k feature detects mismatched software versions on the remote standby route processor (RP) and synchronizes the software version on the standby route processor with active route processor. The following commands were introduced or modified: install autoupgrade, software auto-upgrade. |
|
ISSU-using-install-cmds-for-ASR1k |
Cisco IOS XE Fuji 16.7.1 |
Cisco ASR 1000 Series Aggregation Services Routers supports In-Service Software Upgrades (ISSU) procedure to upgrade software. The ISSU-using-install-cmds-for-ASR1k feature introduces a new method of software upgrade process by using the install command for Dual RP and Dual IOS routers on Cisco ASR 1000 Series Aggregation Services Routers. The following commands were introduced or modified: install activate issu, install activate location esp active, install activate location esp standby, install activate location linecard, install activate location standby, install add file, install commit, redundancy force-switchover, show issu comp-matrix, show issu rollback-timer, showissu state detail, show platform, show redundancy, show version . |
Feedback