Contents

Software upgrade commands· 1

boot-loader file· 1

display boot-loader 2

display version· 4

 

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

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 cloud cluster member ID of a member device.

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

Related commands

display boot-loader

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 a cloud cluster member device. If you do not specify a member device, this command displays the software images on each cloud cluster member device.

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 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.061, Alpha 1029

Copyright (c) 2004-2023 New H3C Technologies Co., Ltd. All rights reserved.

H3C WX3510X uptime is 0 weeks, 6 days, 20 hours, 37 minutes

Last reboot reason : User soft reboot

 

Boot image: flash:/boot.bin

Boot image version: 9.1.061, Alpha 1029

  Compiled Aug 07 2023 14:00:00

System image: flash:/system.bin

System image version: 9.1.061, Alpha 1029

  Compiled Aug 07 2023 14:00:00

 

...

Table 2 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. ·     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. ·     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. ·     Critical process abnormality reboot—The reboot was caused by critical process exceptions.

‌