Table Of Contents

Software Package Management Commands on Cisco IOS XR Software

clear install rollback oldest

install abort

install activate

install add

install attach

install commit

install deactivate

install log-history size

install remove

install resume

install rollback to

install suspend

install verify

show install

show install active

show install committed

show install inactive

show install log

show install package

show install pie-info

show install request

show install rollback

show install suspend

show install which

Software Package Management Commands on Cisco IOS XR Software

---

This chapter describes the Cisco IOS XR commands used to add packages to a router storage device, activate or deactivate packages, upgrade or downgrade existing packages, and display information about packages.

For detailed information about the concepts and tasks necessary to manage the Cisco IOS XR software, see the Cisco IOS XR Getting Started Guide.

clear install rollback oldest

To delete saved installation points from the installation buffer, use the clear install rollback oldest command in Administration EXEC mode.

clear install rollback oldest points

Syntax Description

points

Number of saved installation points to delete, beginning with the oldest saved installation point.

Defaults

No default behavior or values

Command Modes

Administration EXEC

Command History

Release	Modification
Release 3.0	This command was introduced on the Cisco CRS-1.
Release 3.2	This command was first supported on the Cisco XR 12000 Series Router.The command was made available in Administration EXEC mode.
Release 3.3.0	No modification.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Use the clear install rollback oldest command to delete saved installation points from the installation buffer.

Use the show install rollback command to display the software set associated with a saved installation point.

RP/0/RP0/CPU0:router(admin)# show install rollback ?

  0   ID of the rollback point to show package information for

  2   ID of the rollback point to show package information for

  4   ID of the rollback point to show package information for

  9   ID of the rollback point to show package information for

  10  ID of the rollback point to show package information for

RP/0/RP0/CPU0:router(admin)# show install rollback 0

