- Table of Contents
-
- H3C S6116 Ultra-Low Latency Switch Series Command References-Release 671x-6W101
- 00-Preface
- 01-Interface forwarding commands
- 02-CLI commands
- 03-RBAC commands
- 04-Login management commands
- 05-FTP and TFTP commands
- 06-File system management commands
- 07-Configuration file management commands
- 08-Software upgrade commands
- 09-Device management commands
- 10-Tcl commands
- 11-Bulk interface commands
- 12-IP addressing commands
- 13-IPv6 basics commands
- 14-Static routing commands
- 15-IPv6 static routing commands
- 16-AAA commands
- 17-Public key management commands
- 18-SSH commands
- 19-System maintenance and debugging commands
- 20-NTP commands
- 21-SNMP commands
- 22-RMON commands
- 23-Event MIB commands
- 24-Information center commands
- 25-PTP commands
- 26-Network synchronization commands
- Related Documents
-
Title | Size | Download |
---|---|---|
08-Software upgrade commands | 120.23 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-16> ] { all | slot slot-number } { backup | main }
boot-loader file ipe-filename [ patch filename&<1-16> ] { 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 16 patch image files. You can specify only 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 slot number of the device, which is fixed at 1.
backup: Specifies the files as backup startup image files. Backup images are used only when main images are not available.
main: Specifies the files as main startup image files. The device always first attempts to start up with main startup files.
Usage guidelines
The boot-loader file command overwrites the entire startup image list. To add new startup feature images, specify all feature image files in the old startup image list, including feature image files. The new startup image list will contain only the feature image files that are specified in the command.
To load the specified startup software images, you must reboot the system.
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.
|
NOTE: The system will verify the digital signature of the specified images before it updates the startup image list with the specified images. If the digital signature verification fails, the system will not update the startup image list and you will receive a digital signature verification failure message. |
Examples
# Specify flash:/all.ipe as the main startup image file for slot 1.
<Sysname> boot-loader file flash:/all.ipe slot 1 main
Verifying the file flash:/all.ipe on slot 1..............Done.
H3C S6116-48X images in IPE:
boot.bin
system.bin
This command will set the main startup software images. Continue? [Y/N]:Y
Add images to slot 1.
File flash:/boot.bin already exists on slot 1.
File flash:/system.bin already exists on slot 1.
Overwrite the existing files? [Y/N]:Y
Decompressing file boot.bin to flash:/boot.bin........................Done.
Decompressing file system.bin to flash:/system.bin...............................Done.
Verifying the file flash:/boot.bin on slot 1...Done.
Verifying the file flash:/system.bin on slot 1.............Done.
The images that have passed all examinations will be used as the main startup software images at the next reboot on slot 1.
Related commands
display boot-loader
bootrom update
Use bootrom update to load the BootWare image from a file system to the Normal BootWare area.
Syntax
bootrom update file file slot slot-number-list
Views
User view
Predefined user roles
network-admin
Parameters
file file: Specifies the file that contains the BootWare image. The file argument represents the file name, a string of 1 to 63 characters.
slot slot-number-list: Specifies the slot number of the device, which is fixed at 1.
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 will verify the digital signature of 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 that 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
display boot-loader
Use display boot-loader to display current software images and startup software images.
Syntax
display boot-loader [ slot slot-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies the slot number of the device, which is fixed at 1.
Examples
# Display the current software images and startup software images.
<Sysname> display boot-loader
Software images on slot 1:
Current software images:
flash:/boot.bin
flash:/system.bin
Main startup software images:
flash:/boot.bin
flash:/system.bin
Backup startup software images:
flash:/boot.bin
flash:/system.bin
Table 1 Command output
Field |
Description |
Current software images |
Comware images that have been loaded. |
Main startup software images |
Primary Comware images for the next startup. |
Backup startup software images |
Backup Comware images for the next startup. |
Related commands
boot-loader file
display install active
Use display install active to display active software images.
Syntax
display install active [ slot slot-number ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies the slot number of the device, which is fixed at 1.
verbose: Displays detailed information. If you do not specify this keyword, the command displays only image names.
Examples
# Display brief information about active software images.
<Sysname> display install active
Active packages on slot 1:
flash:/boot.bin
flash:/system.bin
flash:/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: S6116-48X
Service name: boot
Platform version: 7.1.022
Product version: Test 2201
Supported board: mpu
[Component]
Component: boot
Description: boot package
flash:/system.bin
[Package]
Vendor: H3C
Product: S6116-48X
Service name: system
Platform version: 7.1.022
Product version: Test 2201
Supported board: mpu
[Component]
Component: system
Description: system package
flash:/feature.bin
[Package]
Vendor: H3C
Product: S6116-48X
Service name: test
Platform version: 7.1.022
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. · 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. The value is fixed at mpu, which indicates the device. |
[Component] |
Information about components included in the image file. |
Component |
Component name. |
Description |
Component description. |
Related commands
install active
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-t5101.bin
flash:/system-t5101.bin
flash:/feature.bin
# Display detailed information about main startup software images.
<Sysname> display install committed verbose
Committed packages on slot 1:
flash:/boot-t5101.bin
[Package]
Vendor: H3C
Product: S6116-48X
Service name: boot
Platform version: 7.1
Product version: Beta 1330
Supported board: mpu
[Component]
Component: boot
Description: boot package
flash:/system-t5101.bin
[Package]
Vendor: H3C
Product: S6116-48X
Service name: system
Platform version: 7.1
Product version: Beta 1330
Supported board: mpu
[Component]
Component: system
Description: system package
flash:/ssh-feature.bin
[Package]
Vendor: H3C
Product: S6116-48X
Service name: ssh
Platform version: 7.1
Product version: Beta 1330
Supported board: mpu
[Component]
Component: ssh
Description: ssh package
For information about the command output, see Table 2.
Related commands
boot-loader file
install commit
install activate
Use install activate to activate feature or patch 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. 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.
slot slot-number: Specifies the slot number of the device, which is fixed at 1.
all: Specifies the device itself.
Usage guidelines
This command activates images and adds the images to the current image list. 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.
Examples
# Activate system-patch.bin on the device.
<Sysname> install activate system-patch.bin slot 1
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 activated image files to the startup 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.
To add inactive images as main or backup startup images, 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.
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.
slot slot-number: Specifies the slot number of the device, which is fixed at 1.
all: Specifies the device itself.
Usage guidelines
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 route-patch.bin on the device.
<Sysname> install deactivate patch flash:/route-patch.bin slot 1
Related commands
display install active