Installing The Software: Cisco 4000 Series Isrs Software Configuration Guide Ol-29328-03
Installing The Software: Cisco 4000 Series Isrs Software Configuration Guide Ol-29328-03
• Overview, page 1
• ROMMON Images, page 2
• Provisioning Files, page 2
• File Systems, page 2
• Autogenerated File Directories and Files, page 3
• Flash Storage, page 4
• Configuring the Configuration Register for Autoboot, page 4
• Licensing, page 5
Overview
Installing software on the router involves installing a consolidated package (bootable image). This consists
of a bundle of subpackages (modular software units), with each subpackage controlling a different set of
functions.
These are the two main methods to install the software:
• Managing and Configuring a Router to Run Using a Consolidated Package, on page 13—This method
allows for individual upgrade of subpackages and generally has reduced boot times compared to the
method below. Use this method if you want to individually upgrade a module's software.
• Managing and Configuring a Router to Run Using Individual Packages, on page 17—This a simple
method that is similar to a 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 a 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 4000 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. For detailed instructions, see the documentation that accompanies
the ROMMON image.
Note A new version of the ROMMON image is not necessarily released at the same time as a consolidated
package for a router.
Provisioning Files
This section provides background information about the files and processes used in Managing and Configuring
a Router to Run Using Individual Packages, on page 17.
The consolidated package on a router consists of a collection of subpackages and a provisioning file titled
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 file's name can be renamed
but subpackage file's names 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 a router to boot, using the provisioning file packages.conf, is beneficial 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 Configuring the Router to Boot Using
Subpackages.
File Systems
The following table provides a list of file systems that can be seen on the Cisco 4000 series routers.
harddisk: Hard disk file system (if NIM-SSD, NIM-HDD, or internal mSATA flash device is
present in the router).
Note The internal mSATA flash device is supported only on Cisco ISR4300 Series
routers.
cns: Cisco Networking Services file directory.
nvram: Router NVRAM. You can copy the startup configuration to NVRAM or from
NVRAM.
system: System memory file system, which includes the running configuration.
usb0: The Universal Serial Bus (USB) flash drive file systems.
usb1: Note The USB flash drive file system is visible only if a USB drive is installed
in usb0: or usb1: ports.
Use the ? help option, or use the copy command in command reference guides, if you find a file system that
is not listed in the table above.
Note Altering autogenerating files on the bootflash: may have unpredictable consequences
for system performance.
Flash Storage
Subpackages are installed to local media storage, such as flash. For flash storage, use the dir bootflash:
command to list the file names.
For more information about the configuration register, see Use of the Configuration Register on All Cisco
Routers and Configuring a Router to Boot the Consolidated Package via TFTP Using the boot Command:
Example, on page 14.
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, change the setting on your terminal
emulation software to 9600.
Licensing
• Cisco Software Licensing, on page 5
• Consolidated Packages, on page 5
• Technology Packages, on page 6
• Feature Licenses, on page 7
• Unlicensed Feature: Example, on page 12
Consolidated Packages
One of the following two consolidated packages (images) is preinstalled on the router:
• universalk9—Contains the ipbasek9 base package and the securityk9, uck9, and appxk9 technology
packages.
• universalk9_npe—Contains the ipbasek9 base package and the securityk9_npe, uck9, and appxk9
technology packages. This image has limited crypto functionality.
Note The terms super package and image also refer to a consolidated package.
Many features within the consolidated package are contained in the ipbasek9 base package. 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 that converts to a Right to Use (RTU) license after 60
days and is then valid permanently.
The following is a list of technology packages:
• securityk9, on page 6
• uck9, on page 7
• appxk9, on page 7
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 the features in the securityk9
technology package without the payload-encryption functionality. This is to fulfill export restriction
requirements. The securityk9_npe package is available only in the 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 the following Cisco Unified Communications features:
• CUBE
• CME-SRST
• SBC
appxk9
The appxk9 technology package contains Application Experience features, which are similar to the features
in the DATA package of the Cisco Integrated Services Routers Generation 2 routers. For more information,
see: http://www.cisco.com/c/en/us/products/collateral/cloud-systems-management/
software-activation-on-integrated-services-routers-isr/white_paper_c11_556985.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 following
sections:
• HSECK9, on page 7
• Performance, on page 8
• CME-SRST, on page 10
HSECK9
The HSECK9 license is required for a feature to have full crypto functionality. Without the HSECK9 license,
only 225 secure tunnels and 85 Mbps of crypto bandwidth would be available. The HSECK9 license allows
features in the securityk9 technology package to use the maximum number of secure tunnels and crypto
bandwidth. To enable the HSECK9 license, purchase the FL-44-HSEC-K9 license from Cisco.com and
install it using the license install license-files command. 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. For more
information about the securityk9 technology package, see securityk9, on page 6.
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.
You can upgrade the throughput of the ESP from 2.5 Gbps to 5 Gbps by activating the right-to-use license
and then reloading the router. For more information on the right-to-use license activation, see Configuring
Cisco Right-To-Use License Configuration Guide. If you want to determine the current throughput level
of the ESP, run the show platform hardware throughput level command. The following example shows the
output of this command before the performance upgrade license is applied:
To configure the throughput level, perform the following steps and to upgrade the throughput level use the
platform hardware throughput level { 2500000 | 5000000} command.
Return of license:
• The device is in the smart license mode with boost performance command configured.
• Use show running-config show license summaryand the license usage commands to display the boost
performance information from the smart account.
• Use the no platform hardware throughput level boost command to disable the functionality.
Note The command is removed from the configuration, but the license is released only after the device is
reloaded.
The throughput level does not take effect until the device is reloaded.
The license visibility is available till the device is reloaded.
One count of boost performance license is reduced from the usage pool, and one license is returned to its
original pool.
Cisco Software License to Smart Licensing
This is to describe a use-case when the device is moving from Cisco Software License(CSL) to Smart License
when boost performance license is on CSL. The boost performance behavior is determined by the availability
of the license in its Smart Account with Boost Performance activated in use in CSL:
To configure the throughput level, perform the following steps and to upgrade the throughput level use the
1 Configure the device with the platform hardware throughput level boost command and then use show
running-config to check if the boost performance license is activated.
2 Use show license to verify if boost performance is in use and in a permanent license mode.
3 Enable smart license by license smart enable command. After registration in success, the license request
is sent to the smart portal for validation. Boost performance is valid if successful, no reload is required.
Otherwise the platform hardware throughput level boost is unattached from configuration. Boost
performance functionality is disabled after reload.
4 During the transition but before the registration, we have to maintain the Evaluation mode for the license
if the is existing to avoid an extra reload later.
5 To exit global configuration mode, enter exit.
6 To save the configuration, enter the copy running-config startup-config command.
7 To reload the router enter reload. A reload is required to activate the throughput level.
CME-SRST
The CME-SRST feature requires the uck9 technology package. To activate the CME-SRST feature license,
see Activating the CME-SRST Feature License, on page 11.
SUMMARY STEPS
DETAILED STEPS
Example:
Router# configure terminal
Step 3 license accept end user agreement Configures a one-time acceptance of the EULA for the
CME-SRST license.
Example: Accept the EULA by typing YES.
Router# license accept end user agreement
Example:
Router# exit
Step 5 show license detail cme-srst Displays the available CME-SRST license.
Note The EULA should be in ACCEPTED
Example: state.
Router# show license detail cme-srst
Example:
Router# write memory
LED Indicators
For information on LEDs on the router, see "LED Indicators" in the "Overview" section of the Hardware
Installation Guide for the Cisco 4000 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 4000 Series Integrated Services Routers.
Related Documentation
For further information on software licenses, see 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.
Note Do not use these procedures if you also need to install any optional subpackages or plan to upgrade
individual subpackages. See Managing and Configuring a Router to Run Using Individual Packages, on
page 17.
• Managing and Configuring a Consolidated Package Using copy and boot Commands, on page 13
• Configuring a Router to Boot the Consolidated Package via TFTP Using the boot Command: Example,
on page 14
Managing and Configuring a Consolidated Package Using copy and boot Commands
To upgrade a consolidated package, copy the consolidated package to the bootflash: directory on the router
using the copy command. After making this copy of the consolidated package, configure the router to boot
using the consolidated package file.
The following example shows the consolidated package file being copied to 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
Configuring a Router to Boot the Consolidated Package via TFTP Using the boot Command:
Example
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
Key Sectors:(Primary,GOOD),(Backup,GOOD),(Revocation,GOOD)
Size of Primary = 2288 Backup = 2288 Revocation = 300
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
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.
A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
Router>
Router>
Router>enable
Router# show version
Cisco IOS XE Software, Version BLD_V154_3_S_XE313_THROTTLE_LATEST_20140527_070027-ext
Cisco IOS Software, ISR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Experimental Version
15.4(20140527:095327)
v154_3_s_xe313_throttle-BLD-BLD_V154_3_S_XE313_THROTTLE_LATEST_20140527_070027-ios 156]
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
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
Step 2 dir bootflash: Displays the previous version of software and that a
package is present.
Example:
Router# dir bootflash:
Example:
Router# show platform
Chassis type: ISR4451/K9
Step 4 mkdir bootflash: URL-to-directory-name Creates a directory to save the expanded software image.
You can use the same name as the image to name the
Example: directory.
Router# mkdir bootflash:mydir
Step 5 request platform software package expand file Expands the software image from the TFTP server
URL-to-consolidated-package to URL-to-directory-name (URL-to-consolidated-package) into the directory used
to save the image (URL-to-directory-name), which was
Example: created in Step 4.
Router# request platform software package expand
file
bootflash:isr4400-universalk9-NIM.bin to
bootflash:mydir
Step 7 boot URL-to-directory-name/packages.conf Boots the consolidated package, by specifying the path
and name of the provisioning file: packages.conf.
Example:
rommon 1 > boot bootflash:mydir/packages.conf
Step 8 show version installed Displays the version of the newly installed software.
Example:
Router# show version installed
Package: Provisioning File, version: n/a, status:
active
Examples
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# copy 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]
A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
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]
How to Install and Upgrade the Software for Cisco IOS XE Denali Release16.3
To install or upgrade the software, use one of the following methods to use the software from a consolidated
package or an individual package. Also see Overview, on page 1.
• Managing and Configuring a Router to Run Using a Consolidated Package, on page 13
• Managing and Configuring a Router to Run Using Individual Packages, on page 17
• Configuring a Router to Boot the Consolidated Package via TFTP Using the boot Command: Example,
on page 14
• Upgrading to Cisco IOS XE Denali Release 16.3, on page 23
Note When the device boots up for first time and if the device requires an upgrade, the entire boot process may
take several minutes. This process will be longer than a normal boot due to the ROMMON upgrade.
The following example illustrates the boot process of a consolidated package:
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
Key Sectors:(Primary,GOOD),(Backup,GOOD),(Revocation,GOOD)
Size of Primary = 2288 Backup = 2288 Revocation = 300
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
To make the new ROMMON permanent, you must restart the RP.
ROMMON upgrade successful. Rebooting for upgrade to take effect.
Expected hash:
ddaf35a193617abacc417349ae204131
12e6fa4e89a97ea20a9eeee64b55d39a
2192992a274fc1a836ba3c23a3feebbd
454d4423643ce80e2a9ac94fa54ca49f
Obtained hash:
ddaf35a193617abacc417349ae204131
12e6fa4e89a97ea20a9eeee64b55d39a
2192992a274fc1a836ba3c23a3feebbd
454d4423643ce80e2a9ac94fa54ca49f
ROM:Sha512 Self Test Passed
Self Tests Latency: 418 msec
Rom image verified correctly
Expected hash:
DDAF35A193617ABACC417349AE204131
12E6FA4E89A97EA20A9EEEE64B55D39A
2192992A274FC1A836BA3C23A3FEEBBD
454D4423643CE80E2A9AC94FA54CA49F
Obtained hash:
DDAF35A193617ABACC417349AE204131
12E6FA4E89A97EA20A9EEEE64B55D39A
2192992A274FC1A836BA3C23A3FEEBBD
454D4423643CE80E2A9AC94FA54CA49F
Sha512 Self Test Passed
Rom image verified correctly
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
Expected hash:
DDAF35A193617ABACC417349AE204131
12E6FA4E89A97EA20A9EEEE64B55D39A
2192992A274FC1A836BA3C23A3FEEBBD
454D4423643CE80E2A9AC94FA54CA49F
Obtained hash:
DDAF35A193617ABACC417349AE204131
12E6FA4E89A97EA20A9EEEE64B55D39A
2192992A274FC1A836BA3C23A3FEEBBD
454D4423643CE80E2A9AC94FA54CA49F
Sha512 Self Test Passed
Found package arch type ARCH_i686_TYPE
Found package FRU type FRU_RP_TYPE
Calculating SHA-1 hash...Validate package: SHA-1 hash:
calculated 8B082C48:35C23C9E:8A091441:D6FACEE6:B5111533
expected 8B082C48:35C23C9E:8A091441:D6FACEE6:B5111533
Image validated
A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
Note Read the Release Notes document pertaining to 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 a router.
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
Step 2 dir bootflash: Displays the previous version of software and that a
package is present.
Example:
Router# dir bootflash:
Step 4 mkdir bootflash: URL-to-directory-name Creates a directory to save the expanded software image.
You can use the same name as the image to name the
Example: directory.
Router# mkdir bootflash:mydir
Step 5 request platform software package expand file Expands the software image from the TFTP server
URL-to-consolidated-package to URL-to-directory-name (URL-to-consolidated-package) into the directory used to
save the image (URL-to-directory-name), which was
Example: created in the Step 4.
Router# request platform software package expand
file
bootflash:isr4400-universalk9-NIM.bin to
bootflash:mydir
Step 7 boot URL-to-directory-name /packages.conf Boots the consolidated package by specifying the path and
name of the provisioning file: packages.conf.
Example:
rommon 1 > boot bootflash:mydir/packages.conf
Step 8 show version installed Displays the version of the newly installed software.
Example:
Router# show version installed
Package: Provisioning File, version: n/a, status:
active
Examples
The initial part of the following 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]
A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
Router# reload
Proceed with reload? [confirm]
SUMMARY STEPS
DETAILED STEPS
Step 2 request platform software package expand file bootflash:/mydir /<IOS-XE image Expands the platform software
to expand super package. package to super package.
Example:
Router# request platform software package expand file
bootflash:/mydir/isr4400-universalk9.03.14.00.S.155-1.S-std.SPA.bin
Step 5 copy NIM firmware subpackage to the folder bootflash:mydir/. Copies the NIM firmware
subpackage into bootflash:mydir.
Example:
Router#copy
bootflash:isr4400-firmware_nim_xdsl.2014-11-17_11.05_39n.SSA.pkg
bootflash:mydir/
Step 6 request platform software package install rp 0 file bootflash:/mydir/<firmware Installs the software package.
subpackage>.
Example:
Router#equest platform software package install rp 0 file
bootflash:mydir/isr4400-firmware_nim_xdsl.2014-11-17_11.05_39n.SSA.pkg
Step 7 hw-module subslot x/y reload to boot the module with the new firmware. Reloads the hardware module subslot
and boots the module with the new
Example: firmware.
Router#hw-module subslot 0/2 reload
Step 8 show platform software subslot 0/2 module firmware to verify that the module Displays the version of the newly
is booted up with the new firmware. installed firmware.
Example:
Router# show platform software subslot 0/2 module firmware
Pe
Examples
The following example shows how to perform firmware upgrade in a router module:
Routermkdir bootflash:mydir
Create directory filename [mydir]?
Created dir bootflash:/mydir
Router#c
Router#copy bootflash:isr4400-universalk9.03.14.00.S.155-1.S-std.SPA.bin bootflash:mydir/
Destination filename [mydir/isr4400-universalk9.03.14.00.S.155-1.S-std.SPA.bin]?
Copy in progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCC
425288648 bytes copied in 44.826 secs (9487544 bytes/sec)
Router#
Router#
Router#dir bootflash:mydir
Directory of bootflash:/mydir/
Router#reload
Proceed with reload? [confirm]
#
File size is 0x150ae3cc
Located mydir/isr4400-mono-universalk9.03.14.00.S.155-1.S-std.SPA.pkg
Image size 353035212 inode num 356929, bks cnt 86191 blk size 8*512
###################################################################
######################################################################
Boot image size = 353035212 (0x150ae3cc) bytes
A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
*Dec 12 09:28:58.922:
%IOS_LICENSE_IMAGE_APPLICATION-6-LICENSE_LEVEL:
Module name = esg Next reboot level = appxk9 and License = appxk9
*Dec 12 09:28:58.943:
%IOS_LICENSE_IMAGE_APPLICATION-6-LICENSE_LEVEL:
Module name = esg Next reboot level = ipbasek9 and License = ipbasek9
*Dec 12 09:28:58.981:
%ISR_THROUGHPUT-6-LEVEL: Throughput level has been set to 1000000 kbps
*Dec 12 09:29:13.302: %SPANTREE-5-EXTENDED_SYSID: Extended SysId enabled for type vlan
*Dec 12 09:29:14.142: %LINK-3-UPDOWN: Interface Lsmpi0, changed state to up
*Dec 12 09:29:14.142: %LINK-3-UPDOWN: Interface EOBC0, changed state to up
*Dec 12 09:29:14.142: %LINK-3-UPDOWN: Interface GigabitEthernet0, changed state to down
*Dec 12 09:29:14.142: %LINK-3-UPDOWN: Interface LIIN0, changed state to up
*Dec 12 09:28:51.438: %CMRP-3-PFU_MISSING:cmand: The platform does not detect a power
supply in slot 1
*Dec 12 09:29:01.256: %CMLIB-6-THROUGHPUT_VALUE:cmand: Throughput license found, throughput
set to 1000000 kbps
*Dec 12 09:29:03.223: %CPPHA-7-START:cpp_ha: CPP 0 preparing ucode
*Dec 12 09:29:03.238: %CPPHA-7-START:cpp_ha: CPP 0 startup init
*Dec 12 09:29:11.335: %CPPHA-7-START:cpp_ha: CPP 0 running init
*Dec 12 09:29:11.645: %CPPHA-7-READY:cpp_ha: CPP 0 loading and initialization complete
*Dec 12 09:29:11.711: %IOSXE-6-PLATFORM:cpp_cp:
Process CPP_PFILTER_EA_EVENT__API_CALL__REGISTER
*Dec 12 09:29:16.280:
%IOSXE_MGMTVRF-6-CREATE_SUCCESS_INFO:
Management vrf Mgmt-intf created with ID 1, ipv4 table-id 0x1, ipv6 table-id 0x1E000001
*Dec 12 09:29:16.330:
%LINEPROTO-5-UPDOWN: Line protocol on Interface Lsmpi0, changed state to up
*Dec 12 09:29:16.330:
%LINEPROTO-5-UPDOWN: Line protocol on Interface EOBC0, changed state to up
*Dec 12 09:29:16.330:
%LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0, changed state to down
*Dec 12 09:29:16.330:
%LINEPROTO-5-UPDOWN: Line protocol on Interface LIIN0, changed state to up
*Dec 12 09:29:17.521: %SYS-5-LOG_CONFIG_CHANGE: Buffer logging disabled
*Dec 12 09:29:18.867: %SYS-5-CONFIG_I: Configured from memory by console
*Dec 12 09:29:18.870:
%IOSXE_OIR-6-REMSPA: SPA removed from subslot 0/0, interfaces disabled
*Dec 12 09:29:18.870:
%IOSXE_OIR-6-REMSPA: SPA removed from subslot 0/1, interfaces disabled
*Dec 12 09:29:18.871:
%IOSXE_OIR-6-REMSPA: SPA removed from subslot 0/2, interfaces disabled
*Dec 12 09:29:18.873:
%SPA_OIR-6-OFFLINECARD: SPA (ISR4451-X-4x1GE) offline in subslot 0/0
*Dec 12 09:29:18.874: %SPA_OIR-6-OFFLINECARD: SPA (NIM-VA-B) offline in subslot 0/1
*Dec 12 09:29:18.874: %SPA_OIR-6-OFFLINECARD: SPA (NIM-VAB-A) offline in subslot 0/2
*Dec 12 09:29:18.876: %IOSXE_OIR-6-INSCARD: Card (fp) inserted in slot F0
Daemon Status: UP
TC Mode: PTM
Selftest Result: 0x00
DELT configuration: disabled
DELT state: not running
Line 1:
Router#
Router#
Router#copy bootflash:isr4400-firmware_nim_xdsl.2014-11-17_11.05_39n.SSA.pkg
bootflash:mydir/
Destination filename [mydir/isr4400-firmware_nim_xdsl.2014-11-17_11.05_39n.SSA.pkg]?
Copy in progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
6640604 bytes copied in 1.365 secs (4864911 bytes/sec)
Router#
Modem Up time
-------------------------------------------
0D 0H 25M 38S
Router#
Version: 1.1
Modem Up time
-------------------------------------------
0D 0H 0M 42S
Router#