Login
- Table of Contents
-
- 01-Fundamentals Command Reference
- 00-Preface
- 01-RBAC commands
- 02-License management commands
- 03-RAID management commands (security devices)
- 04-Software upgrade commands
- 05-ISSU commands
- 06-Automatic configuration commands
- 07-Tcl commands
- 08-Python commands
- 09-Device management commands
- 10-Configuration file management commands
- 11-File system management commands
- 12-Login management commands
- 13-FTP and TFTP commands
- 14-CLI commands
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 04-Software upgrade commands | 237.43 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
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.
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.
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.
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 IRF member ID of a member device.
backup: Specifies the files as backup startup image files. Backup images are used only when main images are not available.
main: Specifies the files as main startup image files. The device always first attempts to start up with main startup files.
Usage guidelines
Prerequisites
Before you specify startup image files, register and activate a license for each upgrade image that requires a license. If a license-based software image lacks a license, the command execution result is as follows:
· If .bin files are specified, the command cannot be executed.
· If an .ipe file is specified, the command sets all images as startup images except for the image that does not have a license.
For more information about licensing, see Fundamentals Configuration Guide.
Application scenarios
When the current software cannot meet the requirements of network operation or user services, you can use this command to upgrade the software to optimize device performance to meet the requirements.
Operating mechanism
The boot-loader file command overwrites the entire startup image list. To add new startup feature images, specify all feature image files in the old startup image list, including feature image files. The new startup image list will contain only the feature image files that are specified in the command.
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.
Restrictions and guidelines
The system verifies the digital signature of the specified images before it updates the startup image list with the specified images. If the digital signature verification fails, the system will not update the startup image list and you will receive a digital signature verification failure message.
To load the specified startup software images, you must reboot the system.
Incremental patches cannot be installed by using the boot-loader file command.
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.
F5000-AK9130 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.
# Specify flash:/all.ipe as the main startup image file for all IRF member devices.
<Sysname> boot-loader file slot1#flash:/all.ipe all main
Verifying the file flash:/all.ipe on slot 1......................................Done.
F5000-AK9130 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.
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 2.
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.
Loading......................Done.
Loading......................Done.
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 2.
The images that have passed all examinations will be used as the main startup software images at the next reboot on slot 3.
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
boot-loader update { all | slot slot-number }
Views
User view
Predefined user roles
network-admin
Parameters
all: Synchronizes startup images from the master to all subordinate devices.
slot slot-number: Specifies the IRF member ID of a subordinate device.
Usage guidelines
Prerequisites
If any of the startup software images require a license, register and activate a license for the image on the new subordinate device before executing this command. Use the display license feature command to verify the licensing state of software images.
Application scenarios
You can use this command to synchronize startup images after adding new member devices.
Operating mechanism
The startup images synchronized to the subordinate device are set as main startup images, regardless of whether the source startup images are main or backup.
· If the master device has started up with main startup images, its main startup images are synchronized to the subordinate device, regardless of whether any main startup image has been respecified on the master device.
· If the master device has started up with backup startup images, its backup startup images are synchronized to the subordinate device, regardless of whether any backup startup image has been respecified on the master device.
Restrictions and guidelines
If a patch installation or ISSU has been performed on the master, use the install commit command to update the set of main startup images on the master before software synchronization. This command ensures startup image consistency between the master and the subordinate device.
Do not reboot any member device during the execution of the boot-loader update command. Member devices might not be able to come up.
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 1
This command will update the specified standby MPU. Please do not reboot any MPU during the upgrade. 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.
Successfully updated the startup software images of slot 1.
Related commands
display boot-loader
install commit
bootrom backup
Use bootrom backup to back up the BootWare image in the Normal area to the Backup area on a BootWare.
Syntax
bootrom backup slot slot-number-list [ all | part ]
Views
User view
Predefined user roles
network-admin
Parameters
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.
all: Backs up the entire BootWare image, including the basic segment and the extended segment. If you do not specify the all or part keyword, this command backs up the entire BootWare image.
part: Backs up the extended BootWare image section.
Usage guidelines
A BootWare is divided into a Normal area and a Backup area. The BootWare image is stored in the Normal area and backed up to the Backup area. At startup, the system reads the BootWare image automatically from the Normal area. If the image is inaccessible, the system reads the BootWare image from the Backup area.
If the BootWare image in the Normal area is corrupted or requires a version rollback, use the bootrom restore command to copy the BootWare image in the Backup area to the Normal area.
Examples
# Back up the entire BootWare image from the Normal area to the Backup area.
<Sysname> bootrom backup slot 1
Now backing up the Boot ROM, please wait...
......Done.
Related commands
bootrom restore
bootrom read
Use bootrom read to back up the BootWare image in the Normal area of a BootWare to the default file system.
Syntax
bootrom read slot slot-number-list [ all | part ]
Views
User view
Predefined user roles
network-admin
Parameters
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.
all: Backs up the entire BootWare image, including the basic segment and the extended segment. If you do not specify the all or part keyword, this command backs up the entire BootWare image.
part: Backs up the extended BootWare image section.
Usage guidelines
For each BootWare image you are backing up, this command creates two files in the default file system: basicbtm.bin for the basic segment and extendbtm.bin for the extended segment.
Examples
# Back up the BootWare image from the Normal area of BootWare to the flash memory.
<Sysname> bootrom read slot 1
Now reading the Boot ROM, please wait...
.........Done.
Related commands
bootrom update
bootrom restore
Use bootrom restore to replace the BootWare image in the Normal area with the BootWare image in the Backup area for image restoration or version rollback.
Syntax
bootrom restore slot slot-number-list [ all | part ]
Views
User view
Predefined user roles
network-admin
Parameters
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.
all: Restores 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: Restores the extended BootWare image section.
Examples
# Restore the entire BootWare image.
<Sysname> bootrom restore slot 1
This command will restore the Boot ROM file on the specified board(s), Continue? [Y/N]:y
Now restoring the Boot ROM, please wait...
......Done.
Related commands
bootrom backup
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 [ 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 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.
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
Application scenarios
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.
Operating mechanism
After you use this command, the system loads the specified BootWare image in the file system to the Normal area of BootWare. The system directly uses the BootWare image in the Normal area when it starts up. If the storage space is insufficient, you can delete the BootWare image file after the system has loaded the BootWare image.
Restrictions and guidelines
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.
The new BootWare images take effect after you reboot the device.
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 member ID of an IRF member device. If you do not specify a member device, this command displays the software images on each IRF member device.
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_backup.bin
flash:/system_backup.bin
# Display the current software images and startup software images.
<Sysname> display boot-loader
Software images on slot 1:
Current software images:
Image Version
flash:/boot.bin Release 0053
flash:/system.bin Release 0053
Main startup software images:
Image Version
flash:/boot.bin Release 0054
flash:/system.bin Release 0054
Backup startup software images:
Image Version
flash:/boot_1.bin --
flash:/system_1.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. |
|
Image |
Image name. |
|
Version |
Image version. If an image is corrupted or deleted, this field displays two hyphens (--). |
|
Backup startup software images |
Backup Comware images for the next startup. If the backup startup software images are not specified, this field displays None. |
Related commands
boot-loader file
display install active
Use display install active to display active software images.
Syntax
display install active [ verbose ]
display install active [ slot slot-number ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies an IRF member device by its member ID. If you do not specify an IRF member device, this command displays information for all IRF member devices.
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 the device:
flash:/boot.bin
flash:/system.bin
flash:/feature1.bin
# 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 the device:
flash:/boot.bin
[Package]
Vendor: H3C
Product: MSR36
Service name: boot
Platform version: 7.1.070
Product version: Test 0001015
Supported board: MSR36-10
[Component]
Component: boot
Description: boot package
flash:/system.bin
[Package]
Vendor: H3C
Product: MSR36
Service name: system
Platform version: 7.1.070
Product version: Test 0001015
Supported board: MSR36-10
[Component]
Component: system
Description: system package
flash:/feature1.bin
[Package]
Vendor: H3C
Product: MSR36
Service name: test
Platform version: 7.1.070
Product version: Test 0001015
Supported board: MSR36-10
[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 |
Device type supported by the software image. |
|
[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
display install backup [ verbose ]
display install backup [ slot slot-number ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies an IRF member device by its member ID. If you do not specify an IRF member device, this command displays information for all IRF member devices.
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
# Display brief information about backup startup software images.
<Sysname> display install backup
Backup startup software images on the device:
flash:/boot.bin
flash:/system.bin
# 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
# Display detailed information about backup startup software images.
<Sysname> display install backup verbose
Backup startup software images on the device:
flash:/boot.bin
[Package]
Vendor: H3C
Product: MSR36
Service name: boot
Platform version: 7.1.070
Product version: Test 0001015
Supported board: MSR36-10
[Component]
Component: boot
Description: boot package
flash:/system.bin
[Package]
Vendor: H3C
Product: MSR36
Service name: system
Platform version: 7.1.070
Product version: Test 0001015
Supported board: MSR36-10
[Component]
Component: system
Description: system package
# 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: MSR36
Service name: boot
Platform version: 7.1.070
Product version: Test 0001015
Supported board: MSR36-10
[Component]
Component: boot
Description: boot package
flash:/system.bin
[Package]
Vendor: H3C
Product: MSR36
Service name: system
Platform version: 7.1.070
Product version: Test 0001015
Supported board: MSR36-10
[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
display install committed [ verbose ]
display install committed [ slot slot-number ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies an IRF member device by its member ID. If you do not specify an IRF member device, this command displays information for all IRF member devices.
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 the device:
flash:/boot.bin
flash:/system.bin
flash:/feature1.bin
# 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 the device:
flash:/boot.bin
[Package]
Vendor: H3C
Product: MSR36
Service name: boot
Platform version: 7.1.070
Product version: Test 0001015
Supported board: MSR36-10
[Component]
Component: boot
Description: boot package
flash:/system.bin
[Package]
Vendor: H3C
Product: MSR36
Service name: system
Platform version: 7.1.070
Product version: Test 0001015
Supported board: MSR36-10
[Component]
Component: system
Description: system package
flash:/feature1.bin
[Package]
Vendor: H3C
Product: MSR36
Service name: feature1
Platform version: 7.1.070
Product version: Test 0001015
Supported board: MSR36-10
[Component]
Component: feature1
Description: feature1 package
# 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: MSR36
Service name: boot
Platform version: 7.1.070
Product version: Test 0001015
Supported board: MSR36-10
[Component]
Component: boot
Description: boot package
flash:/system.bin
[Package]
Vendor: H3C
Product: MSR36
Service name: system
Platform version: 7.1.070
Product version: Test 0001015
Supported board: MSR36-10
[Component]
Component: system
Description: system package
flash:/feature1.bin
[Package]
Vendor: H3C
Product: MSR36
Service name: feature1
Platform version: 7.1.070
Product version: Test 0001015
Supported board: MSR36-10
[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
display install inactive [ verbose ]
display install inactive [ slot slot-number ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies an IRF member device by its member ID. If you do not specify an IRF member device, this command displays information for all IRF member devices.
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.
<Sysname> display install inactive
Inactive packages on the device:
flash:/feature1.bin
# Display brief information about inactive software images.
<Sysname> display install inactive
Inactive packages on slot 1:
flash:/feature1.bin
# Display detailed information about inactive software images.
<Sysname> display install inactive verbose
Inactive packages on the device:
flash:/feature1.bin
[Package]
Vendor: H3C
Product: MSR36
Service name: feature1
Platform version: 7.1.070
Product version: Test 0001015
Supported board: MSR36-10
[Component]
Component: feature1
Description: feature1 package
# Display detailed information about inactive software images.
<Sysname> display install inactive verbose
Inactive packages on slot 1:
flash:/feature1.bin
[Package]
Vendor: H3C
Product: MSR36
Service name: feature1
Platform version: 7.1.070
Product version: Test 0001015
Supported board: MSR36-10
[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
# Display information about .ipe file flash:/test.ipe.
<Sysname> display install ipe-info flash:/test.ipe
Verifying the file flash:/test.ipe on the device................Done.
H3C MSR36-10 images in IPE:
boot.bin
system.bin
# 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 MSR36-10 images in IPE:
boot.bin
system.bin
Related commands
display install package
display install job
Use display install job to display ongoing activate and deactivate operations.
Syntax
display install job
Views
Any view
Predefined user roles
network-admin
network-operator
Examples
# Display ongoing activate and deactivate operations.
<Sysname> display install job
JobID:5
Action:install activate flash:/feature1.bin on the device
The output shows that the device is executing the install activate flash:/feature1.bin command.
# Display ongoing activate and deactivate 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 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 device's file systems.
all: Specifies all software image files in the root directories of the master'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: MSR36
Service name: system
Platform version: 7.1.070
Product version: Test 0001015
Supported board: MSR36-10
# Display detailed information about system.bin.
<Sysname> display install package flash:/system.bin verbose
flash:/system.bin
[Package]
Vendor: H3C
Product: MSR36
Service name: system
Platform version: 7.1.070
Product version: Test 0001015
Supported board: MSR36-10
[Component]
Component: system
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 }
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 an IRF member device by its member ID. If you do not specify a member device, this command displays information for all IRF members.
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: MSR36
Service name: system
Platform version: 7.1.070
Product version: Test 0001015
Supported board: MSR36-10
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. |
firmware update
Use firmware update to upgrade firmware.
Syntax
firmware update 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
slot slot-number: Specifies an IRF member device. The slot-number argument represents its IRF member ID.
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 that cannot be upgraded using the boot-loader command.
To complete the firmware upgrade, you must power cycle the card or subcard.
To power cycle a card or subcard, power cycle the device or remove and reinsert the card or subcard.
Examples
# 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 activate
Use install activate to activate software images.
Syntax
install activate { boot filename | system filename | feature filename&<1-30> } *
install activate patch filename
install activate { boot filename | system filename | feature filename&<1-30> } * slot slot-number
install activate patch filename { all | slot slot-number }
Views
User view
Predefined user roles
network-admin
Parameters
boot: Specifies a boot image file.
system: Specifies a system image file.
feature: Specifies 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 activate 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 member devices.
slot slot-number: Specifies an IRF member device by its member ID.
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.
Centralized devices:
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.
Centralized IRF devices:
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 member device to be upgraded, the command copies the images to the member device automatically.
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
# Activate the system image in system.bin and the feature images in feature1.bin.
<Sysname> install activate system flash:/system.bin feature flash:/feature1.bin
Verifying the file flash:/feature1.bin on the device.....Done.
Verifying the file flash:/system.bin on the device.....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
Upgrade Way: Service Upgrade
Upgrading software images to compatible versions. Continue? [Y/N]:y
This operation might take several minutes, please wait...Done.
# Activate the system image in system.bin and the feature images in feature1.bin on member device 2.
<Sysname> install activate system flash:/system.bin feature flash:/feature1.bin slot 2
Copying file flash:/system.bin to slot2#flash:/system.bin......Done.
Verifying the file flash:/system.bin on slot 2.....Done.
Copying file flash:/feature1.bin to slot2#flash:/feature1.bin......Done.
Verifying the file flash:/feature1.bin on slot 2.....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
2 Service Upgrade
Upgrading software images to compatible versions. Continue? [Y/N]:y
This operation might take several minutes, please wait...Done.
Table 4 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
install deactivate feature filename&<1-30>
install deactivate patch filename
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 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 member devices.
slot slot-number: Specifies an IRF member device by its member ID.
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.
To prevent deactivated images from running after a reboot, you must commit the software changes by using the install commit command.
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
# Deactivate the patch images in the route-patch.bin file.
<Sysname> install deactivate patch flash:/route-patch.bin
This operation might take several minutes, please wait...Done.
# 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
install remove { filename | inactive }
install remove [ slot slot-number ] { filename | inactive }
Views
User view
Predefined user roles
network-admin
Parameters
filename: Specifies a .bin file in the filesystemname/filename.bin format. The value string can have a maximum of 63 characters. The file must be stored in the root directory of a file system on the device. 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 an IRF member device by its member ID. If you do not specify a member device, this command deletes inactive software images from all IRF members.
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 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.
# 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.