Contents

Software upgrade commands· 1

boot-loader file· 1

boot-loader update· 5

display boot-loader 6

version auto-update enable· 8

version check ignore· 8

 

Software upgrade commands

The device starts up from the default file system. For SR6600 routers, the default file system can be the built-in flash memory (factory default) or a USB disk. For SR6600-X routers, the default file system can be the built-in CF card (factory default) or a USB disk.

As a best practice, store the startup images in the factory-default file system.

If the device is starting up from a USB disk, do not remove the USB disk during startup.

The device starts up from the default file system. The default file system can be the built-in flash memory (factory default) or a CF card.

As a best practice, store the startup images in the factory-default file system.

If the device is starting up from a CF card, do not remove the CF card during startup.

boot-loader file

Use boot-loader file to specify startup image files.

Syntax

In standalone mode:

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

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

feature feature-package: Specifies a space-separated list of up to 30 .bin feature image files. Specify each .bin file in the filesystemname/filename.bin format. The files must be stored in the root directory of a file system on the device. The value string excluding the file system location section (if any) 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. The filesystemname:/filename.ipe section 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. You can use this option to upgrade all hardware components that run the same images.

slot slot-number: Specifies an MPU by its slot number. (In standalone mode.)

chassis chassis-number slot slot-number: Specifies an MPU on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the MPU. (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

To avoid configuration failure, make sure no other users are configuring or managing the device.

Before you specify startup image files, perform the following tasks:

·     Save the upgrade files to the root directory of a file system on the active MPU (in standalone mode) or global active MPU (in IRF mode)..

·     Register and activate a license for each image that requires a license. If a license-based software image does not have 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.

If the upgrade images are not stored on the hardware in the slot you specified to upgrade, the system automatically copies the images to that hardware. The destination directory is the root directory of the default storage medium on the hardware. 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.

The boot-loader file command overwrites the entire 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.

Examples

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

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

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

H3C SR6608 images in IPE:

  boot.bin

  system.bin

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

Add images to slot 0.

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

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

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

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

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

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

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

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

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

H3C SR6608 images in IPE:

  boot.bin

  system.bin

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

Add images to slot 1.

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

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

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

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

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

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

File flash:/boot.bin already exists on slot 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

# (In IRF mode.) Specify flash:/all.ipe as the main startup image file for the MPU in slot 0 on IRF member device 1.

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

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

H3C SR6608 images in IPE:

  boot.bin

  system.bin

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

Add images to chassis 1 slot 0.

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

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

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

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

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

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

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

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

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

H3C SR6608 images in IPE:

  boot.bin

  system.bin

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

Add images to chassis 2 slot 1.

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

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

File flash:/Devkit.bin already exists on chassis 2 slot 1.

File flash:/Manufacture.bin already exists on chassis 2 slot 1.

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

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

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

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

File flash:/boot.bin already exists on chassis 2 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.

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

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

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

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

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

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

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

Decompression completed.

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

Related commands

display boot-loader

boot-loader update

In standalone mode, use boot-loader update to synchronize startup images from the active MPU to the standby MPU.

In IRF mode, use boot-loader update to synchronize startup images from the global active MPU to a global standby MPU.

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: Upgrades the standby MPU. (In standalone mode.)

all: Upgrades all global 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 standby MPU. The slot-number argument represents the slot number of the standby MPU. (In IRF mode.)

Usage guidelines

In standalone mode:

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

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

The images used for synchronization are in the main or backup startup software images list instead of the current software images list (see the display boot-loader command).

·     The main images list is used if the active MPU started up with the main startup images.

·     The backup image list is used if the active MPU started up with the main startup images.

The startup images synchronized to the 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 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.

In IRF mode:

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

·     The backup image list is used if the or global active MPU started up with the main 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 global active MPU before software synchronization. This command ensures startup image consistency between the global active MPU and standby MPUs.

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

Examples

# (In standalone mode.) Synchronize startup images from the active MPU to the standby MPU (in slot 1).

<Sysname> boot-loader update slot 1

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

Updating. Please wait...

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

Done.

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

Done.

Successfully updated the startup software images of slot 1.

# (In IRF mode.) Synchronize startup images from the global active MPU to the MPU in slot 1 on IRF member device 1.

<Sysname> boot-loader update chassis 1 slot 1

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

Updating. Please wait...

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

Done.

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

Done.

Successfully updated the startup software images of chassis 1 slot 1.

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 an MPU by its slot number. 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 MPU in an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the MPU. If you do not specify an MPU, this command displays the software images on each MPU in the IRF fabric. (In IRF mode.)

Examples

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

<Sysname> display boot-loader

Software images on slot 0:

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

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

<Sysname> display boot-loader

Software images on chassis 1 slot 0:

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
Software images on slot slot-number	In standalone mode, this field displays the Comware images on the MPU in the specified slot.
Software images on chassis chassis-id slot slot-number	In IRF mode, this field displays the Comware images on an MPU.
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.

As a best practice, use ISSU instead of this command to upgrade software, if possible. The startup software version check feature might fail to work because the software versions of the MPUs are incompatible.

To avoid anomalies, do not disable startup software version check for the standby MPU unless for software upgrade.

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

Examples

# Enable startup software version check for the standby MPU.

<Sysname> system-view

[Sysname] undo version check ignore

Related commands

version auto-update enable