Contents

Software upgrade commands· 1

boot-loader file· 1

boot-loader update· 3

display boot-loader 4

firmware update· 6

version auto-update enable· 7

version check ignore· 7

 

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 file

Use boot-loader file to specify startup image files.

Syntax

In standalone mode:

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

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

In IRF mode:

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

boot-loader file ipe-filename { all | chassis chassis-number slot slot-number } { backup | main }

Views

User view

Predefined user roles

network-admin

Parameters

boot: Specifies a boot image file.

system: Specifies a system image file.

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

filename: Specifies a .bin file in the filesystemname/filename.bin format. The file must be stored in the root directory of a file system on the device. Excluding the file system location section (if any), the value string can have a maximum of 63 characters. For more information about specifying a file, see 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.

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.

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.

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

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 SR6608 images in IPE:

  boot.bin

  system.bin

This command will set the main startup software images. Please do not reboot any MPU during the upgrade. Continue? [Y/N]:Y

Add images to slot 0.

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

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

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

Verifying the file flash:/system.bin on slot 0............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.

You are recommended to delete the .ipe file after you set startup software images for all slots.

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

# (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 SR6608 images in IPE:

  boot.bin

  system.bin

This command will set the main startup software images. Please do not reboot any

 MPU during the upgrade. 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 so

ftware 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]:

File flash:/system.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]:

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

Verifying the file flash:/system.bin on slot 0......

......Done.

The images that have passed all examinations will be used as the main startup so

ftware images at the next reboot on slot 0.

Decompression completed.

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

Related commands

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.

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 0

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

Before pressing ENTER you must choose 'YES' or 'NO'[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 slo 0. Please wait...Done.

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

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

Successfully updated the startup software images of slot 0.

Related commands

display boot-loader

install commit

display boot-loader

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

Syntax

In standalone mode:

display boot-loader [ slot slot-number ]

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

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

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

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.

 

Related commands

boot-loader file

firmware update

Use firmware update to upgrade the CPLD firmware.

Syntax

In standalone mode:

firmware update slot slot-number [ subslot subslot-number ] cpld cpld-number file filename

In IRF mode:

firmware update chassis chassis-number slot slot-number [ subslot subslot-number ] cpld cpld-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. (In IRF mode.)

slot slot-number: Specifies a card by its slot number. (In standalone mode.)

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.

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

Examples

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

version auto-update enable

Use version auto-update enable to enable software synchronization from active MPU to standby MPU at startup.

Use undo version auto-update enable to disable this feature.

Syntax

version auto-update enable

undo version auto-update enable

Default

Software synchronization from active MPU to standby MPU is enabled. If software inconsistency is detected at startup, the standby MPU loads the current software images of the active MPU.

Views

System view

Predefined user roles

network-admin

Usage guidelines

This command is available in standalone mode.

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

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

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

Examples

# Enable software auto-update for the standby MPU.

<Sysname> system-view

[Sysname] version auto-update enable

Related commands

version check ignore

version check ignore

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

Use undo version check ignore to enable this feature.

Syntax

version check ignore

undo version check ignore

Default

The startup software images on the standby MPU are checked for version inconsistency with the current software images on the active MPU.

Views

System view

Predefined user roles

network-admin

Usage guidelines

This command is available in standalone mode.

When the standby MPU starts up, this command disables the system to examine the standby MPU's startup software images for version inconsistency with the active MPU's current software images. The standby MPU can start up with a different software version than the active MPU.

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