#|
Displays the previous version of software and that a package is present. Creates a directory to save the expanded software image. You can use the same name as the image to name the directory. Boots the consolidated package, by specifying the path and name of the provisioning file: packages. Displays the version of the newly installed software. The initial part of the example shows the consolidated package, isruniversalk9. This is a prerequisite step. The remaining part of the example shows the consolidated file, packages.
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 Pacakage section. Also see Overview section. During the upgrade, do not power cycle the device. The following example illustrates the boot process of a consolidated package:.
Obtain a consolidated package that contains your required firmware package and expand the package. 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. 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.
Boots the consolidated package by specifying the path and name of the provisioning file: packages. The initial part of the following example shows the consolidated package, isruniversalk9. When you boot the router in packages. You need to follow the steps described in Installing a Firmware Subpackage section before proceeding with the firmware upgrade.
If you do not boot the router in packages. Reload the hardware module subslot to boot the module with the new firmware. Expands the platform software package to super package. Boots the super package by specifying the path and name of the provisioning file: packages. Copies the NIM firmware subpackage into bootflash:mydir.
Reloads the hardware module subslot and boots the module with the new firmware. Displays the version of the newly installed firmware. The following example shows how to perform firmware upgrade in a router module:.
Skip to content Skip to search Skip to footer. Book Contents Book Contents. Find Matches in This Book. PDF - Complete Book 5. Updated: March 2, Chapter: Installing the Software. These are the two main methods to install the software: Managing and Configuring a Router to Run Using a Consolidated Package —This method allows for individual upgrade of subpackages and generally has reduced boot times compared to the method below.
Rommon Compatibility Matrix The following table provides information about Cisco Series Integrated Services Routers supported in each rommon release. Table 1. Note The rommon release Table 2. Table 3. 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. File Systems The following table provides a list of file systems that can be seen on the Cisco series routers.
Table 4. 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 5. Autogenerated Files File or Directory Description crashinfo files Crashinfo files may appear in the bootflash: file system.
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.
Flash Storage Subpackages are installed to local media storage, such as flash. 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. 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.
Note The console baud rate is set to after changing the confreg to 0x or 0x0. 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. Note The term npe stands for No Payload Encryption. Note The terms super package and image also refer to a consolidated package.
The following examples show how to obtain software authenticity information and internal details of a package: Displaying Digitally Signed Cisco Software Signature Information section Obtaining the Description of a Module or Consolidated Package section Many features within the consolidated package are contained in the ipbasek9 base package.
Technology Packages Technology packages contain software features within a consolidated package. The following is a list of technology packages: Note In Cisco Series Integrated Series Routers, although L2TPv2 sessions comes up without appxk9, you need the appxk9 license for the traffic to go through the sessions. Performance The performance feature, which allows for increased throughput, is enabled by the performance license. To exit global configuration mode, enter exit. You have to deregister and register back the device from the CSSM to execute the boost license command.
Device show running-config include throughput platform hardware throughput level boost Save the configuration and reload the device to enable Boost performance license. Boost Performance License in Smart License Mode This section describes the processes to activate and deactivate the Boost performance license from the device with two use-cases. Enable the boost performance license : Boot the device in Smart License mode. Return of license : The device is in the smart license mode with boost performance command configured.
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. The boost performance behavior is determined by the availability of the license in its Smart Account with Boost Performance activated in CSL: To configure the throughput level, perform the following steps and to upgrade the throughput level use the 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.
When boost performance is in use: Device platform hardware throughput level boost Device show license to ensure that Smart License and Boost performance licenses are enabled.
Remove Smart License Device no license smart enable Check the availability of the boost performance license, you may decide to retain the boost command. No extra reload is required. When boost performance is not in use : Use no platform hardware throughput level boost in the show running-configuration. To remove Smart License, use no license smart enable Check the availability of the boost permanent license to add the boost keyword. Boost Performance is activated and is in-use after reload Note If there is no permanent license available, then no boost performance command and functionality is likely to change.
Device configuration terminal To remove Smart License, use no license smart enable Device no license smart enable Device exist To remove Smart License, reload the router. Device configure terminal Enter yes to accept the end-user license agreement. How to Install and Upgrade the Software To install or upgrade the software, use one of the following methods to use the software from a consolidated package or an individual package. Router config boot system flash bootflash:isruniversalk9.
Building configuration File reception completed. All rights reserved. The software code licensed under GPL Version 2. 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.
By using this product you agree to comply with applicable laws and regulations. If you are unable to comply with U. A summary of U. Warning: the compile-time code checksum does not appear to be present.
Configuration register is 0x Managing and Configuring a Router to Run Using Individual Packages To choose between running individual packages or a consolidated package, see Installing the Software - Overview section.
If doing this, specify the separate server location in the configuration file, where the path to Protocol Pack files is configured. The configuration file provides the path for each downloaded Protocol Pack file stored on the server. Routers using Auto Update download the Protocol Pack files from these locations and install them automatically. The location of each Protocol Pack file is specified by combining the server address, base directory, and specific file path.
The "protocol-pack-server" section of the configuration file provides the address and base directory. A router using Auto Update would use this complete path to download the file from the server. Typical subsections include. The version number typically appears in the filename of the Protocol Pack installation file. For example, the following Protocol Pack In the configuration file, each line that specifies a Protocol Pack installation file location also indicates the matching NBAR software version.
When adding Protocol Pack installation file locations, be sure to specifiy the correct NBAR software version for the file. Download the correct Protocol Pack files for both and store them on the Auto Update server. The following configuration file parameters provide the default Protocol Pack Auto Update behavior. Schedule for the Auto Update upgrade interval. Routers using Auto Update check regularly for updates at the scheduled time.
The actual run time depends on the update-window option. Maintenance window in minutes for NBAR protocol pack auto-update to operate within. The maintenance window is scheduled according to the time configured by the schedule parameters. Because no schedule is configured, routers use the default schedule of checking daily at The example specifies one Protocol Pack file for each of four platform types.
The schedule section specifies the update schedule as weekly on Saturdays at AM. Routers using Auto Update check at this scheduled time for any available updates. Saturday is indicated by the weekly value of 6.
Download the new Protocol Pack installation files for the router models in the network using Auto Update. Protocol Pack installation files typically are compatible with a specific platform type running a specific Cisco IOS release.
Use the show ip nbar version command to display the NBAR software version. In the following example, the NBAR software version is If the NBAR software version has changed, check whether a more up-to-date compatible Protocol Pack is available for the release.
If so, download the new Protocol Pack installation file to provide to routers using Auto Update. Ensure that the new line in the configuration file is in the correct location, and that the specified NBAR2 version number matches the version number in the Protocol Pack filename. Enabling Protocol Pack Auto Update on a router requires:. Specifying the Protocol Pack Auto Update server to use, or ensuring that it has been specified already. Required only if the Protocol Pack Auto Update server has not already been specified.
Disables NBAR protocol pack auto update. Initiates a protocol pack update using the auto update mechanism. Displays the protocol pack auto update configuration, copied files, and statistics.
The following example shows the information provided in the output of this command. To configure local Protocol Pack Auto Update settings on a router, use the command sub-mode described here. Can anyone please give an idea if AX license does support all Data and Security features? I'm interested mainly in routing protocols. Let me know if you have additional concerns or need more reference. Send me an e-mail adawa cisco. Kind regards. Could you please help me find all the features provided by this free license.
Buy or Renew. Find A Community. Cisco Community. Join us in congratulating October's Spotlight Award Winners!
Turn on suggestions. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for. Search instead for. Did you mean:. All Community This category This board. Bilal Aslam.
0コメント