4-3
Cisco ASR 1000 Series Aggregation Services Routers Software Configuration Guide
OL-16506-10
Chapter 4 Software Upgrade Process
ISSU Upgrade for Redundant Platforms
ISSU Rollback Timer Overview
The Cisco ASR 1000 Series Router ISSU procedure has a rollback timer. Rollback timers are used for
for ISSU procedures on all Cisco routers that support ISSU, but this section will provide a brief overview
of ISSU rollback timers on the Cisco ASR 1000 Series Routers.
During ISSU, the rollback timer begins after the consolidated package or subpackage is loaded. If the
upgrade does not move forward in the amount of time specified in the rollback timer, the configuration
will automatically “roll back” to the previous configuration and the ISSU upgrade will be cancelled.
Upgrades using the issu command set and the request platform command set both have the rollback
timer option. The issu command set always uses a rollback timer; the request platform command set
does not use a rollback timer unless the auto-rollback option is used in the request platform software
package install command line.
For the issu command set, the issu acceptversion command can be entered to stop the rollback timer
without committing the upgrade during the ISSU upgrade. The issu commitversion command can be
entered to stop the rollback timer and commit the ISSU upgrade.
For the request platform command set, the request platform software package install rp slot commit
command must be entered to stop the rollback timer only in cases where the auto-rollback option is
used.
The rollback timer for the issu command set can be configured by entering the issu set rollback-timer
command. The rollback timer when used with the request platform command set is specified when you
use the auto-rollback option when entering the issu request platform software package install
command.
For ISSU upgrades on Cisco ASR 1000 Series Routers, it may be advisable to set long rollback times
when the upgrade is being performed on routers with large configurations.
The amount of time left on the rollback timer during an ISSU upgrade can be checked by entering the
show issu rollback-timer command.
Ta b l e 4-2 Limited Interruption Upgrade Compatibility Table
SubPackage Nonredundant RP and ESP Redundant RP and ESP
Consolidated package (any) No (Reload required) Yes (RP switchover)
RPBase No (RP Reload required) Yes (RP switchover)
RPControl Yes (in-service) Yes (in-service)
RPAccess Yes (in-service) Yes (in-service)
RPIOS Ye s
1
(IOS software switchover)
1. Only supported if software redundancy is configured on the RP.
Yes (RP switchover)
ESPBase No
2
(ESP reload required)
2. ESP has to reload to complete ESPBase subpackage upgrade. All router traffic will be lost during ESP upgrade.
Yes
3
(via ESP switchover)
3. An ESP switchover occurs as part of the upgrade, so traffic is forwarded with minimal interruption.
SIPBase
4
4. Any SIPBase upgrade will require the SPA interfaces to go down during the upgrade for all the SPAs in the SIP.
No (SPAs in SIP do not forward
traffic during upgrade)
No (SPAs in SIP do not forward
traffic during upgrade)
SIPSPA
5
5. Any SIPSPA upgrade will require the SPA interfaces for that particular SPA to go down during the upgrade.
No (SPAs in SIP do not forward
traffic during upgrade)
No (SPAs in SIP do not forward
traffic during upgrade)