Software Configuration Guide for the Cisco ISR 4400 Series
Installing the Software
Downloads: This chapterpdf (PDF - 384.0KB) The complete bookPDF (PDF - 3.81MB) | The complete bookePub (ePub - 413.0KB) | Feedback

Table of Contents

Installing the Software

Information About Installing the Software

Overview

ROMMON Images

Provisioning Files

File Systems

Autogenerated File Directories and Files

Flash Storage

Configuring the Configuration Register for Autoboot

Licensing

Cisco Software Licensing

Consolidated Packages

Technology Packages

Feature Licenses

Example: Unlicensed Feature

LED Indicators

Related Documentation

How to Install and Upgrade Software

Managing and Configuring a Router to Run Using a Consolidated Package

Managing and Configuring a Consolidated Package Using copy and boot Commands

Configuring a Router to Boot the Consolidated Package via TFTP Using the Boot Command

Managing and Configuring a Router to Run Using Individual Packages

Installing Subpackages from a Consolidated Package

Installing a Firmware Subpackage

Installing the Software

This chapter is divided into the following two main sections:

Information About Installing the Software

Overview

Installing software on the router involves installing a consolidated package (bootable image). This consists of a bundle of subpackages (modular software units). Each subpackage controls a different set of functions.

These are the two main methods to install the software:

This method allows for individual upgrade of subpackages and also generally has reduced boot times compared to the second method below. Use this method if, for example, you would like to be able to individually upgrade module software.

This a simple method that is similar to typical Cisco router image installation and management that is supported across Cisco routers.

It is better to upgrade software in a planned period of maintenance when an interruption in service is acceptable. The router needs to be rebooted for a software upgrade to take effect.

ROMMON Images

A ROMMON image is a software package used by ROM Monitor (ROMMON) software on the router. The software package is separate from the consolidated package normally used to boot the router. For more information on ROMMON, see the “ROM Monitor Overview and Basic Procedures” section in the Hardware Installation Guide for the Cisco 4400 Series Integrated Services Routers .

An independent ROMMON image (software package) may occasionally be released and the router can be upgraded with the new ROMMON software. Refer to the documentation that accompanies the ROMMON image. A new version of the ROMMON image is not necessarily released at the same time as a consolidated package for the router.

Provisioning Files

This information in this section provides background information about files and processes used in
“Managing and Configuring a Router to Run Using Individual Packages” section.

The consolidated package on the router consists of a collection of subpackages and a provisioning file “packages.conf”. To run the software, the usual method used is to boot the consolidated package, which is copied into memory, expanded, mounted, and run within memory. The provisioning filename can be renamed, and subpackage filenames cannot be renamed. The provisioning file and subpackage files must be kept in the same directory. The provisioning file does not work properly if any individual subpackage file is contained within a different directory.


Note An exception to this is that if a new or upgraded module firmware package is subsequently installed, it need not be in the same directory as the provisioning file.


Configuring the router to boot using the provisioning file, packages.conf, is useful because no changes have to be made to the boot statement after the Cisco IOS XE software is upgraded.

Alternatively, for an example of booting using subpackages, see the example “Configuring the Router to Boot Using Subpackages” section .

File Systems

 

Table 5-1 Router File Systems

File System
Description

bootflash:

Boot flash memory file system.

flash:

Alias to the boot flash memory file system above.

harddisk:

Hard disk file system (for router models that have a hard disk).

cns:

Cisco Networking Services file directory.

nvram:

Router NVRAM. You can copy the startup configuration to NVRAM or from NVRAM.

obfl:

File system for Onboard Failure Logging(OBFL) files.

system:

System memory file system, which includes the running configuration.

tar:

Archive file system.

tmpsys:

Temporary system files file system.

usb0:
usb1:

The Universal Serial Bus (USB) flash drive file systems.

usbtoken0:
usbtoken1:

Usbtoken file system.

Note A usbtoken file system may not always be visible, as the file system is only visible when a usbtoken is inserted.

If you find a file system that is not listed in Table 5-1 , further information may be obtained by using
the ? help option, or look at the copy command in command reference guides.

Autogenerated File Directories and Files

This section discusses the autogenerated files and directories that might be created, and how the files in these directories can be managed.

 

Table 5-2 Autogenerated Files

File or Directory
Description

crashinfo files

Crashinfo files may appear in the bootflash: file system.

These files provide descriptive information of a crash and may be useful for tuning or troubleshooting purposes. However, the files are not part of router operations and can be erased without impacting the functioning of the router.

core directory

The storage area for “.core” files.

If this directory is erased, it will automatically regenerate itself at bootup. The “.core” files in this directory can be erased without impacting any router functionality, but the directory itself should not be erased.

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 directory

The storage area for trace files.

Trace files are useful for troubleshooting; if the IOS process fails, for instance, users or troubleshooting personnel can access trace files using diagnostic mode to gather information related to the IOS failure.

Trace files, however, are not part of router operations and can be erased without impacting the router’s performance.

Important Notes About Autogenerated Directories

