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

boot-loader file

Use boot-loader file to specify startup image files.

Syntax

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

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

Views

User view

Predefined user roles

network-admin

Parameters

boot: Specifies a boot image file.

system: Specifies a system image file.

feature: Specifies a space-separated list of up to 30 feature image files.

patch: Specifies a space-separated list of up to 30 incremental patch image files or 16 non-incremental patch image files. Because the boot, system, and feature images each can have one non-incremental patch image file, you can specify a maximum of 16 non-incremental patch image files.

filename: Specifies a .bin file in the filesystemname/filename.bin format. The file must be stored in the root directory of a file system on the device. Excluding the file system location section (if any), the value string can have a maximum of 63 characters. For more information about specifying a file, see Fundamentals Configuration Guide.

ipe-filename: Specifies an .ipe image package file in the filesystemname/filename.ipe format. The file must be stored in the root directory of a file system on the device. Excluding the file system location section (if any), the value string can have a maximum of 63 characters. For more information about specifying a file, see Fundamentals Configuration Guide.

all: Specifies all hardware components to which the specified images apply.

slot slot-number: Specifies the slot number of an MPU

backup: Specifies the files as backup startup image files. Backup images are used only when main images are not available.

main: Specifies the files as main startup image files. The device always first attempts to start up with main startup files.

Usage guidelines

The boot-loader file command overwrites the entire startup image list. To add new startup feature images, specify all feature image files in the old startup image list, including feature image files. The new startup image list will contain only the feature image files that are specified in the command.

To load the specified startup software images, you must reboot the system.

If the upgrade images are not found in the file system on the slot specified to upgrade, the system automatically copies the images to that file system. The destination directory is the root directory of the file system. If the destination root directory already contains a startup image with the same name as an upgrade image, you must choose whether to overwrite the image.

NOTE:

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

Examples

# Specify flash:/all.ipe as the main startup image file for slot 1.

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

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

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

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

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

# Specify flash:/all.ipe as the main startup image file for slot 1, without immediately decompressing the IPE file.

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

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

XX images in IPE:

boot.bin

system.bin

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

File flash:/all.ipe already exists on slot 1.

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

Copying file flash:/all.ipe to slot1#flash:/all.ipe...Done.

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

# Specify flash:/all.ipe as the main startup image file, without immediately decompressing the IPE file.

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

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

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

File flash:/all.ipe 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.

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

Related commands

display boot-loader

boot-loader update

Use boot-loader update to synchronize startup images.

Syntax

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

Views

User view

Predefined user roles

network-admin

Parameters

all: Synchronizes startup images from the active MPU to the standby MPU.

slot slot-number: Specifies the slot number of the standby MPU.

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 started up with the main startup images.

· The backup image list is used if the active MPU 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 has been installed on the active MPU, use the install commit command to update the main startup images on the active MPU before software synchronization. This command ensures startup image consistency between the active MPU and the standby MPU.

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

Examples

# Synchronize startup images to a slot.

<Sysname> boot-loader update slot 2

This command will update the specified standby MPU. Continue? [Y/N]:y

Updating. Please wait...

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

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

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

Done.

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

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

Done.

Successfully updated the startup software images of slot 2.

Related commands

display boot-loader

install commit

bootrom backup

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

Syntax

bootrom backup slot slot-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.

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

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

bootrom restore slot slot-number-list

Views

User view

Predefined user roles

network-admin

Parameters

Examples

# 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

bootrom update file file slot slot-number-list

Views

User view

Predefined user roles

network-admin

Parameters

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

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

# 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

