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-GIR commands
- 09-Target configuration management commands
- 10-Device management commands
- 11-Tcl commands
- 12-Python commands
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 07-Software upgrade commands | 145.83 KB |
Software upgrade commands
As a best practice, store the startup images in a fixed storage medium. If you store the startup images in a hot swappable storage medium, do not remove the hot swappable storage medium during the startup process.
boot-loader file
Use boot-loader file to specify startup image files.
Syntax
boot-loader file boot filename system filename [ feature filename&<1-30> ] [ patch filename&<1-30> ] { all | slot slot-number } { backup | main }
boot-loader file ipe-filename [ patch filename&<1-30> ] { all | slot slot-number } { backup | main }
Views
User view
Predefined user roles
network-admin
Parameters
boot: Specifies a boot image file.
system: Specifies a system image file.
feature: Specifies a space-separated list of up to 30 feature image files.
patch: Specifies a space-separated list of up to 30 incremental patch image files or 16 non-incremental patch image files. Because the boot, system, and feature images each can have one non-incremental patch image file, you can specify a maximum of 16 non-incremental patch image files.
filename: Specifies a .bin file in the filesystemname/filename.bin format. The file must be stored in the root directory of a file system on the device. Excluding the file system location section (if any), the value string can have a maximum of 63 characters. For more information about specifying a file, see Fundamentals Configuration Guide.
ipe-filename: Specifies an .ipe image package file in the filesystemname/filename.ipe format. The file must be stored in the root directory of a file system on the device. Excluding the file system location section (if any), the value string can have a maximum of 63 characters. For more information about specifying a file, see Fundamentals Configuration Guide.
all: Upgrades the entire system.
slot slot-number: Specifies the slot number of an MPU.
backup: Specifies the files as backup startup image files. Backup images are used only when main images are not available.
main: Specifies the files as main startup image files. The device always first attempts to start up with main startup files.
Usage guidelines
The boot-loader file command overwrites the entire startup image list. To add new startup feature images, specify all feature image files in the old startup image list, including feature image files. The new startup image list will contain only the feature image files that are specified in the command.
To load the specified startup software images, you must reboot the system.
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.
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.
XX images in IPE:
boot.bin
system.bin
feature.bin
This command will set the main startup software images. Continue? [Y/N]:Y
Add images to slot 1.
File flash:/boot.bin already exists on slot 1.
File flash:/system.bin already exists on slot 1.
File flash:/feature.bin already exists on slot 1.
Overwrite the existing files? [Y/N]:Y
Decompressing file boot.bin to flash:/boot.bin........................Done.
Decompressing file system.bin to flash:/system.bin...............................Done.
Decompressing file feature.bin to flash:/feature.bin..................Done.
Verifying the file flash:/boot.bin on slot 1...Done.
Verifying the file flash:/system.bin on slot 1.............Done.
Verifying the file flash:/feature.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.
<Sysname> boot-loader file flash:/all.ipe all main
Verifying the file flash:/all.ipe on slot 1..............Done.
XX Switch images in IPE:
boot.bin
system.bin
feature.bin
This command will set the main startup software images. Continue? [Y/N]:y
Add images to slot 1.
File flash:/boot.bin already exists on slot 1.
File flash:/system.bin already exists on slot 1.
File flash:/feature.bin already exists on slot 1.
Overwrite the existing files? [Y/N]:y
Decompressing file boot.bin to flash:/Boot.bin........................Done.
Decompressing file system.bin to flash:/System.bin...............................Done.
Decompressing file feature.bin to flash:/feature.bin..................Done.
Verifying the file flash:/boot.bin on slot 1...Done.
Verifying the file flash:/system.bin on slot 1.............Done.
Verifying the file flash:/feature.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.
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
boot-loader blade file
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 active MPU to the standby MPU.
slot slot-number: Specifies the slot number of the standby MPU.
Usage guidelines
You can use this command to synchronize startup images after adding new MPUs.
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 started up with the main startup images.
· The backup image list is used if the active MPU 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 a patch has been installed on the active MPU, use the install commit command to update the main startup images on the active MPU before software synchronization. This command ensures startup image consistency between the active MPU and the standby MPU.
Startup image synchronization fails if any software image being synchronized is not available or is corrupted.
Examples
# Synchronize startup images to a slot.
<Sysname> boot-loader update slot 0
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 0. Please wait...
Done.
Setting copied images as main startup software images for slot 0...
The images that have passed all examinations will be used as the main startup software images at the next reboot on slot 0.
Done.
Successfully updated the startup software images of slot 0.
Related commands
display boot-loader
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 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.
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 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 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.
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 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.
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
# Use the file a.bin in the root directory of the flash memory to upgrade the BootWare image.
<Sysname> bootrom update file flash:/a.bin slot 1
This command will update the Boot ROM file on the specified board(s), Continue? [Y/N]:y
Now updating the Boot ROM, please wait................Done.
Related commands
boot-loader file
bootrom-update security-check enable
Use bootrom-update security-check enable to enable BootWare image validity check.
Use undo bootrom-update security-check enable to disable BootWare image validity check.
Syntax
bootrom-update security-check enable
undo bootrom-update security-check enable
Default
BootWare image validity check is enabled.
Views
System view
Predefined user roles
network-admin
Usage guidelines
Before a BootWare image upgrade starts, this feature examines the upgrade BootWare image for file validity and incompatibility with hardware. If the BootWare image passes the check, the upgrade process starts. If the check fails, the system does not perform the upgrade.
Examples
# Enable BootWare image validity check.
<Sysname> system-view
[Sysname] bootrom-update security-check enable
display boot-loader
Use display boot-loader to display current software images and startup software images.
Syntax
display boot-loader [ slot slot-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies the slot number of an MPU. If you do not specify an MPU, this command displays the software images on each MPU.
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
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.
display install active [ slot slot-number ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays information for all cards.
verbose: Displays detailed information. If you do not specify this keyword, the command displays only image names.
Examples
# Display active software images.
<Sysname> display install active
Active packages on slot 1:
flash:/boot.bin
flash:/system.bin
flash:/feature.bin
# Display detailed information about active software images.
<Sysname> display install active verbose
Active packages on slot 1:
flash:/boot.bin
[Package]
Vendor: H3C
Product: xxxx
Service name: boot
Platform version: 7.1.075
Product version: Test 2201
Supported board: mpu
[Component]
Component: boot
Description: boot package
flash:/system.bin
[Package]
Vendor: H3C
Product: xxxx
Service name: system
Platform version: 7.1.075
Product version: Test 2201
Supported board: mpu
[Component]
Component: system
Description: system package
flash:/feature.bin
[Package]
Vendor: H3C
Product: xxxx
Service name: test
Platform version: 7.1.075
Product version: Test 2201
Supported board: mpu
[Component]
Component: test
Description: test package
|
Field |
Description |
|
[Package] |
Detailed information about the software image. |
|
Service name |
Image type: · boot—Boot image. · system—System image. · boot patch—Patch image for the boot image. · system patch—Patch image for the system image. · Any other value indicates a feature image. |
|
Supported board |
Hardware types supported by the software image: · mpu—MPU. · lpu—Service card. · sfc—Switching fabric module. |
|
[Component] |
Information about components included in the image file. |
Related commands
install activate
display install backup
Use display install backup to display backup startup software images.
Syntax
display install backup [ slot slot-number ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays information for all cards.
verbose: Displays detailed information. If you do not specify this keyword, the command displays only image names.
Usage guidelines
Backup startup images are used only when the main boot or system image is missing or corrupt. For more information, see Fundamentals Configuration Guide.
To modify the backup startup image list, use the boot-loader file command.
Examples
# Display the backup startup software images.
<Sysname> display install backup
Backup startup software images on slot 1:
flash:/boot.bin
flash:/system.bin
# Display detailed information about backup startup software images.
<Sysname> display install backup verbose
Backup startup software images on slot 1:
flash:/boot.bin
[Package]
Vendor: H3C
Product: xxxx
Service name: boot
Platform version: 7.1
Product version: Beta 1330
Supported board: mpu
[Component]
Component: boot
Description: boot package
flash:/system.bin
[Package]
Vendor: H3C
Product:xxxx
Service name: system
Platform version: 7.1
Product version: Beta 1330
Supported board: mr, lc, sfc
[Component]
Component: system
Description: system package
For information about the command output, see Table 2.
Related commands
boot-loader file
display install committed
display install committed
Use display install committed to display main startup software images.
Syntax
display install committed [ slot slot-number ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays information for all cards.
verbose: Displays detailed information. If you do not specify this keyword, the command displays only image names.
Usage guidelines
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 the main startup software images.
<Sysname> display install committed
Committed packages on slot 1:
flash:/boot.bin
flash:/system.bin
flash:/feature.bin
# Display detailed information about main startup software images.
<Sysname> display install committed verbose
Committed packages on slot 1:
flash:/boot.bin
[Package]
Vendor: H3C
Product: xxxx
Service name: boot
Platform version: 7.1
Product version: Beta 1330
Supported board: mr, lc, sfc
[Component]
Component: boot
Description: boot package
flash:/system.bin
[Package]
Vendor: H3C
Product:xxxx
Service name: system
Platform version: 7.1
Product version: Beta 1330
Supported board: mr, lc, sfc
[Component]
Component: system
Description: system package
flash:/ssh-feature.bin
[Package]
Vendor: H3C
Product: xxxx
Service name: ssh
Platform version: 7.1
Product version: Beta 1330
Supported board: mr, lc, sfc
[Component]
Component: ssh
Description: ssh package
For information about the command output, see Table 2.
Related commands
boot-loader file
display install backup
install commit
install activate
Use install activate to activate software images.
Syntax
install activate feature filename&<1-30> slot slot-number
install activate patch filename { all | slot slot-number }
Views
User view
Predefined user roles
network-admin
Parameters
feature: Specifies a space-separated list of up to 30 feature image files
patch: Specifies a patch image file. You can specify only one patch image file for the command at a time. However, you can execute the command multiple times to activate multiple patch image files.
filename: Specifies a .bin file in the filesystemname/filename.bin format. The file must be stored in the root directory of a file system on the device. The value string excluding the file system location section (if any) can have a maximum of 63 characters. For more information about specifying a file, see file system management in Fundamentals Configuration Guide.
all: Specifies all cards.
slot slot-number: Specifies a card by its slot number.
Images run in memory immediately after they are activated. However, only patch 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 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.
You can install a maximum of 32 image files on the device: one system image file, one boot image file, and a maximum of 30 feature image files and patch image files.
Examples
# Activate the feature image in feature1.bin on the standby MPU in slot 1.
<Sysname> install activate feature flash:/feature1.bin slot 1
Copying file flash:/feature1.bin to slot1#flash:/feature1.bin......Done.
Verifying the file flash:/feature1.bin on slot 1.....Done.
Upgrade summary according to following table:
flash:/feature1.bin
Running Version New Version
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 3 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 |
This field is not supported in the current software version. ISSU methods: · Service Upgrade. · File Upgrade. · Reboot. This field is displayed only for an upgrade to a compatible version. |
|
Influenced service according to following table |
Services influenced by the upgrade. |
|
Install command does not support incompatible upgrade. |
The install command set does not support incompatible upgrade. |
|
Please use install sequence reboot command to reboot and upgrade the sequence reboot slot. |
The system prompts you to use the install sequence reboot command to manually reboot the switching fabric modules and LPUs for a reboot upgrade. |
Related commands
display install active
install commit
install deactivate
install commit
Use install commit to commit software changes.
Syntax
install commit
Views
User view
Predefined user roles
network-admin
Usage guidelines
This command adds the patch image file to the startup software image list that the device used at startup.
· If the device used the main startup software image list at startup, this command adds the patch image file to the main startup software image list.
· If the device used the backup startup software image list at startup, this command adds the patch image file to the backup startup software image list.
Both the install commit and boot-loader file commands modify the main startup software image list. However, the boot-loader file command can also modify the backup startup image list and add inactive images as main startup images.
Examples
# Commit software changes.
<Sysname> install commit
This operation will take several minutes, please wait...........................Done.
The current software images have been saved as the startup software images.
Current software images on slot 1:
flash:/boot.bin
flash:/system.bin
Current software images on slot 2:
flash:/boot.bin
flash:/system.bin
Related commands
install activate
install deactivate
install deactivate
Use install deactivate to deactivate feature images and patch images.
Syntax
install deactivate feature filename&<1-30> slot slot-number
install deactivate patch filename { all | slot slot-number }
Views
User view
Predefined user roles
network-admin
Parameters
feature: Specifies a space-separated list of up to 30 feature image files.
patch: Specifies a patch image file. You can specify only one patch image file for the command at a time. However, you can execute the command multiple times to deactivate multiple patch image files.
filename: Specifies a .bin file in the filesystemname/filename.bin format. The value string can have a maximum of 63 characters. 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.
all: Specifies all cards on which the specified patch image file has been activated.
slot slot-number: Specifies a card by its slot number.
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 stop running in memory immediately after they are deactivated. However, only patch 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 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
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
|
|
CAUTION: Use the undo version auto-update enable and version check ignore commands with caution. Configured with these two commands, the system will not 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. This might cause the device to malfunction. |
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
|
|
CAUTION: To avoid anomalies, do not disable startup software version check for the standby MPU unless for software upgrade. The device might malfunction if the standby MPU starts up with a different software version than the active MPU. |
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.
If you enable startup software version check for the standby MPU, the system will prevent the standby MPU from starting up with a different software version than the active MPU.
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