The important information about autogenerated directories include:

  • Any autogenerated file on the bootflash: directory should not be deleted, renamed, moved, or altered in any way unless directed by customer support. Altering autogenerating files on the bootflash: can have unpredictable consequences for system performance.
  • Crashinfo, core, and trace files can be deleted.

Flash Storage

Subpackages are installed to local media storage, such as flash. For flash storage, use command
dir bootflash: to list the file names.


Note Flash storage is required for the router’s successful operation.


Configuring the Configuration Register for Autoboot

The configuration register can be used to change router behavior. This includes controlling how the router boots. Set the configuration register to 0x0 to boot into ROM, use one of the following two commands.

    • In Cisco IOS configuration mode, use the command:

config-reg 0x0

    • From the ROMMON prompt, use the command:

confreg 0x0

For further information on the configuration register, see Use of the Configuration Register on All Cisco Routers.

Also refer to the “Configuring a Router to Boot the Consolidated Package via TFTP Using the Boot Command” section.


Note Setting the configuration register to 0x2102 will set the router to autoboot the Cisco IOS XE software.



Note The console baud rate is set to 9600 after changing the confreg to 0x2102 or 0x0. If you cannot establish a console session after setting confreg, or garbage output appears, try changing the setting on your terminal emulation software to 9600.


Cisco Software Licensing

Cisco software licensing consists of processes and components to activate Cisco IOS software feature sets by obtaining and validating Cisco software licenses.

You can enable licensed features and store license files in the bootflash of your router. Licenses may be for consolidated packages, technology packages, or individual features.

An evaluation license is automatically converted to a Right to Use model after 60 days and this license is valid permanently. The conversion to a permanent license only applies to evaluation licenses. For other features supported on your router, you must purchase a permanent license.

See the “Configuring the Cisco IOS Software Activation Feature” of the
Software Activation Configuration Guide, Cisco IOS XE Release 3S .

Consolidated Packages

One of the following two consolidated packages (images) is pre-installed on the router:

  • universalk9—contains base package ipbasek9 and technology packages: securityk9, uck9, and appxk9
  • universalk9_npe—contains base package ipbasek9 and technology packages securityk9-npe, uck9, and appxk9. “npe” stands for No Payload Encryption. This image has limited crypto functionality.

The terms super package and image also refer to a consolidated package.

Obtain software images for the router from:
http://software.cisco.com/download/navigator.html .

An image-based license is used to help bring up all the subsystems that corresponding to the license. This license is enforced only at boot time.

Apart from the universalk9 and universalk9_npe images above, a Boot ROMMON image is available. See the “ROMMON Images” section.

For further information about identifying digitally signed Cisco software and how to show the digital signature information of an image file, see the “Digitally Signed Cisco Software” section in the
Loading and Managing System Images Configuration Guide .

The following examples show how to obtain software authenticity information and internal details of a package:

Many features within the consolidated package are contained in base package ipbasek9. The license key for the ipbasek9 package is activated by default.

Technology Packages

Technology packages contain software features within a consolidated package. To use different sets of features, enable the licenses of selected technology packages. You can enable the licenses for any combination of technology packages.

Each technology package has an evaluation license which converts to a Right to Use (RTU) license after 60 days and is then valid permanently.

Technology packages are as follows:

securityk9

The securityk9 technology package includes all crypto features, including IPsec, SSL/SSH, Firewall and Secure VPN.

The securityk9_npe package (npe = No Payload Encryption) includes all features in the securityk9 technology package without any payload-encryption functionality. This is to fulfill export restriction requirements. The package securityk9_npe is available only in universalk9_npe image. The difference in features between the securityk9 package and the securityk9_npe package is therefore the set of payload-encryption enabling features —such as IPsec and Secure VPN.

uck9

The uck9 technology package includes Unified Communications features: CUBE, CME-SRST and SBC.

appxk9

The appxk9 technology package contains Application Experience features.
The features are similar to the features in the DATA package of the Cisco ISR G2 routers at: http://www.cisco.com/en/US/prod/collateral/routers/ps10616/white_paper_c11_556985_ps10536_Products_White_Paper.html#wp9000791 .

There are many features in the appxk9 package—including: MPLS, PfR, L2/L3 VPN, Broadband, and AVC.

Feature Licenses

To use each of the following features, enable a corresponding feature license, as explained in the sections below.

HSECK9

The HSECK9 license is required for a feature to have full crypto functionality. The HSECK9 license allows features in the securityk9 technology package to use the maximum number of secure tunnels and crypto bandwidth. To enable the license for HSECK9, purchase the FL-44-HSEC-K9 license from cisco.com and install it using the command license install license-files . For further information on obtaining and installing feature licenses, see Configuring the Cisco IOS Software Activation Feature


Note The HSECK9 feature does not have an evaluation license that converts to an RTU license after 60 days; a feature license must be obtained.


To enable the license for the HSECK9 feature, the securityk9 technology package is also required.

Performance

The performance feature, which allows for increased throughput, is enabled by the performance license. This feature is part of the ipbasek9 technology package. To enable the feature, order the performance license (part number FL-44-PERF-K9). The license is displayed as the “throughput” license.

To configure the feature, use the command:
platform hardware throughput level throughput

