Software upgrade commands 1

boot-loader file· 1

boot-loader update· 2

bootrom update· 3

display boot-loader 4

warm-reboot 5

 

The switch can start up from the built-in flash memory or a removable USB disk. H3C recommends that you store the startup images in the built-in flash memory. If you store the startup images on a USB disk, do not remove the USB disk before the startup is complete.

boot-loader file

Use boot-loader file to specify startup software image files.

Syntax

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 }

Views

User view

Predefined user roles

network-admin

Parameters

boot boot-package: Specifies the file path of a .bin boot image file, a case-insensitive string. The file must be stored in the root directory of a storage medium in the system. The maximum length is 63 characters for the storage-medium:/base-filename.bin segments of the file path. This length limit does not include the IRF 2 member ID or slot number in front of the storage medium segment. For more information about specifying a file path, see "Managing the file system."

system system-package: Specifies the file path of a .bin system image file, a case-insensitive string. The file must be stored in the root directory of a storage medium in the system. The maximum length is 63 characters for the storage-medium:/base-filename.bin segments of the file path. This length limit does not include the IRF 2 member ID or slot number information in front of the storage medium segment. For more information about specifying a file path, see "Managing the file system."

feature feature-package: Specifies a space-separated list of up to 30 .bin feature image file paths. The file paths are case insensitive. The files must be stored in the root directory of a storage medium in the system. The maximum length is 63 characters for the storage-medium:/base-filename.bin segments of a file path. This length limit does not include the IRF 2 member ID or slot number information in front of the storage medium segment. For more information about specifying a file path, see "Managing the file system."

ipe-filename: Specifies the file path of an .ipe image package file, a case-insensitive string. The file must be stored in the root directory of a storage medium in the system. The maximum length is 63 characters for the storage-medium:/base-filename.ipe segments of the file path. This length limit does not include the IRF 2 member ID or slot number information in front of the storage medium segment.

all: Specifies startup images for all devices. If you specify this keyword, the system copies device-specific images automatically to the root directory of the storage medium on each device. For a successful upgrade, make sure the specified files include the upgrade images for all devices.

slot slot-number: Specifies the IRF 2 member ID of the device for which the startup images are specified.

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

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

Usage guidelines

Use this command to upgrade the startup software images on each member device. To upgrade only the subordinate devices, you can also use the boot-loader update command.

Before specifying a startup software image file, save the upgrade file to the root directory of a storage medium on any one of the IRF 2 member devices. The system automatically copies the upgrade file to the flash memory on the IRF 2 member device you are upgrading, and sets images in the file as startup images. If a file with the same name as the upgrade file already exists, you must choose whether to overwrite the existing file.

When an .ipe image package file is used for upgrade, you must choose whether to delete the file after the system decompresses the file.

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

Examples

# Specify flash:/all.ipe as the backup startup image file for IRF 2 member device 1.

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

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

all images in IPE:

  boot.bin

  system.bin

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

Do you want to overwrite files without prompt? [Y/N]:y

Specify the backup startup software images for Switch.

Add images to slot 1.

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

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

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 backup startup

software images at the next reboot on slot 1.

Decompression completed.

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

Related commands

display boot-loader

boot-loader update

Use boot-loader update to synchronize startup images from the master to a subordinate device.

Syntax

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

Views

User view

Predefined user roles

network-admin

Parameters

all: Upgrades all the subordinate devices.

slot: Specifies the IRF 2 member ID of a subordinate device.

Usage guidelines

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

The startup images synchronized to the subordinate device are set as main startup images, regardless of whether the source startup images are main or backup.

If the master device has started up with main startup images, its main startup images are synchronized to the subordinate device, regardless of whether any main startup image has been respecified.

If the master device has started up with backup startup images, its backup startup images are synchronized to the subordinate device, regardless of whether any backup startup image has been respecified.

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

If an ISSU patch installation or software upgrade has been performed, use the install commit command to update the set of main startup images on the master before software synchronization for startup image consistency between the master and the subordinate device.

Examples

# Synchronize startup images from the master device to subordinate device 2.

<Sysname> boot-loader update slot 2

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

Updating. Please wait...

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

Done.

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

Done.

Successfully updated the startup software images of slot 2.

Related commands

·     display boot-loader

·     install commit

bootrom update

Use bootrom update to load the Boot ROM image in the flash to the Normal area of Boot ROM.

Syntax

bootrom update file file-url slot slot-number-list

Views

User view

Predefined user roles

network-admin

Parameters

file file-url: Specifies the file that contains the Boot ROM image in the flash. The file-url 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 IRF 2 member ID items. For each item, you can specify an IRF 2 member device or a range of IRF 2 member devices.

