![Cisco ASR1002 - ASR 1002 Router Скачать руководство пользователя страница 85](http://html.mh-extra.com/html/cisco/asr1002-asr-1002-router/asr1002-asr-1002-router_software-configuration-manual_66731085.webp)
Software Upgrade Process
ISSU Upgrade for Redundant Platforms
3
Cisco ASR 1000 Series Aggregation Services Routers Software Configuration Guide
upgrade. The SPA and SIP software subpackages must be upgraded on a per-SPA or per-SIP basis. See
Table 11
to view an In Service table that addresses the contexts where limited interruption upgrades can
be performed.
If you are updating multiple subpackages, you should also realize that the sequence of the upgrade is
important to minimize router downtime for the software upgrade (see the
“Using ISSU to Upgrade
SubPackages (Prior to Cisco IOS XE Release 2.1.2)” section on page 75
).
The specific procedures in this document represent supported and tested installation sequences. The
Cisco IOS XE system software allows other installation sequences for special purposes under the
guidance of Cisco customer support representatives, but the steps in this document should be followed
otherwise. These steps should be followed completely, as the Cisco ASR 1000 Series Routers are
designed to run one version of Cisco IOS XE for all consolidated packages and subpackages on an RP,
and running subpackages from different versions of Cisco IOS XE can cause unexpected router behavior.
When performing ISSU upgrades on the Cisco ASR 1000 Series Routers, it is important to remember
that minimal interruption upgrades can be performed using either the
issu
command set or the
request
platform
command set, and that either command
set can be used to perform limited interruption
individual consolidated package or subpackage upgrades.
Note
ROMmon images are downloaded separately from Cisco IOS XE images and have their own installation
procedures, and are therefore not mentioned as part in this document as part of the ISSU upgrade
procedure.
Table 11
provides a list of the Cisco ASR 1000 Series Routers subpackages and whether or not they can
be upgraded without losing any network traffic in single and dual RP and ESP configurations using
ISSU.
Table 12
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
Yes
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)