Example

platform hardware throughput level throughput

Enforced Lawful Intercept

Enabling the enforced lawful intercept license allows you to use the Lawful Intercept (LI) feature—available when using Cisco IOS XE 3.11 or higher.

The LI feature requires three technology packages: uck9, securityk9, and appxk9.

Lawful Intercept (LI) is the process by which law enforcement agencies (LEAs) conduct electronic surveillance as authorized by judicial or administrative order. For further information on the LI feature, see Lawful Intercept Architecture , in the Cisco User Security Configuration Guide.

CME-SRST

The CME-SRST feature requires the uck9 technology package. Perform the following steps to activate the CME-SRST feature license:

Activating the CME-SRST feature license

Prerequisites

  • License for uck9 technology package
  • A CME-SRST feature must be configured

SUMMARY STEPS

1. show license detail cme-srst

2. configure terminal

3. license accept end user agreement

4. exit

5. show license detail cme-srst

6. write memory

DETAILED STEPS

 

Command or Action
Purpose

Step 1

show license detail cme-srst

 

Router# show license detail cme-srst

Displays the available cme-srst license. EULA should be in NOT ACCEPTED state.

Step 2

configure terminal

 

Router# configure terminal

Enters global configuration mode.

Step 3

license accept end user agreement

 

Router(config)# license accept end user agreement

Configures a one-time acceptance of the EULA for cme-srst license.

Accepts EULA by typing YES.

Step 4

exit

 

Router(config)# exit

Exits global configuration mode.

Step 5

show license detail cme-srst

 

Router# show license detail cme-srst

Displays the available cme-srst license. EULA should be in ACCEPTED state.

Step 6

write memory

 

Router# write memory

Saves configuration.

Example: Unlicensed Feature

If you try to use a feature that is part of a package that is not enabled, an error message appears.

In this example, during configuration, the crypto map command is called and an error message appears. This is because the feature associated with crypto map is part of the securityk9 package and the securityk9 package has not been previously enabled.

Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#crypto map
^
% Invalid input detected at '^' marker.
 

The following show license feature command shows whether the securityk9 package is enabled. In this example, the output shows that securityk9 is not enabled. Note that ipbasek9 is provided by default.

 
Router# show license feature
Feature name Enforcement Evaluation Subscription Enabled RightToUse
appxk9 yes yes no yes yes
uck9 yes yes no no yes
securityk9 yes yes no no yes
ipbasek9 no no no no yes
 

LED Indicators

For information on LEDs on the router, see “LED Indicators” in the
“Overview” section of the Hardware Installation Guide for the Cisco 4400 Series Integrated Services Routers .

For information on LEDs on the SSD Carrier Card NIM, see “Overview of the SSD Carrier Card NIM (NIM-SSD)” in the “Installing and Upgrading Internal Modules and FRUs” section of the Hardware Installation Guide for the Cisco 4400 Series Integrated Services Routers .

Related Documentation

For further information on software licenses see the Software Activation on Cisco Integrated Services Routers and Cisco Integrated Service Routers G2 . For further information on obtaining and installing feature licenses, see Configuring the Cisco IOS Software Activation Feature .

How to Install and Upgrade Software

To install or upgrade software, use one of following main methods to use software from a consolidated package or individual packages. See the “Overview” section.

Managing and Configuring a Router to Run Using a Consolidated Package


Note Do not use these procedures if you also need to install any optional subpackages or plan to upgrade individual subpackages. See the “Managing and Configuring a Router to Run Using Individual Packages” section.


Managing and Configuring a Consolidated Package Using copy and boot Commands

To upgrade a consolidated package, copy the consolidated package into the bootflash: directory on the router using the copy command, as you would on most other Cisco routers. After making this copy of the consolidated package, configure the router to boot using the consolidated package file.

Example: Managing and Configuring a Consolidated Package Using copy and boot Commands

In this example, the consolidated package file is copied onto the bootflash: file system via TFTP. The config register is then set to boot using boot system commands, and the boot system commands instruct the router to boot using the consolidated package stored in the bootflash: file system. The new configuration is then saved using the copy running-config startup-config command, and the system is then reloaded to complete the process.

Router# dir bootflash:
Directory of bootflash:/
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 Mar 18 2008 17:31:17 -07:00 .prst_sync
43201 drwx 4096 Dec 4 2007 04:34:45 -08:00 .installer
 
928862208 bytes total (712273920 bytes free)
 
