Login
- Table of Contents
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 07-Software upgrade commands | 158.19 KB |
Contents
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 [ undecompressed ] }
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: 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.
undecompressed: Specifies the IPE file as the main startup image file without decompressing it. If you do not specify this keyword, the device decompresses the IPE file and then sets the decompressed .bin files as the main startup image files. As a best practice, do not specify this keyword if the device has sufficient storage space.
Usage guidelines
Application scenarios
When the current software cannot meet the requirements of network operation or user services, you can use this command to upgrade the software to optimize device performance to meet the requirements.
Operating mechanism
The boot-loader file command overwrites the entire startup image list. To add new startup feature images, specify all feature image files in the old startup image list, including feature image files. The new startup image list will contain only the feature image files that are specified in the command.
Restrictions and guidelines
The system will verify the digital signature of the specified images before it updates the startup image list with the specified images. If the digital signature verification fails, the system will not update the startup image list and you will receive a digital signature verification failure message.
To load the specified startup software images, you must reboot the system.
Examples
# Specify flash:/all.ipe as the main startup image file for slot 1.
<Sysname> boot-loader file flash:/all.ipe slot 1 main
Verifying the file flash:/all.ipe on slot 1..............Done.
H3C S6880-48Y8C images in IPE:
boot.bin
system.bin
This command will set the main startup software images. Continue? [Y/N]:Y
Add images to slot 1.
File flash:/boot.bin already exists on slot 1.
File flash:/system.bin already exists on slot 1.
Overwrite the existing files? [Y/N]:Y
Decompressing file boot.bin to flash:/boot.bin........................Done.
Decompressing file system.bin to flash:/system.bin...............................Done.
Verifying the file flash:/boot.bin on slot 1...Done.
Verifying the file flash:/system.bin on slot 1.............Done.
The images that have passed all examinations will be used as the main startup software images at the next reboot on slot 1.
# Specify flash:/all.ipe as the main startup image file for slot 1, without immediately decompressing the IPE file.
<Sysname> boot-loader file flash:/all.ipe slot 1 main undecompressed
Verifying the file flash:/all.ipe on slot 1..............Done.
XX images in IPE:
boot.bin
system.bin
This command will set the main startup software image. Continue? [Y/N]:Y
File flash:/all.ipe already exists on slot 1.
Overwrite the existing files? [Y/N]:Y
Copying file flash:/all.ipe to slot1#flash:/all.ipe...Done.
The image that have passed all examinations will be used as the main startup software image at the next reboot on slot 1.
# Specify flash:/all.ipe as the main startup image file for all IRF member devices, without immediately decompressing the IPE file.
<Sysname> boot-loader file slot1#flash:/all.ipe all main undecompressed
Verifying the file flash:/all.ipe on slot 1......................................Done.
XX images in IPE:
Boot.bin
System.bin
This command will set the main startup software images. Continue? [Y/N]:Y
The image that have passed all examinations will be used as the main startup software image at the next reboot on slot 1.
File flash:/all.ipe 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.
The image that have passed all examinations will be used as the main startup software image at the next reboot on slot 2.
The image that have passed all examinations will be used as the main startup software image at the next reboot on slot 3.
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
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.
Examples
# Synchronize startup images to a slot.
<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.
Related commands
display boot-loader
display boot-loader
Use display boot-loader to display current software images and startup software images.
Syntax
display boot-loader [ 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:/b-boot.bin --
flash:/b-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. |
|
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. |
Related commands
boot-loader file
display install active
Use display install active to display active software images.
Syntax
display install active [ slot slot-number ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies the slot number of the device, which is fixed at 1.
verbose: Displays detailed information. If you do not specify this keyword, the command displays only image names.
Examples
# Display brief information about active software images.
<Sysname> display install active
Active packages on slot 1:
flash:/boot.bin
flash:/system.bin
flash:/feature1.bin
# Display detailed information about active software images.
<Sysname> display install active verbose
Active packages on slot 1:
flash:/boot.bin
[Package]
Vendor: H3C
Product: S6880
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: S6880
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: S6880
Service name: test
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu
[Component]
Component: test
Description: test package
|
Field |
Description |
|
[Package] |
Detailed information about the software image. |
|
Service name |
Image type: · boot—Boot image. · boot-patch—Boot image patch. · system—System image. · system-patch—System image patch. · Any other value indicates a feature image. |
|
Platform version |
Platform software version. |
|
Product version |
Product software version. |
|
Supported board |
Device type supported by the software image: mpu—Centralized device. |
|
[Component] |
Information about components included in the image file. |
|
Component |
Component name. |
|
Description |
Component description. |
Related commands
install activate
display install committed
Use display install committed to display main startup software images.
Syntax
display install committed [ slot slot-number ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies the slot number of the device, which is fixed at 1.
verbose: Displays detailed information. If you do not specify this keyword, the command displays only image names.
Usage guidelines
Some install commands modify the current software image list but do not modify the main startup image list. For the software image changes to take effect after a reboot, you must execute the install commit command to update the main startup image list with the image changes. You can use the display install committed command to verify the operation results.
Both the install commit and boot-loader file commands modify the main startup software image list.
Examples
# Display brief information about main startup software images.
<Sysname> display install committed
Committed packages on slot 1:
flash:/boot.bin
flash:/system.bin
flash:/feature1.bin
# Display detailed information about main startup software images.
<Sysname> display install committed verbose
Committed packages on slot 1:
flash:/boot.bin
[Package]
Vendor: H3C
Product: S6880
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: S6880
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: S6880
Service name: feature1
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu
[Component]
Component: feature1
Description: feature1 package
For information about the command output, see Table 2.
Related commands
boot-loader file
install commit
display install inactive
Use display install active to display inactive software images in the root directories of file systems.
Syntax
display install inactive [ slot slot-number ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies the slot number of the device, which is fixed at 1.
verbose: Displays detailed information. If you do not specify this keyword, the command displays only image names.
Examples
# Display brief information about inactive software images in the root directories of the file systems.
<Sysname> display install inactive
Inactive packages on slot 1:
flash:/feature1.bin
# Display detailed information about inactive software images in the root directories of the file systems.
<Sysname> display install inactive verbose
Inactive packages on slot 1:
flash:/feature1.bin
[Package]
Vendor: H3C
Product: S6880
Service name: feature1
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu
[Component]
Component: feature1
Description: feature1 package
For information about the command output, see Table 2.
Related commands
install deactivate
display version
Use display version to display system version information.
Syntax
display version
Views
Any view
Predefined user roles
network-admin
network-operator
Examples
# Display system version information.
<Sysname> display version
H3C Comware Software, Version 9.1.043, ESS 1111
Copyright (c) 2004-2022 New H3C Technologies Co., Ltd. All rights reserved.
H3C S6880-48Y8C uptime is 0 weeks, 0 days, 0 hours, 5 minutes
Last reboot reason : User reboot
Boot image: flash:/s6880-cmw910-boot-e1111.bin
Boot image version: 9.1.043, ESS 1111
Compiled May 18 2022 14:00:00
System image: flash:/s6880-cmw910-system-e1111.bin
System image version: 9.1.043, ESS 1111
Compiled May 18 2022 14:00:00
...
Table 3 Command output
|
Field |
Description |
|
Last reboot reason |
Reason for the last reboot: · User reboot—The reboot was manually initiated from a user interface, such as the CLI or SNMP. · Cold reboot—The reboot was caused by a power cycle. · Kernel abnormality reboot—The reboot was caused by kernel exceptions. · DeadLoop reboot—The reboot was caused by a kernel thread dead loop. · DEV HandShake reboot—The reboot was caused by a device management handshake failure. · Auto Update reboot—The reboot was caused by an automatic software upgrade. · Memory exhaust reboot—The reboot was caused by a memory-exhausted event. · Recover GOLD-detected error—The reboot was caused by a failed GOLD test. · Critical process abnormality reboot—The reboot was caused by core process abnormality. |
display version-update-record
Use display version-update-record to display startup software image upgrade records.
Syntax
display version-update-record
Views
Any view
Predefined user roles
network-admin
network-operator
Usage guidelines
The device records its current startup software version information whenever it starts up, and records all software version update information. Such information can survive reboots.
Examples
# Display the startup software image upgrade records.
Record 1 (updated on Jan 18 2020 at 06:23:54):
*Name : comware-cmw710-boot.bin
Version : 7.1.070 Test 0001
Compile time: Jan 25 2020 15:52:43
*Name : comware-cmw710-system.bin
Version : 7.1.070 Test 0001
Compile time: Jan 25 2020 15:52:43
|
Field |
Description |
|
Record n (updated on Jan 18 2020 at 06:23:54) |
Number of the startup software image upgrade record. Record 1 is the most recent record. The time in parentheses is UTC time. |
|
Name |
Software image file name. |
|
* |
The software image version changed during the upgrade. |
Related commands
reset version-update-record
install activate
Use install activate to activate feature or patch images.
Syntax
install activate feature filename&<1-30> slot slot-number [ test ]
install activate patch filename { all | slot slot-number }
Views
User view
Predefined user roles
network-admin
Parameters
feature: Specifies a space-separated list of up to 30 feature image files.
patch: Specifies a patch image file. You can specify only one patch image file for the command at a time. However, you can execute the command multiple times to activate multiple patch image files.
filename: Specifies a .bin file in the filesystemname/filename.bin format. The file must be stored in the root directory of a file system on the device. Excluding the file system location section (if any), the value string can have a maximum of 63 characters. For more information about specifying a file, see file system management in Fundamentals Configuration Guide.
all: This keyword represents the device. It is identical to slot 1.
slot slot-number: Specifies the slot number of the device, which is fixed at 1.
test: Only identifies the ISSU method to be used for the upgrade. If you do not specify this keyword, the command activates the specified software images.
Usage guidelines
This command requires that all image files on the startup software image list be the same version after the upgrade is finished. It can be executed successfully only if the boot, system, and feature image files on the list are the same version after the upgrade. Before being executed successfully, this command uninstalls all existing patch image files on the list automatically.
If this command fails, perform the following tasks:
1. If some features are not needed anymore, disable the features and use the install deactivate command to uninstall the feature images.
2. Obtain the image files that are required to make sure all image files on the startup software image list are the same version after the upgrade.
3. Specify the image files for this command to activate the images.
An image runs in memory immediately after it is activated. For an activated image to run after a reboot, you must commit the software change by using the install commit command.
Examples
# Identify the ISSU method for feature upgrade with feature1.bin on the device and the upgrade impact.
<Sysname> install activate feature flash:/feature1.bin slot 1 test
Copying file flash:/feature1.bin to slot1#flash:/feature1.bin......Done.
Verifying the file flash:/feature1.bin on slot 1.....Done.
Upgrade summary according to following table:
flash:/feature1.bin
Running Version New Version
Test 0001015 Test 0001016
Slot Upgrade Way
1 Service Upgrade
Influenced service according to following table:
flash:/feature1.bin
Feature1
The output shows that a service upgrade is recommended. The Feature1 module will be rebooted during the upgrade.
# Activate the patch image in patch1.bin on the device.
<Sysname> install activate patch flash:/patch1.bin slot 1
Copying file flash:/patch1.bin to slot1#flash:/patch1.bin......Done.
Verifying the file flash:/patch1.bin on slot 1.....Done.
This operation might take several minutes, please wait...Done.
Table 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 |
ISSU methods: · Service Upgrade. · File Upgrade. · Reboot. This field is displayed only for an upgrade to a compatible version. For more information about ISSU methods, see Fundamentals Configuration Guide. |
|
Influenced service according to following table |
Services influenced by the upgrade. |
Related commands
display install active
install commit
install deactivate
install commit
Use install commit to commit software changes.
Syntax
install commit
Views
User view
Predefined user roles
network-admin
Usage guidelines
This command adds the patch image file to the startup software image list that the device used at startup.
· If the device used the main startup software image list at startup, this command adds the patch image file to the main startup software image list.
· If the device used the backup startup software image list at startup, this command adds the patch image file to the backup startup software image list.
You must execute this command after using the following commands:
· The install activate command in an incremental upgrade.
· The install deactivate command.
In a reboot upgrade, the install activate command modifies both the current and startup software image lists. You do not need to commit software changes.
Both the install commit and boot-loader file commands modify the main startup software image list. To modify the backup startup image list or add inactive images as main startup images, however, you must use the boot-loader file command.
For more information about main and backup startup software images, see Fundamentals Configuration Guide.
Examples
# Commit software changes.
<Sysname> install commit
This operation will take several minutes, please wait...........................Done.
The current software images have been saved as the startup software images.
Current software images on slot 1:
flash:/boot.bin
flash:/system.bin
Related commands
install activate
install deactivate
install deactivate
Use install deactivate to deactivate feature or patch images.
Syntax
install deactivate feature filename&<1-30> slot slot-number
install deactivate patch filename { all | slot slot-number }
Views
User view
Predefined user roles
network-admin
Parameters
feature: Specifies a space-separated list of up to 30 feature image files.
patch: Specifies a patch image file. You can specify only one patch image file for the command at a time. However, you can execute the command multiple times to deactivate multiple patch image files.
filename: Specifies a .bin file in the filesystemname/filename.bin format. The file must be stored in the root directory of a file system on the device. Excluding the file system location section (if any), the value string can have a maximum of 63 characters. For more information about specifying a file, see file system management in Fundamentals Configuration Guide.
all: This keyword represents the device. It is identical to slot 1.
slot slot-number: Specifies the slot number of the device, which is fixed at 1.
Usage guidelines
You can deactivate only active feature and patch images. To prevent deactivated images from running after a reboot, you must commit the software changes by using the install commit command.
Examples
# Deactivate route-patch.bin on the device.
<Sysname> install deactivate patch flash:/route-patch.bin slot 1
This operation might take several minutes, please wait...Done.
Related commands
display install active
display install inactive
