Table Of Contents
Installing and Upgrading Software
Software Packaging on the Cisco ASR 903 Series Router
Cisco ASR 903 Series Router Software Overview
Understanding Cisco ASR 903 Series Router Software Packages
Provisioning Files
Upgrading Field Programmable Hardware Devices
File Systems on the Cisco ASR 903 Series Router
Bootflash Space Requirements
System Requirements
RP Memory Recommendations
ROMmon Version Requirements
Determining the Software Version
Cisco IOS XE 3S to Cisco IOS Version Number Mapping
Autogenerated Files and Directories
Understanding In-Service Software Upgrades
Restrictions for an ISSU Upgrade
Single-Command Upgrade Overview
Downloading an Image
Setting the Router to Boot in Sub-Package Mode
Completing a Single Command Software Upgrade
Preparing for Installation
Completing the Single Command Upgrade
Software Upgrade Examples
Single Command Software Upgrade
Installing and Upgrading Software
This chapter describes how to update software on the Cisco ASR 903 Series Router and includes the following sections:
•
Software Packaging on the Cisco ASR 903 Series Router
•
File Systems on the Cisco ASR 903 Series Router
•
System Requirements
•
Autogenerated Files and Directories
•
Understanding In-Service Software Upgrades
•
Downloading an Image
•
Setting the Router to Boot in Sub-Package Mode
•
Completing a Single Command Software Upgrade
•
Software Upgrade Examples
Software Packaging on the Cisco ASR 903 Series Router
This section covers the following topics:
•
Cisco ASR 903 Series Router Software Overview
•
Provisioning Files
•
Upgrading Field Programmable Hardware Devices
Cisco ASR 903 Series Router Software Overview
The Cisco IOS XE software supports two software installation types:
•
Consolidated image—A single software image containing a full collection of software packages. Consolidated mode provides a simplified installation and can be stored in bootflash, a TFTP server, or a network server. Consolidated mode is not supported on the Cisco ASR 903 Series Router.
•
Sub-package—One or more sub-images extracted from the consolidated image. Sub-package mode provides optimized memory usage and requires that you store files in the bootflash directory. The Cisco ASR 903 Series Router supports sub-package mode.
Caution 
The Cisco ASR 903 Series Router supports sub-package mode; consolidated mode is not supported.
Understanding Cisco ASR 903 Series Router Software Packages
Table 5-1 summarizes the sub-packages within a consolidated image.
Table 5-1 Individual Sub-Packages
Sub-Package
|
Purpose
|
RPBase
|
Route Switch Processor (RSP) operating system
|
RPControl
|
Control plane processes between IOS process and the rest of the platform.
|
RPAccess
|
Handles security features including Secure Socket Layer (SSL) and Secure Shell (SSH)
|
RPIOS
|
Cisco IOS kernel, which is where IOS features are stored and run.
Note Each consolidated image has a unique RPIOS package.
|
FP Pkg
|
Controls FP daemons.
|
IO Pkg
|
Controls input/output driver daemons.
|
LC Base
|
Controls basic kernel functions including runtime, initialization scripts, and chassis control daemons.
|
Provisioning Files
Provisioning files manage the boot process when the Cisco ASR 903 Series Router is configured to run using individual sub-packages. The provisioning file manages the bootup of each individual sub-package. Provisioning files are extracted automatically when individual sub-package files are extracted from a consolidated package. Provisioning files are not necessary for running the router using the complete consolidated package.
Upgrading Field Programmable Hardware Devices
Cisco IOS XE supports upgradeable firmware for field programmable hardware devices such as interface modules (IMs). Generally an upgrade is only necessary in cases where a system message indicates that an upgrade is required or a Cisco technical support representative suggests an upgrade.
The procedures in this chapter describe how to upgrade the firmware on Cisco ASR 903 Series Router.
File Systems on the Cisco ASR 903 Series Router
Table 5-5 provides a list of file systems that can be seen on the Cisco ASR 903 Series Router.
Table 5-2 File Systems
File System
|
Description
|
bootflash:
|
The boot flash memory file system on the active RSP.
|
cns:
|
The Cisco Networking Services file directory.
|
nvram:
|
Router NVRAM. You can copy the startup configuration to NVRAM or from NVRAM.
|
stby-bootflash:
|
The boot flash memory file system on the standby RSP.
|
stby-harddisk:
|
The hard disk file system on the standby RSP.
|
stby-usb[0-1]:
|
The Universal Serial Bus (USB) flash drive file systems on the standby RSP.
|
system:
|
The system memory file system, which includes the running configuration.
|
tar:
|
The archive file system.
|
tmpsys:
|
The temporary system files file system.
|
usb[0-1]:
|
The Universal Serial Bus (USB) flash drive file systems on the active RSP.
|
If you see a file system not listed in Table 5-5, enter the ? help option or see the copy command reference for additional information on that file system.
Bootflash Space Requirements
The in-service software upgrade process requires a minimum of 600 MB available space in bootflash memory.
System Requirements
The following sections describe the system requirements for the Cisco ASR 903 Series Router software:
•
RP Memory Recommendations
•
ROMmon Version Requirements
•
Determining the Software Version
•
Cisco IOS XE 3S to Cisco IOS Version Number Mapping
RP Memory Recommendations
The Cisco IOS XE 3S images and packages available vary based on the route processor installed in the system.
Table 3 describes the consolidated package images, individual software subpackage contents, and memory recommendations for each RSP.
Table 3 Memory Recommendations for the Cisco ASR 903 Series Router Consolidated Package Image
Platform
|
Image Name
|
Software Image
|
Individual Subpackage Contents
|
DRAM Memory
|
Cisco ASR 903 Router
|
Cisco ASR 903 Series RSP1 UNIVERSAL W/O CRYPTO
|
asr903rsp1-universal.version.bin
|
asr903rsp1-rpbase.version.pkg
|
2 GB (RSP1)
4 GB (RSP1+)
|
asr903rsp1-rpcontrol.version.pkg
|
asr903rsp1-rpaccess.version.pkg
|
asr903rsp1-rpios-universal.version. pkg
|
asr903rsp1-espbase.version.pkg
|
asr903rsp1-sipbase.version.pkg
|
asr903rsp1-sipspa.version.pkg
|
asr903rsp1-packages-universal. version.conf
|
packages.conf
|
Cisco ASR 903 Router
|
Cisco ASR 903 Series RSP1 UNIVERSAL
|
asr903rsp1-universalk9.version.bin
|
asr903-hw-programmables.version. pkg
|
2 GB (RSP1)
4 GB (RSP1+)
|
asr903rsp1-espbase.version.pkg
|
asr903rsp1-packages-universalk9. version.conf
|
asr903rsp1-rpaccess.version.pkg
|
asr903rsp1-rpbase.version.pkg
|
asr903rsp1-rpcontrol.version.pkg
|
asr903rsp1-rpios-universalk9.version.pkg
|
asr903rsp1-sipbase.version.pkg
|
asr903rsp1-sipspa.version.pkg
|
packages.conf
|
Cisco ASR 903 Router
|
Cisco ASR 903 Series RSP1 UNIVERSALNPE
|
asr903rsp1-universalk9_npe. version.bin
|
asr903-hw-programmables.version. pkg
|
2 GB (RSP1)
4 GB (RSP1+)
|
asr903rsp1-espbase.version.pkg
|
asr903rsp1-packages-universalk9. version.conf
|
asr903rsp1-rpaccess.version.pkg
|
asr903rsp1-rpbase.version.pkg
|
asr903rsp1-rpcontrol.version.pkg
|
asr903rsp1-rpios-universalk9_npe. version.pkg
|
asr903rsp1-sipbase.version.pkg
|
asr903rsp1-sipspa.version.pkg
|
packages.conf
|
ROMmon Version Requirements
ROMmon Release 15.3(1r)S1 is the recommended release for all ROMmon upgradeable components. For more information about ROMmon images, see Release Notes for the Cisco ASR 903 Router.
Determining the Software Version
You can use the show version installed command to list the installed sub-packages on the router.
Cisco IOS XE 3S to Cisco IOS Version Number Mapping
Each version of Cisco IOS XE 3S has an associated Cisco IOS version. Table 4 lists these mappings for Release 3.50S and forward.
Table 4 Cisco IOS XE 3S to Cisco IOS Version Number Mapping
Cisco IOS XE 3S Version
|
Cisco IOS Version
|
3.5.0S
|
15.2(1)S
|
3.5.1S
|
15.2(1)S1
|
3.6.0S
|
15.2(2)S
|
3.6.1S
|
15.2(2)S1
|
3.7.0S
|
15.2(4)S
|
The Cisco ASR 903 Series Router does not support IOS XE versions prior to 3.50S.
Autogenerated Files and Directories
Table 5-5 provides a list and descriptions of autogenerated files on the Cisco ASR 903 Series Router.
Caution 
Do not alter any autogenerated file in the bootflash: directory should not be deleted, renamed, moved, or altered in any way unless directed by customer support; altering these files can have unpredictable consequences for system performance.
Table 5-5 Autogenerated Files
File or Directory
|
Description
|
crashinfo files
|
A crashinfo file may appear in the bootflash: file system.
Crashinfo files are useful for tuning and troubleshooting, but are not related to router operations: you can erase them without impacting the router's performance.
|
core files
|
The bootflash/core directory is the storage area for .core files.
Caution  Do not erase or move the core directory.
|
lost+found directory
|
This directory is created on bootup if a system check is performed. Its appearance is completely normal and does not indicate any issues with the router.
|
tracelogs files
|
The storage area for trace files is bootflash/tracelogs.
Trace files are useful for troubleshooting; you can access trace files using diagnostic mode to gather information related to the IOS failure.
Caution  Do not erase or move the tracelog directory.
|
Understanding In-Service Software Upgrades
The in-service software upgrade (ISSU) process allows you to update the router software with minimal service interruption. The following sections describe the ISSU process on the Cisco ASR 903 Series Router:
•
Restrictions for an ISSU Upgrade
•
Single-Command Upgrade Overview
Restrictions for an ISSU Upgrade
The following restrictions apply when completing an in-service software upgrade on the Cisco ASR 903 Series Router.
•
ISSU is not supported for single RSP configurations.
•
Cisco IOS XE software compatibility is supported only between identical image types. Cross-image-type upgrades or installations (such as from an advipservicesk9 image to an advipservicesk9image) are not supported in the ISSU process.
•
Running two different image types simultaneously is not supported.
•
In-service upgrades from one package mode to another are not supported.
•
The procedures in this document represent supported and tested installation sequences; following alternative procedures for upgrading the Cisco ASR 903 Series Router software can cause unexpected behavior.
Single-Command Upgrade Overview
The Cisco ASR 903 Series Router supports a single-command upgrade for ISSU. A single command upgrade allows you to install a complete set of sub-packages using a single command. This command will install the complete set of packages on the standby RSP, and then perform a rolling reload of the interface modules on the active RSP. After the interface modules are reloaded, an HA switchover will be performed and the complete set of sub-packages will be installed on the new (i.e. previously active) RSP. For information about completing a single-command upgrade, see Completing a Single Command Software Upgrade.
Downloading an Image
Follow these steps to download a Cisco ASR 903 Series Router software image.
Caution 
Ensure that you have chosen an upgrade image that is supported by your current software version
Step 1
|
Create directory filename [issu]?
Created dir bootflash:/issu
|
Creates an ISSU directory in bootflash.
|
Step 2
|
|
Download the consolidated image file from Cisco.com.
|
Step 3
|
Router# copy filename directory
Example:
Router# copy
asr903rsp1-adventerprisek9.upgrade.bin
bootflash:/issu
|
Copy the consolidated image file to the ISSU bootflash directory.
Note Do not copy the packages.conf file to a new directory after expanding the package. It is required that the packages.conf file and sub package files exist in the same directory.
|
Setting the Router to Boot in Sub-Package Mode
Follow these steps to configure the router to boot in sub-package mode.
Note
For instructions on how to download an image file, see Downloading an Image.
| |
Command
|
Purpose
|
Step 1
|
Router# configure terminal
|
Enters configuration mode.
|
Step 2
|
Router(config)# config-register 0x2
|
Sets the configuration register so that the router boots using a specified image in NVRAM.
Note If the configuration register value is already set to auto-boot the router, you can skip this step.
|
Step 3
|
exit
Example:
Router(config)# exit
|
Exits configuration mode and returns to the EXEC command interpreter prompt.
|
Step 4
|
request platform software package
expand file source-URL [to
destination-URL] [force] [verbose]
[wipe]
Router# request platform software
package expand file
bootflash:issu/asr903rsp1-adventerpri
sek9.base.bin
|
Expands the consolidated image file on the active RSP.
|
Step 5
|
request platform software package
expand file source-URL [to
destination-URL] [force] [verbose]
[wipe]
Router# request platform software
package expand file
stby-bootflash:issu/asr903rsp1-advent
erprisek9.base.bin
|
Expands the consolidated image file on the standby RSP.
Note This step applies only if your router has a redundant RSP.
|
Step 6
|
boot system flash [flash-fs:]
[partition-number:] [filename]
Router(config)# boot system
bootflash:issu/packages.conf
|
Sets the router to boot using the packages.conf file.
|
Step 7
|
exit
Example:
Router(config)# exit
|
Exits configuration mode and returns to the EXEC command interpreter prompt.
|
Step 8
|
Router# copy running-config
startup-config
|
Saves the configuration.
|
Step 9
|
|
Reloads the router.
|
Completing a Single Command Software Upgrade
A single command upgrade updates the active and standby RSPs with a single IOS command. Follow these steps to complete the one-shot upgrade.
Preparing for Installation
Step 1
|
|
Download the new consolidated image file from Cisco.com. For more information about downloading Cisco software image, see Chapter 1 "Using Cisco IOS XE Software."
|
Step 2
|
|
Open a console session to the active RSP. For instructions on how to open a console session, see Console Port, Telnet, and SSH Handling.
|
Step 3
|
Router# copy filename directory
Example:
Router# copy
asr903rsp1-adventerprisek9.upgrade.bi
n bootflash:/issu
|
Copy the new consolidated image file to the active ISSU bootflash directory such that the new image file is in the same location as the existing image file.
Note Do not copy the packages.conf file to a new directory after expanding the package. It is required that the packages.conf file and sub package files exist in the same directory.
Note It is not necessary to copy the new consolidated image file to the standby RSP; the one-shot upgrade process completes this step.
|
Step 4
|
Router# configure terminal
|
Enters configuration mode.
|
Step 5
|
Router(config)# redundancy
|
Enters redundancy configuration mode.
|
Step 6
|
Router(config-red)# mode sso
|
Sets the router in SSO redundancy mode.
|
Step 7
|
end
Example:
|
Exits configuration mode and returns to the EXEC command prompt.
|
Step 8
|
*Jan 12 17:52:26.516:
%RF-5-RF_TERMINAL_STATE: Terminal
state reached for (SSO)
|
Confirms that the router has reached SSO state; wait for this output before proceeding.
|
Step 9
|
Router# copy running-config
startup-config
|
Saves the configuration.
|
Completing the Single Command Upgrade
| |
Command
|
Purpose
|
Step 1
|
request platform software package install node file file-URL [interface-module-delay delay]
Example:
Router# request platform software package install node file bootflash:/issu/asr903rsp1-adventerprisek9.upgrade.bin interface-module-delay 160
|
Initiates the one-shot installation procedure using the consolidated image file.
Note You can adjust the delay between the OIR of each IM using the interface-module-delay keyword.
Caution  We recommend you set the interface-module-delay value to 150 seconds or greater in order to ensure sufficient time for IM software upgrades.
Note Keywords other than interface-module-delay are not supported.
|
Step 2
|
|
The router displays a series of STAGE/SUCCESS messages.
For sample output of a single command upgrade, see Software Upgrade Examples.
|
Step 3
|
Router#
|
Wait for original active RSP to reboot and return to the console prompt.
|
Step 4
|
|
Switch to the new active console
|
Step 5
|
*Jan 12 17:52:26.516:
%RF-5-RF_TERMINAL_STATE: Terminal
state reached for (SSO)
|
Wait for new active console to return to SSO state
|
Software Upgrade Examples
The following sections provide samples of software upgrades on the Cisco ASR 903 Series Router.
Single Command Software Upgrade
Router# request platform software package install node file bootflash:XE371_k9_0810.bin
interface-module-delay 150
NOTE: Currently node has booted from a provisioning file
NOTE: Going to start a dual rp sub-packages node ISSU install
--- Starting initial file path checking ---
Copying bootflash:XE371_k9_0810.bin to stby-bootflash:XE371_k9_0810.bin
Finished initial file path checking
--- Starting config-register verfication ---
Finished config-register verfication
--- Starting image file expansion ---
Expanding image file: bootflash:XE371_k9_0810.bin
Image file expanded and copied
Expanding image file: stby-bootflash:XE371_k9_0810.bin
Image file expanded and copied
Finished image file expansion
STAGE 1: Installing software on standby RP
==========================================
--- Starting local lock acquisition on R0 ---
Finished local lock acquisition on R0
--- Starting installation state synchronization ---
Finished installation state synchronization
--- Starting local lock acquisition on R1 ---
Finished local lock acquisition on R1
--- Starting file path checking ---
Finished file path checking
--- Starting image file verification ---
Checking image file names
Locating image files and validating name syntax
Found asr903rsp1-espbase.BLD_V152_4_S_XE37_THROTTLE_LATEST_20120810_070021.pkg
Found asr903rsp1-rpaccess.BLD_V152_4_S_XE37_THROTTLE_LATEST_20120810_070021.pkg
Found asr903rsp1-rpbase.BLD_V152_4_S_XE37_THROTTLE_LATEST_20120810_070021.pkg
Found asr903rsp1-rpcontrol.BLD_V152_4_S_XE37_THROTTLE_LATEST_20120810_070021.pkg
Found
asr903rsp1-rpios-universalk9_npe.BLD_V152_4_S_XE37_THROTTLE_LATEST_20120810_070021.pkg
Found asr903rsp1-sipbase.BLD_V152_4_S_XE37_THROTTLE_LATEST_20120810_070021.pkg
Found asr903rsp1-sipspa.BLD_V152_4_S_XE37_THROTTLE_LATEST_20120810_070021.pkg
Verifying image file locations
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
Checking if resulting candidate package set would be complete
Finished candidate package set construction
--- Starting compatibility testing ---
Determining whether candidate package set is compatible
Determining whether installation is valid
Determining whether installation is valid ... skipped
Verifying image type compatibility
Checking IPC compatibility for candidate software
Checking candidate package set infrastructure compatibility
Checking infrastructure compatibility with running software
Checking infrastructure compatibility with running software ... skipped
Checking package specific compatibility
Finished compatibility testing
--- Starting list of software package changes ---
Removed asr903rsp1-espbase.2012-08-12_15.26_amprajap.pkg
Removed asr903rsp1-rpaccess.2012-08-12_15.26_amprajap.pkg
Removed asr903rsp1-rpbase.2012-08-12_15.26_amprajap.pkg
Removed asr903rsp1-rpcontrol.2012-08-12_15.26_amprajap.pkg
Removed asr903rsp1-rpios-universalk9_npe.2012-08-12_15.26_amprajap.pkg
Removed asr903rsp1-sipbase.2012-08-12_15.26_amprajap.pkg
Removed asr903rsp1-sipspa.2012-08-12_15.26_amprajap.pkg
Added asr903rsp1-espbase.BLD_V152_4_S_XE37_THROTTLE_LATEST_20120810_070021.pkg
Added asr903rsp1-rpaccess.BLD_V152_4_S_XE37_THROTTLE_LATEST_20120810_070021.pkg
Added asr903rsp1-rpbase.BLD_V152_4_S_XE37_THROTTLE_LATEST_20120810_070021.pkg
Added asr903rsp1-rpcontrol.BLD_V152_4_S_XE37_THROTTLE_LATEST_20120810_070021.pkg
Added
asr903rsp1-rpios-universalk9_npe.BLD_V152_4_S_XE37_THROTTLE_LATEST_20120810_070021.pkg
Added asr903rsp1-sipbase.BLD_V152_4_S_XE37_THROTTLE_LATEST_20120810_070021.pkg
Added asr903rsp1-sipspa.BLD_V152_4_S_XE37_THROTTLE_LATEST_20120810_070021.pkg
Finished list of software package changes
--- Starting commit of software changes ---
Updating provisioning rollback files
Creating pending provisioning file
Committing provisioning file
Finished commit of software changes
SUCCESS: Software provisioned. New software will load on reboot.
STAGE 2: Restarting standby RP
==============================
--- Starting standby reload ---
--- Starting wait for Standby RP to reach terminal redundancy state ---
Finished wait for Standby RP to reach terminal redundancy state
STAGE 3: Installing sipspa package on local RP
==============================================
--- Starting local lock acquisition on R0 ---
Finished local lock acquisition on R0
--- Starting installation state synchronization ---
Finished installation state synchronization
--- Starting file path checking ---
Finished file path checking
--- Starting image file verification ---
Checking image file names
Locating image files and validating name syntax
Found asr903rsp1-sipspa.BLD_V152_4_S_XE37_THROTTLE_LATEST_20120810_070021.pkg
Verifying image file locations
Inspecting image file types
Processing image file constraints
Creating candidate provisioning file
Finished image file verification
--- Starting candidate package set construction ---
Verifying existing software set
Processing candidate provisioning file
Constructing working set for candidate package set
Constructing working set for running package set
Constructing merge of running and candidate packages
Checking if resulting candidate package set would be complete
Finished candidate package set construction
--- Starting compatibility testing ---
Determining whether candidate package set is compatible
WARNING: Candidate software combination not found in compatibility database
Determining whether installation is valid
WARNING: Candidate software combination not found in compatibility database
WARNING: Candidate software combination not found in compatibility database
Software sets are identified as compatible
Verifying image type compatibility
Checking IPC compatibility with running software
Checking candidate package set infrastructure compatibility
Checking infrastructure compatibility with running software
Checking package specific compatibility
Finished compatibility testing
--- Starting impact testing ---
Checking operational impact of change
--- Starting list of software package changes ---
Removed asr903rsp1-sipspa.2012-08-12_15.26_amprajap.pkg
Added asr903rsp1-sipspa.BLD_V152_4_S_XE37_THROTTLE_LATEST_20120810_070021.pkg
Finished list of software package changes
--- Starting commit of software changes ---
Updating provisioning rollback files
Creating pending provisioning file
Committing provisioning file
Finished commit of software changes
--- Starting analysis of software changes ---
Finished analysis of software changes
--- Starting update running software ---
Blocking peer synchronization of operating information
Creating the command set placeholder directory
Finding latest command set
Finding latest command shortlist lookup file
Finding latest command shortlist file
Assembling CLI output libraries
Assembling CLI input libraries
Assembling Dynamic configuration files
Applying interim IPC and database definitions
Replacing running software
Skipping IM reload for Ethernet IM
Skipping IM reload for Ethernet IM
Skipping IM reload for Ethernet IM
Skipping IM reload for Ethernet IM
Skipping IM reload for Ethernet IM
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.
STAGE 4: Installing software on active RP
=========================================
--- Starting local lock acquisition on R0 ---
Finished local lock acquisition on R0
--- Starting installation state synchronization ---
Finished installation state synchronization
--- Starting file path checking ---
Finished file path checking
--- Starting image file verification ---
Checking image file names
Locating image files and validating name syntax
Found asr903rsp1-espbase.BLD_V152_4_S_XE37_THROTTLE_LATEST_20120810_070021.pkg
Found asr903rsp1-rpaccess.BLD_V152_4_S_XE37_THROTTLE_LATEST_20120810_070021.pkg
Found asr903rsp1-rpbase.BLD_V152_4_S_XE37_THROTTLE_LATEST_20120810_070021.pkg
Found asr903rsp1-rpcontrol.BLD_V152_4_S_XE37_THROTTLE_LATEST_20120810_070021.pkg
Found
asr903rsp1-rpios-universalk9_npe.BLD_V152_4_S_XE37_THROTTLE_LATEST_20120810_070021.pkg
Found asr903rsp1-sipbase.BLD_V152_4_S_XE37_THROTTLE_LATEST_20120810_070021.pkg
Found asr903rsp1-sipspa.BLD_V152_4_S_XE37_THROTTLE_LATEST_20120810_070021.pkg
Verifying image file locations
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
Checking if resulting candidate package set would be complete
Finished candidate package set construction
--- Starting compatibility testing ---
Determining whether candidate package set is compatible
Determining whether installation is valid
Determining whether installation is valid ... skipped
Verifying image type compatibility
Checking IPC compatibility for candidate software
Checking candidate package set infrastructure compatibility
Checking infrastructure compatibility with running software
Checking infrastructure compatibility with running software ... skipped
Checking package specific compatibility
Finished compatibility testing
--- Starting list of software package changes ---
Removed asr903rsp1-espbase.2012-08-12_15.26_amprajap.pkg
Removed asr903rsp1-rpaccess.2012-08-12_15.26_amprajap.pkg
Removed asr903rsp1-rpbase.2012-08-12_15.26_amprajap.pkg
Removed asr903rsp1-rpcontrol.2012-08-12_15.26_amprajap.pkg
Removed asr903rsp1-rpios-universalk9_npe.2012-08-12_15.26_amprajap.pkg
Removed asr903rsp1-sipbase.2012-08-12_15.26_amprajap.pkg
Added asr903rsp1-espbase.BLD_V152_4_S_XE37_THROTTLE_LATEST_20120810_070021.pkg
Added asr903rsp1-rpaccess.BLD_V152_4_S_XE37_THROTTLE_LATEST_20120810_070021.pkg
Added asr903rsp1-rpbase.BLD_V152_4_S_XE37_THROTTLE_LATEST_20120810_070021.pkg
Added asr903rsp1-rpcontrol.BLD_V152_4_S_XE37_THROTTLE_LATEST_20120810_070021.pkg
Added
asr903rsp1-rpios-universalk9_npe.BLD_V152_4_S_XE37_THROTTLE_LATEST_20120810_070021.pkg
Added asr903rsp1-sipbase.BLD_V152_4_S_XE37_THROTTLE_LATEST_20120810_070021.pkg
Finished list of software package changes
--- Starting commit of software changes ---
Updating provisioning rollback files
Creating pending provisioning file
Committing provisioning file
Finished commit of software changes
SUCCESS: Software provisioned. New software will load on reboot.
STAGE 5: Restarting active RP (switchover to stdby)
===================================================
--- Starting active reload ---
SUCCESS: node ISSU finished successfully.
RUDY-1#Aug 24 07:54:41.715 R0/0: %PMAN-5-EXITACTION: Process manager is exiting: reload
fru action requested
System Bootstrap, Version 15.3(1r)S1, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 2012 by cisco Systems, Inc.
Compiled Tue 26-Jun-12 12:42 by ccai
Current image running: Boot ROM0UEA platform with 3670016 Kbytes of main memory
Image size 7519 inode num 38, bks cnt 2 blk size 8*512
Located asr903rsp1-rpbase.BLD_V152_4_S_XE37_THROTTLE_LATEST_20120810_070021.pkg
Image size 34216240 inode num 90631, bks cnt 8354 blk size 8*512
##########################################################################################
##########################################################################################
##########################################################################################
#################################################################
Boot image size = 34216240 (0x20a1930) bytes
Package header rev 0 structure detected
Calculating SHA-1 hash...done
validate_package: SHA-1 hash:
calculated e7674970:dbc1eb86:325219c7:b3da0e0f:077e5e4d
expected e7674970:dbc1eb86:325219c7:b3da0e0f:077e5e4d
%IOSXEBOOT-4-BOOT_ACTIVITY_LONG_TIME: (rp/0): load_crash_kernel took: 2 seconds, expected
max time 2 seconds
%IOSXEBOOT-4-DEBUG_CONF: (rp/0): File /bootflash/debug.conf is absent, ignoring
%IOSXEBOOT-4-BOOT_ACTIVITY_LONG_TIME: (rp/0): Chasfs initialisation took: 26 seconds,
expected max time 10 seconds
%IOSXEBOOT-4-BOOT_ACTIVITY_LONG_TIME: (rp/0): upgrade hw-programmable took: 2 seconds,
expected max time 2 seconds
Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph
(c) of the Commercial Computer Software - Restricted
Rights clause at FAR sec. 52.227-19 and subparagraph
(c) (1) (ii) of the Rights in Technical Data and Computer
Software clause at DFARS sec. 252.227-7013.
San Jose, California 95134-1706
Cisco IOS Software, IOS-XE Software (PPC_LINUX_IOSD-UNIVERSALK9_NPE-M), Experimental
Version 15.2(20120810:081250)
[v152_4_s_xe37_throttle-BLD-BLD_V152_4_S_XE37_THROTTLE_LATEST_20120810_070021-ios 131]
Copyright (c) 1986-2012 by Cisco Systems, Inc.
Compiled Fri 10-Aug-12 03:50 by mcpre
Cisco IOS-XE software, Copyright (c) 2005-2012 by cisco Systems, Inc.
All rights reserved. Certain components of Cisco IOS-XE software are
licensed under the GNU General Public License ("GPL") Version 2.0. The
software code licensed under GPL Version 2.0 is free software that comes
with ABSOLUTELY NO WARRANTY. You can redistribute and/or modify such
GPL code under the terms of GPL Version 2.0. For more details, see the
documentation or "License Notice" file accompanying the IOS-XE software,
or the applicable URL provided on the flyer accompanying the IOS-XE
This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
If you require further assistance please contact us by sending email to
cisco ASR-903 (RSP1) processor with 540359K/6147K bytes of memory.
Processor board ID FOX1518P0GP
32768K bytes of non-volatile configuration memory.
3670016K bytes of physical memory.
1328927K bytes of SD flash at bootflash:.
Press RETURN to get started!