Router# copy tftp: bootflash:
Address or name of remote host []? 172.17.16.81
Source filename []? /auto/tftp-users/user/isr4400-universalk9.03.10.00.S.153-3.S-ext.SPA.bin
Destination filename [isr4400-universalk9.03.10.00.S.153-3.S-ext.SPA.bin]?
Accessing
tftp://172.17.16.81//auto/tftp-users/user/isr4400-universalk9.03.10.00.S.153-3.S-ext.SPA.bin
...
Loading /auto/tftp-users/user/isr4400-universalk9.03.10.00.S.153-3.S-ext.SPA.bin from
172.17.16.81 (via GigabitEthernet0):
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!!!!!!!
[OK - 208904396 bytes]
208904396 bytes copied in 330.453 secs (632176 bytes/sec)
Router# dir bootflash:
Directory of bootflash:/
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 Mar 18 2008 17:31:17 -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
isr4400-universalk9.03.10.00.S.153-3.S-ext.SPA.bin
928862208 bytes total (503156736 bytes free)
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# boot system flash
bootflash:isr4400-universalk9.03.10.00.S.153-3.S-ext.SPA.bin
Router(config)# config-reg 0x2102
Router(config)# exit
Router# show run | include boot
boot-start-marker
boot system flash bootflash:isr4400-universalk9.03.10.00.S.153-3.S-ext.SPA.bin
boot-end-marker
Router# copy run start
Destination filename [startup-config]?
Building configuration...
[OK]
Router# reload
 

Configuring a Router to Boot the Consolidated Package via TFTP Using the Boot Command

This section consists of the following example:

Example: Configuring a Router to Boot the Consolidated Package via TFTP Using the boot Command

Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#boot system tftp://10.81.116.4/rtp-isr4400-54/isr4400.bin
Router(config)#config-register 0x2102
Router(config)#exit
Router# show run | include boot
boot-start-marker
boot system tftp://10.81.116.4/rtp-isr4400-54/isr4400.bin
boot-end-marker
license boot level adventerprise
Router# copy running-config startup-config
Destination filename [startup-config]?
Building configuration...
[OK]
Router# reload
Proceed with reload? [confirm]
Sep 13 17:42:54.445 R0/0: %PMAN-5-EXITACTION: Process manager is exiting: process exit with reload chassis code
 
 
Initializing Hardware ...
 
System integrity status: c0000600
Failures detected:
Boot FPGA corrupt
 
 
Key Sectors:(Primary,GOOD),(Backup,GOOD),(Revocation,GOOD)
Size of Primary = 2288 Backup = 2288 Revocation = 300
 
ROM:RSA Self Test Passed
ROM:Sha512 Self Test Passed
Self Tests Latency: 58 msec
 
 
System Bootstrap, Version 12.2(20120618:163328) [username-ESGROM_20120618_GAMMA 101], DEVELOPMENT SOFTWARE
Copyright (c) 1994-2012 by cisco Systems, Inc.
Compiled Mon 06/18/2012 12:39:32.05 by username
 
Current image running: Boot ROM0
 
Last reset cause: LocalSoft
 
Cisco ISR 4400 platform with 4194304 Kbytes of main memory
 
 
IP_ADDRESS: 172.18.42.119
IP_SUBNET_MASK: 255.255.255.0
DEFAULT_GATEWAY: 172.18.42.1
TFTP_SERVER: 10.81.116.4
TFTP_FILE: rtp-isr4400-54/isr4400.bin
TFTP_MACADDR: a4:4c:11:9d:ad:97
TFTP_VERBOSE: Progress
TFTP_RETRY_COUNT: 18
TFTP_TIMEOUT: 7200
TFTP_CHECKSUM: Yes
ETHER_PORT: 0
 
ETHER_SPEED_MODE: Auto Detect
link up...
Receiving rtp-isr4400-54/isr4400.bin from 10.81.116.4 !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
File reception completed.
Boot image size = 424317088 (0x194a90a0) bytes
 
ROM:RSA Self Test Passed
ROM:Sha512 Self Test Passed
Self Tests Latency: 58 msec
 
Package header rev 1 structure detected
Calculating SHA-1 hash...done
validate_package: SHA-1 hash:
calculated 7294dffc:892a6c35:a7a133df:18c032fc:0670b303
expected 7294dffc:892a6c35:a7a133df:18c032fc:0670b303
Signed Header Version Based Image Detected
 
Using FLASH based Keys of type = PRIMARY KEY STORAGE
Using FLASH based Keys of type = ROLLOVER KEY STORAGE
RSA Signed DEVELOPMENT Image Signature Verification Successful.
Package Load Test Latency : 5116 msec
Image validated
%IOSXEBOOT-4-BOOT_ACTIVITY_LONG_TIME: (local/local): load_modules took: 2 seconds, expected max time 2 seconds
 
Restricted Rights Legend
 
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.
 
cisco Systems, Inc.
170 West Tasman Drive
San Jose, California 95134-1706
 
 
 
Cisco IOS Software, IOS-XE Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Experimental Version 15.3(20120910:013018) [mcp_dev-BLD-BLD_MCP_DEV_LATEST_20120910_000023-ios 153]
Copyright (c) 1986-2012 by Cisco Systems, Inc.
Compiled Sun 09-Sep-12 21:28 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
software.
 
 
 
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
export@cisco.com.
 
 
Warning: the compile-time code checksum does not appear to be present.
cisco ISR4451/K9 (2RU) processor with 1133585K/6147K bytes of memory.
Processor board ID FGL1619100P
4 Gigabit Ethernet interfaces
32768K bytes of non-volatile configuration memory.
4194304K bytes of physical memory.
7393215K bytes of Compact flash at bootflash:.
7816688K bytes of USB flash at usb0:.
 
 
Press RETURN to get started!
 
 
Router>
Router>
Router>enable
Router# show version
Cisco IOS Software, IOS-XE Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Experimental Version 15.3(20120910:013018) [mcp_dev-BLD-BLD_MCP_DEV_LATEST_20120910_000023-ios 153]
Copyright (c) 1986-2012 by Cisco Systems, Inc.
Compiled Sun 09-Sep-12 21:28 by mcpre
 
