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-Password recovery control command
- 13-Python commands
- 14-License management commands
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 07-Software upgrade commands | 73.87 KB |
Software upgrade commands
Unless otherwise stated, the term "IRF system" refers to both IRF fabrics and IRF 3 systems. The term "IRF fabric" refers to both a standalone IRF fabric and the parent fabric in an IRF 3 system. In an IRF 3 system, the master device on the parent fabric is also the master of the entire system. For more information about IRF 3, see Virtual Technologies Configuration Guide.
The switch starts up from the default storage medium. The default storage medium can be the built-in flash memory or a USB disk. To change the default storage medium setting, access the BootWare menu. For more information, see the release notes for the switch.
As a best practice, store the startup images in the flash memory and specify the flash memory as the default storage medium.
If the switch is starting up from a USB disk, do not remove the USB disk.
boot-loader file
Use boot-loader file to specify startup software image files.
Syntax
In standalone mode:
boot-loader file boot boot-package system system-package [ feature feature-package&<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 boot-package system system-package [ feature feature-package&<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 boot-package: Specifies the file path of a .bin boot image file, a case-insensitive string. The file must be stored in the root directory of the default storage medium in the system. The maximum length is 63 characters for the storage-medium:/base-filename.bin segments of the file path. For more information about specifying a file, see "Managing the file system."
system system-package: Specifies the file path of a .bin system image file, a case-insensitive string. The file must be stored in the root directory of the default storage medium in the system. The maximum length is 63 characters for the storage-medium:/base-filename.bin segments of the file path. For more information about specifying a file, see "Managing the file system."
feature feature-package: Specifies a space-separated list of up to 30 .bin feature image file paths. The file paths are case insensitive. The files must be stored in the root directory of the default storage medium in the system. The maximum length is 63 characters for the storage-medium:/base-filename.bin segments of a file path. For more information about specifying a file, see "Managing the file system."
ipe-filename: Specifies the file path of an .ipe image package file, a case-insensitive string. The file must be stored in the root directory of the default storage medium in the system. The maximum length is 63 characters for the storage-medium:/base-filename.ipe segments of the file path.
all: Specifies startup images for all cards. If you specify this keyword, the system copies the card-specific images automatically to the root directory of the storage medium on each card. For a successful upgrade, make sure the specified files include the upgrade images for all cards. (In standalone mode.)
all: Specifies startup images for all cards and PEXs. If you specify this keyword, the system copies the card- and PEX-specific images automatically to the root directory of their respective storage media. For a successful upgrade, make sure the specified files include the upgrade images for all cards and PEXs. (In IRF mode.)
slot slot-number: Specifies the slot number of an MPU. (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 storage medium. (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
Use this command to upgrade the startup software images on all MPUs. To upgrade only standby MPUs, you can also use the boot-loader update command.
The upgrade file must be saved in the root directory of the default storage medium on the active MPU (in standalone mode) or the global active MPU (in IRF mode).
If the specified software images require a license, register and activate a license for each image. If a license-based software image lacks a license, the command execution result is as follows:
· The command cannot be executed if you specify .bin image files.
· The command can set all the images except the license-based image that lacks a license if you specify an .ipe file.
For more information about licensing, see Fundamentals Configuration Guide.
The system automatically copies the upgrade file to the flash memory on the MPU or PEX you are upgrading, and sets images in the file as startup images. If a file with the same name as the upgrade file already exists, you must choose whether to overwrite the existing file. If you specify an .ipe file, the system prompts for a choice to delete or retain the .ipe file after it successfully sets the .bin startup images. To delete the .ipe file, enter y at the prompt.
The boot-loader file command overwrites the entire startup software image list. To add new startup feature images, specify all feature image files, including feature image files in the old startup software image list. The new startup software image list will contain only the feature image files that are specified in the command.
You can use only the boot-loader pex file command to upgrade an S5120-HI PEX.
You can use both the boot-load file and boot-loader pex file commands to upgrade an S6300 PEX or an S5130-EI PEX. The boot-load file command sets PEX startup images in the local medium of the PEX. The boot-loader pex file command sets PEX startup images on the parent fabric. The PEX always attempts to start up with images on the local medium prior to images on the parent fabric.
Examples
# (In standalone mode.) Specify flash:/all.ipe as the main startup image file for the MPU in slot 6.
<Sysname> boot-loader file flash:/all.ipe slot 6 main
Verifying the IPE file and the images............Done.
Images in IPE:
boot.bin
system.bin
This command will set the main startup software images. Continue? [Y/N]:Y
Add images to target slot.
File flash:/boot.bin already exists on slot 6.
File flash:/system.bin already exists on slot 6.
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.
The images that have passed all examinations will be used as the main startup so
ftware images at the next reboot on slot 6.
# (In IRF mode.) Specify flash:/all.ipe as the main startup image file for the MPU in slot 6 on IRF member device 1.
<Sysname> boot-loader file flash:/all.ipe chassis 1 slot 6 main
Verifying the IPE file and the images............Done.
Images in IPE:
boot.bin
system.bin
This command will set the main startup software images. Continue? [Y/N]:Y
Add images to target slot.
File flash:/boot.bin already exists on chassis 1 slot 6.
File flash:/system.bin already exists on chassis 1 slot 6.
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.
The images that have passed all examinations will be used as the main startup so
ftware images at the next reboot on chassis 1 slot 6.
· display boot-loader
boot-loader pex file
Use boot-loader pex file to specify startup PEX software image files stored on the parent fabric for PEXs.
Syntax
boot-loader pex pex-model file ipe ipe-filename
Views
User view
Predefined user roles
Parameters
pex pex-model: Specifies the 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 ?.
boot boot-package: Specifies the file path of a .bin boot image file, a case-insensitive string. The file must be stored in the root directory of a storage medium on the parent fabric. The maximum length is 63 characters for the storage-medium:/base-filename.bin segments of the file path. For more information about specifying a file, see "Managing the file system."
system system-package: Specifies the file path of a .bin system image file, a case-insensitive string. The file must be stored in the root directory of a storage medium on the parent fabric. The maximum length is 63 characters for the storage-medium:/base-filename.bin segments of the file path. For more information about specifying a file, see "Managing the file system."
feature feature-package: Specifies a space-separated list of up to 30 .bin feature image file paths. The file paths are case insensitive. The files must be stored in the root directory of a storage medium on the parent fabric. The maximum length is 63 characters for the storage-medium:/base-filename.bin segments of a file path. For more information about specifying a file, see "Managing the file system."
ipe ipe-filename: Specifies the file path of an .ipe image package file, a case-insensitive string. The file must be stored in the root directory of a storage medium on the parent fabric. The maximum length is 63 characters for the storage-medium:/base-filename.ipe segments of the file path. For more information about specifying a file, see "Managing the file system."
Usage guidelines
The PEX startup images on the parent devices are called remote startup images. The PEX startup images on the PEX's local medium 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 to upgrade PEX software.
· If PEXs do not have a storage medium, you must specify remote startup PEX software images.
· If PEXs have a storage medium, you can also use the boot-loader file command to set their local startup software images. These PEXs will always attempt to start up with the local images before they use the remote images.
Before you use the boot-loader pex file command, save the upgrade files to the root directory of the storage medium on the global active MPU.
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 PEX startup failure after an active/standby switchover, execute this command each time you add a new MPU or member device to the parent fabric.
To guarantee that the PEXs load the correct software when an active/standby switchover occurs, make sure the PEX startup software images are the same across the MPUs of all parent devices.
The boot-loader pex file command overwrites the entire PEX startup software image list. To add new startup feature images, specify all feature image files, including feature image files in the old startup software image list. The new startup software 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
# Specify flash:/all.ipe as the remote startup software image file for the PEX-S5120HI PEXs.
<Sysname> boot-loader pex PEX-S5120HI file ipe flash:/all.ipe
Verifying the IPE file and the images............Done.
File flash:/rpu-s5120hi-boot.bin already exists on chassis 1 slot 1.
File flash:/rpu-s5120hi-system.bin already exists on chassis 1 slot 1.
Overwrite the existing files? [Y/N]:Y
Decompressing file rpu-s5120hi-boot.bin to flash:/rpu-s5120hi-boot.bin.....................Done.
Decompressing file rpu-s5120hi-system.bin to flash:/rpu-s5120hi-system.bin............................................ Done.
File flash:/rpu-s5120hi-boot.bin already exists on chassis 1 slot 2.
File flash:/rpu-s5120hi-system.bin already exists on chassis 1 slot 2.
Overwrite the existing files? [Y/N]:Y
Copying file flash:/rpu-s5120hi-boot.bin to chassis1#slot2#flash:/rpu-s5120hi-boot.bin.........................Done.
Copying file flash:/rpu-s5120hi-system.bin to chassis1#slot2#flash:/rpu-s5120hi-system.bin.......................................Done.
File flash:/rpu-s5120hi-boot.bin already exists on chassis 2 slot 2.
File flash:/rpu-s5120hi-system.bin already exists on chassis 2 slot 2.
Overwrite the existing files? [Y/N]:Y
Copying file flash:/rpu-s5120hi-boot.bin to chassis2#slot2#flash:/rpu-s5120hi-boot.bin.........................Done.
Copying file flash:/rpu-s5120hi-system.bin to chassis2#slot2#flash:/rpu-s5120hi-system.bin....................................Done.
# Specify flash:/boot.bin and flash:/system.bin as the remote startup boot and system image files for the PEX-S5120HI PEXs.
<Sysname> boot-loader pex PEX-S5120HI 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 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: Upgrades the standby MPU. (In standalone mode.)
all: Upgrades all standby MPUs in the IRF fabric. (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 of the global active MPU. The chassis-number argument represents the IRF member ID of the device that holds the standby MPU. The slot-number argument represents the slot number of the standby MPU. (In IRF mode.)
Usage guidelines
You can use this command to synchronize startup images after adding new MPUs.
In standalone mode, this command synchronizes startup images from the active MPU to the standby MPU. In IRF mode, this command synchronizes startup images from the global active MPU to standby 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 (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 main startup images.
The startup images synchronized to the standby MPU are set as main startup images, regardless of whether the source startup images are main or backup.
To guarantee a successful synchronization and software consistency across the MPUs, perform the following before synchronization:
· Verify that the current image list on the active MPU or global active MPU contains the same images as the source image list used for synchronization.
· Make sure that all source startup images are valid.
· 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.
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 MPUs.
Examples
# (In standalone mode.) Synchronize startup images from the active MPU to the standby MPU in slot 7.
<Sysname> boot-loader update slot 7
This command will update the specified standby MPU. Continue? [Y/N]:y
Updating. Please wait...
Copying main startup software images to slot 7. Please wait...
Done.
Setting copied images as main startup software images for slot 7...
Done.
Successfully updated the startup software images of slot 7.
# (In IRF mode.) Synchronize startup images from the global active MPU to the MPU in slot 1 on IRF member device 1.
<Sysname> boot-loader update chassis 1 slot 1
This command will update the specified standby MPU. Continue? [Y/N]:y
Updating. Please wait...
Copying main startup software images to chassis 1 slot 1. Please wait...
Done.
Setting copied images as main startup software images for chassis 1 slot 1...
Done.
Successfully updated the startup software images of chassis 1 slot 1.
· display boot-loader
· install commit
bootrom update
Use bootrom update to load the BootWare image in the default storage medium to the Normal area of BootWare.
Syntax
In standalone mode:
bootrom update file file-url slot slot-number-list [ subslot subslot-number-list ]
In IRF mode:
bootrom update file file-url chassis chassis-number slot slot-number-list [ subslot subslot-number-list ]
Views
User view
Predefined user roles
network-admin
Parameters
file file-url: Specifies the file that contains the BootWare image. The file-url 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. Each item specifies a card by its slot number or a range of cards in the form of start-slot-number to end-slot-number. For example, slot 0 to 1 2. (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. Each item specifies a card or PEX by its slot number or a range of cards or PEXs in the form of start-slot-number to end-slot-number on the specified IRF member device. For example, slot 0 to 1 2. (In IRF mode.)
subslot subslot-number-list: Specifies a list of up to seven subslot number items. Each item specifies a subcard by its slot number or a range of subcards in the form of start-subslot-number to end-subslot-number. If you do not specify subcards, the BootWare image for subcards is not loaded. This option is not supported in the current software version.
Usage guidelines
LSQ OAP modules do not support this command. To upgrade an LSQ OAP module, contact H3C Support. For information about LSQ OAP modules, see OAA Configuration Guide.
If a software upgrade requires upgrading the BootWare image, first use this command to preload the new BootWare image in the default storage medium to the BootWare. This command helps shorten the subsequent upgrade time, reducing the risk of upgrade failure caused by unexpected electricity failure.
To complete the upgrade, reboot the device.
To save space, you can delete the BootWare image from the default storage medium after completing the BootWare image upgrade.
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 3
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 image 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
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, and 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 the software images for the parent fabric and its PEXs,.
· For the parent fabric, this command displays both current and startup images.
· For PEXs that have a storage medium, this command displays the current images and local startup images.
· For PEXs that do not have a storage medium, this command displays the current images.
Examples
# (In standalone mode.) Display the current software images and startup software images.
Software images on slot 7:
Current software images:
flash:/S7500E-cmw710-boot-R7180.bin
flash:/S7500E-cmw710-system-R7180.bin
Main startup software images:
flash:/S7500E-cmw710-boot-R7180.bin
flash:/S7500E-cmw710-system-R7180.bin
Backup startup software images:
None
# (In IRF mode.) Display current software images and startup software images.
Software images on chassis 1 slot 7:
Current software images:
flash:/S7500E-cmw710-boot-R7180.bin
flash:/S7500E-cmw710-system-R7180.bin
Main startup software images:
flash:/S7500E-cmw710-boot-R7180.bin
flash:/S7500E-cmw710-system-R7180.bin
Backup startup software images:
None
Table 1 Command output
|
Field |
Description |
|
Software images on slot slot-number |
In standalone mode, this field displays the Comware images on the MPU in the specified slot. |
|
Software images on chassis chassis-id slot slot-number |
In IRF mode, this field displays the Comware images on the specified MPU. The chassis ID represents the IRF member ID, and the slot number represents the MPU's slot number. |
|
Current software images |
Comware images that have been loaded. |
|
Main startup software images |
Main 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 PEX startup software images.
Syntax
display boot-loader pex [ pex-model ]
Views
Any view
Predefined user roles
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 fabric.
Usage guidelines
Use this command to identify the startup software images on the parent fabric for a PEX model.
When loading software from the parent fabric, PEXs always use the software images on the global active MPU. For the PEXs to load the correct software after a master/subordinate switchover occurs, make sure the PEX startup software images are the same across the MPUs.
Examples
# Display the PEX startup software images on all MPUs.
<Sysname> display boot-loader pex
Main load software image files for PEXs to load from the parent device:
PEX model: PEX-S5120HI
flash:/rpu-s5120hi-boot.bin
flash:/rpu-s5120hi-system.bin
PEX model: PEX-S6300
flash:/boot.bin
flash:/system.bin
Backup load software image files for PEXs to load from the parent device:
PEX model: PEX-S5120HI
flash:/rpu-s5120hi-boot.bin
flash:/rpu-s5120hi-system.bin
PEX model: PEX-S6300
flash:/boot-backup.bin
flash:/system-backup.bin
reset boot-loader pex
Use reset boot-loader blade to clear the PEX startup software image list on the device.
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 device has completed startup and is operating correctly.
This command does not delete the startup software images from the device.
Examples
# Clear the startup software image list on the device for the PEX-S6300 switch.
<Sysname> reset boot-loader pex PEX-S6300
Related commands
version auto-update enable
Use version auto-update enable to enable software synchronization from the active MPU to the 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
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 ensure that 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 performs the following operations:
1. Copies the current software images of the active MPU.
2. Specifies them as main startup software images
3. 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 problems, do not disable startup software version check for the standby MPU unless for software upgrade.
To ensure that the standby MPU always runs the same software images as the active MPU, use 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
