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-ISSU commands
- 09-Emergency shell commands
- 10-Device management commands
- 11-Tcl commands
- 12-Python commands
- 13-License management commands
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 07-Software upgrade commands | 63.17 KB |
Software upgrade commands
The device can start up from the built-in flash memory or the USB disk. As a best practice, store the startup images in the built-in flash memory. If you store the startup images on the USB disk, do not remove the USB disk during the startup process.
boot-loader file
Use boot-loader file to specify startup image files.
Syntax
In standalone mode:
boot-loader file boot filename system filename [ feature filename&<1-30> ] { all | slot slot-number } { backup | main }
boot-loader file ipe-filename { all | slot slot-number } { backup | main }
In IRF mode:
boot-loader file boot filename system filename [ feature filename&<1-30> ] { all | chassis chassis-number slot slot-number } { backup | main }
boot-loader file ipe-filename { all | chassis chassis-number slot slot-number } { backup | main }
Views
User view
Predefined user roles
network-admin
Parameters
boot: Specifies a boot image file.
system: Specifies a system image file.
feature: Specifies a space-separated list of up to 30 feature image files.
filename: Specifies a .bin file in the filesystemname/filename.bin format. The file must be stored in the root directory of a file system on the device. Excluding the file system location section (if any), the value string can have a maximum of 63 characters. For more information about specifying a file, see 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 an MPU or firewall card. (In standalone mode.)
chassis chassis-number slot slot-number: Specifies an MPU or PEX. The chassis-number argument represents the IRF member ID of the device that holds the MPU or PEX. The slot-number argument represents the slot number of the MPU or PEX. When you specify a PEX, make sure the PEX has a file system. (In IRF mode.)
backup: Specifies the files as backup startup image files. Backup images are used only when main images are not available.
main: Specifies the files as main startup image files. The device always first attempts to start up with main startup files.
Usage guidelines
Before you specify startup image files, register and activate a license for each upgrade image that requires a license. If a license-based software image lacks a license, the command execution result is as follows:
· If .bin files are specified, the command cannot be executed.
· If an .ipe file is specified, the command sets all images as startup images except for the image that does not have a license.
For more information about licensing, see Fundamentals Configuration Guide.
To load the specified startup software images, you must reboot the system.
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.
Examples
# (In standalone mode.) Specify flash:/all.ipe as the main startup image file for slot 1.
<Sysname> boot-loader file flash:/all.ipe slot 1 main
Verifying the file flash:/all.ipe on slot 1........................
................................................................................
.........................Done.
H3C S10510 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.
# (In standalone mode.) Specify flash:/all.ipe as the main startup image file.
<Sysname> boot-loader file flash:/all.ipe all main
Verifying the file flash:/all.ipe on slot 1........................
...................................................................
.........................Done.
H3C S10510 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.
File flash:/boot.bin already exists on slot 0.
Do you want to overwrite the file?
Y: Overwrite the file.
N: Not overwrite the file.
A: From now on, overwrite or not overwrite without prompt.
Please make a choice. [Y/N/A]:a
What type of overwrite operation do you want to perform?
Y: Overwrite without prompt.
N: Not overwrite or display prompt.
Q: Return to the previous step.
Please make a choice. [Y/N/Q]:y
An existing file will be overwritten without prompt if it has the same name as any upgrade file.
Loading......................Done.
Loading......................Done.
The images that have passed all examinations will be used as the main startup software images at the next reboot on slot 0.
Decompression completed.
Do you want to delete flash:/all.ipe now? [Y/N]:n
Related commands
boot-loader pex file
display boot-loader
boot-loader pex file
Use boot-loader pex file to specify startup image files stored on the parent fabric for PEXs.
Syntax
boot-loader pex pex-model file boot filename system filename [ feature filename&<1-30> ]
boot-loader pex pex-model file ipe ipe-filename
Views
User view
Predefined user roles
network-admin
Parameters
pex pex-model: Specifies the PEX model, a case-insensitive string. You must enter the complete PEX model name for the device to identify the PEX correctly. For available PEX models, enter the boot-loader pex ? command.
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&<1-30>: 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 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.
Usage guidelines
The PEX startup images on the parent devices are called remote startup images. The PEX startup images on the PEX's local file system are called local startup images.
PEXs must load startup software images from the parent fabric when they join the IRF 3 system for the first time. For new PEXs to be added, you must configure this command on the parent fabric.
For PEXs already in the IRF 3 system, you can use this command or the boot-loader file command to upgrade PEX software. The PEXs will always attempt to start up with the local images before they use the remote images.
This command copies the PEX startup images to all MPUs on the parent devices. However, PEXs always start up with the software images on the global active MPU. To prevent a PEX startup failure after an active/standby switchover, execute this command each time you add a new MPU to a parent device.
The boot-loader pex file command overwrites the entire PEX 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 verify the PEX startup software images on the member devices, use the display boot-loader pex command.
Examples
# (In IRF mode.) Specify flash:/all.ipe as the remote startup image file for the S6300 PEXs.
<Sysname> boot-loader pex PEX-S6300 file ipe flash:/all.ipe
Verifying the file flash:/all.ipe on chassis 1 slot 1............Done.
File flash:/rpu-S6300-boot.bin already exists on chassis 1 slot 1.
File flash:/rpu-S6300-system.bin already exists on chassis 1 slot 1.
Overwrite the existing files? [Y/N]:Y
Decompressing file rpu-S6300-boot.bin to flash:/rpu-S6300-boot.bin.....................Done.
Decompressing file rpu-S6300-system.bin to flash:/rpu-S6300-system.bin............................................ Done.
File flash:/rpu-S6300-boot.bin already exists on chassis 1 slot 2.
File flash:/rpu-S6300-system.bin already exists on chassis 1 slot 2.
Overwrite the existing files? [Y/N]:Y
Copying file flash:/rpu-S6300-boot.bin to chassis1#slot2#flash:/rpu-S6300-boot.bin.........................Done.
Copying file flash:/rpu-S6300-system.bin to chassis1#slot2#flash:/rpu-S6300-system.bin.......................................Done.
File flash:/rpu-S6300-boot.bin already exists on chassis 2 slot 2.
File flash:/rpu-S6300-system.bin already exists on chassis 2 slot 2.
Overwrite the existing files? [Y/N]:Y
Copying file flash:/rpu-S6300-boot.bin to chassis2#slot2#flash:/rpu-S6300-boot.bin.........................Done.
Copying file flash:/rpu-S6300-system.bin to chassis2#slot2#flash:/rpu-S6300-system.bin....................................Done.
# (In IRF mode.) Specify flash:/boot.bin and flash:/system.bin as the remote startup boot and system image files for the S6300 PEXs.
<Sysname> boot-loader pex PEX-S6300 file boot flash:/boot.bin system flash:/system.bin
File flash:/boot.bin already exists on chassis 1 slot 2.
File flash:/system.bin already exists on chassis 1 slot 2.
Overwrite the existing files? [Y/N]:Y
Copying file flash:/boot.bin to chassis1#slot2#flash:/boot.bin.........................Done.
Copying file flash:/system.bin to chassis1#slot2#flash:/system.bin...................................................Done.
File flash:/boot.bin already exists chassis 2 slot 2.
File flash:/system.bin already exists chassis 2 slot 2.
Overwrite the existing files? [Y/N]:Y
Copying file flash:/boot.bin to chassis2#slot2#flash:/boot.bin.........................Done.
Copying file flash:/system.bin to chassis2#slot2#flash:/system.bin................................................Done.
Related commands
boot-loader file
display boot-loader pex
boot-loader update
Use boot-loader update to synchronize startup images.
Syntax
In standalone mode:
boot-loader update { all | slot slot-number }
In IRF mode:
boot-loader update { all | chassis chassis-number slot slot-number }
Views
User view
Predefined user roles
network-admin
Parameters
all: Synchronizes startup images from the active MPU to the standby MPU. (In standalone mode.)
all: Synchronizes startup images from the global active MPU to all standby MPUs. (In IRF mode.)
slot slot-number: Specifies the slot number of the standby MPU. (In standalone mode.)
chassis chassis-number slot slot-number: Specifies a standby MPU. The chassis-number argument represents the IRF member ID of the device that holds the MPU. The slot-number argument represents the slot number of the MPU. (In IRF mode.)
Usage guidelines
You can use this command to synchronize startup images after adding new MPUs.
If any of the startup software images require a license, register and activate a license for the image on the new MPU before executing this command. Use the display license feature command to verify the licensing state of software images.
The images used for synchronization are in the main or backup startup software images list instead of the current software images list (see the display boot-loader command).
· The main images list is used if the active MPU (in standalone mode) or global active MPU (in IRF mode) started up with the main startup images.
· The backup image list is used if the active MPU (in standalone mode) or global active MPU (in IRF mode) started up with the backup startup images.
The startup images synchronized to a standby MPU are set as main startup images, regardless of whether the source startup images are main or backup.
If an ISSU patch installation or software upgrade has been performed, use the install commit command to update the main startup images on the active MPU (in standalone mode) or global active MPU (in IRF mode) before software synchronization. This command ensures startup image consistency between the active MPU or (in standalone mode) or global active MPU (in IRF mode) and standby MPUs.
Startup image synchronization fails if any software image being synchronized is not available or is corrupted.
Examples
# Synchronize startup images from the active MPU to the standby MPU in slot 1.
<Sysname> boot-loader update slot 1
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 1. Please wait...
Done.
Setting copied images as main startup software images for slot 1...
Done.
The images that have passed all examinations will be used as the main startup so
ftware images at the next reboot on slot 1.
Successfully updated the startup software images of slot 1.
display boot-loader
install commit
bootrom update
Use bootrom update to load the BootWare image on the default file system to the Normal area of BootWare.
Syntax
In standalone mode:
bootrom update file file slot slot-number-list
In IRF mode:
bootrom update file file chassis chassis-number 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 a space-separated list of up to seven slot number items. An item specifies a card by its slot number or a range of cards in the form of start-slot-number to end-slot-number. The end slot number must be equal to or greater than the start slot number. (In standalone mode.)
chassis chassis-number: Specifies an IRF member device by its member ID or specifies a PEX by its virtual chassis number. (In IRF mode.)
slot slot-number-list: Specifies a space-separated list of up to seven slot number items. An item specifies a card by its slot number, a range of cards in the form of start-slot-number to end-slot-number, or a PEX by its virtual slot number. The end slot number must be equal to or greater than the start slot number. (In IRF mode.)
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 device.
Examples
# (In standalone mode.) Use the file a.bin in the root directory of the flash memory to upgrade the BootWare image.
<Sysname> bootrom update file flash:/a.bin slot 1
This command will update the Boot ROM file on the specified board(s), Continue? [Y/N]:y
Now updating the Boot ROM, please wait................Done.
Related commands
boot-loader file
display boot-loader
Use display boot-loader to display current software images and startup software images.
Syntax
In standalone mode:
display boot-loader [ slot slot-number ]
In IRF mode:
display boot-loader [ chassis chassis-number [ slot slot-number ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies the slot number of an MPU. If you do not specify an MPU, this command displays the software images on each MPU. (In standalone mode.)
chassis chassis-number [ slot slot-number ]: Specifies an IRF member device or an MPU in an IRF member device. The chassis-number argument represents the IRF member ID of the device. The slot-number argument represents the slot number of the MPU on the device. If you do not specify an IRF member device, this command displays the software images on each MPU in the IRF fabric. If you specify an IRF member device without specifying an MPU, this command displays the software images on each MPU on the specified member device. (In IRF mode.)
Usage guidelines
This command displays both current and startup images for the parent fabric and its PEXs.
Examples
# (In standalone mode.) Display the current software images and startup software images.
<Sysname> display boot-loader
Software images on slot 1:
Current software images:
flash:/boot.bin
flash:/system.bin
Main startup software images:
flash:/boot.bin
flash:/system.bin
Backup startup software images:
flash:/boot.bin
flash:/system.bin
# (In IRF mode.) On an IRF 3 system, display the current software images and startup software images.
<Sysname> display boot-loader
Software images on chassis 0 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
Software images on chassis 5 slot 1:
Current software images:
flash:/rpu-S6300-boot.bin
flash:/rpu-S6300-systemt.bin
Main startup software images:
flash:/rpu-S6300-boot.bin
flash:/rpu-S6300-systemt.bin
Backup startup software images:
flash:/rpu-S6300-boot.bin
flash:/rpu-S6300-systemt.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 boot-loader pex
Use display boot-loader pex to display the PEX startup software images stored on the parent fabric.
Syntax
display boot-loader pex [ pex-model ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
pex-model: Specifies a PEX model, a case-insensitive string of 1 to 63 characters. You must enter the complete PEX model name for the device to identify the PEX correctly. For available PEX models, enter boot-loader pex ? If you do not specify a PEX model, the system displays all PEX startup software images on the parent device.
Usage guidelines
Use this command to identify the startup software images on the parent device for a PEX model.
PEXs always start up with the software images on the global active MPU when they attempt to load software from the parent fabric. To guarantee that the PEXs load the correct software when a master/subordinate switchover occurs, make sure the PEX startup software images are the same across all MPUs.
Examples
# Display the PEX startup software images.
<Sysname> display boot-loader pex
Startup software image files for PEXs to load from the parent device:
PEX model: PEX-S6300
flash:/S6300PEX-BOOT.bin
flash:/S6300PEX-SYSTEM.bin
PEX model: PEX-S5130EI
None
PEX model: PEX-S5130HI
None
reset boot-loader pex
Use reset boot-loader blade to clear the list of PEX startup images stored on the parent fabric.
Syntax
reset boot-loader pex pex-model
Views
User view
Predefined user roles
network-admin
Parameters
pex-model: Specifies the PEX model. You must enter the complete PEX model name for the device to identify the PEX correctly. For available PEX models, enter reset boot-loader pex ?
Usage guidelines
To execute this command, make sure the system has completed startup and is operating correctly.
This command does not delete the startup software images from the parent fabric.
Examples
# Clear the list of PEX startup images stored on the parent fabric for the S6300 switch.
<Sysname> reset boot-loader pex PEX-S6300
Related commands
boot-loader pex file
display boot-loader pex
version auto-update enable
Use version auto-update enable to enable software synchronization from active MPU to standby MPU at startup.
Use undo version auto-update enable to disable this feature.
Syntax
version auto-update enable
undo version auto-update enable
Default
Software synchronization from active MPU to standby MPU is enabled. If software inconsistency is detected at startup, the standby MPU loads the current software images of the active MPU.
Views
System view
Predefined user roles
network-admin
Usage guidelines
This command is available in standalone mode.
To make sure the standby MPU always runs the same software images as the active MPU, configure both the version auto-update enable command and the undo version check ignore command.
The startup software version check feature examines the standby MPU's startup software images for version inconsistency with the active MPU's current software images at startup. If their software versions are different, the standby MPU copies the current software images of the active MPU, specifies them as main startup software images, and reboots with these images.
To ensure a successful synchronization in a multiuser environment, make sure no one reboots or swaps MPUs during the software synchronization process. You can configure the information center to output the synchronization status to configuration terminals (see Network Management and Monitoring Configuration Guide).
Examples
# Enable software auto-update for the standby MPU.
<Sysname> system-view
[Sysname] version auto-update enable
Related commands
version check ignore
version check ignore
Use version check ignore to disable startup software version check for the standby MPU at startup.
Use undo version check ignore to enable this feature.
Syntax
version check ignore
undo version check ignore
Default
The startup software images on the standby MPU are checked for version inconsistency with the current software images on the active MPU.
Views
System view
Predefined user roles
network-admin
Usage guidelines
This command is available in standalone mode.
When the standby MPU starts up, this command disables the system to examine the standby MPU's startup software images for version inconsistency with the active MPU's current software images. The standby MPU can start up with a different software version than the active MPU.
As a best practice, use ISSU instead of this command to upgrade software, if possible. The startup software version check feature might fail to work because the software versions of the MPUs are incompatible.
To avoid anomalies, do not disable startup software version check for the standby MPU unless for software upgrade.
To make sure the standby MPU always runs the same software images as the active MPU, configure both the version auto-update enable command and the undo version check ignore command.
Examples
# Enable startup software version check for the standby MPU.
<Sysname> system-view
[Sysname] undo version check ignore
Related commands
version auto-update enable