IOS XE Version: BLD_MCP_DEV_LATES
 
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
software.
 
 
ROM: IOS-XE ROMMON
 
Router uptime is 0 minutes
Uptime for this control processor is 3 minutes
--More-- System returned to ROM by reload
System image file is "tftp://10.81.116.4/rtp-isr4400-54/isr4400.bin"
Last reload reason: Reload Command
 
 
 
This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.
 
A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
 
If you require further assistance please contact us by sending email to
export@cisco.com.
 
License Level: adventerprise
License Type: EvalRightToUse
--More-- Next reload license Level: adventerprise
 
cisco ISR4451/K9 (2RU) processor with 1133585K/6147K bytes of memory.
Processor board ID FGL1619100P
4 Gigabit Ethernet interfaces
32768K bytes of non-volatile configuration memory.
4194304K bytes of physical memory.
7393215K bytes of Compact flash at bootflash:.
7816688K bytes of USB flash at usb0:.
 
Configuration register is 0x2102
 

Managing and Configuring a Router to Run Using Individual Packages

To choose between running individual packages or a consolidated package, see the “Overview” section.

Installing Subpackages from a Consolidated Package

Follow the procedure below when obtaining the consolidated package from a TFTP server.

Another variation of this procedure obtains the consolidated package from a USB flash drive, and this is shown in the “Installing Subpackages from a Consolidated Package on a Flash Drive” section.

Prerequisites

Copy the consolidated package to the TFTP server.

SUMMARY STEPS

1. show version

2. dir bootflash:

3. show platform

4. mkdir bootflash: URL-to-directory-name

5. request platform software package expand file URL-to-consolidated-package to URL-to-directory-name

6. reload

7. boot URL-to-directory-name /packages.conf

8. show version installed

DETAILED STEPS

Command or Action
Purpose

Step 1

show version

 

 

Router# show version

Cisco IOS Software, IOS-XE Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Experimental Version 15.3(20120627:221639) [build_151722 111]

Copyright (c) 1986-2012 by Cisco Systems, Inc.

Compiled Thu 28-Jun-12 15:17 by mcpre

.

.

.

Shows the version of software running on the router. This can later be compared with the version of software to be installed.

Step 2

dir bootflash:

 

Router# dir bootflash:

Displays the previous version of software and that a package is present.

Step 3

show platform

 

 

Router# show platform

Chassis type: ISR4452/K9

Check the inventory. Also see the example in the “Installing Subpackages from a Consolidated Package” section.

Step 4

mkdir bootflash : URL-to-directory-name

 

Router# mkdir bootflash:mydir

Creates a directory to hold the expanded software image. The choice of directory is up to you. One suggestion is to use the same name as the image.

Step 5

request platform software package expand file URL-to-consolidated-package to URL-to-directory-name

 

 

Router# request platform software package expand file bootflash:isr4400-universalk9-NIM.bin to bootflash:mydir

Expands the software image from the TFTP server ( URL-to-consolidated-package ) into the directory used to hold the
image ( URL-to-directory-name ), which was created in the previous step.

Step 6

reload

 

Router# reload

rommon >

Enables ROMMON mode, which allows the software in the consolidated file to be activated.

Step 7

boot URL-to-directory-name /packages.conf

 

rommon 1 > boot bootflash:mydir/packages.conf

Boots the consolidated package, by specifying the path and name of the provisioning file: packages.conf.

Step 8

show version installed

 

Router# show version installed

Package: Provisioning File, version: n/a, status: active

 

Displays the version of the newly installed software.

Example: Installing Subpackages

The initial part of the example shows the consolidated package, isr4400-universalk9.164422SSA.bin , being copied to the TFTP server. This is a prerequisite step. The remaining part of the example shows the consolidated file, packages.conf, being booted.

Router# tftp:isr4400/isr4400-universalk9.164422SSA.bin bootflash:
Address or name of remote host []? 1.1.1.1
Destination filename [isr4400-universalk9.164422SSA.bin]?
Accessing tftp://1.1.1.1/isr4400/isr4400-universalk9.164422SSA.bin...
Loading isr4400/isr4400-universalk9.164422SSA.bin from 1.1.1.1 (via GigabitEthernet0): !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[OK - 410506248 bytes]
 
410506248 bytes copied in 338.556 secs (1212521 bytes/sec)
 
 
Router# show version
Cisco IOS Software, IOS-XE Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Experimental Version 15.3(20120627:221639) [build_151722 111]
Copyright (c) 1986-2012 by Cisco Systems, Inc.
Compiled Thu 28-Jun-12 15:17 by mcpre
 
IOS XE Version: 2012-06-28_15.31_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
software.
 
 
ROM: IOS-XE ROMMON
 
