Login
- Table of Contents
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 07-Software upgrade commands | 165.35 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> ] { all | slot slot-number } { backup | main }
boot-loader file ipe-filename [ patch filename&<1-30> ] { all | slot slot-number } { 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: This keyword is insignificant.
slot slot-number: Specifies the slot number of the device, which is fixed at 1.
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
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.
To load the specified startup software images, you must reboot the system.
|
|
NOTE: The system will verify 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. |
Examples
# Specify flash:/all.ipe as the main startup image file for slot 1.
<Sysname> boot-loader file flash:/all.ipe slot 1 main
Verifying the file flash:/all.ipe on slot 1..............Done.
H3C S6550X-32H-HI images in IPE:
boot.bin
system.bin
This command will set the main startup software images. Continue? [Y/N]:Y
Add images to slot 1.
File flash:/boot.bin already exists on slot 1.
File flash:/system.bin already exists on slot 1.
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.
Verifying the file flash:/boot.bin on slot 1...Done.
Verifying the file flash:/system.bin on slot 1.............Done.
The images that have passed all examinations will be used as the main startup software images at the next reboot on slot 1.
Related commands
display boot-loader
bootrom update
Use bootrom update to load the BootWare image from a file system to the Normal BootWare area.
Syntax
bootrom update file file slot slot-number-list
Views
User view
Predefined user roles
network-admin
Parameters
file file: Specifies the file that contains the BootWare image. The file argument represents the file name, a string of 1 to 63 characters.
slot slot-number-list: Specifies a space-separated list of up to seven slot number items. An item specifies an IRF member device by its member ID or a range of IRF member devices in the form of start-slot-number to end-slot-number. The end slot number must be equal to or greater than the start slot number.
Usage guidelines
BootWare images are contained in the .bin Comware boot image file. You can specify a Comware boot image file in this command to upgrade the BootWares in the system before you upgrade the Comware images. If you do not upgrade BootWares before upgrading Comware images, the system automatically upgrades BootWares as necessary when loading Comware images.
The new BootWare images take effect after you reboot the device.
|
|
NOTE: The system verifies a BootWare image before it loads that image to the Normal area of BootWare. If the digital signature verification fails, the system will not load the image and you will receive a digital signature verification failure message. |
Examples
# Use the file a.bin in the root directory of the flash memory to upgrade the BootWare image.
<Sysname> bootrom update file flash:/a.bin slot 1
This command will update the Boot ROM file on the specified board(s), Continue? [Y/N]:y
Now updating the Boot ROM, please wait................Done.
Related commands
boot-loader file
bootrom-update security-check enable
Use bootrom-update security-check enable to enable BootWare image validity check.
Use undo bootrom-update security-check enable to disable BootWare image validity check.
Syntax
bootrom-update security-check enable
undo bootrom-update security-check enable
Default
BootWare image validity check is enabled.
Views
System view
Predefined user roles
network-admin
Usage guidelines
Before a BootWare image upgrade starts, this feature examines the upgrade BootWare image for file validity and incompatibility with hardware. If the BootWare image passes the check, the upgrade process starts. If the check fails, the system does not perform the upgrade.
Examples
# Enable BootWare image validity check.
<Sysname> system-view
[Sysname] bootrom-update security-check enable
display boot-loader
Use display boot-loader to display current software images and startup software images.
Syntax
display boot-loader [ slot slot-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies the slot number of the device, which is fixed at 1.
Examples
# Display the current software images and startup software images.
<Sysname> display boot-loader
Software images on slot 1:
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.bin
flash:/system.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
display install active
Use display install active to display active software images.
Syntax
display install active [ slot slot-number ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies the slot number of the device, which is fixed at 1.
verbose: Displays detailed information. If you do not specify this keyword, the command displays only image names.
Examples
# Display brief information about 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: S6550X
Service name: boot
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu
[Component]
Component: boot
Description: boot package
flash:/system.bin
[Package]
Vendor: H3C
Product: S6550X
Service name: system
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu
[Component]
Component: system
Description: system package
flash:/feature1.bin
[Package]
Vendor: H3C
Product: S6550X
Service name: test
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu
[Component]
Component: test
Description: test package
|
Field |
Description |
|
[Package] |
Detailed information about the software image. |
|
Service name |
Image type: · boot—Boot image. · boot-patch—Boot image patch. · system—System image. · system-patch—System image patch. · Any other value indicates a feature image. |
|
Platform version |
Platform software version. |
|
Product version |
Product software version. |
|
Supported board |
Device type supported by the software image: · mpu—Centralized device. |
|
[Component] |
Information about components included in the image file. |
|
Component |
Component name. |
|
Description |
Component description. |
Related commands
install activate
display install backup
Use display install backup to display backup 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 the slot number of the device, which is fixed at 1.
verbose: Displays detailed information. If you do not specify this keyword, the command displays only image names.
Usage guidelines
Backup startup images are used only when the main boot or system image is missing or corrupt. For more information, see Fundamentals Configuration Guide.
To modify the backup startup image list, use the boot-loader file command.
Examples
# Display brief information about backup software images.
<Sysname> display install backup
Backup startup software images on slot 1:
flash:/boot.bin
flash:/system.bin
# Display detailed information about backup software images.
<Sysname> display install backup verbose
Backup startup software images on slot 1:
flash:/boot.bin
[Package]
Vendor: H3C
Product: S6550X
Service name: boot
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu
[Component]
Component: boot
Description: boot package
flash:/system.bin
[Package]
Vendor: H3C
Product: S6550X
Service name: system
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu
[Component]
Component: system
Description: system 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 the slot number of the device, which is fixed at 1.
verbose: Displays detailed information. If you do not specify this keyword, the command displays only image names.
Usage guidelines
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.
Both the install commit and boot-loader file commands modify the main startup software image list.
Examples
# Display brief information about 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: S6550X
Service name: boot
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu
[Component]
Component: boot
Description: boot package
flash:/system.bin
[Package]
Vendor: H3C
Product: S6550X
Service name: system
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu
[Component]
Component: system
Description: system package
flash:/feature1.bin
[Package]
Vendor: H3C
Product: S6550X
Service name: feature1
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu
[Component]
Component: feature1
Description: feature1 package
For information about the command output, see Table 2.
display install inactive
Use display install active 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 the slot number of the device, which is fixed at 1.
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: S6550X
Service name: feature1
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu
[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.
H3C S6550X-32H-HI images in IPE:
boot.bin
system.bin
Related commands
display install package
display install job
Use display install job to display ongoing ISSU activate, deactivate, and rollback operations.
Syntax
display install job
Views
Any view
Predefined user roles
network-admin
network-operator
Examples
# Display ongoing ISSU activate, deactivate, and rollback operations.
<Sysname> display install job
JobID:5
Action:install activate flash:/feature1.bin on slot 1
The output shows that the device is executing the install activate flash:/feature1.bin slot 1 command.
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: S6550X
Service name: system
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu
# Display detailed information about system.bin.
<Sysname> display install package flash:/system.bin verbose
flash:/system.bin
[Package]
Vendor: H3C
Product: S6550X
Service name: system
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu
[Component]
Component: system
Description: system package
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
Use this command to identify available rollback points during an ISSU that uses install commands.
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
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 the slot number of the device, which is fixed at 1.
Usage guidelines
A component is a collection of features. The features of a component are installed or uninstalled at the same time.
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.
This command searches only the root directories of the file systems at the specified location.
Examples
# Display the software image file that includes pkg_ctr.
<Sysname> display install which file pkg_ctr
Verifying the file flash:/system-t0001015.bin on slot 1..........................Done.
Found pkg_ctr in flash:/system-t0001015.bin on slot 1.
flash:/system-t0001015.bin
[Package]
Vendor: H3C
Product: S6550X
Service name: system
Platform version: 7.1.070
Product version: Test 0001015
Supported board: cen
Verifying the file flash:/boot-d2601007.bin on slot 1.....Done.
Table 3 Command output
|
Field |
Description |
|
Verifying the file |
The system was verifying the validity of the file. |
|
[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: cen—Centralized device. |
display version
Use display version to display system version information.
Syntax
display version
Views
Any view
Predefined user roles
network-admin
network-operator
Examples
# Display system version information.
<Sysname> display version
H3C Comware Software, Version 9.1.043, ESS 1108
Copyright (c) 2004-2022 New H3C Technologies Co., Ltd. All rights reserved.
H3C S6550X-32H-HI uptime is 0 weeks, 0 days, 11 hours, 10 minutes
Last reboot reason : Cold reboot
Boot image: flash:/s6550x-cmw910-boot-e1108.bin
Boot image version: 9.1.043, ESS 1108
Compiled Feb 17 2022 05:00:00
System image: flash:/s6550x-cmw910-system-e1108.bin
System image version: 9.1.043, ESS 1108
Compiled Feb 17 2022 05:00:00
...
Table 4 Command output
|
Field |
Description |
|
Last reboot reason |
Reason for the last reboot: · User reboot—The reboot was manually initiated from a user interface, such as the CLI or SNMP. · Cold reboot—The reboot was caused by a power cycle. · Kernel abnormality reboot—The reboot was caused by kernel exceptions. · DeadLoop reboot—The reboot was caused by a kernel thread dead loop. · DEV HandShake reboot—The reboot was caused by a device management handshake failure. · Auto Update reboot—The reboot was caused by an automatic software upgrade. · Memory exhaust reboot—The reboot was caused by a memory-exhausted event. · Recover GOLD-detected error—The reboot was caused by a failed GOLD test. · Critical process abnormality reboot—The reboot was caused by core process abnormality. |
display version-update-record
Use display version-update-record to display startup software image upgrade records.
Syntax
display version-update-record
Views
Any view
Predefined user roles
network-admin
network-operator
Usage guidelines
The device records its current startup software version information whenever it starts up, and records all software version update information. Such information can survive reboots.
Examples
# Display the startup software image upgrade records.
<Sysname> display version-update-record
Record 1 (updated on Jan 18 2020 at 06:23:54):
*Name : comware-cmw710-boot.bin
Version : 7.1.070 Test 0001
Compile time: Jan 25 2020 15:52:43
*Name : comware-cmw710-system.bin
Version : 7.1.070 Test 0001
Compile time: Jan 25 2020 15:52:43
|
Field |
Description |
|
Record n (updated on Jan 18 2020 at 06:23:54) |
Number of the startup software image upgrade record. Record 1 is the most recent record. The time in parentheses is UTC time. |
|
Name |
Software image file name. |
|
* |
The software image version changed during the upgrade. |
Related commands
reset version-update-record
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 ISSU operation. If you do not specify this argument, the command aborts all ongoing software image activate and deactivate operations.
Usage 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.
When you abort an ongoing activate or deactivate operation, the system rolls back to the status it was in before the operation was started.
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 feature or patch images.
Syntax
install activate 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
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.
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 file system management in Fundamentals Configuration Guide.
all: This keyword is insignificant.
slot slot-number: Specifies the slot number of the device, which is fixed at 1.
test: Only identifies the ISSU method to be used for the upgrade. If you do not specify this keyword, the command activates the specified software images.
Usage guidelines
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 ISSU method for feature upgrade with feature1.bin on the device and the upgrade impact.
<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 patch image in patch1.bin on the device.
<Sysname> install activate patch flash:/patch1.bin slot 1
Copying file flash:/patch1.bin to slot1#flash:/patch1.bin......Done.
Verifying the file flash:/patch1.bin on slot 1.....Done.
This operation might take several minutes, please wait...Done.
Table 6 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 |
ISSU methods: · Service Upgrade. · File Upgrade. · Reboot. This field is displayed only for an upgrade to a compatible version. For more information about ISSU methods, see Fundamentals Configuration Guide. |
|
Influenced service according to following table |
Services influenced by the 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
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.
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.
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.
Both the install commit and boot-loader file commands modify the main startup software image list. To modify the backup startup image list or add inactive images as main startup images, however, you must use the boot-loader file command.
For more information about main and backup startup software images, see Fundamentals Configuration Guide.
Examples
# Commit software changes.
<Sysname> install commit
This operation will take several minutes, please wait...........................Done.
The current software images have been saved as the startup software images.
Current software images on slot 1:
flash:/boot.bin
flash:/system.bin
Related commands
install activate
install deactivate
install rollback
install deactivate
Use install deactivate to deactivate feature or 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 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 file system management in Fundamentals Configuration Guide.
all: This keyword is insignificant.
slot slot-number: Specifies the slot number of the device, which is fixed at 1.
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 route-patch.bin on the device.
<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
slot slot-number: Specifies the slot number of the device, which is fixed at 1.
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. The file system name cannot contain file system location information. For more information about specifying a file, see file system management in Fundamentals Configuration Guide.
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-t0001015.bin
flash:/system-t0001015.bin
flash:/feature1-t0001015.bin
<Sysname> display install rollback
Install rollback information 1 on slot 1:
Updating from no package
to flash:/feature1-t0001015.bin.
The output shows that currently three image files are active but only two of them are confirmed. Image file flash:/feature1-t0001015.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-t0001015.bin
flash:/system-t0001015.bin
<Sysname> display install committed
Committed packages on slot 1:
flash:/boot-t0001015.bin
flash:/system-t0001015.bin
The output shows the SSH feature has been rolled back to the original software version. The image file flash:/feature1-t0001015.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
To ensure a successful ISSU and make sure that the system can start up and operate correctly after an ISSU, 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.
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 1:
Start to check active package completeness.
Verifying the file flash:/boot-t0001015.bin on slot 1.....................Done.
flash:/boot-t0001015.bin verification successful.
Verifying the file flash:/system-t0001015.bin on slot 1.....................Done.
flash:/system-t0001015.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 2:
Start to check active package completeness.
Verifying the file flash:/boot-t0001015.bin on slot 2.....................Done.
flash:/boot-t0001015.bin verification successful.
Verifying the file flash:/system-t0001015.bin on slot 2.....................Done.
flash:/system-t0001015.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 version-update-record
Use reset version-update-record to clear startup software image upgrade records.
Syntax
reset version-update-record
Views
System view
Predefined user roles
network-admin
Examples
# Clear the startup software image upgrade records.
<Sysname> system-view
[Sysname] reset version-update-record
This command will delete all records of version update. Continue? [Y/N]:y
Related commands
display version-update-record
