Table of Contents

Related Documents

07-Software upgrade commands

Title	Size	Download
07-Software upgrade commands	151.54 KB

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> ] { backup | main }

boot-loader file ipe-filename { backup | main }

In IRF 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 }

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 IRF member ID of a member device. (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.

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.

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

Verifying the file flash:/all.ipe on the device.............Done.

H3C MSR36-10 Switch images in IPE:

boot.bin

system.bin

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

Add images to the device.

File flash:/boot.bin already exists on the device.

File flash:/system.bin already exists on the device.

Overwrite or rename the new file? [Yes/No/Rename]: R

Please input the file name (*.bin)[boot_1.bin]

(To use the recommended file name, press the Enter key):

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

Please input the file name (*.bin)[system_1.bin]

(To use the recommended file name, press the Enter key):system_backup.bin

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

Verifying the file flash:/boot_1.bin on the device...Done.

Verifying the file flash:/system_backup.bin on the device.............Done.

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

# (In standalone mode.) Specify flash:/boot.bin and flash:/system.bin as the main startup boot and system image files.

<Sysname> boot-loader file boot flash:/boot.bin system flash:/system.bin main

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

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

# (In IRF 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 MSR36-10 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 or rename the new file? [Yes/No/Rename]: 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 IRF mode.) Specify flash:/all.ipe as the main startup image file for all IRF member devices.

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

Verifying the file flash:/all.ipe on slot 1......................................Done.

H3C MSR36-10 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 or rename the new file? [Yes/No/Rename]: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 2.

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.

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

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

Decompression completed.

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

Related commands

display boot-loader

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

Syntax

In standalone mode:

display boot-loader

In IRF mode:

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

Examples

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

<Sysname> display boot-loader

Software images on the device:

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

display install active

Use display install active to display active software images.

Syntax

In standalone mode:

display install active [ verbose ]

In IRF mode:

display install active [ slot slot-number ] [ verbose ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

slot slot-number: Specifies an IRF member device by its member ID. If you do not specify an IRF member device, this command displays information for all IRF member devices. (In IRF mode.)

verbose: Displays detailed information. If you do not specify this keyword, the command displays only image names.

Examples

# (In standalone mode.) Display brief information about active software images.

<Sysname> display install active

Active packages on the device:

flash:/boot.bin

flash:/system.bin

flash:/feature1.bin

# (In IRF mode.) Display brief information about active software images.

<Sysname> display install active

Active packages on slot 1:

flash:/boot.bin

flash:/system.bin

flash:/feature1.bin

# (In standalone mode.) Display detailed information about active software images.

<Sysname> display install active verbose

Active packages on the device:

flash:/boot.bin

[Package]

Vendor: H3C

Product: MSR36

Service name: boot

Platform version: 7.1.070

Product version: Test 0001015

Supported board: MSR36-10

[Component]

Component: boot

Description: boot package

flash:/system.bin

[Package]

Vendor: H3C

Product: MSR36

Service name: system

Platform version: 7.1.070

Product version: Test 0001015

Supported board: MSR36-10

[Component]

Component: system

Description: system package

flash:/feature1.bin

[Package]

Vendor: H3C

Product: MSR36

Service name: test

Platform version: 7.1.070

Product version: Test 0001015

Supported board: MSR36-10

[Component]

Component: test

Description: test package

Table 2 Command output

Field	Description
[Package]	Detailed information about the software image.
Service name	Image type: · boot—Boot image. · boot-patch—Boot image patch. · system—System image. · system-patch—System image patch. · Any other value indicates a feature image.
Platform version	Platform software version.
Product version	Product software version.
Supported board	Device type supported by the software image.
[Component]	Information about components included in the image file.
Component	Component name.
Description	Component description.

‌

Related commands

install active

display install backup

Use display install backup to display backup startup software images.

Syntax

In standalone mode:

display install backup [ verbose ]

In IRF mode:

display install backup [ slot slot-number ] [ verbose ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

slot slot-number: Specifies an IRF member device by its member ID. If you do not specify an IRF member device, this command displays information for all IRF member devices. (In IRF mode.)

verbose: Displays detailed information. If you do not specify this keyword, the command displays only image names.

Usage guidelines

If any main image does not exist or is invalid, the system loads the backup startup software images.

You can use the boot-loader file command to modify the backup startup software image list.

Examples

# (In standalone mode.) Display brief information about backup startup software images.

<Sysname> display install backup

Backup startup software images on the device:

flash:/boot.bin

flash:/system.bin

# (In IRF mode.) Display brief information about backup startup software images.

<Sysname> display install backup

Backup startup software images on slot 1:

flash:/boot.bin

flash:/system.bin

# (In standalone mode.) Display detailed information about backup startup software images.

<Sysname> display install backup verbose

Backup startup software images on the device:

flash:/boot.bin

[Package]

Vendor: H3C

Product: MSR36

Service name: boot

Platform version: 7.1.070

Product version: Test 0001015

Supported board: MSR36-10

[Component]

Component: boot

Description: boot package

flash:/system.bin

[Package]

Vendor: H3C

Product: MSR36

Service name: system

Platform version: 7.1.070

Product version: Test 0001015

Supported board: MSR36-10

[Component]

Component: system

Description: system package

# (In IRF mode.) Display detailed information about backup startup software images.

<Sysname> display install backup verbose

Backup startup software images on slot 1:

flash:/boot.bin

[Package]

Vendor: H3C

Product: MSR36

Service name: boot

Platform version: 7.1.070

Product version: Test 0001015

Supported board: MSR36-10

[Component]

Component: boot

Description: boot package

flash:/system.bin

[Package]

Vendor: H3C

Product: MSR36

Service name: system

Platform version: 7.1.070

Product version: Test 0001015

Supported board: MSR36-10

[Component]

Component: system

Description: system package

Related commands

boot-loader file

display install committed

Use display install committed to display main startup software images.

Syntax

In standalone mode:

display install committed [ verbose ]

In IRF mode:

display install committed [ slot slot-number ] [ verbose ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

slot slot-number: Specifies an IRF member device by its member ID. If you do not specify an IRF member device, this command displays information for all IRF member devices. (In IRF mode.)

verbose: Displays detailed information. If you do not specify this keyword, the command displays only image names.

Usage guidelines

Some install commands modify the current software image list but do not modify the main startup image list. For the software image changes to take effect after a reboot, you must execute the install commit command to update the main startup image list with the image changes. You can use the display install committed command to verify the operation results.

Both the install commit and boot-loader file commands modify the main startup software image list.

Examples

# (In standalone mode.) Display brief information about main startup software images.

<Sysname> display install committed

Committed packages on the device:

flash:/boot.bin

flash:/system.bin

flash:/feature1.bin

# (In IRF mode.) Display brief information about main startup software images.

<Sysname> display install committed

Committed packages on slot 1:

flash:/boot.bin

flash:/system.bin

flash:/feature1.bin

# (In standalone mode.) Display detailed information about main startup software images.

<Sysname> display install committed verbose

Committed packages on the device:

flash:/boot.bin

[Package]

Vendor: H3C

Product: MSR36

Service name: boot

Platform version: 7.1.070

Product version: Test 0001015

Supported board: MSR36-10

[Component]

Component: boot

Description: boot package

flash:/system.bin

[Package]

Vendor: H3C

Product: MSR36

Service name: system

Platform version: 7.1.070

Product version: Test 0001015

Supported board: MSR36-10

[Component]

Component: system

Description: system package

flash:/feature1.bin

[Package]

Vendor: H3C

Product: MSR36

Service name: feature1

Platform version: 7.1.070

Product version: Test 0001015

Supported board: MSR36-10

[Component]

Component: feature1

Description: feature1 package

# (In IRF mode.) Display detailed information about main startup software images.

<Sysname> display install committed verbose

Committed packages on slot 1:

flash:/boot.bin

[Package]

Vendor: H3C

Product: MSR36

Service name: boot

Platform version: 7.1.070

Product version: Test 0001015

Supported board: MSR36-10

[Component]

Component: boot

Description: boot package

flash:/system.bin

[Package]

Vendor: H3C

Product: MSR36

Service name: system

Platform version: 7.1.070

Product version: Test 0001015

Supported board: MSR36-10

[Component]

Component: system

Description: system package

flash:/feature1.bin

[Package]

Vendor: H3C

Product: MSR36

Service name: feature1

Platform version: 7.1.070

Product version: Test 0001015

Supported board: MSR36-10

[Component]

Component: feature1

Description: feature1 package

Related commands

boot-loader file

display install backup

install commit

display install inactive

Use display install inactive to display inactive software images.

Syntax

In standalone mode:

display install inactive [ verbose ]

In IRF mode:

display install inactive [ slot slot-number ] [ verbose ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

slot slot-number: Specifies an IRF member device by its member ID. If you do not specify an IRF member device, this command displays information for all IRF member devices. (In IRF mode.)

verbose: Displays detailed information. If you do not specify this keyword, the command displays only image names.

Examples

# (In standalone mode.) Display brief information about inactive software images.

<Sysname> display install inactive

Inactive packages on the device:

flash:/feature1.bin

# (In IRF mode.) Display brief information about inactive software images.

<Sysname> display install inactive

Inactive packages on slot 1:

flash:/feature1.bin

# (In standalone mode.) Display detailed information about inactive software images.

<Sysname> display install inactive verbose

Inactive packages on the device:

flash:/feature1.bin

[Package]

Vendor: H3C

Product: MSR36

Service name: feature1

Platform version: 7.1.070

Product version: Test 0001015

Supported board: MSR36-10

[Component]

Component: feature1

Description: feature1 package

# (In IRF mode.) Display detailed information about inactive software images.

<Sysname> display install inactive verbose

Inactive packages on slot 1:

flash:/feature1.bin

[Package]

Vendor: H3C

Product: MSR36

Service name: feature1

Platform version: 7.1.070

Product version: Test 0001015

Supported board: MSR36-10

[Component]

Component: feature1

Description: feature1 package

Related commands

install deactivate

display install ipe-info

Use display install ipe-info to display the software images included in an .ipe file.

Syntax

display install ipe-info ipe-filename

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

ipe-filename: Specifies an .ipe file in the filesystemname/filename.ipe format. The file must be saved 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 file system management in Fundamentals Configuration Guide.

Examples

# (In standalone mode.) Display information about .ipe file flash:/test.ipe.

<Sysname> display install ipe-info flash:/test.ipe

Verifying the file flash:/test.ipe on the device................Done.

H3C MSR36-10 images in IPE:

boot.bin

system.bin

# (In IRF mode.) Display information about .ipe file flash:/test.ipe.

<Sysname> display install ipe-info flash:/test.ipe

Verifying the file flash:/test.ipe on slot 1................Done.

H3C MSR36-10 images in IPE:

boot.bin

system.bin

Related commands

display install package

display install job

Use display install job to display ongoing activate, deactivate, and rollback operations.

Syntax

display install job

Views

Any view

Predefined user roles

network-admin

network-operator

Examples

# (In standalone mode.) Display ongoing activate, deactivate, and rollback operations.

<Sysname> display install job

JobID:5

Action:install activate flash:/feature1.bin on the device

The output shows that the device is executing the install activate flash:/feature1.bin command.

# (In IRF mode.) Display ongoing activate, deactivate, and rollback operations.

<Sysname> display install job

JobID:5

Action:install activate flash:/feature1.bin on slot 1

The output shows that the device is executing the install activate flash:/feature1.bin slot 1 command.

display install log

Use display install log to display log information for upgrades that used install commands.

Syntax

display install log [ log-id ] [ verbose ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

log-id: Specifies a log entry by its ID. If you do not specify this argument, the command displays all log entries.

verbose: Displays detailed log information. If you do not specify this keyword, the command displays brief log information.

Usage guidelines

The device creates one log entry for each upgrade operation to track the upgrade process and operation result.

The upgrade log can contain a maximum of 50 entries. The latest entry overwrites the oldest entry if the log is full.

Examples

# (In standalone mode.) Display all log entries for upgrades that used install commands.

<Sysname> display install log

Install job 1 started by user root at 04/28/2001 08:39:29.

Job 1 completed successfully at 04/28/2001 08:39:30.

Install job 1 started by user root at 04/28/2001 08:39:29.

Install activate flash:/feature1.bin on the device

Job 1 completed successfully at 04/28/2001 08:39:30.

Install job 1 started by user root at 04/28/2001 08:39:29.

Job 1 completed successfully at 04/28/2001 08:39:30.

-----------------------------------------------------------

Install job 2 started by user root at 04/28/2001 08:40:29.

Job 2 completed successfully at 04/28/2001 08:40:30.

Install job 2 started by user root at 04/28/2001 08:40:29.

Install activate flash:/route.bin on the device

Job 2 completed successfully at 04/28/2001 08:40:30.

Install job 2 started by user root at 04/28/2001 08:40:29.

Job 2 completed successfully at 04/28/2001 08:40:30.

# (In IRF mode.) Display all log entries for upgrades that used install commands.

<Sysname> display install log

Install job 1 started by user root at 04/28/2001 08:39:29.

Job 1 completed successfully at 04/28/2001 08:39:30.

Install job 1 started by user root at 04/28/2001 08:39:29.

Install activate flash:/feature1.bin on slot 1

Job 1 completed successfully at 04/28/2001 08:39:30.

Install job 1 started by user root at 04/28/2001 08:39:29.

Job 1 completed successfully at 04/28/2001 08:39:30.

-----------------------------------------------------------

Install job 2 started by user root at 04/28/2001 08:40:29.

Job 2 completed successfully at 04/28/2001 08:40:30.

Install job 2 started by user root at 04/28/2001 08:40:29.

Install activate flash:/route.bin on slot 1

Job 2 completed successfully at 04/28/2001 08:40:30.

Install job 2 started by user root at 04/28/2001 08:40:29.

Job 2 completed successfully at 04/28/2001 08:40:30.

# (In standalone mode.) Displays detailed information about log entry 1 for the upgrade that used install commands.

<Sysname> display install log 1 verbose

Install job 1 started by user root at 04/28/2001 08:39:29.

Job 1 completed successfully at 04/28/2001 08:39:30.

Install job 1 started by user root at 04/28/2001 08:39:29.

Install activate flash:/feature1.bin on the device

Job 1 completed successfully at 04/28/2001 08:39:30.

Install job 1 started by user root at 04/28/2001 08:39:29.

Job 1 completed successfully at 04/28/2001 08:39:30.

Detail of activating packages on the device.

Get upgrade policy successfully.

Detail of activating packages on the device.

Uncompress package to system successfully.

Remove files from system successfully.

# (In IRF mode.) Displays detailed information about log entry 1 for the upgrade that used install commands.

<Sysname> display install log 1 verbose

Install job 1 started by user root at 04/28/2001 08:39:29.

Job 1 completed successfully at 04/28/2001 08:39:30.

Install job 1 started by user root at 04/28/2001 08:39:29.

Install activate flash:/feature1.bin on slot 1

Job 1 completed successfully at 04/28/2001 08:39:30.

Install job 1 started by user root at 04/28/2001 08:39:29.

Job 1 completed successfully at 04/28/2001 08:39:30.

Detail of activating packages on slot 1.

Get upgrade policy successfully.

Detail of activating packages on slot 1.

Uncompress package to system successfully.

Remove files from system successfully.

Related commands

reset install log-history oldest

display install package

Use display install package to display software image file information.

Syntax

display install package { filename | all } [ verbose ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

filename: Specifies a .bin file in the filesystemname/filename.bin format. The file must be saved 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 file system management in Fundamentals Configuration Guide.

all: Specifies all software image files in the root directories of the device's file systems. (In standalone mode.)

all: Specifies all software image files in the root directories of the master's file systems. (In IRF mode.)

verbose: Displays detailed information. If you do not specify this keyword, the command displays only basic software image information.

Examples

# Display information about system.bin.

<Sysname> display install package flash:/system.bin

flash:/system.bin

[Package]

Vendor: H3C

Product: MSR36

Service name: system

Platform version: 7.1.070

Product version: Test 0001015

Supported board: MSR36-10

# Display detailed information about system.bin.

<Sysname> display install package flash:/system.bin verbose

flash:/system.bin

[Package]

Vendor: H3C

Product: MSR36

Service name: system

Platform version: 7.1.070

Product version: Test 0001015

Supported board: MSR36-10

[Component]

Component: system

display install rollback

Use display install rollback to display rollback point information.

Syntax

display install rollback [ point-id ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

point-id: Specifies a rollback point ID. If you do not specify a rollback point ID, the command displays all rollback points.

Usage guidelines

The system does not record rollback points during an upgrade that uses install commands.

Examples

# (In IRF mode.) Display all rollback points.

<Sysname> display install rollback

Install rollback information 1 on slot 1:

Updating from flash:/route-1.bin

to flash:/route-2.bin.

Install rollback information 2 on slot 1:

Deactivating flash:/route-2.bin

· At rollback point 1, flash:/route-1.bin was upgraded to flash:/route-2.bin.

· At rollback point 2, flash:/route-2.bin was deactivated.

Related commands

install rollback

reset install rollback oldest

display install which

Use display install which to display all software image files that include a specific component or file.

Syntax

In standalone mode:

display install which { component name | file filename }

In IRF mode:

display install which { component name | file filename } [ slot slot-number ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

component name: Specifies a component name.

file filename: Specifies a file in the filename.extension format, a case-insensitive string of up to 63 characters. It cannot contain path information.

slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command displays information for all IRF members. (In IRF mode.)

Usage guidelines

A component is a collection of features. The features of a component are installed or uninstalled at the same time.

When the system displays a component or file error, use this command to identify the image files that include the component or file. Then, you can use the install verify command to identify image file problems.

This command searches only the root directories of the file systems at the specified location.

Examples

# (In IRF mode.) Display the software image file that includes pkg_ctr.

<Sysname> display install which file pkg_ctr

Verifying the file flash:/system-t0001015.bin on slot 1..........................Done.

Found pkg_ctr in flash:/system-t0001015.bin on slot 1.

flash:/system-t0001015.bin

[Package]

Vendor: H3C

Product: MSR36

Service name: system

Platform version: 7.1.070

Product version: Test 0001015

Supported board: MSR36-10

Verifying the file flash:/boot-d2601007.bin on slot 1.....Done.

Table 3 Command output

Field	Description
Verifying the file	The system was verifying the validity of the file.
[Package]	Detailed information about the software image.
Service name	Image type: · boot—Boot image. · system—System image. · patch—Patch image. · Any other value indicates a feature image.
Supported board	Hardware types supported by the software image.

‌

display version comp-matrix

Use display version comp-matrix to display the recommended upgrade methods.

Syntax

display version comp-matrix file { boot filename | system filename | feature filename&<1-30> } *

display version comp-matrix file ipe ipe-filename

Views

Any view

Predefined user roles

network-admin

network-operator

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

ipe-filename: Specifies an .ipe file in the filesystemname/filename.ipe 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 file system management in Fundamentals Configuration Guide.

Usage guidelines

If one or more images are incompatible, the incompatible upgrade method applies. The entire system needs to be rebooted during an incompatible upgrade.

Examples

# (In standalone mode.) Display the recommended upgrade method. In this example, the specified images are incompatible with the running images.

<Sysname> display version comp-matrix file boot flash:/boot-t0001015.bin system flash:/system-t0001015.bin feature flash:/feature1-t0001017.bin

Verifying the file flash:/feature1-t0001017.bin on the device.....Done.

Verifying the file flash:/boot-t0001015.bin on the device.....Done.

Verifying the file flash:/system-t0001015.bin on the device.....Done.

Incompatible upgrade.

# (In IRF mode.) Display the recommended upgrade methods. In this example, the specified images are compatible with the running images.

<Sysname> display version comp-matrix file boot flash:/boot-t0001015.bin system flash:/system-t0001015.bin feature flash:/feature1-t0001015.bin

Verifying the file flash:/feature1-t0001015.bin on slot 1.....Done.

Verifying the file flash:/boot-t0001015.bin on slot 1.....Done.

Verifying the file flash:/system-t0001015.bin on slot 1.....Done.

Slot Upgrade Way

1 File Upgrade

Table 4 Command output

Field	Description
Verifying the file	The system was verifying the validity of the file.
Influenced service according to following table	Services that will be affected by the upgrade. This field is displayed only for compatible versions.
Incompatible upgrade	You are upgrading the software to an incompatible version.
Upgrade Way	Upgrade method: · Service Upgrade. · File Upgrade. · Reboot. This field is displayed only for compatible versions.

‌

firmware update

Use firmware update to upgrade firmware.

Syntax

In standalone mode:

firmware update [ subslot subslot-number ] { cpld cpld-number | fpga fpga-number | module module-number } file filename

In IRF mode:

firmware update slot slot-number [ subslot subslot-number ] { cpld cpld-number | fpga fpga-number | module module-number } file filename

Views

User view

Predefined user roles

network-admin

Parameters

slot slot-number: Specifies an IRF member device. The slot-number argument represents its IRF member ID. (In IRF 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.

The following compatibility matrix shows the support of hardware platforms for this parameter:

Hardware	Parameter compatibility
MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE, MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LMS-EA	No
MSR810-LMS, MSR810-LUS	No
MSR2600-6-X1, MSR2600-10-X1	Yes
MSR 2630	Yes
MSR3600-28, MSR3600-51	Yes
MSR3600-28-SI, MSR3600-51-SI	Yes
MSR3600-28-X1, MSR3600-28-X1-DP, MSR3600-51-X1, MSR3600-51-X1-DP	Yes
MSR3610-I-DP, MSR3610-IE-DP	Yes
MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC	Yes
MSR 3610, MSR 3620, MSR 3620-DP, MSR 3640, MSR 3660	Yes
MSR3610-G, MSR3620-G	Yes

‌

fpga fpga-number: Specifies a field programmable gate array (FPGA) by its number.

The following compatibility matrix shows the support of hardware platforms for this parameter:

Hardware	Parameter compatibility
MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE, MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LMS-EA	No
MSR810-LMS, MSR810-LUS	No
MSR2600-6-X1, MSR2600-10-X1	Yes
MSR 2630	Yes
MSR3600-28, MSR3600-51	Yes
MSR3600-28-SI, MSR3600-51-SI	Yes
MSR3600-28-X1, MSR3600-28-X1-DP, MSR3600-51-X1, MSR3600-51-X1-DP	Yes
MSR3610-I-DP, MSR3610-IE-DP	Yes
MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC	Yes
MSR 3610, MSR 3620, MSR 3620-DP, MSR 3640, MSR 3660	Yes
MSR3610-G, MSR3620-G	Yes

‌

The following compatibility matrix shows the support of hardware platforms for this parameter:

Hardware	Parameter compatibility
MSR810, MSR810-W, MSR810-W-DB, MSR810-LM, MSR810-W-LM, MSR810-10-PoE, MSR810-LM-HK, MSR810-W-LM-HK, MSR810-LMS-EA	No
MSR810-LMS, MSR810-LUS	No
MSR2600-6-X1, MSR2600-10-X1	Yes
MSR 2630	Yes
MSR3600-28, MSR3600-51	Yes
MSR3600-28-SI, MSR3600-51-SI	Yes
MSR3600-28-X1, MSR3600-28-X1-DP, MSR3600-51-X1, MSR3600-51-X1-DP	Yes
MSR3610-I-DP, MSR3610-IE-DP	Yes
MSR3610-X1, MSR3610-X1-DP, MSR3610-X1-DC, MSR3610-X1-DP-DC	Yes
MSR 3610, MSR 3620, MSR 3620-DP, MSR 3640, MSR 3660	Yes
MSR3610-G, MSR3620-G	Yes

‌

module module-number: Specifies a module 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 for the CPLD, which does not run Comware and 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.

<Sysname> firmware update 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.

# (In IRF 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.

install abort

Use install abort to abort ongoing upgrade operations performed by using install commands.

Syntax

install abort [ job-id ]

Views

User view

Predefined user roles

network-admin

Parameters

job-id: Specifies the job ID of an upgrade operation. If you do not specify this argument, the command aborts all ongoing software image activate and deactivate operations.

Usage guidelines

The system creates a software image management job each time you use the install activate, install add, install commit, install deactivate, install remove, or install rollback to command. Each job represents one command and is assigned a unique job ID. You can abort only ongoing activate and deactivate operations.

When you abort an ongoing activate or deactivate operation, the system rolls back to the status it was in before the operation was started.

To obtain the ID of a job, use the display install job command.

Examples

# Abort all ongoing upgrade operations.

<Sysname> install abort

Related commands

display install job

install activate

Use install activate to activate software images.

Syntax

In standalone mode:

install activate { boot filename | system filename | feature filename&<1-30> } *

install activate patch filename

In IRF mode:

install activate { boot filename | system filename | feature filename&<1-30> } * slot slot-number

install activate patch filename { all | slot slot-number }

Views

User view

Predefined user roles

network-admin

Parameters

boot: Specifies a boot image file.

system: Specifies a system image file.

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

patch: Specifies a patch image file. You can specify only one patch image file for the command at a time. However, you can execute the command multiple times to activate multiple patch image files.

all: Specifies all member devices. (In IRF mode.)

slot slot-number: Specifies an IRF member device by its member ID. (In IRF mode.)

Usage guidelines

Before you use this command to activate a software image, read the release notes to identify the licensing requirements for the image. If the image requires a license, make sure the device has a valid license installed for the image.

In standalone mode:

An image runs in memory immediately after it is activated. For an activated image to run after a reboot, you must commit the software change by using the install commit command.

In IRF mode:

Images run in memory immediately after they are activated. However, only images activated by using the install activate patch filename all command still run in memory after a reboot. For other images to take effect after a reboot, you must commit the software change by using the install commit command.

If the specified files are not stored on the member device to be upgraded, the command copies the images to the member device automatically.

At reboot, a subordinate device automatically synchronizes the master device's configuration and status data. You must wait for the synchronization to complete before using the install activate command on the subordinate device. To identify whether the synchronization is complete, use the display system stable state command. The synchronization is complete if the System State field displays Stable.

Examples

# (In standalone mode.) Activate the system image in system.bin and the feature images in feature1.bin.

<Sysname> install activate system flash:/system.bin feature flash:/feature1.bin

Verifying the file flash:/feature1.bin on the device.....Done.

Verifying the file flash:/system.bin on the device.....Done.

Upgrade summary according to following table:

flash:/system.bin

Running Version New Version

Test 0001015 Test 0001016

flash:/feature1.bin

Running Version New Version

NONE Test 0001016

Upgrade Way: Service Upgrade

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

This operation might take several minutes, please wait...Done.

# (In IRF mode.) Activate the system image in system.bin and the feature images in feature1.bin on member device 2.

<Sysname> install activate system flash:/system.bin feature flash:/feature1.bin slot 2

Copying file flash:/system.bin to slot2#flash:/system.bin......Done.

Verifying the file flash:/system.bin on slot 2.....Done.

Copying file flash:/feature1.bin to slot2#flash:/feature1.bin......Done.

Verifying the file flash:/feature1.bin on slot 2.....Done.

Upgrade summary according to following table:

flash:/system.bin

Running Version New Version

Test 0001015 Test 0001016

flash:/feature1.bin

Running Version New Version

None Test 0001016

Slot Upgrade Way

2 Service Upgrade

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

This operation might take several minutes, please wait...Done.

Table 5 Command output

Field	Description
Verifying the file	The system was verifying the validity of the file.
Upgrade summary according to following table	Upgrade summary.
Running Version	Version number of the running software.
New Version	Version number of the new software.
Upgrade Way	Upgrade methods: · Service Upgrade. · File Upgrade. · Reboot. This field is displayed only for an upgrade to a compatible version. This field is not supported in the current software version.
Influenced service according to following table	Services influenced by the upgrade.

‌

Related commands

display install active

install commit

install deactivate

install add

Use install add to decompress an .ipe file.

Syntax

install add ipe-filename filesystem

Views

User view

Predefined user roles

network-admin

Parameters

filesystem: Specifies the destination file system for the software images, in the filesystemname format.

Usage guidelines

To use the install activate command to activate software images, you must use .bin image files. If the upgrade file is an .ipe file, use this command to decompress the .ipe file before you start the upgrade.

To identify software images that are included in an .ipe file, use the display install ipe-info command.

Examples

# Decompress all.ipe to the flash memory.

<Sysname> install add flash:/all.ipe flash:

Verifying the file flash:/all.ipe on slot 1...Done.

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

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

install commit

Use install commit to commit software changes.

Syntax

install commit

Views

User view

Predefined user roles

network-admin

Usage guidelines

Before you use this command, read the release notes to identify software image licensing requirements. Make sure the device has valid licenses for all license-based images.

This command adds the patch image file to the startup software image list that the device used at startup.

· If the device used the main startup software image list at startup, this command adds the patch image file to the main startup software image list.

· If the device used the backup startup software image list at startup, this command adds the patch image file to the backup startup software image list.

Both the install commit and boot-loader file commands modify the main startup software image list. To modify the backup startup image list or add inactive images as main startup images, however, you must use the boot-loader file command.

Examples

# Commit software changes.

<Sysname> install commit

This operation will take several minutes, please wait...........................Done.

Related commands

install activate

install deactivate

install rollback

install deactivate

Use install deactivate to deactivate feature images and patch images.

Syntax

In standalone mode:

install deactivate feature filename&<1-30>

install deactivate patch filename

In IRF mode:

install deactivate feature filename&<1-30> slot slot-number

install deactivate patch filename { all | slot slot-number }

Views

User view

Predefined user roles

network-admin

Parameters

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

patch: Specifies a patch image file. You can specify only one patch image file for the command at a time. However, you can execute the command multiple times to deactivate multiple patch image files.

all: Specifies all member devices. (In IRF mode.)

slot slot-number: Specifies an IRF member device by its member ID. (In IRF mode.)

Usage guidelines

At reboot, a subordinate device automatically synchronizes the master device's configuration and status data. You must wait for the synchronization to complete before using the install deactivate command on the subordinate device. To identify whether the synchronization is complete, use the display system stable state command. The synchronization is complete if the System State field displays Stable.

You can deactivate only active feature and patch images.

(In standalone mode.) To prevent deactivated images from running after a reboot, you must commit the software changes by using the install commit command.

(In IRF mode.) Images deactivated by using the install deactivate patch filename all command do not run after a reboot. To prevent other deactivated images from running after a reboot, you must commit the software change by using the install commit command.

Examples

# (In standalone mode.) Deactivate the patch images in the route-patch.bin file.

<Sysname> install deactivate patch flash:/route-patch.bin

This operation might take several minutes, please wait...Done.

# (In IRF mode.) Deactivate the patch images in the route-patch.bin file for a slot.

<Sysname> install deactivate patch flash:/route-patch.bin slot 1

This operation might take several minutes, please wait...Done.

Related commands

display install active

display install inactive

install remove

Use install remove to delete an inactive software image file.

Syntax

In standalone mode:

install remove { filename | inactive }

In IRF mode:

install remove [ slot slot-number ] { filename | inactive }

Views

User view

Predefined user roles

network-admin

Parameters

filename: Specifies a .bin file in the filesystemname/filename.bin format. The value string can have a maximum of 63 characters. The file must be stored in the root directory of a file system on the device. The file system name cannot contain file system location information. For more information about specifying a file, see file system management in Fundamentals Configuration Guide.

slot slot-number: Specifies an IRF member device by its member ID. If you do not specify a member device, this command deletes inactive software images from all IRF members. (In IRF mode.)

inactive: Deletes all inactive software image files in the root directories of the specified file systems.

Usage guidelines

This command permanently deletes the image files from the device. You cannot use the install rollback to command to revert the operation, or use the install abort command to abort the operation.

Examples

# Delete inactive software image file flash:/feature1.bin.

<Sysname> install remove flash:/feature1.bin

install rollback to

Use install rollback to to roll back the software to an earlier rollback point.

Syntax

install rollback to { point-id | original }

Views

User view

Predefined user roles

network-admin

Parameters

point-id: Specifies a rollback point ID. This option is supported only when there are two or more rollback points. To identify available rollback points, use the display install rollback command.

original: Rolls back to the status before any activate or deactivate operations were performed.

Usage guidelines

During an incremental upgrade, the system creates a rollback point for each activate or deactivate operation of a boot, system, or feature image. The device supports a maximum of 50 rollback points. The earliest rollback point is deleted if this limit has been reached when a rollback point is created.

During a reboot upgrade, the system does not create rollback points. After the upgrade, you can roll back the software only to the status before any activate or deactivate operations were performed.

For a rollback to take effect after a reboot, you must perform a commit operation to update the main startup software image list.

After a commit operation is performed, you cannot perform a rollback.

Patch images do not support rollback.

Examples

# Roll back the software to rollback point 1.

<Sysname>install rollback to 1

This operation might take several minutes, please wait...Done.

# Roll back the software to the original software versions and observe the change made by the rollback.

<Sysname> display install active

Active packages on slot 1:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature1-t0001015.bin

<Sysname> display install rollback

Install rollback information 1 on slot 1:

Updating from no package

to flash:/feature1-t0001015.bin.

The output shows that three image files are active but only two of them are confirmed. Image file flash:/feature1-t0001015.bin is not confirmed yet.

<Sysname> install rollback to original

This operation might take several minutes, please wait...Done.

<Sysname> display install active

Active packages on slot 1:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

<Sysname> display install committed

Committed packages on slot 1:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

The output shows the software has been rolled back to the original software version. The image file flash:/feature1-t0001015.bin has been removed.

Related commands

display install rollback

install verify

Use install verify to verify the software change commit status, image integrity, and image consistency.

Syntax

install verify

Views

User view

Predefined user roles

network-admin

Usage guidelines

To make sure the system can start up and operate correctly after an upgrade performed by using install commands, execute this command to verify the following items:

· Integrity—Verify that the boot, system, and feature images are integral.

· Consistency—Verify that the same active images are running across the entire system.

· Software commit status—Verify that the active images are committed as needed.

If a software image fails the verification, perform the following tasks to resolve the problem:

· To ensure software integrity, download and install the software images again.

· To guarantee software image consistency or change software commit status, use the install activate, install deactivate, and install commit commands as appropriate.

Examples

# (In standalone mode.) Verify the software change confirmation status and software image integrity and consistency.

<Sysname> install verify

Active packages on the device are the reference packages.

Packages will be compared with the reference packages.

This operation will take several minutes, please wait...

Verifying packages on the device:

Start to check active package completeness.

Verifying the file flash:/boot-t0001015.bin on the device...........Done.

flash:/boot-t0001015.bin verification successful.

Verifying the file flash:/system-t0001015.bin on the device............Done.

flash:/system-t0001015.bin verification successful.

Start to check active package consistency.

Active packages are consistent with committed packages on their own board.

Active packages are consistent with the reference packages.

Verification is done.

# Verify the software change confirmation status and software image integrity and consistency.

<Sysname> install verify

Active packages on slot 1 are the reference packages.

Packages will be compared with the reference packages.

This operation will take several minutes, please wait...

Verifying packages on slot 0:

Start to check active package completeness.

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

flash:/boot-t0001015.bin verification successful.

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

flash:/system-t0001015.bin verification successful.

Start to check active package consistency.

Active packages are consistent with committed packages on their own board.

Active packages are consistent with the reference packages.

Verifying packages on slot 1:

Start to check active package completeness.

Verifying the file flash:/boot-t0001015.bin on slot 1.....................Done.

flash:/boot-t0001015.bin verification successful.

Verifying the file flash:/system-t0001015.bin on slot 1.....................Done.

flash:/system-t0001015.bin verification successful.

Start to check active package consistency.

Active packages are consistent with committed packages on their own board.

Active packages are consistent with the reference packages.

Verification is done.

# (In IRF mode.) Verify the software change confirmation status and software image integrity and consistency.

<Sysname> install verify

Active packages on slot 1 are the reference packages.

Packages will be compared with the reference packages.

This operation will take several minutes, please wait...

Verifying packages on slot 1:

Start to check active package completeness.

Verifying the file flash:/boot-t0001015.bin on slot 1.....................Done.

flash:/boot-t0001015.bin verification successful.

Verifying the file flash:/system-t0001015.bin on slot 1.....................Done.

flash:/system-t0001015.bin verification successful.

Start to check active package consistency.

Active packages are consistent with committed packages on their own board.

Active packages are consistent with the reference packages.

Verifying packages on slot 2:

Start to check active package completeness.

Verifying the file flash:/boot-t0001015.bin on slot 2.....................Done.

flash:/boot-t0001015.bin verification successful.

Verifying the file flash:/system-t0001015.bin on slot 2.....................Done.

flash:/system-t0001015.bin verification successful.

Start to check active package consistency.

Active packages are consistent with committed packages on their own board.

Active packages are consistent with the reference packages.

Verification is done.

reset install log-history oldest

Use reset install log-history oldest to clear log entries for upgrade operations performed by using install commands.

Syntax

reset install log-history oldest log-number

Views

User view

Predefined user roles

network-admin

Parameters

log-number: Specifies the number of log entries to be deleted.

Usage guidelines

This command clears the specified number of log entries, beginning with the oldest log entry.

Examples

# Clear the two oldest log entries for upgrade operations performed by using install commands.

<Sysname> reset install log-history oldest 2

Related commands

display install log

reset install rollback oldest

Use reset install rollback oldest to clear rollback points for upgrade operations performed by using install commands.

Syntax

reset install rollback oldest point-id

Views

User view

Predefined user roles

network-admin

Parameters

point-id: Specifies a rollback point by its ID.

Usage guidelines

This command clears the specified rollback point and all rollback points older than the specified rollback point.

Examples

# Clear rollback point 2 and all rollback points older than rollback point 2.

<Sysname> reset install rollback oldest 2

Related commands

display install rollback

01-Fundamentals Command Reference

boot-loader file

display install backup

reset install log-history oldest

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program

Global Learning

Partner Sales Resources

Service Business

News & Events

Contact Us