Table Of Contents
Software Upgrade Processes Supported by Cisco ASR 1000 Series Aggregation Services Routers
Contents
Prerequisites for Software Upgrade Processes
ISSU Upgrade for Redundant Platforms
Overview of ISSU on the Cisco ASR 1000 Series Routers
ISSU Rollback Timer Overview
Software Upgrade with Dual IOS Processes on a Single RP Overview
Cisco IOS XE Software Package Compatibility for ISSU
Restrictions for ISSU
ISSU Upgrade Procedures
Using ISSU to Perform a Consolidated Package Upgrade in a Dual Route Processor Configuration
Using ISSU to Upgrade the SubPackages in a Dual Route Processor Configuration
In Service One-Shot Software Upgrade Procedure
ISSU Procedures (Prior to Cisco IOS XE Release 2.1.2)
Using ISSU to Perform a Consolidated Package Upgrade in a Dual Route Processor Configuration (Prior to Cisco IOS XE 2.1.2)
Using ISSU to Upgrade SubPackages (Prior to Cisco IOS XE Release 2.1.2)
Upgrade Process With Service Impact for Nonredundant Platforms
Configuring SSO on a Cisco ASR 1001, Cisco ASR 1002, or Cisco ASR 1004 Router
Using SubPackages for Software Upgrade on a Cisco ASR 1001 Router
Using SubPackages for Software Upgrade on a Cisco ASR 1002 or Cisco ASR 1004 Router (software upgrade Command Set)
Using SubPackages for Software Upgrade on a Cisco ASR 1002 or Cisco ASR 1004 Router (request platform Command Set)
Minimal Disruptive Restart Process
Restrictions and Limitations
High Availability Considerations
Additional References
Related Documents
Standards
MIBs
RFCs
Technical Assistance
Feature Information for Software Upgrade Process
Software Upgrade Processes Supported by Cisco ASR 1000 Series Aggregation Services Routers
Cisco ASR 1000 Series Aggregation Services Routers support the following software upgrade procedures:
•
In-Service Software Upgrades (ISSU) for redundant platforms—The ISSU process allows software to be updated or otherwise modified while packet forwarding continues with minimal interruption. ISSU supports two different software upgrade modes:
–
Consolidated package mode
–
Subpackage mode
The supported platforms include Cisco ASR 1006 and Cisco ASR 1013 Routers.
•
Upgrade process with service impact for nonredundant platforms—Non-hardware-redundant chassis models (such as the Cisco ASR 1001 Router, Cisco ASR 1002 Router and Cisco ASR 1004 Router) do not support ISSU upgrade or downgrade. Instead subpackage software upgrade is supported only if the router is running in subpackage mode.Traffic loss cannot be avoided during the installation of the ESP package as a part of ISSU.
Table 11 lists Compatibility matrix of the software upgrade process for various Cisco ASR 1000 Series Aggregation Services Router.
Table 11 Software Upgrade Compatibility Matrix for Various Cisco ASR 1000 Series Aggregation Services Router Platforms
Platform
|
Consolidated Package
|
SubPackage
|
Cisco ASR 1006 Router
|
Supported
|
Supported
|
CiscoASR 1013 Router
|
Supported
|
Supported
|
CiscoASR 1004 Router
|
Not Supported
|
Supported
|
CiscoASR 1002 Router
|
Not Supported
|
Supported
|
CiscoASR 1002-F Router
|
Not Supported
|
Supported
|
CiscoASR 1001 Router
|
Not Supported
|
Supported
|
Finding Feature Information in This Module
Your Cisco IOS software release may not support all of the features documented in this module. To reach links to specific feature documentation in this module and to see a list of the releases in which each feature is supported, use the "Feature Information for Software Upgrade Process" section.
Finding Support Information for Platforms and Cisco IOS and Catalyst OS Software Images
Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
This guide discusses various software upgrade procedures and contains the following sections:
•
Prerequisites for Software Upgrade Processes
•
ISSU Upgrade for Redundant Platforms
•
Upgrade Process With Service Impact for Nonredundant Platforms
•
Minimal Disruptive Restart Process
Prerequisites for Software Upgrade Processes
Be sure to complete the following prerequisites for running the ISSU process based on your chassis model:
•
Refer to the ISSU compatibility tables in the Release Notes for Cisco ASR 1000 Series Aggregation Services Routers.
•
4 GB of DRAM memory is required for installing software upgrade on a system with RP1 route processor.
•
ISSU is supported when the router is running in subpackage mode or in consolidated package mode.
•
For the Cisco ASR 1001 Router, the Cisco IOS Software redundancy requires 8-GB DRAM and the IOS software redundancy license.
ISSU Upgrade for Redundant Platforms
ISSU represent a full or partial software upgrade of a system from one version to another with minimal outage on the forwarding plane (minimal packet loss) and no outage on the control plane.
This section covers the following topics:
•
Overview of ISSU on the Cisco ASR 1000 Series Routers
•
ISSU Upgrade Procedures
•
In Service One-Shot Software Upgrade Procedure
•
ISSU Procedures (Prior to Cisco IOS XE Release 2.1.2)
Overview of ISSU on the Cisco ASR 1000 Series Routers
For the Cisco ASR 1000 Series Routers, ISSU-compatibility depends on the software subpackage being upgraded and the hardware configuration. Consolidated packages are ISSU-compatible in dual RP configurations only and have other limitations described later in this document. Some RP and ESP software subpackages can be upgraded in service even in single RP or ESP hardware configurations via dual IOS processes running on the RP; others require dual RP or ESP configurations for an ISSU 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).
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
|
Yes1 (IOS software switchover)
|
Yes (RP switchover)
|
ESPBase
|
No2 (ESP reload required)
|
Yes3 (via ESP switchover)
|
SIPBase4
|
No (SPAs in SIP do not forward traffic during upgrade)
|
No (SPAs in SIP do not forward traffic during upgrade)
|
SIPSPA5
|
No (SPAs in SIP do not forward traffic during upgrade)
|
No (SPAs in SIP do not forward traffic during upgrade)
|
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.
Software Upgrade with Dual IOS Processes on a Single RP Overview
To complete a software upgrade of an individual subpackage using dual IOS processes on a single RP, SSO must first be enabled.
Software upgrade with dual IOS processes is useful for upgrading the individual RP subpackages that can be upgraded without a router reload. See Table 11 for a list of these subpackages. Importantly, note that most subpackage upgrades in a single RP configuration require a hardware reload to complete (whether an RP reload for an RP subpackage, an ESP reload for the ESPBase subpackage, a SIP reload for a SIPBase subpackage, or a SPA reload for the SIPSPA subpackage), so limited interruption upgrades for single RP configurations are not available in most upgrade scenarios.
For information on configuring a second IOS process on a single RP, see the "Using SubPackages for Software Upgrade on a Cisco ASR 1002 or Cisco ASR 1004 Router (software upgrade Command Set)" section.
Cisco IOS XE Software Package Compatibility for ISSU
When upgrading the Cisco IOS XE operating system software using the ISSU process, it is important to determine the compatibility of the upgraded software to your current software and hardware. The ISSU process allows software to be updated or otherwise modified while packet forwarding continues with minimal interruption.
Cisco IOS XE release compatibility using the ISSU process utilizes the SSO functionality to preserve state while software versions on the router differ, as during an upgrade. Most SSO-capable features in each Cisco IOS XE release are ISSU capable. ISSU is only supported if SSO is enabled in the configuration and the system is in a steady state (SSO ready state has been achieved). ISSU compatibility depends on the set of specific feature clients that are in use and whether they support ISSU. All ISSU upgrades include at least one IOS switchover operation. It is important to understand which features are in use and whether these features are ISSU compatible.
Cisco ASR1006 or ASR 1013 series routers are hardware-redundant chassis. The hardware-redundant chassis has two ESP linecards and two RPs which exchange state using hardware links. The Cisco ASR1002 and ASR1004 Series Routers are not hardware redundant, but are software-redundancy capable. The nonredundant chassis has a single RP and a single ESP, but allows the operation of up to two IOS processes on the single RP to exchange states locally.
Restrictions for ISSU
Restrictions for the ISSU procedures include:
Note
Cisco IOS XE software compatibility is between "like" images, for example, advipservicesk9 to advipservicesk9, adventerprisek9 to adventerprisek9, and so on. Cross-image-type upgrades or installations are not supported in the ISSU process. For example, you cannot upgrade ipbase to advipservicesk9 or advipservices to advipservicesk9.
•
Different image types must not be run simultaneously.
•
For ATM SPAs on the Cisco ASR1000 Series Routers, ISSU from releases prior to Cisco IOS XE Release 2.5.0 to Cisco IOS XE Release 2.5.0, or from Cisco IOS XE Release 2.5.0 to a release prior to Cisco IOS XE Release 2.5.0, is not supported. If you want to perform ISSU in this environment, you must first remove the configuration from the ATM SPAs on the router, and then shut down the SPAs using the shutdown command prior to running the ISSU process.
•
Cisco IOS XE releases not listed as compatible in the ISSU compatibility tables (documented in the Release Notes for Cisco ASR 1000 Series Aggregation Services Routers as stated in the "Prerequisites for Software Upgrade Processes" section) must not be run simultaneously (in a Cisco ASR1006 series router or Cisco ASR 1013 series router) or co-installed on any of the Cisco ASR1000 Series Routers since unexpected failures of one or both RPs or state loss can be experienced. Cisco IOS XE releases listed as partially compatible may incur a loss of state. Cisco IOS XE releases listed as requiring an intermediate release are not directly compatible; however, a migration path is available to preserve some or all state by upgrading to a separate intermediate version, as shown in the tables. The tables do not cover nonredundant (software or hardware) environments as no incremental update is possible under those circumstances.
•
In Cisco IOS XE Release 3.1S, ISSU upgrade and subpackage software upgrade from Cisco IOS XE Release 2.x.x to Cisco IOS XE Release 3.x.xS, including release 3.1S, are not supported. The ISSU downgrade from Cisco IOS XE Release 3.x.xS, including release 3.1S to 2.x.x, is also not supported. ISSU upgrade and subpackage software upgrade is restarted from Cisco IOS XE Release 3.1S. Therefore, rebuilds and releases after Cisco IOS XE Release 3.1S will support ISSU and software upgrade and downgrade, based on the ISSU compatibility matrix tables.