·     Specify an IRF 2 member device by its member ID.

·     Specify a range of IRF 2 member devices in the form of start-member-id to end-member-id.

For example, the list can be slot 0 to 2 3.

Usage guidelines

If a software upgrade requires upgrading the Boot ROM image, you can use this command to preload the new Boot ROM image to the Boot ROM before upgrading Comware images. This command helps shorten the subsequent upgrade time, reducing the risk of upgrade failure caused by unexpected electricity failure.

To complete the upgrade, reboot the device.

To save space, you can delete the Boot ROM image in the flash after completing the Boot ROM image upgrade.

Examples

# Use the file a.bin to upgrade the Boot ROM image.

<Sysname> bootrom update file a.bin

   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

display boot-loader [ slot slot-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

slot slot-number: Specifies the member ID of an IRF 2 member device. If you do not specify a member device, the command displays the software images on each IRF 2 member device.

Examples

# Display current software images and startup software images.

<Sysname> display boot-loader

Software images on slot 0:

Current software images:

  flash:/simware-cmw710-boot-a1701.bin

  flash:/simware-cmw710-system-a1701.bin

Main startup software images:

  flash:/simware-cmw710-boot-a1701.bin

  flash:/simware-cmw710-system-a1701.bin

  flash:/simware-cmw710-ssh-a1701.bin

Backup startup software images:

  flash:/simware-cmw710-boot-a1701.bin

  flash:/simware-cmw710-system-a1701.bin

Table 1 Command output

Field	Description
Software images on slot slot-number	This field displays the Comware images on the IRF 2 member device. The slot number represents the device's member ID.
Current software images	Comware images that have been loaded.
Main startup software images	Main Comware images for the next startup.
Backup startup software images	Backup Comware images for the next startup.

 

Related commands

boot-loader file

warm-reboot

Use warm-reboot to upgrade Comware software through a warm reboot.

Syntax

warm-reboot [ file { boot boot-package | system system-package | feature feature-package &<1-30> } ]

warm-reboot [ file ipe ipe-filename ]

Views

User view

Predefined user roles

network-admin

Parameters

boot boot-package: Specifies a .bin boot image file, a case-insensitive string of up to 63 characters. The file path specified for the boot-package argument uses the storage-medium:/base-filename.bin format, for example, flash:/startup-boot.bin.

system system-package: Specifies a .bin system image file, a case-insensitive string of up to 63 characters. The file path specified for the system-package argument uses the storage-medium:/base-filename.bin format, for example, flash:/startup-system.bin.

feature feature-package: Specifies a space-separated list of up to 30 .bin feature image files. Each feature image file name must be a case-insensitive string of up to 63 characters. In addition, the file names must use the storage-medium:/base-filename.bin format, for example, flash:/startup-a.bin.

ipe-filename: Specifies an .ipe Comware image file name, a case-insensitive of up to 63 characters. The file path must use the storage-medium:/base-filename.ipe format, for example, flash:/startup.ipe.

Usage guidelines

If you do not specify upgrade software images, the switch reboots without upgrading software.

If you specify upgrade software images, this command adds the specified images to the main startup software image list and performs a warm reboot.

Use this command in the following situations:

·     Upgrade Comware images without upgrading the Boot ROM. The warm-reboot method directly loads and executes Comware software images in the memory instead of booting the Comware images from the Boot ROM. Compared to upgrading software through the boot-loader command, warm reboot reduces the service downtime.

·     Upgrade only a specific image, for example, upgrade only the system image. When you upgrade feature images through warm reboot, you only need to specify upgrade images for features you are upgrading. The warm-reboot method replaces the old images for the specific features instead of overwriting the entire software list as does the boot-loader command.

Before you specify startup software image files, save the upgrade files to the root directory of the flash memory. If the flash memory is partitioned, save the files to the root directory of the first partition.

This command can upgrade software only between compatible software versions. When the system executes the command, it verifies the compatibility between the current and upgrade software versions. If the software versions are incompatible, you must use the reboot method to upgrade the software from the CLI. For more information about the reboot method for software upgrade, see the fundamental configuration guide for the switch.

Examples

# Perform a warm reboot to upgrade the feature image.

<Sysname> warm-reboot file feature flash:/feature.bin

This operation will delete the rollback point information for the previous upgrade and maybe get unsaved configuration lost. Continue? [Y/N]:Y

Upgrade summary according to following table:

 

flash:/feature.bin

  Running Version             New Version

  Alpha 7122                  Alpha 7123

 

  Slot                        Upgrade Way

  1                           Warm Reboot

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

Table 2 Command output

Field	Description
Running Version	Version of the current software images.
New Version	Version of the upgrade software images.
Slot	Device ID. It is fixed at 1.