Secure Domain Router: Owner

  Node 0/1/SP [SP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/sp/mbihfr-sp.vm

    Rollback Packages: 

      disk0:comp-hfr-mini-3.3.30

  Node 0/1/CPU0 [LC] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/lc/mbihfr-lc.vm

    Rollback Packages: 

      disk0:comp-hfr-mini-3.3.30

  Node 0/6/SP [SP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/sp/mbihfr-sp.vm

    Rollback Packages: 

      disk0:comp-hfr-mini-3.3.30

  Node 0/6/CPU0 [LC] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/lc/mbihfr-lc.vm

    Rollback Packages: 

      disk0:comp-hfr-mini-3.3.30

  Node 0/RP0/CPU0 [RP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/mbihfr-rp.vm

    Rollback Packages: 

      disk0:comp-hfr-mini-3.3.30

  Node 0/RP1/CPU0 [RP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/mbihfr-rp.vm

    Rollback Packages: 

      disk0:comp-hfr-mini-3.3.30

  Node 0/SM0/SP [SP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/sp/mbihfr-sp.vm

    Rollback Packages: 

      disk0:comp-hfr-mini-3.3.30

  Node 0/SM1/SP [SP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/sp/mbihfr-sp.vm

    Rollback Packages: 

      disk0:comp-hfr-mini-3.3.30

  Node 0/SM2/SP [SP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/sp/mbihfr-sp.vm

    Rollback Packages: 

      disk0:comp-hfr-mini-3.3.30

  Node 0/SM3/SP [SP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/sp/mbihfr-sp.vm

    Rollback Packages: 

      disk0:comp-hfr-mini-3.3.30

---

Note When clearing saved installation points from the installation buffer, note that the clear install rollback oldest command ignores secure domain router (SDR) boundaries and performs the operation in global scope.

---

Task ID

Task ID	Operations
pkg-mgmt	read, write

Examples

In the following example, the command show install rollback ? is used to display the available rollback points. The command clear install rollback oldest 2 is then used to delete the two oldest rollback points. The command show install rollback ? is used again to display the remaining rollback points.

RP/0/RP0/CPU0:router(admin)# show install rollback ?        

  0   ID of the rollback point to show package information for

  2   ID of the rollback point to show package information for

  4   ID of the rollback point to show package information for

  9   ID of the rollback point to show package information for

  10  ID of the rollback point to show package information for

RP/0/RP0/CPU0:router(admin)# clear install rollback oldest 2

Install operation 11 'clear install rollback oldest 2' started by user 'lab'

at 18:11:19 UTC Sat Apr 08 2006.

Info:     Successfully deleted the following rollback points:

Info:         0, 2

Install operation 11 completed successfully at 18:11:21 UTC Sat Apr 08 2006.

RP/0/RP0/CPU0:router(admin)#  show install rollback ?

  4   ID of the rollback point to show package information for

  9   ID of the rollback point to show package information for

  10  ID of the rollback point to show package information for

Related Commands

Command	Description
install rollback to	Rolls back the software set to a saved installation point or to the last committed installation point.
show install log	Displays the entries stored in the logging installation buffer.
show install rollback	Displays the software set associated with a saved installation point.

install abort

To abort an installation transaction, use the install abort command in Administration EXEC mode.

install abort [request-id]

Syntax Description

request-id

(Optional) Request ID assigned to an installation operation.

Defaults

Abort the current install operation.

Command Modes

Administration EXEC

Command History

Release	Modification
Release 3.3.0	This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Routers.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Use the install abort command to halt a software installation operation that is in process or that has been suspended.

Only activation, deactivation and rollback operations can be aborted. Specifically, the operation install add can not be aborted, but the operation install add...activate can be aborted.

Use the install abort command with the request-id argument to halt a specific install operation if the request-id is currently in process.

Task ID

Task ID	Operations
pkg-mgmt	read, write

Examples

The following example shows how to halt a specific install operation:

RP/0/RP0/CPU0:router(admin)# install abort

Info:     Please confirm your 'install abort' request by pressing Enter or y, or pressing 
n to cancel it.

Do you really want to abort install operation 15? [confirm] <enter>

Abort confirmed.

Please check console to verify the operation is aborted.

Related Commands

Command	Description
install add	Adds the package encapsulated in a specific PIE file to a storage device.
install deactivate	Removes a package from the active software set.
install activate	Adds a software package or SMU to the active software set.
install resume	Resumes an install activation operation that has been suspended with the command install suspend.
install suspend	Suspends an activation operation.

install activate

To add software functionality to the active software set, use the install activate command in Administration EXEC mode.

install activate device:package [asynchronous] [synchronous] [sdr sdr-name] [noprompt] [location node-id] [test]

Syntax Description

device:package	Device and package, expressed in concatenated form (for example, disk0:hfr-mgbl-1.0.0). For the device argument, the value is a specified storage device, typically disk0:. Press ? after a partial package name to display all possible matches available for activation. If there is only one match, press [TAB] to fill in the rest of the package name. Note Multiple packages can be activated at a time. If multiple Software Maintenance Upgrades (SMUs) are activated, then the operation will involve a node reload and the user will be prompted before the install operation occurs
asynchronous	(Optional) Performs the command in asynchronous mode. In asynchronous mode, the command runs in the background, and the EXEC prompt is returned as soon as possible. This is the default mode.
synchronous	(Optional) Performs the command in synchronous mode. This mode allows the installation process to finish before the prompt is returned.
sdr sdr-name	(Optional) Activates a package for a specific secure domain router (SDR). The sdr-name argument is the name assigned to the secure domain router.
location node-id	(Optional) Activates a package on the designated node. The node-id argument is expressed in the rack/slot/module notation. Note A package cannot be activated on a single node unless some version of the package being activated is already active on all nodes. For example, a Multiprotocol Label Switching (MPLS) package cannot be active on only one node. If a version of the MPLS package is already active on all nodes, an MPLS package then could be upgraded or downgraded on a single node.
noprompt	(Optional) Automatically ignores any reload confirmation prompts that result from a package activation. The router reloads if required.
test	(Optional) Verifies the effects of proposed operations without making changes to the Cisco IOS XR software.

Defaults

The package is activated on all supported nodes.
The operation is performed in asynchronous mode: The install activate command runs in the background, and the EXEC prompt is returned as soon as possible. Packages are activated for all SDRs.

Command Modes

Administration EXEC

Command History

Release	Modification
Release 2.0	This command was introduced on the Cisco CRS-1.
Release 3.0	No modification.
Release 3.2	This command was first supported on the Cisco XR 12000 Series Router. This command was moved from EXEC mode to Administration EXEC mode.
Release 3.3.0	Support was added for the SDR keyword and sdr-name argument. Support was added for the noprompt keyword.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Use the install activate command to add software packages or SMUs to the active software set 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 passed. To upgrade a package, activate the newer version of the package, and the older version is automatically deactivated.

Package activation for a specific secure domain router (SDR)

To activate a package only for a specific SDR, use the install activate command with the sdr keyword and sdr-name argument.

---

Note In Release 3.3.0, SDR-specific activation is supported for specific packages and upgrades, such as optional packages and SMUs. Packages that do not support SDR-specific activation can only be activated for all SDRs in the system. For detailed instructions, see the "Managing Cisco IOS XR Software Packages" module of the Cisco IOS XR Getting Started Guide.

---

Router reload

If the activation requires a router reload, a confirmation prompt appears. Use the install activate command with the noprompt keyword to automatically ignore any reload confirmation prompts and proceed with the package activation. The router reloads if required.

Node reloads

If a software operation requires a node reload, the config-register for that node should be set to autoboot. If the config-register for the node is not set to autoboot, then the system automatically changes the setting and the node reloads. A message describing the change is displayed.

Synchronous mode

Use the install activate command with the synchronous keyword to complete the operation before the prompt is returned. A progress bar indicates the status of the operation. For example:

- 1% complete: The operation can still be aborted (ctrl-c for options)

\ 10% complete: The operation can still be aborted (ctrl-c for options)

When the install activate command is run in asynchronous mode, the system may stay in synchronous mode for a short period of time while the system checks for questions to ask the user.

Press Ctrl-c during a synchronous operation to abort the operation or make the operation asynchronous.

Test option

Use the test keyword to verify the effects of the proposed operations and determine whether the installation can be completed. After previewing the effects of the proposed operations, use the show install log command for more details about the effects of the proposed operations.

---

Note The changes made to the active software set are not persistent during route processor (RP) reloads. Use the install commit command to make changes persistent.

---

Task ID

Task ID	Operations
pkg-mgmt	execute

Examples

The following example shows how to display the packages available for activation using the online help system. In this example, ? is entered after a partial package name to display all possible matches

RP/0/RP0/CPU0:router(admin)# install activate disk0:?

disk0:comp-hfr-mini-3.4.0.1I  disk0:hfr-admin-3.4.0.1I  disk0:hfr-base-3.4.0.1I 

   disk0:hfr-diags-3.4.0.1I

disk0:hfr-fwdg-3.4.0.1I       disk0:hfr-k9sec-3.4.0.1I  disk0:hfr-lc-3.4.0.1I   

   disk0:hfr-mcast-3.4.0.1I

disk0:hfr-mgbl-3.4.0.1I       disk0:hfr-mpls-3.4.0.1I   disk0:hfr-os-mbi-3.4.0.1

I  disk0:hfr-rout-3.4.0.1I

The following example shows how to activate a package on all nodes. Use the install commit command to make the changes persistent across RP reloads.

RP/0/RP0/CPU0:router(admin)# install activate disk0:hfr-mpls-3.3.30 synchronous

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

Info:     across system reloads. Use the command 'admin install commit' to make

Info:     changes persistent.

Info:     Please verify that the system is consistent following the software

Info:     change using the following commands:

Info:         show system verify

Info:         install verify

Install operation 15 completed successfully at 19:16:18 UTC Sat Apr 08 2006.

RP/0/RP0/CPU0:router(admin)# install commit

Install operation 16 'install commit' started by user 'lab' at 19:18:58 UTC

Sat Apr 08 2006.

Install operation 16 completed successfully at 19:19:01 UTC Sat Apr 08 2006.

The following example shows how to activate a package for a specific secure domain router:

RP/0/RP0/CPU0:router(admin)# install activate disk0:hfr-mpls-3.3.80 SDR CE1b 

Install operation 2 'install activate disk0:hfr-mpls-3.3.80 on SDR: CE1b' started by user 
'lab' 

Install operation 2 'install activate disk0:hfr-mpls-3.3.80 on SDR: CE1b' started by user 
'lab' at 15:31:23 GMT Mon Nov 14 2005.

Info:     SDR CE1b: Checking running configuration version compatibility with newly 
activated software ...

Info:     SDR CE1b: No incompatibilities found between the activated software and router 
running configuration.

Info:     The changes made to software configurations will not be persistent across system 
reloads. Use the command 'admin install commit' to make changes persistent.

Info:     Please verify that the system is consistent following the software change using 
the following commands:

Info:         show system verify

Info:         install verify

Install operation 2 completed successfully at 15:32:28 GMT Mon Nov 14 2005.

Related Commands

Command	Description
install add	Adds the package encapsulated in a specific PIE file to a storage device.
install deactivate	Removes a package from the active software set.
show install active	Displays active packages.
show install log	Displays the entries stored in the logging installation buffer.
show install request	Displays the list of incomplete installation manager requests.
install resume	Resumes an install activation operation that has been suspended with the command install suspend.
install suspend	Suspends an activation operation.
show install suspend	Displays the suspension points for an activation operation.

install add

To copy the contents of a Package Installation Envelope (PIE) file to a storage device, use the install add command in Administration EXEC mode.

install add pie-file [asynchronous] [synchronous] [[activate [sdr sdr-name] [noprompt] [location node-id]]

Syntax Description

pie-file	Name and location of the PIE file (composite package) to install. Location options are as follows: •disk0: •disk1: •ftp://username:password@hostname or ip-address/directory-path/ •rcp://username@hostname or ip-address/directory-path/ •tftp://hostname or ip-address/directory-path/ Note Multiple PIE files can be added to a device at a time.
asynchronous	(Optional) Performs the command in asynchronous mode. In asynchronous mode, this command runs in the background, and the EXEC prompt is returned as soon as possible. This is the default mode.
synchronous	(Optional) Performs the command in synchronous mode. This mode allows the installation process to finish before the prompt is returned.
activate	(Optional) Activates the package or packages. This option is run only if the install add operation is successful.
sdr sdr-name	(Optional) Activates a package for a specific secure domain router (SDR). The sdr-name argument is the name assigned to the secure domain router.
location node-id	(Optional) Activates a package on the designated node. The node-id argument is expressed in the rack/slot/module notation. Note A package cannot be activated on a single node unless some version of the package being activated is already active on all nodes. For example, a Multiprotocol Label Switching (MPLS) package cannot be active on only one node. If a version of the MPLS package is already active on all nodes, an MPLS package then could be upgraded or downgraded on a single node.
noprompt	(Optional) Automatically ignores any reload confirmation prompts that result from a package activation. The router reloads if required.

Defaults

Packages are added to the storage device, but not activated.
The operation is performed in asynchronous mode: The install add command runs in the background, and the EXEC prompt is returned as soon as possible.

Command Modes

Administration EXEC

Command History

Release	Modification
Release 2.0	This command was introduced on the Cisco CRS-1.
Release 3.0	No modification.
Release 3.2	This command was first supported on the Cisco XR 12000 Series Router. The command was moved from EXEC mode to Administration EXEC mode.
Release 3.3.0	Support was added for the optional activate keywords and arguments: [sdr sdr-name] [noprompt] and [location node-id]. Support was removed for the to device keyword and argument.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Use the install add command to extract and store packages on the designated storage device. The default storage device for software packages is disk0:.

---

Note When adding a PIE file to a storage device, note that the install add command ignores secure domain router (SDR) boundaries and performs the operation in global scope.

---

Adding and activating a package

Software packages remain inactive until activated with the install activate command.

To add and activate a package at the same time, use the install add command with the activate keyword. When this command is used, the keywords and rules for package activation apply. See the "install activate" section for more information.

---

Note In Release 3.3.0, SDR-specific activation is supported for specific packages and upgrades, such as optional packages and SMUs. Packages that do not support SDR-specific activation can only be activated for all SDRs in the system. For detailed instructions, see the "Managing Cisco IOS XR Software Packages" module of the Cisco IOS XR Getting Started Guide.

---

---

Note If a software activation requires a node reload, the config-register for that node should be set to autoboot. If the config-register for the node is not set to autoboot, then the system automatically changes the setting and the node reloads. A message describing the change is displayed.

---

Synchronous mode

Use the install add command with the synchronous keyword to complete the operation before the prompt is returned. A progress bar indicates the status of the operation. For example:

- 1% complete: The operation can still be aborted (ctrl-c for options)

\ 10% complete: The operation can still be aborted (ctrl-c for options)

TFTP services and image size

Some Cisco IOS XR images may be larger than 32 MB, and the TFTP services provided by some vendors (such as Sun Solaris) may not support a file this large. If you do not have access to a TFTP server that supports files larger than 32 MB:

•Download the software image using FTP or rcp.

•Use a third-party or freeware TFTP server that supports file sizes larger than 32 MB.

Download a patch from Sun Microsystems to correct this limitation (http://www.sun.com).

Task ID

Task ID	Operations
pkg-mgmt	execute

Examples

The following example shows how to add a PIE file. In the following example, a Multiprotocol Label Switching (MPLS) package is added in synchronous mode. This operation copies the files required for the package to the storage device. This package remains inactive until it is activated with the install activate command.

RP/0/RP0/CPU0:router(admin)# install add tftp://209.165.201.1/hfr-mpls.pie synchronous 

Install operation 4 'install add /tftp://209.165.201.1/hfr-mpls.pie synchronous' started 
by user

'lab' at 03:17:05 UTC Mon Nov 14 2005.

Info:     The following package is now available to be activated:

Info:      

Info:         disk0:hfr-mpls-3.3.80

Info:      

Install operation 4 completed successfully at 03:18:30 UTC Mon Nov 14 2005.

In the following example, a package is added and activated with a single command:

RP/0/RP0/CPU0:router(admin)# install add disk1:hfr-mgbl-p.pie-3.3.0 activate

Install operation 4 'install add /disk1:hfr-mgbl-p.pie-3.3.0 activate' started

by user 'lab' at 07:58:56 UTC Wed Mar 01 2006.

The install operation will continue asynchronously.

:router(admin)#Part 1 of 2 (add software): Started

Info:     The following package is now available to be activated:

Info:      

Info:         disk0:hfr-mgbl-3.3.0

Info:      

Part 1 of 2 (add software): Completed successfully

Part 2 of 2 (activate software): Started

Info:     The changes made to software configurations will not be persistent across

system reloads. Use the command 'admin install

Info:     commit' to make changes persistent.

Info:     Please verify that the system is consistent following the software change

using the following commands:

Info:         show system verify

Info:         install verify

Part 2 of 2 (activate software): Completed successfully

Part 1 of 2 (add software): Completed successfully

Part 2 of 2 (activate software): Completed successfully

Install operation 4 completed successfully at 08:00:24 UTC Wed Mar 01 2006.

Related Commands

Command	Description
install activate	Adds a software package to the active software set.
install commit	Makes the changes persistent across RP reloads.
show install log	Displays the entries stored in the logging installation buffer.
show install request	Displays the list of incomplete installation manager requests.

install attach

To attach a terminal to an install operation, use the install attach command in Administration EXEC configuration mode.

install attach [request-id] [asynchronous] [synchronous]

Syntax Description

request-id	(Optional) Request ID assigned to an installation operation.
asynchronous	(Optional) Performs the command in asynchronous mode. In asynchronous mode, this command runs in the background, and the EXEC prompt is returned as soon as possible. This is the default mode.
synchronous	(Optional) Performs the command in synchronous mode. This mode allows the installation process to finish before the prompt is returned.

Defaults

The command operates in synchronous mode.

Command Modes

Administration EXEC

Command History

Release	Modification
Release 3.3.0	This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Routers.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Use the install attach command to attach a terminal to an install operation. This is similar to making the install operation synchronous, and is used for the following reasons:

•To change a asynchronous install operation to a synchronous install operation.

•The install operation is asynchronous but the terminal that ran the command has been lost (due to a failover or terminal timeout).

---

Note An asynchronous operation runs in the background, and the EXEC prompt is returned as soon as possible. This is the default mode. A synchronous operation allows the installation process to finish before the prompt is returned.

---

Task ID

Task ID	Operations
pkg-mgmt	read, write

Examples

The following example, a software package is activated in asynchronous mode. In asynchronous mode, the command runs in the background, and the CLI prompt is returned as soon as possible.

Use the install attach command to attach the terminal to an install operation. This switches the operation to synchronous mode, which allows the installation process to finish before the prompt is returned.

In the following example, the install activate command is entered in asynchronous mode. The CLI prompt returns before the operation is complete.

RP/0/RP0/CPU0:router(admin)#install activate disk0:hfr-mcast-3.7.6

Install operation 14 'install activate disk0:hfr-mcast-3.7.6' started by user

'lab' at 08:04:31 UTC Mon Nov 14 2005.

The install operation will continue asynchronously.

RP/0/RP0/CPU0:router(admin)#Info:     SDR Owner: Checking running configuration version 
compatibility with

Info:     newly activated software ...

Info:     SDR Owner: No incompatibilities found between the activated software

Info:     and router running configuration.

In the following example, the install attach command is used to attach the terminal to the install operation and complete the operation in synchronous mode. The CLI prompt is returned only after the install operation is complete:

RP/0/RP0/CPU0:router(admin)# install attach

Install operation 14 'install activate disk0:hfr-mcast-3.7.6' started by user

'lab' at 08:04:31 UTC Mon Nov 14 2005.

Info:     SDR Owner: Checking running configuration version compatibility with

Info:     newly activated software ...

Info:     SDR Owner: No incompatibilities found between the activated software

Info:     and router running configuration.

Info:     The changes made to software configurations will not be persistent

Info:     across system reloads. Use the command 'admin install commit' to make

Info:     changes persistent.

Info:     Please verify that the system is consistent following the software

Info:     change using the following commands:

Info:         show system verify

Info:         install verify

The currently active software is not committed. If the system reboots then the committed 
software will be used. Use 'install commit' to commit the active software. 

Install operation 14 completed successfully at 08:06:12 UTC Mon Nov 14 2005.

Related Commands

Command	Description
install activate	Adds a software package to the active software set.
install add	Adds the package encapsulated in a specific PIE file to a storage device.
install deactivate	Removes a package from the active software set.

install commit

To save the active software set to be persistent across designated system controller (DSC) reloads, use the install commit command in Administration EXEC mode.

install commit

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

Administration EXEC

Command History

Release	Modification
Release 2.0	This command was introduced on the Cisco CRS-1.
Release 3.0	No modification.
Release 3.2	This command was first supported on the Cisco XR 12000 Series Router. The command was moved from EXEC mode to Administration EXEC mode.
Release 3.3.0	No modification.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

On startup, the primary RP loads the active software set saved with the install commit command.

When a package is activated, it becomes part of the current running configuration. To make the package activation persistent across RP reloads, you must enter the install commit command. If the system is restarted before the active software set is saved with the install commit command, the previously committed software set is used.

---

Note When a committing the active software set, note that the install commit ignores secure domain router (SDR) boundaries and performs the operation in global scope.

---

Task ID

Task ID	Operations
pkg-mgmt	read, write

Examples

The following example shows how to make the current active software set persistent across RP reloads:

RP/0/RP0/CPU0:router(admin)# install commit

Install operation 16 'install commit' started by user 'lab' at 19:18:58 UTC

Sat Apr 08 2006.

Install operation 16 completed successfully at 19:19:01 UTC Sat Apr 08 2006.

Related Commands

Command	Description
show install committed	Displays committed active packages.
show install log	Displays the entries stored in the logging installation buffer.

install deactivate

To remove a package from the active software set, use the install deactivate command in Administration EXEC mode.

install deactivate device:package [asynchronous] [synchronous] [sdr sdr-name] [noprompt] [location node-id] [test]

Syntax Description

device:package	Device and package, expressed in concatenated form (for example, disk0:hfr-mgbl-1.0.0). For the device argument, the value is disk0:. Press ? after a partial package name to display all possible matches available for activation. If there is only one match, press [TAB] to fill in the rest of the package name.
asynchronous	(Optional) Performs the command in asynchronous mode. In asynchronous mode, this command runs in the background, and the EXEC prompt is returned as soon as possible. This is the default mode.
synchronous	(Optional) Performs the command in synchronous mode. This mode allows the installation process to finish before the prompt is returned.
sdr sdr-name	(Optional) Deactivates a package for a specific secure domain router (SDR). The sdr-name argument is the name assigned to the secure domain router.
noprompt	(Optional) Automatically ignores any reload confirmation prompts that result from a package deactivation. The router reloads if required.
location node-id	(Optional) Deactivates a package from the designated node. The node-id argument is entered in the rack/slot/module notation. Note In most cases, a package cannot be deactivated from a node, because some version of that package must be running on all supported nodes after the deactivation operation finishes.
test	(Optional) Verifies the effects of proposed operations without making changes to the Cisco IOS XR software.

Defaults

The package is deactivated on all supported nodes.
The operation is performed in asynchronous mode. The install deactivate command runs in the background, and the EXEC prompt is returned as soon as possible.

Command Modes

Administration EXEC

Command History

Release	Modification
Release 2.0	This command was introduced on the Cisco CRS-1.
Release 3.0	No modification.
Release 3.2	This command was first supported on the Cisco XR 12000 Series Router. The command was moved from EXEC mode to Administration EXEC mode.
Release 3.3.0	Support was added for the sdr keyword and sdr-name argument. Support was added for the noprompt keyword.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Deactivating a package removes the activated package from the active software set from all nodes or from a single node. When a deactivation is attempted, the system runs an automatic check to ensure that the package is not required by other active packages. The deactivation is permitted only after all compatibility checks have passed.

The following restrictions and conditions apply to software deactivation:

•A feature package cannot be deactivated if active packages need it to operate.

•To downgrade a package, activate the older version. The newer package version will be deactivated automatically.

---

Note To deactivate a package only for a specific secure domain router (SDR), use the install activate command with the SDR keyword and sdr-name argument.

---

Router reloads

If the deactivation requires a router reload, a confirmation prompt appears. Use the install deactivate command with the noprompt keyword to automatically ignore any reload confirmation prompts and proceed with the package deactivation. The router reloads if required.

Node reloads

If a software operation requires a node reload, the config-register for that node should be set to autoboot. If the config-register for the node is not set to autoboot, then the system automatically changes the setting and the node reloads. A message describing the change is displayed.

Synchronous operation

Use the install deactivate command with the synchronous keyword to complete the operation before the prompt is returned. A progress bar indicates the status of the operation. For example:

- 1% complete: The operation can still be aborted (ctrl-c for options)

\ 10% complete: The operation can still be aborted (ctrl-c for options)

Test option

Use the test keyword to verify the effects of the deactivation without making changes to the system. Use this option to determine if the deactivation can be completed. After previewing the effects of the proposed operations, use the show install log command for more details about the effects of the proposed operations.

Use the install commit command to make changes persistent across route processor (RP) reloads.

Task ID

Task ID	Operations
pkg-mgmt	execute

Examples

The following example shows how to display the packages available for deactivation using the online help system. In this example, ? is entered after a partial package name to display all possible matches

RP/0/RP0/CPU0:router(admin)# install deactivate disk0:?

disk0:comp-hfr-mini-3.4.0.1I  disk0:hfr-admin-3.4.0.1I  disk0:hfr-base-3.4.0.1I 

   disk0:hfr-diags-3.4.0.1I

disk0:hfr-fwdg-3.4.0.1I       disk0:hfr-k9sec-3.4.0.1I  disk0:hfr-lc-3.4.0.1I   

   disk0:hfr-mcast-3.4.0.1I

disk0:hfr-mgbl-3.4.0.1I       disk0:hfr-mpls-3.4.0.1I   disk0:hfr-os-mbi-3.4.0.1

I  disk0:hfr-rout-3.4.0.1I

The following example shows how to deactivate a package on all supported nodes in synchronous mode.

RP/0/RP0/CPU0:router(admin)# install deactivate disk0:hfr-mpls-3.3.30 synchronous

Install operation 14 'install deactivate disk0:hfr-mpls-3.3.30 synchronous'

started by user 'lab' at 18:38:37 UTC Sat Apr 08 2006.

Info:     The changes made to software configurations will not be persistent

Info:     across system reloads. Use the command 'admin install commit' to make

Info:     changes persistent.

Info:     Please verify that the system is consistent following the software

Info:     change using the following commands:

Info:         show system verify

Info:         install verify

Install operation 14 completed successfully at 18:39:20 UTC Sat Apr 08 2006.

In the following example, the Security package is deactivated for the SDR named "LR1".

RP/0/RP0/CPU0:router(admin)# install deactivate disk0:hfr-k9sec-3.3.0 sdr LR1

Install operation 11 'install deactivate disk0:hfr-k9sec-3.3.0 on SDR: LR1'

started by user 'lab' at 03:25:26 est Thu Mar 02 2006.

- 1% complete: The operation can still be aborted (ctrl-c for options)

The install operation will continue asynchronously.

The changes made to software configurations will 

not be persistent

Info:     across system reloads. Use the command 'admin install commit' to make

Info:     changes persistent.

Info:     Please verify that the system is consistent following the software

Info:     change using the following commands:

Info:         show system verify

Info:         install verify

The currently active software is not committed. If the system reboots then the committed 
software will be used. Use 'install commit' to commit the active software. 

Install operation 11 completed successfully at 03:25:56 est Thu Mar 02 2006.

You cannot deactivate a package if other packages or nodes require that package. In the following example, an attempt to deactivate a package is rejected:

RP/0/RP1/CPU0:router(admin)#install deactivate disk0:hfr-diags-3.3.90 locati$

Install operation 25 'install deactivate disk0:hfr-diags-3.3.90 on node

0/6/CPU0' started by user 'lab' at 23:01:38 UTC Sat Apr 15 2006.

Error:    Cannot proceed with the deactivation because of the following package

Error:    incompatibilities:

Error:      hfr-diags-3.3.90 on nodes of type RP needs hfr-diags-3.3.90, or

Error:    equivalent, to be active on node 0/6/CPU0 on secure domain router

Error:    Owner.

Error:      hfr-diags-3.3.90 on nodes of type DRP needs hfr-diags-3.3.90, or

Error:    equivalent, to be active on node 0/6/CPU0 on secure domain router

Error:    Owner.

Error:      hfr-diags-3.3.90 on nodes of type SP needs hfr-diags-3.3.90, or

Error:    equivalent, to be active on node 0/6/CPU0 on secure domain router

Error:    Owner.

Error:      hfr-diags-3.3.90 on nodes of type LC needs hfr-diags-3.3.90, or

Error:    equivalent, to be active on node 0/6/CPU0 on secure domain router

Error:    Owner.

Error:    Suggested steps to resolve this:

Error:     - check the installation instructions.

Error:     - activate or deactivate the specified packages on the specified

Error:    nodes.

Install operation 25 failed at 23:01:44 UTC Sat Apr 15 2006.

Related Commands

Command	Description
install activate	Adds a software package or SMU to the active software set.
install commit	Makes the changes persistent across RP reloads.
install remove	Removes a deactivated package from a storage device.
show install inactive	Displays inactive packages in the active software set.
show install log	Displays the entries stored in the logging installation buffer.
show install request	Displays the list of incomplete installation manager requests.

install log-history size

To set the maximum number of entries to be stored in the logging installation buffer, use the install log-history size command in Administration configuration mode. To restore the default, use the no form of this command.

install log-history size entries

no install log-history size

Syntax Description

entries

Maximum number of log entries. Valid values are 0 to 255.

Defaults

No default behavior or values

Command Modes

Administration configuration

Command History

Release	Modification
Release 2.0	This command was introduced on the Cisco CRS-1.
Release 3.0	No modification.
Release 3.2	This command was first supported on the Cisco XR 12000 Series Router. The command was moved from EXEC mode to Administration EXEC mode.
Release 3.3.0	No modification.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Use install log-history command to set the maximum number of entries to be stored in the logging installation buffer.

Use the show install log to display the entries stored in the logging installation buffer and the details of install requests.

Task ID

Task ID	Operations
pkg-mgmt	read, write

Examples

The following example shows how to set the maximum size of the logging installation buffer to 100 entries:

RP/0/RP0/CPU0:router(admin-config)# install log-history size 100

Related Commands

Command	Description
show install log	Displays the entries stored in the logging installation buffer.

install remove

To delete inactive packages from a storage device, use the install remove command in Administration EXEC mode.

install remove {[device:package] [inactive [device]]} [asynchronous] [synchronous] [noprompt] [test]

Syntax Description

device:package	(Optional) Device and package, expressed in concatenated form (for example, disk0:hfr-mgbl-1.0.0). For the device argument, the value is disk0:. Note Multiple packages can be removed at the same time.
inactive	(Optional) Removes all inactive packages from all storage device.
device	(Optional) Removes all inactive packages from a specific storage device.
asynchronous	(Optional) Performs the command in asynchronous mode. In asynchronous mode, this command runs in the background, and the EXEC prompt is returned as soon as possible. This is the default mode.
synchronous	(Optional) Performs the command in synchronous mode. This mode allows the installation process to finish before the prompt is returned.
noprompt	(Optional) Automatically ignores any confirmation prompts for a package removal. The specified packages are removed with no further user input.
test	(Optional) Verifies the effects of proposed operations without making changes to the Cisco IOS XR software.

Defaults

The operation is performed in asynchronous mode: The install remove command runs in the background, and the EXEC prompt is returned as soon as possible.

Command Modes

Administration EXEC

Command History

Release	Modification
Release 2.0	This command was introduced on the Cisco CRS-1.
Release 3.0	Support was added to enable removal of multiple packages at the same time and to enable removal of inactive packages from a storage device.
Release 3.2	This command was first supported on the Cisco XR 12000 Series Router. The command was moved from EXEC mode to Administration EXEC mode.
Release 3.3.0	Support was added for the noprompt keyword.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Packages can be removed only if they are deactivated and not in the committed software set.

•Use the command install remove with the inactive keyword to remove all inactive packages from all nodes in the system.

•Use the command install remove with the inactive keyword and the device argument to remove all inactive packages from a specific storage device, such as disk0:.

•Use the command install remove with the device:package argument t o remove a specific inactive package from a specific node.

If the operation requires a router reload, a confirmation prompt appears. Use the install remove command with the noprompt keyword to automatically ignore any reload confirmation prompts and proceed with the package removal. The router reloads if required.

Use the test keyword to verify the effects of the package removal operation and determine whether the operation can be completed. After previewing the effects of the proposed operations, use the show install log command for more details about the effects of the proposed operations.

---

Note When removing a package, note that the install remove command ignores secure domain router (SDR) boundaries and performs the operation in global scope.

---

Task ID

Task ID	Operations
pkg-mgmt	execute

Examples

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/RP1/CPU0:router(admin)# install remove disk0:hfr-diags-3.3.90 test

Install operation 30 'install remove disk0:hfr-diags-3.3.90 test' started by

user 'lab' at 23:40:22 UTC Sat Apr 15 2006.

Warning:  No changes will occur due to 'test' option being specified. The

Warning:  following is the predicted output for this install command.

Info:     This operation will remove the following package:

Info:         disk0:hfr-diags-3.3.90

Info:     After this install remove the following install rollback points will

Info:     no longer be reachable, as the required packages will not be present:

Info:         4, 9, 10, 14, 15, 17, 18

Proceed with removing these packages? [confirm] y

The install operation will continue asynchronously.

Install operation 30 completed successfully at 23.

Related Commands

Command	Description
install add	Installs a package on a storage device.
show install log	Displays the entries stored in the logging installation buffer.
show install request	Displays the list of incomplete installation manager requests.

install resume

To resume a suspended install activation operation, use the install resume command in Administration EXEC mode.

install resume {sw-change | location node-id}

Syntax Description

sw-change	Resumes an activation operation for all nodes.
location node-id	Resumes an activation operation for a specific node. The node-id argument is entered in the rack/slot/module notation.

Defaults

No default behavior or values

Command Modes

Administration EXEC

Command History

Release	Modification
Release 3.3.0	This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Routers.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Use the install resume command to resume a suspended install operation. If the operation is not suspended, then the command has no effect.

Task ID

Task ID	Operations
pkg-mgmt	read, write

Examples

The following example shows how to resume an install operation:

RP/0/RP0/CPU0:router(admin)# install resume 

Install operation 9 has been resumed. 

Info:     Install operation 9 has been resumed.

RP/0/RP0/CPU0:router(admin)#Info:     The changes made to software configurations will not 
be persistent

Info:     across system reloads. Use the command 'admin install commit' to make

Info:     changes persistent.

Info:     Please verify that the system is consistent following the software

Info:     change using the following commands:

Info:         show system verify

Info:         install verify

The currently active software is not committed. If the system reboots then the committed 
software will be used. Use 'install commit' to commit the active software. 

Install operation 9 completed successfully at 07:47:18 UTC Mon Nov 14 2005.

Related Commands

Command	Description
install activate	Activates a software package for all nodes, a single node, or a secure domain router.
install suspend	Suspends an activation operation.
show install suspend	Displays the suspension points for an activation operation.

install rollback to

To roll back the software set to a saved installation point or to the last committed installation point, use the install rollback to command in Administration EXEC mode.

install rollback to {point-id | committed} [asynchronous] [synchronous] [noprompt] [test]

Syntax Description

point-id	Installation point ID number.
committed	Rolls the Cisco IOS XR software back to the last committed installation point.
asynchronous	(Optional) Performs the command in asynchronous mode. In asynchronous mode, this command runs in the background, and the EXEC prompt is returned as soon as possible. This is the default mode.
synchronous	(Optional) Performs the command in synchronous mode. This mode allows the installation process to finish before the prompt is returned.
noprompt	(Optional) Automatically ignores any reload confirmation prompts that result from a rollback operation. The router reloads if required.
test	(Optional) Verifies the effects of proposed operations without making changes to the Cisco IOS XR software.

Defaults

The operation is performed in asynchronous mode: The install rollback to command runs in the background, and the EXEC prompt is returned as soon as possible.

Command Modes

Administration EXEC

Command History

Release	Modification
Release 2.0	This command was introduced on the Cisco CRS-1.
Release 3.0	Support was added to enable roll back to a saved installation point.
Release 3.2	This command was moved from EXEC mode to Administration EXEC mode.
Release 3.3.0	Support was removed for the reload keyword. Support was added for the noprompt keyword.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Use the install rollback command to roll back the configuration to a saved installation point or to the last committed installation point. Rollback points are created when the router is booted and when packages are activated or deactivated. When an installation point is created, the Cisco IOS XR software assigns an ID number to that rollback point. To roll back to a saved installation point, enter the installation point ID number assigned to it for the point-id argument. When a software configuration is committed with the install commit command, that configuration is saved as the last committed installation point. Use the committed keyword to roll back to the last committed installation point.

To display the saved rollback points available, use the online help function:

RP/0/RP0/CPU0:router(admin)# install rollback to ?

      0          Specify the id for the install point to rollback to

      1          Specify the id for the install point to rollback to

      12         Specify the id for the install point to rollback to

      15         Specify the id for the install point to rollback to

      2          Specify the id for the install point to rollback to

      4          Specify the id for the install point to rollback to

      6          Specify the id for the install point to rollback to

      7          Specify the id for the install point to rollback to

      8          Specify the id for the install point to rollback to

      9          Specify the id for the install point to rollback to

      committed  Rollback to the last committed installation point

If a rollback operation requires that the software set be rolled back beyond two saved installation points, a message appears in the output of the install rollback command, indicating that the attempted rollback operation requires the Cisco IOS XR software to be reloaded. You are required to reload the Cisco IOS XR software to protect the system from multiple package activation and deactivation operations (as a result of rolling back beyond the saved installation points), which could cause system instability. For the rollback operation to be completed, you must reenter the install rollback command with the reload keyword.

If a rollback operation requires that a package be activated that is no longer on the system (because the package had been removed), a message appears in the output of the install rollback command indicating that the specified installation point is unavailable and that the required package must be added to roll back the software set to the specified installation point.

If a rollback operation requires a router reload, a confirmation prompt appears. Use the install rollback command with the noprompt keyword to automatically ignore any reload confirmation prompts and proceed with the rollback operation. The router reloads if required.

If a software operation requires a node reload, the config-register for that node should be set to autoboot. If the config-register for the node is not set to autoboot, then the system automatically changes the setting and the node reloads. A message describing the change is displayed.

Use the test keyword to verify the effects of the proposed operations and determine whether the rollback operation can be completed. After previewing the effects of the proposed operations, use the show install log command for more details about the effects of the proposed operations.

---

Note When rolling back to a saved installation point, note that the install rollback command ignores secure domain router (SDR) boundaries and performs the operation in global scope.

---

Use the clear install rollback oldest to delete saved installation points from the installation buffer.

Use the show install rollback command to display the software set associated with a saved installation point.

Task ID

Task ID	Operations
pkg-mgmt	read, write

Examples

The following example shows how to roll back to a saved installation point:

RP/0/RP0/CPU0:router(admin)# install rollback to 8

Install operation 10 'install rollback to 8' started by user 'lab' at 07:49:26

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

Info:     across system reloads. Use the command 'admin install commit' to make

Info:     changes persistent.

Info:     Please verify that the system is consistent following the software

Info:     change using the following commands:

Info:         show system verify

Info:         install verify

The currently active software is the same as the committed software. 

Install operation 10 completed successfully at 07:51:24 UTC Mon Nov 14 2005.

Related Commands

Command	Description
clear install rollback oldest	Deletes saved installation points from the installation buffer.
install commit	Makes the current active software set persistent across reloads.
show install log	Displays the entries stored in the logging installation buffer.
show install request	Displays the list of incomplete installation manager requests.
show install rollback	Displays the software set associated with a saved installation point.

install suspend

To suspend a software activation, deactivation, or rollback, use the install suspend command in Administration EXEC mode.

install suspend {sw-change | location node-id}

Syntax Description

sw-change	Suspends the operation after the software download to all nodes is complete, but before to any software changes are implemented.
location node-id	Suspends the operation for a specific node. If the software change for the node is already in process, the command has no effect. The node-id argument is entered in the rack/slot/module notation.

Defaults

No default behavior or values

Command Modes

Administration EXEC

Command History

Release	Modification
Release 3.3.0	This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Routers.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Use the install suspend command to temporarily suspend an activation, deactivation, or rollback operation. To resume the operation, use the install resume command.

Use the install suspend with the location node-id keyword and argument to suspend the software change for a specific node. If the change for the node is already in process, the command has no effect.

Use the install suspend with the sw-change keyword to suspend the operation after the software download to all nodes is complete, but before any software changes are implemented.

The install suspend command can be run multiple times to set multiple suspension points. Use the show install suspend command to view all suspension points.

Suspension points are valid for the current install operation, or the next install operation if no install operation is currently in progress. Suspension points are cleared after the transaction has been completed.

Task ID

Task ID	Operations
pkg-mgmt	read, write

Examples

The following example shows how to suspend a software activation.

Use the command show install suspend to display the suspended operation. Use the command install resume to cancel the suspension and resume the install operation:

RP/0/RP0/CPU0:router(admin)#install suspend sw-change 

RP/0/RP0/CPU0:router(admin)#install activate disk0:hfr-mcast-3.7.6  

Install operation 9 'install activate disk0:hfr-mcast-3.7.6' started by user

'lab' at 07:44:53 UTC Mon Nov 14 2005.

The install operation will continue asynchronously.

Install operation 9 has been suspended. Use the command 'install resume' in admin mode to 
resume the operation. 

Info:     Install operation 9 has been suspended. Use the command 'install

Info:     resume' in admin mode to resume.

RP/0/RP0/CPU0:router(admin)#show install suspend 

State: install 9 suspended before software change

Related Commands

Command	Description
install activate	Activates a software package for all nodes, a single node, or a secure domain router.
install resume	Resumes an install activation operation that has been suspended with the command install suspend.
show install suspend	Displays the suspension points for an activation operation.

install verify

To verify the consistency of a previously installed software set with the package file from which it originated, use the install verify command in Administration EXEC mode.

install verify [asynchronous] [synchronous] [sdr sdr-name] [location node-id]

Syntax Description

asynchronous	(Optional) Performs the command in asynchronous mode. In asynchronous mode, this command runs in the background, and the EXEC prompt is returned as soon as possible. This is the default mode.
synchronous	(Optional) Performs the command in synchronous mode. This mode allows the installation process to finish before the prompt is returned.
sdr sdr-name	(Optional) Performs the command for a specific secure domain router (SDR). The sdr-name argument is the name assigned to the secure domain router.
location node-id	(Optional) Verifies the consistency of previously installed software from the designated node with the package file from which it originated. The node-id argument is expressed in the rack/slot/module notation.

Defaults

The operation is performed in asynchronous mode: The install verify command runs in the background, and the EXEC prompt is returned as soon as possible.

Command Modes

Administration EXEC

Command History

Release	Modification
Release 3.1	This command was introduced on the Cisco XR 12000 Series Router.
Release 3.2	No modification.
Release 3.3.0	Support was added for the sdr keyword and sdr-name argument.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Use the install verify command to verify the consistency of a previously 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.

---

Note The install verify command can take up to two minutes per package to process.

---

---

Note To perform the command for a specific secure domain router (SDR), use the install verify command with the sdr keyword and sdr-name argument.

---

Task ID

Task ID	Operations
pkg-mgmt	execute

Examples

The following example shows how to verify the consistency of a previously installed software set with the package file from which it originated. This command is run in synchronous mode:

RP/0/RP0/CPU0:router(admin)# install verify synchronous

Install operation 7 'install verify synchronous' started by user 'lab' at

17:04:06 UTC Sat Apr 08 2006.

Info:     This operation can take up to 2 minutes per package being verified.

Info:     Please be patient.

Info:     Verify operation successful, no anomalies found.

Info:     Node 0/1/SP

Info:         [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/CPU0

Info:         [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/SP

Info:         [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/CPU0

Info:         [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/CPU0

Info:         [SUCCESS] /disk0/hfr-diags-3.3.30: Verification Successful.

Info:         [SUCCESS] /disk0/hfr-mgbl-3.3.30: Verification Successful.

Info:         [SUCCESS] /disk0/hfr-k9sec-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/CPU0

Info:         [SUCCESS] /disk0/hfr-diags-3.3.30: Verification Successful.

Info:         [SUCCESS] /disk0/hfr-mgbl-3.3.30: Verification Successful.

Info:         [SUCCESS] /disk0/hfr-k9sec-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/SP

Info:         [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/SP

Info:         [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/SP

Info:         [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/SP

Info:         [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 7 completed successfully at 17:09:29 UTC Sat Apr 08 2006.

Related Commands

Command	Description
show install log	Displays the entries stored in the logging installation buffer.
show install request	Displays the list of incomplete installation manager requests.

show install

To display active packages, use the show install command in EXEC mode or Administration EXEC mode.

show install [all | sdr sdr-name | location node-id] [[detail [sdr sdr-name | location node-id] [summary [sdr sdr-name]]

Syntax Description

all	(Optional) Displays the active packages from all locations.
sdr sdr-name	(Optional) Displays the active packages for a specific secure domain router (SDR). The sdr-name argument is the name assigned to the secure domain router.
location node-id	(Optional) Displays the active packages for a designated node. The node-id argument is expressed in the rack/slot/module notation.
summary	(Optional) Displays a summary of the active packages in a system or secure domain router. Use this command to display the default software profile for SDRs
detail	(Optional) Displays a detailed summary of the active packages for a system, secure domain router, or node.

Defaults

Displays active packages for the system.

Command Modes

EXEC
Administration EXEC

Command History

Release	Modification
Release 2.0	This command was introduced on the Cisco CRS-1 router.
Release 3.0	No modification.
Release 3.2	This command was first supported on the Cisco XR 12000 Series Router. The command was moved from EXEC mode to Administration EXEC mode.
Release 3.3.0	Support was added for the optional keywords and arguments: summary, detail and sdr sdr-name.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

---

Note This command displays output that is similar to the show install active command.

---

Displaying Information for a Specific Node

Use the location keyword and node-id argument to display information for a specific node. If you do not specify a location with the location keyword and node-id argument, this command displays information from all nodes.

Displaying the Default SDR Software Profile

When an SDR is created, the nodes assigned to that SDR are configured with the default software profile. To view a summary of the default SDR software configuration, enter the show install summary command. 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.

Displaying Information for a Specific SDR

Use the sdr keyword and sdr-name argument to display information for a specific SDR.

Task ID

Task ID	Operations
pkg-mgmt	read

Examples

Use the location node-id keyword and argument to display the active packages for a designated node.

RP/0/RP0/CPU0:router# show install location 0/rp0/cpu0

  Node 0/RP0/CPU0 [RP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/mbihfr-rp.vm

    Active Packages: 

      disk0:hfr-diags-3.3.30

      disk0:hfr-mgbl-3.3.30

      disk0:hfr-k9sec-3.3.30

      disk0:comp-hfr-mini-3.3.30

Use the summary keyword to display a summary of the active packages in the system. This command 
also shows the default software profile used for new SDRs.

RP/0/RP0/CPU0:router# show install summary 

Default Profile:

  SDRs:

    Owner

    sdr1

  Active Packages:

    disk0:c12k-sbc-3.3.0

    disk0:c12k-diags-3.3.0

    disk0:c12k-mgbl-3.3.0

    disk0:c12k-mcast-3.3.0

    disk0:c12k-mpls-3.3.0

    disk0:c12k-k9sec-3.3.0

    disk0:c12k-mini-3.3.0

Table 1 describes the significant fields shown in the display.

Table 1 show install Field Descriptions 

Field	Description
Boot Image:	Active Minimum Boot Image (MBI) used to boot the node.
Active Packages:	Active packages loaded on the node.

Related Commands

Command	Description
install activate	Adds a software package or an SMU to the active software set.
show install active	Displays active packages.
show install package	Displays information about a package.
show install pie-info	Displays information on the packages contained in a PIE file.
show install which	Displays the origin of a component, package, or file.

show install active

To display active packages, use the show install active command in EXEC mode or Administration EXEC mode.

show install active [sdr sdr-name | location node-id] [[detail [sdr sdr-name | location node-id] [summary [sdr sdr-name]] [[verbose [sdr sdr-name | location node-id]

Syntax Description

sdr sdr-name	(Optional) Displays the active packages for a specific secure domain router (SDR). The sdr-name argument is the name assigned to the secure domain router. This option is available from Administration EXEC mode only.
location node-id	(Optional) Displays the active packages for a designated node. The node-id argument is expressed in the rack/slot/module notation.
summary	(Optional) Displays a summary of the active packages in a system or secure domain router.
detail	(Optional) Displays a detailed summary of the active packages for a system, secure domain router, or node.
verbose	(Optional) Displays a detailed summary of the active packages for a system, secure domain router, or node, including component and file information for each package.

Defaults

No default behavior or values

Command Modes

EXEC
Administration EXEC

Command History

Release	Modification
Release 2.0	This command was introduced on the Cisco CRS-1.
Release 3.0	No modification.
Release 3.2	This command was first supported on the Cisco XR 12000 Series Router. The command was made available in Administration EXEC mode. The detail keyword was added.
Release 3.3.0	Support was added for the optional keywords and arguments: detail, verbose, and sdr sdr-name.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Use the show install active command to display the active software set from all nodes. If you do not specify a node with the location keyword and node-id argument, this command displays the active software set from all nodes.

When run in Administration EXEC mode, this command displays data for the entire system. When run in the EXEC mode of a secure domain router this command displays data for that secure domain router only.

Use the location keyword and node-id argument to display information for a specific node. If you do not specify a location with the location keyword and node-id argument, this command displays information from all nodes.

Use the sdr keyword and sdr-name argument to display information for a specific secure domain router.

Use the summary keyword to display a summary of the committed packages in a system or secure domain router. Use the detail keyword to display a summary of the committed packages in a system, secure domain router, or node.

---

Note This command displays output that is similar to the show install command.

---

Task ID

Task ID	Operations
pkg-mgmt	read

Examples

The following is sample output from the show install active command with the location keyword and node-id argument specified:

The following is sample output from the show install active command with the summary keyword specified:

RP/0/RP0/CPU0:router(admin)#show install active summary         

Default Profile:

  SDRs:

    Owner

    CE1b

Active Packages:

    disk0:hfr-diags-3.3.30

    disk0:hfr-mgbl-3.3.30

    disk0:hfr-k9sec-3.3.30

    disk0:comp-hfr-mini-3.3.30

The following is sample output from the show install active summary command for a specific SDR:

RP/0/RP0/CPU0:router(admin)# show install active summary sdr owner

Active Packages:

    disk0:hfr-diags-3.3.30

    disk0:hfr-mgbl-3.3.30

    disk0:hfr-k9sec-3.3.30

    disk0:comp-hfr-mini-3.3.30

The following is sample output from the show install active command for a specific SDR:

RP/0/RP0/CPU0:router(admin)#show install active SDR Owner

RP/0/RP0/CPU0:router(admin)#show install active SDR Owner

  Node 0/1/SP [SP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/sp/mbihfr-sp.vm

    Active Packages: 

      disk0:hfr-diags-3.3.30

      disk0:comp-hfr-mini-3.3.30

  Node 0/1/CPU0 [LC] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/lc/mbihfr-lc.vm

    Active Packages: 

      disk0:hfr-diags-3.3.30

      disk0:comp-hfr-mini-3.3.30

  Node 0/6/SP [SP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/sp/mbihfr-sp.vm

    Active Packages: 

      disk0:hfr-diags-3.3.30

      disk0:comp-hfr-mini-3.3.30

  Node 0/6/CPU0 [LC] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/lc/mbihfr-lc.vm

    Active Packages: 

      disk0:hfr-diags-3.3.30

      disk0:comp-hfr-mini-3.3.30

  Node 0/RP0/CPU0 [RP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/mbihfr-rp.vm

    Active Packages: 

      disk0:hfr-diags-3.3.30

      disk0:hfr-mgbl-3.3.30

      disk0:hfr-k9sec-3.3.30

      disk0:comp-hfr-mini-3.3.30

  Node 0/RP1/CPU0 [RP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/mbihfr-rp.vm

    Active Packages: 

      disk0:hfr-diags-3.3.30

      disk0:hfr-mgbl-3.3.30

      disk0:hfr-k9sec-3.3.30

      disk0:comp-hfr-mini-3.3.30

  Node 0/SM0/SP [SP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/sp/mbihfr-sp.vm

    Active Packages: 

      disk0:hfr-diags-3.3.30

      disk0:comp-hfr-mini-3.3.30

  Node 0/SM1/SP [SP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/sp/mbihfr-sp.vm

    Active Packages: 

      disk0:hfr-diags-3.3.30

      disk0:comp-hfr-mini-3.3.30

  Node 0/SM2/SP [SP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/sp/mbihfr-sp.vm

    Active Packages: 

      disk0:hfr-diags-3.3.30

      disk0:comp-hfr-mini-3.3.30

  Node 0/SM3/SP [SP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/sp/mbihfr-sp.vm

    Active Packages: 

      disk0:hfr-diags-3.3.30

      disk0:comp-hfr-mini-3.3.30

Table 2 describes the significant fields shown in the display.

Table 2 show install active Field Descriptions 

Field	Description
Boot Image:	Active Minimum Boot Image (MBI) used to boot the node.
Active Packages:	Active packages loaded on the node.

Related Commands

Command	Description
install activate	Adds a software package or an SMU to the active software set.
show install	Displays active packages.
show install package	Displays information about a package.
show install pie-info	Displays information on the packages contained in a PIE file.
show install which	Searches for a component, package, or file.

show install committed

To display committed software packages, use the show install committed command in EXEC mode or in Administration EXEC mode.

show install committed [sdr sdr-name] [location node-id] [[detail [sdr sdr-name | location node-id]] [[summary [sdr sdr-name]] [[verbose [sdr sdr-name | location node-id]

Syntax Description

sdr sdr-name	(Optional) Displays the committed packages for a specific secure domain router (SDR). The sdr-name argument is the name assigned to the secure domain router.
location node-id	(Optional) Displays the committed packages for a designated node. The node-id argument is expressed in the rack/slot/module notation.
summary	(Optional) Displays a summary of the committed packages in a system or secure domain router.
detail	(Optional) Displays a detailed summary of the committed packages for a system, secure domain router, or node.
verbose	(Optional) Displays a detailed summary of the committed packages for a system, secure domain router, or node, including component and file information for each package.

Defaults

No default behavior or values

Command Modes

Administration EXEC
EXEC

Command History

Release	Modification
Release 2.0	This command was introduced on the Cisco CRS-1 router.
Release 3.0	No modification.
Release 3.2	This command was first supported on the Cisco XR 12000 Series Router. The command was moved from EXEC mode to Administration EXEC mode.
Release 3.3.0	This command was supported in both EXEC mode and Administration EXEC mode. Support was removed for the all keyword. Support was added for the keywords and arguments: sdr sdr-name, detail, summary, and verbose.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Use the show install committed command to display the software committed using the install commit command. This command is useful for verifying that the desired set of packages is committed.

Use the location keyword and node-id argument to display information for a specific node. If you do not specify a location with the location keyword and node-id argument, this command displays information from all nodes.

Use the sdr keyword and sdr-name argument to display information for a specific secure domain router.

Use the summary keyword to display a summary of the committed packages in a system or secure domain router. Use the detail keyword to display a summary of the committed packages in a system, secure domain router, or node.

Task ID

Task ID	Operations
pkg-mgmt	read

Examples

The following is sample output from the show install committed command:

RP/0/RP0/CPU0:router# show install committed 

Secure Domain Router: Owner

  Node 0/1/SP [SP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/sp/mbihfr-sp.vm

    Committed Packages: 

      disk0:hfr-diags-3.3.30

      disk0:comp-hfr-mini-3.3.30

  Node 0/1/CPU0 [LC] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/lc/mbihfr-lc.vm

    Committed Packages: 

      disk0:hfr-diags-3.3.30

      disk0:comp-hfr-mini-3.3.30

  Node 0/6/SP [SP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/sp/mbihfr-sp.vm

    Committed Packages: 

      disk0:hfr-diags-3.3.30

      disk0:comp-hfr-mini-3.3.30

  Node 0/6/CPU0 [LC] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/lc/mbihfr-lc.vm

    Committed Packages: 

      disk0:hfr-diags-3.3.30

      disk0:comp-hfr-mini-3.3.30

  Node 0/RP0/CPU0 [RP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/mbihfr-rp.vm

    Committed Packages: 

      disk0:hfr-diags-3.3.30

      disk0:hfr-mgbl-3.3.30

      disk0:hfr-k9sec-3.3.30

      disk0:comp-hfr-mini-3.3.30

  Node 0/RP1/CPU0 [RP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/mbihfr-rp.vm

    Committed Packages: 

      disk0:hfr-diags-3.3.30

      disk0:hfr-mgbl-3.3.30

      disk0:hfr-k9sec-3.3.30

      disk0:comp-hfr-mini-3.3.30

  Node 0/SM0/SP [SP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/sp/mbihfr-sp.vm

    Committed Packages: 

      disk0:hfr-diags-3.3.30

      disk0:comp-hfr-mini-3.3.30

  Node 0/SM1/SP [SP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/sp/mbihfr-sp.vm

    Committed Packages: 

      disk0:hfr-diags-3.3.30

      disk0:comp-hfr-mini-3.3.30

  Node 0/SM2/SP [SP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/sp/mbihfr-sp.vm

    Committed Packages: 

      disk0:hfr-diags-3.3.30

      disk0:comp-hfr-mini-3.3.30

  Node 0/SM3/SP [SP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/sp/mbihfr-sp.vm

    Committed Packages: 

      disk0:hfr-diags-3.3.30

      disk0:comp-hfr-mini-3.3.30

Table 3 describes the significant fields shown in the display.

Table 3 show install committed Field Descriptions 

Field	Description
Boot Image:	Active Minimum Boot Image (MBI) committed on the node.
Active Packages:	Active packages committed on the node.

Related Commands

Command	Description
install activate	Adds a software package or SMU to the active software set.
install commit	Makes the current active software set persistent across reloads.
show install	Displays active packages.
show install active	Displays active packages.
show install package	Displays information about a package.
show install pie-info	Displays information on the packages contained in a PIE file.
show install which	Displays the origin of a component, package, or file.

show install inactive

To display inactive packages, use the show install inactive command in EXEC mode or in Administration EXEC mode.

show install inactive [sdr sdr-name | location node-id] [detail | verbose]

Syntax Description

sdr sdr-name	(Optional) Displays the inactive packages for a specific secure domain router (SDR). The sdr-name argument is the name assigned to the secure domain router. This option is available from Administration EXEC mode only.
location node-id	(Optional) Displays the inactive software set from a designated node. The node-id argument is expressed in the rack/slot/module notation.
detail	(Optional) Displays summary and component information for inactive packages.
verbose	(Optional) Displays summary, component, and file information for inactive packages.

Defaults

No default behavior or values

Command Modes

EXEC
Administration EXEC

Command History

Release	Modification
Release 2.0	This command was introduced on the Cisco CRS-1.
Release 3.0	No modification.
Release 3.2	This command was first supported on the Cisco XR 12000 Series Router. The command was made available in Administration EXEC mode. The components, files, and none keywords were removed and replaced by the detail, verbose, and brief keywords, respectively. The summary keyword was removed. The default output display was changed to match the output that displayed when the optional summary keyword was entered in previous releases.
Release 3.3.0	No modification.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Task ID

Task ID	Operations
pkg-mgmt	read

Examples

The following is sample output from the show install inactive command:

RP/0/RP0/CPU0:router# show install inactive 

Secure Domain Router: Owner

  Node 0/1/SP [SP] [SDR: Owner]

    Inactive Packages:

      disk0:hfr-fwdg-3.3.30

      disk0:hfr-lc-3.3.30

      disk0:hfr-mcast-3.3.30

      disk0:hfr-mpls-3.3.30

      disk0:hfr-rout-3.3.30

      disk0:hfr-mgbl-3.3.30

      disk0:hfr-k9sec-3.3.30

  Node 0/1/CPU0 [LC] [SDR: Owner]

    Inactive Packages:

      disk0:hfr-rout-3.3.30

      disk0:hfr-mgbl-3.3.30

      disk0:hfr-k9sec-3.3.30

  Node 0/6/SP [SP] [SDR: Owner]

    Inactive Packages:

      disk0:hfr-fwdg-3.3.30

      disk0:hfr-lc-3.3.30

      disk0:hfr-mcast-3.3.30

      disk0:hfr-mpls-3.3.30

      disk0:hfr-rout-3.3.30

      disk0:hfr-mgbl-3.3.30

      disk0:hfr-k9sec-3.3.30

  Node 0/6/CPU0 [LC] [SDR: Owner]

    Inactive Packages:

      disk0:hfr-rout-3.3.30

      disk0:hfr-mgbl-3.3.30

      disk0:hfr-k9sec-3.3.30

  Node 0/RP0/CPU0 [RP] [SDR: Owner]

    Inactive Packages:

      None.

  Node 0/RP1/CPU0 [RP] [SDR: Owner]

    Inactive Packages:

      None.

  Node 0/SM0/SP [SP] [SDR: Owner]

    Inactive Packages:

      disk0:hfr-fwdg-3.3.30

      disk0:hfr-lc-3.3.30

      disk0:hfr-mcast-3.3.30

      disk0:hfr-mpls-3.3.30

      disk0:hfr-rout-3.3.30

      disk0:hfr-mgbl-3.3.30

      disk0:hfr-k9sec-3.3.30

  Node 0/SM1/SP [SP] [SDR: Owner]

    Inactive Packages:

      disk0:hfr-fwdg-3.3.30

      disk0:hfr-lc-3.3.30

      disk0:hfr-mcast-3.3.30

      disk0:hfr-mpls-3.3.30

      disk0:hfr-rout-3.3.30

      disk0:hfr-mgbl-3.3.30

      disk0:hfr-k9sec-3.3.30

  Node 0/SM2/SP [SP] [SDR: Owner]

    Inactive Packages:

      disk0:hfr-fwdg-3.3.30

      disk0:hfr-lc-3.3.30

      disk0:hfr-mcast-3.3.30

      disk0:hfr-mpls-3.3.30

      disk0:hfr-rout-3.3.30

      disk0:hfr-mgbl-3.3.30

      disk0:hfr-k9sec-3.3.30

  Node 0/SM3/SP [SP] [SDR: Owner]

    Inactive Packages:

      disk0:hfr-fwdg-3.3.30

      disk0:hfr-lc-3.3.30

      disk0:hfr-mcast-3.3.30

      disk0:hfr-mpls-3.3.30

      disk0:hfr-rout-3.3.30

      disk0:hfr-mgbl-3.3.30

      disk0:hfr-k9sec-3.3.30

The following is sample output from the show install inactive command with the summary keyword:

RP/0/RP0/CPU0:router# show install inactive summary 

Default Profile:

  SDRs:

    Owner

  Inactive Packages:

    None.

The following is sample output from the show install inactive command with the detail keyword:

RP/0/RP0/CPU0:router# show install inactive detail 

Secure Domain Router: Owner

  Node 0/1/SP [SP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/sp/mbihfr-sp.vm

    Active Packages: 

      disk0:hfr-diags-3.3.30

      disk0:comp-hfr-full-3.3.30

        disk0:hfr-admin-3.3.30

        disk0:hfr-base-3.3.30

        disk0:hfr-os-mbi-3.3.30

  Node 0/1/CPU0 [LC] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/lc/mbihfr-lc.vm

    Active Packages: 

      disk0:hfr-diags-3.3.30

      disk0:comp-hfr-full-3.3.30

        disk0:hfr-mcast-3.3.30

        disk0:hfr-mpls-3.3.30

        disk0:hfr-lc-3.3.30

        disk0:hfr-fwdg-3.3.30

        disk0:hfr-admin-3.3.30

        disk0:hfr-base-3.3.30

        disk0:hfr-os-mbi-3.3.30

  Node 0/6/SP [SP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/sp/mbihfr-sp.vm

    Active Packages: 

      disk0:hfr-diags-3.3.30

      disk0:comp-hfr-full-3.3.30

        disk0:hfr-admin-3.3.30

        disk0:hfr-base-3.3.30

        disk0:hfr-os-mbi-3.3.30

  Node 0/6/CPU0 [LC] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/lc/mbihfr-lc.vm

    Active Packages: 

      disk0:hfr-diags-3.3.30

      disk0:comp-hfr-full-3.3.30

        disk0:hfr-mcast-3.3.30

        disk0:hfr-mpls-3.3.30

        disk0:hfr-lc-3.3.30

        disk0:hfr-fwdg-3.3.30

        disk0:hfr-admin-3.3.30

        disk0:hfr-base-3.3.30

        disk0:hfr-os-mbi-3.3.30

  Node 0/RP0/CPU0 [RP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/mbihfr-rp.vm

    Active Packages: 

      disk0:hfr-diags-3.3.30

      disk0:hfr-mgbl-3.3.30

      disk0:hfr-k9sec-3.3.30

      disk0:comp-hfr-full-3.3.30

        disk0:hfr-mcast-3.3.30

        disk0:hfr-mpls-3.3.30

        disk0:hfr-rout-3.3.30

        disk0:hfr-lc-3.3.30

        disk0:hfr-fwdg-3.3.30

        disk0:hfr-admin-3.3.30

        disk0:hfr-base-3.3.30

        disk0:hfr-os-mbi-3.3.30

  Node 0/RP1/CPU0 [RP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/mbihfr-rp.vm

    Active Packages: 

      disk0:hfr-diags-3.3.30

      disk0:hfr-mgbl-3.3.30

      disk0:hfr-k9sec-3.3.30

      disk0:comp-hfr-full-3.3.30

        disk0:hfr-mcast-3.3.30

        disk0:hfr-mpls-3.3.30

        disk0:hfr-rout-3.3.30

        disk0:hfr-lc-3.3.30

        disk0:hfr-fwdg-3.3.30

        disk0:hfr-admin-3.3.30

        disk0:hfr-base-3.3.30

        disk0:hfr-os-mbi-3.3.30

  Node 0/SM0/SP [SP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/sp/mbihfr-sp.vm

    Active Packages: 

      disk0:hfr-diags-3.3.30

      disk0:comp-hfr-full-3.3.30

        disk0:hfr-admin-3.3.30

        disk0:hfr-base-3.3.30

        disk0:hfr-os-mbi-3.3.30

  Node 0/SM1/SP [SP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/sp/mbihfr-sp.vm

    Active Packages: 

      disk0:hfr-diags-3.3.30

      disk0:comp-hfr-full-3.3.30

        disk0:hfr-admin-3.3.30

        disk0:hfr-base-3.3.30

        disk0:hfr-os-mbi-3.3.30

  Node 0/SM2/SP [SP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/sp/mbihfr-sp.vm

    Active Packages: 

      disk0:hfr-diags-3.3.30

      disk0:comp-hfr-full-3.3.30

        disk0:hfr-admin-3.3.30

        disk0:hfr-base-3.3.30

        disk0:hfr-os-mbi-3.3.30

  Node 0/SM3/SP [SP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/sp/mbihfr-sp.vm

    Active Packages: 

      disk0:hfr-diags-3.3.30

      disk0:comp-hfr-full-3.3.30

        disk0:hfr-admin-3.3.30

        disk0:hfr-base-3.3.30

        disk0:hfr-os-mbi-3.3.30

The following is sample output from the show install inactive command with the location keyword and node-id argument:

RP/0/RP0/CPU0:router# show install inactive location 0/2/cpu0

Node 0/RP0/CPU0 [RP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/mbihfr-rp.vm

    Active Packages: 

      disk0:hfr-diags-3.3.30

      disk0:hfr-mgbl-3.3.30

      disk0:hfr-k9sec-3.3.30

      disk0:comp-hfr-full-3.3.30

Table 4 describes the significant fields shown in the display.

Table 4 show install inactive Field Descriptions 

Field	Description
disk0:hfr-mgbl-3.3.30	Storage device and the name of the package that is inactive.
hfr-mgbl V3.3.30 Manageability Package	Name of the package that is inactive.
Vendor	Name of the manufacturer.
Desc	Name of the package.
Build	The date and time when the inactive package was built.
Source	The source directory where the inactive package was built.

Related Commands

Command	Description
install deactivate	Removes a package from the active software set.
show install package	Displays information about a package.
show install pie-info	Displays information on the packages contained in a PIE file.
show install which	Displays the origin of a component, package, or file.

show install log

To display the details of installation requests, use the show install log command in Administration EXEC mode.

show install log [request-id] [detail | verbose]

Syntax Description

request-id	(Optional) Request ID assigned to an installation operation.
detail	(Optional) Displays detailed information for all previous installs for all request-ids, or for a specific request-id.
verbose	(Optional) Displays verbose information for all previous installs for all request-ids, or for a specific request-id.

Defaults

No default behavior or values

Command Modes

Administration EXEC

Command History

Release	Modification
Release 2.0	This command was introduced on the Cisco CRS-1 router.
Release 3.0	No modification.
Release 3.2	This command was first supported on the Cisco XR 12000 Series Router. The command was moved from EXEC mode to Administration EXEC mode.
Release 3.3.0	Support was added for the keywords detail and verbose.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Use the show install log command to display the details of each install request, including the changes to files and the processes impacted by each request.

The show install log command with no arguments displays a summary of all installation operations. Specify the request-id argument to display details for a specific operation.

---

Note Issue this command with the installation commands that support the test keyword when previewing the effects of an installation command without impacting the running system. The install activate, install deactivate, install remove, and install rollback to commands support the test keyword.

---

Use the show install log detail command to display detailed information for all previous installs. The detailed information is a subset of show install log verbose information.

Specify the request-id argument to display details for a specific operation. The request-id argument is listed beside each operation in the show install log summary and is also attached to messages from that operation. For example, the third installation operation has "Install 3:" attached to all of its status messages.

Task ID

Task ID	Operations
pkg-mgmt	read

Examples

The following example displays information for all install requests:

RP/0/RP1/CPU0:router(admin)# show install log 

Install operation 1 started by user 'cisco' at 09:14:49 UTC Tue Mar 28 2006.

    install add /disk1:hfr-k9sec-p.pie-3.3.90.1I

    /disk1:hfr-mcast-p.pie-3.3.90.1I /disk1:hfr-mgbl-p.pie-3.3.90.1I

    Install operation 1 completed successfully at 09:15:57 UTC Tue Mar 28 2006.

Install operation 2 started by user 'cisco' at 09:16:53 UTC Tue Mar 28 2006.

    install activate disk0:hfr-k9sec-3.3.90 disk0:hfr-mcast-3.3.90

    disk0:hfr-mgbl-3.3.90

    Install operation 2 completed successfully at 09:17:34 UTC Tue Mar 28 2006.

Install operation 3 started by user 'cisco' at 09:19:42 UTC Tue Mar 28 2006.

    install add /disk1:hfr-diags-p.pie-3.3.90.1I

    Install operation 3 completed successfully at 09:20:13 UTC Tue Mar 28 2006.

Install operation 4 started by user 'cisco' at 09:20:26 UTC Tue Mar 28 2006.

    install activate disk0:hfr-diags-3.3.90

    Install operation 4 completed successfully at 09:21:05 UTC Tue Mar 28 2006.

Install operation 5 started by user 'cisco' at 09:21:34 UTC Tue Mar 28 2006.

    install commit

    Install operation 5 completed successfully at 09:21:36 UTC Tue Mar 28 2006.

Install operation 6 started by user 'lab' at 16:30:53 UTC Sat Apr 08 2006.

    install verify

    Install operation 6 completed successfully at 16:36:15 UTC Sat Apr 08 2006.

Install operation 7 started by user 'lab' at 17:04:06 UTC Sat Apr 08 2006.

    install verify synchronous

    Install operation 7 completed successfully at 17:09:29 UTC Sat Apr 08 2006.

Install operation 8 started by user 'lab' at 17:58:34 UTC Sat Apr 08 2006.

    install remove inactive

    Install operation 8 failed at 17:58:34 UTC Sat Apr 08 2006.

Install operation 9 started by user 'lab' at 17:59:23 UTC Sat Apr 08 2006.

    install deactivate disk0:hfr-mpls-3.3.90

    Install operation 9 completed successfully at 18:05:17 UTC Sat Apr 08 2006.

Install operation 10 started by user 'lab' at 18:06:22 UTC Sat Apr 08 2006.

    install activate disk0:hfr-mpls-3.3.90

    Install operation 10 completed successfully at 18:07:09 UTC Sat Apr 08

    2006.

Install operation 11 started by user 'lab' at 18:11:19 UTC Sat Apr 08 2006.

    clear install rollback oldest 2

    Install operation 11 completed successfully at 18:11:21 UTC Sat Apr 08

    2006.

Install operation 12 started by user 'lab' at 18:17:21 UTC Sat Apr 08 2006.

    install activate disk0:hfr-mpls-3.3.90

    Install operation 12 failed at 18:17:26 UTC Sat Apr 08 2006.

Install operation 13 started by user 'lab' at 18:37:22 UTC Sat Apr 08 2006.

    install activate disk0:hfr-mpls-3.3.90

    Install operation 13 failed at 18:37:24 UTC Sat Apr 08 2006.

Install operation 14 started by user 'lab' at 18:38:37 UTC Sat Apr 08 2006.

    install deactivate disk0:hfr-mpls-3.3.90 synchronous

    Install operation 14 completed successfully at 18:39:20 UTC Sat Apr 08

    2006.

Install operation 15 started by user 'lab' at 19:15:33 UTC Sat Apr 08 2006.

    install activate disk0:hfr-mpls-3.3.90 synchronous

    Install operation 15 completed successfully at 19:16:18 UTC Sat Apr 08

    2006.

Install operation 16 started by user 'lab' at 19:18:58 UTC Sat Apr 08 2006.

    install commit

    Install operation 16 completed successfully at 19:19:01 UTC Sat Apr 08

    2006.

Install operation 17 started by user 'lab' at 19:22:15 UTC Sat Apr 08 2006.

    install deactivate disk0:hfr-mpls-3.3.90

    Install operation 17 completed successfully at 19:22:59 UTC Sat Apr 08

    2006.

Install operation 18 started by user 'lab' at 19:23:28 UTC Sat Apr 08 2006.

    install activate disk0:hfr-mpls-3.3.90

    Install operation 18 completed successfully at 19:24:13 UTC Sat Apr 08

    2006.

Install operation 19 started by user 'lab' at 23:46:10 UTC Sat Apr 08 2006.

    install add /disk1:hfr-mpls-p.pie-3.3.90 synchronous

    Install operation 19 failed at 23:46:10 UTC Sat Apr 08 2006.

Install operation 20 started by user 'lab' at 23:46:36 UTC Sat Apr 08 2006.

    install add /disk1:hfr-mpls-p.pie synchronous

    Install operation 20 failed at 23:46:36 UTC Sat Apr 08 2006.

Install operation 21 started by user 'lab' at 23:47:32 UTC Sat Apr 08 2006.

    install add /disk1:hfr-mcast-p.pie-3.3.90.I

    Install operation 21 failed at 23:47:32 UTC Sat Apr 08 2006.

Install operation 22 started by user 'lab' at 23:47:51 UTC Sat Apr 08 2006.

    install add /disk1:/hfr-mcast-p.pie-3.3.90.I

    Install operation 22 failed at 23:47:51 UTC Sat Apr 08 2006.

Install operation 23 started by user 'lab' at 23:48:57 UTC Sat Apr 08 2006.

    install rollback to committed

    Install operation 23 failed at 23:49:03 UTC Sat Apr 08 2006.

Install operation 24 started by user 'lab' at 23:50:11 UTC Sat Apr 08 2006.

    install rollback to 18

    Install operation 24 failed at 23:50:15 UTC Sat Apr 08 2006.

Install operation 25 started by user 'lab' at 23:01:38 UTC Sat Apr 15 2006.

    install deactivate disk0:hfr-diags-3.3.90 on node 0/6/CPU0

    Install operation 25 failed at 23:01:44 UTC Sat Apr 15 2006.

Install operation 26 started by user 'lab' at 23:29:08 UTC Sat Apr 15 2006.

    install remove inactive

    Install operation 26 failed at 23:29:08 UTC Sat Apr 15 2006.

Install operation 27 started by user 'lab' at 23:29:37 UTC Sat Apr 15 2006.

    install deactivate disk0:hfr-diags-3.3.90

    Install operation 27 completed successfully at 23:30:22 UTC Sat Apr 15

    2006.

Install operation 28 started by user 'lab' at 23:35:39 UTC Sat Apr 15 2006.

    install remove inactive

    Install operation 28 failed at 23:35:39 UTC Sat Apr 15 2006.

Install operation 29 started by user 'lab' at 23:39:21 UTC Sat Apr 15 2006.

    install commit

    Install operation 29 completed successfully at 23:39:24 UTC Sat Apr 15

    2006.

Install operation 30 started by user 'lab' at 23:40:22 UTC Sat Apr 15 2006.

    install remove disk0:hfr-diags-3.3.90 test

    Install operation 30 completed successfully at 23:40:45 UTC Sat Apr 15

    2006.

Install operation 31 started by user 'lab' at 23:59:12 UTC Sat Apr 15 2006.

    install remove inactive

    Install operation 31 completed successfully at 23:59:28 UTC Sat Apr 15

    2006.

31 entries shown (max log size 50 entries)

The following example displays the details for a specific install request:

RP/0/RP1/CPU0:router(admin)# show install log 31

Install operation 31 started by user 'lab' at 23:59:12 UTC Sat Apr 15 2006.

    install remove inactive

    Install operation 31 completed successfully at 23:59:28 UTC Sat Apr 15

    2006.

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 verbose                        

Install 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.07

Install 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.1I

    Info:         disk0:hfr-k9sec-3.4.0.1I

    Info:         disk0:hfr-mcast-3.4.0.1I

    Info:         disk0:hfr-mgbl-3.4.0.1I

    Info:         disk0:hfr-mpls-3.4.0.1I

    Info:      

    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.1I

disk0:hfr-mcast-3.4.0.1I disk0:hfr-mgbl-3.4.0.1I disk0:hfr-mpls-3.4.0.1I

Install operation 2 completed successfully at 18:07:48 UTC Sat Jun 03 2006.

Summary:

    Install method: parallel

    Summary 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.1I

        No processes affected

    Summary of changes on nodes 0/1/CPU0, 0/6/CPU0:

        Activated:    hfr-diags-3.4.0.1I

                      hfr-mcast-3.4.0.1I

                      hfr-mpls-3.4.0.1I

            1 hfr-mpls processes affected (0 updated, 1 added, 0 removed, 0

    impacted)

            2 hfr-mcast processes affected (0 updated, 2 added, 0 removed, 0

    impacted)

    Summary of changes on nodes 0/RP0/CPU0, 0/RP1/CPU0:

        Activated:    hfr-diags-3.4.0.1I

                      hfr-k9sec-3.4.0.1I

                      hfr-mcast-3.4.0.1I

                      hfr-mgbl-3.4.0.1I

                      hfr-mpls-3.4.0.1I

            6 hfr-mgbl processes affected (0 updated, 6 added, 0 removed, 0

    impacted)

            8 hfr-mpls processes affected (0 updated, 8 added, 0 removed, 0

    impacted)

            7 hfr-k9sec processes affected (0 updated, 7 added, 0 removed, 0

    impacted)

            14 hfr-mcast processes affected (0 updated, 14 added, 0 removed, 0

    impacted)

Install logs:

    Install operation 2 'install activate disk0:hfr-diags-3.4.0.1I

    disk0:hfr-k9sec-3.4.0.1I disk0:hfr-mcast-3.4.0.1I disk0:hfr-mgbl-3.4.0.1I

    disk0:hfr-mpls-3.4.0.1I' started by user 'labuser' at 18:06:32 UTC Sat Jun

    03 2006.

    Info:     The changes made to software configurations will not be

    Info:     persistent across system reloads. Use the command 'admin install

    Info:     commit' to make changes persistent.

    Info:     Please verify that the system is consistent following the

    Info:     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 detail 

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.1I

disk0:hfr-mcast-3.4.0.1I disk0:hfr-mgbl-3.4.0.1I disk0:hfr-mpls-3.4.0.1I

Install operation 2 completed successfully at 18:07:48 UTC Sat Jun 03 2006.

Summary:

    Install method: parallel

    Summary 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.1I

        No processes affected

    Summary of changes on nodes 0/1/CPU0, 0/6/CPU0:

        Activated:    hfr-diags-3.4.0.1I

                      hfr-mcast-3.4.0.1I

                      hfr-mpls-3.4.0.1I

            1 hfr-mpls processes affected (0 updated, 1 added, 0 removed, 0

    impacted)

            2 hfr-mcast processes affected (0 updated, 2 added, 0 removed, 0

    impacted)

    Summary of changes on nodes 0/RP0/CPU0, 0/RP1/CPU0:

        Activated:    hfr-diags-3.4.0.1I

                      hfr-k9sec-3.4.0.1I

                      hfr-mcast-3.4.0.1I

                      hfr-mgbl-3.4.0.1I

                      hfr-mpls-3.4.0.1I

            6 hfr-mgbl processes affected (0 updated, 6 added, 0 removed, 0

    impacted)

            8 hfr-mpls processes affected (0 updated, 8 added, 0 removed, 0

    impacted)

            7 hfr-k9sec processes affected (0 updated, 7 added, 0 removed, 0

    impacted)

            14 hfr-mcast processes affected (0 updated, 14 added, 0 removed, 0

    impacted)

Install logs:

    Install operation 2 'install activate disk0:hfr-diags-3.4.0.1I

    disk0:hfr-k9sec-3.4.0.1I disk0:hfr-mcast-3.4.0.1I disk0:hfr-mgbl-3.4.0.1I

    disk0:hfr-mpls-3.4.0.1I' started by user 'labuser' at 18:06:32 UTC Sat Jun

    03 2006.

    Info:     The changes made to software configurations will not be

    Info:     persistent across system reloads. Use the command 'admin install

    Info:     commit' to make changes persistent.

    Info:     Please verify that the system is consistent following the

    Info:     software change using the following commands:

    Info:         show system verify

    Info:         install verify

    Install operation 2 completed successfully at 18:07:48 UTC Sat Jun 03 2006.

Related Commands

Command	Description
install activate	Adds a software package or SMU to the active software set.
install add	Installs a package on a storage device.
install commit	Makes the current active software set persistent across reloads.
install deactivate	Removes a package from the active software set.
install remove	Deletes inactive packages from a storage device.
install rollback to	Rolls back the software set to a saved installation point or to the last committed installation point.
install verify	Verifies the consistency of a previously installed software set with the package file from which it originated.

show install package

To display information about a package, use the show install package command in EXEC mode or Administration EXEC mode.

show install package {device:package | all} [brief | detail | verbose]

Syntax Description

device:package	Device and package, expressed in concatenated form (for example, disk0:hfr-mgbl-1.0.0). For the device argument, the value is disk0:.
all	Displays all installed packages on the system.
brief	(Optional) Displays only the name and version of packages.
detail	(Optional) Displays summary and component information for packages.
verbose	(Optional) Displays summary, component, and file information for packages.

Defaults

No default behavior or values

Command Modes

EXEC
Administration EXEC

Command History

Release	Modification
Release 2.0	This command was introduced on the Cisco CRS-1.
Release 3.0	No modification.
Release 3.2	This command was first supported on the Cisco XR 12000 Series Router. The command was made available in Administration EXEC mode. The components, files, and none keywords were removed and replaced by the detail, verbose, and brief keywords, respectively. The summary keyword was removed. The default output display was changed to match the output that displayed when the optional summary keyword was entered in previous releases.
Release 3.3.0	No modification.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Use the show install package command to display information about packages. The output displays the version of the package, name of the manufacturer, name of the package, date and time when the package was built, and source directory where the package was built.

This command returns the same data in EXEC mode and Administration EXEC mode.

For additional information about the status of installed software packages, use the show install active and show install inactive commands.

Task ID

Task ID	Operations
pkg-mgmt	read

Examples

The following is sample output from the show install package command:

RP/0/RP0/CPU0:router(admin)#show install package disk0:comp-hfr-full-3.3.30

disk0:comp-hfr-full-3.3.30

    disk0:hfr-rout-3.3.30

    disk0:hfr-mcast-3.3.30

    disk0:hfr-mpls-3.3.30

    disk0:hfr-lc-3.3.30

    disk0:hfr-fwdg-3.3.30

    disk0:hfr-admin-3.3.30

    disk0:hfr-base-3.3.30

    disk0:hfr-os-mbi-3.3.30

Table 5 describes the significant fields shown in the display.

Table 5 show install package Field Descriptions 

Field	Description
disk0:hfr-rout-3.3.30	Storage device and the name of the package that has been installed.
hfr-rout V3.3.30 Routing Package	Name of the package.
Vendor	Name of the manufacturer.
Desc	Name of the package.
Build	Date and time the package was built.
Source	Source directory where the package was built.

The following is sample output from the show install package command with the all keyword:

RP/0/RP0/CPU0:router# show install package all

disk0:comp-hfr-full-3.3.30

    disk0:hfr-admin-3.3.30

    disk0:hfr-base-3.3.30

    disk0:hfr-fwdg-3.3.30

    disk0:hfr-lc-3.3.30

    disk0:hfr-mcast-3.3.30

    disk0:hfr-mpls-3.3.30

    disk0:hfr-os-mbi-3.3.30

    disk0:hfr-rout-3.3.30

disk0:hfr-mgbl-3.3.30

disk0:hfr-diags-3.3.30

disk0:hfr-k9sec-3.3.30

Related Commands

Command	Description
show install	Displays active software packages.
show install active	Displays active software packages.
show install committed	Displays committed software packages.
show install inactive	Displays inactive packages in the active software set.
show install log	Displays the entries stored in the logging installation buffer.
show install pie-info	Displays information on the packages contained in a PIE file.
show install which	Displays the origin of a component, package, or file.

show install pie-info

To display information about a Package Installation Envelope (PIE) installation file, use the show install pie-info command in Administration EXEC mode.

show install pie-info device:package [summary | detail | verbose]

Syntax Description

device:package	Device, directory path, and package, expressed in concatenated form.
summary	(Optional) Displays summary information.
detail	(Optional) Displays detailed information.
verbose	(Optional) Displays comprehensive information.

Defaults

Displays summary information.

Command Modes

Administration EXEC

Command History

Release	Modification
Release 2.0	This command was introduced on the Cisco CRS-1 router.
Release 3.0	No modification.
Release 3.2	This command was first supported on the Cisco XR 12000 Series Router. The command was moved from EXEC mode to Administration EXEC mode.
Release 3.3.0	Support was added for the keywords detail, and verbose.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Use the show install pie-info command to display information about a specified PIE installation file.

Task ID

Task ID	Operations
pkg-mgmt	read

Examples

The following is sample output from the show install pie-info detail command:

RP/0/RP0/CPU0:router(admin)#show install pie-info disk1:/hfr-mcast-p.pie-3.3.0 detail 

Contents of pie file '/disk1:/hfr-mcast-p.pie-3.3.0':

    Expiry date       : Jan 19, 2007 02:55:56 UTC

    Uncompressed size : 9539249

    hfr-mcast-3.3.0

        hfr-mcast V3.3.0[1I]  Multicast Package

        Vendor : Cisco Systems

        Desc   : Multicast Package

        Build  : Built on Fri Feb 24 08:18:54 UTC 2006

        Source : By edde-bld1 in /vws/aga/production/3.3.0/hfr/workspace for c2.95.3-p8

        Card(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-OC3C

        Components in package hfr-mcast-3.3.0, package  hfr-mcast:

            platform-ipv4-mrib V[fwd-33/9]  HFR platform dependent DLL for MRIB

            doc-hfr-mcast V[ci-33/5]  Contains the man page documentation for HFR    
multicast package commands

	  package-compat V[fwd-33/7]  This is to collect package compatibility info from

other contributing components

            package-multicast V[fwd-33/4]  This is to collect package compatibility info 

about MULTICAST package

            snmp-mcast V[fwd-33/20]  Multicast MIBS on IOS XR

---MORE--

Related Commands

Command	Description
show install	Displays active software packages.
show install active	Displays active software packages.
show install committed	Displays committed software packages.
show install inactive	Displays inactive packages in the active software set.
show install log	Displays the entries stored in the logging installation buffer.
show install package	Displays information about a package.
show install request	Displays the list of incomplete installation manager requests.
show install which	Displays the origin of a component, package, or file.

show install request

To display the list of incomplete installation requests, running and queued, use the show install request command in Administration EXEC mode.

show install request

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

Administration EXEC

Command History

Release	Modification
Release 2.0	This command was introduced on the Cisco CRS-1.
Release 3.0	No modification.
Release 3.2	This command was first supported on the Cisco XR 12000 Series Router. The command was moved from EXEC mode to Administration EXEC mode.
Release 3.3.0	Command syntax was changed from show install requests to show install request.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

The Cisco IOS XR software processes only one installation request at a time. The default of installation commands is asynchronous mode, meaning that the command runs in the background and the EXEC prompt is returned as soon as possible. The show install request command displays any incomplete request that is currently running.

These requests cannot be stopped by pressing Ctrl-C.

---

Note Performing a command in synchronous mode allows the installation process to finish before the prompt is returned.

---

Task ID

Task ID	Operations
pkg-mgmt	read

Examples

The following is sample output from the show install request command:

RP/0/RP0/CPU0:router(admin)# show install request 

Install operation 17 'install add /tftp://172.31.255.255/dir/19mcast'

started by user 'lab' at 14:38:45 UTC Thu Mar 30 2006.

The operation is 1% complete

2,017KB downloaded

The operation can still be aborted.

The following is sample output from the show install request command when no install operations are running:

RP/0/RP0/CPU0:router(admin)# show install request

There are no install requests in operation.

Related Commands

Command	Description
install activate	Adds a software package or an SMU to the active software set.
install add	Installs a package on a storage device.
install deactivate	Removes a package from the active software set.
install remove	Deletes inactive packages from a storage device.
install rollback to	Rolls back the software set to a saved installation point or to the last committed installation point.
install verify	Verifies the consistency of a previously installed software set with the package file from which it originated.

show install rollback

To display the software set associated with a saved installation point, use the show install rollback command in Administration EXEC mode.

show install rollback point-id [sdr sdr-name | location node-id] [[detail [sdr sdr-name | location node-id] [summary [sdr sdr-name]]

Syntax Description

point-id	Installation point ID number.
sdr sdr-name	(Optional) Displays information for a specific secure domain router (SDR). The sdr-name argument is the name assigned to the secure domain router.
location node-id	(Optional) Displays information for a designated node. The node-id argument is expressed in the rack/slot/module notation.
summary	(Optional) Displays a summary of information in a system or secure domain router.
detail	(Optional) Displays a detailed summary of information for a system, secure domain router, or node, including the packages contained in a composite package.

Defaults

No default behavior or values

Command Modes

Administration EXEC

Command History

Release	Modification
Release 3.0	This command was introduced on the Cisco CRS-1.
Release 3.2	This command was first supported on the Cisco XR 12000 Series Router. The command was made available in Administration EXEC mode.
Release 3.3.0	The command was moved to Administration EXEC mode only. Support was added for the keywords and arguments: sdr sdr-name, detail, and summary.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

Use the show install rollback command to display the software set associated with a saved installation point. This command can be used with the install rollback to command to verify the software set associated with a saved installation point before rolling back to the saved installation point.

Use the location keyword and node-id argument to display information for a specific node. If you do not specify a location with the location keyword and node-id argument, this command displays information from all nodes.

Use the sdr keyword and sdr-name argument to display information for a specific secure domain router.

Use the summary keyword to display a summary of the committed packages in a system or secure domain router. Use the detail keyword to display a summary of the committed packages in a system, secure domain router, or node.

Use the clear install rollback oldest command to delete saved installation points from the install buffer.

Task ID

Task ID	Operations
pkg-mgmt	read

Examples

The following is sample output from the show install rollback command:

RP/0/RP0/CPU0:router(admin)#show install rollback 0

Secure Domain Router: Owner

  Node 0/1/SP [SP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/sp/mbihfr-sp.vm

    Rollback Packages: 

      disk0:comp-hfr-mini-3.3.30

  Node 0/1/CPU0 [LC] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/lc/mbihfr-lc.vm

    Rollback Packages: 

      disk0:comp-hfr-mini-3.3.30

  Node 0/6/SP [SP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/sp/mbihfr-sp.vm

    Rollback Packages: 

      disk0:comp-hfr-mini-3.3.30

  Node 0/6/CPU0 [LC] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/lc/mbihfr-lc.vm

    Rollback Packages: 

      disk0:comp-hfr-mini-3.3.30

  Node 0/RP0/CPU0 [RP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/mbihfr-rp.vm

    Rollback Packages: 

      disk0:comp-hfr-mini-3.3.30

  Node 0/RP1/CPU0 [RP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/mbihfr-rp.vm

    Rollback Packages: 

      disk0:comp-hfr-mini-3.3.30

  Node 0/SM0/SP [SP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/sp/mbihfr-sp.vm

    Rollback Packages: 

      disk0:comp-hfr-mini-3.3.30

  Node 0/SM1/SP [SP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/sp/mbihfr-sp.vm

    Rollback Packages: 

      disk0:comp-hfr-mini-3.3.30

  Node 0/SM2/SP [SP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/sp/mbihfr-sp.vm

    Rollback Packages: 

      disk0:comp-hfr-mini-3.3.30

  Node 0/SM3/SP [SP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/sp/mbihfr-sp.vm

    Rollback Packages: 

      disk0:comp-hfr-mini-3.3.30

The following is sample output from the show install rollback detail command:

RP/0/RP0/CPU0:router(admin)#show install rollback 0 detail 

Secure Domain Router: Owner

  Node 0/1/SP [SP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/sp/mbihfr-sp.vm

    Rollback Packages: 

      disk0:comp-hfr-full-3.3.30

        disk0:hfr-admin-3.3.30

        disk0:hfr-base-3.3.30

        disk0:hfr-os-mbi-3.3.30

  Node 0/1/CPU0 [LC] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/lc/mbihfr-lc.vm

    Rollback Packages: 

      disk0:comp-hfr-full-3.3.30

        disk0:hfr-mcast-3.3.30

        disk0:hfr-mpls-3.3.30

        disk0:hfr-lc-3.3.30

        disk0:hfr-fwdg-3.3.30

        disk0:hfr-admin-3.3.30

        disk0:hfr-base-3.3.30

        disk0:hfr-os-mbi-3.3.30

  Node 0/6/SP [SP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/sp/mbihfr-sp.vm

    Rollback Packages: 

      disk0:comp-hfr-full-3.3.30

        disk0:hfr-admin-3.3.30

        disk0:hfr-base-3.3.30

        disk0:hfr-os-mbi-3.3.30

  Node 0/6/CPU0 [LC] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/lc/mbihfr-lc.vm

    Rollback Packages: 

      disk0:comp-hfr-full-3.3.30

        disk0:hfr-mcast-3.3.30

        disk0:hfr-mpls-3.3.30

        disk0:hfr-lc-3.3.30

        disk0:hfr-fwdg-3.3.30

        disk0:hfr-admin-3.3.30

        disk0:hfr-base-3.3.30

        disk0:hfr-os-mbi-3.3.30

  Node 0/RP0/CPU0 [RP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/mbihfr-rp.vm

    Rollback Packages: 

      disk0:comp-hfr-full-3.3.30

        disk0:hfr-rout-3.3.30

        disk0:hfr-mcast-3.3.30

        disk0:hfr-mpls-3.3.30

        disk0:hfr-lc-3.3.30

        disk0:hfr-fwdg-3.3.30

        disk0:hfr-admin-3.3.30

        disk0:hfr-base-3.3.30

        disk0:hfr-os-mbi-3.3.30

  Node 0/RP1/CPU0 [RP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/mbihfr-rp.vm

    Rollback Packages: 

      disk0:comp-hfr-full-3.3.30

        disk0:hfr-rout-3.3.30

        disk0:hfr-mcast-3.3.30

        disk0:hfr-mpls-3.3.30

        disk0:hfr-lc-3.3.30

        disk0:hfr-fwdg-3.3.30

        disk0:hfr-admin-3.3.30

        disk0:hfr-base-3.3.30

        disk0:hfr-os-mbi-3.3.30

  Node 0/SM0/SP [SP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/sp/mbihfr-sp.vm

    Rollback Packages: 

      disk0:comp-hfr-full-3.3.30

        disk0:hfr-admin-3.3.30

        disk0:hfr-base-3.3.30

        disk0:hfr-os-mbi-3.3.30

  Node 0/SM1/SP [SP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/sp/mbihfr-sp.vm

    Rollback Packages: 

      disk0:comp-hfr-full-3.3.30

        disk0:hfr-admin-3.3.30

        disk0:hfr-base-3.3.30

        disk0:hfr-os-mbi-3.3.30

  Node 0/SM2/SP [SP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/sp/mbihfr-sp.vm

    Rollback Packages: 

      disk0:comp-hfr-full-3.3.30

        disk0:hfr-admin-3.3.30

        disk0:hfr-base-3.3.30

        disk0:hfr-os-mbi-3.3.30

  Node 0/SM3/SP [SP] [SDR: Owner]

    Boot Image: /disk0/hfr-os-mbi-3.3.30/sp/mbihfr-sp.vm

    Rollback Packages: 

      disk0:comp-hfr-full-3.3.30

        disk0:hfr-admin-3.3.30

        disk0:hfr-base-3.3.30

        disk0:hfr-os-mbi-3.3.30

Table 6 describes the significant fields shown in the display.

Table 6 show install rollback Field Descriptions 

Field	Description
Boot Image:	Minimum Boot Image (MBI) used to boot the node.
Rollback Packages:	Packages that will be rolled back.

Related Commands

Command	Description
clear install rollback oldest	Deletes saved installation points from the install buffer.
install rollback to	Rolls back the software set to a saved installation point or to the last committed installation point.

show install suspend

To display the suspension points for an install activation operation, use the show install suspend command in Administration EXEC mode.

show install suspend

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

Administration EXEC

Command History

Release	Modification
Release 3.3.0	This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Routers.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

The install suspend command may be run multiple times to set multiple suspension points. Use the show install suspend command to view all suspension points.

The suspension points are valid only for the duration of the current install operation. They are cleared after the transaction has been completed.

Task ID

Task ID	Operations
pkg-mgmt	read

Examples

The following example shows output for the command show install suspend:

RP/0/RP0/CPU0:router(admin)#show install suspend

Note: The suspension points set below will be used only for

the participating nodes in an incremental activation, deactivation,

rollback install operation.

Future suspension points:

   before software change

   location 0/RP0/CPU0

Related Commands

Command	Description
install resume	Resumes an install activation operation that has been suspended with the command install suspend.
install suspend	Suspends an activation operation.

show install which

To display the origin of a named process, component, or package, use the show install which command in EXEC mode or Administration EXEC mode.

show install which {component name [verbose] | file filename} [sdr sdr-name | location node-id]

Syntax Description

component name	Displays the package information for the component specified in the name argument.
verbose	(Optional) Displays summary, component, and file information for each component.
file filename	Displays the package information for the file specified in the filename argument.
location node-id	(Optional) Displays information for the designated node. The node-id argument is expressed in the rack/slot/module notation.
sdr sdr-name	(Optional) Displays information for a specific secure domain router (SDR). The sdr-name argument is the name assigned to the secure domain router.

Defaults

The default search is performed for the active software set.

Command Modes

EXEC
Administration EXEC

Command History

Release	Modification
Release 2.0	This command was introduced on the Cisco CRS-1.
Release 3.0	No modification.
Release 3.2	This command was first supported on the Cisco XR 12000 Series Router. The command was moved from EXEC mode to Administration EXEC mode.
Release 3.3.0	This command was supported in both EXEC mode and Administration EXEC mode. Support was removed for the files keyword. Support was added for the verbose keyword. Support was added for the SDR SDR-name keyword and argument.

Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of the Cisco IOS XR System Security Configuration Guide.

This command returns the same data in EXEC mode and Administration EXEC mode.

Task ID

Task ID	Operations
pkg-mgmt	read

Examples

The following is sample output from the show install which command with the file and location keywords specified:

RP/0/RP0/CPU0:router# show install which file bgp location 0/RP0/CPU0

Node 0/RP0/CPU0 has file bgp for boot package /disk0/hfr-os-mbi-3.3.30/mbihfr-rt

Package:

    hfr-rout

        hfr-rout V3.3.30[1I]  Routing Package

        Vendor : Cisco Systems

        Desc   : Routing Package

        Build  : Built on Mon Mar 27 10:01:45 UTC 2006

        Source : By edde-bld1 in /vws/aga/production/3.3.30.1I/hfr/workspace fo8

        Card(s): RP, DRP, DRPSC

        Restart information:

          Default:

            parallel impacted processes restart

Component:

    ipv4-bgp V[fwd-33/69]  IPv4 Border Gateway Protocol (BGP)

File: bgp

Table 7 describes the significant fields shown in the display.

Table 7 show install which Field Descriptions 

Field	Description
Package:	Version of the package, name of the manufacturer, name of the package, date and time when the package was built, and source directory where the package was built.
Component:	Component name and version number.

Related Commands

Command	Description
show install	Displays active software packages.
show install active	Displays active software packages.
show install inactive	Displays inactive packages in the active software set.
show install committed	Displays committed software packages.
show install log	Displays the entries stored in the logging installation buffer.
show install package	Displays information about a package.
show install request	Displays the list of incomplete installation manager requests.
show install which	Displays the origin of a component, package, or file.