Note
When you run the software upgrade from Cisco IOS XE Release 2.x.x to Cisco IOS XE Release 3.x.xS, you have to load the new image on both RPs, verify that it is good code, change the boot loader variable, and reboot the whole chassis. Failure to do that results in a "wedged" router and the only remedy is physically pull out one of the RPs, boot on the remaining RP, downgrade its code to the same version as the pulled out RP and start the process over again.
ISSU Upgrade Procedures
This section contains the following topics:
•
Using ISSU to Perform a Consolidated Package Upgrade in a Dual Route Processor Configuration
•
Using ISSU to Upgrade the SubPackages in a Dual Route Processor Configuration
Using ISSU to Perform a Consolidated Package Upgrade in a Dual Route Processor Configuration
Consolidated packages can only be upgraded using ISSU in dual Route Processor configurations. ISSU is not supported for consolidated package upgrades in single Route Processor configurations.
If you want the RPs on your Cisco ASR 1000 Series router to be running using a consolidated package after the ISSU upgrade is complete, use the following instructions:
Note
This procedure will only work if the current RPs are already running consolidated packages.
SUMMARY STEPS
1.
ip tftp source-interface gigabitethernet slot/port
2.
copy tftp: URL-to-target-location
3.
copy source-file-system:filename standby-destination-filesystem
4.
dir URL-to-target-location
dir URL-to-target-stby-location
5.
issu loadversion rp upgrade-rp-number standby-file-system:filename
6.
issu runversion
7.
telnet ip-address port
8.
issu acceptversion
9.
issu commitversion
10.
show version, show version active-RP running, show version active-RP provisioned
show platform
show running-configuration
11.
hw-module slot RP slot number reload
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
ip tftp source-interface gigabitethernet slot/port
Example:
Router(config)# ip tftp source-interface
gigabitethernet 0
|
Specifies the Gigabit Ethernet TFTP source-interface to be configured:
slot/port—Specifies the location of the TFTP source-interface.
Note To copy a file using TFTP through the Management Ethernet interface, the ip tftp source-interface GigabitEthernet 0 command must be entered before entering the copy tftp command.
|
Step 2
|
copy tftp: URL-to-target-location
copy source-file-system:filename
standby-destination-filesystem
Example:
Router# copy tftp bootflash:
|
Copy the consolidated package onto the active RP.
|
Step 3
|
copy source-file-system:filename
standby-destination-filesystem
Example:
Router# copy
bootflash:asr1000rp1-adventerprisek9.02.01.01.122-33.
XNA1.bin stby-bootflash:
|
Copy the consolidated package onto the standby RP.
|
Step 4
|
dir URL-to-target-location
dir URL-to-target-stby-location
Example:
Router# dir bootflash:
Router# dir stby-bootflash:
|
(Optional) Display the contents of the target directories to confirm the successful copy of the file package.
|
Step 5
|
issu loadversion rp upgrade-rp-number
standby-file-system:filename
Example:
Router# issu loadversion rp 1 file
stby-bootflash:asr1000rp1-adventerprisek9.02.01.01.12
2-33.XNA1.bin
|
Load the target consolidated package onto the standby RP.
After you receive the message indicating that the terminal state has been reached, go on to Step 6.
|
Step 6
|
issu runversion
Example:
Router# issu runversion
|
Run the consolidated package that was loaded in Step 5.
Note If this command is entered before the terminal state is reached, a "peer is not online" or "Standby RP is not in terminal state" error message will be seen and the issu runversion command will not work. If the issu runversion command does not run for these reasons, wait for the "terminal state is reached" message to appear and retry the issu runversion command. You can also monitor the terminal state using the show platform command.
After ISSU runversion is completed, a switchover will automatically occur and the standby RP will become the active RP.
|
Step 7
|
telnet ip-address port
Example:
[unix-server-1 ~]$ telnet 172.17.52.157 2003
User Access Verification
Username: user
Password: ********
Router>
|
Log in to the RP being upgraded, preferably using the RP's console port, to complete the upgrade. (This is the new active RP, that was the standby RP prior to the ISSU process.)
Note Ensure the hostname does not end in "-stby" after logging into the RP, as this indicates that the RP being accessed is still the standby RP.
There are many ways to log on to a console port. The example shows access to the console port from a UNIX host using telnet.
|
Step 8
|
issu acceptversion
Example:
Router# issu acceptversion
|
(Optional) Stops the ISSU rollback timer.
This step is optional as long as Step 9 is completed before the rollback timer expires.
|
Step 9
|
issu commitversion
Example:
Router# issu commitversion
|
Completes the ISSU upgrade.
|
Step 10
|
show version
show version active-RP running
show version active-RP provisioned
show platform
show running-configuration
|
(Optional) Enter the show version, show platform, or show running-configuration commands to confirm that the upgrade completed successfully, as follows:
• show version—Confirm that the correct software version is running on your router and that the RP was booted from the correct file.
• show running-configuration—Confirm that the booting configuration, in particular the boot system statements, are correct.
Tip  Use the show running-config | include boot command to display only the boot statements from the show running-configuration output.
• show platform— Confirm that both RP0 and RP1 are correctly running as active and standby.
|
Step 11
|
hw-module slot RP-slot reload
Example:
Router# hw-module slot R0 reload
|
Reload the new software on the Standby RP.
|
Examples
The following example shows how to perform consolidated package upgrade in a dual route processor configuration:
Router(config)# ip tftp source-interface gigabitethernet 0
Router# copy tftp bootflash:
Address or name of remote host []? 172.17.16.81
Source filename []?
/auto/tftp-users/user/asr1000rp1-adventerprisek9.02.01.01.122-33.XNA1.bin
Destination filename [asr1000rp1-adventerprisek9.02.01.01.122-33.XNA1.bin]?
Accessing
tftp://172.17.16.81//auto/tftp-users/user/asr1000rp1-adventerprisek9.02.01.01.122-33.XNA1.
bin...
Loading /auto/tftp-users/user/asr1000rp1-adventerprisek9.02.01.01.122-33.XNA1.bin from
172.17.16.81 (via GigabitEthernet0):
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!
209227980 bytes copied in 329.215 secs (635536 bytes/sec)
Router# copy bootflash:asr1000rp1-adventerprisek9.02.01.01.122-33.XNA1.bin stby-bootflash:
Destination filename [asr1000rp1-adventerprisek9.02.01.01.122-33.XNA1.bin]?
Copy in progress...CCCCCCCC
<output removed for brevity>
209227980 bytes copied in 434.790 secs (481216 bytes/sec)
11 drwx 16384 Dec 4 2007 04:32:46 -08:00 lost+found
86401 drwx 4096 Dec 4 2007 06:06:24 -08:00 .ssh
14401 drwx 4096 Dec 4 2007 06:06:36 -08:00 .rollback_timer
28801 drwx 4096 Jul 21 2008 15:29:25 -07:00 .prst_sync
43201 drwx 4096 Dec 4 2007 04:34:45 -08:00 .installer
12 -rw- 208904396 May 28 2008 16:17:34 -07:00
asr1000rp1-adventerprisek9.02.01.00.122-33.XNA.bin
57604 -rw- 47071436 May 29 2008 15:45:24 -07:00
asr1000rp1-espbase.02.01.00.122-33.XNA.pkg
57602 -rw- 5740 May 29 2008 15:45:23 -07:00
asr1000rp1-packages-adventerprisek9.02.01.00.122-33.XNA.conf
57605 -rw- 20334796 May 29 2008 15:45:25 -07:00
asr1000rp1-rpaccess.02.01.00.122-33.XNA.pkg
57606 -rw- 22294732 May 29 2008 15:45:25 -07:00
asr1000rp1-rpbase.02.01.00.122-33.XNA.pkg
57607 -rw- 21946572 May 29 2008 15:45:26 -07:00
asr1000rp1-rpcontrol.02.01.00.122-33.XNA.pkg
57608 -rw- 48099532 May 29 2008 15:45:27 -07:00
asr1000rp1-rpios-adventerprisek9.02.01.00.122-33.XNA.pkg
57609 -rw- 34324684 May 29 2008 15:45:28 -07:00
asr1000rp1-sipbase.02.01.00.122-33.XNA.pkg
57610 -rw- 22124748 May 29 2008 15:45:29 -07:00
asr1000rp1-sipspa.02.01.00.122-33.XNA.pkg
14 -rw- 275093 May 29 2008 16:27:53 -07:00
crashinfo_RP_00_00_20080529-162753-DST
15 -rw- 7516 Jul 2 2008 15:01:39 -07:00 startup-config
13 -rw- 45977 Apr 9 2008 16:48:46 -07:00 target_support_output.tgz.tgz
16 -rw- 209227980 Jul 17 2008 16:06:58 -07:00
asr1000rp1-adventerprisek9.02.01.01.122-33.XNA1.bin
928862208 bytes total (76644352 bytes free)
Router# dir stby-bootflash:
Directory of stby-bootflash:/
11 drwx 16384 Dec 13 2004 03:45:47 -08:00 lost+found
87937 drwx 4096 Jul 17 2008 16:43:34 -07:00 .rollback_timer
14657 drwx 4096 Jul 17 2008 16:43:34 -07:00 .installer
29313 drwx 4096 Dec 13 2004 03:53:00 -08:00 .ssh
12 -rw- 33554432 Dec 13 2004 03:53:49 -08:00 nvram_00100
13 -rw- 208904396 Jun 5 2008 20:12:53 -07:00
asr1000rp1-adventerprisek9.02.01.00.122-33.XNA.bin
58625 drwx 4096 Jul 21 2008 15:32:59 -07:00 .prst_sync
43972 -rw- 47071436 Jun 5 2008 20:16:55 -07:00
asr1000rp1-espbase.02.01.00.122-33.XNA.pkg
43970 -rw- 5740 Jun 5 2008 20:16:54 -07:00
asr1000rp1-packages-adventerprisek9.02.01.00.122-33.XNA.conf
43973 -rw- 20334796 Jun 5 2008 20:16:56 -07:00
asr1000rp1-rpaccess.02.01.00.122-33.XNA.pkg
43974 -rw- 22294732 Jun 5 2008 20:16:56 -07:00
asr1000rp1-rpbase.02.01.00.122-33.XNA.pkg
43975 -rw- 21946572 Jun 5 2008 20:16:57 -07:00
asr1000rp1-rpcontrol.02.01.00.122-33.XNA.pkg
43976 -rw- 48099532 Jun 5 2008 20:16:58 -07:00
asr1000rp1-rpios-adventerprisek9.02.01.00.122-33.XNA.pkg
43977 -rw- 34324684 Jun 5 2008 20:16:59 -07:00
asr1000rp1-sipbase.02.01.00.122-33.XNA.pkg
43978 -rw- 22124748 Jun 5 2008 20:17:00 -07:00
asr1000rp1-sipspa.02.01.00.122-33.XNA.pkg
43971 -rw- 6256 Jun 5 2008 20:17:00 -07:00 packages.conf
14 -rw- 209227980 Jul 17 2008 16:16:07 -07:00
asr1000rp1-adventerprisek9.02.01.01.122-33.XNA1.bin
945377280 bytes total (276652032 bytes free)
Router# issu loadversion rp 1 file
stby-bootflash:asr1000rp1-adventerprisek9.02.01.01.122-33.XNA1.bin
--- Starting installation state synchronization ---
Finished installation state synchronization
--- Starting file path checking ---
Finished file path checking
--- Starting system installation readiness checking ---
Finished system installation readiness checking
--- Starting installation changes ---
Setting up image to boot on next reset
Starting automatic rollback timer
Finished installation changes
SUCCESS: Software will now load.
*Jul 21 23:34:27.206: %ASR1000_OIR-6-OFFLINECARD: Card (rp) offline in slot R1
*Jul 21 23:34:27.271: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault
(PEER_NOT_PRESENT)
*Jul 21 23:34:27.271: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER_DOWN)
*Jul 21 23:34:27.271: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault
(PEER_REDUNDANCY_STATE_CHANGE)
*Jul 21 23:37:05.528: %ASR1000_OIR-6-ONLINECARD: Card (rp) online in slot R1
*Jul 21 23:37:25.480: %REDUNDANCY-5-PEER_MONITOR_EVENT: Active detected a standby
insertion (raw-event=PEER_FOUND(4))
*Jul 21 23:37:25.480: %REDUNDANCY-5-PEER_MONITOR_EVENT: Active detected a standby
insertion (raw-event=PEER_REDUNDANCY_STATE_CHANGE(5))
Finished installation state synchronization
*Jul 21 23:37:26.349: %REDUNDANCY-3-IPC: IOS versions do not match.
*Jul 21 23:38:47.172: %HA_CONFIG_SYNC-6-BULK_CFGSYNC_SUCCEED: Bulk Sync succeeded
*Jul 21 23:38:47.173: %RF-5-RF_TERMINAL_STATE: Terminal state reached for (SSO)
--- Starting installation state synchronization ---
Finished installation state synchronization
Initiating active RP failover
SUCCESS: Standby RP will now become active
System Bootstrap, Version 12.2(33r)XN2, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 2008 by cisco Systems, Inc.
<additional output removed for brevity>
*Jul 21 23:43:31.970: %SYS-5-RESTART: System restarted --
Cisco IOS Software, IOS-XE Software (PPC_LINUX_IOSD-ADVENTERPRISEK9-M), Version
12.2(33)XNA, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2008 by Cisco Systems, Inc.
Compiled Thu 01-May-08 00:29 by mcpre
*Jul 21 23:43:31.978: %SSH-5-ENABLED: SSH 1.99 has been enabled
*Jul 21 23:43:35.196: Relay: standby progression done
*Jul 21 23:43:35.197: %PLATFORM-6-RF_PROG_SUCCESS: RF state STANDBY HOT
At this point of the procedure, use your UNIX client to log in to the other RP:
[unix-server-1 ~]$ telnet 172.17.52.157 2003
Router# issu acceptversion
Cancelling rollback timer
SUCCESS: Rollback timer cancelled
Router# issu commitversion
--- Starting installation changes ---
Cancelling rollback timer
Finished installation changes
Building configuration...
SUCCESS: version committed: bootflash:asr1000rp1-adventerprisek9.02.01.01.122-33.XNA1.bin
After you confirm the software versions and configuration, reload the RP as shown in the following example:
Router# hw-module slot R0 reload
Proceed with reload of module? [confirm]
*Jul 21 23:54:27.271: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault
(PEER_NOT_PRESENT)
*Jul 21 23:54:27.271: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER_DOWN)
*Jul 21 23:54:27.271: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault
(PEER_REDUNDANCY_STATE_CHANGE)
*Jul 21 23:57:05.528: %ASR1000_OIR-6-ONLINECARD: Card (rp) online in slot R0
*Jul 21 23:57:25.480: %REDUNDANCY-5-PEER_MONITOR_EVENT: Active detected a standby
insertion (raw-event=PEER_FOUND(4))
*Jul 21 23:57:25.480: %REDUNDANCY-5-PEER_MONITOR_EVENT: Active detected a standby
insertion (raw-event=PEER_REDUNDANCY_STATE_CHANGE(5))
*Jul 21 23:58:47.172: %HA_CONFIG_SYNC-6-BULK_CFGSYNC_SUCCEED: Bulk Sync succeeded
*Jul 21 23:58:47.173: %RF-5-RF_TERMINAL_STATE: Terminal state reached for (SSO)
Using ISSU to Upgrade the SubPackages in a Dual Route Processor Configuration
This section provides instructions on performing an ISSU upgrade on a Cisco ASR 1000 Series Router with dual RPs that is currently running individual subpackages.
This section covers the following topics:
•
Using ISSU to Upgrade the SubPackages on a Cisco ASR 1006 or ASR 1013 Router (issu Command Set)
•
Using ISSU to Upgrade SubPackages on a Cisco ASR 1006 Router or ASR 1013 Router (request platform command set)
Using ISSU to Upgrade the SubPackages on a Cisco ASR 1006 or ASR 1013 Router (issu Command Set)
This section provides the instructions for performing an ISSU upgrade using subpackages on a Cisco ASR 1006 router or ASR 1013 router with a dual RP setup using the issu command set.
This procedure can only be performed if the current ASR 1006 or ASR 1013 routers have two active RPs and both RPs are running subpackages.
SUMMARY STEPS
1.
show version
show version active-rp installed
dir filesystem:<directory>
show platform
show redundancy-states
2.
copy running-config startup-config
3.
mkdir URL-to-directory-name
4.
ip tftp source-interface gigabitethernet slot/port
5.
copy tftp: URL-to-target-location
6.
request platform software package expand file URL-to-consolidated-package
7.
dir URL-to-consolidated-package
8.
copy file-system:asr1000rp1-espbase.version.pkg URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1000rp1-rpaccess.version.pkg URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1000rp1-rpbase.version.pkg URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1000rp1-rpcontrol.version.pkg URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1000rp1-rpios.version.pkg URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1000rp1-sipbase.version.pkg URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1000rp1-sipspa.version.pkg URL-to-directory-of-sub-packages-active-RP
Note
In step 6, each individual subpackage that was extracted in step 4 is copied to the directory where the subpackages that are currently running the standby RP are stored.
9.
copy file-system:asr1000rp1-espbase.version.pkg URL-to-directory-of-sub-packages-standby-RP
copy file-system:asr1000rp1-rpaccess.version.pkg URL-to-directory-of-sub-packages-standby-RP
copy file-system:asr1000rp1-rpbase.version.pkg URL-to-directory-of-sub-packages-standby-RP
copy file-system:asr1000rp1-rpcontrol.version.pkg URL-to-directory-of-sub-packages-standby-RP
copy file-system:asr1000rp1-rpios.version.pkg URL-to-directory-of-sub-packages-standby-RP
copy file-system:asr1000rp1-sipbase.version.pkg URL-to-directory-of-sub-packages-standby-RP
copy file-system:asr1000rp1-sipspa.version.pkg URL-to-directory-of-sub-packages-standby-RP
10.
issu loadversion rp standby-RP file URL-to-standby-file-system:asr1000rp*version*.pkg force
11.
hw-module slot standby-RP reload
12.
issu loadversion rp active-RP file URL-to-active-file-system:asr1000rp1-{sipbase,sipspa}*version*.pkg slot SIP-slot-number force
issu commitversion
Repeat this step for each SIP installed in the router before moving onto the next step.
13.
issu loadversion rp active-RP file URL-to-active-file-system:asr1000rp1-esp*version*.pkg slot standby-ESP-slot
issu commitversion
issu loadversion rp active-RP file URL-to-active-file-system:asr1000rp1-esp*version*.pkg slot active-ESP-slot
issu commitversion
14.
issu loadversion rp active-RP file URL-to-active-file-system:asr1000rp1*version*.pkg force
15.
show version active-RP provisioned
show version active-RP installed
16.
redundancy force-switchover
17.
request platform software package clean
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
show version
show version active-rp installed
dir filesystem: directory
show platform
show redundancy states
Example:
Router# show version
Router# show version r0 installed
Router# dir bootflash:
Router# show platform
Router# show redundancy states
|
(Optional) Use the following commands to confirm the current router configuration, as follows:
• show version and show version active-rp installed—Verify the running version of the Cisco IOS XE software on the router, and which file was used to boot the router, and where that file is stored.
• dir—Confirm that the files that were used to boot the router are located in the directory.
• show platform—Confirm the current status of the active and standby RPs.
• show redundancy states—Confirm the operational and configured redundancy states.
|
Step 2
|
copy running-config startup-config
Example:
Router# copy running-config startup-config
|
After you have confirmed that the system states are acceptable, save the current configuration to the startup configuration.
|
Step 3
|
mkdir URL-to-directory-name
Example:
Router# mkdir usb0:221subs
|
Create a directory to store the consolidated package and subpackages.
This directory must be created in most cases because the consolidated packages and subpackages have to be separated from the subpackages that booted the router at this step of the procedure.
|
Step 4
|
ip tftp source-interface gigabitethernet slot/port
Example:
Router(config)# ip tftp source-interface
gigabitethernet 0
|
Specifies the Gigabit Ethernet TFTP source-interface to be configured:
slot/port—Specifies the location of the TFTP source-interface.
Note To copy a file using TFTP through the Management Ethernet interface, the ip tftp source-interface GigabitEthernet 0 command must be entered before entering the copy tftp command.
|
Step 5
|
copy tftp: URL-to-target-location
Example:
Router# copy tftp: usb0:221subs
|
Copy the consolidated package file into the directory created in Step 3.
The consolidated package in this step should not be copied into the same directory where the subpackages that are currently running your router are stored (the directory containing the packages.conf provisioning file from which the router was booted).
Tip  It is recommended that you copy the package onto a usb: or harddisk: file system for space considerations when performing this step of the procedure.
|
Step 6
|
request platform software package expand file
URL-to-consolidated-package
Example:
Router# request platform software package
expand file
usb0:221subs/asr1000rp1-adventerprisek9.02.02.0
1.122-33.XNB1.bin
|
Extract the subpackages out of the consolidated package file into the temporary directory.
Note Take extra care to extract the subpackages to a temporary subdirectory and do not delete any of the files currently running the router at this point of the procedure.
To erase the files that were running on the router before the ISSU upgrade, enter the request platform software package clean command after the ISSU upgrade has been completed.
|
Step 7
|
dir target-URL
Example:
Router# dir usb0:221subs
|
(Optional) Display the directory to confirm that the files were extracted.
|
Step 8
|
copy file-system:asr1000rp1-espbase.version.pkg
URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1000rp1-rpaccess.version.pkg
URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1000rp1-rpbase.version.pkg
URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1000rp1-rpcontrol.version.pkg
URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1000rp1-rpios.version.pkg
URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1000rp1-sipbase.version.pkg
URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1000rp1-sipspa.version.pkg
URL-to-directory-of-sub-packages-active-RP
Example:
Router# copy
usb0:221subs/asr1000rp1-espbase.02.02.01.122-33
.XNB1.pkg bootflash:
Router# copy
usb0:221subs/asr1000rp1-rpaccess.02.02.01.122-3
3.XNB1.pkg bootflash:
Router# copy
usb0:221subs/asr1000rp1-rpbase.02.02.01.122-33.
XNB1.pkg bootflash:
Router# copy
usb0:221subs/asr1000rp1-rpcontrol.02.02.01.122-
33.XNB1.pkg bootflash:
Router# copy
usb0:221subs/asr1000rp1-rpios-adventerprisek9.0
2.02.01.122-33.XNB1.pkg bootflash:
Router# copy
usb0:221subs/asr1000rp1-sipbase.02.02.01.122-33
.XNB1.pkg bootflash:
Router# copy
usb0:221subs/asr1000rp1-sipspa.02.02.01.122-33.
XNB1.pkg bootflash:
|
Copy the subpackages out of the temporary directory into the directory on the router where the subpackages running the active RP are currently stored.
|
Step 9
|
copy file-system:asr1000rp1-espbase.version.pkg
URL-to-directory-of-sub-packages-standby-RP
copy file-system:asr1000rp1-rpaccess.version.pkg
URL-to-directory-of-sub-packages-standby-RP
copy file-system:asr1000rp1-rpbase.version.pkg
URL-to-directory-of-sub-packages-standby-RP
copy file-system:asr1000rp1-rpcontrol.version.pkg
URL-to-directory-of-sub-packages-standby-RP
copy file-system:asr1000rp1-rpios.version.pkg
URL-to-directory-of-sub-packages-standby-RP
copy file-system:asr1000rp1-sipbase.version.pkg
URL-to-directory-of-sub-packages-standby-RP
copy file-system:asr1000rp1-sipspa.version.pkg
URL-to-directory-of-sub-packages-standby-RP
Example:
Router# copy
usb0:221subs/asr1000rp1-espbase.02.02.01.122-33
.XNB1.pkg stby-bootflash:
Router# copy
usb0:221subs/asr1000rp1-rpaccess.02.02.01.122-3
3.XNB1.pkg stby-bootflash:
Router# copy
usb0:221subs/asr1000rp1-rpbase.02.02.01.122-33.
XNB1.pkg stby-bootflash:
Router# copy
usb0:221subs/asr1000rp1-rpcontrol.02.02.01.122-
33.XNB1.pkg stby-bootflash:
Router# copy
usb0:221subs/asr1000rp1-rpios-adventerprisek9.0
2.02.01.122-33.XNB1.pkg stby-bootflash:
Router# copy
usb0:221subs/asr1000rp1-sipbase.02.02.01.122-33
.XNB1.pkg stby-bootflash:
Router# copy
usb0:221subs/asr1000rp1-sipspa.02.02.01.122-33.
XNB1.pkg stby-bootflash:
|
Copy the subpackages out of the temporary directory into the directory on the router where the subpackages running the standby RP are currently stored.
|
Step 10
|
issu loadversion rp standby-RP file
target-standbyRP-URL-for-sub-packages:asr1000rp*
version*.pkg force
Example:
Router# issu loadversion rp 1 file
stby-bootflash:asr1000rp*02.02.01.122-33.XNB1*.
pkg force
|
Upgrade the RP subpackages on the standby RP, where the "rp*" wildcard is specified to capture all of the RP subpackages for the desired upgrade release.
|
Step 11
|
hw-module slot standby-RP reload
Example:
Router# hw-module slot R1 reload
|
Reload the standby RP.
|
Step 12
|
issu loadversion rp active-RP file
URL-to-active-file-system:asr1000rp1-{sipbase,sip
spa}*version*.pkg slot SIP-slot-number force
issu commitversion
Repeat this step for each SIP installed in the
router before moving onto the next step.
Example:
Router# issu loadversion rp 0 file
bootflash:asr1000rp1-{sipbase,sipspa}*02.02.01.
122-33.XNB1*.pkg slot 0 force
Router# issu commitversion
Router# issu loadversion rp 0 file
bootflash:asr1000rp1-{sipbase,sipspa}*02.02.01.
122-33.XNB1*.pkg slot 1 force
Router# issu commitversion
Router# issu loadversion rp 0 file
bootflash:asr1000rp1-{sipbase,sipspa}*02.02.01.
122-33.XNB1*.pkg slot 2 force
Router# issu commitversion
|
Upgrade the SIP and SPA subpackages for each SIP on the router.
Note This step must be completed one SIP at a time, and repeated for each SIP installed on the router before performing the next step.
Tip  You can use the show ip interface brief command to identify which slots contain SIPs and SPAs. The interfaces with three numbers (in the form SIP-number/SPA-number/interface-number) identify the SIP and SPA locations in the router.
Note The pattern options used in this CLI (sipbase and sipspa) were introduced in Cisco IOS XE Release 2.1.2 and are not available in previous Cisco IOS XE Releases. See the "ISSU Procedures (Prior to Cisco IOS XE Release 2.1.2)" section for pre-Cisco IOS XE Release 2.1.2 ISSU upgrade procedures.
|
Step 13
|
issu loadversion rp active-RP file
URL-to-active-file-system:asr1000rp1-esp*version*.
pkg slot standby-ESP-slot
issu commitversion
issu loadversion rp active-RP file
URL-to-active-file-system:asr1000rp1-esp*version*.
pkg slot active-ESP-slot
issu commitversion
Example:
Router# issu loadversion rp 0 file
bootflash:asr1000rp1-esp*02.02.01.122-33.XNB1*.
pkg slot 1
Router# issu commitversion
Router# issu loadversion rp 0 file
bootflash:asr1000rp1-esp*02.02.01.122-33.XNB1*.
pkg slot 0
Router# issu commitversion
|
Upgrade the ESP Base subpackage on the standby and the active ESPs.
After entering the issu loadversion rp command on the active RP, the ESP switchover will occur automatically. Minimal traffic interruption will occur as a result of this switchover.
|
Step 14
|
issu loadversion rp active-RP file
URL-to-active-file-system:asr1000rp*version*.pkg
force
Example:
Router# issu loadversion rp 0 file
bootflash:asr1000rp1*02.02.01.122-33.XNB1*.pkg
force
|
Upgrade all of the subpackages on the active RP.
Note This step is required to ensure that all subpackages on the router were upgraded as part of this procedure, and might upgrade some subpackages that would otherwise be missed in the process.
|
Step 15
|
show version active-RP provisioned
show version active-RP installed
Example:
Router# show version r0 provisioned
Router# show version r0 installed
|
(Optional) Confirm that the subpackages are provisioned and installed.
|
Step 16
|
redundancy force-switchover
Example:
Router# redundancy force-switchover
|
Force an RP switchover to complete the upgrade.
|
Step 17
|
request platform software package clean
Example:
Router# request platform software package clean
|
(Optional) Removes all unused subpackages files from the router.
|
Examples
The following example shows ISSU upgrade using subpackages on a Cisco ASR 1006 router or ASR 1013 router with a dual RP setup using the issu command set
Cisco IOS Software, IOS-XE Software (PPC_LINUX_IOSD-ADVENTERPRISEK9-M), Version
12.2(33)XNA, RELEASE SOFTWARE (fc1)
<output removed for brevity>
System image file is "bootflash:packages.conf"
<output removed for brevity>
Slot Type State Insert time (ago)
--------- ------------------- --------------------- -----------------
0 ASR1000-SIP10 ok 00:03:03
0/0 SPA-4XT-SERIAL ok 00:01:35
0/1 SPA-5X1GE-V2 ok 00:01:35
0/2 SPA-2XOC3-POS ok 00:01:36
0/3 SPA-4XT-SERIAL ok 00:01:35
1 ASR1000-SIP10 ok 00:03:03
1/0 SPA-4X1FE-TX-V2 ok 00:01:36
1/1 SPA-2X1GE-V2 ok 00:01:35
1/3 SPA-1XOC12-POS ok 00:01:36
R0 ASR1000-RP1 ok, active 00:03:03
R1 ASR1000-RP1 ok, standby 00:03:03
F0 ASR1000-ESP10 ok, active 00:03:03
F1 ASR1000-ESP10 ok, standby 00:03:03
P0 ASR1006-PWR-AC ok 00:02:07
P1 ASR1006-FAN ok 00:02:07
Slot CPLD Version Firmware Version
--------- ------------------- ---------------------------------------
Router# show version r0 installed
Package: Provisioning File, version: n/a, status: active
File: bootflash:packages.conf, on: RP0
File SHA1 checksum: 174bef13f7ce20af077bae7aaefb5279c790dd57
Package: rpbase, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: active
File:
bootflash:asr1000rp1-rpbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg,
on: RP0
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 661bcb2efda479533c87f23504bf7021d42b3165
Package: rpaccess, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: active
File:
bootflash:asr1000rp1-rpaccess.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg
, on: RP0
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: b0dc8e07cd4f997b045280fa79051e41068c6f3e
Package: rpcontrol, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: active
File:
bootflash:asr1000rp1-rpcontrol.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pk
g, on: RP0/0
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 258c79c9b9e67eb4c21dcb4c9b2fe8b8c1f96cfd
Package: rpios-adventerprisek9, version:
BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1, status: active
File:
bootflash:asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_200809
24_0100_1.pkg, on: RP0/0
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 88ea800ae1c094c46ca5e2f26d116f4e0012c219
Package: rpcontrol, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: inactive
File:
bootflash:asr1000rp1-rpcontrol.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pk
g, on: RP0/1
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 258c79c9b9e67eb4c21dcb4c9b2fe8b8c1f96cfd
Package: rpios-adventerprisek9, version:
BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1, status: inactive
File:
bootflash:asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_200809
24_0100_1.pkg, on: RP0/1
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 88ea800ae1c094c46ca5e2f26d116f4e0012c219
Package: rpbase, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: active
File:
bootflash:asr1000rp1-rpbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg,
on: RP1
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 661bcb2efda479533c87f23504bf7021d42b3165
Package: rpaccess, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: active
File:
bootflash:asr1000rp1-rpaccess.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg
, on: RP1
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: b0dc8e07cd4f997b045280fa79051e41068c6f3e
Package: rpcontrol, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: active
File:
bootflash:asr1000rp1-rpcontrol.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pk
g, on: RP1/0
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 258c79c9b9e67eb4c21dcb4c9b2fe8b8c1f96cfd
Package: rpios-adventerprisek9, version:
BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1, status: active
File:
bootflash:asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_200809
24_0100_1.pkg, on: RP1/0
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 88ea800ae1c094c46ca5e2f26d116f4e0012c219
Package: rpcontrol, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: inactive
File:
bootflash:asr1000rp1-rpcontrol.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pk
g, on: RP1/1
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 258c79c9b9e67eb4c21dcb4c9b2fe8b8c1f96cfd
Package: rpios-adventerprisek9, version:
BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1, status: inactive
File:
bootflash:asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_200809
24_0100_1.pkg, on: RP1/1
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 88ea800ae1c094c46ca5e2f26d116f4e0012c219
Package: espbase, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: active
File:
bootflash:asr1000rp1-espbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg,
on: ESP0
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: da8e5c93d0fa3f7cf27381841fa9efcde409964d
Package: espbase, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: active
File:
bootflash:asr1000rp1-espbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg,
on: ESP1
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: da8e5c93d0fa3f7cf27381841fa9efcde409964d
Package: sipbase, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: active
File:
bootflash:asr1000rp1-sipbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg,
on: SIP0
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 31b36be34aa63e0aafbb8abb2cc40a0cbcd5f68e
Package: sipspa, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: active
File:
bootflash:asr1000rp1-sipspa.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg,
on: SIP0/0
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 337c662bcea5d34736e6df3acf7d7cb2a0a8c2f7
Package: sipspa, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: active
File:
bootflash:asr1000rp1-sipspa.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg,
on: SIP0/1
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 337c662bcea5d34736e6df3acf7d7cb2a0a8c2f7
Package: sipspa, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: active
File:
bootflash:asr1000rp1-sipspa.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg,
on: SIP0/2
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 337c662bcea5d34736e6df3acf7d7cb2a0a8c2f7
Package: sipspa, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: active
File:
bootflash:asr1000rp1-sipspa.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg,
on: SIP0/3
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 337c662bcea5d34736e6df3acf7d7cb2a0a8c2f7
Package: sipbase, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: active
File:
bootflash:asr1000rp1-sipbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg,
on: SIP1
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 31b36be34aa63e0aafbb8abb2cc40a0cbcd5f68e
Package: sipspa, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: active
File:
bootflash:asr1000rp1-sipspa.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg,
on: SIP1/0
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 337c662bcea5d34736e6df3acf7d7cb2a0a8c2f7
Package: sipspa, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: active
File:
bootflash:asr1000rp1-sipspa.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg,
on: SIP1/1
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 337c662bcea5d34736e6df3acf7d7cb2a0a8c2f7
Package: sipspa, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: inactive
File:
bootflash:asr1000rp1-sipspa.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg,
on: SIP1/2
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 337c662bcea5d34736e6df3acf7d7cb2a0a8c2f7
Package: sipspa, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: active
File:
bootflash:asr1000rp1-sipspa.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg,
on: SIP1/3
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 337c662bcea5d34736e6df3acf7d7cb2a0a8c2f7
Package: sipbase, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: inactive
File:
bootflash:asr1000rp1-sipbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg,
on: SIP2
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 31b36be34aa63e0aafbb8abb2cc40a0cbcd5f68e
Package: sipspa, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: inactive
File:
bootflash:asr1000rp1-sipspa.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg,
on: SIP2/0
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 337c662bcea5d34736e6df3acf7d7cb2a0a8c2f7
Package: sipspa, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: inactive
File:
bootflash:asr1000rp1-sipspa.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg,
on: SIP2/1
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 337c662bcea5d34736e6df3acf7d7cb2a0a8c2f7
Package: sipspa, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: inactive
File:
bootflash:asr1000rp1-sipspa.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg,
on: SIP2/2
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 337c662bcea5d34736e6df3acf7d7cb2a0a8c2f7
Package: sipspa, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: inactive
File:
bootflash:asr1000rp1-sipspa.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg,
on: SIP2/3
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 337c662bcea5d34736e6df3acf7d7cb2a0a8c2f7
Router# mkdir usb0:221subs
Create directory filename [221subs]?
Created dir bootflash:221subs
Router(config)# ip tftp source-interface gigabitethernet 0
Router# copy tftp: usb0:221subs
Address or name of remote host []? 172.17.16.81
Source filename []? /auto/users/asr1000rp1-adventerprisek9.02.02.01.122-33.XNB1.bin
Destination filename [asr1000rp1-adventerprisek9.02.02.01.122-33.XNB1.bin]?
Accessing
tftp://172.17.16.81//auto/users/asr1000rp1-adventerprisek9.02.02.01.122-33.XNB1.bin...
Loading /auto/users/asr1000rp1-adventerprisek9.02.02.01.122-33.XNB1.bin from 172.17.16.81
(via GigabitEthernet0):
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!.!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!
209227980 bytes copied in 880.002 secs (237759 bytes/sec)
Router# request platform software package expand file
usb0:221subs/asr1000rp1-adventerprisek9.02.02.01.122-33.XNB1.bin
SUCCESS: Finished expanding all-in-one software package.
Directory of usb0:/221subs/
72013 -rw- 51904716 Oct 7 2008 15:46:02 -07:00
asr1000rp1-espbase.02.02.01.122-33.XNB1.pkg
72004 -rw- 5773 Oct 7 2008 15:46:02 -07:00
asr1000rp1-packages-adventerprisek9.02.02.01.122-33.XNB1.conf
72014 -rw- 20533452 Oct 7 2008 15:46:03 -07:00
asr1000rp1-rpaccess.02.02.01.122-33.XNB1.pkg
72015 -rw- 22388940 Oct 7 2008 15:46:03 -07:00
asr1000rp1-rpbase.02.02.01.122-33.XNB1.pkg
72016 -rw- 27961548 Oct 7 2008 15:46:03 -07:00
asr1000rp1-rpcontrol.02.02.01.122-33.XNB1.pkg
72017 -rw- 50942156 Oct 7 2008 15:46:03 -07:00
asr1000rp1-rpios-adventerprisek9.02.02.01.122-33.XNB1.pkg
72018 -rw- 36442316 Oct 7 2008 15:46:03 -07:00
asr1000rp1-sipbase.02.02.01.122-33.XNB1.pkg
72019 -rw- 26366156 Oct 7 2008 15:46:03 -07:00
asr1000rp1-sipspa.02.02.01.122-33.XNB1.pkg
72005 -rw- 6290 Oct 7 2008 15:46:03 -07:00 packages.conf
72003 -rw- 224768204 Oct 7 2008 15:38:57 -07:00
asr1000rp1-adventerprisek9.02.02.01.122-33.XNB1.bin
928862208 bytes total (466358272 bytes free)
Router# copy usb0:221subs/asr1000rp1-espbase.02.02.01.122-33.XNB1.pkg bootflash:
Destination filename [asr1000rp1-espbase.02.02.01.122-33.XNB1.pkg]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
51904716 bytes copied in 5.478 secs (9475122 bytes/sec)
Router# copy usb0:221subs/asr1000rp1-rpaccess.02.02.01.122-33.XNB1.pkg bootflash:
Destination filename [asr1000rp1-rpaccess.02.02.01.122-33.XNB1.pkg]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
20533452 bytes copied in 2.346 secs (8752537 bytes/sec)
Router# copy usb0:221subs/asr1000rp1-rpbase.02.02.01.122-33.XNB1.pkg bootflash:
Destination filename [asr1000rp1-rpbase.02.02.01.122-33.XNB1.pkg]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
22388940 bytes copied in 2.496 secs (8969928 bytes/sec)
Router# copy usb0:221subs/asr1000rp1-rpcontrol.02.02.01.122-33.XNB1.pkg bootflash:
Destination filename [asr1000rp1-rpcontrol.02.02.01.122-33.XNB1.pkg]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
27961548 bytes copied in 2.992 secs (9345437 bytes/sec)
Router# copy usb0:221subs/asr1000rp1-rpios-adventerprisek9.02.02.01.122-33.XNB1.pkg
bootflash:
Destination filename [asr1000rp1-rpios-adventerprisek9.02.02.01.122-33.XNB1.pkg]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
50942156 bytes copied in 5.719 secs (8907529 bytes/sec)
Router# copy usb0:221subs/asr1000rp1-sipbase.02.02.01.122-33.XNB1.pkg bootflash:
Destination filename [asr1000rp1-sipbase.02.02.01.122-33.XNB1.pkg]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCC
36442316 bytes copied in 3.906 secs (9329830 bytes/sec)
Router# copy usb0:221subs/asr1000rp1-sipspa.02.02.01.122-33.XNB1.pkg bootflash:
Destination filename [asr1000rp1-sipspa.02.02.01.122-33.XNB1.pkg]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
26366156 bytes copied in 2.857 secs (9228616 bytes/sec)
Router# copy usb0:221subs/asr1000rp1-espbase.02.02.01.122-33.XNB1.pkg stby-bootflash:
Destination filename [asr1000rp1-espbase.02.02.01.122-33.XNB1.pkg]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
51904716 bytes copied in 5.478 secs (9475122 bytes/sec)
Router# copy usb0:221subs/asr1000rp1-rpaccess.02.02.01.122-33.XNB1.pkg stby-bootflash:
Destination filename [asr1000rp1-rpaccess.02.02.01.122-33.XNB1.pkg]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
20533452 bytes copied in 2.346 secs (8752537 bytes/sec)
Router# copy usb0:221subs/asr1000rp1-rpbase.02.02.01.122-33.XNB1.pkg stby-bootflash:
Destination filename [asr1000rp1-rpbase.02.02.01.122-33.XNB1.pkg]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
22388940 bytes copied in 2.496 secs (8969928 bytes/sec)
Router# copy usb0:221subs/asr1000rp1-rpcontrol.02.02.01.122-33.XNB1.pkg stby-bootflash:
Destination filename [asr1000rp1-rpcontrol.02.02.01.122-33.XNB1.pkg]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
27961548 bytes copied in 2.992 secs (9345437 bytes/sec)
Router# copy usb0:221subs/asr1000rp1-rpios-adventerprisek9.02.02.01.122-33.XNB1.pkg
stby-bootflash:
Destination filename [asr1000rp1-rpios-adventerprisek9.02.02.01.122-33.XNB1.pkg]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
50942156 bytes copied in 5.719 secs (8907529 bytes/sec)
Router# copy usb0:221subs/asr1000rp1-sipbase.02.02.01.122-33.XNB1.pkg stby-bootflash:
Destination filename [asr1000rp1-sipbase.02.02.01.122-33.XNB1.pkg]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCC
36442316 bytes copied in 3.906 secs (9329830 bytes/sec)
Router# copy usb0:221subs/asr1000rp1-sipspa.02.02.01.122-33.XNB1.pkg stby-bootflash:
Destination filename [asr1000rp1-sipspa.02.02.01.122-33.XNB1.pkg]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
26366156 bytes copied in 2.857 secs (9228616 bytes/sec)
Router#issu loadversion rp 1 file stby-bootflash:asr1000rp*02.02.01.122-33.XNB1*.pkg force
--- Starting installation state synchronization ---
Finished installation state synchronization
--- Starting file path checking ---
Finished file path checking
--- Starting image file verification ---
Checking image file names
Verifying image file locations
Locating image files and validating name syntax
Inspecting image file types
WARNING: In-service installation of IOSD package
WARNING: requires software redundancy on target RP
WARNING: or on-reboot parameter
WARNING: Automatically setting the on-reboot flag
WARNING: In-service installation of RP Base package
WARNING: requires software reboot of target RP
Processing image file constraints
Creating candidate provisioning file
Finished image file verification
--- Starting candidate package set construction ---
Verifying existing software set
Processing candidate provisioning file
Constructing working set for candidate package set
Constructing working set for running package set
Constructing merge of running and candidate packages
Finished candidate package set construction
--- Starting compatibility testing ---
Determining whether candidate package set is compatible
Determining whether installation is valid
Determining whether installation is valid ... skipped
Checking IPC compatibility for candidate software
Checking candidate package set infrastructure compatibility
Checking infrastructure compatibility with running software
Checking infrastructure compatibility with running software ... skipped
Checking package specific compatibility
Finished compatibility testing
--- Starting commit of software changes ---
Updating provisioning rollback files
Creating pending provisioning file
Committing provisioning file
Finished commit of software changes
SUCCESS: Software provisioned. New software will load on reboot.
Router# hw-module slot r1 reload
*Sep 25 19:16:29.709: %ASR1000_OIR-6-OFFLINECARD: Card (rp) offline in slot R1
*Sep 25 19:16:29.787: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault
(PEER_NOT_PRESENT)
*Sep 25 19:16:29.788: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER_DOWN)
*Sep 25 19:16:29.788: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault
(PEER_REDUNDANCY_STATE_CHANGE)
*Sep 25 19:19:05.496: %ASR1000_OIR-6-ONLINECARD: Card (rp) online in slot R1
*Sep 25 19:19:30.549: %REDUNDANCY-5-PEER_MONITOR_EVENT: Active detected a standby
insertion (raw-event=PEER_FOUND(4))
*Sep 25 19:19:30.550: %REDUNDANCY-5-PEER_MONITOR_EVENT: Active detected a standby
insertion (raw-event=PEER_REDUNDANCY_STATE_CHANGE(5))
*Sep 25 19:19:31.512: %REDUNDANCY-3-IPC: IOS versions do not match.
*Sep 25 19:21:02.256: %HA_CONFIG_SYNC-6-BULK_CFGSYNC_SUCCEED: Bulk Sync succeeded
*Sep 25 19:21:02.257: %RF-5-RF_TERMINAL_STATE: Terminal state reached for (SSO)
Router# issu loadversion rp 0 file
bootflash:asr1000rp1-{sipbase,sipspa}*02.02.01.122-33.XNB1*.pkg slot 0 force
--- Starting installation state synchronization ---
Finished installation state synchronization
--- Starting file path checking ---
Finished file path checking
--- Starting image file verification ---
Checking image file names
Verifying image file locations
Locating image files and validating name syntax
Inspecting image file types
Processing image file constraints
Creating candidate provisioning file
Finished image file verification
--- Starting candidate package set construction ---
Verifying existing software set
Processing candidate provisioning file
Constructing working set for candidate package set
Constructing working set for running package set
Constructing merge of running and candidate packages
Finished candidate package set construction
--- Starting compatibility testing ---
Determining whether candidate package set is compatible
WARNING: Candidate software combination not found in compatibility database
Determining whether installation is valid
WARNING: Candidate software combination not found in compatibility database
WARNING: Candidate software combination not found in compatibility database
Software sets are identified as compatible
Checking IPC compatibility with running software
Checking candidate package set infrastructure compatibility
Checking infrastructure compatibility with running software
Checking package specific compatibility
Finished compatibility testing
--- Starting impact testing ---
Checking operational impact of change
--- Starting commit of software changes ---
Updating provisioning rollback files
Creating pending provisioning file
Committing provisioning file
Finished commit of software changes
--- Starting analysis of software changes ---
Finished analysis of software changes
--- Starting update running software ---
Blocking peer synchronization of operating information
Creating the command set placeholder directory
Finding latest command set
Finding latest command shortlist lookup file
Finding latest command shortlist file
Assembling CLI output libraries
Assembling CLI input libraries
Applying interim IPC and database definitions
Replacing running software
Applying final IPC and database definitions
*Sep 29 15:12:18.972: %ASR1000_OIR-6-OFFLINECARD: Card (cc) offline in slot 0
*Sep 29 15:12:18.973: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 0/0, interfaces
disabled
*Sep 29 15:12:18.973: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 0/1, interfaces
disabled
*Sep 29 15:12:18.973: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 0/2, interfaces
disabled
*Sep 29 15:12:18.973: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 0/3, interfaces
disabled
*Sep 29 15:12:18.977: %SPA_OIR-6-OFFLINECARD: SPA (SPA-4XT-SERIAL) offline in subslot 0/0
*Sep 29 15:12:18.981: %SPA_OIR-6-OFFLINECARD: SPA (SPA-5X1GE-V2) offline in subslot 0/1
*Sep 29 15:12:18.985: %SPA_OIR-6-OFFLINECARD: SPA (SPA-2XOC3-POS) offline in subslot 0/2
*Sep 29 15:12:18.994: %SPA_OIR-6-OFFLINECARD: SPA (SPA-4XT-SERIAL) offline in subslot 0/3
*Sep 29 15:13:04.553: %ASR1000_OIR-6-ONLINECARD: Card (cc) online in slot 0
*Sep 29 15:13:06.051: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 0/0
*Sep 29 15:13:06.935: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 0/1
*Sep 29 15:13:07.765: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 0/2
*Sep 29 15:13:08.250: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 0/3 Generating
software version information
Notifying running software of updates
Unblocking peer synchronization of operating information
*Sep 29 15:13:14.936: %LINK-3-UPDOWN: SIP0/0: Interface EOBC0/1, changed state to up
*Sep 29 15:13:21.431: %FPD_MGMT-3-MISSING_DEV_INFO: Could not find Unknown FPD (
FPD ID=1) in the list of FPD IDs populated for SPA-4XT-SERIAL card in subslot 0/0.
*Sep 29 15:13:21.634: %SPA_OIR-6-ONLINECARD: SPA (SPA-4XT-SERIAL) online in subslot
0/0Cleaning temporary installation files
Finished update running software
SUCCESS: Finished installing software.
*Sep 29 15:13:21.967: %LINK-3-UPDOWN: Interface GigabitEthernet0/1/0, changed state to
down
*Sep 29 15:13:21.968: %LINK-3-UPDOWN: Interface GigabitEthernet0/1/2, changed state to
down
*Sep 29 15:13:21.969: %LINK-3-UPDOWN: Interface GigabitEthernet0/1/3, changed state to
down
*Sep 29 15:13:21.969: %LINK-3-UPDOWN: Interface GigabitEthernet0/1/4, changed state to
down
*Sep 29 15:13:20.772: %LINK-3-UPDOWN: SIP0/1: Interface EOBC0/1, changed state to up
FPD ID=1) in the list of FPD IDs populated for SPA-4XT-SERIAL card in subslot 0/3.
*Sep 29 15:13:26.364: %SPA_OIR-6-ONLINECARD: SPA (SPA-4XT-SERIAL) online in subslot 0/3
*Sep 29 15:13:25.347: %LINK-3-UPDOWN: SIP0/1: Interface GigabitEthernet0/1/0, changed
state to down
*Sep 29 15:13:25.567: %LINK-3-UPDOWN: SIP0/1: Interface GigabitEthernet0/1/2, changed
state to down
*Sep 29 15:13:26.141: %LINK-3-UPDOWN: SIP0/1: Interface GigabitEthernet0/1/3, changed
state to down
*Sep 29 15:13:26.603: %LINK-3-UPDOWN: SIP0/3: Interface EOBC0/1, changed state to up
*Sep 29 15:13:28.355: %LINK-3-UPDOWN: Interface Serial0/3/1, changed state to down
*Sep 29 15:13:27.112: %LINK-3-UPDOWN: SIP0/1: Interface GigabitEthernet0/1/4, changed
state to down
Router# issu commitversion
--- Starting installation changes ---
Cancelling rollback timer
Finished installation changes
SUCCESS: Installation changes committed
Router# issu loadversion rp 0 file
bootflash:asr1000rp1-{sipbase,sipspa}*02.02.01.122-33.XNB1*.pkg slot 1 force
--- Starting installation state synchronization ---
Finished installation state synchronization
--- Starting file path checking ---
Finished file path checking
--- Starting image file verification ---
Checking image file names
Verifying image file locations
Locating image files and validating name syntax
Inspecting image file types
Processing image file constraints
Creating candidate provisioning file
Finished image file verification
--- Starting candidate package set construction ---
Verifying existing software set
Processing candidate provisioning file
Constructing working set for candidate package set
Constructing working set for running package set
Constructing merge of running and candidate packages
Finished candidate package set construction
--- Starting compatibility testing ---
Determining whether candidate package set is compatible
WARNING: Candidate software combination not found in compatibility database
Determining whether installation is valid
Software sets are identified as compatible
Checking IPC compatibility with running software
Checking candidate package set infrastructure compatibility
Checking infrastructure compatibility with running software
Checking package specific compatibility
Finished compatibility testing
--- Starting impact testing ---
Checking operational impact of change
--- Starting commit of software changes ---
Updating provisioning rollback files
Creating pending provisioning file
Committing provisioning file
Finished commit of software changes
--- Starting analysis of software changes ---
Finished analysis of software changes
--- Starting update running software ---
Blocking peer synchronization of operating information
Creating the command set placeholder directory
Finding latest command set
Finding latest command shortlist lookup file
Finding latest command shortlist file
Assembling CLI output libraries
Assembling CLI input libraries
Applying interim IPC and database definitions
Replacing running software
Applying final IPC and database definitions
*Sep 29 15:17:29.883: %ASR1000_OIR-6-OFFLINECARD: Card (cc) offline in slot 1
*Sep 29 15:17:29.887: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 1/0, interfaces
disabled
*Sep 29 15:17:29.887: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 1/1, interfaces
disabled
*Sep 29 15:17:29.887: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 1/3, interfaces
disabled
*Sep 29 15:17:29.890: %SPA_OIR-6-OFFLINECARD: SPA (SPA-4X1FE-TX-V2) offline in subslot 1/0
*Sep 29 15:17:29.895: %SPA_OIR-6-OFFLINECARD: SPA (SPA-2X1GE-V2) offline in subslot 1/1
*Sep 29 15:17:29.898: %SPA_OIR-6-OFFLINECARD: SPA (SPA-1XOC12-POS) offline in subslot 1/3
*Sep 29 15:18:15.555: %ASR1000_OIR-6-ONLINECARD: Card (cc) online in slot 1
*Sep 29 15:18:16.939: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 1/0
*Sep 29 15:18:17.721: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 1/1
*Sep 29 15:18:18.065: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 1/3
*Sep 29 15:18:24.912: %LINK-3-UPDOWN: SIP1/0: Interface EOBC1/1, changed state to up
*Sep 29 15:18:27.856: %SPA_OIR-6-ONLINECARD: SPA (SPA-4X1FE-TX-V2) online in subslot 1/0
Generating software version information
Notifying running software of updates
Unblocking peer synchronization of operating information
*Sep 29 15:18:30.388: %LINK-3-UPDOWN: SIP1/1: Interface EOBC1/1, changed state to
upUnmounting old packages
*Sep 29 15:18:32.259: %SPA_OIR-6-ONLINECARD: SPA (SPA-2X1GE-V2) online in subslot 1/1
*Sep 29 15:18:33.572: %SPA_OIR-6-ONLINECARD: SPA (SPA-1XOC12-POS) online in subslot
1/3Cleaning temporary installation files
Finished update running software
SUCCESS: Finished installing software.
*Sep 29 15:18:34.066: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/0, changed state to
down
*Sep 29 15:18:34.281: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/1, changed state to
down
*Sep 29 15:18:35.068: %LINEPROTO-5-UPDOWN: Line protocol on Interface
GigabitEthernet1/1/0, changed state to down
*Sep 29 15:18:33.905: %LINK-3-UPDOWN: SIP1/3: Interface EOBC1/1, changed state to up
*Sep 29 15:18:34.625: %LINK-3-UPDOWN: SIP1/1: Interface GigabitEthernet1/1/0, changed
state to down
*Sep 29 15:18:35.293: %LINK-3-UPDOWN: SIP1/1: Interface GigabitEthernet1/1/1, changed
state to down
*Sep 29 15:18:38.950: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/0, changed state to up
*Sep 29 15:18:38.686: %LINK-3-UPDOWN: SIP1/1: Interface GigabitEthernet1/1/0, changed
state to up
*Sep 29 15:18:39.972: %LINEPROTO-5-UPDOWN: Line protocol on Interface
GigabitEthernet1/1/0, changed state to up
Router# issu commitversion
--- Starting installation changes ---
Cancelling rollback timer
Finished installation changes
SUCCESS: Installation changes committed
Router# issu loadversion rp 0 file
bootflash:asr1000rp1-{sipbase,sipspa}*02.02.01.122-33.XNB1*.pkg slot 2 force
--- Starting installation state synchronization ---
Finished installation state synchronization
--- Starting file path checking ---
Finished file path checking
--- Starting image file verification ---
Checking image file names
Verifying image file locations
Locating image files and validating name syntax
Inspecting image file types
Processing image file constraints
Creating candidate provisioning file
Finished image file verification
--- Starting candidate package set construction ---
Verifying existing software set
Processing candidate provisioning file
Constructing working set for candidate package set
Constructing working set for running package set
Constructing merge of running and candidate packages
Finished candidate package set construction
--- Starting compatibility testing ---
Determining whether candidate package set is compatible
WARNING: Candidate software combination not found in compatibility database
Determining whether installation is valid
Software sets are identified as compatible
Checking IPC compatibility with running software
Checking candidate package set infrastructure compatibility
Checking infrastructure compatibility with running software
Checking package specific compatibility
Finished compatibility testing
--- Starting impact testing ---
Checking operational impact of change
--- Starting commit of software changes ---
Updating provisioning rollback files
Creating pending provisioning file
Committing provisioning file
Finished commit of software changes
--- Starting analysis of software changes ---
Finished analysis of software changes
--- Starting update running software ---
Blocking peer synchronization of operating information
Creating the command set placeholder directory
Finding latest command set
Finding latest command shortlist lookup file
Finding latest command shortlist file
Assembling CLI output libraries
Assembling CLI input libraries
Applying interim IPC and database definitions
Replacing running software
Applying final IPC and database definitions
Generating software version information
Notifying running software of updates
Unblocking peer synchronization of operating information
Cleaning temporary installation files
Finished update running software
SUCCESS: Finished installing software.
Router# issu commitversion
--- Starting installation changes ---
Cancelling rollback timer
Finished installation changes
SUCCESS: Installation changes committed
Router# issu loadversion rp 0 file bootflash:asr1000rp1-espbase*02.02.01.122-33.XNB1*.pkg
slot 1
--- Starting installation state synchronization ---
Finished installation state synchronization
--- Starting file path checking ---
Finished file path checking
--- Starting image file verification ---
Checking image file names
Verifying image file locations
Locating image files and validating name syntax
Inspecting image file types
Processing image file constraints
Creating candidate provisioning file
Finished image file verification
--- Starting candidate package set construction ---
Verifying existing software set
Processing candidate provisioning file
Constructing working set for candidate package set
Constructing working set for running package set
Constructing merge of running and candidate packages
Finished candidate package set construction
--- Starting compatibility testing ---
Determining whether candidate package set is compatible
WARNING: Candidate software combination not found in compatibility database
Determining whether installation is valid
WARNING: Candidate software combination not found in compatibility database
WARNING: Candidate software combination not found in compatibility database
Software sets are identified as compatible
Checking IPC compatibility with running software
Checking candidate package set infrastructure compatibility
Checking infrastructure compatibility with running software
Checking package specific compatibility
Finished compatibility testing
--- Starting impact testing ---
Checking operational impact of change
--- Starting commit of software changes ---
Updating provisioning rollback files
Creating pending provisioning file
Committing provisioning file
Finished commit of software changes
--- Starting analysis of software changes ---
Finished analysis of software changes
--- Starting update running software ---
Blocking peer synchronization of operating information
Creating the command set placeholder directory
Finding latest command set
Finding latest command shortlist lookup file
Finding latest command shortlist file
Assembling CLI output libraries
Assembling CLI input libraries
Applying interim IPC and database definitions
Replacing running software
Applying final IPC and database definitions
003967: Oct 5 12:15:26.337 EDT: %CMRP-5-PRERELEASE_HARDWARE: R0/0: cmand: F1:0 is
pre-release hardware
003972: Oct 5 12:16:07.792 EDT: %CMRP-5-PRERELEASE_HARDWARE: R0/0: cmand: F1:0 is
pre-release hardware
003984: Oct 5 12:16:29.016 EDT: %IOSXE-3-PLATFORM: F0: cpp_cp: QFP:00 Thread:043
TS:00000014574807111078 %FWALL-3-HA_INVALID_MSG_RCVD: invalid version 65539 opcode b
-Traceback= 801e9f58 800fd87c 800d9489 801c28e9 801c46a6 801c4c2a 80020055 Generating
software version information
Notifying running software of updates
Unblocking peer synchronization of operating information
Cleaning temporary installation files
Finished update running software
SUCCESS: Finished installing software.
Router# issu commitversion
--- Starting installation changes ---
Cancelling rollback timer
Finished installation changes
SUCCESS: Installation changes committed
Router# issu loadversion rp 0 file bootflash:asr1000rp1-espbase.*02.02.01.122-33.XNB1*.pkg
slot 0
--- Starting installation state synchronization ---
Finished installation state synchronization
--- Starting file path checking ---
Finished file path checking
--- Starting image file verification ---
Checking image file names
Verifying image file locations
Locating image files and validating name syntax
Inspecting image file types
Processing image file constraints
Creating candidate provisioning file
Finished image file verification
--- Starting candidate package set construction ---
Verifying existing software set
Processing candidate provisioning file
Constructing working set for candidate package set
Constructing working set for running package set
Constructing merge of running and candidate packages
Finished candidate package set construction
--- Starting compatibility testing ---
Determining whether candidate package set is compatible
WARNING: Candidate software combination not found in compatibility database
Determining whether installation is valid
Software sets are identified as compatible
Checking IPC compatibility with running software
Checking candidate package set infrastructure compatibility
Checking infrastructure compatibility with running software
Checking package specific compatibility
Finished compatibility testing
--- Starting impact testing ---
Checking operational impact of change
--- Starting commit of software changes ---
Updating provisioning rollback files
Creating pending provisioning file
Committing provisioning file
Finished commit of software changes
--- Starting analysis of software changes ---
Finished analysis of software changes
--- Starting update running software ---
Blocking peer synchronization of operating information
Creating the command set placeholder directory
Finding latest command set
Finding latest command shortlist lookup file
Finding latest command shortlist file
Assembling CLI output libraries
Assembling CLI input libraries
Applying interim IPC and database definitions
Replacing running software
Applying final IPC and database definitions
004324: Oct 5 12:31:20.470 EDT: %CMRP-5-PRERELEASE_HARDWARE: R0/0: cmand: F0:0 is
pre-release hardware
004327: Oct 5 12:32:02.485 EDT: %CMRP-5-PRERELEASE_HARDWARE: R0/0: cmand: F0:0 is
pre-release hardware Generating software version information
Notifying running software of updates
Unblocking peer synchronization of operating information
Cleaning temporary installation files
Finished update running software
SUCCESS: Finished installing software.
Router# issu commitversion
--- Starting installation changes ---
Cancelling rollback timer
Finished installation changes
SUCCESS: Installation changes committed
Router# issu loadversion rp 0 file bootflash:asr1000rp1*02.02.01.122-33.XNB1*.pkg force
--- Starting installation state synchronization ---
Finished installation state synchronization
--- Starting file path checking ---
Finished file path checking
--- Starting image file verification ---
Checking image file names
Verifying image file locations
Locating image files and validating name syntax
Inspecting image file types
WARNING: In-service installation of IOSD package
WARNING: requires software redundancy on target RP
WARNING: or on-reboot parameter
WARNING: Automatically setting the on-reboot flag
WARNING: In-service installation of RP Base package
WARNING: requires software reboot of target RP
Processing image file constraints
Creating candidate provisioning file
Finished image file verification
--- Starting candidate package set construction ---
Verifying existing software set
Processing candidate provisioning file
Constructing working set for candidate package set
Constructing working set for running package set
Constructing merge of running and candidate packages
Finished candidate package set construction
--- Starting compatibility testing ---
Determining whether candidate package set is compatible
Determining whether installation is valid
Determining whether installation is valid ... skipped
Checking IPC compatibility for candidate software
Checking candidate package set infrastructure compatibility
Checking infrastructure compatibility with running software
Checking infrastructure compatibility with running software ... skipped
Checking package specific compatibility
Finished compatibility testing
--- Starting commit of software changes ---
Updating provisioning rollback files
Creating pending provisioning file
Committing provisioning file
Finished commit of software changes
SUCCESS: Software provisioned. New software will load on reboot.
Router# show version r0 provisioned
Package: Provisioning File, version: n/a, status: active
File: bootflash:packages.conf, on: RP0
File SHA1 checksum: aca136bd8bcb99f87e6aa7a0ce2a92a3b5a5a200
Package: rpbase, version: BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1,
status: active
File:
bootflash:asr1000rp1-rpbase.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_
1.pkg, on: RP0
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: 32b3fceaf59e3acd7cf9937ef33a822d6b359887
Package: rpaccess, version:
BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: active
File:
bootflash:asr1000rp1-rpaccess.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_010
0_1.pkg, on: RP0
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: 7c8dfdf9b2e3602b0c6c531a88dd93c8d2d180c6
Package: rpcontrol, version:
BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: active
File:
bootflash:asr1000rp1-rpcontrol.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_01
00_1.pkg, on: RP0/0
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: a544cd10841b237066ccbc4714f4e23c00a9d2e5
Package: rpios-adventerprisek9, version:
BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: active
File:
bootflash:asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST
_20080924_0100_1.pkg, on: RP0/0
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: a4967ac35d6ac37ef275b28e032773762be9f202
Package: rpcontrol, version:
BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: inactive
File:
bootflash:asr1000rp1-rpcontrol.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_01
00_1.pkg, on: RP0/1
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: a544cd10841b237066ccbc4714f4e23c00a9d2e5
Package: rpios-adventerprisek9, version:
BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: inactive
File:
bootflash:asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST
_20080924_0100_1.pkg, on: RP0/1
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: a4967ac35d6ac37ef275b28e032773762be9f202
Package: rpbase, version: BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1,
status: active
File:
bootflash:asr1000rp1-rpbase.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_
1.pkg, on: RP1
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: 32b3fceaf59e3acd7cf9937ef33a822d6b359887
Package: rpaccess, version:
BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: active
File:
bootflash:asr1000rp1-rpaccess.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_010
0_1.pkg, on: RP1
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: 7c8dfdf9b2e3602b0c6c531a88dd93c8d2d180c6
Package: rpcontrol, version:
BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: active
File:
bootflash:asr1000rp1-rpcontrol.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_01
00_1.pkg, on: RP1/0
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: a544cd10841b237066ccbc4714f4e23c00a9d2e5
Package: rpios-adventerprisek9, version:
BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: active
File:
bootflash:asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST
_20080924_0100_1.pkg, on: RP1/0
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: a4967ac35d6ac37ef275b28e032773762be9f202
Package: rpcontrol, version:
BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: inactive
File:
bootflash:asr1000rp1-rpcontrol.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_01
00_1.pkg, on: RP1/1
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: a544cd10841b237066ccbc4714f4e23c00a9d2e5
Package: rpios-adventerprisek9, version:
BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: inactive
File:
bootflash:asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST
_20080924_0100_1.pkg, on: RP1/1
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: a4967ac35d6ac37ef275b28e032773762be9f202
Package: rpios-adventerprisek9, version: unknown, status: active
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: active
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: active
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: active
File: unknown, on: SIP0/0
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: active
File: unknown, on: SIP0/1
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: active
File: unknown, on: SIP0/2
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: active
File: unknown, on: SIP0/3
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: active
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: active
File: unknown, on: SIP1/0
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: active
File: unknown, on: SIP1/1
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: inactive
File: unknown, on: SIP1/2
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: active
File: unknown, on: SIP1/3
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: inactive
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: inactive
File: unknown, on: SIP2/0
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: inactive
File: unknown, on: SIP2/1
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: inactive
File: unknown, on: SIP2/2
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: inactive
File: unknown, on: SIP2/3
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Router# show version r1 provisioned
Package: Provisioning File, version: n/a, status: active
File: bootflash:packages.conf, on: RP0
File SHA1 checksum: aca136bd8bcb99f87e6aa7a0ce2a92a3b5a5a200
Package: rpbase, version: BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1,
status: active
File:
bootflash:asr1000rp1-rpbase.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_
1.pkg, on: RP0
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: 32b3fceaf59e3acd7cf9937ef33a822d6b359887
Package: rpaccess, version:
BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: active
File:
bootflash:asr1000rp1-rpaccess.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_010
0_1.pkg, on: RP0
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: 7c8dfdf9b2e3602b0c6c531a88dd93c8d2d180c6
Package: rpcontrol, version:
BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: active
File:
bootflash:asr1000rp1-rpcontrol.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_01
00_1.pkg, on: RP0/0
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: a544cd10841b237066ccbc4714f4e23c00a9d2e5
Package: rpios-adventerprisek9, version:
BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: active
File:
bootflash:asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST
_20080924_0100_1.pkg, on: RP0/0
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: a4967ac35d6ac37ef275b28e032773762be9f202
Package: rpcontrol, version:
BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: inactive
File:
bootflash:asr1000rp1-rpcontrol.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_01
00_1.pkg, on: RP0/1
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: a544cd10841b237066ccbc4714f4e23c00a9d2e5
Package: rpios-adventerprisek9, version:
BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: inactive
File:
bootflash:asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST
_20080924_0100_1.pkg, on: RP0/1
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: a4967ac35d6ac37ef275b28e032773762be9f202
Package: rpbase, version: BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1,
status: active
File:
bootflash:asr1000rp1-rpbase.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_
1.pkg, on: RP1
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: 32b3fceaf59e3acd7cf9937ef33a822d6b359887
Package: rpaccess, version:
BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: active
File:
bootflash:asr1000rp1-rpaccess.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_010
0_1.pkg, on: RP1
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: 7c8dfdf9b2e3602b0c6c531a88dd93c8d2d180c6
Package: rpcontrol, version:
BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: active
File:
bootflash:asr1000rp1-rpcontrol.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_01
00_1.pkg, on: RP1/0
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: a544cd10841b237066ccbc4714f4e23c00a9d2e5
Package: rpios-adventerprisek9, version:
BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: active
File:
bootflash:asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST
_20080924_0100_1.pkg, on: RP1/0
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: a4967ac35d6ac37ef275b28e032773762be9f202
Package: rpcontrol, version:
BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: inactive
File:
bootflash:asr1000rp1-rpcontrol.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_01
00_1.pkg, on: RP1/1
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: a544cd10841b237066ccbc4714f4e23c00a9d2e5
Package: rpios-adventerprisek9, version:
BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: inactive
File:
bootflash:asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST
_20080924_0100_1.pkg, on: RP1/1
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: a4967ac35d6ac37ef275b28e032773762be9f202
Package: rpios-adventerprisek9, version: unknown, status: active
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: active
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: active
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: inactive
File: unknown, on: SIP0/0
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: inactive
File: unknown, on: SIP0/1
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: inactive
File: unknown, on: SIP0/2
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: inactive
File: unknown, on: SIP0/3
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: active
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: inactive
File: unknown, on: SIP1/0
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: inactive
File: unknown, on: SIP1/1
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: inactive
File: unknown, on: SIP1/2
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: inactive
File: unknown, on: SIP1/3
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: inactive
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: inactive
File: unknown, on: SIP2/0
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: inactive
File: unknown, on: SIP2/1
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: inactive
File: unknown, on: SIP2/2
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: inactive
File: unknown, on: SIP2/3
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Router# redundancy force-switchover
Proceed with switchover to standby RP? [confirm]
*Sep 25 19:38:33.562: %SYS-5-SWITCHOVER: Switchover requested by Exec. Reason: redundancy
force-switchover
Router# request platform software package clean
Cleaning up unnecessary package files
No path specified, will use booted path bootflash:packages.conf
Scanning boot directory for packages ... done.
Preparing packages list to delete ...
asr1000rp1-espbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg
File is in use, will not delete.
asr1000rp1-espbase.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg
File is in use, will not delete.
asr1000rp1-rpaccess.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg
File is in use, will not delete.
asr1000rp1-rpbase.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg
File is in use, will not delete.
asr1000rp1-rpcontrol.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg
File is in use, will not delete.
asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_
0100_1.pkg
File is in use, will not delete.
asr1000rp1-sipbase.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg
File is in use, will not delete.
asr1000rp1-sipspa.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg
File is in use, will not delete.
File is in use, will not delete.
Files that will be deleted:
asr1000-rommon.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg
asr1000-rommon.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg
asr1000rp1-adventerprisek9.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.bin
asr1000rp1-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1
.bin
asr1000rp1-packages-adventerprisek9.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100
_1.conf
asr1000rp1-packages-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_200809
24_0100_1.conf
asr1000rp1-rpaccess.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg
asr1000rp1-rpbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg
asr1000rp1-rpcontrol.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg
asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.
pkg
asr1000rp1-sipbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg
asr1000rp1-sipspa.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg
Do you want to proceed? [confirm]y
Deleting file
bootflash:asr1000-rommon.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg ...
done.
Deleting file
bootflash:asr1000-rommon.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.p
kg ... done.
Deleting file
bootflash:asr1000rp1-adventerprisek9.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_010
0_1.bin ... done.
Deleting file
bootflash:asr1000rp1-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080
924_0100_1.bin ... done.
Deleting file
bootflash:asr1000rp1-packages-adventerprisek9.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_200
80924_0100_1.conf ... done.
Deleting file
bootflash:asr1000rp1-packages-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LAT
EST_20080924_0100_1.conf ... done.
Deleting file
bootflash:asr1000rp1-rpaccess.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg
... done.
Deleting file
bootflash:asr1000rp1-rpbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg
... done.
Deleting file
bootflash:asr1000rp1-rpcontrol.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pk
g ... done.
Deleting file
bootflash:asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_200809
24_0100_1.pkg ... done.
Deleting file
bootflash:asr1000rp1-sipbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg
... done.
Deleting file
bootflash:asr1000rp1-sipspa.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg
... done.
Deleting file bootflash:packages.conf.00- ... done.
Deleting file bootflash:packages.conf.01- ... done.
Deleting file bootflash:packages.conf.02- ... done.
Deleting file bootflash:packages.conf.03- ... done.
Deleting file bootflash:packages.conf.04- ... done.
Using ISSU to Upgrade SubPackages on a Cisco ASR 1006 Router or ASR 1013 Router (request platform command set)
This procedure can only be performed if the current ASR 1006 router or ASR 1013 router has two active RPs and both RPs are running subpackages.
To perform an ISSU upgrade using subpackages on a Cisco ASR 1006 router or ASR 1013 router with a dual RP setup using the request platform command set, follow the following instructions.
SUMMARY STEPS
1.
show version
show version active-rp installed
show version standby-rp installed
dir filesystem:<directory>
show platform
2.
mkdir URL-to-directory-name
3.
ip tftp source-interface gigabitethernet slot/port
4.
copy tftp: URL-to-target-location
5.
request platform software package expand file URL-to-consolidated-package
6.
dir URL-to-consolidated-package
7.
copy file-system:asr1000rp1-espbase.version.pkg URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1000rp1-rpaccess.version.pkg URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1000rp1-rpbase.version.pkg URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1000rp1-rpcontrol.version.pkg URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1000rp1-rpios.version.pkg URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1000rp1-sipbase.version.pkg URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1000rp1-sipspa.version.pkg URL-to-directory-of-sub-packages-active-RP
8.
copy file-system:asr1000rp1-espbase.version.pkg URL-to-directory-of-sub-packages-standby-RP
copy file-system:asr1000rp1-rpaccess.version.pkg URL-to-directory-of-sub-packages-standby-RP
copy file-system:asr1000rp1-rpbase.version.pkg URL-to-directory-of-sub-packages-standby-RP
copy file-system:asr1000rp1-rpcontrol.version.pkg URL-to-directory-of-sub-packages-standby-RP
copy file-system:asr1000rp1-rpios.version.pkg URL-to-directory-of-sub-packages-standby-RP
copy file-system:asr1000rp1-sipbase.version.pkg URL-to-directory-of-sub-packages-standby-RP
copy file-system:asr1000rp1-sipspa.version.pkg URL-to-directory-of-sub-packages-standby-RP
9.
request platform software package install rp standby-RP file URL-to-standby-file-system:asr1000rp*version*.pkg force
10.
hw-module slot standby-RP reload
11.
request platform software package install rp active-RP file URL-to-active-file-system:image slot SIP-slot-number force
Repeat this step for each SIP installed in the router before moving onto the next step.
12.
request platform software package install rp active-RP file URL-to-active-file-system:asr1000rp1-esp*version*.pkg slot standby-ESP-slot
request platform software package install rp active-RP file URL-to-active-file-system:asr1000rp1-esp*version*.pkg slot active-ESP-slot
13.
request platform software package install rp active-RP file URL-to-active-file-system:asr1000rp*version*.pkg force
14.
show version active-RP provisioned
show version active-RP installed
15.
redundancy force-switchover
16.
request platform software package clean
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
show version
show version active-rp installed
show version standby-rp installed
dir filesystem:<directory>
show platform
Example:
Router# show version
Router# show version r0 installed
Router# show version r1 installed
Router# dir bootflash:
Router# show platform
|
(Optional) Use the following commands to confirm the current router configuration, as follows:
• show version and show version active-rp installed—Verify the running version of the Cisco IOS XE software on the router, and which file was used to boot the router, and where that file is stored.
• dir—Confirm that the files that were used to boot the router are located in the directory.
• show platform—Confirm the current status of the active and standby RPs.
|
Step 2
|
mkdir URL-to-directory-name
Example:
Router# mkdir usb0:221subs
|
Creates a directory to store the consolidated package and subpackages.
This directory must be created in most cases because the consolidated packages and subpackages have to be separated from the subpackages that booted the router at this step of the procedure.
|
Step 3
|
ip tftp source-interface gigabitethernet slot/port
Example:
Router(config)# ip tftp source-interface
gigabitethernet 0
|
Specifies the Gigabit Ethernet TFTP source-interface to be configured:
slot/port—Specifies the location of the TFTP source-interface.
Note To copy a file using TFTP through the Management Ethernet interface, the ip tftp source-interface GigabitEthernet 0 command must be entered before entering the copy tftp command.
|
Step 4
|
copy tftp: URL-to-target-location
Example:
Router# copy tftp: usb0:221subs
|
Copies the consolidated package file into the directory created in Step 2.
The consolidated package in this step should not be copied into the same directory where the subpackages that are currently running your router are stored (the directory containing the packages.conf provisioning file from which the router was booted).
Tip  It is recommended that you copy the package onto a usb: or harddisk: file system for space considerations when performing this step of the procedure.
|
Step 5
|
request platform software package expand file
URL-to-consolidated-package
Example:
Router# request platform software package
expand file
usb0:221subs/asr1000rp1-adventerprisek9.02.02.0
1.122-33.XNB1.bin
|
Extracts the subpackages out of the consolidated package file into the temporary directory.
Note Take extra care to extract the subpackages to a temporary subdirectory and do not delete any of the files currently running the router at this point of the procedure.
To erase the files that were running on the router before the ISSU upgrade, enter the request platform software package clean command after the ISSU upgrade has been completed.
|
Step 6
|
dir target-URL
Example:
Router# dir usb0:221subs
|
(Optional) Displays the directory to confirm that the files were extracted.
|
Step 7
|
copy file-system:asr1000rp1-espbase.version.pkg
URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1000rp1-rpaccess.version.pkg
URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1000rp1-rpbase.version.pkg
URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1000rp1-rpcontrol.version.pkg
URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1000rp1-rpios.version.pkg
URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1000rp1-sipbase.version.pkg
URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1000rp1-sipspa.version.pkg
URL-to-directory-of-sub-packages-active-RP
Example:
Router# copy
usb0:221subs/asr1000rp1-espbase.02.02.01.122-33
.XNB1.pkg bootflash:
Router# copy
usb0:221subs/asr1000rp1-rpaccess.02.02.01.122-3
3.XNB1.pkg bootflash:
Router# copy
usb0:221subs/asr1000rp1-rpbase.02.02.01.122-33.
XNB1.pkg bootflash:
Router# copy
usb0:221subs/asr1000rp1-rpcontrol.02.02.01.122-
33.XNB1.pkg bootflash:
Router# copy
usb0:221subs/asr1000rp1-rpios-adventerprisek9.0
2.02.01.122-33.XNB1.pkg bootflash:
Router# copy
usb0:221subs/asr1000rp1-sipbase.02.02.01.122-33
.XNB1.pkg bootflash:
Router# copy
usb0:221subs/asr1000rp1-sipspa.02.02.01.122-33.
XNB1.pkg bootflash:
|
Copies the subpackages out of the temporary directory into the directory on the router where the subpackages running the active RP are currently stored.
|
Step 8
|
copy file-system:asr1000rp1-espbase.version.pkg
URL-to-directory-of-sub-packages-standby-RP
copy file-system:asr1000rp1-rpaccess.version.pkg
URL-to-directory-of-sub-packages-standby-RP
copy file-system:asr1000rp1-rpbase.version.pkg
URL-to-directory-of-sub-packages-standby-RP
copy file-system:asr1000rp1-rpcontrol.version.pkg
URL-to-directory-of-sub-packages-standby-RP
copy file-system:asr1000rp1-rpios.version.pkg
URL-to-directory-of-sub-packages-standby-RP
copy file-system:asr1000rp1-sipbase.version.pkg
URL-to-directory-of-sub-packages-standby-RP
copy file-system:asr1000rp1-sipspa.version.pkg
URL-to-directory-of-sub-packages-standby-RP
Example:
Router# copy
usb0:221subs/asr1000rp1-espbase.02.02.01.122-33
.XNB1.pkg stby-bootflash:
Router# copy
usb0:221subs/asr1000rp1-rpaccess.02.02.01.122-3
3.XNB1.pkg stby-bootflash:
Router# copy
usb0:221subs/asr1000rp1-rpbase.02.02.01.122-33.
XNB1.pkg stby-bootflash:
Router# copy
usb0:221subs/asr1000rp1-rpcontrol.02.02.01.122-
33.XNB1.pkg stby-bootflash:
Router# copy
usb0:221subs/asr1000rp1-rpios-adventerprisek9.0
2.02.01.122-33.XNB1.pkg stby-bootflash:
Router# copy
usb0:221subs/asr1000rp1-sipbase.02.02.01.122-33
.XNB1.pkg stby-bootflash:
Router# copy
usb0:221subs/asr1000rp1-sipspa.02.02.01.122-33.
XNB1.pkg stby-bootflash:
|
Copies the subpackages out of the temporary directory into the directory on the router where the subpackages running the standby RP are currently stored.
|
Step 9
|
request platform software package install rp
standby-RP file
target-standbyRP-URL-for-sub-packages:asr1000rp*
version*.pkg force
Example:
Router# request platform software package
install rp 1 file
stby-bootflash:asr1000rp*02.02.01.122-33.XNB1*.
pkg force
|
Upgrades the RP subpackages on the standby RP, where the "rp*" wildcard is specified to capture all of the RP subpackages for the desired upgrade release.
|
Step 10
|
hw-module slot standby-RP reload
Example:
Router# hw-module slot R1 reload
|
Reloads the standby RP.
|
Step 11
|
request platform software package install rp
active-RP file
URL-to-active-file-system:asr1000rp1-{sipbase,sip
spa}*version*.pkg slot SIP-slot-number force
Repeat this step for each SIP installed in the
router before moving onto the next step.
Example:
Router# request platform software package
install rp 0 file
bootflash:asr1000rp1-{sipbase,sipspa}*02.02.01.
122-33.XNB1*.pkg slot 0 force
Router# request platform software package
install rp 0 file
bootflash:asr1000rp1-{sipbase,sipspa}*02.02.01.
122-33.XNB1*.pkg slot 1 force
Router# request platform software package
install rp 0 file
bootflash:asr1000rp1-{sipbase,sipspa}*02.02.01.
122-33.XNB1*.pkg slot 2 force
|
Upgrades the SIP and SPA subpackages for each SIP on the router.
Note This step must be completed one SIP at a time, and repeated for each SIP installed on the router before performing the next step.
Tip  You can use the show ip interface brief command to identify which slots contain SIPs and SPAs. The interfaces with three numbers (in the form SIP-number/SPA-number/interface-number) identify the SIP and SPA locations in the router.
Note The pattern options used in this CLI (sipbase and sipspa) were introduced in Cisco IOS XE Release 2.1.2 and are not available in previous Cisco IOS XE Releases. See the "ISSU Procedures (Prior to Cisco IOS XE Release 2.1.2)" section for pre-Cisco IOS XE Release 2.1.2 ISSU upgrade procedures.
|
Step 12
|
request platform software package install rp
active-RP file
URL-to-active-file-system:asr1000rp1-esp*version*.
pkg slot standby-ESP-slot
request platform software package install rp
active-RP file
URL-to-active-file-system:asr1000rp1-esp*version*.
pkg slot active-ESP-slot
Example:
Router# request platform software package
install rp 0 file
bootflash:asr1000rp1-esp*02.02.01.122-33.XNB1*.
pkg slot 1
Router# request platform software package
install rp 0 file
bootflash:asr1000rp1-esp*02.02.01.122-33.XNB1*.
pkg slot 0
|
Upgrades the ESP Base subpackage on the standby and the active ESPs.
After entering the issu loadversion rp command on the active RP, the ESP switchover will occur automatically. Minimal traffic interruption will occur as a result of this switchover.
|
Step 13
|
request platform software package install rp
active-RP file
URL-to-active-file-system:asr1000rp*version*.pkg
force
Example:
Router# request platform software package
install rp 0 file
bootflash:asr1000rp1*02.02.01.122-33.XNB1*.pkg
force
|
Upgrades all of the sub-packages on the active RP.
Note This step is required to ensure that all subpackages on the router were upgraded as part of this procedure, and might upgrade some subpackages that would otherwise be missed in the process.
|
Step 14
|
show version active-RP provisioned
show version active-RP installed
Example:
Router# show version r0 provisioned
Router# show version r0 installed
|
(Optional) Confirms the subpackages are provisioned and installed.
|
Step 15
|
redundancy force-switchover
Example:
Router# redundancy force-switchover
|
Forces an RP switchover to complete the upgrade.
|
Step 16
|
request platform software package clean
|
(Optional) Removes all unused subpackage files from the router.
|
Examples
This example shows ISSU upgrade using subpackages on a Cisco ASR 1006 router or ASR 1013 router with a dual RP setup:
Cisco IOS Software, IOS-XE Software (PPC_LINUX_IOSD-ADVENTERPRISEK9-M), Version
12.2(33)XNA, RELEASE SOFTWARE (fc1)
<output removed for brevity>
System image file is "bootflash:packages.conf"
<output removed for brevity>
Slot Type State Insert time (ago)
--------- ------------------- --------------------- -----------------
0 ASR1000-SIP10 ok 00:03:03
0/0 SPA-4XT-SERIAL ok 00:01:35
0/1 SPA-5X1GE-V2 ok 00:01:35
0/2 SPA-2XOC3-POS ok 00:01:36
0/3 SPA-4XT-SERIAL ok 00:01:35
1 ASR1000-SIP10 ok 00:03:03
1/0 SPA-4X1FE-TX-V2 ok 00:01:36
1/1 SPA-2X1GE-V2 ok 00:01:35
1/3 SPA-1XOC12-POS ok 00:01:36
R0 ASR1000-RP1 ok, active 00:03:03
R1 ASR1000-RP1 ok, standby 00:03:03
F0 ASR1000-ESP10 ok, active 00:03:03
F1 ASR1000-ESP10 ok, standby 00:03:03
P0 ASR1006-PWR-AC ok 00:02:07
P1 ASR1006-FAN ok 00:02:07
Slot CPLD Version Firmware Version
--------- ------------------- ---------------------------------------
Router# show version r0 installed
Package: Provisioning File, version: n/a, status: active
File: bootflash:packages.conf, on: RP0
File SHA1 checksum: 174bef13f7ce20af077bae7aaefb5279c790dd57
Package: rpbase, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: active
File:
bootflash:asr1000rp1-rpbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg,
on: RP0
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 661bcb2efda479533c87f23504bf7021d42b3165
Package: rpaccess, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: active
File:
bootflash:asr1000rp1-rpaccess.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg
, on: RP0
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: b0dc8e07cd4f997b045280fa79051e41068c6f3e
Package: rpcontrol, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: active
File:
bootflash:asr1000rp1-rpcontrol.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pk
g, on: RP0/0
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 258c79c9b9e67eb4c21dcb4c9b2fe8b8c1f96cfd
Package: rpios-adventerprisek9, version:
BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1, status: active
File:
bootflash:asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_200809
24_0100_1.pkg, on: RP0/0
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 88ea800ae1c094c46ca5e2f26d116f4e0012c219
Package: rpcontrol, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: inactive
File:
bootflash:asr1000rp1-rpcontrol.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pk
g, on: RP0/1
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 258c79c9b9e67eb4c21dcb4c9b2fe8b8c1f96cfd
Package: rpios-adventerprisek9, version:
BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1, status: inactive
File:
bootflash:asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_200809
24_0100_1.pkg, on: RP0/1
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 88ea800ae1c094c46ca5e2f26d116f4e0012c219
Package: rpbase, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: active
File:
bootflash:asr1000rp1-rpbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg,
on: RP1
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 661bcb2efda479533c87f23504bf7021d42b3165
Package: rpaccess, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: active
File:
bootflash:asr1000rp1-rpaccess.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg
, on: RP1
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: b0dc8e07cd4f997b045280fa79051e41068c6f3e
Package: rpcontrol, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: active
File:
bootflash:asr1000rp1-rpcontrol.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pk
g, on: RP1/0
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 258c79c9b9e67eb4c21dcb4c9b2fe8b8c1f96cfd
Package: rpios-adventerprisek9, version:
BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1, status: active
File:
bootflash:asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_200809
24_0100_1.pkg, on: RP1/0
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 88ea800ae1c094c46ca5e2f26d116f4e0012c219
Package: rpcontrol, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: inactive
File:
bootflash:asr1000rp1-rpcontrol.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pk
g, on: RP1/1
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 258c79c9b9e67eb4c21dcb4c9b2fe8b8c1f96cfd
Package: rpios-adventerprisek9, version:
BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1, status: inactive
File:
bootflash:asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_200809
24_0100_1.pkg, on: RP1/1
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 88ea800ae1c094c46ca5e2f26d116f4e0012c219
Package: espbase, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: active
File:
bootflash:asr1000rp1-espbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg,
on: ESP0
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: da8e5c93d0fa3f7cf27381841fa9efcde409964d
Package: espbase, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: active
File:
bootflash:asr1000rp1-espbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg,
on: ESP1
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: da8e5c93d0fa3f7cf27381841fa9efcde409964d
Package: sipbase, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: active
File:
bootflash:asr1000rp1-sipbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg,
on: SIP0
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 31b36be34aa63e0aafbb8abb2cc40a0cbcd5f68e
Package: sipspa, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: active
File:
bootflash:asr1000rp1-sipspa.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg,
on: SIP0/0
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 337c662bcea5d34736e6df3acf7d7cb2a0a8c2f7
Package: sipspa, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: active
File:
bootflash:asr1000rp1-sipspa.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg,
on: SIP0/1
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 337c662bcea5d34736e6df3acf7d7cb2a0a8c2f7
Package: sipspa, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: active
File:
bootflash:asr1000rp1-sipspa.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg,
on: SIP0/2
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 337c662bcea5d34736e6df3acf7d7cb2a0a8c2f7
Package: sipspa, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: active
File:
bootflash:asr1000rp1-sipspa.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg,
on: SIP0/3
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 337c662bcea5d34736e6df3acf7d7cb2a0a8c2f7
Package: sipbase, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: active
File:
bootflash:asr1000rp1-sipbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg,
on: SIP1
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 31b36be34aa63e0aafbb8abb2cc40a0cbcd5f68e
Package: sipspa, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: active
File:
bootflash:asr1000rp1-sipspa.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg,
on: SIP1/0
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 337c662bcea5d34736e6df3acf7d7cb2a0a8c2f7
Package: sipspa, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: active
File:
bootflash:asr1000rp1-sipspa.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg,
on: SIP1/1
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 337c662bcea5d34736e6df3acf7d7cb2a0a8c2f7
Package: sipspa, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: inactive
File:
bootflash:asr1000rp1-sipspa.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg,
on: SIP1/2
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 337c662bcea5d34736e6df3acf7d7cb2a0a8c2f7
Package: sipspa, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: active
File:
bootflash:asr1000rp1-sipspa.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg,
on: SIP1/3
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 337c662bcea5d34736e6df3acf7d7cb2a0a8c2f7
Package: sipbase, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: inactive
File:
bootflash:asr1000rp1-sipbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg,
on: SIP2
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 31b36be34aa63e0aafbb8abb2cc40a0cbcd5f68e
Package: sipspa, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: inactive
File:
bootflash:asr1000rp1-sipspa.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg,
on: SIP2/0
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 337c662bcea5d34736e6df3acf7d7cb2a0a8c2f7
Package: sipspa, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: inactive
File:
bootflash:asr1000rp1-sipspa.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg,
on: SIP2/1
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 337c662bcea5d34736e6df3acf7d7cb2a0a8c2f7
Package: sipspa, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: inactive
File:
bootflash:asr1000rp1-sipspa.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg,
on: SIP2/2
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 337c662bcea5d34736e6df3acf7d7cb2a0a8c2f7
Package: sipspa, version: BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1,
status: inactive
File:
bootflash:asr1000rp1-sipspa.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg,
on: SIP2/3
Built: 2008-09-24_03.46, by: mcpre
File SHA1 checksum: 337c662bcea5d34736e6df3acf7d7cb2a0a8c2f7
Router# mkdir usb0:221subs
Create directory filename [221subs]?
Created dir bootflash:221subs
Router(config)# ip tftp source-interface gigabitethernet 0
Router# copy tftp: usb0:221subs
Address or name of remote host []? 172.17.16.81
Source filename []? /auto/users/asr1000rp1-adventerprisek9.02.02.01.122-33.XNB1.bin
Destination filename [asr1000rp1-adventerprisek9.02.02.01.122-33.XNB1.bin]?
Accessing
tftp://172.17.16.81//auto/users/asr1000rp1-adventerprisek9.02.02.01.122-33.XNB1.bin...
Loading /auto/users/asr1000rp1-adventerprisek9.02.02.01.122-33.XNB1.bin from 172.17.16.81
(via GigabitEthernet0):
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!.!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!
209227980 bytes copied in 880.002 secs (237759 bytes/sec)
Router# request platform software package expand file
usb0:221subs/asr1000rp1-adventerprisek9.02.02.01.122-33.XNB1.bin
SUCCESS: Finished expanding all-in-one software package.
Directory of usb0:/221subs/
72013 -rw- 51904716 Oct 7 2008 15:46:02 -07:00
asr1000rp1-espbase.02.02.01.122-33.XNB1.pkg
72004 -rw- 5773 Oct 7 2008 15:46:02 -07:00
asr1000rp1-packages-adventerprisek9.02.02.01.122-33.XNB1.conf
72014 -rw- 20533452 Oct 7 2008 15:46:03 -07:00
asr1000rp1-rpaccess.02.02.01.122-33.XNB1.pkg
72015 -rw- 22388940 Oct 7 2008 15:46:03 -07:00
asr1000rp1-rpbase.02.02.01.122-33.XNB1.pkg
72016 -rw- 27961548 Oct 7 2008 15:46:03 -07:00
asr1000rp1-rpcontrol.02.02.01.122-33.XNB1.pkg
72017 -rw- 50942156 Oct 7 2008 15:46:03 -07:00
asr1000rp1-rpios-adventerprisek9.02.02.01.122-33.XNB1.pkg
72018 -rw- 36442316 Oct 7 2008 15:46:03 -07:00
asr1000rp1-sipbase.02.02.01.122-33.XNB1.pkg
72019 -rw- 26366156 Oct 7 2008 15:46:03 -07:00
asr1000rp1-sipspa.02.02.01.122-33.XNB1.pkg
72005 -rw- 6290 Oct 7 2008 15:46:03 -07:00 packages.conf
72003 -rw- 224768204 Oct 7 2008 15:38:57 -07:00
asr1000rp1-adventerprisek9.02.02.01.122-33.XNB1.bin
928862208 bytes total (466358272 bytes free)
Router# copy usb0:221subs/asr1000rp1-espbase.02.02.01.122-33.XNB1.pkg bootflash:
Destination filename [asr1000rp1-espbase.02.02.01.122-33.XNB1.pkg]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
51904716 bytes copied in 5.478 secs (9475122 bytes/sec)
Router# copy usb0:221subs/asr1000rp1-rpaccess.02.02.01.122-33.XNB1.pkg bootflash:
Destination filename [asr1000rp1-rpaccess.02.02.01.122-33.XNB1.pkg]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
20533452 bytes copied in 2.346 secs (8752537 bytes/sec)
Router# copy usb0:221subs/asr1000rp1-rpbase.02.02.01.122-33.XNB1.pkg bootflash:
Destination filename [asr1000rp1-rpbase.02.02.01.122-33.XNB1.pkg]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
22388940 bytes copied in 2.496 secs (8969928 bytes/sec)
Router# copy usb0:221subs/asr1000rp1-rpcontrol.02.02.01.122-33.XNB1.pkg bootflash:
Destination filename [asr1000rp1-rpcontrol.02.02.01.122-33.XNB1.pkg]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
27961548 bytes copied in 2.992 secs (9345437 bytes/sec)
Router# copy usb0:221subs/asr1000rp1-rpios-adventerprisek9.02.02.01.122-33.XNB1.pkg
bootflash:
Destination filename [asr1000rp1-rpios-adventerprisek9.02.02.01.122-33.XNB1.pkg]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
50942156 bytes copied in 5.719 secs (8907529 bytes/sec)
Router# copy usb0:221subs/asr1000rp1-sipbase.02.02.01.122-33.XNB1.pkg bootflash:
Destination filename [asr1000rp1-sipbase.02.02.01.122-33.XNB1.pkg]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCC
36442316 bytes copied in 3.906 secs (9329830 bytes/sec)
Router# copy usb0:221subs/asr1000rp1-sipspa.02.02.01.122-33.XNB1.pkg bootflash:
Destination filename [asr1000rp1-sipspa.02.02.01.122-33.XNB1.pkg]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
26366156 bytes copied in 2.857 secs (9228616 bytes/sec)
Router# copy usb0:221subs/asr1000rp1-espbase.02.02.01.122-33.XNB1.pkg stby-bootflash:
Destination filename [asr1000rp1-espbase.02.02.01.122-33.XNB1.pkg]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
51904716 bytes copied in 5.478 secs (9475122 bytes/sec)
Router# copy usb0:221subs/asr1000rp1-rpaccess.02.02.01.122-33.XNB1.pkg stby-bootflash:
Destination filename [asr1000rp1-rpaccess.02.02.01.122-33.XNB1.pkg]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
20533452 bytes copied in 2.346 secs (8752537 bytes/sec)
Router# copy usb0:221subs/asr1000rp1-rpbase.02.02.01.122-33.XNB1.pkg stby-bootflash:
Destination filename [asr1000rp1-rpbase.02.02.01.122-33.XNB1.pkg]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
22388940 bytes copied in 2.496 secs (8969928 bytes/sec)
Router# copy usb0:221subs/asr1000rp1-rpcontrol.02.02.01.122-33.XNB1.pkg stby-bootflash:
Destination filename [asr1000rp1-rpcontrol.02.02.01.122-33.XNB1.pkg]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
27961548 bytes copied in 2.992 secs (9345437 bytes/sec)
Router# copy usb0:221subs/asr1000rp1-rpios-adventerprisek9.02.02.01.122-33.XNB1.pkg
stby-bootflash:
Destination filename [asr1000rp1-rpios-adventerprisek9.02.02.01.122-33.XNB1.pkg]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
50942156 bytes copied in 5.719 secs (8907529 bytes/sec)
Router# copy usb0:221subs/asr1000rp1-sipbase.02.02.01.122-33.XNB1.pkg stby-bootflash:
Destination filename [asr1000rp1-sipbase.02.02.01.122-33.XNB1.pkg]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCC
36442316 bytes copied in 3.906 secs (9329830 bytes/sec)
Router# copy usb0:221subs/asr1000rp1-sipspa.02.02.01.122-33.XNB1.pkg stby-bootflash:
Destination filename [asr1000rp1-sipspa.02.02.01.122-33.XNB1.pkg]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
26366156 bytes copied in 2.857 secs (9228616 bytes/sec)
Router# request platform software package install rp 1 file
stby-bootflash:asr1000rp*02.02.01.122-33.XNB1*.pkg force
--- Starting installation state synchronization ---
Finished installation state synchronization
--- Starting file path checking ---
Finished file path checking
--- Starting image file verification ---
Checking image file names
Verifying image file locations
Locating image files and validating name syntax
Inspecting image file types
WARNING: In-service installation of IOSD package
WARNING: requires software redundancy on target RP
WARNING: or on-reboot parameter
WARNING: Automatically setting the on-reboot flag
WARNING: In-service installation of RP Base package
WARNING: requires software reboot of target RP
Processing image file constraints
Creating candidate provisioning file
Finished image file verification
--- Starting candidate package set construction ---
Verifying existing software set
Processing candidate provisioning file
Constructing working set for candidate package set
Constructing working set for running package set
Constructing merge of running and candidate packages
Finished candidate package set construction
--- Starting compatibility testing ---
Determining whether candidate package set is compatible
Determining whether installation is valid
Determining whether installation is valid ... skipped
Checking IPC compatibility for candidate software
Checking candidate package set infrastructure compatibility
Checking infrastructure compatibility with running software
Checking infrastructure compatibility with running software ... skipped
Checking package specific compatibility
Finished compatibility testing
--- Starting commit of software changes ---
Updating provisioning rollback files
Creating pending provisioning file
Committing provisioning file
Finished commit of software changes
SUCCESS: Software provisioned. New software will load on reboot.
Router# hw-module slot r1 reload
*Sep 25 18:20:15.371: %ASR1000_OIR-6-OFFLINECARD: Card (rp) offline in slot R1
*Sep 25 18:20:15.426: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault
(PEER_NOT_PRESENT)
*Sep 25 18:20:15.427: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER_DOWN)
*Sep 25 18:20:15.427: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault
(PEER_REDUNDANCY_STATE_CHANGE)
*Sep 25 18:22:58.808: %ASR1000_OIR-6-ONLINECARD: Card (rp) online in slot R1
*Sep 25 18:23:23.038: %REDUNDANCY-5-PEER_MONITOR_EVENT: Active detected a standby
insertion (raw-event=PEER_FOUND(4))
*Sep 25 18:23:23.039: %REDUNDANCY-5-PEER_MONITOR_EVENT: Active detected a standby
insertion (raw-event=PEER_REDUNDANCY_STATE_CHANGE(5))
*Sep 25 18:23:23.894: %REDUNDANCY-3-IPC: IOS versions do not match.
*Sep 25 18:24:54.264: %HA_CONFIG_SYNC-6-BULK_CFGSYNC_SUCCEED: Bulk Sync succeeded
*Sep 25 18:24:54.265: %RF-5-RF_TERMINAL_STATE: Terminal state reached for (SSO)Router#sho
Router#request platform software package install rp 0 file
bootflash:asr1000rp1-{sipspa,sipbase}*02.02.01.122-33.XNB1*.pkg slot 0 force
--- Starting installation state synchronization ---
Finished installation state synchronization
--- Starting file path checking ---
Finished file path checking
--- Starting image file verification ---
Checking image file names
Verifying image file locations
Locating image files and validating name syntax
Inspecting image file types
Processing image file constraints
Creating candidate provisioning file
Finished image file verification
--- Starting candidate package set construction ---
Verifying existing software set
Processing candidate provisioning file
Constructing working set for candidate package set
Constructing working set for running package set
Constructing merge of running and candidate packages
Finished candidate package set construction
--- Starting compatibility testing ---
Determining whether candidate package set is compatible
WARNING: Candidate software combination not found in compatibility database
Determining whether installation is valid
WARNING: Candidate software combination not found in compatibility database
WARNING: Candidate software combination not found in compatibility database
Software sets are identified as compatible
Checking IPC compatibility with running software
Checking candidate package set infrastructure compatibility
Checking infrastructure compatibility with running software
Checking package specific compatibility
Finished compatibility testing
--- Starting impact testing ---
Checking operational impact of change
--- Starting commit of software changes ---
Updating provisioning rollback files
Creating pending provisioning file
Committing provisioning file
Finished commit of software changes
--- Starting analysis of software changes ---
Finished analysis of software changes
--- Starting update running software ---
Blocking peer synchronization of operating information
Creating the command set placeholder directory
Finding latest command set
Finding latest command shortlist lookup file
Finding latest command shortlist file
Assembling CLI output libraries
Assembling CLI input libraries
Applying interim IPC and database definitions
Replacing running software
*Sep 29 13:48:03.269: %ASR1000_OIR-6-OFFLINECARD: Card (cc) offline in slot 0
*Sep 29 13:48:03.270: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 0/0, interfaces
disabled
*Sep 29 13:48:03.270: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 0/1, interfaces
disabled
*Sep 29 13:48:03.271: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 0/2, interfaces
disabled
*Sep 29 13:48:03.271: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 0/3, interfaces
disabled
*Sep 29 13:48:03.274: %SPA_OIR-6-OFFLINECARD: Applying final IPC and database
definitions
SPA (SPA-4XT-SERIAL) offline in subslot 0/0
*Sep 29 13:48:03.278: %SPA_OIR-6-OFFLINECARD: SPA (SPA-5X1GE-V2) offline in subslot 0/1
*Sep 29 13:48:03.282: %SPA_OIR-6-OFFLINECARD: SPA (SPA-2XOC3-POS) offline in subslot 0/2
*Sep 29 13:48:03.286: %SPA_OIR-6-OFFLINECARD: SPA (SPA-4XT-SERIAL) offline in subslot 0/3
*Sep 29 13:48:49.448: %ASR1000_OIR-6-ONLINECARD: Card (cc) online in slot 0
*Sep 29 13:48:50.872: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 0/0
*Sep 29 13:48:51.703: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 0/1
*Sep 29 13:48:52.680: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 0/2
*Sep 29 13:48:53.217: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 0/3 Generating
software version information
*Sep 29 13:49:01.223: %FPD_MGMT-3-MISSING_DEV_INFO: Could not find Unknown FPD (
FPD ID=1) in the list of FPD IDs populated for SPA-4XT-SERIAL card in subslot 0/0.
Notifying running software of updates
Unblocking peer synchronization of operating information
*Sep 29 13:49:01.336: %SPA_OIR-6-ONLINECARD: SPA (SPA-4XT-SERIAL) online in subslot 0/0
*Sep 29 13:49:03.344: %LINK-3-UPDOWN: Interface Serial0/0/2, changed state to
downUnmounting old packages
*Sep 29 13:48:59.734: %LINK-3-UPDOWN: SIP0/0: Interface EOBC0/1, changed state to
upCleaning temporary installation files
Finished update running software
SUCCESS: Finished installing software.
*Sep 29 13:49:05.151: %LINK-3-UPDOWN: SIP0/1: Interface EOBC0/1, changed state to up
*Sep 29 13:49:08.006: %SPA_OIR-6-ONLINECARD: SPA (SPA-5X1GE-V2) online in subslot 0/1
*Sep 29 13:49:09.086: %LINK-3-UPDOWN: Interface GigabitEthernet0/1/2, changed state to
down
*Sep 29 13:49:09.087: %LINK-3-UPDOWN: Interface GigabitEthernet0/1/3, changed state to
down
*Sep 29 13:49:09.087: %LINK-3-UPDOWN: Interface GigabitEthernet0/1/4, changed state to
down
*Sep 29 13:49:09.294: %SPA_OIR-6-ONLINECARD: SPA (SPA-2XOC3-POS) online in subslot 0/2
*Sep 29 13:49:09.580: %LINK-3-UPDOWN: Interface GigabitEthernet0/1/0, changed state to
down
*Sep 29 13:49:07.951: %LINK-3-UPDOWN: SIP0/2: Interface EOBC0/1, changed state to up
*Sep 29 13:49:10.067: %ASR1000_SPA-3-UNSUPPORTED_DATA: Data conversion error (media type,
0x1D)
-Traceback= 1#e9e10f82e25cfb5f8d242ef69a2dec39 :10000000+61C550 :10000000+61A6B
4 :10000000+61AA38 :10000000+25A3950 :10000000+259AB1C ethernet:DF73000+2AA6C if
_combined:FD4F000+70070 if_combined:FD4F000+70288 :10000000+2434540 :10000000+2433D9C
*Sep 29 13:49:10.070: %ASR1000_SPA-3-UNSUPPORTED_DATA: Data conversion error (media type,
0x1D)
-Traceback= 1#e9e10f82e25cfb5f8d242ef69a2dec39 :10000000+61C550 :10000000+61A6B
4 :10000000+61AA38 :10000000+25A3950 :10000000+259AB1C ethernet:DF73000+2AA6C if
_combined:FD4F000+70070 if_combined:FD4F000+70288 :10000000+2434540 :10000000+2433D9C
*Sep 29 13:49:11.161: %FPD_MGMT-3-MISSING_DEV_INFO: Could not find Unknown FPD (
FPD ID=1) in the list of FPD IDs populated for SPA-4XT-SERIAL card in subslot 0/3.
*Sep 29 13:49:11.289: %SPA_OIR-6-ONLINECARD: SPA (SPA-4XT-SERIAL) online in subslot 0/3
*Sep 29 13:49:11.605: %ASR1000_SPA-3-UNSUPPORTED_DATA: Data conversion error (media type,
0x1D)
-Traceback= 1#e9e10f82e25cfb5f8d242ef69a2dec39 :10000000+61C550 :10000000+61A6B
4 :10000000+61AA38 :10000000+25A3950 :10000000+259AB1C ethernet:DF73000+2AA6C if
_combined:FD4F000+70070 if_combined:FD4F000+70288 :10000000+2434540 :10000000+2433D9C
*Sep 29 13:49:10.788: %LINK-3-UPDOWN: SIP0/1: Interface GigabitEthernet0/1/0, changed
state to down
*Sep 29 13:49:11.114: %LINK-3-UPDOWN: SIP0/1: Interface GigabitEthernet0/1/2, changed
state to down
*Sep 29 13:49:11.217: %LINK-3-UPDOWN: SIP0/1: Interface GigabitEthernet0/1/3, changed
state to down
*Sep 29 13:49:11.530: %LINK-3-UPDOWN: SIP0/1: Interface GigabitEthernet0/1/4, changed
state to down
*Sep 29 13:49:10.567: %LINK-3-UPDOWN: SIP0/3: Interface EOBC0/1, changed state to up
*Sep 29 13:49:13.289: %LINK-3-UPDOWN: Interface Serial0/3/1, changed state to down
Router#request platform software package install rp 0 file
bootflash:asr1000rp1-{sipspa,sipbase}*02.02.01.122-33.XNB1*.pkg slot 1 force
--- Starting installation state synchronization ---
Finished installation state synchronization
--- Starting file path checking ---
Finished file path checking
--- Starting image file verification ---
Checking image file names
Verifying image file locations
Locating image files and validating name syntax
Inspecting image file types
Processing image file constraints
Creating candidate provisioning file
Finished image file verification
--- Starting candidate package set construction ---
Verifying existing software set
Processing candidate provisioning file
Constructing working set for candidate package set
Constructing working set for running package set
Constructing merge of running and candidate packages
Finished candidate package set construction
--- Starting compatibility testing ---
Determining whether candidate package set is compatible
WARNING: Candidate software combination not found in compatibility database
Determining whether installation is valid
Software sets are identified as compatible
Checking IPC compatibility with running software
Checking candidate package set infrastructure compatibility
Checking infrastructure compatibility with running software
Checking package specific compatibility
Finished compatibility testing
--- Starting impact testing ---
Checking operational impact of change
--- Starting commit of software changes ---
Updating provisioning rollback files
Creating pending provisioning file
Committing provisioning file
Finished commit of software changes
--- Starting analysis of software changes ---
Finished analysis of software changes
--- Starting update running software ---
Blocking peer synchronization of operating information
Creating the command set placeholder directory
Finding latest command set
Finding latest command shortlist lookup file
Finding latest command shortlist file
Assembling CLI output libraries
Assembling CLI input libraries
Applying interim IPC and database definitions
Replacing running software
Applying final IPC and database definitions
*Sep 29 13:53:01.370: %ASR1000_OIR-6-OFFLINECARD: Card (cc) offline in slot 1
*Sep 29 13:53:01.370: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 1/0, interfaces
disabled
*Sep 29 13:53:01.370: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 1/1, interfaces
disabled
*Sep 29 13:53:01.370: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 1/3, interfaces
disabled
*Sep 29 13:53:01.373: %SPA_OIR-6-OFFLINECARD: SPA (SPA-4X1FE-TX-V2) offline in subslot 1/0
*Sep 29 13:53:01.378: %SPA_OIR-6-OFFLINECARD: SPA (SPA-2X1GE-V2) offline in subslot 1/1
*Sep 29 13:53:01.381: %SPA_OIR-6-OFFLINECARD: SPA (SPA-1XOC12-POS) offline in subslot 1/3
*Sep 29 13:53:45.225: %ASR1000_OIR-6-ONLINECARD: Card (cc) online in slot 1
*Sep 29 13:53:47.082: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 1/0
*Sep 29 13:53:47.833: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 1/1
*Sep 29 13:53:48.727: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 1/3 Generating
software version information
Notifying running software of updates
Unblocking peer synchronization of operating information
*Sep 29 13:53:55.700: %LINK-3-UPDOWN: SIP1/0: Interface EOBC1/1, changed state to
upUnmounting old packages
*Sep 29 13:54:03.132: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/0, changed state to
down
*Sep 29 13:54:03.135: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/1, changed state to
down
*Sep 29 13:54:00.621: %LINK-3-UPDOWN: SIP1/1: Interface EOBC1/1, changed state to up
*Sep 29 13:54:03.449: %SPA_OIR-6-ONLINECARD: SPA (SPA-2X1GE-V2) online in subslot 1/1
*Sep 29 13:54:04.139: %LINEPROTO-5-UPDOWN: Line protocol on Interface
GigabitEthernet1/1/0, changed state to downCleaning temporary installation files
Finished update running software
SUCCESS: Finished installing software.
*Sep 29 13:54:04.320: %SPA_OIR-6-ONLINECARD: SPA (SPA-4X1FE-TX-V2) online in subslot 1/0
*Sep 29 13:54:05.911: %LINK-3-UPDOWN: SIP1/1: Interface GigabitEthernet1/1/0, changed
state to down
*Sep 29 13:54:06.243: %LINK-3-UPDOWN: SIP1/1: Interface GigabitEthernet1/1/1, changed
state to down
*Sep 29 13:54:03.492: %LINK-3-UPDOWN: SIP1/3: Interface EOBC1/1, changed state to up
*Sep 29 13:54:09.434: %SPA_OIR-6-ONLINECARD: SPA (SPA-1XOC12-POS) online in subslot 1/3
*Sep 29 13:54:10.427: %LINK-3-UPDOWN: Interface GigabitEthernet1/1/0, changed state to up
*Sep 29 13:54:09.709: %LINK-3-UPDOWN: SIP1/1: Interface GigabitEthernet1/1/0, changed
state to up
*Sep 29 13:54:11.445: %LINEPROTO-5-UPDOWN: Line protocol on Interface
GigabitEthernet1/1/0, changed state to up
Router# request platform software package install rp 0 file
bootflash:asr1000rp1-{sipspa,sipbase}*02.02.01.122-33.XNB1*.pkg slot 2 force
--- Starting installation state synchronization ---
Finished installation state synchronization
--- Starting file path checking ---
Finished file path checking
--- Starting image file verification ---
Checking image file names
Verifying image file locations
Locating image files and validating name syntax
Inspecting image file types
Processing image file constraints
Creating candidate provisioning file
Finished image file verification
--- Starting candidate package set construction ---
Verifying existing software set
Processing candidate provisioning file
Constructing working set for candidate package set
Constructing working set for running package set
Constructing merge of running and candidate packages
Finished candidate package set construction
--- Starting compatibility testing ---
Determining whether candidate package set is compatible
WARNING: Candidate software combination not found in compatibility database
Determining whether installation is valid
Software sets are identified as compatible
Checking IPC compatibility with running software
Checking candidate package set infrastructure compatibility
Checking infrastructure compatibility with running software
Checking package specific compatibility
Finished compatibility testing
--- Starting impact testing ---
Checking operational impact of change
--- Starting commit of software changes ---
Updating provisioning rollback files
Creating pending provisioning file
Committing provisioning file
Finished commit of software changes
--- Starting analysis of software changes ---
Finished analysis of software changes
--- Starting update running software ---
Blocking peer synchronization of operating information
Creating the command set placeholder directory
Finding latest command set
Finding latest command shortlist lookup file
Finding latest command shortlist file
Assembling CLI output libraries
Assembling CLI input libraries
Applying interim IPC and database definitions
Replacing running software
Applying final IPC and database definitions
Generating software version information
Notifying running software of updates
Unblocking peer synchronization of operating information
Cleaning temporary installation files
Finished update running software
SUCCESS: Finished installing software.
Router# request platform software package install rp 0 file
bootflash:asr1000rp1-espbase*02.02.01.122-33.XNB1*.pkg slot 1
--- Starting installation state synchronization ---
Finished installation state synchronization
--- Starting file path checking ---
Finished file path checking
--- Starting image file verification ---
Checking image file names
Verifying image file locations
Locating image files and validating name syntax
Inspecting image file types
Processing image file constraints
Creating candidate provisioning file
Finished image file verification
--- Starting candidate package set construction ---
Verifying existing software set
Processing candidate provisioning file
Constructing working set for candidate package set
Constructing working set for running package set
Constructing merge of running and candidate packages
Finished candidate package set construction
--- Starting compatibility testing ---
Determining whether candidate package set is compatible
WARNING: Candidate software combination not found in compatibility database
Determining whether installation is valid
WARNING: Candidate software combination not found in compatibility database
WARNING: Candidate software combination not found in compatibility database
Software sets are identified as compatible
Checking IPC compatibility with running software
Checking candidate package set infrastructure compatibility
Checking infrastructure compatibility with running software
Checking package specific compatibility
Finished compatibility testing
--- Starting impact testing ---
Checking operational impact of change
--- Starting commit of software changes ---
Updating provisioning rollback files
Creating pending provisioning file
Committing provisioning file
Finished commit of software changes
--- Starting analysis of software changes ---
Finished analysis of software changes
--- Starting update running software ---
Blocking peer synchronization of operating information
Creating the command set placeholder directory
Finding latest command set
Finding latest command shortlist lookup file
Finding latest command shortlist file
Assembling CLI output libraries
Assembling CLI input libraries
Applying interim IPC and database definitions
Replacing running software
Applying final IPC and database definitions
003967: Oct 5 12:15:26.337 EDT: %CMRP-5-PRERELEASE_HARDWARE: R0/0: cmand: F1:0 is
pre-release hardware
003972: Oct 5 12:16:07.792 EDT: %CMRP-5-PRERELEASE_HARDWARE: R0/0: cmand: F1:0 is
pre-release hardware
003984: Oct 5 12:16:29.016 EDT: %IOSXE-3-PLATFORM: F0: cpp_cp: QFP:00 Thread:043
TS:00000014574807111078 %FWALL-3-HA_INVALID_MSG_RCVD: invalid version 65539 opcode b
-Traceback= 801e9f58 800fd87c 800d9489 801c28e9 801c46a6 801c4c2a 80020055 Generating
software version information
Notifying running software of updates
Unblocking peer synchronization of operating information
Cleaning temporary installation files
Finished update running software
SUCCESS: Finished installing software.
Router# request platform software package install rp 0 file
bootflash:asr1000rp1-espbase.*02.02.01.122-33.XNB1*.pkg slot 0
--- Starting installation state synchronization ---
Finished installation state synchronization
--- Starting file path checking ---
Finished file path checking
--- Starting image file verification ---
Checking image file names
Verifying image file locations
Locating image files and validating name syntax
Inspecting image file types
Processing image file constraints
Creating candidate provisioning file
Finished image file verification
--- Starting candidate package set construction ---
Verifying existing software set
Processing candidate provisioning file
Constructing working set for candidate package set
Constructing working set for running package set
Constructing merge of running and candidate packages
Finished candidate package set construction
--- Starting compatibility testing ---
Determining whether candidate package set is compatible
WARNING: Candidate software combination not found in compatibility database
Determining whether installation is valid
Software sets are identified as compatible
Checking IPC compatibility with running software
Checking candidate package set infrastructure compatibility
Checking infrastructure compatibility with running software
Checking package specific compatibility
Finished compatibility testing
--- Starting impact testing ---
Checking operational impact of change
--- Starting commit of software changes ---
Updating provisioning rollback files
Creating pending provisioning file
Committing provisioning file
Finished commit of software changes
--- Starting analysis of software changes ---
Finished analysis of software changes
--- Starting update running software ---
Blocking peer synchronization of operating information
Creating the command set placeholder directory
Finding latest command set
Finding latest command shortlist lookup file
Finding latest command shortlist file
Assembling CLI output libraries
Assembling CLI input libraries
Applying interim IPC and database definitions
Replacing running software
Applying final IPC and database definitions
004324: Oct 5 12:31:20.470 EDT: %CMRP-5-PRERELEASE_HARDWARE: R0/0: cmand: F0:0 is
pre-release hardware
004327: Oct 5 12:32:02.485 EDT: %CMRP-5-PRERELEASE_HARDWARE: R0/0: cmand: F0:0 is
pre-release hardware Generating software version information
Notifying running software of updates
Unblocking peer synchronization of operating information
Cleaning temporary installation files
Finished update running software
SUCCESS: Finished installing software.
Router# request platform software package install rp 0 file
bootflash:asr1000rp1*02.02.01.122-33.XNB1*.pkg
--- Starting installation state synchronization ---
Finished installation state synchronization
--- Starting file path checking ---
Finished file path checking
--- Starting image file verification ---
Checking image file names
Verifying image file locations
Locating image files and validating name syntax
Inspecting image file types
WARNING: In-service installation of IOSD package
WARNING: requires software redundancy on target RP
WARNING: or on-reboot parameter
WARNING: Automatically setting the on-reboot flag
WARNING: In-service installation of RP Base package
WARNING: requires software reboot of target RP
Processing image file constraints
Creating candidate provisioning file
Finished image file verification
--- Starting candidate package set construction ---
Verifying existing software set
Processing candidate provisioning file
Constructing working set for candidate package set
Constructing working set for running package set
Constructing merge of running and candidate packages
Finished candidate package set construction
--- Starting compatibility testing ---
Determining whether candidate package set is compatible
Determining whether installation is valid
Determining whether installation is valid ... skipped
Checking IPC compatibility for candidate software
Checking candidate package set infrastructure compatibility
Checking infrastructure compatibility with running software
Checking infrastructure compatibility with running software ... skipped
Checking package specific compatibility
Finished compatibility testing
--- Starting commit of software changes ---
Updating provisioning rollback files
Creating pending provisioning file
Committing provisioning file
Finished commit of software changes
SUCCESS: Software provisioned. New software will load on reboot.
Router# show version r0 provisioned
Package: Provisioning File, version: n/a, status: active
File: bootflash:packages.conf, on: RP0
File SHA1 checksum: aca136bd8bcb99f87e6aa7a0ce2a92a3b5a5a200
Package: rpbase, version: BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1,
status: active
File:
bootflash:asr1000rp1-rpbase.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_
1.pkg, on: RP0
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: 32b3fceaf59e3acd7cf9937ef33a822d6b359887
Package: rpaccess, version:
BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: active
File:
bootflash:asr1000rp1-rpaccess.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_010
0_1.pkg, on: RP0
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: 7c8dfdf9b2e3602b0c6c531a88dd93c8d2d180c6
Package: rpcontrol, version:
BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: active
File:
bootflash:asr1000rp1-rpcontrol.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_01
00_1.pkg, on: RP0/0
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: a544cd10841b237066ccbc4714f4e23c00a9d2e5
Package: rpios-adventerprisek9, version:
BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: active
File:
bootflash:asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST
_20080924_0100_1.pkg, on: RP0/0
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: a4967ac35d6ac37ef275b28e032773762be9f202
Package: rpcontrol, version:
BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: inactive
File:
bootflash:asr1000rp1-rpcontrol.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_01
00_1.pkg, on: RP0/1
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: a544cd10841b237066ccbc4714f4e23c00a9d2e5
Package: rpios-adventerprisek9, version:
BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: inactive
File:
bootflash:asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST
_20080924_0100_1.pkg, on: RP0/1
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: a4967ac35d6ac37ef275b28e032773762be9f202
Package: rpbase, version: BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1,
status: active
File:
bootflash:asr1000rp1-rpbase.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_
1.pkg, on: RP1
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: 32b3fceaf59e3acd7cf9937ef33a822d6b359887
Package: rpaccess, version:
BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: active
File:
bootflash:asr1000rp1-rpaccess.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_010
0_1.pkg, on: RP1
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: 7c8dfdf9b2e3602b0c6c531a88dd93c8d2d180c6
Package: rpcontrol, version:
BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: active
File:
bootflash:asr1000rp1-rpcontrol.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_01
00_1.pkg, on: RP1/0
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: a544cd10841b237066ccbc4714f4e23c00a9d2e5
Package: rpios-adventerprisek9, version:
BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: active
File:
bootflash:asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST
_20080924_0100_1.pkg, on: RP1/0
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: a4967ac35d6ac37ef275b28e032773762be9f202
Package: rpcontrol, version:
BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: inactive
File:
bootflash:asr1000rp1-rpcontrol.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_01
00_1.pkg, on: RP1/1
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: a544cd10841b237066ccbc4714f4e23c00a9d2e5
Package: rpios-adventerprisek9, version:
BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: inactive
File:
bootflash:asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST
_20080924_0100_1.pkg, on: RP1/1
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: a4967ac35d6ac37ef275b28e032773762be9f202
Package: rpios-adventerprisek9, version: unknown, status: active
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: active
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: active
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: active
File: unknown, on: SIP0/0
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: active
File: unknown, on: SIP0/1
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: active
File: unknown, on: SIP0/2
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: active
File: unknown, on: SIP0/3
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: active
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: active
File: unknown, on: SIP1/0
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: active
File: unknown, on: SIP1/1
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: inactive
File: unknown, on: SIP1/2
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: active
File: unknown, on: SIP1/3
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: inactive
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: inactive
File: unknown, on: SIP2/0
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: inactive
File: unknown, on: SIP2/1
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: inactive
File: unknown, on: SIP2/2
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: inactive
File: unknown, on: SIP2/3
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
In Service One-Shot Software Upgrade Procedure
In service one-shot software upgrade procedure is an alternate to the standard ISSU procedure (see, ISSU Upgrade Procedures) that enables you to upgrade or downgrade software using a single command. One-shot ISSU needs minimal user intervention or monitoring. Unlike the standard ISSU procedures, once the upgrade is initiated, the upgrade process cannot be cancelled.
The one-shot upgrade procedure is divided into stages. When a failure occurs, the command execution is stalled and users have to perform the rollback tasks manually. Necessary switchovers are automatically taken care of in one of the upgrade stages. During a switchover, the console and its output are lost. Additional commands are used to connect back to the console.
Note
One-shot upgrade does not support multiple upgrades at the same time.
The command request platform software package install node file <consolidated file name> interface-module-delay <secs> is used for the one-shot ISSU procedure.
interface-module-delay is an optional parameter.
Example:
router#request platform software package install node file bootflash
interface-module-delay 1
The SIP-delay option enables you to delay the SIP restart duration thus enabling you to choose the restart time to minimize traffic loss.
The request platform software package install node file attach command enables the users to view the last run log that contains the reports of all the stages of the one-shot upgrade.
The request platform software package check file MDR command enables the users to initiate the ISSU procedure using MDR. For more information see, "Minimal Disruptive Restart Process" section.
ISSU Procedures (Prior to Cisco IOS XE Release 2.1.2)
These instructions should be followed only if you are upgrading using ISSU to a pre-Cisco IOS XE 2.1.2 release. If you are using Cisco IOS XE Release 2.2.1 or later, follow the earlier instructions in this chapter to perform your ISSU upgrade.
This section contains the following topics:
•
Using ISSU to Perform a Consolidated Package Upgrade in a Dual Route Processor Configuration (Prior to Cisco IOS XE 2.1.2)
•
Using ISSU to Upgrade SubPackages (Prior to Cisco IOS XE Release 2.1.2)
Using ISSU to Perform a Consolidated Package Upgrade in a Dual Route Processor Configuration (Prior to Cisco IOS XE 2.1.2)
This procedure is identical to the procedure used to upgrade post-Cisco IOS XE 2.2 images using ISSU.
See the "Using ISSU to Perform a Consolidated Package Upgrade in a Dual Route Processor Configuration" section for instructions on performing this process.
Using ISSU to Upgrade SubPackages (Prior to Cisco IOS XE Release 2.1.2)
This procedure will work on single RPs configured to run two IOS processes or on routers configured with dual RPs.
Versions of Cisco IOS XE Release 2.1 prior to Cisco IOS XE Release 2.1.2 and versions of Cisco IOS XE Release 2.2 prior to Cisco IOS XE Release 2.2.1 and installations not booted from the RPBase subpackage on Cisco IOS XE Release 2.2.1 or 2.1.2 require a different ISSU upgrade procedure.
Step 1
Copy all subpackages other than the RPBase subpackage into the same directory.
Step 2
Install the RP subpackages from the directory simultaneously by using a wildcard statement to capture all of the RP subpackages. This command should capture the RPControl, RPAccess, and RPIOS subpackages without capturing the RPBase subpackage and should be done using the standby bay.
Use the asr1000rp1-rp*version.pkg syntax instead of using the {pattern} syntax to complete this upgrade:
request platform software package install rp 1 file stby-bootflash:asr1000rp*02.02.01.122-33.XNB1*.pkg bay 1 force
Step 3
Wait for the system to reach SSO ready state. The show platform command can be used to monitor whether both IOS instances are active, and a system message will indicate SSO state has been reached.
Step 4
Use the redundancy force-switchover command to trigger an IOS switchover.
Step 5
Wait for the system to reach SSO ready state. Like in step 3, the state can be monitored by checking system messages or by entering the show platform command.
Step 6
Install the RP subpackages from the directory simultaneously by using a wildcard statement to capture all of the RP subpackages. This command should capture the RPControl, RPAccess, and RPIOS subpackages without capturing the RPBase subpackage and should be done using the standby bay.
Use the "asr1000rp1-rp*version.pkg syntax instead of using the {pattern} syntax to complete this upgrade:
request platform software package install rp 0 file
stby-bootflash:asr1000rp*02.02.01.122-33.XNB1*.pkg bay 0 force
Step 7
Install the SIPBASE and SIPSPA packages on each SIP:
Router# request platform software package install rp 0 file
bootflash:asr1000rp1-sip*02.02.01.122-33.XNB1*.pkg slot 0 force
Router# request platform software package install rp 0 file
bootflash:asr1000rp1-sip*02.02.01.122-33.XNB1*.pkg slot 1 force
Router# request platform software package install rp 0 file
bootflash:asr1000rp1-sip*02.02.01.122-33.XNB1*.pkg slot 2 force
Step 8
Install the ESPBASE package on the ESP:
Router# request platform software package install rp 0 file
bootflash:asr1000rp1-esp*02.02.01.122-33.XNB1*.pkg
Step 9
Copy the RPBase subpackage into the directory, then upgrade all of the RP subpackages simultaneously. This step will upgrade the RPBase subpackage, which is the last remaining subpackage that requires an upgrade:
request platform software package install rp 1 file
bootflash:asr1000rp*02.02.01.122-33.XNB1*.pkg force
Step 10
Enter show version provisioned to confirm that all of the software has been updated.
Step 11
Reload the router using the reload command when appropriate to complete the installation.
Downgrades in versions that do not support the {pattern} syntax are problematic because an
RPBASE package for the downgrade version will always be present if an upgrade was
previously performed. Removing and restaging all packages will work in this case, but they
effectively put the system into a state where if the RP reloads prior to the installation
being completed, the RP may no longer be bootable.
Upgrade Process With Service Impact for Nonredundant Platforms
Subpackage software upgrade is supported for nonredundant platforms such as Cisco ASR 1001 Router, Cisco ASR 1002, and ASR 1004 Routers in subpackage mode. This is because the software upgrade procedure on these chassis types requires an RP reload when upgrading the RPBase subpackage at the last step.
During the software upgrade process, there will be outage on the control plane as the entire platform is rebooted so that access to the router operating system and ROMmon is lost for a period of time.
For non-hardware-redundant chassis types, SIP impact can be mitigated by installing SIPs one slot at a time if SPAs are redundant across SIPs (such as when using Gigabit Etherchannel). ESP redundancy provides similar capability for the ESP allowing hitless upgrade of a chassis from one software release to another. Consolidated package mode does not provide such a per-slot staging option and always incurs a traffic loss equivalent to simultaneous OIR of all SIPs.
Note
The Cisco ASR 1002 and ASR 1002-F Routers come by default with 4-GB DRAM. The Cisco ASR 1001 Router comes by default with 4-GB DRAM, and is upgradeable up to 8-GB or 16-GB DRAM.
This section explains how to upgrade subpackages on a Cisco ASR 1001, 1002 or 1004 Router. It contains the following sections:
•
Configuring SSO on a Cisco ASR 1001, Cisco ASR 1002, or Cisco ASR 1004 Router
•
Using SubPackages for Software Upgrade on a Cisco ASR 1001 Router
•
Using SubPackages for Software Upgrade on a Cisco ASR 1002 or Cisco ASR 1004 Router (software upgrade Command Set)
•
Using SubPackages for Software Upgrade on a Cisco ASR 1002 or Cisco ASR 1004 Router (request platform Command Set)
Configuring SSO on a Cisco ASR 1001, Cisco ASR 1002, or Cisco ASR 1004 Router
The following instructions show how to configure SSO on a Cisco ASR 1001, Cisco ASR 1002, and Cisco ASR 1004 Routers. The standby IOS process is created automatically as part of these configuration steps.
Step 1
(Optional) Enter the show version command to confirm the amount of DRAM on your router:
<some output removed for brevity>
32768K bytes of non-volatile configuration memory.
4194304K bytes of physical memory.
921599K bytes of eUSB flash at bootflash:.
39004543K bytes of SATA hard disk at bootflash:.
Configuration register is 0x2102
In the example show version output, the router has 4 GB of DRAM memory.
If you are using a Cisco ASR 1001, Cisco ASR 1002, or Cisco ASR 1004 Router with 2-GB DRAM memory on the RP, SSO cannot be configured on your RP.
Step 2
(Optional) Enter show redundancy states to see the current HA configuration:
Router# show redundancy states
Redundancy Mode (Operational) = Non-redundant
Redundancy Mode (Configured) = Non-redundant
Redundancy State = Non Redundant
In this example, HA for the dual RPs is not configured, as indicated by the nonredundant operational mode.
Step 3
Enter configure terminal to enter global configuration mode:
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Step 4
Enter the redundancy command to enter redundancy configuration mode:
Router(config)# redundancy
Step 5
Enter mode sso to enable SSO, or mode none to disable dual software redundancy:
Router(config-red)# mode sso
Router(config-red)# mode none
Step 6
Return to privileged EXEC mode using any method, such as entering Ctrl-Z or the exit command multiple times until you get to the # router prompt:
Step 7
Enter the show redundancy states command to confirm the configured redundancy mode changed to your new configuration.
In the following example, the configured redundancy mode has been changed to SSO. Note that the operation redundancy mode remains unchanged:
Router# show redundancy states
Redundancy Mode (Operational) = Non-redundant
Redundancy Mode (Configured) = sso
Redundancy State = Non Redundant
Step 8
Enter the copy running-config startup-config command to save the new configuration, and press enter to confirm the filename (or change the name, if desired):
Router# copy running-config startup-config
Destination filename [startup-config]?
Building configuration...
Step 9
After the reload is complete, enter the show redundancy states command to confirm the operational redundancy mode has changed to the mode that you configured in Step 5.
In this example, the operational redundancy mode has changed to SSO:
Router# show redundancy states
peer state = 8 -STANDBY HOT
Redundancy Mode (Operational) = sso
Redundancy Mode (Configured) = sso
Step 10
The router must be reloaded for the new HA configuration. Enter the reload command to reload the router:
Proceed with reload? [confirm]
<bootup messages removed for brevity>
If you are not using the console port to complete this procedure, your session may be terminated at this point. If you session is terminated, give the router a few minutes to complete the reload and then log into the router.
Step 11
(Optional) To confirm an active and a standby IOS process exist, and how the processes are numbered, enter the show platform command.
In this example, the show platform command output reveals that R0/0 is the active IOS process and R0/1 is the standby IOS process:
Slot Type State Insert time (ago)
--------- ------------------- --------------------- -----------------
0 ASR1000-SIP10 ok 00:52:34
0/0 SPA-2X1GE-V2 ok 00:51:30
0/1 SPA-2XT3/E3 ok 00:51:24
R0 ASR1000-RP1 ok 00:52:34
R0/1 ok, standby 00:51:00
F0 ASR1000-ESP10 ok, active 00:52:34
P0 ASR1004-PWR-AC ok 00:51:57
P1 ASR1004-PWR-AC ok 00:51:57
Using SubPackages for Software Upgrade on a Cisco ASR 1001 Router
This section provides instructions on using software upgrade for Cisco ASR 1001 Router running subpackages.
These instructions assume two IOS processes are active on the RP and that the router is already running using subpackages.
SUMMARY STEPS
1.
show version
show version installed
dir filesystem:<directory>
show platform
show redundancy-states
2.
redundancy
mode sso
3.
mkdir URL-to-directory-name
4.
ip tftp source-interface gigabitethernet slot/port
5.
copy tftp: URL-to-target-location
6.
request platform software package expand file URL-to-consolidated-package
7.
dir URL-to-consolidated-package
8.
copy file-system:asr1001-espbase.version.pkg URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1001-rpaccess.version.pkg URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1001-rpbase.version.pkg URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1001-rpcontrol.version.pkg URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1001-rpios.version.pkg URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1001-sipbase.version.pkg URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1001-sipspa.version.pkg URL-to-directory-of-sub-packages-active-RP
9.
issu loadversion rp 0 file file-system:asr1001-{rpaccess,rpios,rpcontrol}*version-string*.pkg bay standby-bay force
10.
issu commitversion
11.
redundancy force-switchover
12.
show platform
13.
issu loadversion rp 0 file file-system:asr1001-{rpaccess,rpios,rpcontrol}*version-string*.pkg bay standby-bay force
14.
issu commitversion
15.
issu loadversion rp 0 file file-system:asr1001-{rpbase,sipbase,sipspa,espbase}*version*.pkg force
16.
show version installed
17.
reload
Note
Step 17 does not have to be performed immediately, and should be done at a convenient time.
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
show version
show version installed
dir filesystem:<directory>
show platform
show redundancy-states
Example:
Router# show version
Router# show version r0 installed
Router# dir bootflash:
Router# show platform
Router# show redundancy-states
|
(Optional) Use the following commands to confirm the current router configuration, as follows:
• show version and show version active-rp installed—Verify the running version of the Cisco IOS XE software on the router, and which file was used to boot the router, and where that file is stored.
• dir—Confirm that the files that were used to boot the router are located in the directory.
• show platform—Confirm the current status of the active and standby RPs.
• show redundancy states—Confirm the operational and configured redundancy states.
|
Step 2
|
redundancy
mode sso
Example:
Router(config)# redundancy
Router(config-red)# mode sso
|
Configure SSO if it is not already configured.
Note Save the configuration after making this configuration step.
|
Step 3
|
mkdir URL-to-directory-name
Example:
Router# mkdir 221subs
|
Create a directory to store the consolidated package and subpackages.
This directory must be created in most cases because the consolidated packages and subpackages have to be separated from the subpackages that booted the router at this step of the procedure.
|
Step 4
|
ip tftp source-interface gigabitethernet slot/port
Example:
Router(config)# ip tftp source-interface
gigabitethernet 0
|
Specifies the Gigabit Ethernet TFTP source-interface to be configured:
slot/port—Specifies the location of the TFTP source-interface.
Note To copy a file using TFTP through the Management Ethernet interface, the ip tftp source-interface GigabitEthernet 0 command must be entered before entering the copy tftp command.
|
Step 5
|
copy tftp: URL-to-target-location
Example:
Router# copy tftp: 221subs
|
Copy the consolidated package file into the directory created in Step 3.
The consolidated package in this step should not be copied into the same directory where the subpackages that are currently running your router are stored (the directory containing the packages.conf provisioning file from which the router was booted).
Tip  It is recommended that you copy the package onto a usb: or harddisk: file system for space considerations when performing this step of the procedure.
|
Step 6
|
request platform software package expand file
URL-to-consolidated-package
(Optional) dir target-URL
Example:
Router# request platform software package expand
file
usb0:221subs/asr1001-universalk9.03.02.01.S.151-1.S
1_2.bin
Router# dir 221subs
|
Extract the subpackages out of the consolidated package file into the temporary directory.
Note Take extra care to extract the subpackages to a temporary subdirectory and do not delete any of the files currently running the router at this point of the procedure.
To erase the files that were running on the router before the ISSU upgrade, enter the request platform software package clean command after the ISSU upgrade has been completed.
|
Step 7
|
dir target-URL
Example:
Router# dir 221subs
|
(Optional) Display the directory to confirm that the files were extracted.
|
Step 8
|
copy file-system:asr1001-espbase.version.pkg
URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1001-rpaccess.version.pkg
URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1001-rpbase.version.pkg
URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1001-rpcontrol.version.pkg
URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1001-rpios.version.pkg
URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1001-sipbase.version.pkg
URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1001-sipspa.version.pkg
URL-to-directory-of-sub-packages-active-RP
Example:
Router# copy
221subs/asr1001-espbase.03.02.01.S.151-1.S1_2.pkg
bootflash:
Router# copy
221subs/asr1001-rpaccess.03.02.01.S.151-1.S1_2.pkg
bootflash:
Router# copy
221subs/asr1001-rpbase.03.02.01.S.151-1.S1_2.pkg
bootflash:
Router# copy
221subs/asr1001-rpcontrol.03.02.01.S.151-1.S1_2.pkg
bootflash:
Router# copy
221subs/asr1001-rpios-universalk9.03.02.01.S.151-1.
S1_2.pkg bootflash:
Router# copy
221subs/asr1001-sipbase.03.02.01.S.151-1.S1_2.pkg
bootflash:
Router# copy
221subs/asr1001-sipspa.03.02.01.S.151-1.S1_2.pkg
bootflash:
|
Copy the subpackages out of the temporary directory into the directory on the router where the subpackages running the active RP are currently stored.
|
Step 9
|
issu loadversion rp 0 file
file-system:asr1001-{rpaccess,rpios,rpcontrol}*versio
n-string*.pkg bay standby-bay force
Example:
Router# issu loadversion rp 0 file
bootflash:asr1001-{rpaccess,rpios,rpcontrol}*03.02.
01.S.151-1.S1_2*.pkg bay 1 force
|
Upgrade the RPAccess, RPIOS, and RPControl subpackages in the standby bay.
|
Step 10
|
issu commitversion
Example:
Router# issu commitversion
|
Once the SSO state is reached, commit the software version.
|
Step 11
|
redundancy force-switchover
Example:
Router# redundancy force-switchover
|
Force a switchover from the active IOS process to the standby IOS process.
Note Your connection to the router often drops and is expected behavior at this point of the procedure in many scenarios.
If this step drops your connection to the router, wait a few minutes before reconnecting to the router and then continue to Step 12.
|
Step 12
|
show platform
Example:
Router# show platform
|
(Optional) Monitor system state to ensure both IOS processes are active.
|
Step 13
|
issu loadversion rp 0 file
file-system:asr1001-{rpaccess,rpios,rpcontrol}*vers
ion-string*.pkg bay standby-bay force
Example:
Router# issu loadversion rp 0 file
bootflash:asr1001-{rpaccess,rpios,rpcontrol}*03.02.
01.S.151-1.S1_2*.pkg bay 0 force
|
Upgrade the RPAccess, RPIOS, and RPControl subpackages in the standby bay (a different bay than in Step 9).
|
Step 14
|
issu commitversion
Example:
Router# issu commitversion
|
Commit the software version.
|
Step 15
|
issu loadversion rp 0 file
file-system:asr1001-{rpbase,sipbase,sipspa,espbase}*v
ersion*.pkg force
Example:
Router#issu loadversion rp 0 file
bootflash:221subs/asr1001-{rpbase,sipbase,sipspa,es
pbase}*03.02.01.S.151-1.S1_2.pkg force
|
Upgrade the RP, SIP, SPA, and ESP subpackages for each SIP on the router.
Note This step must be completed one SIP at a time, and repeated for each SIP installed on the router before performing the next step.
Tip  You can use the show ip interface brief command to identify which slots contain SIPs and SPAs. The interfaces with three numbers (in the form SIP-number/SPA-number/interface-number) identify the SIP and SPA locations in the router.
Note The pattern options used in this CLI (rpbase, sipbase, sipspa, and espbase) were introduced in Cisco IOS XE Release 2.1.2 and are not available in previous Cisco IOS XE Releases. See the "ISSU Procedures (Prior to Cisco IOS XE Release 2.1.2)" section for pre-Cisco IOS XE Release 2.1.2 ISSU upgrade procedures.
|
Step 16
|
show version installed
Example:
Router# show version installed
|
(Optional) Verify that the subpackages are properly installed.
|
Step 17
|
reload
Example:
Router# reload
|
(Optional) Reload the RP.
Tip  The router will continue normal operation even without a reload, so you can reload the router during scheduled maintenance or a slower traffic period. It is highly recommended reload to avoid conflicts in the software base.
|
Examples
The following example shows the software upgrade for Cisco ASR 1001 Router running subpackages.
Cisco IOS Software, IOS-XE Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Experimental
Version 15.1(20110301:124851) [asr1001-universalk9.03.02.01.S.151-1.S1]
Copyright (c) 1986-2011 by Cisco Systems, Inc.
Compiled Tue 01-Mar-11 06:25 by mcpre
Cisco IOS-XE software, Copyright (c) 2005-2011 by cisco Systems, Inc.
All rights reserved. Certain components of Cisco IOS-XE software are
licensed under the GNU General Public License ("GPL") Version 2.0. The
software code licensed under GPL Version 2.0 is free software that comes
with ABSOLUTELY NO WARRANTY. You can redistribute and/or modify such
GPL code under the terms of GPL Version 2.0. For more details, see the
documentation or "License Notice" file accompanying the IOS-XE software,
or the applicable URL provided on the flyer accompanying the IOS-XE
Router uptime is 5 days, 26 minutes
Uptime for this control processor is 5 days, 27 minutes
System returned to ROM by reload
System image file is "bootflash:asr1001-universalk9.03.02.01.S.151-1.S1"
Last reload reason: Reload Command
This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
If you require further assistance please contact us by sending email to
--------------------------------------------------------------------------------
*0 ASR1001 JAE14020AT1 ASR1001:JAE14020AT1
License Package Information for Module:'asr1001'
Module name Image level Pri Config Valid license
------------------------------------------------------------------------
asr1001 adventerprise 1 NO adventerprise
advipservices 2 NO advipservices
Module name Current Level Reboot Level
------------------------------------------------------------------------
cisco ASR1001 (1RU) processor with 3851680K/6147K bytes of memory.
6 Gigabit Ethernet interfaces
32768K bytes of non-volatile configuration memory.
8388608K bytes of physical memory.
7782399K bytes of eUSB flash at bootflash:.
Configuration register is 0x8102
Router# show version installed
Package: Provisioning File, version: n/a, status: active
File: consolidated:packages.conf, on: RP0
File SHA1 checksum: e11c9aacb8c233ed10eeac61ca20a9469fb0b81e
Package: rpbase, version: 03.02.01.S.151-1.S1, status: active
File: consolidated:asr1001-rpbase.03.02.01.S.151-1.S1.pkg, on: RP0
Built: 2011-03-01_07.10, by: mcpre
File SHA1 checksum: e3c93ac457f2632ae90ba346692d58001cf0d02c
Package: rpcontrol, version: 03.02.01.S.151-1.S1, status: active
File: consolidated:asr1001-rpcontrol.03.02.01.S.151-1.S1.pkg, on: RP0/0
Built: 2011-03-01_07.10, by: mcpre
File SHA1 checksum: 59ba43488cf2a0e7bc06b66fad0e574bbdf42a62
<output removed for brevity>
Router#show redundancy states
Redundancy Mode (Operational) = Non-redundant
Redundancy Mode (Configured) = Non-redundant
Redundancy State = Non Redundant
Manual Swact = disabled (system is simplex (no peer unit))
Communications = Down Reason: Simplex mode
client_notification_TMR = 30000 milliseconds
keep_alive TMR = 4000 milliseconds
Slot Type State Insert time (ago)
--------- ------------------- --------------------- -----------------
0/1 SPA-2X1GE-V2 ok 5d07h
R0 ASR1001 ok, active 5d07h
F0 ASR1001 ok, active 5d07h
P0 ASR1001-PWR-AC ps, fail 5d07h
P1 ASR1001-PWR-AC ok 5d07h
P2 ASR1001-FANTRAY ok 5d07h
Slot CPLD Version Firmware Version
--------- ------------------- ---------------------------------------
0 1001050E 12.2(20090526:143323) [gschnorr-mcp_...
R0 10010514 12.2(20090526:143323) [gschnorr-mcp_...
F0 1001050E 12.2(20090526:143323) [gschnorr-mcp_...
Create directory filename [221subs]?
Created dir bootflash:221subs
Router(config)# ip tftp source-interface gigabitethernet 0
Router# copy tftp: 221subs
Address or name of remote host []? 172.27.55.254
Source filename []? /auto/users/asr1001-universalk9.03.02.01.S.151-1.S1_2.bin,12
Destination filename [asr1001-universalk9.03.02.01.S.151-1.S1.bin,12]?
Accessing
tftp://172.27.55.254//auto/users/asr1001-universalk9.03.02.01.S.151-1.S1_2.bin,12...
Loading /auto/users/asr1001-universalk9.03.02.01.S.151-1.S1.bin,12 (via GigabitEthernet0):
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!.!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!
209227980 bytes copied in 880.002 secs (237759 bytes/sec)
Router# request platform software package expand file
221subs/asr1001-universalk9.03.02.01.S.151-1.S1_2.bin
SUCCESS: Finished expanding all-in-one software package.
72013 -rw- 51904716 Oct 7 2008 15:46:02 -07:00
asr1001-espbase.03.02.01.S.151-1.S1_2.pkg
72004 -rw- 5773 Oct 7 2008 15:46:02 -07:00
asr1001-packages-universalk9.03.02.01.S.151-1.S1_2.conf
72014 -rw- 20533452 Oct 7 2008 15:46:03 -07:00
asr1001-rpaccess.03.02.01.S.151-1.S1_2.pkg
72015 -rw- 22388940 Oct 7 2008 15:46:03 -07:00
asr1001-rpbase.03.02.01.S.151-1.S1_2.pkg
72016 -rw- 27961548 Oct 7 2008 15:46:03 -07:00
asr1001-rpcontrol.03.02.01.S.151-1.S1_2.pkg
72017 -rw- 50942156 Oct 7 2008 15:46:03 -07:00
asr1001-rpios-universalk9.03.02.01.S.151-1.S1_2.pkg
72018 -rw- 36442316 Oct 7 2008 15:46:03 -07:00
asr1001-sipbase.03.02.01.S.151-1.S1_2.pkg
72019 -rw- 26366156 Oct 7 2008 15:46:03 -07:00
asr1001-sipspa.03.02.01.S.151-1.S1_2.pkg
72005 -rw- 6290 Oct 7 2008 15:46:03 -07:00 packages.conf
72003 -rw- 224768204 Oct 7 2008 15:38:57 -07:00
asr1001-universalk9.03.02.01.S.151-1.S1_2.bin
928862208 bytes total (466358272 bytes free)
Router# copy 221subs/asr1001-espbase.03.02.01.S.151-1.S1_2.pkg bootflash:
Destination filename [asr1001-espbase.03.02.01.S.151-1.S1_2.pkg]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
51904716 bytes copied in 5.478 secs (9475122 bytes/sec)
Router# copy 221subs/asr1001-rpaccess.03.02.01.S.151-1.S1_2.pkg bootflash:
Destination filename [asr1001-rpaccess.03.02.01.S.151-1.S1_2.pkg]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
20533452 bytes copied in 2.346 secs (8752537 bytes/sec)
Router# copy 221subs/asr1001-rpbase.03.02.01.S.151-1.S1_2.pkg bootflash:
Destination filename [asr1001-rpbase.03.02.01.S.151-1.S1_2.pkg]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
22388940 bytes copied in 2.496 secs (8969928 bytes/sec)
Router# copy 221subs/asr1001-rpcontrol.03.02.01.S.151-1.S1_2.pkg bootflash:
Destination filename [asr1001-rpcontrol.03.02.01.S.151-1.S1_2.pkg]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
27961548 bytes copied in 2.992 secs (9345437 bytes/sec)
Router# copy 221subs/asr1001-rpios-universalk9.03.02.01.S.151-1.S1_2.pkg bootflash:
Destination filename [asr1001-rpios-universalk9.03.02.01.S.151-1.S1_2.pkg]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
50942156 bytes copied in 5.719 secs (8907529 bytes/sec)
Router# copy 221subs/asr1001-sipbase.03.02.01.S.151-1.S1_2.pkg bootflash:
Destination filename [asr1001-sipbase.03.02.01.S.151-1.S1_2.pkg]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCC
36442316 bytes copied in 3.906 secs (9329830 bytes/sec)
Router# copy 221subs/asr1001-sipspa.03.02.01.S.151-1.S1_2.pkg bootflash:
Destination filename [asr1001-sipspa.03.02.01.S.151-1.S1_2.pkg]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
26366156 bytes copied in 2.857 secs (9228616 bytes/sec)
Router# issu loadversion rp 0 file
bootflash:221subs/asr1001-{rpaccess,rpios,rpcontrol}*03.02.01.S.151-1.S1_2.pkg bay 1 force
--- Starting local lock acquisition on R0 ---
Finished local lock acquisition on R0
--- Starting file path checking ---
Finished file path checking
--- Starting image file verification ---
Checking image file names
Locating image files and validating name syntax
Found asr1001-rpaccess.03.02.01.S.151-1.S1_2.pkg
Found asr1001-rpios-universalk9.03.02.01.S.151-1.S1_2.pkg
Found asr1001-rpcontrol.03.02.01.S.151-1.S1_2.pkg
Verifying image file locations
Inspecting image file types
Processing image file constraints
Creating candidate provisioning file
Finished image file verification
--- Starting candidate package set construction ---
Verifying existing software set
Processing candidate provisioning file
Constructing working set for candidate package set
Constructing working set for running package set
Constructing merge of running and candidate packages
Checking if resulting candidate package set would be complete
Finished candidate package set construction
--- Starting compatibility testing ---
Determining whether candidate package set is compatible
WARNING: Candidate software combination not found in compatibility database
Determining whether installation is valid
WARNING: Candidate software combination not found in compatibility database
WARNING: Candidate software combination not found in compatibility database
Software sets are identified as compatible
Verifying image type compatibility
Checking IPC compatibility with running software
Checking candidate package set infrastructure compatibility
Checking infrastructure compatibility with running software
Checking package specific compatibility
Finished compatibility testing
--- Starting impact testing ---
Checking operational impact of change
WARNING: Connection may be lost during installation of IOS package
--- Starting list of software package changes ---
No old package files removed
Added asr1001-rpaccess.03.02.01.S.151-1.S1_2.pkg
Added asr1001-rpcontrol.03.02.01.S.151-1.S1_2.pkg
Added asr1001-rpios-universalk9.03.02.01.S.151-1.S1_2.pkg
Finished list of software package changes
--- Starting commit of software changes ---
Updating provisioning rollback files
Creating pending provisioning file
Committing provisioning file
Finished commit of software changes
--- Starting analysis of software changes ---
Finished analysis of software changes
--- Starting update running software ---
Blocking peer synchronization of operating information
Creating the command set placeholder directory
Finding latest command set
Finding latest command shortlist lookup file
Finding latest command shortlist file
Assembling CLI output libraries
Assembling CLI input libraries
Assembling Dynamic configuration files
Applying interim IPC and database definitions
Replacing running software
Restarting IOS PID: 9275, in slot/bay 0/1
*Mar 15 16:28:50.014: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER)
*Mar 15 16:28:50.014: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER)
*Mar 15 16:28:50.014: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER)
*Mar 15 16:28:52.224: %RF-5-RF_RELOAD: Peer reload. Reason: EHSA standby down s
*Mar 15 16:29:29.183: %CMRP-5-PRERELEASE_HARDWARE: R0/0: cmand: 0 is pre-releae
*Mar 15 16:29:29.214: %REDUNDANCY-5-PEER_MONITOR_EVENT: Active detected a stand)
*Mar 15 16:29:29.214: %REDUNDANCY-5-PEER_MONITOR_EVENT: Active detected a stand)
Generating software version information
Unblocking peer synchronization of operating information
Cleaning temporary installation files
Finished update running software
Router#issu commitversion
--- Starting local lock acquisition on R0 ---
Finished local lock acquisition on R0
--- Starting installation changes ---
Cancelling rollback timer
Finished installation changes
SUCCESS: Installation changes committed
*Mar 15 16:30:24.885: %NBAR_HA-5-NBAR_INFO: NBAR sync DONE!
*Mar 15 16:30:25.421: %HA_CONFIG_SYNC-6-BULK_CFGSYNC_SUCCEED: Bulk Sync succeedd
*Mar 15 16:30:25.423: %RF-5-RF_TERMINAL_STATE: Terminal state reached for (SSO)
Router#redundancy force-switchover
Proceed with switchover to standby RP? [confirm]y Manual Swact = enabled
%ASR1000_INFRA-6-CONSOLE_ACTIVE: R0/1 console active. Press RETURN to get star!
*Mar 15 16:31:00.014: %REDUNDANCY-3-SWITCHOVER: RP switchover (PEER_NOT_PRESENT)
*Mar 15 16:31:00.015: %REDUNDANCY-3-SWITCHOVER: RP switchover (PEER_DOWN)
*Mar 15 16:31:00.015: %REDUNDANCY-3-SWITCHOVER: RP switchover (PEER_REDUNDANCY_)
*Mar 15 16:31:00.328: %LINK-3-UPDOWN: Interface Lsmpi0, changed state to up
*Mar 15 16:31:00.328: %LINK-3-UPDOWN: Interface EOBC0, changed state to up
*Mar 15 16:31:00.328: %LINK-3-UPDOWN: Interface LIIN0, changed state to up
*Mar 15 16:31:01.328: %LINEPROTO-5-UPDOWN: Line protocol on Interface Lsmpi0, cp
*Mar 15 16:31:01.328: %LINEPROTO-5-UPDOWN: Line protocol on Interface EOBC0, chp
*Mar 15 16:31:01.328: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEtn
*Mar 15 16:31:01.328: %LINEPROTO-5-UPDOWN: Line protocol on Interface LIIN0, chp
*Mar 15 16:31:02.064: %RF-5-RF_RELOAD: Self reload. Reason: redundancy force-swr
*Mar 15 16:31:02.293: %SYS-5-SWITCHOVER: Switchover requested by red_switchover.
*Mar 15 16:31:02.321: %LINK-3-UPDOWN: Interface Null0, changed state to up
*Mar 15 16:31:03.321: %LINEPROTO-5-UPDOWN: Line protocol on Interface Null0, chp
*Mar 15 16:31:03.322: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEtn
*Mar 15 16:31:03.322: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEtn
*Mar 15 16:31:03.322: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEtn
*Mar 15 16:31:03.322: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEtn
*Mar 15 16:31:03.322: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEtn
*Mar 15 16:31:03.322: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEtn
*Mar 15 16:31:43.168: %CMRP-5-PRERELEASE_HARDWARE: R0/0: cmand: 0 is pre-releae
*Mar 15 16:31:43.189: %REDUNDANCY-5-PEER_MONITOR_EVENT: Active detected a stand)
*Mar 15 16:31:43.189: %REDUNDANCY-5-PEER_MONITOR_EVENT: Active detected a stand)
*Mar 15 16:32:28.411: %NBAR_HA-5-NBAR_INFO: NBAR sync DONE!
*Mar 15 16:32:28.971: %HA_CONFIG_SYNC-6-BULK_CFGSYNC_SUCCEED: Bulk Sync succeedd
*Mar 15 16:32:28.973: %RF-5-RF_TERMINAL_STATE: Terminal state reached for (SSO)
Router# issu loadversion rp 0 file
bootflash:221subs/asr1001-{rpaccess,rpios,rpcontrol}*03.02.01.S.151-1.S1_2.pkg bay 0 force
--- Starting local lock acquisition on R0 ---
Finished local lock acquisition on R0
--- Starting file path checking ---
Finished file path checking
--- Starting image file verification ---
Checking image file names
Locating image files and validating name syntax
Verifying image file locations
Inspecting image file types
Processing image file constraints
Creating candidate provisioning file
Finished image file verification
--- Starting candidate package set construction ---
Verifying existing software set
Processing candidate provisioning file
Constructing working set for candidate package set
Constructing working set for running package set
Constructing merge of running and candidate packages
Checking if resulting candidate package set would be complete
Finished candidate package set construction
--- Starting compatibility testing ---
Determining whether candidate package set is compatible
WARNING: Candidate software combination not found in compatibility database
Determining whether installation is valid
Software sets are identified as compatible
Verifying image type compatibility
Checking IPC compatibility with running software
Checking candidate package set infrastructure compatibility
Checking infrastructure compatibility with running software
Checking package specific compatibility
Finished compatibility testing
--- Starting impact testing ---
Checking operational impact of change
WARNING: Connection may be lost during installation of IOS package
--- Starting list of software package changes ---
Removed asr1001-rpaccess.03.02.01.S.151-1.S1.pkg
Removed asr1001-rpcontrol.03.02.01.S.151-1.S1.pkg
Removed asr1001-rpios-universalk9.03.02.01.S.151-1.S1.pkg
No new package files added
Finished list of software package changes
--- Starting commit of software changes ---
Updating provisioning rollback files
Creating pending provisioning file
Committing provisioning file
Finished commit of software changes
--- Starting analysis of software changes ---
Finished analysis of software changes
--- Starting update running software ---
Blocking peer synchronization of operating information
Creating the command set placeholder directory
Finding latest command set
Finding latest command shortlist lookup file
Finding latest command shortlist file
Assembling CLI output libraries
Assembling CLI input libraries
Assembling Dynamic configuration files
Applying interim IPC and database definitions
Replacing running software
Restarting IOS PID: 20548, in slot/bay 0/0
*Mar 15 16:36:14.365: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER)
*Mar 15 16:36:14.365: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER)
*Mar 15 16:36:14.365: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER)
*Mar 15 16:36:16.558: %RF-5-RF_RELOAD: Peer reload. Reason: EHSA standby down
*Mar 15 16:36:49.361: %CMRP-5-PRERELEASE_HARDWARE: R0/0: cmand: 0 is pre-releae
*Mar 15 16:36:49.365: %REDUNDANCY-5-PEER_MONITOR_EVENT: Active detected a stand)
*Mar 15 16:36:49.365: %REDUNDANCY-5-PEER_MONITOR_EVENT: Active detected a stand)
*Mar 15 16:37:00.004: %ASR1000_PEM-6-PEMOK: The PEM in slot 2 is functioning pry
*Mar 15 16:37:00.005: %ASR1000_PEM-6-FANOK: The fan in slot 2/0 is functioning y
*Mar 15 16:37:00.005: %ASR1000_PEM-6-FANOK: The fan in slot 2/1 is functioning y
*Mar 15 16:37:00.005: %ASR1000_PEM-6-FANOK: The fan in slot 2/2 is functioning y
*Mar 15 16:37:00.005: %ASR1000_PEM-6-FANOK: The fan in slot 2/3 is functioning y
*Mar 15 16:37:00.005: %ASR1000_PEM-6-FANOK: The fan in slot 2/4 is functioning y
*Mar 15 16:37:00.005: %ASR1000_PEM-6-FANOK: The fan in slot 2/5 is functioning y
*Mar 15 16:37:00.005: %ASR1000_PEM-6-FANOK: The fan in slot 2/6 is functioning y
*Mar 15 16:37:00.470: %LICENSE-6-COUNT: R0/0: licensed: Feature cube_250 1.0 li
*Mar 15 16:37:00.471: %LICENSE-6-COUNT: R0/0: licensed: Feature cube_250 1.0 li
*Mar 15 16:37:00.703: %CMRP-5-PRERELEASE_HARDWARE: R0/0: cmand: 0 is pre-releae
*Mar 15 16:37:01.961: %CMRP-6-THROUGHPUT_LICENSE: R0/0: cmand: Throughput liceG
*Mar 15 16:37:06.571: %CMRP-5-PRERELEASE_HARDWARE: R0/0: cmand: 0 is pre-relean
Notifying running software of updates
Unblocking peer synchronization of operating information
Cleaning temporary installation files
Finished update running software
SUCCESS: Finished installing software.
Router#issu commitversion
--- Starting local lock acquisition on R0 ---
Finished local lock acquisition on R0
--- Starting installation changes ---
Cancelling rollback timer
Finished installation changes
SUCCESS: Installation changes committed
Router#issu loadversion rp 0 file
bootflash:221subs/asr1001-{rpbase,sipbase,sipspa,espbase}*03.02.01.S.151-1.S1_2.pkg force
--- Starting local lock acquisition on R0 ---
Finished local lock acquisition on R0
--- Starting file path checking ---
Finished file path checking
--- Starting image file verification ---
Checking image file names
Locating image files and validating name syntax
Verifying image file locations
Inspecting image file types
WARNING: In-service installation of RP Base package
WARNING: requires software reboot of target RP
WARNING: Automatically setting the on-reboot flag
Processing image file constraints
Creating candidate provisioning file
Finished image file verification
--- Starting candidate package set construction ---
Verifying existing software set
Processing candidate provisioning file
Constructing working set for candidate package set
Constructing working set for running package set
Constructing merge of running and candidate packages
Checking if resulting candidate package set would be complete
Finished candidate package set construction
--- Starting compatibility testing ---
Determining whether candidate package set is compatible
Determining whether installation is valid
Determining whether installation is valid ... skipped
Verifying image type compatibility
Checking IPC compatibility for candidate software
Checking candidate package set infrastructure compatibility
Checking infrastructure compatibility with running software
Checking infrastructure compatibility with running software ... skipped
Checking package specific compatibility
Finished compatibility testing
--- Starting list of software package changes ---
Removed asr1001-espbase.03.02.01.S.151-1.S1.pkg
Removed asr1001-rpbase.03.02.01.S.151-1.S1.pkg
Removed asr1001-sipbase.03.02.01.S.151-1.S1.pkg
Removed asr1001-sipspa.03.02.01.S.151-1.S1.pkg
Added asr1001-espbase.03.02.01.S.151-1.S1_2.pkg
Added asr1001-rpbase.03.02.01.S.151-1.S1_2.pkg
Added asr1001-sipbase.03.02.01.S.151-1.S1_2.pkg
Added asr1001-sipspa.03.02.01.S.151-1.S1_2.pkg
Finished list of software package changes
--- Starting commit of software changes ---
Updating provisioning rollback files
Creating pending provisioning file
Committing provisioning file
Finished commit of software changes
SUCCESS: Software provisioned. New software will load on reboot.
Using SubPackages for Software Upgrade on a Cisco ASR 1002 or Cisco ASR 1004 Router (software upgrade Command Set)
This section provides instructions on using software upgrade for Cisco ASR 1002 or 1004 Router running subpackages.
These instructions assume two IOS processes are active on the RP and that the router is already running using subpackages. For information on checking and configuring two IOS processes on the same RP, see the "Using SubPackages for Software Upgrade on a Cisco ASR 1002 or Cisco ASR 1004 Router (software upgrade Command Set)" section.
SUMMARY STEPS
1.
show version
show version installed
dir filesystem:<directory>
show platform
show redundancy-states
2.
redundancy
mode sso
3.
mkdir URL-to-directory-name
4.
ip tftp source-interface gigabitethernet slot/port
5.
copy tftp: URL-to-target-location
6.
request platform software package expand file URL-to-consolidated-package
7.
dir URL-to-consolidated-package
8.
copy file-system:asr1000rp1-espbase.version.pkg URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1000rp1-rpaccess.version.pkg URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1000rp1-rpbase.version.pkg URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1000rp1-rpcontrol.version.pkg URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1000rp1-rpios.version.pkg URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1000rp1-sipbase.version.pkg URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1000rp1-sipspa.version.pkg URL-to-directory-of-sub-packages-active-RP
9.
issu loadversion rp 0 file file-system:asr1000rp1-{rpaccess,rpios,rpcontrol}*version-string*.pkg bay standby-bay force
10.
issu commitversion
11.
redundancy force-switchover
12.
show platform
13.
issu loadversion rp 0 file file-system:asr1000rp1-{rpaccess,rpios,rpcontrol}*version-string*.pkg bay standby-bay force
14.
issu commitversion
15.
issu loadversion rp 0 file file-system:asr1000rp1-{sipbase,sipspa}*version*.pkg slot SIP-slot-number force
issu commitversion
Note
Repeat this step for each SIP installed in your router before proceeding to the next step.
16.
issu loadversion rp 0 file file-system:asr1000rp1-esp*version*.pkg force
17.
issu commitversion
18.
issu loadversion rp 0 file file-system:asr1000rp*version*.pkg
19.
show version installed
20.
reload
21.
request platform software package clean
Note
Step 19, 20, and 21 does not have to be performed immediately, and can be done at a convenient time.
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
show version
show version installed
dir filesystem:<directory>
show platform
show redundancy-states
Example:
Router# show version
Router# show version r0 installed
Router# dir bootflash:
Router# show platform
Router# show redundancy-states
|
(Optional) Use the following commands to confirm the current router configuration, as follows:
• show version and show version active-rp installed—Verify the running version of the Cisco IOS XE software on the router, and which file was used to boot the router, and where that file is stored.
• dir—Confirm that the files that were used to boot the router are located in the directory.
• show platform—Confirm the current status of the active and standby RPs.
• show redundancy states—Confirm the operational and configured redundancy states.
|
Step 2
|
redundancy
mode sso
Example:
Router(config)# redundancy
Router(config-red)# mode sso
|
Configure SSO if it is not already configured.
Note Save the configuration after making this configuration step.
|
Step 3
|
mkdir URL-to-directory-name
Example:
Router# mkdir usb0:221subs
|
Create a directory to store the consolidated package and subpackages.
This directory must be created in most cases because the consolidated packages and subpackages have to be separated from the subpackages that booted the router at this step of the procedure.
|
Step 4
|
ip tftp source-interface gigabitethernet slot/port
Example:
Router(config)# ip tftp source-interface
gigabitethernet 0
|
Specifies the Gigabit Ethernet TFTP source-interface to be configured:
slot/port—Specifies the location of the TFTP source-interface.
Note To copy a file using TFTP through the Management Ethernet interface, the ip tftp source-interface GigabitEthernet 0 command must be entered before entering the copy tftp command.
|
Step 5
|
copy tftp: URL-to-target-location
Example:
Router# copy tftp: usb0:221subs
|
Copy the consolidated package file into the directory created in Step 3.
The consolidated package in this step should not be copied into the same directory where the subpackages that are currently running your router are stored (the directory containing the packages.conf provisioning file from which the router was booted).
Tip  It is recommended that you copy the package onto a usb: or harddisk: file system for space considerations when performing this step of the procedure.
|
Step 6
|
request platform software package expand file
URL-to-consolidated-package
(Optional) dir target-URL
Example:
Router# request platform software package
expand file
usb0:221subs/asr1000rp1-adventerprisek9.02.02.0
1.122-33.XNB1.bin
Router# dir usb0:221subs
|
Extract the subpackages out of the consolidated package file into the temporary directory.
Note Take extra care to extract the subpackages to a temporary subdirectory and do not delete any of the files currently running the router at this point of the procedure.
To erase the files that were running on the router before the ISSU upgrade, enter the request platform software package clean command after the ISSU upgrade has been completed.
|
Step 7
|
dir target-URL
Example:
Router# dir usb0:221subs
|
(Optional) Display the directory to confirm that the files were extracted.
|
Step 8
|
copy file-system:asr1000rp1-espbase.version.pkg
URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1000rp1-rpaccess.version.pkg
URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1000rp1-rpbase.version.pkg
URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1000rp1-rpcontrol.version.pkg
URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1000rp1-rpios.version.pkg
URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1000rp1-sipbase.version.pkg
URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1000rp1-sipspa.version.pkg
URL-to-directory-of-sub-packages-active-RP
Example:
Router# copy
usb0:221subs/asr1000rp1-espbase.02.02.01.122-33
.XNB1.pkg bootflash:
Router# copy
usb0:221subs/asr1000rp1-rpaccess.02.02.01.122-3
3.XNB1.pkg bootflash:
Router# copy
usb0:221subs/asr1000rp1-rpbase.02.02.01.122-33.
XNB1.pkg bootflash:
Router# copy
usb0:221subs/asr1000rp1-rpcontrol.02.02.01.122-
33.XNB1.pkg bootflash:
Router# copy
usb0:221subs/asr1000rp1-rpios-adventerprisek9.0
2.02.01.122-33.XNB1.pkg bootflash:
Router# copy
usb0:221subs/asr1000rp1-sipbase.02.02.01.122-33
.XNB1.pkg bootflash:
Router# copy
usb0:221subs/asr1000rp1-sipspa.02.02.01.122-33.
XNB1.pkg bootflash:
|
Copy the subpackages out of the temporary directory into the directory on the router where the subpackages running the active RP are currently stored.
|
Step 9
|
issu loadversion rp 0 file
file-system:asr1000rp1-{rpaccess,rpios,rpcontrol
}*version-string*.pkg bay standby-bay force
Example:
Router# issu loadversion rp 0 file
bootflash:asr1000rp1-{rpaccess,rpios,rpcontrol}
*02.02.01.122-33.XNB1*.pkg bay 1 force
|
Upgrade the RPAccess, RPIOS, and RPControl subpackages in the standby bay.
|
Step 10
|
issu commitversion
Example:
Router# issu commitversion
|
Once the SSO state is reached, commit the software version.
|
Step 11
|
redundancy force-switchover
Example:
Router# redundancy force-switchover
|
Force a switchover from the active IOS process to the standby IOS process.
Note Your connection to the router often drops and is expected behavior at this point of the procedure in many scenarios.
If this step drops your connection to the router, wait a few minutes before reconnecting to the router and then continue to Step 12.
|
Step 12
|
show platform
Example:
Router# show platform
|
(Optional) Monitor system state to ensure both IOS processes are active.
|
Step 13
|
issu loadversion rp 0 file
file-system:asr1000rp1-{rpaccess,rpios,rpcontrol
}*version-string*.pkg bay standby-bay force
Example:
Router# issu loadversion rp 0 file
bootflash:asr1000rp1-{rpaccess,rpios,rpcontrol}
*02.02.01.122-33.XNB1*.pkg bay 0 force
|
Upgrade the RPAccess, RPIOS, and RPControl subpackages in the standby bay (a different bay than in Step 9).
|
Step 14
|
issu commitversion
Example:
Router# issu commitversion
|
Commit the software version.
|
Step 15
|
issu loadversion rp 0 file
file-system:asr1000rp1-{sipbase,sipspa}*version*.
pkg slot SIP-slot-number force
issu commitversion
Repeat this step for each SIP installed in your
router before proceeding to the next step.
Example:
Router# issu loadversion rp 0 file
bootflash:asr1000rp1-{sipspa,sipbase}*02.02.01.
122-33.XNB1*.pkg slot 0 force
Router# issu commitversion
Router# issu loadversion rp 0 file
bootflash:asr1000rp1-{sipspa,sipbase}*02.02.01.
122-33.XNB1*.pkg slot 1 force
Router# issu commitversion
Router# issu loadversion rp 0 file
bootflash:asr1000rp1-{sipspa,sipbase}*02.02.01.
122-33.XNB1*.pkg slot 2 force
Router# issu commitversion
|
Upgrade the SIP and SPA subpackages for each SIP on the router.
Note This step must be completed one SIP at a time, and repeated for each SIP installed on the router before performing the next step.
Tip  You can use the show ip interface brief command to identify which slots contain SIPs and SPAs. The interfaces with three numbers (in the form SIP-number/SPA-number/interface-number) identify the SIP and SPA locations in the router.
Note The pattern options used in this CLI (sipbase and sipspa) were introduced in Cisco IOS XE Release 2.1.2 and are not available in previous Cisco IOS XE Releases. See the "ISSU Procedures (Prior to Cisco IOS XE Release 2.1.2)" section for pre-Cisco IOS XE Release 2.1.2 ISSU upgrade procedures.
|
Step 16
|
issu loadversion rp 0 file
file-system:asr1000rp1-esp*version*.pkg force
Example:
Router# issu loadversion rp 0 file
bootflash:asr1000rp1-esp*02.02.01.122-33.XNB1*.
pkg force
|
Upgrade the ESP Base subpackage.
|
Step 17
|
issu commitversion
Example:
Router# issu commitversion
|
Commit the ESP Base software.
|
Step 18
|
issu loadversion rp 0 file
file-system:asr1000rp*version*.pkg
Example:
Router# issu loadversion rp 0 file
bootflash:asr1000rp*02.02.01.122-33.XNB1*.pkg
|
Upgrades all subpackages, including the RPBase subpackage, which is the last subpackage that needs to be upgraded.
Note This step is required to ensure that all subpackages on the router were upgraded as part of this procedure, and might upgrade some subpackages that would otherwise be missed in the process.
|
Step 19
|
show version installed
Example:
Router# show version installed
|
(Optional) Verify that the subpackages are properly installed.
|
Step 20
|
reload
Example:
Router# reload
|
Reload the RP.
Tip  The router will continue normal operation even without a reload, so you can reload the router during scheduled maintenance or a slower traffic period.
|
Step 21
|
request platform software package clean
|
(Optional) Removes the unused subpackages from the router.
|
Examples
The following example shows the software upgrade for Cisco ASR 1002 or 1004 Router running sub-packages:
Cisco IOS Software, IOS-XE Software (PPC_LINUX_IOSD-ADVENTERPRISEK9-M), Version
12.2(33)XNA, RELEASE SOFTWARE (fc1)
<output removed for brevity>
System image file is "bootflash:packages.conf"
<output removed for brevity>
cisco ASR1004 (RP1) processor with 752142K/6147K bytes of memory.
5 Gigabit Ethernet interfaces
32768K bytes of non-volatile configuration memory.
4194304K bytes of physical memory.
937983K bytes of eUSB flash at bootflash:.
39004543K bytes of SATA hard disk at bootflash:.
253424K bytes of USB flash at usb0:.
Configuration register is 0x2102
Router# show version installed
Package: Provisioning File, version: n/a, status: active
File: bootflash:packages.conf, on: RP0
File SHA1 checksum: 9172d30751d79fc1afb7b405eca244bbf9f8f2f2
Package: rpbase, version: 02.01.00.122-33.XNA, status: active
File: bootflash:asr1000rp1-rpbase.02.01.00.122-33.XNA.pkg, on: RP0
Built: 2008-05-01_01.48, by: mcpre
File SHA1 checksum: c09fe08ff908c8ce0b789d8acc774fe43dacf5e3
Package: rpaccess, version: 02.01.01.122-33.XNA, status: active
File: bootflash:asr1000rp1-rpaccess.02.01.01.122-33.XNA.pkg, on: RP0
Built: 2008-07-08_16.01, by: mcpre
File SHA1 checksum: c1afc591c9cd198409820226c4f23d2647d0d138
<output removed for brevity>
Router# show redundancy states
peer state = 4 -STANDBY COLD
Redundancy Mode (Operational) = sso
Redundancy Mode (Configured) = sso
Maintenance Mode = Disabled
Manual Swact = disabled (peer unit not yet in terminal standby state)
client_notification_TMR = 30000 milliseconds
Slot Type State Insert time (ago)
--------- ------------------- --------------------- -----------------
0 ASR1000-SIP10 ok 00:04:43
0/0 SPA-1XOC12-POS ok 00:03:25
0/1 SPA-2XOC3-POS ok 00:03:24
0/3 SPA-5X1GE-V2 ok 00:03:20
R0 ASR1000-RP1 ok 00:04:43
R0/1 ok, standby 00:02:55
F0 ASR1000-ESP10 ok, active 00:04:43
P0 ASR1004-PWR-AC ok 00:03:53
P1 ASR1004-FAN ok 00:03:53
Slot CPLD Version Firmware Version
--------- ------------------- ---------------------------------------
Router# mkdir usb0:221subs
Create directory filename [221subs]?
Created dir bootflash:221subs
Router(config)# ip tftp source-interface gigabitethernet 0
Router# copy tftp: usb0:221subs
Address or name of remote host []? 172.17.16.81
Source filename []? /auto/users/asr1000rp1-adventerprisek9.02.02.01.122-33.XNB1.bin
Destination filename [asr1000rp1-adventerprisek9.02.02.01.122-33.XNB1.bin]?
Accessing
tftp://172.17.16.81//auto/users/asr1000rp1-adventerprisek9.02.02.01.122-33.XNB1.bin...
Loading /auto/users/asr1000rp1-adventerprisek9.02.02.01.122-33.XNB1.bin from 172.17.16.81
(via GigabitEthernet0):
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!.!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!
209227980 bytes copied in 880.002 secs (237759 bytes/sec)
Router# request platform software package expand file
usb0:221subs/asr1000rp1-adventerprisek9.02.02.01.122-33.XNB1.bin
SUCCESS: Finished expanding all-in-one software package.
Directory of usb0:/221subs/
72013 -rw- 51904716 Oct 7 2008 15:46:02 -07:00
asr1000rp1-espbase.02.02.01.122-33.XNB1.pkg
72004 -rw- 5773 Oct 7 2008 15:46:02 -07:00
asr1000rp1-packages-adventerprisek9.02.02.01.122-33.XNB1.conf
72014 -rw- 20533452 Oct 7 2008 15:46:03 -07:00
asr1000rp1-rpaccess.02.02.01.122-33.XNB1.pkg
72015 -rw- 22388940 Oct 7 2008 15:46:03 -07:00
asr1000rp1-rpbase.02.02.01.122-33.XNB1.pkg
72016 -rw- 27961548 Oct 7 2008 15:46:03 -07:00
asr1000rp1-rpcontrol.02.02.01.122-33.XNB1.pkg
72017 -rw- 50942156 Oct 7 2008 15:46:03 -07:00
asr1000rp1-rpios-adventerprisek9.02.02.01.122-33.XNB1.pkg
72018 -rw- 36442316 Oct 7 2008 15:46:03 -07:00
asr1000rp1-sipbase.02.02.01.122-33.XNB1.pkg
72019 -rw- 26366156 Oct 7 2008 15:46:03 -07:00
asr1000rp1-sipspa.02.02.01.122-33.XNB1.pkg
72005 -rw- 6290 Oct 7 2008 15:46:03 -07:00 packages.conf
72003 -rw- 224768204 Oct 7 2008 15:38:57 -07:00
asr1000rp1-adventerprisek9.02.02.01.122-33.XNB1.bin
928862208 bytes total (466358272 bytes free)
Router# copy usb0:221subs/asr1000rp1-espbase.02.02.01.122-33.XNB1.pkg bootflash:
Destination filename [asr1000rp1-espbase.02.02.01.122-33.XNB1.pkg]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
51904716 bytes copied in 5.478 secs (9475122 bytes/sec)
Router# copy usb0:221subs/asr1000rp1-rpaccess.02.02.01.122-33.XNB1.pkg bootflash:
Destination filename [asr1000rp1-rpaccess.02.02.01.122-33.XNB1.pkg]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
20533452 bytes copied in 2.346 secs (8752537 bytes/sec)
Router# copy usb0:221subs/asr1000rp1-rpbase.02.02.01.122-33.XNB1.pkg bootflash:
Destination filename [asr1000rp1-rpbase.02.02.01.122-33.XNB1.pkg]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
22388940 bytes copied in 2.496 secs (8969928 bytes/sec)
Router# copy usb0:221subs/asr1000rp1-rpcontrol.02.02.01.122-33.XNB1.pkg bootflash:
Destination filename [asr1000rp1-rpcontrol.02.02.01.122-33.XNB1.pkg]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
27961548 bytes copied in 2.992 secs (9345437 bytes/sec)
Router# copy usb0:221subs/asr1000rp1-rpios-adventerprisek9.02.02.01.122-33.XNB1.pkg
bootflash:
Destination filename [asr1000rp1-rpios-adventerprisek9.02.02.01.122-33.XNB1.pkg]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
50942156 bytes copied in 5.719 secs (8907529 bytes/sec)
Router# copy usb0:221subs/asr1000rp1-sipbase.02.02.01.122-33.XNB1.pkg bootflash:
Destination filename [asr1000rp1-sipbase.02.02.01.122-33.XNB1.pkg]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCC
36442316 bytes copied in 3.906 secs (9329830 bytes/sec)
Router# copy usb0:221subs/asr1000rp1-sipspa.02.02.01.122-33.XNB1.pkg bootflash:
Destination filename [asr1000rp1-sipspa.02.02.01.122-33.XNB1.pkg]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
26366156 bytes copied in 2.857 secs (9228616 bytes/sec)
Router# issu loadversion rp 0 file
bootflash:asr1000rp1-{rpaccess,rpios,rpcontrol}*02.02.01.122-33.XNB1*.pkg bay 1 force
--- Starting file path checking ---
Finished file path checking
--- Starting image file verification ---
Checking image file names
Verifying image file locations
Locating image files and validating name syntax
Inspecting image file types
Processing image file constraints
Creating candidate provisioning file
Finished image file verification
--- Starting candidate package set construction ---
Verifying existing software set
Processing candidate provisioning file
Constructing working set for candidate package set
Constructing working set for running package set
Constructing merge of running and candidate packages
Finished candidate package set construction
--- Starting compatibility testing ---
Determining whether candidate package set is compatible
WARNING: Candidate software combination not found in compatibility database
Determining whether installation is valid
WARNING: Candidate software combination not found in compatibility database
WARNING: Candidate software combination not found in compatibility database
Software sets are identified as compatible
Checking IPC compatibility with running software
Checking candidate package set infrastructure compatibility
Checking infrastructure compatibility with running software
Checking package specific compatibility
Finished compatibility testing
--- Starting impact testing ---
Checking operational impact of change
WARNING: Connection may be lost during installation of IOS package
--- Starting commit of software changes ---
Updating provisioning rollback files
Creating pending provisioning file
Committing provisioning file
Finished commit of software changes
--- Starting analysis of software changes ---
Finished analysis of software changes
--- Starting update running software ---
Blocking peer synchronization of operating information
Creating the command set placeholder directory
Finding latest command set
Finding latest command shortlist lookup file
Finding latest command shortlist file
Assembling CLI output libraries
Assembling CLI input libraries
Applying interim IPC and database definitions
Replacing running software
*Sep 25 18:04:24.517: %ASR1000_INFRA-6-BIPC_READ_ERR: R0/0: ppc_linux_iosd-image:
connection read error from iman bipc, rc 32, bring down IPC Restarting IOS PID: 19257, in
slot/bay 0/1
*Sep 25 18:04:39.325: %PMAN-3-PROCHOLDDOWN: R0/0: pman.sh: The process
ppc_linux_iosd-image has been helddown (rc 137)
*Sep 25 18:04:39.422: %PMAN-0-PROCFAILCRIT: R0/0: pvp.sh: A critical process
ppc_linux_iosd_image has failed (rc 137)
*Sep 25 18:04:39.462: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault
(PEER_NOT_PRESENT)
*Sep 25 18:04:39.462: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER_DOWN)
*Sep 25 18:04:39.463: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault
(PEER_REDUNDANCY_STATE_CHANGE)FIXME: kill/restart security package: 0 1 rp_security
Applying final IPC and database definitions
Generating software version information
Notifying running software of updates
Unblocking peer synchronization of operating information
Cleaning temporary installation files
Finished update running software
SUCCESS: Finished installing software.
*Sep 25 18:05:32.476: %REDUNDANCY-5-PEER_MONITOR_EVENT: Active detected a standby
insertion (raw-event=PEER_FOUND(4))
*Sep 25 18:05:32.476: %REDUNDANCY-5-PEER_MONITOR_EVENT: Active detected a standby
insertion (raw-event=PEER_REDUNDANCY_STATE_CHANGE(5))
*Sep 25 18:05:33.409: %REDUNDANCY-3-IPC: IOS versions do not match.
*Sep 25 18:07:39.886: %HA_CONFIG_SYNC-6-BULK_CFGSYNC_SUCCEED: Bulk Sync succeeded
*Sep 25 18:07:39.888: %RF-5-RF_TERMINAL_STATE: Terminal state reached for (SSO)
Router# issu commitversion
--- Starting installation changes ---
Cancelling rollback timer
Finished installation changes
SUCCESS: Installation changes committed
Router# redundancy force-switchover
Proceed with switchover to standby RP? [confirm]
%ASR1000_INFRA-6-CONSOLE_ACTIVE: R0/1 console active. Press RETURN to get started!
*Sep 25 18:08:27.898: %CMANRP-6-CMHASTATUS: RP switchover, received fastpath becoming
active event
*Sep 25 18:08:28.224: %CMANRP-6-CMHASTATUS: RP switchover, received chassis event to
become active
*Sep 25 18:08:28.229: %NETCLK-5-NETCLK_MODE_CHANGE: Network clock source not available.
The network clock has changed to freerun
*Sep 25 18:08:28.243: %REDUNDANCY-3-SWITCHOVER: RP switchover (PEER_NOT_PRESENT)
*Sep 25 18:08:28.243: %REDUNDANCY-3-SWITCHOVER: RP switchover (PEER_DOWN)
*Sep 25 18:08:27.956: %SYS-5-SWITCHOVER: Switchover requested by Exec. Reason: redundancy
force-switchover.: %REDUNDANCY-3-SWITCHOVER: RP switchover (PEER_REDUNDANCY_STATE_CHANGE)
*Sep 25 18:08:28.248: %PLATFORM-6-HASTATUS: RP switchover, sent message became active. IOS
is ready to switch to primary after chassis confirmation
*Sep 25 18:08:28.249: %CMANRP-6-CMHASTATUS: RP switchover, received chassis event became
active
*Sep 25 18:08:28.497: %PLATFORM-6-HASTATUS_DETAIL: RP switchover, received chassis event
became active. Switch to primary (count 1)
*Sep 25 18:08:29.746: %ACE-3-TRANSERR: ASR1000-ESP(14): IKEA trans 0x3; opcode 0x25; param
0xA; error 0x4; retry cnt 0
*Sep 25 18:08:29.746: %ACE-3-TRANSERR: ASR1000-ESP(14): IKEA trans 0x4; opcode 0x25; param
0xB; error 0x4; retry cnt 0
*Sep 25 18:08:29.746: %ACE-3-TRANSERR: ASR1000-ESP(14): IKEA trans 0x5; opcode 0x25; param
0xC; error 0x4; retry cnt 0
*Sep 25 18:08:30.630: %LINK-3-UPDOWN: Interface Null0, changed state to up
*Sep 25 18:08:30.631: %LINK-3-UPDOWN: Interface Loopback0, changed state to up
*Sep 25 18:08:30.635: %LINK-5-CHANGED: Interface POS0/0/0, changed state to
administratively down
*Sep 25 18:08:30.636: %LINK-5-CHANGED: Interface POS0/1/0, changed state to
administratively down
*Sep 25 18:08:30.636: %LINK-5-CHANGED: Interface POS0/1/1, changed state to
administratively down
*Sep 25 18:08:30.636: %LINK-5-CHANGED: Interface GigabitEthernet0/3/0, changed state to
administratively down
*Sep 25 18:08:30.636: %LINK-5-CHANGED: Interface GigabitEthernet0/3/1, changed state to
administratively down
*Sep 25 18:08:30.636: %LINK-5-CHANGED: Interface GigabitEthernet0/3/2, changed state to
administratively down
*Sep 25 18:08:30.636: %LINK-5-CHANGED: Interface GigabitEthernet0/3/3, changed state to
administratively down
*Sep 25 18:08:30.636: %LINK-5-CHANGED: Interface GigabitEthernet0/3/4, changed state to
administratively down
*Sep 25 18:08:31.630: %LINEPROTO-5-UPDOWN: Line protocol on Interface Null0, changed state
to up
*Sep 25 18:08:31.630: %LINEPROTO-5-UPDOWN: Line protocol on Interface Loopback0, changed
state to up
*Sep 25 18:09:16.667: %REDUNDANCY-3-IPC: IOS versions do not match.
*Sep 25 18:09:16.717: %REDUNDANCY-5-PEER_MONITOR_EVENT: Active detected a standby
insertion (raw-event=PEER_FOUND(4))
*Sep 25 18:09:16.717: %REDUNDANCY-5-PEER_MONITOR_EVENT: Active detected a standby
insertion (raw-event=PEER_REDUNDANCY_STATE_CHANGE(5))
*Sep 25 18:11:00.500: %HA_CONFIG_SYNC-6-BULK_CFGSYNC_SUCCEED: Bulk Sync succeeded
*Sep 25 18:11:00.502: %RF-5-RF_TERMINAL_STATE: Terminal state reached for (SSO)
Slot Type State Insert time (ago)
--------- ------------------- --------------------- -----------------
0 ASR1000-SIP10 ok 00:14:44
0/0 SPA-1XOC12-POS ok 00:04:02
0/1 SPA-2XOC3-POS ok 00:04:02
0/3 SPA-5X1GE-V2 ok 00:04:02
R0 ASR1000-RP1 ok 00:14:44
R0/0 ok, standby 00:02:01
F0 ASR1000-ESP10 ok, active 00:14:44
P0 ASR1004-PWR-AC ok 00:13:54
P1 ASR1004-FAN ok 00:13:54
Slot CPLD Version Firmware Version
--------- ------------------- ---------------------------------------
Router# issu loadversion rp 0 file
bootflash:asr1000rp1-{rpaccess,rpios,rpcontrol}*02.02.01.122-33.XNB1*.pkg bay 0 force
--- Starting file path checking ---
Finished file path checking
--- Starting image file verification ---
Checking image file names
Verifying image file locations
Locating image files and validating name syntax
Inspecting image file types
Processing image file constraints
Creating candidate provisioning file
Finished image file verification
--- Starting candidate package set construction ---
Verifying existing software set
Processing candidate provisioning file
Constructing working set for candidate package set
Constructing working set for running package set
Constructing merge of running and candidate packages
Finished candidate package set construction
--- Starting compatibility testing ---
Determining whether candidate package set is compatible
WARNING: Candidate software combination not found in compatibility database
Determining whether installation is valid
Software sets are identified as compatible
Checking IPC compatibility with running software
Checking candidate package set infrastructure compatibility
Checking infrastructure compatibility with running software
Checking package specific compatibility
Finished compatibility testing
--- Starting impact testing ---
Checking operational impact of change
WARNING: Connection may be lost during installation of IOS package
--- Starting commit of software changes ---
Updating provisioning rollback files
Creating pending provisioning file
Committing provisioning file
Finished commit of software changes
--- Starting analysis of software changes ---
Finished analysis of software changes
--- Starting update running software ---
Blocking peer synchronization of operating information
Creating the command set placeholder directory
Finding latest command set
Finding latest command shortlist lookup file
Finding latest command shortlist file
Assembling CLI output libraries
Assembling CLI input libraries
Applying interim IPC and database definitions
Replacing running software
*Sep 25 18:13:27.604: %IOSXE-4-PLATFORM: R0/0: kernel: scooby: Scooby: FD close
Restarting IOS PID: 20492, in slot/bay 0/0
*Sep 25 18:13:53.696: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault
(PEER_NOT_PRESENT)
*Sep 25 18:13:53.696: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER_DOWN)
*Sep 25 18:13:53.697: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault
(PEER_REDUNDANCY_STATE_CHANGE)FIXME: kill/restart security package: 0 0 rp_security
Applying final IPC and database definitions
*Sep 25 18:13:56.593: %DYNCMD-7-CMDSET_UNLOADED: The Dynamic Command set from the Shell
Manager has been unloaded
*Sep 25 18:13:56.963: %DYNCMD-7-CMDSET_LOADED: The Dynamic Command set has been loaded
from the Shell Manager
*Sep 25 18:13:59.457: %RF-5-RF_RELOAD: Peer reload. Reason: EHSA standby down Generating
software version information
Notifying running software of updates
Unblocking peer synchronization of operating information
Cleaning temporary installation files
Finished update running software
SUCCESS: Finished installing software.
Router# issu commitversion
--- Starting installation changes ---
Cancelling rollback timer
Finished installation changes
SUCCESS: Installation changes committed
*Sep 25 18:14:47.232: %CMRP-5-PRERELEASE_HARDWARE: R0/0: cmand: 0:0 is pre-release
hardware
*Sep 25 18:14:47.299: %REDUNDANCY-5-PEER_MONITOR_EVENT: Active detected a standby
insertion (raw-event=PEER_FOUND(4))
*Sep 25 18:14:47.299: %REDUNDANCY-5-PEER_MONITOR_EVENT: Active detected a standby
insertion (raw-event=PEER_REDUNDANCY_STATE_CHANGE(5))
Router# issu loadversion rp 0 file
bootflash:asr1000rp1-{sipspa,sipbase}*02.02.01.122-33.XNB1*.pkg slot 0 force
--- Starting file path checking ---
Finished file path checking
--- Starting image file verification ---
Checking image file names
Verifying image file locations
Locating image files and validating name syntax
Inspecting image file types
Processing image file constraints
Creating candidate provisioning file
Finished image file verification
--- Starting candidate package set construction ---
Verifying existing software set
Processing candidate provisioning file
Constructing working set for candidate package set
Constructing working set for running package set
Constructing merge of running and candidate packages
Finished candidate package set construction
--- Starting compatibility testing ---
Determining whether candidate package set is compatible
WARNING: Candidate software combination not found in compatibility database
Determining whether installation is valid
WARNING: Candidate software combination not found in compatibility database
WARNING: Candidate software combination not found in compatibility database
Software sets are identified as compatible
Checking IPC compatibility with running software
Checking candidate package set infrastructure compatibility
Checking infrastructure compatibility with running software
Checking package specific compatibility
Finished compatibility testing
--- Starting impact testing ---
Checking operational impact of change
--- Starting commit of software changes ---
Updating provisioning rollback files
Creating pending provisioning file
Committing provisioning file
Finished commit of software changes
--- Starting analysis of software changes ---
Finished analysis of software changes
--- Starting update running software ---
Blocking peer synchronization of operating information
Creating the command set placeholder directory
Finding latest command set
Finding latest command shortlist lookup file
Finding latest command shortlist file
Assembling CLI output libraries
Assembling CLI input libraries
Applying interim IPC and database definitions
Replacing running software
Applying final IPC and database definitions
*Sep 29 11:05:40.249: %ASR1000_OIR-6-OFFLINECARD: Card (cc) offline in slot 0
*Sep 29 11:05:40.250: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 0/0, interfaces
disabled
*Sep 29 11:05:40.250: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 0/1, interfaces
disabled
*Sep 29 11:05:40.250: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 0/3, interfaces
disabled
*Sep 29 11:05:48.163: %CMRP-5-PRERELEASE_HARDWARE: R0/0: cmand: 0:0 is pre-release
hardware Generating software version information
Notifying running software of updates
Unblocking peer synchronization of operating information
Cleaning temporary installation files
Finished update running software
SUCCESS: Finished installing software.
*Sep 29 11:06:23.227: %ASR1000_OIR-6-ONLINECARD: Card (cc) online in slot 0
*Sep 29 11:06:23.225: %CMRP-5-PRERELEASE_HARDWARE: R0/0: cmand: 0:0 is pre-release
hardware
*Sep 29 11:06:24.624: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 0/0
*Sep 29 11:06:25.379: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 0/1
*Sep 29 11:06:26.306: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 0/3
*Sep 29 11:06:33.776: %SPA_OIR-6-ONLINECARD: SPA (SPA-1XOC12-POS) online in subslot 0/0
*Sep 29 11:06:33.934: %LINK-3-UPDOWN: SIP0/0: Interface EOBC0/1, changed state to up
*Sep 29 11:06:37.496: %LINK-3-UPDOWN: SIP0/1: Interface EOBC0/1, changed state to up
*Sep 29 11:06:43.820: %SPA_OIR-6-ONLINECARD: SPA (SPA-2XOC3-POS) online in subslot 0/1
*Sep 29 11:06:42.046: %LINK-3-UPDOWN: SIP0/3: Interface EOBC0/1, changed state to up
*Sep 29 11:06:48.410: %SPA_OIR-6-ONLINECARD: SPA (SPA-5X1GE-V2) online in subslot 0/3
Router# issu commitversion
--- Starting installation changes ---
Cancelling rollback timer
Finished installation changes
SUCCESS: Installation changes committed
Router# issu loadversion rp 0 file
bootflash:asr1000rp1-{sipspa,sipbase}*02.02.01.122-33.XNB1*.pkg slot 1 force
--- Starting file path checking ---
Finished file path checking
--- Starting image file verification ---
Checking image file names
Verifying image file locations
Locating image files and validating name syntax
Inspecting image file types
Processing image file constraints
Creating candidate provisioning file
Finished image file verification
--- Starting candidate package set construction ---
Verifying existing software set
Processing candidate provisioning file
Constructing working set for candidate package set
Constructing working set for running package set
Constructing merge of running and candidate packages
Finished candidate package set construction
--- Starting compatibility testing ---
Determining whether candidate package set is compatible
WARNING: Candidate software combination not found in compatibility database
Determining whether installation is valid
Software sets are identified as compatible
Checking IPC compatibility with running software
Checking candidate package set infrastructure compatibility
Checking infrastructure compatibility with running software
Checking package specific compatibility
Finished compatibility testing
--- Starting impact testing ---
Checking operational impact of change
--- Starting commit of software changes ---
Updating provisioning rollback files
Creating pending provisioning file
Committing provisioning file
Finished commit of software changes
--- Starting analysis of software changes ---
Finished analysis of software changes
--- Starting update running software ---
Blocking peer synchronization of operating information
Creating the command set placeholder directory
Finding latest command set
Finding latest command shortlist lookup file
Finding latest command shortlist file
Assembling CLI output libraries
Assembling CLI input libraries
Applying interim IPC and database definitions
Replacing running software
Applying final IPC and database definitions
Generating software version information
Notifying running software of updates
Unblocking peer synchronization of operating information
Cleaning temporary installation files
Finished update running software
SUCCESS: Finished installing software.
Router# issu commitversion
--- Starting installation changes ---
Cancelling rollback timer
Finished installation changes
SUCCESS: Installation changes committed
Router#issu loadversion rp 0 file bootflash:asr1000rp1-esp*02.02.01.122-33.XNB1*.pkg force
--- Starting file path checking ---
Finished file path checking
--- Starting image file verification ---
Checking image file names
Verifying image file locations
Locating image files and validating name syntax
Inspecting image file types
Processing image file constraints
Creating candidate provisioning file
Finished image file verification
--- Starting candidate package set construction ---
Verifying existing software set
Processing candidate provisioning file
Constructing working set for candidate package set
Constructing working set for running package set
Constructing merge of running and candidate packages
Finished candidate package set construction
--- Starting compatibility testing ---
Determining whether candidate package set is compatible
WARNING: Candidate software combination not found in compatibility database
Determining whether installation is valid
WARNING: Candidate software combination not found in compatibility database
WARNING: Candidate software combination not found in compatibility database
Software sets are identified as compatible
Checking IPC compatibility with running software
Checking candidate package set infrastructure compatibility
Checking infrastructure compatibility with running software
Checking package specific compatibility
Finished compatibility testing
--- Starting impact testing ---
Checking operational impact of change
--- Starting commit of software changes ---
Updating provisioning rollback files
Creating pending provisioning file
Committing provisioning file
Finished commit of software changes
--- Starting analysis of software changes ---
Finished analysis of software changes
--- Starting update running software ---
Blocking peer synchronization of operating information
Creating the command set placeholder directory
Finding latest command set
Finding latest command shortlist lookup file
Finding latest command shortlist file
Assembling CLI output libraries
Assembling CLI input libraries
Applying interim IPC and database definitions
Replacing running software
Applying final IPC and database definitions
*Sep 25 18:22:56.525: %ASR1000_OIR-6-OFFLINECARD: Card (fp) offline in slot F0
*Sep 25 18:22:58.588: %CMRP-5-PRERELEASE_HARDWARE: R0/0: cmand: F0:0 is pre-release
hardware Generating software version information
Notifying running software of updates
Unblocking peer synchronization of operating information
Cleaning temporary installation files
Finished update running software
SUCCESS: Finished installing software.
*Sep 25 18:23:35.356: %DYNCMD-7-CMDSET_UNLOADED: The Dynamic Command set from the Shell
Manager has been unloaded
*Sep 25 18:23:35.846: %DYNCMD-7-CMDSET_LOADED: The Dynamic Command set has been loaded
from the Shell Manager
*Sep 25 18:23:45.207: %ASR1000_OIR-6-ONLINECARD: Card (fp) online in slot F0
*Sep 25 18:23:45.206: %CMRP-5-PRERELEASE_HARDWARE: R0/0: cmand: F0:0 is pre-release
hardware
*Sep 25 18:23:55.309: %CPPHA-7-SYSREADY: F0: cpp_ha: CPP client process FMAN-FP (5 of 5)
ready.
*Sep 25 18:23:55.698: %CPPHA-7-START: F0: cpp_ha: CPP 0 preparing image
/usr/cpp/bin/cpp-mcplo-ucode
*Sep 25 18:23:55.931: %CPPHA-7-START: F0: cpp_ha: CPP 0 startup init image
/usr/cpp/bin/cpp-mcplo-ucode
*Sep 25 18:24:00.837: %CPPHA-7-START: F0: cpp_ha: CPP 0 running init image
/usr/cpp/bin/cpp-mcplo-ucode
*Sep 25 18:24:01.077: %CPPHA-7-READY: F0: cpp_ha: CPP 0 loading and initialization
complete
*Sep 25 18:24:01.077: %CPPHA-6-SYSINIT: F0: cpp_ha: CPP HA system configuration start.
*Sep 25 18:24:02.403: %IOSXE-6-PLATFORM: F0: cpp_cp: Process
CPP_PFILTER_EA_EVENT__API_CALL__REGISTER
*Sep 25 18:24:02.597: %CPPHA-6-SYSINIT: F0: cpp_ha: CPP HA system enabled.
*Sep 25 18:24:02.598: %CPPHA-6-SYSINIT: F0: cpp_ha: CPP HA system initialization
complete.
Router# issu commitversion
--- Starting installation changes ---
Cancelling rollback timer
Finished installation changes
SUCCESS: Installation changes committed
Router# issu loadversion rp 0 file bootflash:asr1000rp*02.02.01.122-33.XNB1*.pkg
--- Starting file path checking ---
Finished file path checking
--- Starting image file verification ---
Checking image file names
Verifying image file locations
Locating image files and validating name syntax
Inspecting image file types
WARNING: In-service installation of RP Base package
WARNING: requires software reboot of target RP
WARNING: Automatically setting the on-reboot flag
Processing image file constraints
Creating candidate provisioning file
Finished image file verification
--- Starting candidate package set construction ---
Verifying existing software set
Processing candidate provisioning file
Constructing working set for candidate package set
Constructing working set for running package set
Constructing merge of running and candidate packages
Finished candidate package set construction
--- Starting compatibility testing ---
Determining whether candidate package set is compatible
Determining whether installation is valid
Determining whether installation is valid ... skipped
Checking IPC compatibility for candidate software
Checking candidate package set infrastructure compatibility
Checking infrastructure compatibility with running software
Checking infrastructure compatibility with running software ... skipped
Checking package specific compatibility
Finished compatibility testing
--- Starting commit of software changes ---
Updating provisioning rollback files
Creating pending provisioning file
Committing provisioning file
Finished commit of software changes
SUCCESS: Software provisioned. New software will load on reboot.
Router# show version provisioned
Package: Provisioning File, version: n/a, status: active
File: bootflash:packages.conf, on: RP0
File SHA1 checksum: aca136bd8bcb99f87e6aa7a0ce2a92a3b5a5a200
Package: rpbase, version: BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1,
status: active
File:
bootflash:asr1000rp1-rpbase.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_
1.pkg, on: RP0
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: 32b3fceaf59e3acd7cf9937ef33a822d6b359887
Package: rpaccess, version:
BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: active
File:
bootflash:asr1000rp1-rpaccess.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_010
0_1.pkg, on: RP0
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: 7c8dfdf9b2e3602b0c6c531a88dd93c8d2d180c6
Package: rpcontrol, version:
BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: active
File:
bootflash:asr1000rp1-rpcontrol.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_01
00_1.pkg, on: RP0/0
--More-- Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: a544cd10841b237066ccbc4714f4e23c00a9d2e5
Package: rpios-adventerprisek9, version:
BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: active
File:
bootflash:asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST
_20080924_0100_1.pkg, on: RP0/0
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: a4967ac35d6ac37ef275b28e032773762be9f202
Package: rpcontrol, version:
BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: active
File:
bootflash:asr1000rp1-rpcontrol.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_01
00_1.pkg, on: RP0/1
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: a544cd10841b237066ccbc4714f4e23c00a9d2e5
Package: rpios-adventerprisek9, version:
BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: active
File:
bootflash:asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST
_20080924_0100_1.pkg, on: RP0/1
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: a4967ac35d6ac37ef275b28e032773762be9f202
Package: rpbase, version: BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1,
status: inactive
File:
bootflash:asr1000rp1-rpbase.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_
1.pkg, on: RP1
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: 32b3fceaf59e3acd7cf9937ef33a822d6b359887
Package: rpaccess, version:
BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: inactive
File:
bootflash:asr1000rp1-rpaccess.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_010
0_1.pkg, on: RP1
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: 7c8dfdf9b2e3602b0c6c531a88dd93c8d2d180c6
Package: rpcontrol, version:
BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: inactive
File:
bootflash:asr1000rp1-rpcontrol.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_01
00_1.pkg, on: RP1/0
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: a544cd10841b237066ccbc4714f4e23c00a9d2e5
Package: rpios-adventerprisek9, version:
BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: inactive
--More-- File:
bootflash:asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST
_20080924_0100_1.pkg, on: RP1/0
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: a4967ac35d6ac37ef275b28e032773762be9f202
Package: rpcontrol, version:
BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: inactive
File:
bootflash:asr1000rp1-rpcontrol.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_01
00_1.pkg, on: RP1/1
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: a544cd10841b237066ccbc4714f4e23c00a9d2e5
Package: rpios-adventerprisek9, version:
BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1, status: inactive
File:
bootflash:asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST
_20080924_0100_1.pkg, on: RP1/1
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: a4967ac35d6ac37ef275b28e032773762be9f202
Package: rpios-adventerprisek9, version: unknown, status: active
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: inactive
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: active
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: active
File: unknown, on: SIP0/0
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: active
File: unknown, on: SIP0/1
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: inactive
File: unknown, on: SIP0/2
--More-- Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: active
File: unknown, on: SIP0/3
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: inactive
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: inactive
File: unknown, on: SIP1/0
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: inactive
File: unknown, on: SIP1/1
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
--More-- Package: rpios-adventerprisek9, version: unknown, status: inactive
File: unknown, on: SIP1/2
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: inactive
File: unknown, on: SIP1/3
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: inactive
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: inactive
File: unknown, on: SIP2/0
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: inactive
File: unknown, on: SIP2/1
Built: 2008-09-24_03.52, by: mcpre
--More-- File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: inactive
File: unknown, on: SIP2/2
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
Package: rpios-adventerprisek9, version: unknown, status: inactive
File: unknown, on: SIP2/3
Built: 2008-09-24_03.52, by: mcpre
File SHA1 checksum: unknown
<some output removed for brevity>
Router# request platform software package clean
Cleaning up unnecessary package files
No path specified, will use booted path bootflash:packages.conf
Scanning boot directory for packages ... done.
Preparing packages list to delete ...
asr1000rp1-espbase.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg
File is in use, will not delete.
asr1000rp1-rpaccess.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg
File is in use, will not delete.
asr1000rp1-rpbase.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg
File is in use, will not delete.
asr1000rp1-rpcontrol.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg
File is in use, will not delete.
asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_
0100_1.pkg
File is in use, will not delete.
asr1000rp1-sipbase.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg
File is in use, will not delete.
asr1000rp1-sipspa.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg
File is in use, will not delete.
File is in use, will not delete.
Files that will be deleted:
asr1000-rommon.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg
asr1000-rommon.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg
asr1000rp1-adventerprisek9.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.bin
asr1000rp1-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1
.bin
asr1000rp1-espbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg
asr1000rp1-packages-adventerprisek9.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100
_1.conf
asr1000rp1-packages-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_200809
24_0100_1.conf
asr1000rp1-rpaccess.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg
asr1000rp1-rpbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg
asr1000rp1-rpcontrol.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg
asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.
pkg
asr1000rp1-sipbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg
asr1000rp1-sipspa.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg
Do you want to proceed? [confirm]y
Deleting file
bootflash:asr1000-rommon.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg ...
done.
Deleting file
bootflash:asr1000-rommon.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.p
kg ... done.
Deleting file
bootflash:asr1000rp1-adventerprisek9.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_010
0_1.bin ... done.
Deleting file
bootflash:asr1000rp1-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080
924_0100_1.bin ... done.
Deleting file
bootflash:asr1000rp1-espbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg
... done.
Deleting file
bootflash:asr1000rp1-packages-adventerprisek9.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_200
80924_0100_1.conf ... done.
Deleting file
bootflash:asr1000rp1-packages-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LAT
EST_20080924_0100_1.conf ... done.
Deleting file
bootflash:asr1000rp1-rpaccess.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg
... done.
Deleting file
bootflash:asr1000rp1-rpbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg
... done.
Deleting file
bootflash:asr1000rp1-rpcontrol.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pk
g ... done.
Deleting file
bootflash:asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_200809
24_0100_1.pkg ... done.
Deleting file
bootflash:asr1000rp1-sipbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg
... done.
Deleting file
bootflash:asr1000rp1-sipspa.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg
... done.
Deleting file bootflash:packages.conf.00- ... done.
Deleting file bootflash:packages.conf.01- ... done.
Deleting file bootflash:packages.conf.02- ... done.
Deleting file bootflash:packages.conf.03- ... done.
Deleting file bootflash:packages.conf.04- ... done.
Deleting file bootflash:packages.conf.05- ... done.
Using SubPackages for Software Upgrade on a Cisco ASR 1002 or Cisco ASR 1004 Router (request platform Command Set)
This section provides instructions on using software upgrade for Cisco ASR 1002 or 1004 Router running subpackages using the request platform command set.
These instructions assume two IOS processes are active on the RP and that the router is already running using subpackages. For information on checking and configuring two IOS processes on the same RP, see the "Using SubPackages for Software Upgrade on a Cisco ASR 1002 or Cisco ASR 1004 Router (software upgrade Command Set)" section.
SUMMARY STEPS
1.
show version
show version installed
dir filesystem:<directory>
show platform
show redundancy-states
2.
redundancy
mode sso
3.
mkdir URL-to-directory-name
4.
ip tftp source-interface gigabitethernet slot/port
5.
copy tftp: URL-to-target-location
6.
request platform software package expand file URL-to-consolidated-package
7.
dir URL-to-consolidated-package
8.
copy file-system:asr1000rp1-espbase.version.pkg URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1000rp1-rpaccess.version.pkg URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1000rp1-rpbase.version.pkg URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1000rp1-rpcontrol.version.pkg URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1000rp1-rpios.version.pkg URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1000rp1-sipbase.version.pkg URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1000rp1-sipspa.version.pkg URL-to-directory-of-sub-packages-active-RP
9.
request platform software package install rp 0 file file-system:asr1000rp1-{rpaccess,rpios,rpcontrol}*version-string*.pkg bay standby-bay force
10.
redundancy force-switchover
11.
show platform
12.
request platform software package install rp 0 file file-system:asr1000rp1-{rpaccess,rpios,rpcontrol}*version-string*.pkg bay standby-bay force
13.
request platform software package install rp 0 file file-system:asr1000rp1-{sipbase,sipspa}*version*.pkg slot SIP-slot-number
Repeat this step for each SIP installed in your router before proceeding to the next step.
14.
request platform software package install rp 0 file file-system:asr1000rp1-esp*version*.pkg force
15.
request platform software package install rp 0 file file-system:asr1000rp*version*.pkg
16.
show version provisioned
17.
reload
18.
request platform software package clean
Note
Step 16, 17, 18 does not have to be performed immediately, and can be done at a convenient time.
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
show version
show version installed
dir filesystem:<directory>
show platform
show redundancy-states
Example:
Router# show version
Router# show version r0 installed
Router# dir bootflash:
Router# show platform
Router# show redundancy-states
|
(Optional) Use the following commands to confirm the current router configuration, as follows:
• show version and show version active-rp installed—Verify the running version of the Cisco IOS XE software on the router, and which file was used to boot the router, and where that file is stored.
• dir—Confirm that the files that were used to boot the router are located in the directory.
• show platform—Confirm the current status of the active and standby RPs.
• show redundancy states—Confirm the operational and configured redundancy states.
|
Step 2
|
redundancy
mode sso
Example:
Router(config)# redundancy
Router(config-red)# mode sso
|
Configure SSO if it is not already configured.
Note Save the configuration after making this configuration step.
|
Step 3
|
mkdir URL-to-directory-name
Example:
Router# mkdir usb0:221subs
|
Create a directory to store the consolidated package and subpackages.
This directory must be created in most cases because the consolidated packages and subpackages have to be separated from the subpackages that booted the router at this step of the procedure.
|
Step 4
|
ip tftp source-interface gigabitethernet slot/port
Example:
Router(config)# ip tftp source-interface
gigabitethernet 0
|
Specifies the Gigabit Ethernet TFTP source-interface to be configured:
slot/port—Specifies the location of the TFTP source-interface.
Note To copy a file using TFTP through the Management Ethernet interface, the ip tftp source-interface GigabitEthernet 0 command must be entered before entering the copy tftp command.
|
Step 5
|
copy tftp: URL-to-target-location
Example:
Router# copy tftp: usb0:221subs
|
Copy the consolidated package file into the directory created in Step 3.
The consolidated package in this step should not be copied into the same directory where the subpackages that are currently running your router are stored (the directory containing the packages.conf provisioning file from which the router was booted).
Tip  It is recommended that you copy the package onto a usb: or harddisk: file system for space considerations when performing this step of the procedure.
|
Step 6
|
request platform software package expand file
URL-to-consolidated-package
Example:
Router# request platform software package
expand file
usb0:221subs/asr1000rp1-adventerprisek9.02.02.0
1.122-33.XNB1.bin
|
Extract the subpackages out of the consolidated package file into the temporary directory.
Note Take extra care to extract the subpackages to a temporary subdirectory and do not delete any of the files currently running the router at this point of the procedure.
To erase the files that were running on the router before the ISSU upgrade, enter the request platform software package clean command after the ISSU upgrade has been completed.
|
Step 7
|
dir target-URL
Example:
Router# dir usb0:221subs
|
(Optional) Display the directory to confirm that the files were extracted.
|
Step 8
|
copy file-system:asr1000rp1-espbase.version.pkg
URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1000rp1-rpaccess.version.pkg
URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1000rp1-rpbase.version.pkg
URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1000rp1-rpcontrol.version.pkg
URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1000rp1-rpios.version.pkg
URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1000rp1-sipbase.version.pkg
URL-to-directory-of-sub-packages-active-RP
copy file-system:asr1000rp1-sipspa.version.pkg
URL-to-directory-of-sub-packages-active-RP
Example:
Router# copy
usb0:221subs/asr1000rp1-espbase.02.02.01.122-33
.XNB1.pkg bootflash:
Router# copy
usb0:221subs/asr1000rp1-rpaccess.02.02.01.122-3
3.XNB1.pkg bootflash:
Router# copy
usb0:221subs/asr1000rp1-rpbase.02.02.01.122-33.
XNB1.pkg bootflash:
Router# copy
usb0:221subs/asr1000rp1-rpcontrol.02.02.01.122-
33.XNB1.pkg bootflash:
Router# copy
usb0:221subs/asr1000rp1-rpios-adventerprisek9.0
2.02.01.122-33.XNB1.pkg bootflash:
Router# copy
usb0:221subs/asr1000rp1-sipbase.02.02.01.122-33
.XNB1.pkg bootflash:
Router# copy
usb0:221subs/asr1000rp1-sipspa.02.02.01.122-33.
XNB1.pkg bootflash:
|
Copy the subpackages out of the temporary directory into the directory on the router where the subpackages running the active RP are currently stored.
|
Step 9
|
request platform software package install rp 0
file
file-system:asr1000rp1-{rpaccess,rpios,rpcontrol
}*version-string*.pkg bay standby-bay force
Example:
Router# request platform software package
install rp 0 file
bootflash:asr1000rp1-{rpaccess,rpios,rpcontrol}
*02.02.01.122-33.XNB1*.pkg bay 1 force
|
Upgrade the RPAccess, RPIOS, and RPControl subpackages in the standby bay.
|
Step 10
|
redundancy force-switchover
Example:
Router# redundancy force-switchover
|
Force a switchover from the active IOS process to the standby IOS process.
Note Your connection to the router often drops and is expected behavior at this point of the procedure in many scenarios.
If this step drops your connection to the router, wait a few minutes before reconnecting to the router and then continue to Step 11.
|
Step 11
|
(Optional) show platform
Example:
Router# show platform
|
(Optional) Monitor system state to ensure both IOS processes are active.
|
Step 12
|
request platform software package install rp 0
file
file-system:asr1000rp1-{rpaccess,rpios,rpcontrol
}*version-string*.pkg bay standby-bay force
Example:
Router# request platform software package
install rp 0 file
bootflash:asr1000rp1-{rpaccess,rpios,rpcontrol}
*02.02.01.122-33.XNB1*.pkg bay 0 force
|
Upgrade the RPAccess, RPIOS, and RPControl subpackages in the standby bay, which in this context is the opposite bay used in Step 9.
Note The pattern options used in this CLI (rpaccess, rpios, and rpcontrol) were introduced in Cisco IOS XE Release 2.1.2 and are not available in previous Cisco IOS XE Releases. See the "ISSU Procedures (Prior to Cisco IOS XE Release 2.1.2)" section for pre-Cisco IOS XE Release 2.1.2 ISSU upgrade procedures.
|
Step 13
|
request platform software package install rp 0
file
file-system:asr1000rp1-{sipbase,sipspa}*version*.
pkg slot SIP-slot-number force
Repeat this step for each SIP installed in your
router before proceeding to the next step.
Example:
Router# request platform software package
install rp 0 file
bootflash:asr1000rp1-{sipspa,sipbase}*02.02.01.
122-33.XNB1*.pkg slot 0 force
Router# request platform software package
install rp 0 file
bootflash:asr1000rp1-{sipspa,sipbase}*02.02.01.
122-33.XNB1*.pkg slot 1 force
Router# request platform software package
install rp 0 file
bootflash:asr1000rp1-{sipspa,sipbase}*02.02.01.
122-33.XNB1*.pkg slot 2 force
|
Upgrade the SIP and SPA subpackages for each SIP on the router.
Note This step must be completed one SIP at a time, and repeated for each SIP installed on the router before performing the next step.
Tip  You can use the show ip interface brief command to identify which slots contain SIPs and SPAs. The interfaces with three numbers (in the form SIP-number/SPA-number/interface-number) identify the SIP and SPA locations in the router.
Note The pattern options used in this CLI (sipbase and sipspa) were introduced in Cisco IOS XE Release 2.1.2 and are not available in previous Cisco IOS XE Releases. See the "ISSU Procedures (Prior to Cisco IOS XE Release 2.1.2)" section for pre-Cisco IOS XE Release 2.1.2 ISSU upgrade procedures.
|
Step 14
|
request platform software package install rp 0
file file-system:asr1000rp1-esp*version*.pkg
force
Example:
Router# request platform software package
install rp 0 file
bootflash:asr1000rp1-esp*02.02.01.122-33.XNB1*.
pkg force
|
Upgrade the ESP Base subpackage.
|
Step 15
|
request platform software package install rp 0
file file-system:asr1000rp*version*.pkg
Example:
Router# request platform software package
install rp 0 file
bootflash:asr1000rp*02.02.01.122-33.XNB1*.pkg
|
Upgrade all subpackages, including the RPBase subpackage, which is the last subpackage that needs to be upgraded.
Note This step is required to ensure that all subpackages on the router were upgraded as part of this procedure, and might upgrade some subpackages that would otherwise be missed in the process.
|
Step 16
|
show version installed
Example:
Router# show version installed
|
(Optional) Verify that the subpackages are properly installed.
|
Step 17
|
reload
Example:
Router# reload
|
Reload the RP.
Tip  The router will continue normal operation even without a reload, so you can reload the router during scheduled maintenance or a slower traffic period.
|
Step 18
|
request platform software package clean
|
(Optional) Removes the unused subpackages from the router.
|
Examples
The following example shows the software upgrade for Cisco ASR 1002 or 1004 Router running sub-packages:
Cisco IOS Software, IOS-XE Software (PPC_LINUX_IOSD-ADVENTERPRISEK9-M), Version
12.2(33)XNA, RELEASE SOFTWARE (fc1)
<output removed for brevity>
System image file is "bootflash:packages.conf"
<output removed for brevity>
cisco ASR1004 (RP1) processor with 752142K/6147K bytes of memory.
5 Gigabit Ethernet interfaces
32768K bytes of non-volatile configuration memory.
4194304K bytes of physical memory.
937983K bytes of eUSB flash at bootflash:.
39004543K bytes of SATA hard disk at bootflash:.
253424K bytes of USB flash at usb0:.
Configuration register is 0x2102
Router# show version installed
Package: Provisioning File, version: n/a, status: active
File: bootflash:packages.conf, on: RP0
File SHA1 checksum: 9172d30751d79fc1afb7b405eca244bbf9f8f2f2
Package: rpbase, version: 02.01.00.122-33.XNA, status: active
File: bootflash:asr1000rp1-rpbase.02.01.00.122-33.XNA.pkg, on: RP0
Built: 2008-05-01_01.48, by: mcpre
File SHA1 checksum: c09fe08ff908c8ce0b789d8acc774fe43dacf5e3
Package: rpaccess, version: 02.01.01.122-33.XNA, status: active
File: bootflash:asr1000rp1-rpaccess.02.01.01.122-33.XNA.pkg, on: RP0
Built: 2008-07-08_16.01, by: mcpre
File SHA1 checksum: c1afc591c9cd198409820226c4f23d2647d0d138
<output removed for brevity>
Router# show redundancy states
peer state = 4 -STANDBY COLD
Redundancy Mode (Operational) = sso
Redundancy Mode (Configured) = sso
Maintenance Mode = Disabled
Manual Swact = disabled (peer unit not yet in terminal standby state)
client_notification_TMR = 30000 milliseconds
Slot Type State Insert time (ago)
--------- ------------------- --------------------- -----------------
0 ASR1000-SIP10 ok 00:04:43
0/0 SPA-1XOC12-POS ok 00:03:25
0/1 SPA-2XOC3-POS ok 00:03:24
0/3 SPA-5X1GE-V2 ok 00:03:20
R0 ASR1000-RP1 ok 00:04:43
R0/1 ok, standby 00:02:55
F0 ASR1000-ESP10 ok, active 00:04:43
P0 ASR1004-PWR-AC ok 00:03:53
P1 ASR1004-FAN ok 00:03:53
Slot CPLD Version Firmware Version
--------- ------------------- ---------------------------------------
Router# mkdir usb0:221subs
Create directory filename [221subs]?
Created dir bootflash:221subs
Router(config)# ip tftp source-interface gigabitethernet 0
Router# copy tftp: usb0:221subs
Address or name of remote host []? 172.17.16.81
Source filename []? /auto/users/asr1000rp1-adventerprisek9.02.02.01.122-33.XNB1.bin
Destination filename [asr1000rp1-adventerprisek9.02.02.01.122-33.XNB1.bin]?
Accessing
tftp://172.17.16.81//auto/users/asr1000rp1-adventerprisek9.02.02.01.122-33.XNB1.bin...
Loading /auto/users/asr1000rp1-adventerprisek9.02.02.01.122-33.XNB1.bin from 172.17.16.81
(via GigabitEthernet0):
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!.!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!
209227980 bytes copied in 880.002 secs (237759 bytes/sec)
Router# request platform software package expand file
usb0:221subs/asr1000rp1-adventerprisek9.02.02.01.122-33.XNB1.bin
SUCCESS: Finished expanding all-in-one software package.
Directory of usb0:/221subs/
72013 -rw- 51904716 Oct 7 2008 15:46:02 -07:00
asr1000rp1-espbase.02.02.01.122-33.XNB1.pkg
72004 -rw- 5773 Oct 7 2008 15:46:02 -07:00
asr1000rp1-packages-adventerprisek9.02.02.01.122-33.XNB1.conf
72014 -rw- 20533452 Oct 7 2008 15:46:03 -07:00
asr1000rp1-rpaccess.02.02.01.122-33.XNB1.pkg
72015 -rw- 22388940 Oct 7 2008 15:46:03 -07:00
asr1000rp1-rpbase.02.02.01.122-33.XNB1.pkg
72016 -rw- 27961548 Oct 7 2008 15:46:03 -07:00
asr1000rp1-rpcontrol.02.02.01.122-33.XNB1.pkg
72017 -rw- 50942156 Oct 7 2008 15:46:03 -07:00
asr1000rp1-rpios-adventerprisek9.02.02.01.122-33.XNB1.pkg
72018 -rw- 36442316 Oct 7 2008 15:46:03 -07:00
asr1000rp1-sipbase.02.02.01.122-33.XNB1.pkg
72019 -rw- 26366156 Oct 7 2008 15:46:03 -07:00
asr1000rp1-sipspa.02.02.01.122-33.XNB1.pkg
72005 -rw- 6290 Oct 7 2008 15:46:03 -07:00 packages.conf
72003 -rw- 224768204 Oct 7 2008 15:38:57 -07:00
asr1000rp1-adventerprisek9.02.02.01.122-33.XNB1.bin
928862208 bytes total (466358272 bytes free)
Router# copy usb0:221subs/asr1000rp1-espbase.02.02.01.122-33.XNB1.pkg bootflash:
Destination filename [asr1000rp1-espbase.02.02.01.122-33.XNB1.pkg]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
51904716 bytes copied in 5.478 secs (9475122 bytes/sec)
Router# copy usb0:221subs/asr1000rp1-rpaccess.02.02.01.122-33.XNB1.pkg bootflash:
Destination filename [asr1000rp1-rpaccess.02.02.01.122-33.XNB1.pkg]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
20533452 bytes copied in 2.346 secs (8752537 bytes/sec)
Router# copy usb0:221subs/asr1000rp1-rpbase.02.02.01.122-33.XNB1.pkg bootflash:
Destination filename [asr1000rp1-rpbase.02.02.01.122-33.XNB1.pkg]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
22388940 bytes copied in 2.496 secs (8969928 bytes/sec)
Router# copy usb0:221subs/asr1000rp1-rpcontrol.02.02.01.122-33.XNB1.pkg bootflash:
Destination filename [asr1000rp1-rpcontrol.02.02.01.122-33.XNB1.pkg]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
27961548 bytes copied in 2.992 secs (9345437 bytes/sec)
Router# copy usb0:221subs/asr1000rp1-rpios-adventerprisek9.02.02.01.122-33.XNB1.pkg
bootflash:
Destination filename [asr1000rp1-rpios-adventerprisek9.02.02.01.122-33.XNB1.pkg]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
50942156 bytes copied in 5.719 secs (8907529 bytes/sec)
Router# copy usb0:221subs/asr1000rp1-sipbase.02.02.01.122-33.XNB1.pkg bootflash:
Destination filename [asr1000rp1-sipbase.02.02.01.122-33.XNB1.pkg]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCC
36442316 bytes copied in 3.906 secs (9329830 bytes/sec)
Router# copy usb0:221subs/asr1000rp1-sipspa.02.02.01.122-33.XNB1.pkg bootflash:
Destination filename [asr1000rp1-sipspa.02.02.01.122-33.XNB1.pkg]?
Copy in
progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
26366156 bytes copied in 2.857 secs (9228616 bytes/sec)
Router# request platform software package install rp 0 file
bootflash:asr1000rp1-{rpaccess,rpios,rpcontrol}*02.02.01.122-33.XNB1*.pkg bay 1 force
--- Starting file path checking ---
Finished file path checking
--- Starting image file verification ---
Checking image file names
Verifying image file locations
Locating image files and validating name syntax
Inspecting image file types
Processing image file constraints
Creating candidate provisioning file
Finished image file verification
--- Starting candidate package set construction ---
Verifying existing software set
Processing candidate provisioning file
Constructing working set for candidate package set
Constructing working set for running package set
Constructing merge of running and candidate packages
Finished candidate package set construction
--- Starting compatibility testing ---
Determining whether candidate package set is compatible
WARNING: Candidate software combination not found in compatibility database
Determining whether installation is valid
WARNING: Candidate software combination not found in compatibility database
WARNING: Candidate software combination not found in compatibility database
Software sets are identified as compatible
Checking IPC compatibility with running software
Checking candidate package set infrastructure compatibility
Checking infrastructure compatibility with running software
Checking package specific compatibility
Finished compatibility testing
--- Starting impact testing ---
Checking operational impact of change
WARNING: Connection may be lost during installation of IOS package
--- Starting commit of software changes ---
Updating provisioning rollback files
Creating pending provisioning file
Committing provisioning file
Finished commit of software changes
--- Starting analysis of software changes ---
Finished analysis of software changes
--- Starting update running software ---
Blocking peer synchronization of operating information
Creating the command set placeholder directory
Finding latest command set
Finding latest command shortlist lookup file
Finding latest command shortlist file
Assembling CLI output libraries
Assembling CLI input libraries
Applying interim IPC and database definitions
Replacing running software
*Sep 25 11:23:27.008: %ASR1000_INFRA-6-BIPC_READ_ERR: R0/0: ppc_linux_iosd-image:
connection read error from iman bipc, rc 32, bring down IPC Restarting IOS PID: 19252, in
slot/bay 0/1
*Sep 25 11:23:41.837: %PMAN-3-PROCHOLDDOWN: R0/0: pman.sh: The process
ppc_linux_iosd-image has been helddown (rc 137)
*Sep 25 11:23:41.920: %PMAN-0-PROCFAILCRIT: R0/0: pvp.sh: A critical process
ppc_linux_iosd_image has failed (rc 137)
*Sep 25 11:23:41.962: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault
(PEER_NOT_PRESENT)
*Sep 25 11:23:41.962: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER_DOWN)
*Sep 25 11:23:41.962: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault
(PEER_REDUNDANCY_STATE_CHANGE)FIXME: kill/restart security package: 0 1 rp_security
Applying final IPC and database definitions
Generating software version information
Notifying running software of updates
Unblocking peer synchronization of operating information
Cleaning temporary installation files
Finished update running software
SUCCESS: Finished installing software.
*Sep 25 11:24:35.148: %REDUNDANCY-5-PEER_MONITOR_EVENT: Active detected a standby
insertion (raw-event=PEER_FOUND(4))
*Sep 25 11:24:35.149: %REDUNDANCY-5-PEER_MONITOR_EVENT: Active detected a standby
insertion (raw-event=PEER_REDUNDANCY_STATE_CHANGE(5))
*Sep 25 11:24:36.067: %REDUNDANCY-3-IPC: IOS versions do not match.
*Sep 25 11:26:48.281: %HA_CONFIG_SYNC-6-BULK_CFGSYNC_SUCCEED: Bulk Sync succeeded
*Sep 25 11:26:48.283: %RF-5-RF_TERMINAL_STATE: Terminal state reached for (SSO)
Router# redundancy force-switchover
Proceed with switchover to standby RP? [confirm]
%ASR1000_INFRA-6-CONSOLE_ACTIVE: R0/1 console active. Press RETURN to get started!
*Sep 25 11:31:33.401: %NETCLK-5-NETCLK_MODE_CHANGE: Network clock source not available.
The network clock has changed to freerun
*Sep 25 11:31:33.438: %REDUNDANCY-3-SWITCHOVER: RP switchover (PEER_NOT_PRESENT)
*Sep 25 11:31:33.438: %REDUNDANCY-3-SWITCHOVER: RP switchover (PEER_DOWN)
*Sep 25 11:31:33.438: %REDUNDANCY-3-SWITCHOVER: RP switchover
(PEER_REDUNDANCY_STATE_CHANGE)
*Sep 25 11:31:33.442: %PLATFORM-6-HASTATUS: RP switchover, sent message became active. IOS
is ready to switch to primary after
*Sep 25 11:31:33.061: %SYS-5-SWITCHOVER: Switchover requested by Exec. Reason: redundancy
force-switchover. chassis confirmation
*Sep 25 11:31:33.446: %CMANRP-6-CMHASTATUS: RP switchover, received chassis event became
active
*Sep 25 11:31:33.692: %PLATFORM-6-HASTATUS_DETAIL: RP switchover, received chassis event
became active. Switch to primary (count 1)
*Sep 25 11:31:35.683: %ACE-3-TRANSERR: ASR1000-ESP(14): IKEA trans 0x3; opcode 0x25; param
0xA; error 0x4; retry cnt 0
*Sep 25 11:31:35.683: %ACE-3-TRANSERR: ASR1000-ESP(14): IKEA trans 0x4; opcode 0x25; param
0xB; error 0x4; retry cnt 0
*Sep 25 11:31:35.684: %ACE-3-TRANSERR: ASR1000-ESP(14): IKEA trans 0x5; opcode 0x25; param
0xC; error 0x4; retry cnt 0
*Sep 25 11:31:35.802: %LINK-3-UPDOWN: Interface Null0, changed state to up
*Sep 25 11:31:35.803: %LINK-3-UPDOWN: Interface Loopback0, changed state to up
*Sep 25 11:31:35.808: %LINK-5-CHANGED: Interface POS0/0/0, changed state to
administratively down
*Sep 25 11:31:35.808: %LINK-5-CHANGED: Interface POS0/1/0, changed state to
administratively down
*Sep 25 11:31:35.808: %LINK-5-CHANGED: Interface POS0/1/1, changed state to
administratively down
*Sep 25 11:31:35.808: %LINK-5-CHANGED: Interface GigabitEthernet0/3/0, changed state to
administratively down
*Sep 25 11:31:35.808: %LINK-5-CHANGED: Interface GigabitEthernet0/3/1, changed state to
administratively down
*Sep 25 11:31:35.808: %LINK-5-CHANGED: Interface GigabitEthernet0/3/2, changed state to
administratively down
*Sep 25 11:31:35.808: %LINK-5-CHANGED: Interface GigabitEthernet0/3/3, changed state to
administratively down
*Sep 25 11:31:35.808: %LINK-5-CHANGED: Interface GigabitEthernet0/3/4, changed state to
administratively down
*Sep 25 11:31:36.802: %LINEPROTO-5-UPDOWN: Line protocol on Interface Null0, changed state
to up
*Sep 25 11:31:36.802: %LINEPROTO-5-UPDOWN: Line protocol on Interface Loopback0, changed
state to up
*Sep 25 11:32:21.530: %REDUNDANCY-3-IPC: IOS versions do not match.
*Sep 25 11:32:21.615: %REDUNDANCY-5-PEER_MONITOR_EVENT: Active detected a standby
insertion (raw-event=PEER_FOUND(4))
*Sep 25 11:32:21.615: %REDUNDANCY-5-PEER_MONITOR_EVENT: Active detected a standby
insertion (raw-event=PEER_REDUNDANCY_STATE_CHANGE(5))
*Sep 25 11:34:05.450: %HA_CONFIG_SYNC-6-BULK_CFGSYNC_SUCCEED: Bulk Sync succeeded
*Sep 25 11:34:05.453: %RF-5-RF_TERMINAL_STATE: Terminal state reached for (SSO)
Slot Type State Insert time (ago)
--------- ------------------- --------------------- -----------------
0 ASR1000-SIP10 ok 00:31:12
0/0 SPA-1XOC12-POS ok 00:11:35
0/1 SPA-2XOC3-POS ok 00:11:35
0/3 SPA-5X1GE-V2 ok 00:11:35
R0 ASR1000-RP1 ok 00:31:12
R0/0 ok, standby 00:05:38
F0 ASR1000-ESP10 ok, active 00:31:12
P0 ASR1004-PWR-AC ok 00:30:22
P1 ASR1004-FAN ok 00:30:22
Slot CPLD Version Firmware Version
--------- ------------------- ---------------------------------------
Router# request platform software package install rp 0 file
bootflash:asr1000rp1-{rpaccess,rpios,rpcontrol}*02.02.01.122-33.XNB1*.pkg bay 0 force
--- Starting file path checking ---
Finished file path checking
--- Starting image file verification ---
Checking image file names
Verifying image file locations
Locating image files and validating name syntax
Inspecting image file types
Processing image file constraints
Creating candidate provisioning file
Finished image file verification
--- Starting candidate package set construction ---
Verifying existing software set
Processing candidate provisioning file
Constructing working set for candidate package set
Constructing working set for running package set
Constructing merge of running and candidate packages
Finished candidate package set construction
--- Starting compatibility testing ---
Determining whether candidate package set is compatible
WARNING: Candidate software combination not found in compatibility database
Determining whether installation is valid
Software sets are identified as compatible
Checking IPC compatibility with running software
Checking candidate package set infrastructure compatibility
Checking infrastructure compatibility with running software
Checking package specific compatibility
Finished compatibility testing
--- Starting impact testing ---
Checking operational impact of change
WARNING: Connection may be lost during installation of IOS package
--- Starting commit of software changes ---
Updating provisioning rollback files
Creating pending provisioning file
Committing provisioning file
*Sep 25 11:39:35.632: %ACE-3-INITFAIL: ASR1000-ESP(14): initialization failed (timed
out)Finished commit of software changes
--- Starting analysis of software changes ---
Finished analysis of software changes
--- Starting update running software ---
Blocking peer synchronization of operating information
Creating the command set placeholder directory
Finding latest command set
Finding latest command shortlist lookup file
Finding latest command shortlist file
Assembling CLI output libraries
Assembling CLI input libraries
Applying interim IPC and database definitions
Replacing running software
*Sep 25 11:40:31.859: %IOSXE-4-PLATFORM: R0/0: kernel: scooby: Scooby: FD close
Restarting IOS PID: 21974, in slot/bay 0/0
FIXME: kill/restart security package: 0 0 rp_security
Applying final IPC and database definitions
*Sep 25 11:40:59.590: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault
(PEER_NOT_PRESENT)
*Sep 25 11:40:59.591: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault (PEER_DOWN)
*Sep 25 11:40:59.591: %REDUNDANCY-3-STANDBY_LOST: Standby processor fault
(PEER_REDUNDANCY_STATE_CHANGE)
*Sep 25 11:41:02.177: %DYNCMD-7-CMDSET_UNLOADED: The Dynamic Command set from the Shell
Manager has been unloaded
*Sep 25 11:41:02.719: %DYNCMD-7-CMDSET_LOADED: The Dynamic Command set has been loaded
from the Shell Manager
*Sep 25 11:41:05.397: %RF-5-RF_RELOAD: Peer reload. Reason: EHSA standby down Generating
software version information
Notifying running software of updates
Unblocking peer synchronization of operating information
Cleaning temporary installation files
Finished update running software
SUCCESS: Finished installing software.
*Sep 25 11:41:50.918: %CMRP-5-PRERELEASE_HARDWARE: R0/0: cmand: 0:0 is pre-release
hardware
*Sep 25 11:41:50.937: %REDUNDANCY-5-PEER_MONITOR_EVENT: Active detected a standby
insertion (raw-event=PEER_FOUND(4))
*Sep 25 11:41:50.937: %REDUNDANCY-5-PEER_MONITOR_EVENT: Active detected a standby
insertion (raw-event=PEER_REDUNDANCY_STATE_CHANGE(5))
Router# request platform software package install rp 0 file
bootflash:asr1000rp1-{sipspa,sipbase}*02.02.01.122-33.XNB1*.pkg slot 0 force
--- Starting file path checking ---
Finished file path checking
--- Starting image file verification ---
Checking image file names
Verifying image file locations
Locating image files and validating name syntax
Inspecting image file types
Processing image file constraints
Creating candidate provisioning file
Finished image file verification
--- Starting candidate package set construction ---
Verifying existing software set
Processing candidate provisioning file
Constructing working set for candidate package set
Constructing working set for running package set
Constructing merge of running and candidate packages
Finished candidate package set construction
--- Starting compatibility testing ---
Determining whether candidate package set is compatible
WARNING: Candidate software combination not found in compatibility database
Determining whether installation is valid
WARNING: Candidate software combination not found in compatibility database
WARNING: Candidate software combination not found in compatibility database
Software sets are identified as compatible
Checking IPC compatibility with running software
Checking candidate package set infrastructure compatibility
Checking infrastructure compatibility with running software
Checking package specific compatibility
Finished compatibility testing
--- Starting impact testing ---
Checking operational impact of change
--- Starting commit of software changes ---
Updating provisioning rollback files
Creating pending provisioning file
Committing provisioning file
Finished commit of software changes
--- Starting analysis of software changes ---
Finished analysis of software changes
--- Starting update running software ---
Blocking peer synchronization of operating information
Creating the command set placeholder directory
Finding latest command set
Finding latest command shortlist lookup file
Finding latest command shortlist file
Assembling CLI output libraries
Assembling CLI input libraries
Applying interim IPC and database definitions
Replacing running software
Applying final IPC and database definitions
*Sep 29 10:11:16.631: %ASR1000_OIR-6-OFFLINECARD: Card (cc) offline in slot 0
*Sep 29 10:11:16.632: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 0/0, interfaces
disabled
*Sep 29 10:11:16.632: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 0/1, interfaces
disabled
*Sep 29 10:11:16.632: %ASR1000_OIR-6-REMSPA: SPA removed from subslot 0/3, interfaces
disabled
*Sep 29 10:11:24.575: %CMRP-5-PRERELEASE_HARDWARE: R0/0: cmand: 0:0 is pre-release
hardware Generating software version information
Notifying running software of updates
Unblocking peer synchronization of operating information
Cleaning temporary installation files
Finished update running software
SUCCESS: Finished installing software.
*Sep 29 10:12:00.274: %ASR1000_OIR-6-ONLINECARD: Card (cc) online in slot 0
*Sep 29 10:12:00.271: %CMRP-5-PRERELEASE_HARDWARE: R0/0: cmand: 0:0 is pre-release
hardware
*Sep 29 10:12:01.833: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 0/0
*Sep 29 10:12:02.579: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 0/1
*Sep 29 10:12:03.460: %ASR1000_OIR-6-INSSPA: SPA inserted in subslot 0/3
*Sep 29 10:12:10.405: %LINK-3-UPDOWN: SIP0/0: Interface EOBC0/1, changed state to up
*Sep 29 10:12:16.944: %SPA_OIR-6-ONLINECARD: SPA (SPA-1XOC12-POS) online in subslot 0/0
*Sep 29 10:12:15.024: %LINK-3-UPDOWN: SIP0/1: Interface EOBC0/1, changed state to up
*Sep 29 10:12:20.938: %SPA_OIR-6-ONLINECARD: SPA (SPA-2XOC3-POS) online in subslot 0/1
*Sep 29 10:12:17.086: %LINK-3-UPDOWN: SIP0/3: Interface EOBC0/1, changed state to up
*Sep 29 10:12:23.640: %SPA_OIR-6-ONLINECARD: SPA (SPA-5X1GE-V2) online in subslot 0/3
Router# request platform software package install rp 0 file
bootflash:asr1000rp1-{sipspa,sipbase}*02.02.01.122-33.XNB1*.pkg slot 1 force
--- Starting file path checking ---
Finished file path checking
--- Starting image file verification ---
Checking image file names
Verifying image file locations
Locating image files and validating name syntax
Inspecting image file types
Processing image file constraints
Creating candidate provisioning file
Finished image file verification
--- Starting candidate package set construction ---
Verifying existing software set
Processing candidate provisioning file
Constructing working set for candidate package set
Constructing working set for running package set
Constructing merge of running and candidate packages
Finished candidate package set construction
--- Starting compatibility testing ---
Determining whether candidate package set is compatible
WARNING: Candidate software combination not found in compatibility database
Determining whether installation is valid
Software sets are identified as compatible
Checking IPC compatibility with running software
Checking candidate package set infrastructure compatibility
Checking infrastructure compatibility with running software
Checking package specific compatibility
Finished compatibility testing
--- Starting impact testing ---
Checking operational impact of change
--- Starting commit of software changes ---
Updating provisioning rollback files
Creating pending provisioning file
Committing provisioning file
Finished commit of software changes
--- Starting analysis of software changes ---
Finished analysis of software changes
--- Starting update running software ---
Blocking peer synchronization of operating information
Creating the command set placeholder directory
Finding latest command set
Finding latest command shortlist lookup file
Finding latest command shortlist file
Assembling CLI output libraries
Assembling CLI input libraries
Applying interim IPC and database definitions
Replacing running software
Applying final IPC and database definitions
Generating software version information
Notifying running software of updates
Unblocking peer synchronization of operating information
Cleaning temporary installation files
Finished update running software
SUCCESS: Finished installing software.
Router# request platform software package install rp 0 file
bootflash:asr1000rp1-esp*02.02.01.122-33.XNB1*.pkg force
--- Starting file path checking ---
Finished file path checking
--- Starting image file verification ---
Checking image file names
Verifying image file locations
Locating image files and validating name syntax
Inspecting image file types
Processing image file constraints
Creating candidate provisioning file
Finished image file verification
--- Starting candidate package set construction ---
Verifying existing software set
Processing candidate provisioning file
Constructing working set for candidate package set
Constructing working set for running package set
Constructing merge of running and candidate packages
Finished candidate package set construction
--- Starting compatibility testing ---
Determining whether candidate package set is compatible
WARNING: Candidate software combination not found in compatibility database
Determining whether installation is valid
WARNING: Candidate software combination not found in compatibility database
WARNING: Candidate software combination not found in compatibility database
Software sets are identified as compatible
Checking IPC compatibility with running software
Checking candidate package set infrastructure compatibility
Checking infrastructure compatibility with running software
Checking package specific compatibility
Finished compatibility testing
--- Starting impact testing ---
Checking operational impact of change
--- Starting commit of software changes ---
Updating provisioning rollback files
Creating pending provisioning file
Committing provisioning file
Finished commit of software changes
--- Starting analysis of software changes ---
Finished analysis of software changes
--- Starting update running software ---
Blocking peer synchronization of operating information
Creating the command set placeholder directory
Finding latest command set
Finding latest command shortlist lookup file
Finding latest command shortlist file
Assembling CLI output libraries
Assembling CLI input libraries
Applying interim IPC and database definitions
Replacing running software
Applying final IPC and database definitions
*Sep 25 12:43:27.892: %ASR1000_OIR-6-OFFLINECARD: Card (fp) offline in slot F0
*Sep 25 12:43:29.992: %CMRP-5-PRERELEASE_HARDWARE: R0/0: cmand: F0:0 is pre-release
hardware Generating software version information
Notifying running software of updates
Unblocking peer synchronization of operating information
Cleaning temporary installation files
Finished update running software
SUCCESS: Finished installing software.
*Sep 25 12:44:11.960: %ASR1000_OIR-6-ONLINECARD: Card (fp) online in slot F0
*Sep 25 12:44:11.957: %CMRP-5-PRERELEASE_HARDWARE: R0/0: cmand: F0:0 is pre-release
hardware
*Sep 25 12:44:21.256: %CPPHA-7-SYSREADY: F0: cpp_ha: CPP client process FMAN-FP (5 of 5)
ready.
*Sep 25 12:44:21.798: %CPPHA-7-START: F0: cpp_ha: CPP 0 preparing image
/usr/cpp/bin/cpp-mcplo-ucode
*Sep 25 12:44:21.909: %CPPHA-7-START: F0: cpp_ha: CPP 0 startup init image
/usr/cpp/bin/cpp-mcplo-ucode
*Sep 25 12:44:26.763: %CPPHA-7-START: F0: cpp_ha: CPP 0 running init image
/usr/cpp/bin/cpp-mcplo-ucode
*Sep 25 12:44:27.004: %CPPHA-7-READY: F0: cpp_ha: CPP 0 loading and initialization
complete
*Sep 25 12:44:27.004: %CPPHA-6-SYSINIT: F0: cpp_ha: CPP HA system configuration start.
*Sep 25 12:44:28.321: %IOSXE-6-PLATFORM: F0: cpp_cp: Process
CPP_PFILTER_EA_EVENT__API_CALL__REGISTER
*Sep 25 12:44:28.516: %CPPHA-6-SYSINIT: F0: cpp_ha: CPP HA system enabled.
*Sep 25 12:44:28.517: %CPPHA-6-SYSINIT: F0: cpp_ha: CPP HA system initialization
complete.
Router# request platform software package install rp 0 file
bootflash:asr1000rp*02.02.01.122-33.XNB1*.pkg
--- Starting file path checking ---
Finished file path checking
--- Starting image file verification ---
Checking image file names
Verifying image file locations
Locating image files and validating name syntax
Inspecting image file types
WARNING: In-service installation of RP Base package
WARNING: requires software reboot of target RP
WARNING: Automatically setting the on-reboot flag
Processing image file constraints
Creating candidate provisioning file
Finished image file verification
--- Starting candidate package set construction ---
Verifying existing software set
Processing candidate provisioning file
Constructing working set for candidate package set
Constructing working set for running package set
Constructing merge of running and candidate packages
Finished candidate package set construction
--- Starting compatibility testing ---
Determining whether candidate package set is compatible
Determining whether installation is valid
Determining whether installation is valid ... skipped
Checking IPC compatibility for candidate software
Checking candidate package set infrastructure compatibility
Checking infrastructure compatibility with running software
Checking infrastructure compatibility with running software ... skipped
Checking package specific compatibility
Finished compatibility testing
--- Starting commit of software changes ---
Updating provisioning rollback files
Creating pending provisioning file
Committing provisioning file
Finished commit of software changes
SUCCESS: Software provisioned. New software will load on reboot.
Proceed with reload? [confirm]y
Router# request platform software package clean
Cleaning up unnecessary package files
No path specified, will use booted path bootflash:packages.conf
Scanning boot directory for packages ... done.
Preparing packages list to delete ...
asr1000rp1-espbase.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg
File is in use, will not delete.
asr1000rp1-rpaccess.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg
File is in use, will not delete.
asr1000rp1-rpbase.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg
File is in use, will not delete.
asr1000rp1-rpcontrol.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg
File is in use, will not delete.
asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_
0100_1.pkg
File is in use, will not delete.
asr1000rp1-sipbase.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg
File is in use, will not delete.
asr1000rp1-sipspa.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg
File is in use, will not delete.
File is in use, will not delete.
Files that will be deleted:
asr1000-rommon.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg
asr1000-rommon.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.pkg
asr1000rp1-adventerprisek9.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.bin
asr1000rp1-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1
.bin
asr1000rp1-espbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg
asr1000rp1-packages-adventerprisek9.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100
_1.conf
asr1000rp1-packages-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_200809
24_0100_1.conf
asr1000rp1-rpaccess.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg
asr1000rp1-rpbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg
asr1000rp1-rpcontrol.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg
asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.
pkg
asr1000rp1-sipbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg
asr1000rp1-sipspa.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg
Do you want to proceed? [confirm]y
Deleting file
bootflash:asr1000-rommon.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg ...
done.
Deleting file
bootflash:asr1000-rommon.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080924_0100_1.p
kg ... done.
Deleting file
bootflash:asr1000rp1-adventerprisek9.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_010
0_1.bin ... done.
Deleting file
bootflash:asr1000rp1-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LATEST_20080
924_0100_1.bin ... done.
Deleting file
bootflash:asr1000rp1-espbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg
... done.
Deleting file
bootflash:asr1000rp1-packages-adventerprisek9.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_200
80924_0100_1.conf ... done.
Deleting file
bootflash:asr1000rp1-packages-adventerprisek9.BLD_V122_33_XNB_ASR_02.02.01.122-33.XNB1_LAT
EST_20080924_0100_1.conf ... done.
Deleting file
bootflash:asr1000rp1-rpaccess.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg
... done.
Deleting file
bootflash:asr1000rp1-rpbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg
... done.
Deleting file
bootflash:asr1000rp1-rpcontrol.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pk
g ... done.
Deleting file
bootflash:asr1000rp1-rpios-adventerprisek9.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_200809
24_0100_1.pkg ... done.
Deleting file
bootflash:asr1000rp1-sipbase.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg
... done.
Deleting file
bootflash:asr1000rp1-sipspa.BLD_V122_33_XNA_ASR_RLS1_THROTTLE_LATEST_20080924_0100_1.pkg
... done.
Deleting file bootflash:packages.conf.00- ... done.
Deleting file bootflash:packages.conf.01- ... done.
Deleting file bootflash:packages.conf.02- ... done.
Deleting file bootflash:packages.conf.03- ... done.
Deleting file bootflash:packages.conf.04- ... done.
Deleting file bootflash:packages.conf.05- ... done.
Minimal Disruptive Restart Process
A software upgrade of a SIP in any mode results in the SIP being reset and the occurrence of minimal outage during the upgrade. Minimal Disruptive Restart (MDR) minimizes traffic disruption during a software upgrade and supports consolidated package software upgrade and subpackage software upgrade for SIP-40.
The software upgrade of a SIP using MDR is supported only on the Cisco ASR 1000 Series Aggregation Services routers running Cisco IOS XE Release 3.8S and later.
Note
MDR upgrades (both consolidated and subpackage upgrades) are supported only on hardware-redundant dual route processor (RP) and Enhanced Services Processors (ESP) platforms.
MDR process reduces the downtime (time during which the data plane is unavailable) due to a reload of a SIP or a SPA. The downtime is reduced from 100 seconds to not more than 25 seconds on a SIP reload and from 30 seconds to not more than 10 seconds on a SPA reload. The reload time of a SIP or SPA using a MDR or a non-MDR upgrade remains the same.
MDR for a SIP is permitted if following conditions are met:
•
Chassis is hardware redundant (dual RP and dual ESP)
•
SIP-type supports MDR.
•
At least one MDR-compatible SPA in the SIP should be present for the MDR process.
•
All the SPAs associated with the SIP support MDR.
•
Both the current software version and the upgrade software version must be ISSU and MDR compatible for both the SIPBase and SIPSPA subpackages for each SPA type that is present.
The following SPAs support MDR:
–
SPA-2X1GE-V2
–
SPA-5X1GE-V2
–
SPA-8X1GE-V2
–
SPA-10X1GE-V2
–
SPA-1X10GE-L-V2
Use the request platform software package verify rp file and issu checkversion commands with the MDR option to verify the MDR upgrade compatibility of a consolidated package or an individual subpackage.
When performing an ISSU upgrade, you can specify whether the upgrade should use MDR. If you do not specify this, the ISSU upgrade process will remain unchanged.
For more information on ISSU upgrade for nonredundant platforms, see "Upgrade Process With Service Impact for Nonredundant Platforms" section.
Restrictions and Limitations
•
MDR is not supported on nonhardware-redundant platforms, such as, Cisco ASR 1001 Router, Cisco ASR 1002 Router, Cisco ASR 1002-X Router, or Cisco ASR 1004 Router, and on hardware-redundant platforms without redundant hardware, such as, Cisco ASR 1006 router, or Cisco ASR 1013 router with only a single RP or ESP.
•
MDR is not supported on SIP10.
•
MDR does not support software downgrade.
•
To use MDR, both the current software and the upgrade software must be ISSU and MDR compatible.
•
If a SIP is performing an MDR upgrade the following events cannot be handled during the upgrade:
–
Fast Reroute (FRR)
–
Automatic protection switching (APS)
–
Ethernet over Multiprotocol Label Switching (EoMPLS) and pseudoWire (PW) down that require an attachment circuit (AC) port to be shut.
–
Interface flaps and interface errors
–
Interface-specific or linecard-specific configuration changes
–
SPA Online Insertion and Removal (OIR)
–
Transceiver OIR
–
Line alarms
–
Statistics—Error counts will be reset
High Availability Considerations
Any high-availability (HA) failover that occurs during MDR-process terminates the process. This includes failures such as active RP IOS failover during the MDR upgrade process or active RP FRU failure in a chassis with redundant hardware during subpackage upgrade.
For MDR upgrade using consolidated packages, upgrade is initiated by the upgraded active RP after the ESP software has been upgraded.
Additional References
The following sections provide references related to the Software Upgrade Process feature.
Related Documents
Related Topic
|
Title
|
Cisco IOS XE commands
|
Cisco IOS Master Commands List, All Releases
|
Performing an In Service Software Upgrade
|
High Availability Configuration Guide, Cisco IOS XE Release 3S
|
Standards
Standard
|
Title
|
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.
|
—
|
MIBs
MIB
|
MIBs Link
|
None
|
To locate and download MIBs for selected platforms, Cisco IOS XE software releases, and feature sets, use Cisco MIB Locator found at the following URL:
http://www.cisco.com/go/mibs
|
RFCs
RFC
|
Title
|
No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature.
|
—
|
Technical Assistance
Description
|
Link
|
The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies.
To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds.
Access to most tools on the Cisco Support website requires a Cisco.com user ID and password.
|
http://www.cisco.com/cisco/web/support/index.html
|
Feature Information for Software Upgrade Process
Table 13 lists the release history for this feature on the Cisco ASR 1000 Series Routers.
For information on a feature in this technology that is not documented here, see the Cisco ASR 1000 Series Aggregation Services Routers Documentation Roadmap.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS XE software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note
Table 13 lists only the Cisco IOS XE software release that introduced support for a given feature in a given Cisco IOS XE software release train. Unless noted otherwise, subsequent releases of that Cisco IOS XE software release train also support that feature.
Table 13 Feature Information for Software Upgrade Process
Feature Name
|
Releases
|
Feature Information
|
Minimal Disruptive Restart Process
|
Cisco IOS XE Release 3.8
|
This feature supports a software upgrade of a SIP with minimal disruptive restart.
|
Software Upgrade Process
|
Cisco IOS XE Release 2.6
|
This feature was introduced.
Cisco ASR 1000 Series Routers support the following software upgrade procedures:
• In Service Software Upgrades (ISSU) for redundant platforms
• Upgrade process with service impact for nonredundant platforms.
|
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
Cisco ASR 1000 Series Aggregation Services Routers Software Configuration Guide
Copyright © 2008 - 2013 Cisco Systems, Inc. All rights reserved.