Router uptime is 0 minutes
Uptime for this control processor is 3 minutes
System returned to ROM by reload
System image file is "tftp:isr4400/isr4400.bin"
Last reload reason: Reload Command
 
This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.
 
A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
 
If you require further assistance please contact us by sending email to
export@cisco.com.
 
License Level: adventerprise
License Type: EvalRightToUse
Next reload license Level: adventerprise
cisco ISR4451/K9 (2RU) processor with 1136676K/6147K bytes of memory.
Processor board ID FGL161611AB
4 Gigabit Ethernet interfaces
32768K bytes of non-volatile configuration memory.
4194304K bytes of physical memory.
7393215K bytes of Compact flash at bootflash:.
 
Configuration register is 0x8000
 
Router# dir bootflash:
Directory of bootflash:/
 
11 drwx 16384 May 3 2012 19:58:37 +00:00 lost+found
178465 drwx 4096 Jun 6 2012 15:20:20 +00:00 core
584065 drwx 4096 Jul 13 2012 19:19:00 +00:00 .prst_sync
405601 drwx 4096 May 3 2012 19:59:30 +00:00 .rollback_timer
113569 drwx 40960 Jul 13 2012 19:19:32 +00:00 tracelogs
64897 drwx 4096 May 3 2012 19:59:42 +00:00 .installer
13 -rw- 1305 May 7 2012 17:43:42 +00:00 startup-config
14 -rw- 1305 May 7 2012 17:43:55 +00:00 running-config
15 -r-- 1541 Jun 4 2012 18:32:41 +00:00 debug.conf
16 -rw- 1252 May 22 2012 19:58:39 +00:00 running-config-20120522
519169 drwx 4096 Jun 4 2012 15:29:01 +00:00 vman_fdb
 
7451738112 bytes total (7067635712 bytes free)
 
 
 

Router# show platform

Chassis type: ISR4452/K9

 

Slot Type State Insert time (ago)

--------- ------------------- --------------------- -----------------

0 ISR4452/K9 ok 15:57:33

0/0 ISR4451-6X1GE ok 15:55:24

1 ISR4452/K9 ok 15:57:33

1/0 SM-1T3/E3 ok 15:55:24

2 ISR4452/K9 ok 15:57:33

2/0 SM-1T3/E3 ok 15:55:24

R0 ISR4452/K9 ok, active 15:57:33

F0 ISR4451-FP ok, active 15:57:33

P0 Unknown ps, fail never

P1 XXX-XXXX-XX ok 15:56:58

P2 ACS-4450-FANASSY ok 15:56:58

 

Slot CPLD Version Firmware Version

--------- ------------------- ---------------------------------------

