Software upgrade commands -- boot-loader blade file

Use boot-loader blade file to specify the startup image files for security engines to start up from the device.

Syntax

boot-loader blade blade-model file boot filename system filename [ feature filename&<1-30> ]

boot-loader blade blade-model file ipe ipe-filename

Views

User view

Predefined user roles

network-admin

Parameters

blade-model: Specifies the security engine model. You must enter the complete security engine model name for the device to identify the security engine correctly. For available security engine models, enter boot-loader blade ?

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 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

This command copies the security engine startup images to every MPU. However, security engines always use the software images on the active MPU (in standalone mode) or the global active MPU (in IRF mode). To prevent a security engine startup failure after an active/standby switchover, execute this command each time you add a new MPU.

This command overwrites the entire security engine startup image list. To add new startup feature images, specify all feature image files, including feature image files in the old startup image list. The new startup image list will contain only the feature image files that are specified in the command.

You can also use the boot-loader file command to set startup software images in the local file system of a security engine. The security engines will always attempt to start up from the local file system before they use the startup software images stored on the device.

Examples

# (Distributed devices in standalone mode.) Specify slot1.1#flash:/m9000_fw.ipe as the startup image file for the Blade-m9k security engine.

<Sysname> boot-loader blade Blade-m9k file ipe slot1.1#flash:/m9000_fw.ipe

Verifying the IPE file and the images............................Done.

File flash:/blade3fwm9k-cmw710-boot-a0002.bin already exists on slot 5.

File flash:/blade3fwm9k-cmw710-system-a0002.bin already exists on slot 5.

Overwrite the existing files? [Y/N]:Y

Decompressing file blade3fwm9k-cmw710-boot-a0002.bin to flash:/blade3fwm9k-cmw710-boot-a0002.bin....................Done.

Decompressing file blade3fwm9k-cmw710-system-a0002.bin to flash:/blade3fwm9k-cmw710-system-a0002.bin..............................Done.

File flash:/blade3fwm9k-cmw710-boot-a0002.bin already exists on slot 4.

File flash:/blade3fwm9k-cmw710-system-a0002.bin already exists on slot 4.

Overwrite the existing files? [Y/N]:Y

Copying file flash:/blade3fwm9k-cmw710-boot-a0002.bin to slot4#flash:/blade3fwm9k-cmw710-boot-a0002.bin..................................Done.

Copying file flash:/blade3fwm9k-cmw710-system-a0002.bin to slot4#flash:/blade3fwm9k-cmw710-system-a0002.bin................................Done.

# (Distributed devices in standalone mode.) Specify slot1.1#flash:/blade3fwm9k-cmw710-boot-a0002.bin and slot1.1#flash:/blade3fwm9k-cmw710-system-a0002.bin as the startup boot and system image files for the Blade-m9k security engine.

<Sysname>boot-loader blade Blade-m9k file boot slot1.1#cfa0:/blade3fwm9k-cmw710-boot-a0002.bin system slot1.1#cfa0:/blade3fwm9k-cmw710-system-a0002.bin

File flash:/blade3fwm9k-cmw710-boot-a0002.bin already exists on slot 4.

File flash:/blade3fwm9k-cmw710-system-a0002.bin already exists on slot 4.

Overwrite the existing files? [Y/N]:Y

Copying file cfa0:/blade3fwm9k-cmw710-boot-a0002.bin to slot4#flash:/blade3fwm9k-cmw710-boot-a0002.bin..................Done.

Copying file cfa0:/blade3fwm9k-cmw710-system-a0002.bin to slot4#flash:/blade3fwm9k-cmw710-system-a0002.bin.........................Done.

File flash:/blade3fwm9k-cmw710-boot-a0002.bin already exists on slot 5.

File flash:/blade3fwm9k-cmw710-system-a0002.bin already exists on slot 5.

Overwrite the existing files? [Y/N]:Y

Copying file cfa0:/blade3fwm9k-cmw710-boot-a0002.bin to flash:/blade3fwm9k-cmw710-boot-a0002.bin.................Done.

Copying file cfa0:/blade3fwm9k-cmw710-system-a0002.bin to flash:/blade3fwm9k-cmw710-system-a0002.bin............................Done.

Related commands

display boot-loader blade

Software upgrade commands -- boot-loader file

Use boot-loader file to specify startup image files.

Syntax

Centralized devices:

boot-loader file boot filename system filename [ feature filename&<1-30> ] { backup | main }

boot-loader file ipe-filename { backup | main }

Distributed devices in standalone mode:Centralized IRF devices:

boot-loader file boot filename system filename [ feature filename&<1-30> ] { all | slot slot-number [ cpu cpu-number ] } { backup | main }

boot-loader file ipe-filename { all | slot slot-number [ cpu cpu-number ] } { backup | main }

