Login
- Table of Contents
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 07-Software upgrade commands | 189.11 KB |
Software upgrade commands
As a best practice, store the startup images in a fixed storage medium. If you store the startup images in a hot swappable storage medium, do not remove the hot swappable storage medium during the startup process.
boot-loader file
Use boot-loader file to specify startup image files.
Syntax
boot-loader file boot filename system filename [ feature filename&<1-30> ] [ patch filename&<1-30> ] { backup | main }
boot-loader file ipe-filename [ patch filename&<1-30> ] { backup | main }
Views
User view
Predefined user roles
network-admin
Parameters
boot: Specifies a boot image file.
system: Specifies a system image file.
feature: Specifies a space-separated list of up to 30 feature image files.
patch: Specifies a space-separated list of up to 30 incremental patch image files or 16 non-incremental patch image files. Because the boot, system, and feature images each can have one non-incremental patch image file, you can specify a maximum of 16 non-incremental patch image files.
filename: Specifies a .bin file in the filesystemname/filename.bin format. The file must be stored in the root directory of a file system on the device. Excluding the file system location section (if any), the value string can have a maximum of 63 characters. For more information about specifying a file, see Fundamentals Configuration Guide.
ipe-filename: Specifies an .ipe image package file in the filesystemname/filename.ipe format. The file must be stored in the root directory of a file system on the device. Excluding the file system location section (if any), the value string can have a maximum of 63 characters. For more information about specifying a file, see Fundamentals Configuration Guide.
all: Upgrades the entire system.
backup: Specifies the files as backup startup image files. Backup images are used only when main images are not available.
main: Specifies the files as main startup image files. The device always first attempts to start up with main startup files.
Usage guidelines
Prerequisites
Before you specify startup image files, register and activate a license for each upgrade image that requires a license. If a license-based software image lacks a license, the command execution result is as follows:
· If .bin files are specified, the command cannot be executed.
· If an .ipe file is specified, the command sets all images as startup images except for the image that does not have a license.
For more information about licensing, see Fundamentals Configuration Guide.
Application scenarios
When the current software cannot meet the requirements of network operation or user services, you can use this command to upgrade the software to optimize device performance to meet the requirements.
Operating mechanism
The boot-loader file command overwrites the entire startup image list. To add new startup feature images, specify all feature image files in the old startup image list, including feature image files. The new startup image list will contain only the feature image files that are specified in the command.
Restrictions and guidelines
The system verifies the digital signature of the specified images before it updates the startup image list with the specified images. If the digital signature verification fails, the system will not update the startup image list and you will receive a digital signature verification failure message.
To load the specified startup software images, you must reboot the system.
Examples
# Specify flash:/all.ipe as the main startup image file.
<Sysname> boot-loader file flash:/all.ipe main
Verifying the file flash:/all.ipe on the device............Done.
xx Switch images in IPE:
boot.bin
system.bin
feature.bin
This command will set the main startup software images. Continue? [Y/N]:Y
Add images to the device.
File flash:/boot.bin already exists on the device.
File flash:/system.bin already exists on the device.
File flash:/feature.bin already exists on the device.
Overwrite the existing files? [Y/N]:Y
Decompressing file boot.bin to flash:/boot.bin........................Done.
Decompressing file system.bin to flash:/system.bin...............................Done.
Decompressing file feature.bin to flash:/feature.bin..................Done.
Verifying the file flash:/boot.bin on the device...Done.
Verifying the file flash:/system.bin on the device.............Done.
Verifying the file flash:/feature.bin on the device...Done.
The images that have passed all examinations will be used as the main startup software images at the next reboot on the device.
# Specify flash:/boot.bin and flash:/system.bin as the main startup boot and system image files.
<Sysname> boot-loader file boot flash:/boot.bin system flash:/system.bin feature flash:/feature.bin main
This command will set the main startup software images. Continue? [Y/N]:y
The images that have passed all examinations will be used as the main startup software images at the next reboot on the device.
Related commands
display boot-loader
display boot-loader
Use display boot-loader to display current software images and startup software images.
Syntax
display boot-loader
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
Examples
# Display the current software images and startup software images.
<Sysname> display boot-loader
Software images on the device:
Current software images:
flash:/boot.bin
flash:/system.bin
Main startup software images:
flash:/boot.bin
flash:/system.bin
Backup startup software images:
flash:/boot_backup.bin
flash:/system_backup.bin
Table 1 Command output
|
Field |
Description |
|
Current software images |
Comware images that have been loaded. |
|
Main startup software images |
Primary Comware images for the next startup. |
|
Backup startup software images |
Backup Comware images for the next startup. |
Related commands
boot-loader file
firmware update
Use firmware update to upgrade firmware.
Syntax
firmware update [ subslot subslot-number ] { cpld cpld-number | fpga fpga-number | module module-number } file filename
Views
User view
Predefined user roles
network-admin
Parameters
subslot subslot-number: Specifies a subcard by its subslot number. If you do not specify a subcard, the command upgrades firmware for all subcards on the base card.
cpld cpld-number: Specifies a complex programmable logical device (CPLD) by its number.
fpga fpga-number: Specifies a field programmable gate array (FPGA) by its number.
file filename: Specifies an upgrade file in the filesystemname/filename.extension format. The file must be stored in the root directory of a file system on the device. Excluding the file system location section (if any), the value string can have a maximum of 63 characters. For more information about specifying a file, see Fundamentals Configuration Guide.
Usage guidelines
Use this command to upgrade firmware that cannot be upgraded using the boot-loader command.
To complete the firmware upgrade, you must power cycle the card or subcard.
To power cycle a card or subcard, use one of the following methods:
· Power cycle the device.
· Remove and reinsert the card or subcard.
Examples
# Upgrade CPLD 1.
<Sysname> firmware update cpld 1 file package.bin
Updating firmware for CPLD on the specified card or subcard. Continue?[Y/N]:y
Updating the firmware…
Please power cycle the card or subcard to activate the firmware.
display install active
Use display install active to display active software images.
display install active [ slot slot-number ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays information for all cards.
verbose: Displays detailed information. If you do not specify this keyword, the command displays only image names.
Examples
# Display active software images.
<Sysname> display install active
Active packages on slot 1:
flash:/boot.bin
flash:/system.bin
flash:/feature1.bin
# Display detailed information about active software images.
<Sysname> display install active verbose
Active packages on slot 1:
flash:/boot.bin
[Package]
Vendor: H3C
Product: xxxx
Service name: boot
Platform version: xxx
Product version: xxx
Supported board: xxx
[Component]
Component: boot
Description: boot package
…
|
Field |
Description |
|
[Package] |
Detailed information about the software image. |
|
Service name |
Image type: · boot—Boot image. · system—System image. · boot patch—Patch image for the boot image. · system patch—Patch image for the system image. · Any other value indicates a feature image. |
|
Supported board |
Hardware types supported by the software image. |
|
[Component] |
Information about components included in the image file. |
Related commands
install active
display install backup
Use display install backup to display backup startup software images.
Syntax
display install backup [ slot slot-number ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays information for all cards.
verbose: Displays detailed information. If you do not specify this keyword, the command displays only image names.
Usage guidelines
Application scenarios
Backup startup images are used only when the main boot or system image is missing or corrupt. For more information, see Fundamentals Configuration Guide.
Restrictions and guidelines
To modify the backup startup image list, use the boot-loader file command.
Examples
# Display the backup startup software images.
<Sysname> display install backup
Backup startup software images on slot 1:
flash:/boot.bin
flash:/system.bin
# Display detailed information about backup startup software images.
<Sysname> display install backup verbose
Backup startup software images on slot 1:
flash:/boot.bin
[Package]
Vendor: H3C
Product: xxxx
Service name: boot
Platform version: xxx
Product version: xxx
Supported board: xxx
[Component]
Component: boot
Description: boot package
…
For information about the command output, see Table 2.
Related commands
boot-loader file
display install committed
display install committed
Use display install committed to display main startup software images.
Syntax
display install committed [ slot slot-number ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays information for all cards.
verbose: Displays detailed information. If you do not specify this keyword, the command displays only image names.
Usage guidelines
Application scenarios
Some install commands modify the current software image list but do not modify the main startup image list. For the software image changes to take effect after a reboot, you must execute the install commit command to update the main startup image list with the image changes. You can use the display install committed command to verify the operation results.
Restrictions and guidelines
Both the install commit and boot-loader file commands modify the main startup software image list.
Examples
# Display the main startup software images.
<Sysname> display install committed
Committed packages on slot 1:
flash:/boot.bin
flash:/system.bin
flash:/feature1.bin
# Display detailed information about main startup software images.
<Sysname> display install committed verbose
Committed packages on slot 1:
flash:/boot.bin
[Package]
Vendor: H3C
Product: xxxx
Service name: boot
Platform version: xxx
Product version: xxx
Supported board: xxx
[Component]
Component: boot
Description: boot package
…
For information about the command output, see Table 2.
Related commands
boot-loader file
display install backup
install commit
display install inactive
Use display install inactive to display inactive software images in the root directories of file systems.
Syntax
display install inactive [ slot slot-number ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays information for all cards.
verbose: Displays detailed information. If you do not specify this keyword, the command displays only image names.
Examples
# Display brief information about inactive software images in the root directories of the file systems.
<Sysname> display install inactive
Inactive packages on slot 1:
flash:/feature1.bin
# Display detailed information about inactive software images in the root directories of the file systems.
<Sysname> display install inactive verbose
Inactive packages on slot 1:
flash:/feature1.bin
[Package]
Vendor: H3C
Product: xxxx
Service name: feature1
Platform version: xxx
Product version: xxx
Supported board: xxx
[Component]
Component: feature1
Description: feature1 package
For information about the command output, see Table 2.
Related commands
install deactivate
display install ipe-info
Use display install ipe-info to display the software images included in an .ipe file.
Syntax
display install ipe-info ipe-filename
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
ipe-filename: Specifies an .ipe file in the filesystemname/filename.ipe format. The file must be stored in the root directory of a file system on the device. The value string excluding the file system location section (if any) can have a maximum of 63 characters. For more information about specifying a file, see file system management in Fundamentals Configuration Guide.
Examples
# Display information about .ipe file flash:/test.ipe.
<Sysname> display install ipe-info flash:/test.ipe
Verifying the file flash:/test.ipe on slot 1..............Done.
XX images in IPE:
boot.bin
system.bin
Related commands
display install package
display install job
Use display install job to display ongoing activate, deactivate, and rollback operations.
Syntax
display install job
Views
Any view
Predefined user roles
network-admin
network-operator
Examples
# Display ongoing activate, deactivate, and rollback operations.
<Sysname> display install job
JobID:5
Action:install activate flash:/feature1.bin on the device
The output shows that the device is executing the install activate flash:/feature1.bin command.
display install log
Use display install log to display upgrade log information.
Syntax
display install log [ log-id ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
log-id: Specifies a log entry by its ID. If you do not specify this argument, the command displays all upgrade log entries.
verbose: Displays detailed upgrade log information. If you do not specify this keyword, the command displays brief upgrade log information.
Usage guidelines
Operating mechanism
The device creates one log entry for each upgrade operation to track the upgrade process and operation result.
Restrictions and guidelines
The upgrade log can contain a maximum of 50 entries. The latest entry overwrites the oldest entry if the log is full.
A device reboot clears all upgrade log entries.
Examples
# Display all upgrade log entries.
<Sysname> display install log
Install job 1 started by user root at 04/28/2001 08:39:29.
Job 1 completed successfully at 04/28/2001 08:39:30.
Install job 1 started by user root at 04/28/2001 08:39:29.
Install activate flash:/feature1.bin on slot 1
Job 1 completed successfully at 04/28/2001 08:39:30.
Install job 1 started by user root at 04/28/2001 08:39:29.
Job 1 completed successfully at 04/28/2001 08:39:30.
-----------------------------------------------------------
Install job 2 started by user root at 04/28/2001 08:40:29.
Job 2 completed successfully at 04/28/2001 08:40:30.
Install job 2 started by user root at 04/28/2001 08:40:29.
Install activate flash:/route.bin on slot 1
Job 2 completed successfully at 04/28/2001 08:40:30.
Install job 2 started by user root at 04/28/2001 08:40:29.
Job 2 completed successfully at 04/28/2001 08:40:30.
# Displays detailed information about upgrade log entry 1.
<Sysname> display install log 1 verbose
Install job 1 started by user root at 04/28/2001 08:39:29.
Job 1 completed successfully at 04/28/2001 08:39:30.
Install job 1 started by user root at 04/28/2001 08:39:29.
Install activate flash:/feature1.bin on slot 1
Job 1 completed successfully at 04/28/2001 08:39:30.
Install job 1 started by user root at 04/28/2001 08:39:29.
Job 1 completed successfully at 04/28/2001 08:39:30.
Detail of activating packages on slot 1.
Get upgrade policy successfully.
Detail of activating packages on slot 1.
Uncompress package to system successfully.
Remove files from system successfully.
Table 3 Command output
|
Field |
Description |
|
Detail of xxx |
Detailed information about an upgrade operation. |
|
Get upgrade policy successfully. |
Obtained the upgrade policy. |
|
Uncompress package to system successfully. |
Decompressed the package successfully. |
|
Remove files from system successfully. |
Deleted files from the system successfully. |
Related commands
reset install log-history oldest
display install package
Use display install package to display software image file information.
Syntax
display install package { filename | all } [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
filename: Specifies a .bin file in the filesystemname/filename.bin format. The file must be stored in the root directory of a file system on the device. The value string excluding the file system location section (if any) can have a maximum of 63 characters. For more information about specifying a file, see file system management in Fundamentals Configuration Guide.
all: Specifies all software image files in the root directories of the device's file systems.
verbose: Displays detailed information. If you do not specify this keyword, the command displays only basic software image information.
Examples
# Display information about system.bin.
<Sysname> display install package flash:/system.bin
flash:/system.bin
[Package]
Vendor: H3C
Product: xxxx
Service name: system
Platform version: xxx
Product version: xxx
Supported board: xxx
For information about the command output, see Table 2.
display install rollback
Use display install rollback to display rollback point information.
Syntax
display install rollback [ point-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
point-id: Specifies a rollback point ID. If you do not specify a rollback point ID, the command displays all rollback points.
Usage guidelines
Application scenarios
Use this command to identify available rollback points during an upgrade that uses install commands.
Restrictions and guidelines
The system does not record rollback points during an upgrade.
Examples
# Display all rollback points.
<Sysname> display install rollback
Install rollback information 1 on slot 1:
Updating from flash:/route-1.bin
to flash:/route-2.bin.
Install rollback information 2 on slot 1:
Deactivating flash:/route-2.bin
The output shows that the device has two rollback points.
· At rollback point 1, flash:/route-1.bin was upgraded to flash:/route-2.bin.
· At rollback point 2, flash:/route-2.bin was deactivated.
Related commands
install rollback
reset install rollback oldest
display install which
Use display install which to display all software image files that include a specific component or file.
Syntax
display install which { component name | file filename } [ slot slot-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
component name: Specifies a component name.
file filename: Specifies a file in the filename.extension format, a case-insensitive string of up to 63 characters. It cannot contain path information.
slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays information for all cards.
Usage guidelines
Concepts
A component is a collection of features. The features of a component are installed or uninstalled at the same time.
Application scenarios
When the system displays a component or file error, use this command to identify the image files that include the component or file. Then, you can use the install verify command to identify image file problems.
Operating mechanism
This command searches only the root directories of the file systems at the specified location.
Examples
# Display the software image files that include pkg_ctr.
<Sysname> display install which file pkg_ctr
Verifying the file flash:/system.bin on slot 1..........................Done.
Found pkg_ctr in flash:/system.bin on slot 1.
flash:/system.bin
[Package]
Vendor: H3C
Product: xxxx
Service name: system
Platform version: xxx
Product version: xxx
Supported board: xxx
…
Table 4 Command output
|
Field |
Description |
|
Verifying the file |
The system was verifying the validity of the file. |
|
Found pkg_ctr in |
The image file in which the specified component or file was found. |
|
[Package] |
Detailed information about the software image. |
|
Service name |
Image type: · boot—Boot image. · system—System image. · patch—Patch image. · Any other value indicates a feature image. |
|
Supported board |
Hardware types supported by the software image. |
install abort
Use install abort to abort an ongoing activate or deactivate operation.
Syntax
install abort [ job-id ]
Views
User view
Predefined user roles
network-admin
Parameters
job-id: Specifies the job ID of an upgrade operation. If you do not specify this argument, the command aborts all ongoing software image activate and deactivate operations.
Usage guidelines
Operating mechanism
When you abort an ongoing activate or deactivate operation, the system rolls back to the status it was in before the operation was started.
Restrictions and guidelines
The system creates a software image management job each time you use the install activate, install add, install commit, install deactivate, install remove, or install rollback to command. Each job represents one command and is assigned a unique job ID. To obtain the ID of a job, use the display install job command.
Examples
# Abort all ongoing software image activate and deactivate operations.
<Sysname> install abort
Related commands
display install job
install activate
Use install activate to activate software images, or identify the upgrade method and the possible impact on the device.
Syntax
install activate { boot filename | system filename | feature filename&<1-30> } * slot slot-number [ test ]
install activate patch filename { all | slot slot-number }
Views
User view
Predefined user roles
network-admin
Parameters
boot: Specifies a boot image file.
system: Specifies a system image file.
feature: Specifies a space-separated list of up to 30 feature image files
patch: Specifies a patch image file. You can specify only one patch image file for the command at a time. However, you can execute the command multiple times to activate multiple patch image files. You can specify both incremental and non-incremental patch image files. The device can use a maximum of 30 incremental patch image files. Because the boot, system, and feature images each can have one non-incremental patch image file, the device can use a maximum of 16 non-incremental patch image files. For more information about incremental and non-incremental patch images, see software upgrade in Fundamentals Configuration Guide.
filename: Specifies a .bin file in the filesystemname/filename.bin format. The file must be stored in the root directory of a file system on the device. The value string excluding the file system location section (if any) can have a maximum of 63 characters. For more information about specifying a file, see file system management in Fundamentals Configuration Guide.
all: Specifies all cards.
slot slot-number: Specifies a card by its slot number.
test: Only identifies the upgrade method to be used. If you do not specify this keyword, the command activates the specified software images.
Prerequisites
Before you use this command to activate a software image, read the release notes to identify the licensing requirements for the image. If the image requires a license, make sure the device has a valid license installed for the image.
Restrictions and guidelines
The software images for the device are digitally signed. The system verifies the digital signature of an image for authenticity and integrity before it activates it. If the digital signature verification fails, the system will not activate the image and you will receive a digital signature verification failure message.
This command requires that all image files on the startup software image list be the same version after the upgrade is finished. It can be executed successfully only if the boot, system, and feature image files on the list are the same version after the upgrade. Before being executed successfully, this command uninstalls all existing patch image files on the list automatically.
If this command fails, perform the following tasks:
1. If some features are not needed anymore, disable the features and use the install deactivate command to uninstall the feature images.
2. Obtain the image files that are required to make sure all image files on the startup software image list are the same version after the upgrade.
3. Specify the image files for this command to activate the images.
An image runs in memory immediately after it is activated. For an activated image to run after a reboot, you must commit the software change by using the install commit command.
Examples
# Identify the upgrade method for feature upgrade with feature1.bin and the upgrade impact on the device.
<Sysname> install activate feature flash:/feature1.bin slot 1 test
Copying file flash:/feature1.bin to slot1#flash:/feature1.bin......Done.
Verifying the file flash:/feature1.bin on slot 1.....Done.
Upgrade summary according to following table:
flash:/feature1.bin
Running Version New Version
Test 0001015 Test 0001016
Slot Upgrade Way
1 Service Upgrade
Influenced service according to following table:
flash:/feature1.bin
Feature1
The output shows that a service upgrade is recommended. The Feature1 module will be rebooted during the upgrade.
# Activate the system image in system.bin and the feature images in feature1.bin.
<Sysname> install activate system flash:/system.bin feature flash:/feature1.bin slot 1
Copying file flash:/system.bin to slot1#flash:/system.bin......Done.
Verifying the file flash:/system.bin on slot 1.....Done.
Copying file flash:/feature1.bin to slot1#flash:/feature1.bin......Done.
Verifying the file flash:/feature1.bin on slot 1.....Done.
Verifying the file flash:/feature1.bin on slot 1.....Done.
Verifying the file flash:/system.bin on slot 1.....Done.
Upgrade summary according to following table:
flash:/system.bin
Running Version New Version
Test 0001015 Test 0001016
flash:/feature1.bin
Running Version New Version
None Test 0001016
Slot Upgrade Way
0 Service Upgrade
1 Service Upgrade
Upgrading software images to compatible versions. Continue? [Y/N]:y
This operation might take several minutes, please install activate
Table 5 Command output
|
Field |
Description |
|
Verifying the file |
The system was verifying the validity of the file. |
|
Upgrade summary according to following table |
Upgrade summary. |
|
Running Version |
Version number of the running software. |
|
New Version |
Version number of the new software. |
|
Upgrade Way |
Upgrade methods: · Service Upgrade. · File Upgrade. · Reboot. |
|
Influenced service according to following table |
Services influenced by the upgrade. |
|
Install command does not support incompatible upgrade. |
The install command set does not support incompatible upgrade. |
Related commands
display install active
install commit
install deactivate
install add
Use install add to decompress an .ipe file.
Syntax
install add ipe-filename filesystem
Views
User view
Predefined user roles
network-admin
Parameters
ipe-filename: Specifies an .ipe file in the filesystemname/filename.ipe format. The file must be stored in the root directory of a file system on the device. The value string excluding the file system location section (if any) can have a maximum of 63 characters. For more information about specifying a file, see file system management in Fundamentals Configuration Guide.
filesystem: Specifies the destination file system for the software images, in the filesystemname format.
Usage guidelines
To use the install activate command to activate software images, you must use .bin image files. If the upgrade file is an .ipe file, use this command to decompress the .ipe file before you start the upgrade.
To identify software images that are included in an .ipe file, use the display install ipe-info command.
Examples
# Decompress all.ipe to the flash memory.
<Sysname> install add flash:/all.ipe flash:
Verifying the file flash:/all.ipe on slot 1...Done.
Decompressing file boot.bin to flash:/boot.bin.......................Done.
Decompressing file system.bin to flash:/system.bin.................................Done.
install commit
Use install commit to commit software changes.
Syntax
install commit
Views
User view
Predefined user roles
network-admin
Usage guidelines
Application scenarios
You must execute this command after using the following commands:
· The install activate command in an incremental upgrade.
· The install deactivate command.
· The install rollback command.
Operating mechanism
This command adds the patch image file to the startup software image list that the device used at startup.
· If the device used the main startup software image list at startup, this command adds the patch image file to the main startup software image list.
· If the device used the backup startup software image list at startup, this command adds the patch image file to the backup startup software image list.
· Both the install commit and boot-loader file commands modify the main startup software image list. However, the boot-loader file command can also modify the backup startup image list and add inactive images as main startup images.
· For more information about main and backup startup software images, see Fundamentals Configuration Guide.
Restrictions and guidelines
In a reboot upgrade, the install activate command modifies both the current and startup software image lists. You do not need to commit software changes.
Examples
# Commit software changes.
<Sysname> install commit
This operation will take several minutes, please wait...........................Done.
Related commands
install activate
install deactivate
install rollback
install deactivate
Use install deactivate to deactivate feature images and patch images.
Syntax
install deactivate feature filename&<1-30> slot slot-number
install deactivate patch filename { all | slot slot-number }
Views
User view
Predefined user roles
network-admin
Parameters
feature: Specifies a space-separated list of up to 30 feature image files.
patch: Specifies a patch image file. You can specify only one patch image file for the command at a time. However, you can execute the command multiple times to deactivate multiple patch image files.
filename: Specifies a .bin file in the filesystemname/filename.bin format. The value string can have a maximum of 63 characters. For more information about specifying a file, see file system management in Fundamentals Configuration Guide.
all: Specifies all cards.
slot slot-number: Specifies a card by its slot number.
Usage guidelines
You can deactivate only active feature and patch images.
To prevent deactivated images from running after a reboot, you must commit the software changes by using the install commit command.
Examples
# Deactivate the patch images in the route-patch.bin file.
<Sysname> install deactivate patch flash:/route-patch.bin slot 1
This operation might take several minutes, please wait...Done.
# Deactivate a patch image from a VM.
<Sysname> install deactivate patch flash:/route-patch.bin slot 1
This operation might take several minutes, please wait...Done.
Related commands
display install active
display install inactive
install remove
Use install remove to delete an inactive software image file.
Syntax
install remove [ slot slot-number ] { filename | inactive }
Views
User view
Predefined user roles
network-admin
Parameters
filename: Specifies a .bin file in the filesystemname/filename.bin format. The value string can have a maximum of 63 characters. The file must be stored in the root directory of a file system on the device. For more information about specifying a file, see file system management in Fundamentals Configuration Guide.
slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays information for all cards.
inactive: Deletes all inactive software image files in the root directories of the specified file systems.
Usage guidelines
This command permanently deletes the image files from the device. You cannot use the install rollback to command to revert the operation, or use the install abort command to abort the operation.
Examples
# Delete inactive software image file flash:/feature1.bin.
<Sysname> install remove flash:/feature1.bin
install rollback to
Use install rollback to to roll back the software to an earlier rollback point.
Syntax
install rollback to { point-id | original }
Views
User view
Predefined user roles
network-admin
Parameters
point-id: Specifies a rollback point ID. This option is supported only when there are two or more rollback points. To identify available rollback points, use the display install rollback command.
original: Rolls back to the status before any activate or deactivate operations were performed.
During an incremental upgrade, the system creates a rollback point for each activate or deactivate operation of a boot, system, or feature image. The device supports a maximum of 50 rollback points. The earliest rollback point is deleted if this limit has been reached when a rollback point is created.
During a reboot upgrade, the system does not create rollback points. After the upgrade, you can roll back the software only to the status before any activate or deactivate operations were performed.
For a rollback to take effect after a reboot, you must perform a commit operation to update the main startup software image list.
After a commit operation is performed, you cannot perform a rollback.
Patch images do not support rollback.
Examples
# Roll back the software to rollback point 1.
<Sysname>install rollback to 1
This operation might take several minutes, please wait...Done.
# Roll back the software to the original software versions and observe the change made by the rollback.
<Sysname> display install active
Active packages on slot 1:
flash:/boot.bin
flash:/system.bin
flash:/feature1.bin
<Sysname> display install rollback
Install rollback information 1 on slot 1:
Updating from no package
to flash:/feature1.bin.
The output shows that currently three image files are active but only two of them are confirmed. The image file flash:/ssh-feature-a0201.bin is not confirmed yet.
<Sysname> install rollback to original
This operation might take several minutes, please wait...Done.
<Sysname> display install active
Active packages on slot 1:
flash:/boot.bin
flash:/system.bin
<Sysname> display install committed
Committed packages on slot 1:
flash:/boot.bin
flash:/system.bin
The output shows the SSH feature has been rolled back to the original software version. The image file flash:/ssh-feature-a0201.bin has been removed.
Related commands
display install rollback
install verify
Use install verify to verify the software change commit status, image integrity, and image consistency.
Syntax
install verify
Views
User view
Predefined user roles
network-admin
Usage guidelines
Application scenarios
To ensure a successful upgrade and make sure the system can start up and operate correctly after an upgrade, execute this command to verify the following items:
· Integrity—Verify that the boot, system, and feature images are integral.
· Consistency—Verify that the same active images are running across the entire system.
· Software commit status—Verify that the active images are committed as needed.
Restrictions and guidelines
If a software image fails the verification, perform the following tasks to resolve the problem:
· To ensure software integrity, download and install the software images again.
· To guarantee software image consistency or change software commit status, use the install activate, install deactivate, and install commit commands as appropriate.
Examples
# Verify the software change confirmation status and software image integrity and consistency.
<Sysname> install verify
Active packages on slot 1 are the reference packages.
Packages will be compared with the reference packages.
This operation will take several minutes, please wait...
Verifying packages on slot 0:
Start to check active package completeness.
Verifying the file flash:/boot.bin on slot 0.....................Done.
flash:/boot.bin verification successful.
Verifying the file flash:/system.bin on slot 0.....................Done.
flash:/system.bin verification successful.
Start to check active package consistency.
Active packages are consistent with committed packages on their own board.
Active packages are consistent with the reference packages.
Verifying packages on slot 1:
Start to check active package completeness.
Verifying the file flash:/boot.bin on slot 1.....................Done.
flash:/boot.bin verification successful.
Verifying the file flash:/system.bin on slot 1.....................Done.
flash:/system.bin verification successful.
Start to check active package consistency.
Active packages are consistent with committed packages on their own board.
Active packages are consistent with the reference packages.
Verification is done.
reset install log-history oldest
Use reset install log-history oldest to clear upgrade log entries.
Syntax
reset install log-history oldest log-number
Views
User view
Predefined user roles
network-admin
Parameters
log-number: Specifies the number of upgrade log entries to be deleted.
Usage guidelines
This command clears the specified number of log entries, beginning with the oldest log entry.
Examples
# Clear the two oldest upgrade log entries.
<Sysname> reset install log-history oldest 2
Related commands
display install log
reset install rollback oldest
Use reset install rollback oldest to clear upgrade rollback points.
Syntax
reset install rollback oldest point-id
Views
User view
Predefined user roles
network-admin
Parameters
point-id: Specifies a rollback point by its ID.
Usage guidelines
|
|
CAUTION: This command clears the specified rollback point and all rollback points earlier than the specified rollback point. |
Examples
# Clear rollback point 2 and all rollback points older than rollback point 2.
<Sysname> reset install rollback oldest 2
Related commands
display install rollback
