Contents

Software upgrade commands· 1

boot-loader file· 1

boot-loader pex file (IRF3.1) 3

boot-loader update· 4

bootrom update· 6

display boot-loader 6

version auto-update enable· 8

version check ignore· 8

 

Software upgrade commands

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

In standalone mode:

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

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

In IRF mode:

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

boot-loader file ipe-filename [ patch filename&<1-16> ] { 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.

patch: Specifies a space-separated list of up to 16 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 or security card. (In standalone mode.)

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

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

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

Usage guidelines

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.

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

display boot-loader

boot-loader pex file (IRF3.1)

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

Syntax

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.

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

Examples

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

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 to a slot.

<Sysname> boot-loader update slot 1

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 1. Please wait...

Done.

Setting copied images as main startup software images for 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.

Successfully updated the startup software images of slot 1.

Related commands

display boot-loader

install commit

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

In IRF mode:

bootrom update file file chassis chassis-number 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.

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

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.

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

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

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