The install mode process flow comprises three commands to perform installation and upgrade of software on platforms– install add, install activate, and install commit.
The following flow chart explains the install process with install commands:
The install add command copies the software package from a local or remote location to the platform. The command extracts individual components
of the .package file into subpackages and packages.conf files. It also validates the file to ensure that the image file is
specific to the platform on which it is being installed.
The location of the software package can be in several places, as shown in the output of the following command:
IR1831#install add file ?
bootflash: Package name
crashinfo: Package name
flash: Package name
ftp: Package name
http: Package name
https: Package name
pram: Package name
rcp: Package name
scp: Package name
sftp: Package name
tftp: Package name
webui: Package name
The install activate command performs the required validations and provisions the packages previously added using the install add command. It also triggers a system reload.
The install commit command confirms the packages previously activated using the install activate command, and makes the updates persistent over reloads.
Note
|
Installing an update replaces any previously installed software image. At any time, only one image can be installed in a device.
|
The following set of install commands is available:
Table 3. List of install Commands
|
Command
|
Syntax
|
Purpose
|
|
install add
|
install add file location:filename.bin
|
Copies the contents of the image, package, and SMUs to the software repository. File location may be local or remote. This
command does the following:
-
Validates the file–checksum, platform compatibility checks, and so on.
-
Extracts individual components of the package into subpackages and packages.conf
-
Copies the image into the local inventory and makes it available for the next steps.
|
|
install activate
|
install activate
|
Activates the package added using the install add command.
-
Use the show install summary command to see which image is inactive. This image will get activated.
-
System reloads on executing this command. Confirm if you want to proceed with the activation. Use this command with the prompt-level none keyword to automatically ignore any confirmation prompts.
|
|
(install activate) auto abort-timer
|
install activate auto-abort timer <30-1200>
|
The auto-abort timer starts automatically, with a default value of 120 minutes. If the install commit command is not executed within the time provided, the activation process is terminated, and the system returns to the last-committed
state.
-
You can change the time value while executing the install activate command.
-
The install commit command stops the timer, and continues the installation process.
-
The install activate auto-abort timer stop command stops the timer without committing the package.
-
Use this command with the prompt-level none keyword to automatically ignore any confirmation prompts.
-
This command is valid only in the three-step install variant.
|
|
install commit
|
install commit
|
Commits the package activated using the install activate command, and makes it persistent over reloads.
|
|
install abort
|
install abort
|
Terminates the installation and returns the system to the last-committed state.
-
This command is applicable only when the package is in activated status (uncommitted state).
-
If you have already committed the image using the install commit command, use the install rollback to command to return to the preferred version.
|
|
install remove
|
install remove {file <filename> | inactive}
|
Deletes inactive packages from the platform repository. Use this command to free up space.
|
|
install rollback to
|
install rollback to {base | label | committed | id}
|
Rolls back the software set to a saved installation point or to the last-committed installation point. The following are the
characteristics of this command:
|
Note
|
If you are performing install rollback to a previous image, the previous image must be installed in install mode. Only SMU
rollback is possible in bundle mode.
|
|
|
install deactivate
|
install deactivate file <filename>
|
Removes a package from the platform repository. This command is supported only for SMUs.
|
The following show commands are also available:
Table 4. List of show Commands
|
Command
|
Syntax
|
Purpose
|
|
show install log
|
show install log
|
Provides the history and details of all install operations that have been performed since the platform was booted.
|
|
show install package
|
show install package <filename>
|
Provides details about the .pkg/.bin file that is specified.
|
|
show install summary
|
show install summary
|
Provides an overview of the image versions and their corresponding install states.
|
|
show install active
|
show install active
|
Provides information about the active packages.
|
|
show install inactive
|
show install inactive
|
Provides information about the inactive packages.
|
|
show install committed
|
show install committed
|
Provides information about the committed packages.
|
|
show install uncommitted
|
show install uncommitted
|
Provides information about uncommitted packages.
|
|
show install rollback
|
show install rollback {point-id | label}
|
Displays the package associated with a saved installation point.
|
|
show version
|
show version [rp-slot] [installed [user-interface] | provisioned | running]
|
Displays information about the current package, along with hardware and platform information.
|
Feedback