Table Of Contents
In Service Software Upgrades (ISSU)
ISSU on the Cisco ASR 1000 Series Routers Overview
ISSU Rollback Timer Overview on the Cisco ASR 1000 Series Router
Important Notes about ISSU Compatibility
ISSU with Dual IOS Processes on a Single RP Overview
ISSU Upgrade Procedures
Using ISSU to Perform a Consolidated Package Upgrade in a Dual Route Processor Configuration
Examples
Using ISSU to Upgrade Sub-Packages in a Dual Route Processor Configuration
Using ISSU to Upgrade Sub-Packages on a Cisco ASR 1006 Router (issu command set)
Using ISSU to Upgrade Sub-Packages on a Cisco ASR 1006 Router (request platform command set)
Using ISSU to Upgrade Sub-Packages on a Cisco ASR 1002 or Cisco ASR 1004 Router
Configuring RPR or SSO on a Cisco ASR 1002 or Cisco ASR 1004 Router
Using ISSU to Upgrade Sub-Packages on a Cisco ASR 1002 or Cisco ASR 1004 Router (issu command set)
Using ISSU to Upgrade Sub-Packages on a Cisco ASR 1002 or Cisco ASR 1004 Router (request platform command set)
ISSU Upgrade Procedures (Pre Cisco IOS XE Release 2.1.2)
Using ISSU to Perform a Consolidated Package Upgrade in a Dual Route Processor Configuration (Pre Cisco IOS XE 2.1.2)
Using ISSU to Perform a Consolidated Package Upgrade on a Single Route Processor Configuration (Pre Cisco IOS XE 2.1.2)
Using ISSU to Upgrade Sub-Packages (Pre Cisco IOS XE Release 2.1.2)
In Service Software Upgrades (ISSU)
This section covers the following topics:
•
ISSU on the Cisco ASR 1000 Series Routers Overview
•
ISSU Upgrade Procedures
•
ISSU Upgrade Procedures (Pre Cisco IOS XE Release 2.1.2)
ISSU on the Cisco ASR 1000 Series Routers Overview
The In Service Software Upgrade (ISSU) process allows software to be updated or otherwise modified while packet forwarding continues with minimal interruption.
For the Cisco ASR 1000 Series Routers, it is important to realize that ISSU-compatibility depends on the software sub-package 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 sub-packages can be upgraded using ISSU 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 sub-packages must be upgraded on a per-SPA or per-SIP basis. See Table 5-1 to view an ISSU table that addresses the contexts where limited interruption upgrades can be performed.
If you are updating multiple sub-packages, 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 Sub-Packages (Pre 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 sub-packages on an RP, and running sub-packages 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 sub-package upgrades.
Table 5-1 provides a list of the Cisco ASR 1000 Series Routers sub-packages and whether or not they can be upgraded without losing any network traffic in single and dual RP and ESP configurations using ISSU.
Table 5-1 Limited Interruption Upgrade Compatibility Table
Sub-Package
|
Non-redundant 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)
|
5 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.
|
ISSU Rollback Timer Overview on the Cisco ASR 1000 Series Router
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 sub-package 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.
Important Notes about ISSU Compatibility
•
It is important to note that every upgrade, including limited interruption supported upgrades, may introduce minor delays (often less than a second) where incoming or buffered traffic may be lost. Careful planning that takes into consideration your hardware configuration before the upgrade, in particular your SIP and SPA hardware installations, can help minimize the impact of lost traffic during the upgrade.
•
An RP reload is required to finalize an RPBase sub-package upgrade, as well as any consolidated package upgrade, so all network traffic is lost during the RP reload in single RP configurations during these upgrades. In dual RP configurations, the standby RP can be reset without impacting the active RP, so the standby RP can reset to finish the upgrade without impacting the forwarding of network traffic.
The RPBase sub-package upgrade is also performed last so the reload can be delayed in many sub-package upgrade scenarios for this reason.
•
Some sub-packages require an RP reload before allowing other sub-packages to be upgraded.
To avoid having to reload the RP multiple times to upload multiple packages that require RP reloads, be sure to specify certain sub-package combinations when defining the sub-package names in the issu or request platform software package command in such a way that the command captures the name of all of the sub-packages you would like to upgrade. The RP reload will then upgrade all of the sub-packages that require an upgrade collectively rather than individually.
See the "Using ISSU to Upgrade Sub-Packages (Pre Cisco IOS XE Release 2.1.2)" section for an example of a router upgrade that maximizes uptime by using wildcard characters.
•
The RPControl and RPAccess sub-packages can be upgraded without reloading any hardware, so these sub-packages can be upgraded without losing any network traffic. The supported installation procedure instructions specify that these sub-packages be upgraded simultaneously with the RPIOS sub-package.
•
The ESP must be reset to finalize an upgrade of the ESPBase sub-package. In a single ESP configuration, traffic will be lost as a result of this reset. In a dual ESP configuration, the standby ESP can be reset without impacting the active ESP, so the standby ESP can reset to finish the upgrade without impacting the forwarding of network traffic.
•
If a SIPSPA sub-package is used to upgrade a SPA, the SPA that is being upgraded must be reloaded to finalize the upgrade. All network traffic travelling through that SPA during the SPA reload will be lost. All other SIPs and SPAs on the router continue to be fully operational during the SPA reload.
•
Optional sub-packages, such as the "sipspawma" package for the Cisco WebEx Node for the ASR 1000 Series SPA, are also supported by the ISSU process. The optional sub-packages should be downloaded and located in the directory of the provisioning file along with the individual sub-packages on each RP. The optional sub-package version must match the software version of the ISSU target.
•
If a SIPBase sub-package is used to upgrade a SIP, that SIP must be reloaded to finalize the upgrade. All network traffic travelling through the SPAs within that SIP during the SIP reload will be lost. All other SIPs and SPAs on the router continue to be fully operational during the SIP reload.
•
Wildcard characters in the sub-package name string of the issu or request platform software package command sets can be used to minimize downtime of SIP and SPA sub-package upgrades when the wildcard is defined to capture the SIP and SPA sub-packages simultaneously. Using this wildcard allows the SIP and all the SPAs in the SIP to be updated collectively, thereby allowing for one single traffic disruption for both the SIP and SPA upgrades rather than individual traffic disruptions for the individual upgrades.
See the "Using ISSU to Upgrade Sub-Packages (Pre Cisco IOS XE Release 2.1.2)" section for an examples on using wildcards to avoid multiple SIP and SPA reloads.
•
The ISSU upgrade procedures on the Cisco ASR 1000 Series Routers is specific to the router platform. Many of the commands and keywords used to perform ISSU upgrades on the Cisco ASR 1000 Series Routers cannot be used to complete ISSU upgrades on other Cisco routers.
ISSU with Dual IOS Processes on a Single RP Overview
To complete an ISSU upgrade of an individual sub-package using dual IOS processes on a single RP, RPR or SSO must first be enabled.
ISSU with dual IOS processes is useful for upgrading the individual RP sub-packages that can be upgraded without a router reload. See Table 5-1 for a list of these sub-packages. Importantly, note that most sub-package upgrades in a single RP configuration require a hardware reload to complete (whether an RP reload for an RP sub-package, an ESP reload for the ESPBase sub-package, a SIP reload for a SIPBase sub-package, or a SPA reload for the SIPSPA sub-package), 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 "Configuring RPR or SSO on a Cisco ASR 1002 or Cisco ASR 1004 Router" section.
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 Sub-Packages in a Dual Route Processor Configuration
•
Using ISSU to Upgrade Sub-Packages on a Cisco ASR 1002 or Cisco ASR 1004 Router
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.
copy tftp: URL-to-target-location
2.
copy source-file-system:filename standby-destination-filesystem
3.
dir URL-to-target-location
dir URL-to-target-stby-location
4.
issu loadversion rp upgrade-rp-number standby-file-system:filename
5.
issu runversion
6.
telnet ip-address port
7.
issu acceptversion
8.
issu commitversion
9.
show version, show version active-RP running, show version active-RP provisioned
show platform
show running-configuration
10.
hw-module slot RP slot number reload
DETAILED STEPS
| |
Command or Action
|
Purpose
|
Step 1
|
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 2
|
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 3
|
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 4
|
issu loadversion rp upgrade-rp-number standby-file-system:filename
Example
Router# issu loadversion rp 1 file
stby-bootflash:asr1000rp1-adventerprisek9.02.01.01.122-33.XNA
1.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 5.
|
Step 5
|
issu runversion
Example
Router# issu runversion
|
Run the consolidated package that was loaded in Step 4.
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 6
|
telnet ip-address port
Example
[unix-server-1 ~]$ telnet 172.17.52.157 2003
Router>
|
Log on 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 7
|
issu acceptversion
Example
Router# issu acceptversion
|
(Optional) Stops the ISSU rollback timer.
This step is optional as long as Step 8 is completed before the rollback timer expires.
|
Step 8
|
issu commitversion
Example
Router# issu commitversion
|
Completes the ISSU upgrade.
|
Step 9
|
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 runnning-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 10
|
hw-module slot RP-slot reload
Example
Router# hw-module slot R0 reload
|
Reload the new software on the RP.
|
Examples
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 on 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 Sub-Packages 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 sub-packages.
This section covers the following topics
•
Using ISSU to Upgrade Sub-Packages on a Cisco ASR 1006 Router (issu command set)
•
Using ISSU to Upgrade Sub-Packages on a Cisco ASR 1006 Router (request platform command set)
Using ISSU to Upgrade Sub-Packages on a Cisco ASR 1006 Router (issu command set)
This section provides the instruction for performing an ISSU upgrade using sub-packages on a Cisco ASR 1006 router with a dual RP setup using the issu command set.
This procedure can only be performed if the current ASR 1006 has two active RPs and both RPs are running sub-packages.
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.
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
Note
In step 6, each individual sub-package that was extracted in step 4 is copied to the directory where the sub-packages that are currently running the standby RP are stored.
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.
issu loadversion rp standby-RP file URL-to-standby-file-system:asr1000rp*version*.pkg force
10.
hw-module slot standby-RP reload
11.
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.
12.
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
13.
issu loadversion rp active-RP file URL-to-active-file-system:asr1000rp1*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
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 sub-packages.
This directory must be created in most cases because the consolidated packages and sub-packages have to be separated from the sub-packages that booted the router at this step of the procedure.
|
Step 4
|
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 sub-packages 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.01.122-33.XNB1.bin
|
Extract the sub-packages out of the consolidated package file into the temporary directory.
Note Take extra care to extract the sub-packages to a temporary sub-directory 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) Display 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:
|
Copy the sub-packages out of the temporary directory into the directory on the router where the sub-packages 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:
|
Copy the sub-packages out of the temporary directory into the directory on the router where the sub-packages running the standby RP are currently stored.
|
Step 9
|
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 sub-packages on the standby RP, where the "rp*" wildcard is specified to capture all of the RP sub-packages for the desired upgrade release.
|
Step 10
|
hw-module slot standby-RP reload
Example
Router# hw-module slot R1 reload
|
Reload the standby RP.
|
Step 11
|
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.
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 sub-packages 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 Upgrade Procedures (Pre Cisco IOS XE Release 2.1.2)" section for pre-Cisco IOS XE Release 2.1.2 ISSU upgrade procedures.
|
Step 12
|
issu loadversion rp active-RP file URL-to-active-file-system:asr1000rp1-esp*version*.pkg slot standby-RP-slot
issu commitversion
issu loadversion rp active-RP file URL-to-active-file-system:asr1000rp1-esp*version*.pkg slot active-RP-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 sub-package 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
|
issu loadversion rp active-RP file URL-to-active-file-system:asr1000rp*version*.pkg force
Example
Router# issu loadversion rp 0 file bootflash:asr1000rp1-rp*02.02.01.122-33.XNB1*.pkg force
|
Upgrade all of the sub-packages on the active RP.
Note This step is required to ensure that all sub-packages on the router were upgraded as part of this procedure, and might upgrade some sub-packages 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) Confirm that the sub-packages are provisioned and installed.
|
Step 15
|
redundancy force-switchover
Example
Router# redundancy force-switchover
|
Force an RP switchover to complete the upgrade.
|
Step 16
|
request platform software package clean
Example
Router# request platform software package clean
|
(Optional) Removes all unused sub-packages files from the router.
|
Examples
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# 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-rp*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 Sub-Packages on a Cisco ASR 1006 Router (request platform command set)
This section provides the instruction for performing an ISSU upgrade using sub-packages on a Cisco ASR 1006 router with a dual RP setup using the request platform command set.
Prerequisites
This procedure can only be performed if the current ASR 1006 has two active RPs and both RPs are running sub-packages.
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.
copy tftp: URL-to-target-location
4.
request platform software package expand file URL-to-consolidated-package
5.
dir URL-to-consolidated-package
6.
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
7.
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
8.
request platform software package install rp standby-RP file URL-to-standby-file-system:asr1000rp*version*.pkg force
9.
hw-module slot standby-RP reload
10.
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.
11.
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
12.
request platform software package install rp active-RP file URL-to-active-file-system:asr1000rp*version*.pkg force
13.
show version active-RP provisioned
show version active-RP installed
14.
redundancy force-switchover
15.
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
|
Create a directory to store the consolidated package and sub-packages.
This directory must be created in most cases because the consolidated packages and sub-packages have to be separated from the sub-packages that booted the router at this step of the procedure.
|
Step 3
|
copy tftp: URL-to-target-location
Example
Router# copy tftp: usb0:221subs
|
Copy 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 sub-packages 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 4
|
request platform software package expand file URL-to-consolidated-package
Example
Router# request platform software package expand file usb0:221subs/asr1000rp1-adventerprisek9.02.02.01.122-33.XNB1.bin
|
Extract the sub-packages out of the consolidated package file into the temporary directory.
Note Take extra care to extract the sub-packages to a temporary sub-directory 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 5
|
dir target-URL
Example
Router# dir usb0:221subs
|
(Optional) Display the directory to confirm that the files were extracted.
|
Step 6
|
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 sub-packages out of the temporary directory into the directory on the router where the sub-packages running the active RP are currently stored.
|
Step 7
|
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 sub-packages out of the temporary directory into the directory on the router where the sub-packages running the standby RP are currently stored.
|
Step 8
|
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
|
Upgrade the RP sub-packages on the standby RP, where the "rp*" wildcard is specified to capture all of the RP sub-packages for the desired upgrade release.
|
Step 9
|
hw-module slot standby-RP reload
Example
Router# hw-module slot R1 reload
|
Reload the standby RP.
|
Step 10
|
request platform software package install rp active-RP file URL-to-active-file-system:asr1000rp1-{sipbase,sipspa}*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
|
Upgrade the SIP and SPA sub-packages 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 Upgrade Procedures (Pre Cisco IOS XE Release 2.1.2)" section for pre-Cisco IOS XE Release 2.1.2 ISSU upgrade procedures.
|
Step 11
|
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
|
Upgrade the ESP Base sub-package 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 12
|
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-rp*02.02.01.122-33.XNB1*.pkg force
|
Upgrade all of the sub-packages on the active RP.
Note This step is required to ensure that all sub-packages on the router were upgraded as part of this procedure, and might upgrade some sub-packages that would otherwise be missed in the process.
|
Step 13
|
show version active-RP provisioned
show version active-RP installed
Example
Router# show version r0 provisioned
Router# show version r0 installed
|
(Optional) Confirm the sub-packages are provisioned and installed.
|
Step 14
|
redundancy force-switchover
Example
Router# redundancy force-switchover
|
Force an RP switchover to complete the upgrade.
|
Step 15
|
request platform software package clean
|
(Optional) Remove all unused sub-package files from the router.
|
Examples
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# 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:asr1000rp*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
Using ISSU to Upgrade Sub-Packages on a Cisco ASR 1002 or Cisco ASR 1004 Router
This section explains how to upgrade sub-packages using ISSU on a Cisco ASR 1002 or 1004 Router.
It contains the following sections:
•
Configuring RPR or SSO on a Cisco ASR 1002 or Cisco ASR 1004 Router
•
Using ISSU to Upgrade Sub-Packages on a Cisco ASR 1002 or Cisco ASR 1004 Router (issu command set)
•
Using ISSU to Upgrade Sub-Packages on a Cisco ASR 1002 or Cisco ASR 1004 Router (request platform command set)
Configuring RPR or SSO on a Cisco ASR 1002 or Cisco ASR 1004 Router
The following instructions show how to configure RPR or SSO on a 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 1002 Router or Cisco ASR 1004 Router with 2 GB of DRAM memory on the RP, RPR or 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 non-redundant 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 rpr to enable RPR, mode sso to enable SSO, or mode none to disable dual software redundancy.
Router(config-red)# mode rpr
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
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 10
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 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 ISSU to Upgrade Sub-Packages on a Cisco ASR 1002 or Cisco ASR 1004 Router (issu command set)
This section provides instructions on using ISSU to upgrade a Cisco ASR 1002 or 1004 Router running sub-packages.
These instructions assume two IOS processes are active on the RP and that the router is already running using sub-packages. For information on checking and configuring two IOS processes on the same RP, see the "Configuring RPR or SSO on a Cisco ASR 1002 or Cisco ASR 1004 Router" 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.
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.
issu loadversion rp 0 file file-system:asr1000rp1-{rpaccess,rpios,rpcontrol}*version-string*.pkg bay standby-bay force
9.
issu commitversion
10.
redundancy force-switchover
11.
show platform
12.
issu loadversion rp 0 file file-system:asr1000rp1-{rpaccess,rpios,rpcontrol}*version-string*.pkg bay standby-bay force
13.
issu commitversion
14.
issu loadversion install 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.
15.
issu loadversion rp 0 file file-system:asr1000rp1-esp*version*.pkg force
16.
issu commitversion
17.
issu loadversion rp 0 file file-system:asr1000rp*version*.pkg
18.
show version installed
Step 19 and later does not have to be performed immediately, and should be done at a convenient time.
19.
reload
20.
request platform software package clean
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.
Although SSO is the better redundancy option, RPR can also be used to establish a second IOS process on the RP to complete this process.
|
Step 3
|
mkdir URL-to-directory-name
Example
Router# mkdir usb0:221subs
|
Create a directory to store the consolidated package and sub-packages.
This directory must be created in most cases because the consolidated packages and sub-packages have to be separated from the sub-packages that booted the router at this step of the procedure.
|
Step 4
|
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 sub-packages 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
(Optional) dir target-URL
Example
Router# request platform software package expand file usb0:221subs/asr1000rp1-adventerprisek9.02.02.01.122-33.XNB1.bin
Router# dir usb0:221subs
|
Extract the sub-packages out of the consolidated package file into the temporary directory.
Note Take extra care to extract the sub-packages to a temporary sub-directory 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) Display 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:
|
Copy the sub-packages out of the temporary directory into the directory on the router where the sub-packages running the active RP are currently stored.
|
Step 8
|
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 sub-packages in the standby bay.
|
Step 9
|
issu commitversion
Example
Router# issu commitversion
|
Once the SSO or RPR state is reached, commit the software version.
|
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
|
show platform
Example
Router# show platform
|
(Optional) Monitor system state to ensure both IOS processes are active.
|
Step 12
|
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 sub-packages in the standby bay (a different bay than in Step 8).
|
Step 13
|
issu commitversion
Example
Router# issu commitversion
|
Commit the software version.
|
Step 14
|
issu loadversion install 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 sub-packages 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 Upgrade Procedures (Pre Cisco IOS XE Release 2.1.2)" section for pre-Cisco IOS XE Release 2.1.2 ISSU upgrade procedures.
|
Step 15
|
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 sub-package.
|
Step 16
|
issu commitversion
Example
Router# issu commitversion
|
Commit the ESP Base software.
|
Step 17
|
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 sub-packages, including the RPBase sub-package, which is the last sub-package that needs to be upgraded.
Note This step is required to ensure that all sub-packages on the router were upgraded as part of this procedure, and might upgrade some sub-packages that would otherwise be missed in the process.
|
Step 18
|
show version installed
Example
Router# show version installed
|
(Optional) Verify that the sub-packages are properly installed.
|
Step 19
|
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 20
|
request platform software package clean
|
(Optional) Removes the unused sub-packages from the router.
|
Examples
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