Cisco 4000 Series ISRs Software Configuration Guide
Installing the Software
Downloads: This chapterpdf (PDF - 1.53 MB) The complete bookPDF (PDF - 4.38 MB) | Feedback

Installing the Software

Contents

Installing the Software

This chapter includes the following sections:

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:

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.

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.

Table 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 (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.

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.

Note   

The USB flash drive file system is visible only if a USB drive is installed in usb0: or usb1: ports.

usbtoken0:

usbtoken1:

usbtoken file system.

Note   

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

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.

Autogenerated File Directories and Files

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

Table 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 Cisco IOS process fails, for instance, users or troubleshooting personnel can access trace files using diagnostic mode to gather information related to the Cisco IOS failure.

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

Important Notes About Autogenerated Directories

Important information about autogenerated directories include:

  • Autogenerated files on the bootflash: directory should not be deleted, renamed, moved, or altered in any way unless directed by Cisco customer support.


    Note


    Altering autogenerating files on the bootflash: may 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 the dir bootflash: command to list the file names.


Note


Flash storage is required for successful operation of a router.


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, by using one of the following commands:

  • In Cisco IOS configuration mode, use the config-reg 0x0 command.

  • From the ROMMON prompt, use the confreg 0x0 command.

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.


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

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 pertain to 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 applies only 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" chapter of the Software Activation Configuration Guide, Cisco IOS XE Release 3S.

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 term npe stands for No Payload Encryption.



Note


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


To obtain software images for the router, go to http:/​/​software.cisco.com/​download/​navigator.html.

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

Apart from the universalk9 and universalk9_npe images, a Boot ROMMON image is available. For more information, see ROMMON Images.

For more 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, Cisco IOS XE Release 3S.

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 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

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

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.

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 platform hardware throughput level throughput command in the global configuration mode:

platform hardware throughput level throughput

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.

Activating the CME-SRST Feature License

Before You Begin

Ensure the following:

  • License for uck9 technology package is available.

  • The CME-SRST feature is 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 ActionPurpose
    Step 1 show license detail cme-srst


    Example:
    Router# show license detail cme-srst
     

    Displays the available CME-SRST license.

    Note   

    The EULA should be in NOT ACCEPTED state.

     
    Step 2 configure terminal


    Example:
    Router# configure terminal
     

    Enters global configuration mode.

     
    Step 3 license accept end user agreement


    Example:
    Router# license accept end user agreement
     

    Configures a one-time acceptance of the EULA for the CME-SRST license.

    Accept the EULA by typing YES.

     
    Step 4 exit


    Example:
    Router# exit
     

    Exits global configuration mode.

     
    Step 5 show license detail cme-srst


    Example:
    Router# show license detail cme-srst
     

    Displays the available CME-SRST license.

    Note   

    The EULA should be in ACCEPTED state.

     
    Step 6 write memory


    Example:
    Router# write memory
     

    Saves configuration.

     

    Unlicensed Feature: Example

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

    In the following example, the crypto map command is called during configuration and an error message is displayed. This is because, the feature associated with crypto map is part of the securityk9 package and the securityk9 package is not enabled.

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

    Use the show license feature command to view the license features that are enabled. In the following example, the securityk9 and the uck9 packages are not enabled.


    Note


    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             yes      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 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.

    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 an individual package. Also see Overview.

    Managing and Configuring a Router to Run Using a Consolidated Package

    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
     
    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: 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 
    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-2014 by cisco Systems, Inc.
    Compiled Mon 05/27/2014 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, 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]
    Copyright (c) 1986-2014 by Cisco Systems, Inc.
    Compiled Tue 27-May-14 21:28 by mcpre
     
    Cisco IOS-XE software, Copyright (c) 2005-2014 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 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]
     
    IOS XE Version: BLD_V154_3_S_XE313_THROTTLE_LATEST
     
    Cisco IOS-XE software, Copyright (c) 2005-2014 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://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 Overview.

    The following topics are included in this section:

    Installing Subpackages from a Consolidated Package

    Perform the following procedure to obtain the consolidated package from a TFTP server.

    Another variation of this procedure obtains the consolidated package from a USB flash drive. This is described in Installing Subpackages from a Consolidated Package on a Flash Drive.

    Before You Begin

    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 ActionPurpose
      Step 1 show version


      Example:
      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:


      Example:
      Router# dir bootflash:
       

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

       
      Step 3 show platform


      Example:
      Router# show platform
      Chassis type: ISR4451/K9
       

      Displays the inventory.

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


      Example:
      Router# mkdir bootflash:mydir
       

      Creates a directory to save the expanded software image.

      You can use the same name as the image to name the directory.

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


      Example:
      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 save the image (URL-to-directory-name), which was created in Step 4.

       
      Step 6 reload


      Example:
      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


      Example:
      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


      Example:
      Router# show version installed
      Package: Provisioning File, version: n/a, status: active
       

      Displays the version of the newly installed software.

       
      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]
       
      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: ISR4451/K9
      
      Slot         Type                State                 Insert time (ago)
      ---------    ------------------- --------------------- -----------------
      0            ISR4451/K9          ok                    15:57:33
       0/0         ISR4451-6X1GE       ok                    15:55:24
      1            ISR4451/K9          ok                    15:57:33
       1/0         SM-1T3/E3           ok                    15:55:24
      2            ISR4451/K9          ok                    15:57:33
       2/0         SM-1T3/E3           ok                    15:55:24
      R0           ISR4451/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 described in Installing Subpackages from a Consolidated Package.


        Step 1   show version
        Step 2   dir usbn:
        Step 3   show platform
        Step 4   mkdir bootflash:URL-to-directory-name
        Step 5   request platform software package expand fileusbn: package-name to URL-to-directory-name
        Step 6   reload
        Step 7   boot URL-to-directory-name/packages.conf
        Step 8   show version installed

        Installing a Firmware Subpackage

        Before You Begin

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

        You can install a firmware subpackage if the router has been configured using, for example, Managing and Configuring a Router to Run Using Individual Packages.

        Firmware subpackages 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 procedure below.


        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
           Command or ActionPurpose
          Step 1 show version


          Example:
          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:


          Example:
          Router# dir bootflash:
           

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

           
          Step 3 show platform


          Example:
          Router# show platform
          Chassis type: ISR4451/K9
           

          Checks the inventory.

          Also see the example in Installing Subpackages from a Consolidated Package.

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


          Example:
          Router# mkdir bootflash:mydir
           

          Creates a directory to save the expanded software image.

          You can use the same name as the image to name the directory.

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


          Example:
          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 save the image (URL-to-directory-name), which was created in the Step 4.

           
          Step 6 reload


          Example:
          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


          Example:
          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


          Example:
          Router# show version installed
          Package: Provisioning File, version: n/a, status: active
           

          Displays the version of the newly installed software.

           

          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]
           
          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: ISR4451/K9
           
          Slot Type State Insert time (ago)
          --------- ------------------- --------------------- -----------------
          0 ISR4451/K9 ok 15:57:33
          0/0 ISR4451-6X1GE ok 15:55:24
          1 ISR4451/K9 ok 15:57:33
          1/0 SM-1T3/E3 ok 15:55:24
          2 ISR4451/K9 ok 15:57:33
          2/0 SM-1T3/E3 ok 15:55:24
          R0 ISR4451/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
          

          Upgrading the Firmware on xDSL NIMs

          To upgrade the firmware on a xDSL Network Interface Module (NIM), perform these steps:

          Before You Begin

          When you boot the router in packages.conf mode with the Cisco IOS XE image (super package) during the installation period, you can upgrade or downgrade the firmware without reloading the router. You need to follow the steps described in Installing a Firmware Subpackage before proceeding with the firmware upgrade.

          If you do not boot the router in packages.conf mode with the Cisco IOS XE image, you need to follow the below prerequisites before proceeding with the firmware upgrade:

          • Copy the firmware subpackage (NIM firmware) into bootflash:/mydir.

          • Send a request to the platform software package expand file boot flash:/mydir/<IOS-XE image> to expand the super package.

          • Reload the hardware module subslot to boot the module with the new firmware.

          • Verify that the module is booted up with the new firmware using the show platform software subslot x/y module firmware command.

          SUMMARY STEPS

            1.    copy Cisco IOS XE image into bootflash: mydir.

            2.    request platform software package expand file bootflash:/mydir /<IOS-XE image to expand super package.

            3.    reload.

            4.    boot bootflash:mydir/ /packages.conf.

            5.    copy NIM firmware subpackage to the folder bootflash:mydir/.

            6.    request platform software package install rp 0 file bootflash:/mydir/<firmware subpackage>.

            7.    hw-module subslot x/y reload to boot the module with the new firmware.

            8.    show platform software subslot 0/2 module firmware to verify that the module is booted up with the new firmware.


          DETAILED STEPS
             Command or ActionPurpose
            Step 1 copy Cisco IOS XE image into bootflash: mydir.

            Example:
            Router# mkdir bootflash:mydir
             

            Creates a directory to save the expanded software image.

            You can use the same name as the image to name the directory.

             
            Step 2 request platform software package expand file bootflash:/mydir /<IOS-XE image to expand super package.


            Example:
            Router#  request platform software package expand file 
            bootflash:/mydir/isr4400-universalk9.03.14.00.S.155-1.S-std.SPA.bin
             

            Expands the platform software package to super package.

             
            Step 3 reload.


            Example:
            Router# reload
            rommon >
             

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

             
            Step 4 boot bootflash:mydir/ /packages.conf.


            Example:
            rommon 1 > boot bootflash:mydir/packages.conf
             

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

             
            Step 5 copy NIM firmware subpackage to the folder bootflash:mydir/.


            Example:
            Router#copy bootflash:isr4400-firmware_nim_xdsl.2014-11-17_11.05_39n.SSA.pkg
             bootflash:mydir/
             

            Copies the NIM firmware subpackage into bootflash:mydir.

             
            Step 6 request platform software package install rp 0 file bootflash:/mydir/<firmware 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
             

            Installs the software package.

             
            Step 7hw-module subslot x/y reload to boot the module with the new firmware.


            Example:
            Router#hw-module subslot 0/2 reload
             

            Reloads the hardware module subslot and boots the module with the new firmware.

             
            Step 8 show platform software subslot 0/2 module firmware to verify that the module is booted up with the new firmware.


            Example:
            Router# show platform software subslot 0/2 module firmware
            Pe
             

            Displays the version of the newly installed firmware.

             

            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/
            
            632738  -rw-        425288648  Dec 12 2014 09:16:42 +00:00  
            isr4400-universalk9.03.14.00.S.155-1.S-std.SPA.bin
            
            7451738112 bytes total (474025984 bytes free)
            Router#
            
            Router#request platform software package 
            expand file bootflash:/mydir/isr4400-universalk9.03.14.00.S.155-1.S-std.SPA.bin
            Verifying parameters
            Validating package type
            Copying package files
            SUCCESS: Finished expanding all-in-one software package.
            
            Router#reload
            Proceed with reload? [confirm]
            
            *Dec 12 09:26:09.874: %SYS-5-RELOAD: Reload requested by console. Reload Reason: 
            Reload Command.Dec 12 09:26:25.156 R0/0: %PMAN-5-EXITACTION: Process manager is exiting:
            process exit with reload chassis code 
            
            
            Initializing Hardware ...
            
            System integrity status: 00000610
             Rom image verified correctly
             System Bootstrap, Version 15.3(3r)S1, RELEASE SOFTWARE
            Copyright (c) 1994-2013  by cisco Systems, Inc.
            
             Current image running: Boot ROM0
            
            Last reset cause: LocalSoft
             Cisco ISR4451-X/K9 platform with 4194304 Kbytes of main memory
            
            
            rommon 1  boot bootflash:mydir/packages.conf
            
             File size is 0x000028f1
             Located mydir/packages.conf 
             Image size 
            10481 inode num 632741, bks cnt 3 blk size 8*512
             
            #
             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
            
             Package header rev 1 structure detected
             Calculating SHA-1 hash...done
             validate_package: SHA-1 hash:
             	calculated 8e966678:8afb08f4:8a88bb8f:fe591121:8bddf4b3
             	expected   8e966678:8afb08f4:8a88bb8f:fe591121:8bddf4b3
            
             RSA Signed RELEASE Image Signature Verification Successful.
             Package Load Test Latency : 3799 msec 
             Image validated
             Dec 12 09:28:50.338 R0/0: %FLASH_CHECK-3-DISK_QUOTA: Flash disk quota exceeded 
            [free space is 61864 kB] - Please clean up files on bootflash.  
            
                          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, ISR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 15.5(1)S, 
            RELEASE SOFTWARE (fc5)
            Technical Support: http://www.cisco.com/techsupport
            Copyright (c) 1986-2014 by Cisco Systems, Inc.
            Compiled Thu 20-Nov-14 18:28 by mcpre
            
            
            
            Cisco IOS-XE software, Copyright (c) 2005-2014 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.
            
            cisco ISR4451-X/K9 (2RU) processor with 1681388K/6147K bytes of memory.
            Processor board ID FTX1736AJUT
            2 Ethernet interfaces
            4 Gigabit Ethernet interfaces
            2 ATM interfaces
            32768K bytes of non-volatile configuration memory.
            4194304K bytes of physical memory.
            7393215K bytes of flash memory at bootflash:.
            
            Press RETURN to get started!
            
            *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
            *Dec 12 09:29:18.876: %IOSXE_OIR-6-ONLINECARD: Card (fp) online in slot F0
            *Dec 12 09:29:18.882: %IOSXE_OIR-6-INSSPA: SPA inserted in subslot 0/0
            *Dec 12 09:29:18.884: %IOSXE_OIR-6-INSSPA: SPA inserted in subslot 0/1
            *Dec 12 09:29:18.884: %IOSXE_OIR-6-INSSPA: SPA inserted in subslot 0/2
            *Dec 12 09:29:18.935: %SYS-5-RESTART: System restarted --
            Cisco IOS Software, ISR Software (X86_64_LINUX_IOSD-UNIVERSALK9-M), Version 15.5(1)S, 
            RELEASE SOFTWARE (fc5)
            Technical Support: http://www.cisco.com/techsupport
            Copyright (c) 1986-2014 by Cisco Systems, Inc.
            Compiled Thu 20-Nov-14 18:28 by mcpre
            *Dec 12 09:29:18.895: %SPA-3-ENVMON_NOT_MONITORED:iomd:  Environmental monitoring 
            is not enabled for ISR4451-X-4x1GE[0/0]
            *Dec 12 09:29:19.878: %LINK-5-CHANGED: Interface GigabitEthernet0, 
            
            changed state to administratively down
            *Dec 12 09:29:22.419: %SPA_OIR-6-ONLINECARD: SPA (ISR4451-X-4x1GE) online in subslot 0/0
            *Dec 12 09:29:22.610: %SYS-6-BOOTTIME: Time taken to reboot after reload =  194 seconds
            *Dec 12 09:29:24.354: %LINK-3-UPDOWN: Interface GigabitEthernet0/0/0, 
            changed state to down
            *Dec 12 09:29:24.415: %LINK-3-UPDOWN: Interface GigabitEthernet0/0/2, 
            changed state to down
            *Dec 12 09:29:24.417: %LINK-3-UPDOWN: Interface GigabitEthernet0/0/3, 
            changed state to down
            *Dec 12 09:29:30.919: %LINK-3-UPDOWN: Interface GigabitEthernet0/0/0, 
            changed state to up
            *Dec 12 09:29:30.925: %LINK-3-UPDOWN: Interface GigabitEthernet0/0/2,
             changed state to up
            *Dec 12 09:29:30.936: %LINK-3-UPDOWN: Interface GigabitEthernet0/0/3,
             changed state to up
            *Dec 12 09:29:31.919: %LINEPROTO-5-UPDOWN: Line protocol on Interface 
            GigabitEthernet0/0/0, changed state to up
            *Dec 12 09:29:31.930: %LINEPROTO-5-UPDOWN: Line protocol on
             Interface GigabitEthernet0/0/2, changed state to up
            *Dec 12 09:29:31.936: %LINEPROTO-5-UPDOWN: Line protocol on 
            Interface GigabitEthernet0/0/3, changed state to up
            *Dec 12 09:29:34.147: %SSH-5-ENABLED: SSH 1.99 has been enabled
            *Dec 12 09:30:29.152: %SPA_OIR-6-ONLINECARD: SPA (NIM-VA-B) online in subslot 0/1
            *Dec 12 09:30:29.470: %SPA_OIR-6-ONLINECARD: SPA (NIM-VAB-A) online in subslot 0/2
            *Dec 12 09:30:31.152: %LINK-3-UPDOWN: Interface Ethernet0/1/0, changed state to down
            *Dec 12 09:30:31.152: %LINK-3-UPDOWN: Interface ATM0/1/0, changed state to down
            *Dec 12 09:30:31.470: %LINK-3-UPDOWN: Interface Ethernet0/2/0, changed state to down
            *Dec 12 09:30:31.470: %LINK-3-UPDOWN: Interface ATM0/2/0, changed state to down
            *Dec 12 09:31:03.074: %CONTROLLER-5-UPDOWN: Controller VDSL 0/2/0, changed state to up
            *Dec 12 09:31:05.075: %LINK-3-UPDOWN: Interface Ethernet0/2/0, changed state to up
            *Dec 12 09:31:06.076: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet0/2/0, 
            changed state to up
            *Dec 12 09:31:12.559: %CONTROLLER-5-UPDOWN: Controller VDSL 0/1/0, changed state to up
            *Dec 12 09:31:20.188: %LINK-3-UPDOWN: Interface ATM0/1/0, changed state to up
            *Dec 12 09:31:21.188: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0/1/0, 
            changed state to up
            Router>
            Router>en
            Password: 
            Router#
            Router#show controller vdsl 0/2/0
            Controller VDSL 0/2/0 is UP
            
            Daemon Status:		UP 
            
            			XTU-R (DS)		XTU-C (US)
            Chip Vendor ID:		'BDCM'			 'BDCM'
            Chip Vendor Specific:   0x0000			 0xA41B
            Chip Vendor Country:    0xB500			 0xB500
            Modem Vendor ID:	'CSCO'			 '    '
            Modem Vendor Specific:  0x4602			 0x0000
            Modem Vendor Country:   0xB500			 0x0000
            Serial Number Near:     FOC18426DQ8 4451-X/K15.5(1)S   
            Serial Number Far:      
            Modem Version Near:     15.5(1)S
            Modem Version Far:      0xa41b
            
            Modem Status(L1):	TC Sync (Showtime!) 
            DSL Config Mode:	VDSL2 
            Trained Mode(L1):	G.993.2 (VDSL2) Profile 30a
            
            TC Mode:		PTM 
            Selftest Result:	0x00 
            DELT configuration:	disabled 
            DELT state:		not running 
            
            Failed full inits:	0
            Short inits:		0
            Failed short inits:	0
            
            Modem FW  Version:	4.14L.04
            Modem PHY Version:	A2pv6F039h.d24o_rc1
            
            Line 1:
            
            			XTU-R (DS)		XTU-C (US)
            Trellis:		 ON			 ON
            SRA: 			 disabled		 disabled
            SRA count: 		 0			 0
            Bit swap: 		 enabled		 enabled
            Bit swap count:		 9			 0
            Profile 30a: 		 enabled
            Line Attenuation:	  3.5 dB		  0.0 dB
            Signal Attenuation:	  0.0 dB		  0.0 dB
            Noise Margin:		 30.9 dB		12.4 dB
            Attainable Rate:	200000 kbits/s		 121186 kbits/s
            Actual Power:		13.3 dBm		 7.2 dBm
            Per Band Status:       	D1 	D2 	D3 	U0 	U1 	U2 	U3
            Line Attenuation(dB):   0.9	1.5	5.5	N/A	0.1	0.9	3.8	
            Signal Attenuation(dB): 0.8	1.5	5.5	N/A	0.0	0.2	3.2	
            Noise Margin(dB):       31.1	31.0	30.9	N/A	12.3	12.4	12.5	
            Total FECC:		0			 0
            Total ES:		0			 0
            Total SES:		0			 0
            Total LOSS:		0			 0
            Total UAS:		51			 51
            Total LPRS:		0			 0
            Total LOFS:		0			 0
            Total LOLS:		0			 0
            
            
             		  DS Channel1	  DS Channel0	US Channel1	  US Channel0
            Speed (kbps):		  NA	      100014		NA	      100014
            SRA Previous Speed:	  NA	           0		NA	           0
            Previous Speed:		  NA	           0		NA	           0
            Reed-Solomon EC:	  NA	           0		NA	           0
            CRC Errors:		  NA	           0		NA	           0
            Header Errors:		  NA	           0		NA	           0
            Interleave (ms):	  NA	        9.00		NA	        0.00
            Actual INP:		  NA	        4.00		NA	        0.00
            
            Training Log :	Stopped
            Training Log Filename :	flash:vdsllog.bin
            
            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#
            
            Router#request platform software package install rp 0 file 
            bootflash:mydir/isr4400-firmware_nim_xdsl.2014-11-17_11.05_39n.SSA.pkg
            --- Starting local lock acquisition on R0 ---
            Finished local lock acquisition on R0
            
            --- Starting file path checking ---
            Finished file path checking
            
            --- Starting image file verification ---
            Checking image file names
            Locating image files and validating name syntax
              Found isr4400-firmware_nim_xdsl.2014-11-17_11.05_39n.SSA.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
            Checking command output
            Constructing merge of running and candidate packages
            Checking if resulting candidate package set would be complete
            Finished candidate package set construction
            
            --- Starting ISSU compatiblity verficiation ---
            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 ISSU compatiblity verficiation
            
            --- Starting impact testing ---
            Checking operational impact of change
            Finished impact testing
            
            --- Starting list of software package changes ---
            Old files list:
              Removed isr4400-firmware_nim_xdsl.03.14.00.S.155-1.S-std.SPA.pkg
            New files list:
              Added isr4400-firmware_nim_xdsl.2014-11-17_11.05_39n.SSA.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
            Skipping soft links for firmware upgrade
            Skipping soft links for firmware upgrade
              Assembling Dynamic configuration files
              Applying interim IPC and database definitions
            rsync: getaddrinfo: cc2-0 873: Name or service not known rsync error: 
            error in socket IO (code 10) at /auto/mcpbuilds19/
            release/03.14.00.S/BLD-V03_14_00_S_FC5/contrib/rsync/clientserver.c(104) [sender=2.6.9]
            rsync: getaddrinfo: cc2-0 873: Name or service not known rsync error: 
            error in socket IO (code 10) at /auto/mcpbuilds19/
            release/03.14.00.S/BLD-V03_14_00_S_FC5/contrib/rsync/clientserver.c(104) [sender=2.6.9]
            rsync: getaddrinfo: cc2-0 873: Name or service not known rsync error: 
            error in socket IO (code 10) at /auto/mcpbuilds19
            /release/03.14.00.S/BLD-V03_14_00_S_FC5/contrib/rsync/clientserver.c(104) [sender=2.6.9]
              Replacing running software
              Replacing CLI software
              Restarting software
              Applying final IPC and database definitions
            rsync: getaddrinfo: cc2-0 873: Name or service not known rsync error: 
            error in socket IO (code 10) at /auto/mcpbuilds19/
            release/03.14.00.S/BLD-V03_14_00_S_FC5/contrib/rsync/clientserver.c(104) [sender=2.6.9]
              Generating software version information
              Notifying running software of updates
              Unblocking peer synchronization of operating information
            Unmounting old packages
            Cleaning temporary installation files
              Finished update running software
              
            SUCCESS: Finished installing software.
            Router#
            Router#show platform software subslot 0/2 module firmware
            Avg Load info
            -------------------------------------------
            1.83 1.78 1.44 3/45 607
            
            Kernel distribution info
            -------------------------------------------
            Linux version 3.4.11-rt19 (sapanwar@blr-atg-001) (gcc version 4.6.2 
            (Buildroot 2011.11) ) #3 SMP PREEMPT Fri Nov 7 09:26:19 IST 2014
            
            Module firmware versions
            -------------------------------------------
            Modem Fw Version: 4.14L.04
            Modem Phy Version: A2pv6F039h.d24o_rc1
            
            Boot Loader: Secondry
            -------------------------------------------
            Version: 1.1
            
            Modem Up time 
            -------------------------------------------
            0D 0H 25M 38S
            
            Router#
            
            Router#hw-module subslot 0/2 reload
            Proceed with reload of module? [confirm]
            Router#
            *Dec 12 09:55:59.645: %IOSXE_OIR-6-SOFT_RELOADSPA: SPA(NIM-VAB-A) 
            reloaded on subslot 0/2
            *Dec 12 09:55:59.646: %SPA_OIR-6-OFFLINECARD: SPA (NIM-VAB-A) offline in subslot 0/2
            *Dec 12 09:55:59.647: %CONTROLLER-5-UPDOWN: Controller VDSL 0/2/0, changed state to down
            *Dec 12 09:57:22.514: new extended attributes received from iomd(slot 0 bay 2 board 0)
            *Dec 12 09:57:22.514: %IOSXE_OIR-6-SOFT_RELOADSPA: SPA(NIM-VAB-A)
             reloaded on subslot 0/2
            *Dec 12 09:57:22.515: %SPA_OIR-6-OFFLINECARD: SPA (NIM-VAB-A) offline in subslot 0/2
            Router#
            Router#
            *Dec 12 09:58:35.471: %SPA_OIR-6-ONLINECARD: SPA (NIM-VAB-A) online in subslot 0/2
            *Dec 12 09:58:37.470: %LINK-3-UPDOWN: Interface Ethernet0/2/0, changed state to down
            *Dec 12 09:58:37.470: %LINK-3-UPDOWN: Interface ATM0/2/0, changed state to down
            Router#
            
            Router#show platform software subslot 0/2 module firmware
            Avg Load info
            -------------------------------------------
            0.84 0.23 0.08 1/45 598
            
            Kernel distribution info
            -------------------------------------------
            Linux version 3.4.11-rt19 (sapanwar@blr-atg-001) (gcc version 4.6.2 (Buildroot 2011.11) ) #6 SMP PREEMPT Mon Nov 17 10:51:41 IST 2014
            
            Module firmware versions
            -------------------------------------------
            Modem Fw Version: 4.14L.04
            Modem Phy Version: A2pv6F039n.d24o_rc1
            
            Boot Loader: Secondry
            -------------------------------------------
            Version: 1.1
            
            Modem Up time 
            -------------------------------------------
            0D 0H 0M 42S
            
            Router#