display boot-loader [ slot slot-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

slot slot-number: Specifies the slot number of an MPU. If you do not specify an MPU, this command displays the software images on each MPU.

Examples

# Display the current software images and startup software images.

<Sysname> display boot-loader

Software images on slot 1:

Current software images:

flash:/boot.bin

flash:/system.bin

Main startup software images:

flash:/boot.bin

flash:/system.bin

Backup startup software images:

flash:/boot.bin

flash:/system.bin

# Display the current software images and startup software images.

<Sysname> display boot-loader

Software images on slot 1:

Current software images:

Image Version

flash:/boot.bin Release 0053

flash:/system.bin Release 0053

Main startup software images:

Image Version

flash:/boot.bin Release 0054

flash:/system.bin Release 0054

Backup startup software images:

Image Version

flash:/b-boot.bin --

flash:/b-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.
Image	Image name.
Version	Image version. If an image is corrupted or deleted, this field displays two hyphens (--).
Backup startup software images	Backup Comware images for the next startup.

Related commands

boot-loader file

display install active

Use display install active to display active software images.

Syntax

display install active [ slot slot-number ] [ verbose ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays information for all cards.

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:/feature1.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: S12500

Service name: boot

Platform version: 9.1.043

Product version: Test 0001015

Supported board: mpu

[Component]

Component: boot

Description: boot package

flash:/system.bin

[Package]

Vendor: H3C

Product: S12500

Service name: system

Platform version: 9.1.043

Product version: Test 0001015

Supported board: mpu

[Component]

Component: system

Description: system package

flash:/feature1.bin

[Package]

Vendor: H3C

Product: S12500

Service name: test

Platform version: 9.1.043

Product version: Test 0001015

Supported board: mpu

[Component]

Component: test

Description: test package

Table 2 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: · mpu—MPU. · lpu—Service card. · sfc—Switching fabric module.
[Component]	Information about components included in the image file.
Component	Component name.
Description	Component description.

‌

Related commands

install activate

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 a card by its slot number. If you do not specify a card, this command displays information for all cards.

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

Usage guidelines

Some install commands modify the current software image list but do not modify the main startup image list. For the software image changes to take effect after a reboot, you must execute the install commit command to update the main startup image list with the image changes. You can use the display install committed command to verify the operation results.

Both the install commit and boot-loader file commands modify the main startup software image list.

Examples

# Display brief information about main startup software images.

<Sysname> display install committed

Committed packages on slot 1:

flash:/boot.bin

flash:/system.bin

flash:/feature1.bin

# Display detailed information about main startup software images.

<Sysname> display install committed verbose

Committed packages on slot 1:

flash:/boot.bin

[Package]

Vendor: H3C

Product: S12500

Service name: boot

Platform version: 9.1.043

Product version: Test 0001015

Supported board: mpu

[Component]

Component: boot

Description: boot package

flash:/system.bin

[Package]

Vendor: H3C

Product: S12500

Service name: system

Platform version: 9.1.043

Product version: Test 0001015

Supported board: mpu

[Component]

Component: system

Description: system package

flash:/feature1.bin

[Package]

Vendor: H3C

Product: S12500

Service name: feature1

Platform version: 9.1.043

Product version: Test 0001015

Supported board: mpu

[Component]

Component: feature1

Description: feature1 package

For information about the command output, see Table 2.

display version

Use display version to display system version information.

Syntax

display version

Views

Any view

Predefined user roles

network-admin

network-operator

Examples

# Display system version information.

<Sysname> display version

H3C Comware Software, Version 9.1.055, Demo 5202P14

H3C S12508R uptime is 0 weeks, 1 day, 20 hours, 2 minutes

Last reboot reason : Cold reboot

Boot image: flash:/S12500R-CMW910-BOOT-D5202P14.bin

Boot image version: 9.1.055, Demo 5202P14

Compiled Aug 30 2022 14:00:00

System image: flash:/S12500R-CMW910-SYSTEM-D5202P14.bin

System image version: 9.1.055, Demo 5202P14

Compiled Aug 30 2022 14:00:00

...

Table 3 Command output

Field	Description
Last reboot reason	Reason for the last reboot: · User reboot—The reboot was manually initiated from a user interface, such as the CLI or SNMP. · Cold reboot—The reboot was caused by a power cycle. · Deep cold reboot—The reboot was caused by a system-wide power cycle. · Kernel abnormality reboot—The reboot was caused by kernel exceptions. · DeadLoop reboot—The reboot was caused by a kernel thread dead loop. · DEV HandShake reboot—The reboot was caused by a device management handshake failure. · SlaveSwitch reboot—The reboot was caused by a master/subordinate switchover. · Auto Update reboot—The reboot was caused by an automatic software upgrade. · Memory exhaust reboot—The reboot was caused by a card-memory-exhausted event.

Field

Description

Last reboot reason

Reason for the last reboot:

· User reboot—The reboot was manually initiated from a user interface, such as the CLI or SNMP.

· Cold reboot—The reboot was caused by a power cycle.

· Deep cold reboot—The reboot was caused by a system-wide power cycle.

· Kernel abnormality reboot—The reboot was caused by kernel exceptions.

· DeadLoop reboot—The reboot was caused by a kernel thread dead loop.

· DEV HandShake reboot—The reboot was caused by a device management handshake failure.

· SlaveSwitch reboot—The reboot was caused by a master/subordinate switchover.

· Auto Update reboot—The reboot was caused by an automatic software upgrade.

· Memory exhaust reboot—The reboot was caused by a card-memory-exhausted event.

‌

display version-update-record

Use display version-update-record to display startup software image upgrade records.

Syntax

display version-update-record

Views

Any view

Predefined user roles

network-admin

network-operator

Usage guidelines

The device records its current startup software version information whenever it starts up, and records all software version update information. Such information can survive reboots.

Examples

# Display the startup software image upgrade records.

<Sysname> display version-update-record

Record 1 (updated on Jan 18 2020 at 06:23:54):

*Name : comware-cmw710-boot.bin

Version : 7.1.070 Test 0001

Compile time: Jan 25 2020 15:52:43

*Name : comware-cmw710-system.bin

Version : 7.1.070 Test 0001

Compile time: Jan 25 2020 15:52:43

Table 4 Command output

Field	Description
Record n (updated on Jan 18 2020 at 06:23:54)	Number of the startup software image upgrade record. Record 1 is the most recent record. The time in parentheses is UTC time.
Name	Software image file name.
*	The software image version changed during the upgrade.

‌

Related commands

reset version-update-record

install activate

Use install activate to activate feature or patch images.

Syntax

install activate { boot filename | system filename | feature filename&<1-30> } * slot slot-number [ test ]

install activate patch filename { all | slot slot-number }

Views

User view

Predefined user roles

network-admin

Parameters

boot: Specifies a boot image file.

system: Specifies a system image file.

feature: Specifies a space-separated list of up to 30 feature image files.

patch: Specifies a patch image file. You can specify only one patch image file for the command at a time. However, you can execute the command multiple times to activate multiple patch image files.

all: Specifies all cards.

slot slot-number: Specifies a card by its slot number.

test: Only identifies the ISSU method to be used for the upgrade. If you do not specify this keyword, the command activates the specified software images.

Usage guidelines

This command activates images and adds the images to the current image list. Images run in memory immediately after they are activated. However, only images activated by using the install activate patch filename all command still run in memory after a reboot. For other images to take effect after a reboot, you must commit the software change by using the install commit command.

If the image file is not on the card to be upgraded, the install activate command automatically copies the image file to the card.

If you specify the active MPU for the slot slot-number option, the command takes effect on the active MPU and all LPUs. If you specify the standby MPU for the slot slot-number option, the command takes effect only on the standby MPU.

Examples

# Identify the ISSU method for feature upgrade with feature1.bin on the standby MPU (in slot 1) and the upgrade impact.

<Sysname> install activate feature flash:/feature1.bin slot 1 test

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

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

Upgrade summary according to following table:

flash:/feature1.bin

Running Version New Version

Test 0001015 Test 0001016

Slot Upgrade Way

1 Service Upgrade

Influenced service according to following table:

flash:/feature1.bin

Feature1

The output shows that a service upgrade is recommended. The Feature1 module will be rebooted during the upgrade.

# Activate the system image in system.bin and the feature images in feature1.bin on the standby MPU (in slot 1).

<Sysname> install activate system flash:/system.bin feature flash:/feature1.bin slot 1

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

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

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

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

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

Upgrade summary according to following table:

flash:/system.bin

Running Version New Version

Test 0001015 Test 0001016

flash:/feature1.bin

Running Version New Version

None Test 0001016

Slot Upgrade Way

1 Service Upgrade

Upgrading software images to compatible versions. Continue? [Y/N]:y

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

Table 5 Command output

Field	Description
Verifying the file	The system was verifying the validity of the file.
Upgrade summary according to following table	Upgrade summary.
Running Version	Version number of the running software.
New Version	Version number of the new software.
Upgrade Way	ISSU methods: · Service Upgrade. · File Upgrade. · Reboot. This field is displayed only for an upgrade to a compatible version. For more information about ISSU methods, see Fundamentals Configuration Guide.
Influenced service according to following table	Services influenced by the upgrade.

Related commands

display install active

install commit

install deactivate

install commit

Use install commit to commit software changes.

Syntax

install commit

Views

User view

Predefined user roles

network-admin

Usage guidelines

This command adds the patch image file to the startup image list that the device used at startup.

· If the device used the main startup software image list at startup, this command adds the patch image file to the main startup software image list.

· If the device used the backup startup software image list at startup, this command adds the patch image file to the backup startup software image list.

Both the install commit and boot-loader file commands modify the main startup software image list. To modify the backup startup image list or add inactive images as main startup images, however, you must use the boot-loader file command.

For more information about main and backup startup software images, see Fundamentals Configuration Guide.

Examples

# Commit software changes.

<Sysname> install commit

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

Related commands

install activate

install deactivate

Use install deactivate to deactivate feature or patch images.

Syntax

install deactivate feature filename&<1-30> slot slot-number

install deactivate patch filename { all | slot slot-number }

Views

User view

Predefined user roles

network-admin

Parameters

feature: Specifies a space-separated list of up to 30 feature image files.

patch: Specifies a patch image file. You can specify only one patch image file for the command at a time. However, you can execute the command multiple times to deactivate multiple patch image files.

all: Specifies all cards.

slot slot-number: Specifies a card by its slot number.

Usage guidelines

You can deactivate only active feature and patch images.

Images stop running in memory immediately after they are deactivated. However, only patch images deactivated by using the install deactivate patch filename all command do not run after a reboot. To prevent other deactivated images from running after a reboot, you must commit the software change by using the install commit command.

Examples

# Deactivate route-patch.bin on card 1.

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

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

Related commands

display install active

reset version-update-record

Use reset version-update-record to clear startup software image upgrade records.

Syntax

reset version-update-record

Views

System view

Predefined user roles

network-admin

Examples

# Clear the startup software image upgrade records.

<Sysname> system-view

[Sysname] reset version-update-record

This command will delete all records of version update. Continue? [Y/N]:y

Related commands

display version-update-record

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

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.

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

Use version check ignore to disable startup software version check for inconsistency when the standby MPU starts up.

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

CAUTION:

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

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 on standby MPU at startup, 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 on the standby MPU at startup.

<Sysname> system-view

[Sysname] undo version check ignore

Related commands

version auto-update enable

01-Fundamentals Command Reference

boot-loader file

bootrom backup

display version-update-record

version auto-update enable

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program

Global Learning

Partner Sales Resources

Service Business

News & Events

Contact Us