-
Cisco IOS XR System Management Configuration Guide, Release 3.5
-
Preface
-
Upgrading and Managing Cisco IOS XR Software
-
Creating a Backup Disk for the Cisco IOS XR Software
-
Software Entitlement on Cisco IOS XR Software
-
Process Placement on Cisco IOS XR Software
-
Implementing NTP on Cisco IOS XR Software
-
Implementing Physical and Virtual Terminals on Cisco IOS XR Software
-
Configuring Secure Domain Routers on Cisco IOS XR Software
-
Managing the Router Hardware
-
Implementing CDP on Cisco IOS XR Software
-
Implementing SNMP on Cisco IOS XR Software
-
Index
-
Table Of Contents
Upgrading and Managing Cisco IOS XR Software
Overview of Cisco IOS XR Software Packages
Package Installation Envelopes (PIE Files)
Summary of Cisco IOS XR Software Packages
Packages in the Cisco IOS XR Unicast Routing Core Bundle
Optional Cisco IOS XR Software Packages
Summary of Cisco IOS XR Software Bundles
PIE Filenames and Version Numbers
Filename Component Description
Information About Package Management
Copying the PIE File to a Local Storage Device or Network Server
Adding and Activating a Package with a Single Command
Upgrading and Downgrading Packages
Committing the Active Software Set
Rolling Back to a Previous Install Operation
Managing Software Operations in Secure Domain Routers (SDRs)
Managing Software Packages in a Multishelf System
Default Software Profile for New SDRs
Impact of Package Version Changes
Impact of Package Activation and Deactivation
Concurrent install Operations in an SDR
Delaying the Return of the CLI prompt
Displaying Installation Log Information
Activation and Deactivation Prerequisites
Obtaining and Placing Cisco IOS XR Software
Locating and Downloading Cisco IOS XR Software
Unpacking Software Bundles (tar Files)
Transferring Installation Files from a Network File Server to a Local Storage Device
Prepare for Software install Operations
Adding and Activating Packages
Committing the Active Package Set
Displaying the Committed Package Versions
Deactivating and Removing Cisco IOS XR Software Packages
Rolling Back to a Previous Software Set
Displaying the Active Packages Associated with a Rollback Point
Rolling Back to a Specific Rollback Point
Rolling Back to the Last Committed Package Set
Manageability Package Features
Session Border Controller Package
Upgrading and Managing Cisco IOS XR Software
The Cisco IOS XR software is divided into software packages so that you can select which features run on your router. This chapter describes the concepts and tasks necessary to add feature packages, upgrade the active set of packages, roll back to a previously active set of packages, and perform other related package management tasks.
Feature History for Upgrading and Managing Cisco IOS XR Software
Contents
•
Overview of Cisco IOS XR Software Packages
•
•
•
Overview of Cisco IOS XR Software Packages
The Cisco IOS XR software is divided into software packages so that you can select which features run on your router. Each package contains the components to perform a specific set of router functions, such as routing, security, or Modular Services card support. Bundles are groups of packages that can be downloaded as a set. For example, the Unicast Routing Core Bundle provides six packages for use on every router.
Adding a package to the router does not affect the operation of the router: it only copies the package files to a local storage device on the router, known as the boot device. (such as the internal flash disk0: on a Cisco CRS-1, or the compact flash drive on a Cisco XR 12000 Series Router). To make the package functional on the router, you must activate it for one or more cards.
To upgrade a package, you activate a newer version of the package. When the automatic compatibility checks have been passed, the new version is activated, and the old version is deactivated.
To downgrade a package, you activate an older version of the package. When the automatic compatibility checks have been passed, the older version is activated, and the newer version is deactivated.
This section contains the following information:
•
•
•
Note
Package Installation Envelopes (PIE Files)
Package Installation Envelopes (PIE), are nonbootable files that contain a single package or a set of packages (called a composite package or bundle). Because the files are nonbootable, they are used to add software package files to a running router.
PIE files have a pie extension. When a PIE file contains software for a specific bug fix, it is called a Software Maintenance Update (SMU).
Note
If the manageability Package Installation Envelopes (PIE) is installed, the entire SONET MIB history is available. If needed, you must configure SNMP and enable the SONET trap.
Summary of Cisco IOS XR Software Packages
Every router includes a basic set of required packages contained in the Cisco IOS XR Unicast Routing Core Bundle. Additional optional packages can be added and activated on the router to provide specific features. This section includes the following information:
•
•
•
Packages in the Cisco IOS XR Unicast Routing Core Bundle
Table 1 describes the packages contained in the Cisco IOS XR Unicast Routing Core Bundle.
The filename for this bundle is:
•
•
See the "Software Package Feature List" section for additional information on the specific features provided by each package.
Optional Cisco IOS XR Software Packages
Table 2 describes the optional packages that can be activated individually.
See the "Software Package Feature List" section for additional information on the specific features provided by each package.
Software Maintenance Updates
An SMU is a PIE file that contains fixes for a specific defect. A composite SMU is a PIE file that contains SMUs for more than one package. SMUs are added and activated using the same procedures as other PIE files. SMUs are created to respond to immediate issues and do not include new features. Typically, SMUs do not have a large impact on router operations. SMU versions are synchronized to the package major, minor, and maintenance versions they upgrade.
SMUs are not an alternative to maintenance releases. They provide quick resolution of immediate issues. All bugs fixed by SMUs are integrated into the maintenance releases. For information on available SMUs, contact Cisco Technical Support, as described in Obtaining Technical Assistance in the monthly What's New in Cisco Product Documentation.
Summary of Cisco IOS XR Software Bundles
The Cisco IOS XR Software packages are provided in the feature bundles listed in Table 3.
See the "Software Package Feature List" section for additional information on the specific features provided by each package.
PIE Filenames and Version Numbers
PIE filenames have two formats: one for composite-package PIEs (bundles) and one for single-package PIEs. A composite-package file is a PIE file that contains multiple packages.
Note
Table 4 and Table 5 show the filenames in Cisco CRS-1 and Cisco XR 12000 Series Routers.
Filename Component Description
The filename components for all packages are described in Table 6.
Table 6 Composite- and Single-Package Filename Components
comp
The "comp" prefix indicates that the file is a composite of multiple packages.
platform
Identifies the platform for which the software package is designed.
•
•
composite_name
Identifies a specific composite package.
•
package_type
Identifies the type of package the file supports (package_type applies only to single-package PIEs). Package types include:
•
•
•
•
•
•
•
•
•
•
•
•
major
Identifies the major release of this package.
•
•
•
minor
Identifies the minor release of this package.
•
–
–
•
•
maintenance
Identifies the maintenance release of this package.
•
•
•
ddts
SMUs only. Identifies a Distributed Defect Tracking System (DDTS) number that describes the problem this SMU addresses.
DDTS is the method used to track known bugs and the resolutions or workarounds for those issues.
Information About Package Management
This section describes the following concepts for managing Cisco IOS XR software packages:
•
–
–
–
–
–
•
•
•
•
•
•
•
Summary of Package Management
The general procedure for adding optional packages, upgrading a package or package set, or downgrading packages on the router is as follows:
1.
2.
3.
4.
Figure 1 illustrates key steps in the package management process.
Figure 1 Process to Add, Activate, and Commit Cisco IOS XR Software Packages
Copying the PIE File to a Local Storage Device or Network Server
To add an optional package or upgrade or downgrade a package, you must copy the appropriate PIE file to a local storage device or to a network file server to which the router has access.
If you need to store PIE files on the router, we recommended storing PIE files on the hard disk. Flash disk0 serves as the boot device for packages that have been added or activated on the system. Flash disk1 is used as a backup for disk0.
Tip
Adding Packages to an SDR
Use the install add command to unpack the package software files from a PIE file and copy them to the boot device (usually disk0).
•
•
•
Note
Activating Packages
Software packages remain inactive until activated with the install activate command.
After a package has been added to the SDR, use the install activate command to activate the package or SMUs for all valid cards. Information within the package is used to verify compatibility with the target cards and with the other active software. Actual activation is performed only after the package compatibility and application program interface (API) compatibility checks have been passed.
Note
Activating a Package for all Secure Domain Routers (SDRs)
To activate a package for all secure domain routers (SDRs) in the system, use the install activate command in administration EXEC mode.
Note
Activating a Package for a Single SDR
•
•
Adding and Activating a Package with a Single Command
To add and activate a package with a single command, use the install add command with the activate keyword.
•
•
Upgrading and Downgrading Packages
•
•
Actual activation is performed only after the compatibility checks have been passed.
Committing the Active Software Set
When a package is activated for one or more SDRs, it becomes part of the current running configuration for those SDRs. To make the package activation persistent across reloads, enter the install commit command. On startup, the designated secure domain router shelf controller (DSDRSC) of the SDR loads the committed software set.
•
•
•
Rolling Back to a Previous Install Operation
Although the term commit sounds final, the Cisco IOS XR software provides the flexibility to roll back the selected package set to previously saved package sets. Each time a package is activated or deactivated, a rollback point is created that defines the package set that is active after the package activation or deactivation. The software also creates a rollback point for the last committed package set. If you find that you prefer a previous package set over the currently active package set, you can use the install rollback command to make a previously active package set active again.
For more information, see the "Rolling Back to a Previous Software Set" section.
Managing Software Operations in Secure Domain Routers (SDRs)
In Release 3.4.0 and later release, most install operations can be performed for all SDRs, or for a specific SDR. Install operations, such as adding and activating software packages, are performed in either administration EXEC mode or EXEC mode.
•
•
For more information, review the other sections in this document. For example, see the "Summary of Cisco IOS XR Software Packages" section for an overview of adding and activating packages on a single SDR or on all SDRs. See also the following Cisco Systems documents:
•
•
Managing Software Packages in a Multishelf System
Software operations in a multishelf system are the same as in a single-shelf system: software packages are added and activated on one or more SDRs from either administration EXEC mode or from EXEC mode. The DSC keeps track of software operations for the entire system, while the DSDRSC of each SDR manages the software operations for that specific SDR. Install operations for a specific SDR can also be performed from administration EXEC mode for many features.
•
•
See the Software Package Management Commands on Cisco IOS XR Software module of Cisco IOS XR System Management Command Reference for more information on SDR support for each install command.
Note
Figure 2 DSC in a CRS-1/M-F1 Multishelf System
Default Software Profile for New SDRs
When a new non-owner SDR is created, the nodes assigned to that SDR are activated with the default software profile. In Release 3.4.0, the default profile is the active software set for the owner SDR. The owner SDR is the default SDR accessed by logging into the DSC of the system.
To view the default software profile, use the show install active summary command in administration EXEC mode. Any new nodes that are configured to become a part of an SDR will boot with the default software profile listed in the output of this command.
RP/0/0/CPU0:router(admin)# show install active summaryDefault Profile:SDRs:Ownersdr1Active Packages:disk0:c12k-sbc-3.3.0disk0:c12k-diags-3.3.0disk0:c12k-mgbl-3.3.0disk0:c12k-mcast-3.3.0disk0:c12k-mpls-3.3.0disk0:c12k-k9sec-3.3.0disk0:c12k-mini-3.3.0Upgrading Packages
To upgrade a package that is currently active on an SDR, add and activate a newer version of the same package (see Figure 3). The older version of the software package is deactivated automatically. These actions are permitted only after the package compatibility checks and API version compatibility checks have been passed.
Deactivated packages are not removed from the router. To remove inactive package files, use the install remove command. See the "Deactivating and Removing Cisco IOS XR Software Packages" section for more information.
Caution
Figure 3 Example of a Maintenance Release Package Upgrade
Downgrading Packages
To downgrade a software package, activate an older version on one or more cards for which that package is already active. The newer version of the same software package is deactivated automatically. These actions are performed only after the package compatibility checks and API version compatibility checks have been passed.
Deactivated packages are not removed from the router. To remove inactive package files, use the install remove command. See the "Deactivating and Removing Cisco IOS XR Software Packages" section for more information.
Impact of Package Version Changes
Each package version change has a different impact on the operation of the router, depending on the type of package and whether the upgrade is for a major, minor, or maintenance release. The following resources can provide more information on the impact of a package version change:
•
•
•
Impact of Package Activation and Deactivation
Activation or deactivation of a package can have an immediate impact on the system. The system can be affected in the following ways:
•
•
•
Note
•
•
•
•
•
Tip
Concurrent install Operations in an SDR
In Release 3.4.0 later release, multiple install operations can be performed in different SDRs at the same time, as long as they do not impact the same node. In other words, only one install command can run on a node at a time.
Install operations performed on an SDR impact only the nodes assigned to that SDR, so operations can be performed on both SDRs at the same time. If a user performs an install operation to one or more SDRs from administration EXEC mode, users of the effected SDRs can still perform additional install operations as long as they do not impact the same nodes.
If a second install operation impacts the same nodes as another incomplete instal operation, then the new CLI is rejected until the first operation is complete.
Delaying the Return of the CLI prompt
By default, the CLI prompt is returned to the screen before the installation operation is complete, which allows you to enter other noninstall commands. If additional installation requests are attempted before the first operation is complete, they are not run.
To delay the return of the CLI prompt until an installation operation is complete, enter the install command with the synchronous keyword. For example:
install add disk1:pie-file synchronous
install activate disk0:package synchronous
To determine if an install command is currently running, enter the show install request command.
Displaying Installation Log Information
The install log provides information on the history of the install operations. Each time an install operation is run, a number is assigned to that operation.
•
•
•
Tip
Examples
•
Displaying install log Entries: Example
The following example displays information for the install requests. Use the verbose keyword to display detailed information, including files changes, impact to processes, and impact to dynamic link libraries (DLL).
RP/0/RP0/CPU0:router(admin)# show install log verboseInstall operation 1 started by user 'labuser' at 17:48:51 UTC Sat Jun 03 2006.install add /disk1:hfr-diags-p.pie-PD34-06.06.07/disk1:hfr-k9sec-p.pie-PD34-06.06.07 /disk1:hfr-mcast-p.pie-PD34-06.06.07/disk1:hfr-mgbl-p.pie-PD34-06.06.07 /disk1:hfr-mpls-p.pie-PD34-06.06.07Install operation 1 completed successfully at 17:51:32 UTC Sat Jun 03 2006.Install logs:Install operation 1 'install add /disk1:hfr-diags-p.pie-PD34-06.06.07/disk1:hfr-k9sec-p.pie-PD34-06.06.07 /disk1:hfr-mcast-p.pie-PD34-06.06.07/disk1:hfr-mgbl-p.pie-PD34-06.06.07 /disk1:hfr-mpls-p.pie-PD34-06.06.07'started by user 'labuser' at 17:48:51 UTC Sat Jun 03 2006.Info: The following packages are now available to be activated:Info:Info: disk0:hfr-diags-3.4.0.1IInfo: disk0:hfr-k9sec-3.4.0.1IInfo: disk0:hfr-mcast-3.4.0.1IInfo: disk0:hfr-mgbl-3.4.0.1IInfo: disk0:hfr-mpls-3.4.0.1IInfo:Install operation 1 completed successfully at 17:51:32 UTC Sat Jun 03 2006.Install operation 2 started by user 'labuser' at 18:06:32 UTC Sat Jun 03 2006.install activate disk0:hfr-diags-3.4.0.1I disk0:hfr-k9sec-3.4.0.1Idisk0:hfr-mcast-3.4.0.1I disk0:hfr-mgbl-3.4.0.1I disk0:hfr-mpls-3.4.0.1IInstall operation 2 completed successfully at 18:07:48 UTC Sat Jun 03 2006.Summary:Install method: parallelSummary of changes on nodes 0/1/SP, 0/6/SP, 0/SM0/SP, 0/SM1/SP, 0/SM2/SP,0/SM3/SP:Activated: hfr-diags-3.4.0.1INo processes affectedSummary of changes on nodes 0/1/CPU0, 0/6/CPU0:Activated: hfr-diags-3.4.0.1Ihfr-mcast-3.4.0.1Ihfr-mpls-3.4.0.1I1 hfr-mpls processes affected (0 updated, 1 added, 0 removed, 0impacted)2 hfr-mcast processes affected (0 updated, 2 added, 0 removed, 0impacted)Summary of changes on nodes 0/RP0/CPU0, 0/RP1/CPU0:Activated: hfr-diags-3.4.0.1Ihfr-k9sec-3.4.0.1Ihfr-mcast-3.4.0.1Ihfr-mgbl-3.4.0.1Ihfr-mpls-3.4.0.1I6 hfr-mgbl processes affected (0 updated, 6 added, 0 removed, 0impacted)8 hfr-mpls processes affected (0 updated, 8 added, 0 removed, 0impacted)7 hfr-k9sec processes affected (0 updated, 7 added, 0 removed, 0impacted)14 hfr-mcast processes affected (0 updated, 14 added, 0 removed, 0impacted)Install logs:Install operation 2 'install activate disk0:hfr-diags-3.4.0.1Idisk0:hfr-k9sec-3.4.0.1I disk0:hfr-mcast-3.4.0.1I disk0:hfr-mgbl-3.4.0.1Idisk0:hfr-mpls-3.4.0.1I' started by user 'labuser' at 18:06:32 UTC Sat Jun03 2006.Info: The changes made to software configurations will not beInfo: persistent across system reloads. Use the command 'admin installInfo: commit' to make changes persistent.Info: Please verify that the system is consistent following theInfo: software change using the following commands:Info: show system verify--More--The following example displays information for a specific install request. Use the detail keyword to display additional information, including impact to processes and nodes impacted.
RP/0/RP0/CPU0:router(admin)# show install log 2 detailInstall operation 2 started by user 'labuser' at 18:06:32 UTC Sat Jun 03 2006.install activate disk0:hfr-diags-3.4.0.1I disk0:hfr-k9sec-3.4.0.1Idisk0:hfr-mcast-3.4.0.1I disk0:hfr-mgbl-3.4.0.1I disk0:hfr-mpls-3.4.0.1IInstall operation 2 completed successfully at 18:07:48 UTC Sat Jun 03 2006.Summary:Install method: parallelSummary of changes on nodes 0/1/SP, 0/6/SP, 0/SM0/SP, 0/SM1/SP, 0/SM2/SP,0/SM3/SP:Activated: hfr-diags-3.4.0.1INo processes affectedSummary of changes on nodes 0/1/CPU0, 0/6/CPU0:Activated: hfr-diags-3.4.0.1Ihfr-mcast-3.4.0.1Ihfr-mpls-3.4.0.1I1 hfr-mpls processes affected (0 updated, 1 added, 0 removed, 0impacted)2 hfr-mcast processes affected (0 updated, 2 added, 0 removed, 0impacted)Summary of changes on nodes 0/RP0/CPU0, 0/RP1/CPU0:Activated: hfr-diags-3.4.0.1Ihfr-k9sec-3.4.0.1Ihfr-mcast-3.4.0.1Ihfr-mgbl-3.4.0.1Ihfr-mpls-3.4.0.1I6 hfr-mgbl processes affected (0 updated, 6 added, 0 removed, 0impacted)8 hfr-mpls processes affected (0 updated, 8 added, 0 removed, 0impacted)7 hfr-k9sec processes affected (0 updated, 7 added, 0 removed, 0impacted)14 hfr-mcast processes affected (0 updated, 14 added, 0 removed, 0impacted)Install logs:Install operation 2 'install activate disk0:hfr-diags-3.4.0.1Idisk0:hfr-k9sec-3.4.0.1I disk0:hfr-mcast-3.4.0.1I disk0:hfr-mgbl-3.4.0.1Idisk0:hfr-mpls-3.4.0.1I' started by user 'labuser' at 18:06:32 UTC Sat Jun03 2006.Info: The changes made to software configurations will not beInfo: persistent across system reloads. Use the command 'admin installInfo: commit' to make changes persistent.Info: Please verify that the system is consistent following theInfo: software change using the following commands:Info: show system verifyInfo: install verifyInstall operation 2 completed successfully at 18:07:48 UTC Sat Jun 03 2006.Package Management Procedures
Review the concepts in the "Information About Package Management" section before performing the following tasks. The following sections describe package management tasks:
•
•
•
•
•
•
•
Activation and Deactivation Prerequisites
The following prerequisites must be met for a package to be activated or deactivated.
•
•
•
•
•
•
Activation is performed only after the package compatibility checks and API version compatibility checks have been passed. If a conflict is found, an on-screen error message is displayed.
While a software package is being activated, other requests are not allowed to run on any of the impacted nodes. Package activation is completed when a message similar to the following appears:
Install operation 2 completed successfully at 20:30:29 UTC Mon Nov 14 2005.. Each CLI install request is assigned a requestID, which can be used later to review the events.
Obtaining and Placing Cisco IOS XR Software
This section contains information to locate the available software packages, and transfer them either to a local storage device or to a network server. When this is done, the package or packages can be added and activated on one or more SDRs.
There are two primary ways to obtain Cisco IOS XR software packages.
•
•
The boot device is the local disk on the DSC where Cisco IOS XR software is added and activated. PIE files should not be stored on this boot device.
•
•
This section includes the following information:
•
•
•
Locating and Downloading Cisco IOS XR Software
To obtain Cisco IOS XR software, use the Cisco IOS XR Software Selector tool at the following web site:
http://www.cisco.com/pcgi-bin/Software/IOXPlanner/planner-tool/ioxplanner.cgi?
The Cisco IOS XR Software Selector tool allows you to browse for your software upgrade from a single interface. You can display and select software by package or bundle name, release, and platform. The tool also includes XML schemas. Choosing a platform, release, or software feature automatically limits the choices based on your selection, until you arrive at your preferred software.
After you select the package or bundle you want, platform, and release number, follow the instructions on the web page to download the software you have selected.
Unpacking Software Bundles (tar Files)
If the software you downloaded is in a tar file (which is denoted by a tar filename extension), you must unpack the file before the PIE files can be added to the router. Third-party software programs can unpack tar files and place the Cisco IOS XR software files in a folder you select. For more information on unpacking tar files, see the documentation for the third-party program.
Transferring Installation Files from a Network File Server to a Local Storage Device
If the Cisco IOS XR software PIE files are located on a remote TFTP, FTP, SFTP, or rcp server, you can copy the files to a local storage device such as disk1. When the PIE files are located on a local storage device, the software packages can be added and activated on the router from that storage device. Table 7 describes the supported server protocols, and the CLI syntax used copy files from each server type to the local storage device.
Tip
Note
The router commands listed in Table 8 show how to copy package files to the router using three types of file transfer protocols.
Table 9 describes the command variables for copying packages from a network server.
Table 9 Command Variables for Copying and Adding Packages from a Network Server
hostname_or_ipaddress
Host name or IP address of the server that stores the source file.
pie-name
Name of the PIE file (package). See the "Overview of Cisco IOS XR Software Packages" section for descriptions of the available packages.
username
Required for FTP and rcp only and must be a valid username on the FTP or rcp server.
password
Required for FTP only. If a password is not provided, the networking device accepts anonymous FTP.
directory-path
The specified directory should be a directory under the home directory of the user. In the rcp and FTP examples in Table 8, the file being downloaded is in a subdirectory called "images" in the home directory of the user "john."
Note
When the installation files have been transferred to a network file server or the router, you are ready to activate or upgrade the software.
Note
Prepare for Software install Operations
Before adding or activating Cisco IOS XR software:
•
•
•
•
•
This section includes instructions to prepare for software install operations.
Note
SUMMARY STEPS
1.
a.
b.
c.
2.
show install active [sdr sdr-name]
3.
show install pie-info device:package [brief | detail | verbose]
4.
install verify [sdr sdr-name]
5.
6.
a.
b.
7.
DETAILED STEPS
Step 1
Verify that the ROM Monitor version is correct:
admin
show diag
Example:RP/0/RP0/CPU0:router# admin
RP/0/RP0/CPU0:router(admin)# show diag
•
•
Note
•
Step 2
show install active [sdr sdr-name]
Example:RP/0/RP0/CPU0:router(admin)# show install active
•
–
–
–
Note
Step 3
show install pie-info device:package [brief | detail | verbose]
Example:RP/0/RP0/CPU0:router(admin)# show install pie-info disk1:/hfr-mcast-p.pie-3.3.30
Displays information imbedded in the package. The following keywords provide three levels of information:
•
•
•
Note
Step 4
install verify [sdr sdr-name]
Example:RP/0/RP0/CPU0:router(admin)# install verify
Verifies that there are no corrupted software files. The consistency of a previously installed software set is verified against the package file from which it originated. This command can be used as a debugging tool to verify the validity of the files that constitute the packages to determine if there are any corrupted files. This command is particularly useful when issued after the activation of a package or upgrading the Cisco IOS XR software to a major release.
To perform the command for a specific secure domain router (SDR), use the install verify command with the sdr keyword and sdr-name argument.
Note
Step 5
exit
Example:RP/0/RP0/CPU0:router(admin)# exit
Exits administration EXEC mode and returns to EXEC mode.
Step 6
show system verify start
show system verify [detail | report]
Example:RP/0/RP0/CPU0:router# show system verify start
RP/0/RP0/CPU0:router# show system verify
Verifies the system is stable. A variety of information is displayed including the memory and CPU usage, process status, protocol status, and other status information.
•
•
–
–
Note
Step 7
show clock
Example:RP/0/RP0/CPU0:router# show clock
Verifies that the system clock is correct. Software operations use certificates based on router clock times.
Examples
This section contains examples for the following subjects:
•
•
•
•
•
•
Verifying That the ROM Monitor Version Is Correct: Example
In the following example, the ROM Monitor software version is displayed in the "ROMMON:" field for each card.
Note
RP/0/RP0/CPU0:router# adminRP/0/RP0/CPU0:router(admin)# show diagNODE 0/1/SP : MSC(SP)MAIN: board type 500060800-25021-05 rev B0dev 079239S/N SAD09280BS9PCA: 73-7648-08 rev B0PID: CRS-MSCVID: V02CLEI: IPUCAC1BAAECI: 132502Board State : IOS XR RUNPLD: Motherboard: 0x0025, Processor: 0xda13, Power: N/AMONLIB: QNXFFS Monlib Version 3.0ROMMON: Version 1.38(20050525:193402) [CRS-1 ROMMON]PLIM 0/1/CPU0 : JACKET CARDMAIN: board type 580070800-23819-03 rev C0dev N/AS/N SAD094401CRPCA: 73-8982-06 rev C0PID: CRS1-SIP-800VID: V01CLEI: COUIAAMCAAECI: 134912Board State : IOS XR RUNPLD: Motherboard: 0x0025, Processor: 0xda13, Power: N/AMONLIB: QNXFFS Monlib Version 3.0ROMMON: Version 1.38(20050525:193559) [CRS-1 ROMMON]Interface port config: 0 PortsOptical reach type: UnknownConnector type: MT-P--More--Displaying the Active Software for All SDRs or for a Specific SDR: Example
The following example displays the active packages for all SDRs in the system. Use this information to determine if a software change is required:
RP/0/RP1/CPU0:router(admin)#show install active summaryDefault Profile:SDRs:OwnerCE1bActive Packages:disk0:hfr-diags-3.3.30disk0:hfr-mgbl-3.3.30disk0:hfr-k9sec-3.3.30disk0:comp-hfr-mini-3.3.30The following example displays a summary of active packages for a specific SDR:
RP/0/RP1/CPU0:router(admin)# show install active summary sdr ownerActive Packages:disk0:hfr-diags-3.3.30disk0:hfr-mgbl-3.3.30disk0:hfr-k9sec-3.3.30disk0:comp-hfr-mini-3.3.30Displaying Information About the Contents of a PIE File: Example
In the following example, information is displayed about the Multicast PIE. This command displays the expiry date of the package, the cards supported by the package, and other details. Use this information to verify the compatibility of the package with your system and other software packages.
Note
RP/0/RP1/CPU0:router(admin)# show install pie-info disk1:/hfr-mcast-p.pie-3.3.30 detailContents of pie file '/disk1:/hfr-mcast-p.pie-3.3.30':Expiry date : Jan 19, 2007 02:55:56 UTCUncompressed size : 9539249hfr-mcast-3.3.30hfr-mcast V3.3.30[1I] Multicast PackageVendor : Cisco SystemsDesc : Multicast PackageBuild : Built on Fri Feb 24 08:18:54 UTC 2006Source : By edde-bld1 in /vws/aga/production/3.3.30/hfr/workspace for c2.95.3-p8Card(s): RP, DRP, DRPSC, OC3-POS-4, OC12-POS, GE-3, OC12-POS-4, OC48-POS, E3-OC48-POS, E3-OC12-POS-4, E3-OC3-POS-16, E3-OC3CComponents in package hfr-mcast-3.3.30, package hfr-mcast:platform-ipv4-mrib V[fwd-33/9] HFR platform dependent DLL for MRIBdoc-hfr-mcast V[ci-33/5] Contains the man page documentation for HFR--MORE--Verifying That There are No Corrupted Software Files: Example
Verifies the consistency of the currently active software against the file from which it originated.
RP/0/RP0/CPU0:router(admin)# install verifyInstall operation 5 'install verify' started by user 'lab' at 14:06:40 UTCWed May 10 2006.The install operation will continue asynchronously.RP/0/RP0/CPU0:router(admin)#Info: This operation can take up to 2 minutes.Info: Please be patient.Info: Verify operation successful, no anomalies found.Info: Node 0/1/SPInfo: [SUCCESS] /bootflash/hfr-diags-3.3.30: Verification Successful.Info: [SUCCESS] /bootflash/hfr-admin-3.3.30: Verification Successful.Info: [SUCCESS] /bootflash/hfr-base-3.3.30: Verification Successful.Info: [SUCCESS] /bootflash/hfr-os-mbi-3.3.30: Verification Successful.Info: Node 0/1/CPU0Info: [SUCCESS] /bootflash/hfr-diags-3.3.30: Verification Successful.Info: [SUCCESS] /bootflash/hfr-mcast-3.3.30: Verification Successful.Info: [SUCCESS] /bootflash/hfr-mpls-3.3.30: Verification Successful.Info: [SUCCESS] /bootflash/hfr-lc-3.3.30: Verification Successful.Info: [SUCCESS] /bootflash/hfr-fwdg-3.3.30: Verification Successful.Info: [SUCCESS] /bootflash/hfr-admin-3.3.30: Verification Successful.Info: [SUCCESS] /bootflash/hfr-base-3.3.30: Verification Successful.Info: [SUCCESS] /bootflash/hfr-os-mbi-3.3.30: Verification Successful.Info: Node 0/6/SPInfo: [SUCCESS] /bootflash/hfr-diags-3.3.30: Verification Successful.Info: [SUCCESS] /bootflash/hfr-admin-3.3.30: Verification Successful.Info: [SUCCESS] /bootflash/hfr-base-3.3.30: Verification Successful.Info: [SUCCESS] /bootflash/hfr-os-mbi-3.3.30: Verification Successful.Info: Node 0/6/CPU0Info: [SUCCESS] /bootflash/hfr-diags-3.3.30: Verification Successful.Info: [SUCCESS] /bootflash/hfr-mcast-3.3.30: Verification Successful.Info: [SUCCESS] /bootflash/hfr-mpls-3.3.30: Verification Successful.Info: [SUCCESS] /bootflash/hfr-lc-3.3.30: Verification Successful.Info: [SUCCESS] /bootflash/hfr-fwdg-3.3.30: Verification Successful.Info: [SUCCESS] /bootflash/hfr-admin-3.3.30: Verification Successful.Info: [SUCCESS] /bootflash/hfr-base-3.3.30: Verification Successful.Info: [SUCCESS] /bootflash/hfr-os-mbi-3.3.30: Verification Successful.Info: Node 0/RP0/CPU0Info: [SUCCESS] /disk0/hfr-mgbl-3.3.30: Verification Successful.Info: [SUCCESS] /disk0/hfr-k9sec-3.3.30: Verification Successful.Info: [SUCCESS] /disk0/hfr-diags-3.3.30: Verification Successful.Info: [SUCCESS] /disk0/hfr-rout-3.3.30: Verification Successful.Info: [SUCCESS] /disk0/hfr-mcast-3.3.30: Verification Successful.Info: [SUCCESS] /disk0/hfr-mpls-3.3.30: Verification Successful.Info: [SUCCESS] /disk0/hfr-lc-3.3.30: Verification Successful.Info: [SUCCESS] /disk0/hfr-fwdg-3.3.30: Verification Successful.Info: [SUCCESS] /disk0/hfr-admin-3.3.30: Verification Successful.Info: [SUCCESS] /disk0/hfr-base-3.3.30: Verification Successful.Info: [SUCCESS] /disk0/hfr-os-mbi-3.3.30: Verification Successful.Info: Node 0/RP1/CPU0Info: [SUCCESS] /disk0/hfr-mgbl-3.3.30: Verification Successful.Info: [SUCCESS] /disk0/hfr-k9sec-3.3.30: Verification Successful.Info: [SUCCESS] /disk0/hfr-diags-3.3.30: Verification Successful.Info: [SUCCESS] /disk0/hfr-rout-3.3.30: Verification Successful.Info: [SUCCESS] /disk0/hfr-mcast-3.3.30: Verification Successful.Info: [SUCCESS] /disk0/hfr-mpls-3.3.30: Verification Successful.Info: [SUCCESS] /disk0/hfr-lc-3.3.30: Verification Successful.Info: [SUCCESS] /disk0/hfr-fwdg-3.3.30: Verification Successful.Info: [SUCCESS] /disk0/hfr-admin-3.3.30: Verification Successful.Info: [SUCCESS] /disk0/hfr-base-3.3.30: Verification Successful.Info: [SUCCESS] /disk0/hfr-os-mbi-3.3.30: Verification Successful.Info: Node 0/SM0/SPInfo: [SUCCESS] /bootflash/hfr-diags-3.3.30: Verification Successful.Info: [SUCCESS] /bootflash/hfr-admin-3.3.30: Verification Successful.Info: [SUCCESS] /bootflash/hfr-base-3.3.30: Verification Successful.Info: [SUCCESS] /bootflash/hfr-os-mbi-3.3.30: Verification Successful.Info: Node 0/SM1/SPInfo: [SUCCESS] /bootflash/hfr-diags-3.3.30: Verification Successful.Info: [SUCCESS] /bootflash/hfr-admin-3.3.30: Verification Successful.Info: [SUCCESS] /bootflash/hfr-base-3.3.30: Verification Successful.Info: [SUCCESS] /bootflash/hfr-os-mbi-3.3.30: Verification Successful.Info: Node 0/SM2/SPInfo: [SUCCESS] /bootflash/hfr-diags-3.3.30: Verification Successful.Info: [SUCCESS] /bootflash/hfr-admin-3.3.30: Verification Successful.Info: [SUCCESS] /bootflash/hfr-base-3.3.30: Verification Successful.Info: [SUCCESS] /bootflash/hfr-os-mbi-3.3.30: Verification Successful.Info: Node 0/SM3/SPInfo: [SUCCESS] /bootflash/hfr-diags-3.3.30: Verification Successful.Info: [SUCCESS] /bootflash/hfr-admin-3.3.30: Verification Successful.Info: [SUCCESS] /bootflash/hfr-base-3.3.30: Verification Successful.Info: [SUCCESS] /bootflash/hfr-os-mbi-3.3.30: Verification Successful.Install operation 5 completed successfully at 14:12:21 UTC Wed May 10 2006.Verifying the Current System Status: Example
The following example shows how to prepare for system verification:
RP/0/RP1/CPU0:router# show system verify startStoring initial router status ...done.The following example shows output from running the show system verify command:
Note
RP/0/RP1/CPU0:router# show system verifyGetting current router status ...System Verification Report==========================- Verifying Memory Usage- Verified Memory Usage : [OK]- Verifying CPU Usage- Verified CPU Usage : [OK]- Verifying Blocked Processes- Verified Blocked Processes : [OK]- Verifying Aborted Processes- Verified Aborted Processes : [OK]- Verifying Crashed Processes- Verified Crashed Processes : [OK]- Verifying LC Status- Verified LC Status : [OK]- Verifying QNET StatusUnable to get current LC status info- Verified QNET Status : [FAIL]- Verifying GSP Fabric Status- Verified GSP Fabric Status : [OK]- Verifying GSP Ethernet Statusgsp WARNING messages for routerCurrent set of gsp ping nodes does not match initial set of nodes- Verified GSP Ethernet Status : [WARNING]- Verifying POS interface Status- Verified POS interface Status : [OK]- Verifying TenGigE interface Status- Verified TenGigE interface Status : [OK]- Verifying TCP statistics- Verified TCP statistics : [OK]- Verifying UDP statisticstcp_udp_raw WARNING messages for routerUDP Packets sent has not increased during this period.- Verified UDP statistics : [WARNING]- Verifying RAW statistics- Verified RAW statistics : [OK]- Verifying RIB Status- Verified RIB Status : [OK]- Verifying CEF Status- Verified CEF Status : [OK]- Verifying CEF Consistency Status- Verified CEF Consistency Status : [OK]- Verifying BGP Status- Verified BGP Status : [OK]- Verifying ISIS Status- Verified ISIS Status : [OK]- Verifying OSPF Status- Verified OSPF Status : [OK]- Verifying Syslog Messages- Verified Syslog Messages : [OK]System may not be stable. Please look into WARNING messages.Verifying That the System Clock Is Correct: Example
The following example displays the current system clock setting:
RP/0/RP0/CPU0:router# show clock17:30:47.718 UTC Sat Apr 15 2006Adding and Activating Packages
The procedure in this section describes how to upgrade or add Cisco IOS XR software PIE files that are stored on a local storage device, such as flash disk1, or on a remote TFTP, FTP, SFTP, or rcp server. The PIE software file can include any of the following:
•
•
•
When you need to add and activate two or more of the preceding package types, you should add and activate them in the order listed above.
Note
For an description of the software management process, see Information About Package Management.
These instructions are also used to downgrade software packages. See Downgrading Packages for more information.
Note
Prerequisites
Before upgrading or adding packages from flash disk1, verify that the following prerequisites have been met:
•
•
•
•
SUMMARY STEPS
1.
2.
3.
4.
install add device:pie-file [sdr sdr-name] [activate]
or
install add tftp://hostname_or_ipaddress/directory-path/pie-file [sdr sdr-name] [activate]
or
install add ftp://username:password@hostname_or_ipaddress/directory-path/pie-file [sdr sdr-name] [activate]
or
install add rcp://username@hostname_or_ipaddress/directory-path/pie-file [sdr sdr-name] [activate]
5.
6.
7.
8.
9.
10.
11.
a.
b.
12.
a.
b.
13.
DETAILED STEPS
Step 1
Connect to the console port and log in.
Establishes a CLI management session with the SDR.
•
•
For more information on console connections, see Cisco IOS XR Getting Started Guide.
Step 2
dir device:
Example:RP/0/RP0/CPU0:router# dir disk1:
(Optional) Displays the package files that are available for package upgrades and additions.
•
•
Step 3
admin
Example:RP/0/RP0/CPU0:router# admin
(Optional) Enters administration EXEC mode.
•
•
Note
Step 4
install add device:pie-file [sdr sdr-name] [activate]
or
install add tftp://hostname_or_ipaddress/directory-path/pi e-file [sdr sdr-name] [activate]
or
install add ftp://username:password@hostname_or_ipaddress/
directory-path/pie-file [sdr sdr-name] [activate]or
install add rcp://username@hostname_or_ipaddress/directory -path/
pie-file [sdr sdr-name] [activate]Example:RP/0/RP0/CPU0:router(admin)# install add disk1:c12k-mgbl.pie-3.3.30.1i
or
RP/0/RP0/CPU0:router(admin)# install add tftp://10.1.1.1/images/hfr-k9sec-p.pie
or
RP/0/RP0/CPU0:router(admin)# install add ftp://john:secret@10.1.1.1/images/hfr-k9sec-p. pie
or
RP/0/RP0/CPU0:router(admin)# install add rcp://john@10.1.1.1/images/gsr-k9sec-p.pie
Unpacks a PIE file from local storage device or network server and adds the package files to the boot device of the router. The boot device is located on the DSC.
The following arguments are used when adding a package from a PIE file located on a network server:
•
•
•
•
•
•
•
•
Note
Step 5
show install inactive summary [sdr sdr-name]
Example:RP/0/RP0/CPU0:router(admin)# show install inactive summary
(Optional) Displays the inactive packages on the router. Verify that the package added in the previous step appears in the display.
•
•
Step 6
install activate device:package [test] [sdr sdr-name] [location nodeID]
Example:RP/0/RP0/CPU0:router(admin)# install activate disk0:c12k-mgbl-3.3.30
Activates a package that was added to one or more SDRs.
•
•
•
•
•
•
Note
TipStep 7
Repeat Steps 4 through 6 until all packages are activated.
Activates additional packages as required.
Step 8
show install active summary [sdr sdr-name]
Example:RP/0/RP0/CPU0:router# show install active
(Optional) Displays all active packages. Use this display to determine if the correct packages are active.
•
Step 9
Verify that there are no corrupted software files.
install verify [sdr sdr-name]
Example:RP/0/RP0/CPU0:router(admin)# install verify
(Optional) Verifies the consistency of a installed software set with the package file from which it originated. This command can be used as a debugging tool to verify the validity of the files that constitute the packages to determine if there are any corrupted files. This command is particularly useful when issued after the activation of a package or upgrading the Cisco IOS XR software to a major release.
To perform the command for a specific secure domain router (SDR) in administration EXEC mode, use the sdr sdr-name keyword and argument.
Note
Step 10
exit
Example:RP/0/RP0/CPU0:router(admin)# exit
(Optional) Exits administration EXEC mode and returns to EXEC mode.
Use this command only if you performed the install operations in administration EXEC mode.
Step 11
show system verify start
show system verify [detail | report]
Example:RP/0/RP0/CPU0:router# show system verify start
RP/0/RP0/CPU0:router# show system verify
(Optional) Verifies the system is stable. A variety of information is displayed, including the memory and CPU usage, process status, protocol status, and other status information. Use this information to verify that the system is stable. Enter this command in EXEC mode for each SDR impacted by the install operation.
•
•
–
–
Note
Step 12
admin
install commit [sdr sdr-name]
Example:RP/0/RP0/CPU0:router(admin)# install commit
(Optional) Commits the current set of packages for an SDR or for all SDRs so that these packages are used if the router is restarted.
•
•
•
For more information, see the "Committing the Active Package Set" section.
Step 13
Upgrade the field-programmable device (FPD) software, if necessary.
Whenever a Cisco IOS XR software image is released that supports SPAs and SIPs, a companion SPA or SIP FPD image is bundled with the Cisco IOS XR software release. However, the FPD image is not automatically upgraded. You must manually upgrade the FPD image running on the SPA or SIP when you upgrade the Cisco IOS XR software image. FPD versions must be compatible with the Cisco IOS XR software that is running on the router.
For information on FRDs, including instructions to upgrade FRD images, refer to the Upgrading FPD Cisco IOS XR Software module of Cisco IOS XR Interface and Hardware Component Configuration Guide.
Examples
This section contains examples for the following subjects:
•
•
Adding a Package: Example
The following example shows how to add the contents of a PIE file on disk1 to the boot device. Because the software package is added to the boot device by default, it is not necessary to specify the destination device in the CLI.
RP/0/RP0/CPU0:router(admin)# install add disk1:hfr-mpls-p.pie-3.3.30 synchronousInstall operation 4 'install add /disk1:hfr-mpls.pie synchronous' started by user'cisco' at 18:10:18 UTC Sat Apr 08 2006.Info: The following package is now available to be activated:Info:Info: disk0:hfr-mpls-3.3.80Info:Install operation 4 completed successfully at 18:14:11 UTC Sat Apr 08 2006.The following example shows how to add the contents of a PIE file on a TFTP server to the boot device:
RP/0/RP0/CPU0:router(admin)# install add tftp://209.165.201.1/hfr-mpls.pie synchronousInstall operation 4 'install add /tftp://209.165.201.1/hfr-mpls.pie synchronous' started by user 'cisco' at 18:16:18 UTC Sat Apr 08 2006.Info: The following package is now available to be activated:Info:Info: disk0:hfr-mpls-3.3.80Info:Install operation 4 completed successfully at 18:19:10 UTC Sat Apr 08 2006.Activating a Package: Example
The following example shows the activation of the MPLS package on a Cisco CRS-1 router. The package is activated on the boot device disk0.
RP/0/RP0/CPU0:router(admin)# install activate disk0:hfr-mpls-3.3.30 synchronousInstall operation 15 'install activate disk0:hfr-mpls-3.3.30 synchronous'started by user 'lab' at 19:15:33 UTC Sat Apr 08 2006.Info: The changes made to software configurations will not be persistentInfo: across system reloads. Use the command 'admin install commit' to makeInfo: changes persistent.Info: Please verify that the system is consistent following the softwareInfo: change using the following commands:Info: show system verifyInfo: install verifyInstall operation 5 completed successfully at 19:16:18 UTC Sat Apr 08 2006.Adding and Activating a Package from an FTP File Server with One Command: Example
To add and activate a package with a single command, enter the install add command with the activate keyword. In the following example, the Manageability PIE located on disk1 is verified, unpacked, and added to the boot device disk0. Because this operation is performed in administration EXEC mode, the package is activated for all SDRs in the system.
RP/0/RP0/CPU0:router(admin)# install add disk1:hfr-mgbl-p.pie-3.3.30 activateInstall operation 4 'install add /disk1:hfr-mgbl-p.pie-3.3.30 activate' startedby user 'cisco' at 07:58:56 UTC Wed Mar 01 2006.The install operation will continue asynchronously.:router(admin)#Part 1 of 2 (add software): StartedInfo: The following package is now available to be activated:Info:Info: disk0:hfr-mgbl-3.3.30Info:Part 1 of 2 (add software): Completed successfullyPart 2 of 2 (activate software): StartedInfo: The changes made to software configurations will not be persistent acrosssystem reloads. Use the command 'admin installInfo: commit' to make changes persistent.Info: Please verify that the system is consistent following the software changeusing the following commands:Info: show system verifyInfo: install verifyPart 2 of 2 (activate software): Completed successfullyPart 1 of 2 (add software): Completed successfullyPart 2 of 2 (activate software): Completed successfullyInstall operation 4 completed successfully at 08:00:24 UTC Wed Mar 01 2006.Displaying the Active Packages: Example
The following example displays a summary of the active packages on a router. Because this operation is performed in administration EXEC mode, the active packages for all SDRs are displayed.
RP/0/RP0/CPU0:router(admin)# show install active summaryDefault Profile:SDRs:OwnerCE1bActive Packages:Active Packages:disk0:hfr-pagent-3.5.0.1Idisk0:hfr-fpd-3.5.0.1Idisk0:hfr-firewall-3.5.0.1Idisk0:hfr-doc-3.5.0.1Idisk0:hfr-diags-3.5.0.1Idisk0:hfr-mgbl-3.5.0.1Idisk0:hfr-mcast-3.5.0.1Idisk0:hfr-mpls-3.5.0.1Idisk0:hfr-k9sec-3.5.0.1Idisk0:comp-hfr-mini-3.5.0.1IYou can also display the active packages for a specific SDR, or for a specific node. Enter the show install active command in EXEC mode, or use the sdr option in administration EXEC mode, as shown in the following example:
RP/0/RP0/CPU0:router(admin)# show install active sdr ownerSecure Domain Router: OwnerNode 0/1/CPU0 [LC] [SDR: Owner]Boot Device: mem:Boot Image: /disk0/hfr-os-mbi-3.5.0.1I/lc/mbihfr-lc.vmActive Packages:disk0:hfr-pagent-3.5.0.1Idisk0:hfr-fpd-3.5.0.1Idisk0:hfr-firewall-3.5.0.1Idisk0:hfr-diags-3.5.0.1Idisk0:hfr-mcast-3.5.0.1Idisk0:hfr-mpls-3.5.0.1Idisk0:comp-hfr-mini-3.5.0.1INode 0/6/CPU0 [LC] [SDR: Owner]Boot Device: mem:Boot Image: /disk0/hfr-os-mbi-3.5.0.1I/lc/mbihfr-lc.vmActive Packages:disk0:hfr-pagent-3.5.0.1Idisk0:hfr-fpd-3.5.0.1Idisk0:hfr-firewall-3.5.0.1Idisk0:hfr-diags-3.5.0.1Idisk0:hfr-mcast-3.5.0.1Idisk0:hfr-mpls-3.5.0.1Idisk0:comp-hfr-mini-3.5.0.1INode 0/RP0/CPU0 [RP] [SDR: Owner]Boot Device: disk0:Boot Image: /disk0/hfr-os-mbi-3.5.0.1I/mbihfr-rp.vmActive Packages:disk0:hfr-pagent-3.5.0.1Idisk0:hfr-fpd-3.5.0.1Idisk0:hfr-firewall-3.5.0.1Idisk0:hfr-doc-3.5.0.1Idisk0:hfr-diags-3.5.0.1Idisk0:hfr-mgbl-3.5.0.1Idisk0:hfr-mcast-3.5.0.1Idisk0:hfr-mpls-3.5.0.1Idisk0:hfr-k9sec-3.5.0.1Idisk0:comp-hfr-mini-3.5.0.1ICommitting the Active Package Set
When a package is activated, it becomes part of the current running configuration. To make the package activation persistent across SDR or system-wide reloads, enter the install commit command. On startup, the DSDRSC of the SDR loads this committed software set.
Note
If the system is reloaded before the current active software is committed with the install commit command, the previously committed software set is used.
•
•
Tip
In the following example, the active software packages are committed on all SDRs in a Cisco CRS-1 router:
RP/0/RP0/CPU0:router(admin)# install commitInstall operation 16 'install commit' started by user 'lab' at 19:18:58 UTCSat Apr 08 2006.Install operation 16 completed successfully at 19:19:01 UTC Sat Apr 08 2006.Displaying the Committed Package Versions
To view which packages are committed, enter the show install committed command using the following syntax:
Administration EXEC Mode
show install committed [sdr sdr-name | location node-id] [summary [sdr sdr-name]] [detail [sdr sdr-name | location node-id]] [verbose [sdr sdr-name | location node-id]]
EXEC Mode
show install committed [location node-id] [summary] [detail [location node-id]] [verbose [location node-id]]
Note
In the following example, the committed packages are shown for the owner SDR:
RP/0/RP0/CPU0:router# show install committedSecure Domain Router: OwnerNode 0/1/SP [SP] [SDR: Owner]Boot Image: /disk0/hfr-os-mbi-3.3.30/sp/mbihfr-sp.vmCommitted Packages:disk0:hfr-diags-3.3.30disk0:comp-hfr-mini-3.3.30Node 0/1/CPU0 [LC] [SDR: Owner]Boot Image: /disk0/hfr-os-mbi-3.3.30/lc/mbihfr-lc.vmCommitted Packages:disk0:hfr-diags-3.3.30disk0:comp-hfr-mini-3.3.30Node 0/6/SP [SP] [SDR: Owner]Boot Image: /disk0/hfr-os-mbi-3.3.30/sp/mbihfr-sp.vmCommitted Packages:disk0:hfr-diags-3.3.30disk0:comp-hfr-mini-3.3.30Node 0/6/CPU0 [LC] [SDR: Owner]Boot Image: /disk0/hfr-os-mbi-3.3.30/lc/mbihfr-lc.vmCommitted Packages:--More--As with the show install active command, the show install committed command may display a composite package that represents all packages in the Cisco IOS XR Unicast Routing Core Bundle.
Deactivating and Removing Cisco IOS XR Software Packages
When a package is deactivated, it is no longer active on the SDR, but the package files remain on the boot disk. The package files can be reactivated later, or they can be removed from the disk.
A package is deactivated using the following methods:
•
•
•
Restrictions
The following are the restrictions when deactivating and removing Cisco IOS XR Software packages:
•
•
•
•
•
•
•
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
a.
b.
8.
a.
b.
9.
DETAILED STEPS
Step 1
Connect to the console port and log in.
Establishes a CLI management session with the SDR.
•
•
For more information on console connections, see Cisco IOS XR Getting Started Guide.
Step 2
admin
Example:RP/0/RP0/CPU0:router# admin
(Optional) Enters administration EXEC mode.
•
•
Step 3
install deactivate device:package [sdr sdr-name] [location node-id] [test]
Example:RP/0/RP1/CPU0:router(admin)# install deactivate disk0:hfr-diags-3.3.30
Deactivates a package for one or more SDRs.
Deactivating a Package for all SDRs
To deactivate a package for all SDRs in the system, use the install deactivate command in administration EXEC mode.
Deactivating a Package for a Specific SDR
•
•
Deactivating a Package for a Specific Node
•
Notes
•
•
Step 4
show install inactive summary [sdr sdr-name]
Example:RP/0/RP0/CPU0:router(admin)# show install inactive summary
(Optional) Displays the inactive packages on the router.
•
Step 5
Verify that there are no corrupted software files.
install verify [sdr sdr-name]
Example:RP/0/RP1/CPU0:router(admin)# install verify
(Optional) Verifies the consistency of a installed software set with the package file from which it originated. This command can be used as a debugging tool to verify the validity of the files that constitute the packages to determine if there are any corrupted files. This command is particularly useful when issued after the activation of a package or upgrading the Cisco IOS XR software to a major release.
To perform the command for a SDR, use the install verify command with the sdr keyword and sdr-name argument.
Note
Step 6
exit
Example:RP/0/RP1/CPU0:router(admin)# exit
(Optional) Exits administration EXEC mode and returns to EXEC mode.
Use this command only if you performed the install operations in administration EXEC mode.
Step 7
Verify the system is stable:
show system verify start
show system verify [detail | report]
Example:RP/0/RP1/CPU0:router# show system verify start
RP/0/RP1/CPU0:router# show system verify
(Optional) Displays a variety of information including the memory and CPU usage, process status, protocol status, and other status information. Use this information to verify that the SDR is stable.
•
•
–
–
Note
Step 8
admin
install commit
Example:RP/0/RP1/CPU0:router(admin)# install commit
(Optional) Commits the current set of packages so that these packages are used if the router is restarted. Packages can be removed only if the deactivation operation is committed.
Note
For more information, see the "Committing the Active Package Set" section.
Step 9
install remove {[device:package] [inactive [device]]} [test]
Example:RP/0/RP1/CPU0:router(admin)# install remove disk0:hfr-diags-3.3.30
(Optional) Removes the inactive package.
•
•
•
•
•
Command Modes
•
•
•
Examples
In the following example, a package is deactivated from all SDRs in a router. The changes are committed and the inactive package is removed from the router:
•
•
•
Deactivating the Package
RP/0/RP0/CPU0:router(admin)# install deactivate disk0:hfr-diags-3.3.30Install operation 27 'install deactivate disk0:hfr-diags-3.3.30' started byuser 'lab' at 23:29:37 UTC Sat Apr 15 2006.The install operation will continue asynchronously.RP/0/RP1/CPU0:router(admin)#Info: The changes made to software configurationInfo: across system reloads. Use the command 'admin install commit' to makeInfo: changes persistent.Info: Please verify that the system is consistent following the softwareInfo: change using the following commands:Info: show system verifyInfo: install verifyInstall operation 27 completed successfully at 23:30:22 UTC Sat Apr 15 2006.Committing the Active Software Set
RP/0/RP0/CPU0:router(admin)# install commitInstall operation 29 'install commit' started by user 'lab' at 23:39:21 UTCSat Apr 15 2006.Install operation 29 completed successfully at 23:39:24 UTC Sat Apr 15 2006.Displaying the Inactive Packages
RP/0/RP0/CPU0:router(admin)# show install inactive summaryDefault Profile:SDRs:OwnerInactive Packages:disk0:hfr-diags-3.3.30Removing the Inactive Package from the Router
The following example shows how to remove an inactive package. In this example, the operation is run in test mode. The operation is confirmed and the package is removed.
RP/0/RP0/CPU0:router(admin)# install remove disk0:hfr-diags-3.3.30 testInstall operation 30 'install remove disk0:hfr-diags-3.3.30 test' started byuser 'lab' at 23:40:22 UTC Sat Apr 15 2006.Warning: No changes will occur due to 'test' option being specified. TheWarning: following is the predicted output for this install command.Info: This operation will remove the following package:Info: disk0:hfr-diags-3.3.30Info: After this install remove the following install rollback points willInfo: no longer be reachable, as the required packages will not be present:Info: 4, 9, 10, 14, 15, 17, 18Proceed with removing these packages? [confirm] yThe install operation will continue asynchronously.Install operation 30 completed successfully at 23.Rolling Back to a Previous Software Set
The Cisco IOS XR software allows you to roll back one or more SDRs to a previous committed or uncommitted software set. Use the show install rollback ? command to view the available rollback points, and the install rollback to command to roll back the SDR to a previous software set. You can also use the install rollback to committed command to roll back to the most recent committed software set.
Note
Review the following sections for more information:
•
•
•
Displaying Rollback Points
A rollback point is created every time a software package is activated, deactivated, or committed. Use the show install rollback ? command to display the eligible rollback points:
RP/0/RP0/CPU0:router# adminRP/0/RP0/CPU0:router(admin)# show install rollback ?RP/0/RP0/CPU0:router(admin)#show install rollback ?0 ID of the rollback point to show package information for2 ID of the rollback point to show package information forIn this example, the rollback points are 0 and 2. The rollback point with the highest number is the current software point. For example, if the last install operation was operation 3 (activating the MPLS package) then the highest rollback point is 3, which is the same as the current software (MPLS package activated).
Command Modes
Enter the command in administration EXEC mode to display rollback points for all SDRs. Enter the command in EXEC mode to display rollback points for the SDR to which you are currently logged in. You can also display rollback points for a specific SDR in administration EXEC mode by using the sdr sdr-name keyword and argument.
Displaying the Active Packages Associated with a Rollback Point
To display the active packages associated with a rollback point, use the show install rollback command with the point-id argument. This command displays the packages that will be active if you roll back one or more SDRs to that installation point. For example, the show install rollback 2 command displays the packages that will be active if you roll back to rollback point 2.
RP/0/RP0/CPU0:router(admin)# show install rollback 2Secure Domain Router: OwnerNode 0/1/SP [SP] [SDR: Owner]Boot Image: /disk0/hfr-os-mbi-3.3.84/sp/mbihfr-sp.vmRollback Packages:disk0:hfr-diags-3.3.84disk0:comp-hfr-mini-3.3.84Node 0/1/CPU0 [LC] [SDR: Owner]Boot Image: /disk0/hfr-os-mbi-3.3.84/lc/mbihfr-lc.vmRollback Packages:disk0:hfr-diags-3.3.84disk0:comp-hfr-mini-3.3.84Node 0/RP0/CPU0 [RP] [SDR: Owner]Boot Image: /disk0/hfr-os-mbi-3.3.84/mbihfr-rp.vmRollback Packages:disk0:hfr-diags-3.3.84disk0:hfr-mgbl-3.3.84disk0:hfr-k9sec-3.3.84disk0:comp-hfr-mini-3.3.84Node 0/RP1/CPU0 [RP] [SDR: Owner]Boot Image: /disk0/hfr-os-mbi-3.3.84/mbihfr-rp.vmRollback Packages:disk0:hfr-diags-3.3.84disk0:hfr-mgbl-3.3.84disk0:hfr-k9sec-3.3.84disk0:comp-hfr-mini-3.3.84Node 0/SM0/SP [SP] [SDR: Owner]Boot Image: /disk0/hfr-os-mbi-3.3.84/sp/mbihfr-sp.vmRollback Packages:disk0:hfr-diags-3.3.84disk0:comp-hfr-mini-3.3.84Node 0/SM1/SP [SP] [SDR: Owner]Boot Image: /disk0/hfr-os-mbi-3.3.84/sp/mbihfr-sp.vmRollback Packages:disk0:hfr-diags-3.3.84disk0:comp-hfr-mini-3.3.84Node 0/SM2/SP [SP] [SDR: Owner]Boot Image: /disk0/hfr-os-mbi-3.3.84/sp/mbihfr-sp.vmRollback Packages:disk0:hfr-diags-3.3.84disk0:comp-hfr-mini-3.3.84Node 0/SM3/SP [SP] [SDR: Owner]Boot Image: /disk0/hfr-os-mbi-3.3.84/sp/mbihfr-sp.vmRollback Packages:disk0:hfr-diags-3.3.84disk0:comp-hfr-mini-3.3.84Command Modes
The command syntax in EXEC and administration EXEC modes is different. In administration EXEC mode, the sdr sdr-name option allows you to view the rollback points for a specific SDR. To view the rollback points that apply to all SDRs, enter the command without the sdr option. In EXEC mode, the rollback points are displayed only for the SDR to which you are currently logged in:
Administration EXEC Mode Syntax
show install rollback point-id [sdr sdr-name | location node-id] [summary [sdr sdr-name]] [detail [sdr sdr-name | location node-id]]
EXEC Mode Syntax
show install rollback point-id [location node-id] [summary] [detail [location node-id]]
Note
Rolling Back to a Specific Rollback Point
You can roll back to a specific rollback point, including a noncommitted software set:
•
•
•
In the following example, the system is rolled back to noncommitted rollback point 8:
RP/0/RP0/CPU0:router(admin)# install rollback to 8Install operation 10 'install rollback to 8' started by user 'cisco' at 07:49:26UTC Mon Nov 14 2005.The install operation will continue asynchronously.RP/0/RP0/CPU0:router(admin)#Info: The changes made to software configurations will not be persistentInfo: across system reloads. Use the command 'admin install commit' to makeInfo: changes persistent.Info: Please verify that the system is consistent following the softwareInfo: change using the following commands:Info: show system verifyInfo: install verifyThe currently active software is the same as the committed software.Install operation 10 completed successfully at 07:51:24 UTC Mon Nov 14 2005.Rolling Back to the Last Committed Package Set
Use the install rollback to committed command to roll back to the last committed package set.
In the following example, all SDRs in the system are rolled back to the last committed package set:
RP/0/RP0/CPU0:router(admin)# install rollback to committedInstall operation 27 'install rollback to committed' started by user 'lab' at16:41:38 UTC Sat Nov 19 2005.Info: The rollback to committed software will require a reload of impactedInfo: nodes because it is over multiple activation & deactivationInfo: operations.Info: This operation will reload the following node:Info: 0/RP1/CPU0 (RP) (SDR: Owner)Info: This operation will reload all RPs in the Owner SDR, and therebyInfo: indirectly cause every node in the router to reload.Proceed with this install operation? [confirm]RP/0/RP0/CPU0:router(admin)#Updating Commit Database. Please wait...[OK]Info: The changes made to software configurations will not be persistentInfo: across system reloads. Use the command 'admin install commit' to makeInfo: changes persistent.Info: Please verify that the system is consistent following the softwareInfo: change using the following commands:Info: show system verifyInfo: install verifyInstall operation 27 completed successfully at 16:42:23 UTC Sat Nov 19 2005.Rolling Back the Committed Software Set for All SDRs
To perform a rollback for all SDRs in the system, use the install rollback to committed command in administration EXEC mode.
Rolling Back the Committed Software Set for a Specific SDR
•
•
Software Package Feature List
This appendix lists the features and components included with each Cisco IOS XR software package:
•
•
OS Package Features
The OS package provides the basic operating system and the following features:
•
•
•
•
•
•
•
•
•
•
Base Package Features
The Base package provides the basic infrastructure required to boot the router to the CLI prompt and activate software packages. The Base package also provides the following features:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Admin Package Features
The Admin package provides the basic software required to manage the router. The Admin package provides the following features:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Forwarding Package Features
The Forwarding package provides the following features:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Routing Package Features
The Routing package supports routing protocols (BGP, OSPF, and IS-IS), RIB, and the routing policy engine. The Routing package supports the following features:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Line Card Package Features
The Line Card package supports the following features:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Manageability Package Features
The Manageability package supports the following features:
•
•
•
•
•
•
•
•
•
•
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
Security Package Features
The Security package supports the following features:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
MPLS Package Features
The Multiprotocol Label Switching (MPLS) package supports the following features:
•
•
–
–
–
–
–
–
–
–
–
–
–
•
•
–
–
–
–
–
•
–
–
–
–
–
–
–
•
–
–
•
Multicast Package Features
The Multicast package supports the following features:
•
•
•
•
•
•
•
•
•
•
•
•
•
Diagnostics Package
Cisco IOS XR online diagnostics allow you to test and verify hardware functionality while connected to a live network. Scheduled diagnostics help ensure system high availability (HA). If a problem is detected, online diagnostics help isolate the location of the problem, allowing you to identify and replace the hardware. Online diagnostics are also used for system acceptance when receiving new hardware.
The online diagnostics contain tests that check different hardware components and verify the data path and control signals. Nondisruptive online diagnostic tests provide background health monitoring and can be scheduled or run on demand. On-demand diagnostics run from the command-line interface (CLI); scheduled diagnostics run at user-designated intervals or specified times when the system is connected to a live network.
Integrated Field Diagnostics (IFDs) are provided to allow the loading and unloading of offline diagnostic images. Loading a diagnostic image places the specified location out of service. When an offline diagnostic image is loaded, the diagnostic start and diagnostic stop commands are used to control test execution, and the show diagnostic content and show diagnostic results commands are used to show the test list and results.
The integrated field diagnostics detect problems in hardware components, including memory (failures that occur over time).
For more general information on diagnostics, see Cisco IOS XR Diagnostics. See Cisco IOS XR Interface and Hardware Component Command Reference for diagnostic command information.
Session Border Controller Package
The Session Border Controller (SBC) package provides border management services for Cisco XR 12000 Series Routers. Session Border Controllers controls and manages real-time multimedia traffic flows between IP network borders, handling signaling and media. SBCs perform native IP interconnection functions required for real-time communications, such as access control, NAT/firewall traversal, bandwidth policing, accounting, signaling interworking, legal intercept, and QoS management.
Additional References
The following sections provide references related to software package management on Cisco IOS XR software.
Related Documents
Standards
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature.
—
MIBs
—
To locate and download MIBs using Cisco IOS XR software, use the Cisco MIB Locator found at the following URL and choose a platform under the Cisco Access Products menu: http://cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
RFCs
No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature.
—
Technical Assistance
