Contents

Software upgrade commands· 1

boot-loader blade file· 1

boot-loader file· 3

boot-loader update· 5

bootrom backup· 6

bootrom restore· 7

bootrom update· 8

bootrom-update security-check enable· 9

display boot-loader 10

display boot-loader blade· 11

reset boot-loader blade· 12

version auto-update enable· 13

version check ignore· 14

 

Software upgrade commands

As a best practice, store the startup images in the factory default file system. If you store the startup images in a hot swappable storage medium, do not remove the hot swappable storage medium during the startup process.

boot-loader 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 file system management in 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 file system management in 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.

 

NOTE: The system will verify the digital signatures of the specified images before it copies them to each MPU. If the digital signature verification fails, the system will not copy the images to the MPUs and you will receive a digital signature verification failure message.

 

Examples

# (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:/blade4fwm9k-cmw710-boot-a0002.bin already exists on slot 5.

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

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

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

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

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

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

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

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

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

# (In standalone mode.) Specify slot1.1#flash:/blade4fwm9k-cmw710-boot-a0002.bin and slot1.1#flash:/blade4fwm9k-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:/blade4fwm9k-cmw710-boot-a0002.bin system slot1.1#cfa0:/blade4fwm9k-cmw710-system-a0002.bin

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

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

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

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

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

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

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

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

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

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

Related commands

display boot-loader blade

boot-loader file

Use boot-loader file to specify startup image files.

Syntax

In standalone mode:

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

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

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 file system management in 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 file system management in 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 security card. (In standalone mode.)  

chassis chassis-number slot slot-number: Specifies an MPU in the IRF fabric. The chassis-number argument represents the IRF member ID of the device that holds the MPU. The slot-number argument represents the slot number of the MPU. (In IRF mode.)

cpu cpu-number: Specifies the CPU number of the security engine on the specified security 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.

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.

Incremental patches cannot be installed by using the boot-loader file command.

 

NOTE: The system will verify the digital signature of the specified images before it updates the startup image list with the specified images. If the digital signature verification fails, the system will not update the startup image list and you will receive a digital signature verification failure message.

 

Examples

# (In standalone mode.) Specify flash:/all.ipe as the main startup image file for slot 1.

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

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

H3C SecPath M9006 images in IPE:

  boot.bin

  system.bin

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

Add images to slot 1.

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

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

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

Decompressing file boot.bin to flash:/boot.bin........................Done.

Decompressing file system.bin to flash:/system.bin...............................Done.

Verifying the file flash:/boot.bin on slot 1...Done.

Verifying the file flash:/system.bin on slot 1.............Done.

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

# (In standalone mode.) Specify flash:/all.ipe as the main startup image file.

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

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

H3C SecPath M9006 images in IPE:

  Boot.bin

  System.bin

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

Add images to slot 1.

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

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

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

Decompressing file Boot.bin to flash:/Boot.bin........................Done.

Decompressing file System.bin to flash:/System.bin...............................Done.

Verifying the file flash:/boot.bin on slot 1...Done.

Verifying the file flash:/system.bin on slot 1.............Done.

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

File flash:/boot.bin already exists on slot 0.

Do you want to overwrite the file?

 Y: Overwrite the file.

 N: Not overwrite the file.

 A: From now on, overwrite or not overwrite without prompt.

Please make a choice. [Y/N/A]:a

What type of overwrite operation do you want to perform?

  Y: Overwrite without prompt.

  N: Not overwrite or display prompt.

  Q: Return to the previous step.

Please make a choice. [Y/N/Q]:y

An existing file will be overwritten without prompt if it has the same name as any upgrade file.

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

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

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

Decompression completed.                                                       

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

 

Related commands

boot-loader blade file

display boot-loader

boot-loader update

Use boot-loader update to synchronize startup images.

Syntax

In standalone mode:

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

In IRF mode:

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

Views

User view

Predefined user roles

network-admin

Parameters

all: Synchronizes startup images from the active MPU to the standby MPU. (In standalone mode.)

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

slot slot-number: Specifies the slot number of the standby MPU. (In standalone mode.)

chassis chassis-number slot slot-number: Specifies a standby MPU. The chassis-number argument represents the IRF member ID of the device that holds the MPU. The slot-number argument represents the slot number of the MPU. (In IRF mode.)

Usage guidelines

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

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.

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. Please do not reboot any MPU during the upgrade. Continue? [Y/N]:y

Updating. Please wait...

Verifying the file flash:/BOOT.bin on slot 1.............Done.

Verifying the file flash:/SYSTEM.bin on slot 1.....................Done.

Successfully updated the startup software images of slot 1.

Related commands

display boot-loader

bootrom backup

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

Syntax

In standalone mode:

bootrom backup slot slot-number-list [ cpu cpu-number ] [ subslot subslot-number-list ]

In IRF mode:

bootrom backup chassis chassis-number slot slot-number-list [ cpu cpu-number ] [ subslot subslot-number-list ]

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. (In standalone mode.)

chassis chassis-number: Specifies an IRF member device by its member ID. (In IRF mode.)

slot slot-number-list: Specifies a space-separated list of up to seven slot number items. An item specifies a card by its slot number 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. (In IRF mode.)

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.

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

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

In standalone mode:

bootrom restore slot slot-number-list [ cpu cpu-number ] [ subslot subslot-number-list ]

In IRF mode:

bootrom restore chassis chassis-number slot slot-number-list [ cpu cpu-number ] [ subslot subslot-number-list ]

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. (In standalone mode.)

