Login
- Table of Contents
-
- 01-Fundamentals Command Reference
- 00-Preface
- 01-CLI commands
- 02-RBAC commands
- 03-Login management commands
- 04-FTP and TFTP commands
- 05-File system management commands
- 06-Configuration file management commands
- 07-Software upgrade commands
- 08-Emergency shell commands
- 09-Automatic configuration commands
- 10-Device management commands
- 11-Tcl commands
- 12-Python commands
- 13-License management commands
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 07-Software upgrade commands | 161.01 KB |
Software upgrade commands
As a best practice, store the startup images in the factory default file system. 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
In standalone mode:
boot-loader file boot filename system filename [ feature filename&<1-30> ] { all | slot slot-number } { backup | main }
boot-loader file ipe-filename { all | slot slot-number } { backup | main }
In IRF mode:
boot-loader file boot filename system filename [ feature filename&<1-30> ] { all | chassis chassis-number slot slot-number } { backup | main }
boot-loader file ipe-filename { all | chassis chassis-number 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.
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.
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 file system management in Fundamentals Configuration Guide.
all: Specifies all hardware components to which the specified images apply.
slot slot-number: Specifies the slot number of an MPU. (In standalone mode.)
chassis chassis-number slot slot-number: Specifies an MPU in the IRF fabric. The chassis-number argument represents the IRF member ID of the device that holds the MPU. The slot-number argument represents the slot number of the MPU. (In IRF mode.)
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.
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.
To load the specified startup software images, you must reboot the system.
If the upgrade images are not found in the file system on the slot specified to upgrade, the system automatically copies the images to that file system. The destination directory is the root directory of the file system. If the destination root directory already contains a startup image with the same name as an upgrade image, you must choose whether to overwrite the image.
Incremental patches cannot be installed by using the boot-loader file command.
Examples
# (In standalone mode.) 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 MSR56-60 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 or rename the new file? [Yes/No/Rename]: 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.
# (In standalone mode.) Specify flash:/all.ipe as the main startup image file.
<Sysname> boot-loader file flash:/all.ipe all main
Verifying the file flash:/all.ipe on slot 1..............Done.
H3C MSR56-60 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 or rename the new file? [Yes/No/Rename]: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.
File flash:/boot.bin already exists on slot 0.
Do you want to overwrite the file?
Y: Overwrite the file.
N: Not overwrite the file.
A: From now on, overwrite or not overwrite without prompt.
Please make a choice. [Y/N/A]:a
What type of overwrite operation do you want to perform?
Y: Overwrite without prompt.
N: Not overwrite or display prompt.
Q: Return to the previous step.
Please make a choice. [Y/N/Q]:Y
An existing file will be overwritten without prompt if it has the same name as any upgrade file.
Loading......................Done.
Loading......................Done.
The images that have passed all examinations will be used as the main startup software images at the next reboot on slot 0.
Decompression completed.Do you want to delete flash:/all.ipe now? [Y/N]:N
Related commands
display boot-loader
boot-loader update
Use boot-loader update to synchronize startup images.
Syntax
In standalone mode:
boot-loader update { all | slot slot-number }
In IRF mode:
boot-loader update { all | chassis chassis-number slot slot-number }
Views
User view
Predefined user roles
network-admin
Parameters
all: Synchronizes startup images from the active MPU to the standby MPU. (In standalone mode.)
all: Synchronizes startup images from the global active MPU to all standby MPUs. (In IRF mode.)
slot slot-number: Specifies the slot number of the standby MPU. (In standalone mode.)
chassis chassis-number slot slot-number: Specifies a standby MPU. The chassis-number argument represents the IRF member ID of the device that holds the MPU. The slot-number argument represents the slot number of the MPU. (In IRF mode.)
Usage guidelines
You can use this command to synchronize startup images after adding new MPUs.
If any of the startup software images require a license, register and activate a license for the image on the new MPU before executing this command. Use the display license feature command to verify the licensing state of software images.
The images used for synchronization are in the main or backup startup software images list instead of the current software images list (see the display boot-loader command).
· The main images list is used if the active MPU (in standalone mode) or global active MPU (in IRF mode) started up with the main startup images.
· The backup image list is used if the active MPU (in standalone mode) or global active MPU (in IRF mode) started up with the backup startup images.
The startup images synchronized to a standby MPU are set as main startup images, regardless of whether the source startup images are main or backup.
If an upgrade has been performed by using install commands or a patch has been installed, use the install commit command to update the main startup images on the active MPU (in standalone mode) or global active MPU (in IRF mode) before software synchronization. This command ensures startup image consistency between the active MPU or (in standalone mode) or global active MPU (in IRF mode) and standby MPUs.
Startup image synchronization fails if any software image being synchronized is not available or is corrupted.
Examples
# Synchronize startup images from the active MPU to the standby MPU in slot 1.
<Sysname> boot-loader update slot 2
This command will update the specified standby MPU. Continue? [Y/N]:y
Updating. Please wait...
Verifying the file flash:/boot.bin on slot 1...Done.
Verifying the file flash:/system.bin on slot 1....Done.
Copying main startup software images to slot 2. Please wait...
Done.
Setting copied images as main startup software images for slot 2...
The images that have passed all examinations will be used as the main startup software images at the next reboot on slot 2.
Done.
Successfully updated the startup software images of slot 2.
display boot-loader
install commit
bootrom update
Use bootrom update to load the BootWare image from a file system to the Normal BootWare area.
Syntax
In standalone mode:
bootrom update file file slot slot-number-list [ subslot subslot-number-list ] [ all | part ]
In IRF mode:
bootrom update file file chassis chassis-number slot slot-number-list [ subslot subslot-number-list ] [ all | part ]
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 a card by its slot number or a range of cards 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. (In standalone mode.)
chassis chassis-number: Specifies an IRF member device by its member ID. (In IRF mode.)
slot slot-number-list: Specifies a space-separated list of up to seven slot number items. An item specifies a card by its slot number or a range of cards in the form of start-slot-number to end-slot-number on the specified IRF member device. The end slot number must be equal to or greater than the start slot number. (In IRF mode.)
subslot subslot-number-list: Specifies a list of up to seven subslot number items. Each item specifies a subcard by its subslot number or a range of subcards in the form of start-subslot-number to end-subslot-number. If you do not specify a subcard, this command loads the BootWare image for the base card.
all: Loads the entire BootWare image, including the basic segment and the extended segment. If you do not specify the all or part keyword, this command restores the entire BootWare image.
part: Loads the extended BootWare image section.
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 card.
Examples
# (In standalone mode.) 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
display boot-loader
Use display boot-loader to display current software images and startup software images.
Syntax
In standalone mode:
display boot-loader [ slot slot-number ]
In IRF mode:
display boot-loader [ chassis chassis-number [ slot slot-number ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies the slot number of an MPU. If you do not specify an MPU, this command displays the software images on each MPU. (In standalone mode.)
chassis chassis-number [ slot slot-number ]: Specifies an IRF member device or an MPU in an IRF member device. The chassis-number argument represents the IRF member ID of the device. The slot-number argument represents the slot number of the MPU on the device. If you do not specify an IRF member device, this command displays the software images on each MPU in the IRF fabric. If you specify an IRF member device without specifying an MPU, this command displays the software images on each MPU on the specified member device. (In IRF mode.)
Examples
# (In standalone mode.) 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
In standalone mode:
display install active [ slot slot-number ] [ verbose ]
In IRF mode:
display install active [ chassis chassis-number 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 on the device. (In standalone mode.)
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command displays information for all cards on the IRF fabric. (In IRF mode.)
verbose: Displays detailed information. If you do not specify this keyword, the command displays only image names.
Examples
# (In standalone mode.) 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
# (In standalone mode.) Display detailed information about active software images.
<Sysname> display install active verbose
Active packages on slot 1:
flash:/boot.bin
[Package]
Vendor: H3C
Product: MSR56
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: MSR56
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: MSR56
Service name: test
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu
[Component]
Component: test
Description: test package
Table 2 Command output
|
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 |
Card type supported by the software image: · mpu—MPU. · spu or spe—Service card. |
|
[Component] |
Information about components included in the image file. |
|
Component |
Component name. |
|
Description |
Component description. |
Related commands
install active
display install backup
Use display install backup to display backup startup software images.
Syntax
In standalone mode:
display install backup [ slot slot-number ] [ verbose ]
In IRF mode:
display install backup [ chassis chassis-number 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 on the device. (In standalone mode.)
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command displays information for all cards on the IRF fabric. (In IRF mode.)
verbose: Displays detailed information. If you do not specify this keyword, the command displays only image names.
Usage guidelines
If any main image does not exist or is invalid, the system loads the backup startup software images.
You can use the boot-loader file command to modify the backup startup software image list.
Examples
# (In standalone mode.) Display brief information about backup startup software images.
<Sysname> display install backup
Backup startup software images on slot 1:
flash:/boot.bin
flash:/system.bin
# (In standalone mode.) 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: MSR56
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: MSR56
Service name: system
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu
[Component]
Component: system
Description: system package
Related commands
boot-loader file
display install committed
display install committed
Use display install committed to display main startup software images.
Syntax
In standalone mode:
display install committed [ slot slot-number ] [ verbose ]
In IRF mode:
display install committed [ chassis chassis-number 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 on the device. (In standalone mode.)
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command displays information for all cards on the IRF fabric. (In IRF mode.)
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
# (In standalone mode.) 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
# (In standalone mode.) 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: MSR56
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: MSR56
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: MSR56
Service name: feature1
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu
[Component]
Component: feature1
Description: feature1 package
Related commands
boot-loader file
display install backup
install commit
display install inactive
Use display install inactive to display inactive software images.
Syntax
In standalone mode:
display install inactive [ slot slot-number ] [ verbose ]
In IRF mode:
display install inactive [ chassis chassis-number 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 on the device. (In standalone mode.)
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command displays information for all cards on the IRF fabric. (In IRF mode.)
verbose: Displays detailed information. If you do not specify this keyword, the command displays only image names.
Examples
# (In standalone mode.) Display brief information about inactive software images.
<Sysname> display install inactive
Inactive packages on slot 1:
flash:/feature1.bin
# (In standalone mode.) Display detailed information about inactive software images.
<Sysname> display install inactive verbose
Inactive packages on slot 1:
flash:/feature1.bin
[Package]
Vendor: H3C
Product: MSR56
Service name: feature1
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu
[Component]
Component: feature1
Description: feature1 package
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 saved 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
# (In standalone mode.) 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 MSR56 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
# (In standalone mode.) Display ongoing 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 log
Use display install log to display log information for upgrades that used install commands.
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 log entries.
verbose: Displays detailed log information. If you do not specify this keyword, the command displays brief log information.
Usage guidelines
The device creates one log entry for each upgrade operation to track the upgrade process and operation result.
The upgrade log can contain a maximum of 50 entries. The latest entry overwrites the oldest entry if the log is full.
Examples
# (In standalone mode.) Display all log entries for upgrades that used install commands.
<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.
# (In standalone mode.) Displays detailed information about log entry 1 for the upgrade that used install commands.
<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.
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 saved 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 active MPU's file systems. (In standalone mode.)
all: Specifies all software image files in the root directories of the file systems on the global active MPU. (In IRF mode.)
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: MSR56
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: MSR56
Service name: system
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu
[Component]
Component: system
Description: system package
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
The system does not record rollback points during an upgrade that uses install commands.
Examples
# (In standalone mode.) 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
· 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
In standalone mode:
display install which { component name | file filename } [ slot slot-number ]
In IRF mode:
display install which { component name | file filename } [ chassis chassis-number 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 on the device. (In standalone mode.)
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command displays information for all cards on the IRF fabric. (In IRF mode.)
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
# (In standalone mode.) 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: MSR56
Service name: system
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu
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: · mpu—MPU. · spu or spe—Service card. |
display version comp-matrix
Use display version comp-matrix to display the recommended upgrade methods.
Syntax
display version comp-matrix file { boot filename | system filename | feature filename&<1-30> } *
display version comp-matrix file ipe ipe-filename
Views
Any view
Predefined user roles
network-admin
network-operator
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.
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.
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.
Usage guidelines
If one or more images are incompatible, the incompatible upgrade method applies. The entire system needs to be rebooted during an incompatible upgrade.
Examples
# (In standalone mode.) Display the recommended upgrade method.
<Sysname> display version comp-matrix file feature flash:/feature1-t0001015.bin
Verifying the file flash:/feature1-t0001015.bin on slot 0.....Done.
Slot Upgrade Way
0 Service Upgrade
1 Service Upgrade
2 Service Upgrade
Influenced service according to following table on slot 0:
flash:/feature1-t0001015.bin
Feature1
Influenced service according to following table on slot 2:
flash:/feature1-t0001015.bin
Feature1
Influenced service according to following table on slot 1:
flash:/feature1-t0001015.bin
Feature1
Table 4 Command output
|
Field |
Description |
|
Verifying the file |
The system was verifying the validity of the file. |
|
Influenced service according to following table |
Services that will be affected by the upgrade. This field is displayed only for compatible versions. |
|
Incompatible upgrade |
You are upgrading the software to an incompatible version. |
|
Upgrade Way |
Upgrade method: · Service Upgrade. · File Upgrade. · Reboot. This field is displayed only for compatible versions. |
firmware update
Use firmware update to upgrade firmware.
Syntax
In standalone mode:
firmware update slot slot-number [ subslot subslot-number ] { cpld cpld-number | fpga fpga-number | module module-number } file filename
In IRF mode:
firmware update chassis chass-number slot slot-number [ subslot subslot-number ] { cpld cpld-number | fpga fpga-number | module module-number } file filename
Views
User view
Predefined user roles
network-admin
Parameters
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the IRF member ID. The slot-number argument represents the slot number of the card. (In IRF mode.)
slot slot-number: Specifies a card by its slot number. (In standalone mode.)
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.
module module-number: Specifies a module 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 file system management in Fundamentals Configuration Guide.
Usage guidelines
Use this command to upgrade firmware for the CPLD, which does not run Comware and 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.
· Execute the power-supply off command, and then execute the power-supply on command.
Examples
# (In standalone mode.) Upgrade CPLD 1 in slot 1.
<Sysname> firmware update slot 1 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.
install abort
Use install abort to abort ongoing upgrade operations performed by using install commands.
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
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. You can abort only ongoing activate and deactivate operations.
When you abort an ongoing activate or deactivate operation, the system rolls back to the status it was in before the operation was started.
To obtain the ID of a job, use the display install job command.
Examples
# Abort all ongoing upgrade operations.
<Sysname> install abort
Related commands
display install job
install activate
Use install activate to activate software images.
Syntax
In standalone mode:
install activate { boot filename | system filename | feature filename&<1-30> } * slot slot-number
install activate patch filename { all | slot slot-number }
In IRF mode:
install activate { boot filename | system filename | feature filename&<1-30> } * chassis chassis-number slot slot-number
install activate patch filename { all | chassis chassis-number 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.
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 on the device. (In standalone mode.)
all: Specifies all cards on the IRF fabric. (In IRF mode.)
slot slot-number: Specifies a card by its slot number. (In standalone mode.)
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. (In IRF mode.)
Usage guidelines
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.
Images run in memory immediately after they are activated. However, only images activated by using the install activate patch filename all command still run in memory after a reboot. For other images to take effect after a reboot, you must commit the software change by using the install commit command.
If the specified files are not stored on the MPU to be upgraded, the command copies the files to the MPU automatically.
If the specified files are not stored on the security engine to be upgraded, the command copies the files to the security engine automatically.
(In standalone mode.) If you specify the active MPU for the slot slot-number option, the command takes effect on the active MPU and all LPUs. If you specify the standby MPU for the slot slot-number option, the command takes effect only on the standby MPU.
(In IRF mode.) If you specify the global active MPU for the chassis chassis-number slot slot-number option, the command takes effect on the global active MPU and all LPUs. If you specify a standby MPU for the chassis chassis-number slot slot-number option, the command takes effect on the standby MPU.
(In IRF mode.) At reboot, a subordinate device automatically synchronizes the master device's configuration and status data. You must wait for the synchronization to complete before using the install activate command on the subordinate device. To identify whether the synchronization is complete, use the display system stable state command. The synchronization is complete if the System State field displays Stable.
Examples
# (In standalone mode.) Activate the system image in system.bin and the feature images in feature1.bin on the standby MPU (in slot 1).
<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
1 Service Upgrade
Upgrading software images to compatible versions. Continue? [Y/N]:y
This operation might take several minutes, please wait...Done.
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. This field is displayed only for an upgrade to a compatible version. This field is not supported in the current software version. |
|
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
Before you use this command, read the release notes to identify software image licensing requirements. Make sure the device has valid licenses for all license-based images.
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. To modify the backup startup image list or add inactive images as main startup images, however, you must use the boot-loader file command.
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
In standalone mode:
install deactivate feature filename&<1-30> slot slot-number
install deactivate patch filename { all | slot slot-number }
In IRF mode:
install deactivate feature filename&<1-30> chassis chassis-number slot slot-number
install deactivate patch filename { all | chassis chassis-number slot slot-number }
Views
User view
Predefined user roles
network-admin
Parameters
feature: Specifies feature image files. You can specify 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 saved 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 on the device. (In standalone mode.)
all: Specifies all cards on the IRF fabric. (In IRF mode.)
slot slot-number: Specifies a card by its slot number. (In standalone mode.)
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. (In IRF mode.)
Usage guidelines
At reboot, a subordinate device automatically synchronizes the master device's configuration and status data. You must wait for the synchronization to complete before using the install deactivate command on the subordinate device. To identify whether the synchronization is complete, use the display system stable state command. The synchronization is complete if the System State field displays Stable.
You can deactivate only active feature and patch images.
Images deactivated by using the install deactivate patch filename all command do not run after a reboot. To prevent other deactivated images from running after a reboot, you must commit the software change by using the install commit command.
Examples
# (In standalone mode.) Deactivate the patch images in the route-patch.bin file for a slot.
<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
In standalone mode:
install remove [ slot slot-number ] { filename | inactive }
In IRF mode:
install remove [ chassis chassis-number 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. 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.
slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command deletes inactive software images from all cards. (In standalone mode.)
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command deletes inactive software images from all cards. (In IRF mode.)
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 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 software 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 make sure the system can start up and operate correctly after an upgrade performed by using install commands, 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 the device are the reference packages.
Packages will be compared with the reference packages.
This operation will take several minutes, please wait...
Verifying packages on the device:
Start to check active package completeness.
Verifying the file flash:/boot-t0001015.bin on the device...........Done.
flash:/boot-t0001015.bin verification successful.
Verifying the file flash:/system-t0001015.bin on the device............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.
# (In standalone mode.) 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-t0001015.bin on slot 0.....................Done.
flash:/boot-t0001015.bin verification successful.
Verifying the file flash:/system-t0001015.bin on slot 0.....................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 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.
Verification is done.
# 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 install log-history oldest
Use reset install log-history oldest to clear log entries for upgrade operations performed by using install commands.
Syntax
reset install log-history oldest log-number
Views
User view
Predefined user roles
network-admin
Parameters
log-number: Specifies the number of 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 log entries for upgrade operations performed by using install commands.
<Sysname> reset install log-history oldest 2
Related commands
display install log
reset install rollback oldest
Use reset install rollback oldest to clear rollback points for upgrade operations performed by using install commands.
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
This command clears the specified rollback point and all rollback points older 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
version auto-update enable
Use version auto-update enable to enable software synchronization from active MPU to standby MPU at startup.
Use undo version auto-update enable to disable this feature.
Syntax
version auto-update enable
undo version auto-update enable
Default
Software synchronization from active MPU to standby MPU is enabled. If software inconsistency is detected at startup, the standby MPU loads the current software images of the active MPU.
Views
System view
Predefined user roles
network-admin
Usage guidelines
This command is available in standalone mode.
To make sure the standby MPU always runs the same software images as the active MPU, configure both the version auto-update enable command and the undo version check ignore command.
The startup software version check feature examines the standby MPU's startup software images for version inconsistency with the active MPU's current software images at startup. If their software versions are different, the standby MPU copies the current software images of the active MPU, specifies them as main startup software images, and reboots with these images.
To ensure a successful synchronization in a multiuser environment, make sure no one reboots or swaps MPUs during the software synchronization process. You can configure the information center to output the synchronization status to configuration terminals (see Network Management and Monitoring Configuration Guide).
Examples
# Enable software auto-update for the standby MPU.
<Sysname> system-view
[Sysname] version auto-update enable
Related commands
version check ignore
version check ignore
Use version check ignore to disable startup software version check for the standby MPU at startup.
Use undo version check ignore to enable this feature.
Syntax
version check ignore
undo version check ignore
Default
The startup software images on the standby MPU are checked for version inconsistency with the current software images on the active MPU.
Views
System view
Predefined user roles
network-admin
Usage guidelines
This command is available in standalone mode.
When the standby MPU starts up, this command disables the system to examine the standby MPU's startup software images for version inconsistency with the active MPU's current software images. The standby MPU can start up with a different software version than the active MPU.
To avoid anomalies, do not disable startup software version check for the standby MPU unless for software upgrade.
To make sure the standby MPU always runs the same software images as the active MPU, configure both the version auto-update enable command and the undo version check ignore command.
Examples
# Enable startup software version check for the standby MPU.
<Sysname> system-view
[Sysname] undo version check ignore
Related commands
version auto-update enable