0 12090323 15.3(01r)S [ciscouser-ISRRO...

1 12090323 15.3(01r)S [ciscouser-ISRRO...

2 12090323 15.3(01r)S [ciscouser-ISRRO...

R0 12090323 15.3(01r)S [ciscouser-ISRRO...

F0 12090323 15.3(01r)S [ciscouser-ISRRO...

 
Router# mkdir bootflash:isr4400-universalk9.dir1
Create directory filename [isr4400-universalk9.dir1]?
Created dir bootflash:/isr4400-universalk9.dir1
Router# request platform software package expand file bootflash:isr4400-universalk9.NIM.bin to bootflash:isr4400-universalk9.dir1
Verifying parameters
Validating package type
Copying package files
SUCCESS: Finished expanding all-in-one software package.
 
Router# reload
Proceed with reload? [confirm]
 
*Jul 13 19:39:06.354: %SYS-5-RELOAD: Reload requested by console. Reload Reason: Reload Command.
 
rommon 1 > boot bootflash:isr4400-universalk9.dir1/packages.conf
 
File size is 0x00002836
Located isr4400-universalk9.dir1/packages.conf
Image size 10294 inode num 324484, bks cnt 3 blk size 8*512
#
File is comprised of 1 fragments (33%)
 
is_valid_sha1hash: SHA-1 hash:
calculated 62f6235a:fc98eb3a:85ce183e:834f1cb3:8a1f71d1
expected 62f6235a:fc98eb3a:85ce183e:834f1cb3:8a1f71d1
File size is 0x04b3dc00
Located isr4400-universalk9.dir1/isr4400-mono-universalk9-build_164422SSA.pkg
Image size 78896128 inode num 324491, bks cnt 19262 blk size 8*512
#############################################################################################################################################
File is comprised of 21 fragments (0%)
.....
 
 
 
Router# show version installed
Package: Provisioning File, version: n/a, status: active
File: bootflash:isr4400-universalk9.dir1/packages.conf, on: RP0
Built: n/a, by: n/a
File SHA1 checksum: ad09affd3f8820f4844f27acc1add502e0b8f459
 
Package: rpbase, version: 2012-07-10_16.22_mcpre, status: active
File: bootflash:isr4400-universalk9.dir1/isr4400-mono-universalk9-build_164422SSA.pkg, on: RP0
Built: 2012-07-10_16.22, by: mcpre
File SHA1 checksum: 5e95c9cbc4eaf5a4a5a1ac846ee2d0f41d1a026b
 
Package: firmware_attributes, version: 2012-07-10_16.22_mcpre, status: active
File: bootflash:isr4400-universalk9.dir1/isr4400-firmware_attributes_164422SSA.pkg, on: RP0/0
Built: 2012-07-10_16.22, by: mcpre
File SHA1 checksum: 71614f2d9cbe7f96d3c6e99b67d514bd108c6c99
 
Package: firmware_dsp_sp2700, version: 2012-07-10_16.22_mcpre, status: active
File: bootflash:isr4400-universalk9.dir1/isr4400-firmware_dsp_164422SSA.pkg, on: RP0/0
Built: 2012-07-10_16.22, by: mcpre
File SHA1 checksum: 8334565edf7843fe246783b1d5c6ed933d96d79e
Package: firmware_fpge, version: 2012-07-10_16.22_mcpre, status: active
File: bootflash:isr4400-universalk9.dir1/isr4400-firmware_fpge_164422SSA.pkg, on: RP0/0
Built: 2012-07-10_16.22, by: mcpre
File SHA1 checksum: eb72900ab32c1c50652888ff486cf370ac901dd7
 
Package: firmware_sm_1t3e3, version: 2012-07-10_16.22_mcpre, status: active
File: bootflash:isr4400-universalk9.dir1/isr4400-firmware_sm_1t3e3_164422SSA.pkg, on: RP0/0
Built: 2012-07-10_16.22, by: mcpre
File SHA1 checksum: 803005f15d8ea71ab088647e2766727ac2269871
 
Package: rpcontrol, version: 2012-07-10_16.22_mcpre, status: active
File: bootflash:isr4400-universalk9.dir1/isr4400-mono-universalk9_164422SSA.pkg, on: RP0/0
Built: 2012-07-10_16.22, by: mcpre
File SHA1 checksum: 980fd58fe581e9346c44417b451d1c09ebb640c2
 
Package: rpios-universalk9, version: dir1, status: active
File: bootflash:isr4400-universalk9.dir1/isr4400-mono-universalk9_164422SSA.pkg, on: RP0/0
Built: 2012-07-10_16.23, by: mcpre
File SHA1 checksum: 27084f7e30a1d69d45a33e05d1b00345040799fb
Package: rpaccess, version: 2012-07-10_16.22_mcpre, status: active
File: bootflash:isr4400-universalk9.dir1/isr4400-mono-universalk9_164422SSA.pkg, on: RP0/0
Built: 2012-07-10_16.22, by: mcpre
File SHA1 checksum: 0119802deda2da91c38473c47a998fb3ed423448
 
Package: firmware_attributes, version: 2012-07-10_16.22_mcpre, status: n/a
File: bootflash:isr4400-universalk9.dir1/isr4400-firmware_attributes_164422SSA.pkg, on: RP0/1
Built: 2012-07-10_16.22, by: mcpre
File SHA1 checksum: 71614f2d9cbe7f96d3c6e99b67d514bd108c6c99
 
Package: firmware_dsp_sp2700, version: 2012-07-10_16.22_mcpre, status: n/a
File: bootflash:isr4400-universalk9.dir1/isr4400-firmware_dsp_164422SSA.pkg, on: RP0/1
Built: 2012-07-10_16.22, by: mcpre
File SHA1 checksum: 8334565edf7843fe246783b1d5c6ed933d96d79e
 
Package: firmware_fpge, version: 2012-07-10_16.22_mcpre, status: n/a
File: bootflash:isr4400-universalk9.dir1/isr4400-firmware_fpge-BLD-BLD_MCP_DEV_LATEST_20120710_164422SSA.pkg, on: RP0/1
Built: 2012-07-10_16.22, by: mcpre
File SHA1 checksum: eb72900ab32c1c50652888ff486cf370ac901dd7
 
Package: firmware_sm_1t3e3, version: 2012-07-10_16.22_mcpre, status: n/a
File: bootflash:isr4400-universalk9.dir1/isr4400-firmware_sm_1t3e3-BLD-BLD_MCP_DEV_LATEST_20120710_164422SSA.pkg, on: RP0/1
Built: 2012-07-10_16.22, by: mcpre
File SHA1 checksum: 803005f15d8ea71ab088647e2766727ac2269871
 
Package: rpcontrol, version: 2012-07-10_16.22_mcpre, status: n/a
File: bootflash:isr4400-universalk9.dir1/isr4400-rpcontrol-BLD-BLD_MCP_DEV_LATEST_20120710_164422SSA.pkg, on: RP0/1
Built: 2012-07-10_16.22, by: mcpre
File SHA1 checksum: 980fd58fe581e9346c44417b451d1c09ebb640c2
 
Package: rpios-universalk9, version: 2012-07-10_16.23_mcpre, status: n/a
File: bootflash:isr4400-universalk9.dir1/isr4400-rpios-universalk9-BLD-BLD_MCP_DEV_LATEST_20120710_164422SSA.pkg, on: RP0/1
Built: 2012-07-10_16.23, by: mcpre
File SHA1 checksum: 27084f7e30a1d69d45a33e05d1b00345040799fb
 
Package: rpaccess, version: 2012-07-10_16.22_mcpre, status: n/a
File: bootflash:isr4400-universalk9.dir1/isr4400-rpaccess-BLD-BLD_MCP_DEV_LATEST_20120710_164422SSA.pkg, on: RP0/1
Built: 2012-07-10_16.22, by: mcpre
File SHA1 checksum: 0119802deda2da91c38473c47a998fb3ed423448
 
Package: rpbase, version: 2012-07-10_16.22_mcpre, status: n/a
File: bootflash:isr4400-universalk9.dir1/isr4400-rpbase-BLD-BLD_MCP_DEV_LATEST_20120710_164422SSA.pkg, on: RP1
Built: 2012-07-10_16.22, by: mcpre
File SHA1 checksum: 5e95c9cbc4eaf5a4a5a1ac846ee2d0f41d1a026b
 
Package: firmware_attributes, version: 2012-07-10_16.22_mcpre, status: n/a
File: bootflash:isr4400-universalk9.dir1/isr4400-firmware_attributes-BLD-BLD_MCP_DEV_LATEST_20120710_164422SSA.pkg, on: RP1/0
Built: 2012-07-10_16.22, by: mcpre
File SHA1 checksum: 71614f2d9cbe7f96d3c6e99b67d514bd108c6c99
 
Package: firmware_dsp_sp2700, version: 2012-07-10_16.22_mcpre, status: n/a
File: bootflash:isr4400-universalk9.dir1/isr4400-firmware_dsp_sp2700-BLD-BLD_MCP_DEV_LATEST_20120710_164422SSA.pkg, on: RP1/0
Built: 2012-07-10_16.22, by: mcpre
File SHA1 checksum: 8334565edf7843fe246783b1d5c6ed933d96d79e
 
Package: firmware_fpge, version: 2012-07-10_16.22_mcpre, status: n/a

 

Installing Subpackages from a Consolidated Package on a Flash Drive

The steps for installing subpackages from a consolidated package on a USB flash drive are similar to those shown in the
“Installing Subpackages from a Consolidated Package” section.

Prerequisites

Copy the desired consolidated package/image to a USB flash drive and insert the USB flash drive into one of the router’s USB ports.

Summary Steps

1. show version

2. dir usb n :

3. show platform

4. mkdir bootflash: URL-to-directory-name

5. request platform software package expand file usb n : package-name to URL-to-directory-name

6. reload

7. boot URL-to-directory-name /packages.conf

8. show version installed

Installing a Firmware Subpackage

The second method of installing individual subpackages is described below. Installing a firmware subpackage can be done if the router has previously been configured using, for example, the
“Managing and Configuring a Router to Run Using Individual Packages” section.

Firmware sub packages are not released individually. You can select a firmware package from within a consolidated package after expanding the consolidated package. The firmware package can then be installed as shown in the steps below.

Prerequisites

Obtain a consolidated package that contains your required firmware package and expand the package. (See the “Managing and Configuring a Router to Run Using Individual Packages” section.) Take a note of the location and name of the firmware package and use this information in the steps below for the “ URL-to-package-name .


Note Read the release notes of the consolidated package, to verify that the firmware within the consolidated package is compatible with the version of Cisco IOS XE software that is currently installed on the router.


SUMMARY STEPS

1. show version

2. dir bootflash:

3. show platform

4. request platform software package install rp 0 file URL-to-package-name auto-copy on-reboot

5. reload

6. show version installed

DETAILED STEPS

Command or Action
Purpose

Step 1

show version

 
Router# show version

Cisco IOS Software, IOS-XE Software

.

.

Shows the version of software running on the router.

Step 2

dir bootflash:

 

Router# dir bootflash:

Lists the file names in bootflash.

Step 3

show platform

 

Router# show platform

Displays the inventory.

Step 4

request platform software package install rp 0 file URL-to-package-name [on-reboot]

 

Router# request platform software package install rp 0 file isr4400-universalk9.2012-07-10_16.24_myname/isr4400-firmware_sm_1t3e3.2012-07-10_16.24_myname.SSA.pkg on-reboot

Installs a firmware package.

on-reboot —Specifies that the installation will not be completed until the next RP reboot.

Step 5

reload

Restarts the router and allows the software in the consolidated file to be activated.

Step 6

show version installed

Example

Router# show version installed

Package: Provisioning File, version: n/a, status: active

File: consolidated:packages.conf, on: RP0

Built: n/a, by: n/a

File SHA1 checksum: 62150e0836e9d3e1d7059d09b04e87aa0d037dcd

 

Package: rpbase, version: BLD_V153_2_S_XE39_THROTTLE_LATEST_20130226_121211, status: active

File: consolidated:isr4400-mono-universalk9.BLD_V153_2_S_XE39_THROTTLE_LATEST_20130226_121211.SSA.pkg, on: RP0

Built: 2013-02-26_09.35, by: mcnam

File SHA1 checksum: e2752dae72da5596cab1fc5c762f46fd37438849

.

.

.

Displays the Package and version of software that has been installed.