chassis chassis-number: Specifies an IRF member device by its member ID. (In IRF mode.)

slot slot-number-list: Specifies a space-separated list of up to seven slot number items. An item specifies a card by its slot number 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. (In IRF mode.)

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.

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

# (In standalone mode.) 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

bootrom update

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

Syntax

In standalone mode:

bootrom update file file slot slot-number-list [ cpu cpu-number ] [ subslot subslot-number-list ]

In IRF mode:

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

Views

User view

Predefined user roles

network-admin

Parameters

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

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

chassis chassis-number: Specifies an IRF member device by its member ID. (In IRF mode.)

slot slot-number-list: Specifies a space-separated list of up to seven slot number items. An item specifies a card by its slot number 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. (In IRF mode.)

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.

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

 

NOTE: The system verifies a BootWare image before it loads that image to the Normal area of BootWare. If the digital signature verification fails, the system will not load the image and you will receive a digital signature verification failure message.

 

Examples

# (In standalone mode.) Use the file a.bin in the root directory of the flash memory to upgrade the BootWare image.

<Sysname> bootrom update file flash:/a.bin slot 1

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

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

Related commands

boot-loader file

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

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 [ cpu cpu-number ] ]

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. (In standalone mode.)

chassis chassis-number [ slot slot-number ]: Specifies an IRF member device or an MPU in an IRF member device. The chassis-number argument represents the IRF member ID of the device. The slot-number argument represents the slot number of the MPU on the device. If you do not specify an IRF member device, this command displays the software images on each MPU in the IRF fabric. If you specify an IRF member device without specifying an MPU, this command displays the software images on each MPU on the specified member device. (In IRF mode.)

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

Usage guidelines

This command displays both the current and startup images for the device and the security engines.

Examples

# (In standalone mode.) Display the current software images and startup software images.

<Sysname> display boot-loader

Software images on slot 1:

Current software images:

  flash:/boot.bin

  flash:/system.bin

Main startup software images:

  flash:/boot.bin

  flash:/system.bin

Backup startup software images:

  flash:/boot.bin

  flash:/system.bin

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. If the backup startup software images are not specified, this field displays None.

 

Related commands

boot-loader file

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.

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

(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: Blade3fw

  None

 

Blade model: Blade4fw

  flash:/BLADE4FWM9000S-FPGA-CMW710-BOOT-A9702P03.bin

  flash:/BLADE4FWM9000S-FPGA-CMW710-SYSTEM-A9702P03.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.

 

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

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

The following compatibility matrix shows the support of hardware platforms for this command:

 

Hardware platform	Module type	Command compatibility
M9006 M9010 M9014	Blade 4 firewall module	Yes
	Blade 5 firewall module	Yes
	NAT module	Yes
M9010-GM	Encryption module	Yes
M9016-V	Blade 5 firewall module	Yes
M9008-S M9012-S	Blade 4 firewall module	No
	Intrusion prevention service (IPS) module	No
	Video network gateway module	No
M9008-S-6GW	IPv6 module	No
M9008-S-V	Blade 4 firewall module	No
M9000-AI-E4 M9000-AI-E8 M9000-AI-E16	Blade 5 firewall module	Yes
M9000-X06 M9000-X10	Blade 6 firewall module	Yes

‌

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

CAUTION: Use the undo version auto-update enable and version check ignore commands with caution. Configured with these two commands, the system will not 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. This might cause the device to malfunction.

 

This command is available in standalone mode.

To make sure the standby MPU always runs the same software images as the active MPU, configure both the version auto-update enable command and the undo version check ignore command.

The startup software version check feature examines the standby MPU's startup software images for version inconsistency with the active MPU's current software images at startup. If their software versions are different, the standby MPU copies the current software images of the active MPU, specifies them as main startup software images, and reboots with these images.

To ensure a successful synchronization in a multiuser environment, make sure no one reboots or swaps MPUs during the software synchronization process. You can configure the information center to output the synchronization status to configuration terminals (see Network Management and Monitoring Configuration Guide).

Examples

# Enable software auto-update for the standby MPU.

<Sysname> system-view

[Sysname] version auto-update enable

Related commands

version check ignore

version check ignore

Use version check ignore to disable startup software version check for the standby MPU at startup.

Use undo version check ignore to enable this feature.

Syntax

version check ignore

undo version check ignore

The following compatibility matrix shows the support of hardware platforms for this command:

 

Hardware platform	Module type	Command compatibility
M9006 M9010 M9014	Blade 4 firewall module	Yes
	Blade 5 firewall module	Yes
	NAT module	Yes
M9010-GM	Encryption module	Yes
M9016-V	Blade 5 firewall module	Yes
M9008-S M9012-S	Blade 4 firewall module	No
	Intrusion prevention service (IPS) module	No
	Video network gateway module	No
M9008-S-6GW	IPv6 module	No
M9008-S-V	Blade 4 firewall module	No
M9000-AI-E4 M9000-AI-E8 M9000-AI-E16	Blade 5 firewall module	Yes
M9000-X06 M9000-X10	Blade 6 firewall module	Yes

‌

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

CAUTION: To avoid anomalies, do not disable startup software version check for the standby MPU unless for software upgrade. The device might malfunction if the standby MPU starts up with a different software version than the active MPU.

 

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.

If you enable startup software version check for the standby MPU, the system will prevent the standby MPU from starting up with a different software version than the active MPU.

To make sure 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