Distributed devices in IRF mode:

boot-loader file boot filename system filename [ feature filename&<1-30> ] { all | chassis chassis-number slot slot-number [ cpu cpu-number ] } { backup | main }

boot-loader file ipe-filename { all | chassis chassis-number slot slot-number [ cpu cpu-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. (Distributed devices in standalone mode.)

slot slot-number: Specifies the IRF member ID of a member device. (Centralized IRF devices.) (IRF 3 incapable.)

slot slot-number: Specifies the IRF member ID of a member device or the slot number of a PEX. To specify a PEX, make sure the PEX has a file system. (Centralized IRF devices.) (IRF 3 capable.)

chassis chassis-number slot slot-number: Specifies an MPU or firewall card in the IRF fabric. The chassis-number argument represents the IRF member ID of the device that holds the MPU or firewall card. The slot-number argument represents the slot number of the MPU or firewall card. (Distributed devices in IRF mode.) (IRF 3 incapable.)

chassis chassis-number slot slot-number: Specifies an MPU, PEX, or firewall card. The chassis-number argument represents the IRF member ID of the device that holds the MPU, PEX, or firewall card. The slot-number argument represents the slot number of the MPU, PEX, or firewall card. When you specify a PEX, make sure the PEX has a file system. (Distributed devices in IRF mode.) (IRF 3 capable.)

cpu cpu-number: Specifies the CPU number of the security engine on the specified firewall card. This option is dedicated for security engine upgrade.

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.

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.

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.

You can use this command to upgrade PEXs that have a file system by updating their local startup software images. To upgrade PEXs that do not have a file system, you must use the boot-loader pex file command.

You can use this command to specify startup software images for a security engine to load from its local file system. You can also use the boot-loader blade file command to specify startup software images for the security engine to load from the device. The security engine will always attempt to start up from its local file system before it uses the startup software images stored on the active MPU or global active MPU.

Examples

# (Centralized devices.) Specify flash:/all.ipe as the main startup image file.

<Sysname> boot-loader file flash:/all.ipe main

Verifying the file flash:/all.ipe on the device............Done.

xx Switch images in IPE:

boot.bin

system.bin

This command will set the main startup software images. Continue? [Y/N]:Y

Add images to the device.

File flash:/boot.bin already exists on the device.

File flash:/system.bin already exists on the device.

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 the device...Done.

Verifying the file flash:/system.bin on the device.............Done.

The images that have passed all examinations will be used as the main startup software images at the next reboot on the device.

# (Centralized devices.) Specify flash:/boot.bin and flash:/system.bin as the main startup boot and system image files.

<Sysname> boot-loader file boot flash:/boot.bin system flash:/system.bin main

This command will set the main startup software images. Continue? [Y/N]:y

The images that have passed all examinations will be used as the main startup software images at the next reboot on the device.

# (Distributed devices in standalone mode.) (Centralized IRF devices.) 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 IPE file and the images............Done.

XX Switch 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.

# (Distributed devices 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.

XX Switch 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

# (Centralized IRF devices.) Specify flash:/all.ipe as the main startup image file for all IRF member devices.

<Sysname> boot-loader file slot1#flash:/all.ipe all main

Verifying the file flash:/all.ipe on slot 1...............................Done.

XX Switch 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.

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 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.

Loading......................Done.

Loading......................Done.

Loading......................Done.

Loading......................Done.

The images that have passed all examinations will be used as the main startup software images at the next reboot on slot 2.

The images that have passed all examinations will be used as the main startup software images at the next reboot on slot 3.

Decompression completed.

Do you want to delete flash:/all.ipe now? [Y/N]:n

Related commands

boot-loader blade file

boot-loader pex file

display boot-loader

Software upgrade commands -- boot-loader pex file (IRF 3)

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 to upgrade PEX software.

· If PEXs do not have a file system, you must specify remote startup PEX software images.

· If PEXs have a file system, 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.

(Centralized IRF devices.) This command copies the PEX startup images to all parent devices automatically. However, PEXs always start up with the software images on the master device. To prevent the PEX startup failure after a master/subordinate switchover, execute this command each time you add a parent device.

(Distributed devices in IRF mode.) 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

# (Centralized IRF devices.) Specify flash:/all.ipe as the remote startup image file for the PEX-S5120HI PEXs.

<Sysname> boot-loader pex PEX-S5120HI file ipe flash:/all.ipe

Verifying the file flash:/all.ipe on slot 1............Done.

File flash:/rpu-s5120hi-boot.bin already exists on slot 1.

File flash:/rpu-s5120hi-system.bin already exists on 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 slot 2.

File flash:/rpu-s5120hi-system.bin already exists on slot 2.

Overwrite the existing files? [Y/N]:Y

Copying file flash:/rpu-s5120hi-boot.bin to slot2#flash:/rpu-s5120hi-boot.bin.........................Done.

Copying file flash:/rpu-s5120hi-system.bin to slot2#flash:/rpu-s5120hi-system.bin.............................................Done.

# (Centralized IRF devices.) 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 slot 1.

File flash:/system.bin already exists on slot 1.

Overwrite the existing files? [Y/N]:y

Copying file flash:/boot.bin to slot1#flash:/boot.bin.........................Done.

Copying file flash:/system.bin to slot1#flash:/system.bin......................................................Done.

# (Distributed devices in IRF mode.) Specify flash:/all.ipe as the remote startup image file for the PEX-S5120HI PEXs.

<Sysname> boot-loader pex PEX-S5120HI file ipe flash:/all.ipe

Verifying the file flash:/all.ipe on chassis 1 slot 1............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.

# (Distributed devices in IRF mode.) 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 file

display boot-loader pex

Software upgrade commands -- boot-loader pex file (IRF 3.1)

Use boot-loader pex file to upgrade startup images for PEXs from the parent fabric.

Syntax

Centralized IRF devices:

boot-loader pex file ipe ipe-filename transfer-service ftp { all | slot slot-list }

Distributed devices in IRF mode:

boot-loader pex file ipe ipe-filename transfer-service ftp { all | chassis chassis-list }

Views

User view

Predefined user roles

network-admin

mdc-admin

Parameters

ipe ipe-filename: Specifies an .ipe image package file in the filesystemname/pex_images/filename.ipe format. The file must be stored in the pex_images folder in the root directory of a file system on the parent fabric. 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.

transfer-service: Specifies the file transfer service for the parent fabric to use to transfer the .ipe file to PEXs.

ftp Specifies FTP as the file transfer service.

all: Specifies all PEXs.

slot slot-list: Specifies a space-separated list of up to 10 virtual slot number items. An item specifies a PEX by its virtual slot number or a range of PEXs 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. (Centralized IRF devices.)

chassis chassis-list: Specifies a space-separated list of up to 10 virtual chassis number items. An item specifies a PEX by its virtual chassis number or a range of PEXs in the form of start-chassis-number to end-chassis-number. The end chassis number must be equal to or greater than the start chassis number. (Distributed devices in IRF mode.)

Usage guidelines

This command upgrades PEXs from the parent fabric in an IRF 3.1 system. You can also upgrade a PEX by logging in to the PEX through the console port. Upgrading PEXs from the parent fabric has the following benefits:

· It is easy to ensure compatibility between the startup images of PEXs and the startup images of the parent fabric.

· You do not need to log in to PEXs.

You can transfer the upgrade file to the pex_images folder only on the default MDC.

After the file transfer process is completed, PEXs that successfully received the .ipe file automatically reboot to complete the upgrade. PEXs that failed to receive the .ipe file do not reboot and are not upgraded.

You cannot use this command to upgrade PEXs if the PEXs are S5560-EI switches. To upgrade the PEXs, you must log in to each of them through their respective console ports.

Examples

# (Centralized IRF devices.) Upgrade PEX 100 and PEXs 105 through 110.

<Sysname> boot-loader pex file ipe slot1#flash/pex_images:/all.ipe transfer-service ftp slot 100 105 to 110

# (Distributed devices in IRF mode.) Upgrade PEX 100 and PEXs 105 through 110.

<Sysname> boot-loader pex file ipe chassis1#slot1#flash/pex_images:/all.ipe transfer-service ftp chassis 100 105 to 110

Software upgrade commands -- boot-loader update

Use boot-loader update to synchronize startup images.

Syntax

Distributed devices in standalone mode:Centralized IRF devices:

boot-loader update { all | slot slot-number }

Distributed devices 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. (Distributed devices in standalone mode.)

all: Synchronizes startup images from the master to all subordinate devices. (Centralized IRF devices.)

all: Synchronizes startup images from the global active MPU to all standby MPUs. (Distributed devices in IRF mode.)

slot slot-number: Specifies the slot number of the standby MPU. (Distributed devices in standalone mode.)

slot slot-number: Specifies the IRF member ID of a subordinate device. (Centralized IRF devices.)

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. (Distributed devices in IRF mode.)

Usage guidelines

Centralized IRF devices:

You can use this command to synchronize startup images after adding new member devices.

If any of the startup software images require a license, register and activate a license for the image on the new subordinate device before executing this command. Use the display license feature command to verify the licensing state of software images.

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.

If a patch installation or ISSU has been performed on the master, use the install commit command to update the set of main startup images on the master before software synchronization. This command ensures startup image consistency between the master and the subordinate device.

Startup image synchronization fails if any software image being synchronized is not available or is corrupted.

Distributed devices in standalone mode:Distributed devices in IRF mode:

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 a patch installation or ISSU 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...

Copying main startup software images to slot 1. Please wait...

Done.

Setting copied images as main startup software images for slot 1...

Done.

Successfully updated the startup software images of slot 1.

Related commands

display boot-loader

install commit

Software upgrade commands -- bootrom backup

Use bootrom backup to back up the BootWare image in the Normal area to the Backup area on a BootWare.

Syntax

Centralized devices:

bootrom backup [ cpu cpu-number ] [ subslot subslot-number-list ] [ all | part ]

Distributed devices in standalone mode:Centralized IRF devices:

bootrom backup slot slot-number-list [ cpu cpu-number ] [ subslot subslot-number-list ] [ all | part ]

Distributed devices in IRF mode:

bootrom backup chassis chassis-number slot slot-number-list [ cpu cpu-number ] [ subslot subslot-number-list ] [ all | part ]

Views

User view

Predefined user roles

network-admin

Parameters

slot slot-number-list: Specifies a space-separated list of up to seven slot number items. An item specifies a card by its slot number or a range of cards in the form of start-slot-number to end-slot-number. The end slot number must be equal to or greater than the start slot number. (Distributed devices in standalone mode.)

slot slot-number-list: Specifies a space-separated list of up to seven slot number items. An item specifies an IRF member device by its member ID or a range of IRF member devices 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. (Centralized IRF devices.) (IRF 3 incapable.)

slot slot-number-list: Specifies a space-separated list of up to seven slot number items. An item can specify an IRF member device by its member ID or specify a PEX by its virtual slot number. An item can also specify a range of IRF member devices or PEXs 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. (Centralized IRF devices.) (IRF 3 capable.)

chassis chassis-number: Specifies an IRF member device by its member ID. (Distributed devices in IRF mode.) (IRF 3 incapable.)

chassis chassis-number: Specifies an IRF member device by its member ID or specifies a PEX by its virtual chassis number. (Distributed devices in IRF mode.) (IRF 3 capable.)

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 on the specified IRF member device. The end slot number must be equal to or greater than the start slot number. (Distributed devices in IRF mode.) (IRF 3 incapable.)

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. (Distributed devices in IRF mode.) (IRF 3 capable.)

subslot subslot-number-list: Specifies a list of up to seven subslot number items. An item specifies a subcard by its subslot number or a range of subcards in the form of start-subslot-number to end-subslot-number. If you do not specify a subcard, this command backs up the BootWare image for the base card.

all: Backs up the entire BootWare image, including the basic segment and the extended segment. If you do not specify the all or part keyword, this command backs up the entire BootWare image.

part: Backs up the extended BootWare image section.

cpu cpu-number: Specifies a CPU by its number. The cpu cpu-number option is available only if multiple CPUs are available on the specified slot.

Usage guidelines

A BootWare is divided into a Normal area and a Backup area. The BootWare image is stored in the Normal area and backed up to the Backup area. At startup, the system reads the BootWare image automatically from the Normal area. If the image is inaccessible, the system reads the BootWare image from the Backup area.

If the BootWare image in the Normal area is corrupted or requires a version rollback, use the bootrom restore command to copy the BootWare image in the Backup area to the Normal area.

Examples

# Back up the entire BootWare image from the Normal area to the Backup area.

<Sysname> bootrom backup slot 1

Now backing up the Boot ROM, please wait...

......Done.

Related commands

bootrom restore

Software upgrade commands -- bootrom read

Use bootrom read to back up the BootWare image in the Normal area of a BootWare to the default file system.

Syntax

Centralized devices:

bootrom read [ cpu cpu-number ] [ subslot subslot-number-list ] [ all | part ]

Distributed devices in standalone mode:Centralized IRF devices:

bootrom read slot slot-number-list [ cpu cpu-number ] [ subslot subslot-number-list ] [ all | part ]

Distributed devices in IRF mode:

bootrom read chassis chassis-number slot slot-number-list [ cpu cpu-number ] [ subslot subslot-number-list ] [ all | part ]

Views

User view

Predefined user roles

network-admin

Parameters

slot slot-number-list: Specifies a space-separated list of up to seven slot number items. An item specifies a card by its slot number or a range of cards in the form of start-slot-number to end-slot-number. The end slot number must be equal to or greater than the start slot number. (Distributed devices in standalone mode.)

slot slot-number-list: Specifies a space-separated list of up to seven slot number items. An item specifies an IRF member device by its member ID or a range of IRF member devices 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. (Centralized IRF devices.) (IRF 3 incapable.)

slot slot-number-list: Specifies a space-separated list of up to seven slot number items. An item can specify an IRF member device by its member ID or specify a PEX by its virtual slot number. An item can also specify a range of IRF member devices or PEXs 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. (Centralized IRF devices.) (IRF 3 capable.)

chassis chassis-number: Specifies an IRF member device by its member ID. (Distributed devices in IRF mode.) (IRF 3 incapable.)

chassis chassis-number: Specifies an IRF member device by its member ID or specifies a PEX by its virtual chassis number. (Distributed devices in IRF mode.) (IRF 3 capable.)

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 on the specified IRF member device. The end slot number must be equal to or greater than the start slot number. (Distributed devices in IRF mode.) (IRF 3 incapable.)

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. (Distributed devices in IRF mode.) (IRF 3 capable.)

subslot subslot-number-list: Specifies a list of up to seven subslot number items. An item specifies a subcard by its subslot number or a range of subcards in the form of start-subslot-number to end-subslot-number. If you do not specify a subcard, this command backs up the BootWare image for the base card.

all: Backs up the entire BootWare image, including the basic segment and the extended segment. If you do not specify the all or part keyword, this command backs up the entire BootWare image.

part: Backs up the extended BootWare image section.

cpu cpu-number: Specifies a CPU by its number. The cpu cpu-number option is available only if multiple CPUs are available on the specified slot.

Usage guidelines

For each BootWare image you are backing up, this command creates two files (basicbtm.bin and extendbtm.bin) in the flash memory for the basic segment and the extended segment. If the BootWare image in the Normal area of a BootWare is corrupted or requires a version rollback, use the bootrom update command to read the two backup files from the flash memory to the BootWare.

Examples

# Back up the BootWare image from the Normal area of BootWare to the flash memory.

<Sysname> bootrom read slot 1

Now reading the Boot ROM, please wait...

.........Done.

Related commands

bootrom update

Software upgrade commands -- bootrom restore

Use bootrom restore to replace the BootWare image in the Normal area with the BootWare image in the Backup area for image restoration or version rollback.

Syntax

Centralized devices:

bootrom restore [ cpu cpu-number ] [ subslot subslot-number-list ] [ all | part ]

Distributed devices in standalone mode:Centralized IRF devices:

bootrom restore slot slot-number-list [ cpu cpu-number ] [ subslot subslot-number-list ] [ all | part ]

Distributed devices in IRF mode:

bootrom restore chassis chassis-number slot slot-number-list [ cpu cpu-number ] [ subslot subslot-number-list ] [ all | part ]

Views

User view

Predefined user roles

network-admin

Parameters

slot slot-number-list: Specifies a space-separated list of up to seven slot number items. An item specifies an IRF member device by its member ID or a range of IRF member devices 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. (Centralized IRF devices.) (IRF 3 incapable.)

slot slot-number-list: Specifies a space-separated list of up to seven slot number items. An item can specify an IRF member device by its member ID or specify a PEX by its virtual slot number. An item can also specify a range of IRF member devices or PEXs 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. (Centralized IRF devices.) (IRF 3 capable.)

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. (Distributed devices in standalone mode.)

chassis chassis-number: Specifies an IRF member device by its member ID. (Distributed devices in IRF mode.) (IRF 3 incapable.)

chassis chassis-number: Specifies an IRF member device by its member ID or specifies a PEX by its virtual chassis number. (Distributed devices in IRF mode.) (IRF 3 capable.)

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 on the specified IRF member device. The end slot number must be equal to or greater than the start slot number. (Distributed devices in IRF mode.) (IRF 3 incapable.)

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. (Distributed devices in IRF mode.) (IRF 3 capable.)

subslot subslot-number-list: Specifies a list of up to seven subslot number items. Each item specifies a subcard by its subslot number or a range of subcards in the form of start-subslot-number to end-subslot-number. If you do not specify a subcard, this command restores the BootWare image for the base card.

all: Restores the entire BootWare image, including the basic segment and the extended segment. If you do not specify the all or part keyword, this command restores the entire BootWare image.

part: Restores the extended BootWare image section.

cpu cpu-number: Specifies a CPU by its number. The cpu cpu-number option is available only if multiple CPUs are available on the specified slot.

Examples

# (Centralized devices.) Restore the entire BootWare image.

<Sysname> bootrom restore all

This command will restore the Boot ROM file, Continue? [Y/N]:y

Now restoring the Boot ROM, please wait...

......Done.

# (Distributed devices in standalone mode.) (Centralized IRF devices.) Restore the entire BootWare image.

<Sysname> bootrom restore slot 1

This command will restore the Boot ROM file on the specified board(s), Continue? [Y/N]:y

Now restoring the Boot ROM, please wait...

......Done.

Related commands

bootrom backup

Software upgrade commands -- bootrom update

Use bootrom update to load the BootWare image from a file system to the Normal BootWare area.

Syntax

Centralized devices:

bootrom update file file [ cpu cpu-number ] [ subslot subslot-number-list ] [ all | part ]

Distributed devices in standalone mode:Centralized IRF devices:

bootrom update file file slot slot-number-list [ cpu cpu-number ] [ subslot subslot-number-list ] [ all | part ]

Distributed devices in IRF mode:

bootrom update file file chassis chassis-number slot slot-number-list [ cpu cpu-number ] [ subslot subslot-number-list ] [ all | part ]

Views

User view

Predefined user roles

network-admin

Parameters

file file: Specifies the file that contains the BootWare image. The file argument represents the file name, a string of 1 to 63 characters.

slot slot-number-list: Specifies a space-separated list of up to seven slot number items. An item specifies an IRF member device by its member ID or a range of IRF member devices 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. (Centralized IRF devices.) (IRF 3 incapable.)

slot slot-number-list: Specifies a space-separated list of up to seven slot number items. An item can specify an IRF member device by its member ID or specify a PEX by its virtual slot number. An item can also specify a range of IRF member devices or PEXs 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. (Centralized IRF devices.) (IRF 3 capable.)

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. (Distributed devices in standalone mode.)

chassis chassis-number: Specifies an IRF member device by its member ID. (Distributed devices in IRF mode.) (IRF 3 incapable.)

chassis chassis-number: Specifies an IRF member device by its member ID or specifies a PEX by its virtual chassis number. (Distributed devices in IRF mode.) (IRF 3 capable.)

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 on the specified IRF member device. The end slot number must be equal to or greater than the start slot number. (Distributed devices in IRF mode.) (IRF 3 incapable.)

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. (Distributed devices in IRF mode.) (IRF 3 capable.)

subslot subslot-number-list: Specifies a list of up to seven subslot number items. Each item specifies a subcard by its subslot number or a range of subcards in the form of start-subslot-number to end-subslot-number. If you do not specify a subcard, this command loads the BootWare image for the base card.

all: Loads the entire BootWare image, including the basic segment and the extended segment. If you do not specify the all or part keyword, this command restores the entire BootWare image.

part: Loads the extended BootWare image section.

cpu cpu-number: Specifies a CPU by its number. The cpu cpu-number option is available only if multiple CPUs are available on the specified slot.

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

# (Centralized devices.) 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

This command will update the Boot ROM file, Continue? [Y/N]:y

Now updating the Boot ROM, please wait................Done.

# (Distributed devices in standalone mode.) (Centralized IRF devices.) 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

Software upgrade commands -- bootrom-update security-check enable

Use bootrom-update security-check enable to enable BootWare image validity check.

Use undo bootrom-update security-check enable to disable BootWare image validity check.

Syntax

bootrom-update security-check enable

undo bootrom-update security-check enable

Default

BootWare image validity check is enabled.

Views

System view

Predefined user roles

network-admin

Usage guidelines

Before a BootWare image upgrade starts, this feature examines the upgrade BootWare image for file validity and incompatibility with hardware. If the BootWare image passes the check, the upgrade process starts. If the check fails, the system does not perform the upgrade.

Examples

# Enable BootWare image validity check.

<Sysname> system-view

[Sysname] bootrom-update security-check enable

Software upgrade commands -- display boot-loader

Use display boot-loader to display current software images and startup software images.

Syntax

Centralized devices:

display boot-loader

Distributed devices in standalone mode:Centralized IRF devices:

display boot-loader [ slot slot-number [ cpu cpu-number ] ]

Distributed devices in IRF mode:

display boot-loader [ chassis chassis-number [ slot slot-number [ cpu cpu-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. (Distributed devices in standalone mode.)

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. (Centralized IRF devices.)

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. (Distributed devices in IRF mode.)

cpu cpu-number: Specifies the CPU number of the security engine on the specified firewall card.

Usage guidelines

This command displays the software images for the parent fabric, its PEXs, and security engine.

· For the parent fabric, this command displays both current and startup images.

· For PEXs that have a file system, this command displays the current images and local startup images.

· For PEXs that do not have a file system, this command displays the current images.

· For security engines, this command displays the current images and local startup images.

Examples

# (Centralized devices.) Display the current software images and startup software images.

<Sysname> display boot-loader

Software images on the device:

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

# (Distributed devices in standalone mode.) (Centralized IRF devices.) 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

# (Centralized IRF devices.) On an IRF 3 system, 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

Software images on slot 101:

Current software images:

flash:/rpu-s5120hi-boot.bin

flash:/rpu-s5120hi-system.bin

Main startup software images:

flash:/rpu-s5120hi-boot.bin

flash:/rpu-s5120hi-system.bin

Backup startup software images:

flash:/rpu-s5120hi-boot.bin

flash:/rpu-s5120hi-system.bin

# (Distributed devices 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-s5120hi-boot.bin

flash:/rpu-s5120hi-systemt.bin

Main startup software images:

flash:/rpu-s5120hi-boot.bin

flash:/rpu-s5120hi-systemt.bin

Backup startup software images:

flash:/rpu-s5120hi-boot.bin

flash:/rpu-s5120hi-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

Software upgrade commands -- display boot-loader blade

Use display boot-loader blade to display security engine startup software images stored on the device.

Syntax

display boot-loader blade [ blade-model ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

blade-model: Specifies a security engine model. You must enter the complete model name for the device to identify the security engine correctly. For available security engine models, enter boot-loader blade ? If you do not specify a security engine model, the system displays all security engine startup software images stored on the device.

Usage guidelines

Use this command to identify the startup software images on the device for a security engine model.

(Distributed devices in standalone mode.) Security engines always start up with the software images on the active MPU when they attempt to load software from the device. To guarantee that the security engines load the correct software when an active/standby switchover occurs, make sure the security engine startup software images are the same across the MPUs.

(Distributed devices in IRF mode.) Security engines 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 security engines load the correct software when a master/subordinate switchover occurs, make sure the security engine startup software images are the same across the MPUs.

Examples

# Display the security engine startup software images.

<Sysname> display boot-loader blade Blade-m9k

Startup software image files for BLADEs to load from the parent device:

Blade model: Blade-m9k

flash:/blade3fwm9k-cmw710-boot-a0002.bin

flash:/blade3fwm9k-cmw710-system-a0002.bin

Table 2 Command output

Field | Description
Startup software image files for BLADEs to load from the parent device | Startup image files for the security engine to load from the device.
Blade model | Security engine model.

Software upgrade commands -- 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 master device or 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 member devices or 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-S5120HI

flash:/rpu-s5120hi-boot.bin

flash:/rpu-s5120hi-system.bin

PEX model: PEX-S5820V2

flash:/boot.bin

flash:/system.bin

Software upgrade commands -- 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 an IRF member device by its member ID. If you do not specify an IRF member device, this command displays information for all IRF member devices.

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: xxxx

Service name: boot

Platform version: 7.1.022

Product version: Test 2201

Supported board: mpu

[Component]

Component: boot

Description: boot package

Software image signature: HP

flash:/system.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: system

Platform version: 7.1.022

Product version: Test 2201

Supported board: mpu

[Component]

Component: system

Description: system package

Software image signature: HP

flash:/feature.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: test

Platform version: 7.1.022

Product version: Test 2201

Supported board: mpu

[Component]

Component: test

Description: test package

Software image signature: HP

Table 3 Command output

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 can only be mpu, which indicates an IRF member device.
[Component] | Information about components included in the image file.
Component | Component name.
Description | Component description.
Software image signature | Signature for the software image: · HP. · HP-US. · HPE. The Comware system can be upgraded from a version with the HP or HP-US signature to a version with the HPE signature. To upgrade the Comware system from a version without a signature to a version with the HPE signature, you must first patch the Comware system or upgrade the Comware system to a version with the HP or HP-US signature.

‌

Related commands

install active

Software upgrade commands -- 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 an IRF member device by its member ID. If you do not specify an IRF member device, this command displays information for all IRF member devices.

verbose: Displays detailed information. If you do not specify this keyword, the command displays only image names.

Usage guidelines

After you execute the install commit command, use the display install committed command to verify that the main startup image list has been updated with the software image changes.

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: xxxx

Service name: boot

Platform version: 7.1

Product version: Beta 1330

Supported board: mpu

[Component]

Component: boot

Description: boot package

Software image signature: HP

flash:/system-t5101.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: system

Platform version: 7.1

Product version: Beta 1330

Supported board: mpu

[Component]

Component: system

Description: system package

Software image signature: HP

flash:/ssh-feature.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: ssh

Platform version: 7.1

Product version: Beta 1330

Supported board: mpu

[Component]

Component: ssh

Description: ssh package

Software image signature: HP

For information about the command output, see Table 3.

Related commands

boot-loader file

install commit

Software upgrade commands -- firmware update

Use firmware update to upgrade firmware.

Syntax

Centralized devices:

firmware update [ subslot subslot-number ] { cpld cpld-number | cpu cpu-number | fpga fpga-number | module module-number } file filename

Distributed devices in standalone mode:Centralized IRF devices:

firmware update slot slot-number [ subslot subslot-number ] { cpld cpld-number | cpu cpu-number | fpga fpga-number | module module-number } file filename

Distributed devices in IRF mode:

firmware update chassis chassis-number slot slot-number [ subslot subslot-number ] { cpld cpld-number | cpu cpu-number | fpga fpga-number | module module-number } file filename

Views

User view

Predefined user roles

network-admin

Parameters

chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the IRF member ID. The slot-number argument represents the slot number of the card. (Distributed devices in IRF mode.) (IRF 3 incapable.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member device or specifies a PEX. The chassis-number argument represents the member ID of the IRF member device or the virtual chassis number of the PEX. The slot-number argument represents the slot number of the card or PEX. The slot number is fixed at 0 for the PEX. (Distributed devices in IRF mode.) (IRF 3 capable.)

slot slot-number: Specifies a card by its slot number. (Distributed devices in standalone mode.)

slot slot-number: Specifies an IRF member device. The slot-number argument represents its IRF member ID. (Centralized IRF devices.) (IRF 3 incapable.)

slot slot-number: Specifies an IRF member device by its member ID or specifies a PEX by its virtual slot number. (Centralized IRF devices.) (IRF 3 capable.)

subslot subslot-number: Specifies a subcard by its subslot number. If you do not specify a subcard, the command upgrades firmware for all subcards on the base card.

cpld cpld-number: Specifies a complex programmable logical device (CPLD) by its number.

fpga fpga-number: Specifies a field programmable gate array (FPGA) by its number.

cpu cpu-number: Specifies a CPU by its number.

module module-number: Specifies a module by its number.

file filename: Specifies an upgrade file in the filesystemname/filename.extension 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

Use this command to upgrade firmware that cannot be upgraded using the boot-loader command.

To complete the firmware upgrade, you must power cycle the card or subcard.

To power cycle a card or subcard, use one of the following methods:

· Power cycle the device.

· Remove and reinsert the card or subcard.

· Execute the power-supply off command, and then execute the power-supply on command.

Examples

# (Centralized devices.) Upgrade CPLD 1.

<Sysname> firmware update cpld 1 file package.bin

Updating firmware for CPLD on the specified card or subcard. Continue?[Y/N]:y

Updating the firmware…

Please power cycle the card or subcard to activate the firmware.

# (Distributed devices in standalone mode.) (Centralized IRF devices.) Upgrade CPLD 1 in slot 1.

<Sysname> firmware update slot 1 cpld 1 file package.bin

Updating firmware for CPLD on the specified card or subcard. Continue?[Y/N]:y

Updating the firmware…

Please power cycle the card or subcard to activate the firmware.

Software upgrade commands -- 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.

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.

all: Specifies all IRF member devices.

slot slot-number: Specifies an IRF member device by its member ID.

Usage guidelines

This command adds feature or patch images to the current image list. An image runs in memory immediately after it is activated. However, an activated image cannot stay activated after a reboot unless it meets the following requirements:

· It is a patch image.

· It was activated on all IRF members by using the install activate patch filename all command.

For activated images that cannot stay activated after a reboot, you must execute the install commit command to commit the software changes.

If the image file is not on the member device to be upgraded, the install activate command automatically copies the image file to the member device when you activate the images.

Examples

# Activate system-patch.bin on IRF member device 1.

<Sysname> install activate system-patch.bin slot 1

Related commands

display install active

install commit

install deactivate

Software upgrade commands -- 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 image list with which the system started up.

· The image file is added to the main images list if the system started up with the main startup images.

· The image file is added to the backup image list if the system started up with the backup startup images.

For software changes to take effect at the next startup, you must execute this command after executing the install activate or install deactivate command.

Examples

# Commit software changes.

<Sysname> install commit

This operation will take several minutes, please wait...........................Done.

Related commands

install activate

install deactivate

Software upgrade commands -- 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.

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.

all: Specifies all IRF member devices.

slot slot-number: Specifies an IRF member device by its member ID.

Usage guidelines

You can deactivate only active feature and patch images.

An image stops running in memory immediately after it is deactivated. However, a deactivated image becomes active again after a reboot unless it meets the following requirements:

· It is a patch image.

· It was deactivated on all IRF members by using the install deactivate patch filename all command.

To prevent deactivated images from running again after a reboot, execute the install commit command to commit the software changes.

Examples

# Deactivate route-patch.bin on IRF member device 1.

<Sysname> install deactivate patch flash:/route-patch.bin slot 1

Related commands

display install active

Software upgrade commands -- reset boot-loader blade

Use reset boot-loader blade to clear the list of security engine startup software images stored on the device.

Syntax

reset boot-loader blade blade-model

Views

User view

Predefined user roles

network-admin

Parameters

blade-model: Specifies the security engine model. You must enter the complete security engine model name for the device to identify the security engine correctly. For available security engine models, enter reset boot-loader blade ?

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 list of startup software images stored on the device for the Blade-m9k security engine.

<Sysname> reset boot-loader blade Blade-m9k

Related commands

boot-loader blade file

display boot-loader blade

Software upgrade commands -- 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 S5820V2 switch.

<Sysname> reset boot-loader pex PEX-S5820V2

Related commands

boot-loader pex file

display boot-loader pex

Software upgrade commands -- 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 on distributed devices 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

Software upgrade commands -- 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 on distributed devices 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