Table of Contents

Related Documents

08-ISSU commands

Title	Size	Download
08-ISSU commands	226.32 KB

ISSU commands

ISSU is available only for dual-chassis IRF fabrics. When the master reboots for an upgrade, the subordinate member takes over for service continuity.

display install active

Use display install active to display active software images.

Syntax

In standalone mode:

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

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays information for all cards. (In standalone mode.)

chassis chassis-number slot slot-number: Specifies a card 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 card. If you do not specify a card, this command displays information for all cards. (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 active software images.

<Sysname> display install active

Active packages on slot 1:

flash:/boot.bin

flash:/system.bin

flash:/feature1.bin

# (In IRF mode.) Display active software images.

<Sysname> display install active

Active packages on chassis 1 slot 1:

flash:/boot.bin

flash:/system.bin

flash:/patch1.bin

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

<Sysname> display install active verbose

Active packages on slot 1:

flash:/boot.bin

[Package]

Vendor: H3C

Product: 12500X-AF

Service name: boot

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu

[Component]

Component: boot

Description: boot package

flash:/system.bin

[Package]

Vendor: H3C

Product: 12500X-AF

Service name: system

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu

[Component]

Component: system

Description: system package

flash:/feature1.bin

[Package]

Vendor: H3C

Product: 12500X-AF

Service name: test

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu

[Component]

Component: test

Description: test package

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

<Sysname> display install active verbose

Active packages on chassis 1 slot 1:

flash:/boot.bin

[Package]

Vendor: H3C

Product: 12500X-AF

Service name: boot

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu lpu

[Component]

Component: boot

Description: boot package

flash:/system.bin

[Package]

Vendor: H3C

Product: 12500X-AF

Service name: system

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu lpu

[Component]

Component: system

Description: system package

flash:/patch1.bin

[Package]

Vendor: H3C

Product: 12500X-AF

Service name: test

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu lpu

[Component]

Component: test

Description: test package

Table 1 Command output

Field	Description
[Package]	Detailed information about the software image.
Service name	Image type: · boot—Boot image. · system—System image. · boot patch—Patch image for the boot image. · system patch—Patch image for the system image. · Any other value indicates a feature image.
Supported board	Hardware types supported by the software image: · mpu—MPU. · lpu—Service card. · sfc—Switching fabric module.
[Component]	Information about components included in the image file.

Related commands

install active

display install backup

Use display install backup to display backup startup software images.

Syntax

In standalone mode:

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

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays information for all cards. (In standalone mode.)

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

Usage guidelines

Backup startup images are used only when the main boot or system image is missing or corrupt. For more information, see Fundamentals Configuration Guide.

To modify the backup startup image list, use the boot-loader file command.

Examples

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

<Sysname> display install backup

Backup startup software images on slot 1:

flash:/boot.bin

flash:/system.bin

# (In IRF mode.) Display the backup startup software images.

<Sysname> display install backup

Backup startup software images on chassis 1 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 slot 1:

flash:/boot.bin

[Package]

Vendor: H3C

Product: 12500X-AF

Service name: boot

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu

[Component]

Component: boot

Description: boot package

flash:/system.bin

[Package]

Vendor: H3C

Product: 12500X-AF

Service name: system

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu

[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 chassis 1 slot 1:

flash:/boot.bin

[Package]

Vendor: H3C

Product: 12500X-AF

Service name: boot

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu lpu

[Component]

Component: boot

Description: boot package

flash:/system.bin

[Package]

Vendor: H3C

Product: 12500X-AF

Service name: system

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu lpu

[Component]

Component: system

Description: system package

Backup startup software images on chassis 2 slot 1:

flash:/boot.bin

[Package]

Vendor: H3C

Product: 12500X-AF

Service name: boot

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu lpu

[Component]

Component: boot

Description: boot package

flash:/system.bin

[Package]

Vendor: H3C

Product: 12500X-AF

Service name: system

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu lpu

[Component]

Component: system

Description: system package

For information about the command output, see Table 1.

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 [ slot slot-number ] [ verbose ]

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays information for all cards. (In standalone 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 the main startup software images.

<Sysname> display install committed

Committed packages on slot 1:

flash:/boot.bin

flash:/system.bin

flash:/feature1.bin

# (In IRF mode.) Display the main startup software images.

<Sysname> display install committed

Committed packages on chassis 1 slot 1:

flash:/boot.bin

flash:/system.bin

flash:/patch1.bin

# (In standalone 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: 12500X-AF

Service name: boot

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu

[Component]

Component: boot

Description: boot package

flash:/system.bin

[Package]

Vendor: H3C

Product: 12500X-AF

Service name: system

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu

[Component]

Component: system

Description: system package

flash:/feature1.bin

[Package]

Vendor: H3C

Product: 12500X-AF

Service name: feature1

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu

[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 chassis 1 slot 1:

flash:/boot.bin

[Package]

Vendor: H3C

Product: 12500X-AF

Service name: boot

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu lpu

[Component]

Component: boot

Description: boot package

flash:/system.bin

[Package]

Vendor: H3C

Product: 12500X-AF

Service name: system

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu lpu

[Component]

Component: system

Description: system package

flash:/patch1.bin

[Package]

Vendor: H3C

Product: 12500X-AF

Service name: patch1

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu lpu

[Component]

Component: patch1

Description: patch1 package

Committed packages on chassis 2 slot 1:

flash:/boot.bin

[Package]

Vendor: H3C

Product: 12500X-AF

Service name: boot

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu lpu

[Component]

Component: boot

Description: boot package

flash:/system.bin

[Package]

Vendor: H3C

Product: 12500X-AF

Service name: system

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu lpu

[Component]

Component: system

Description: system package

flash:/patch1.bin

[Package]

Vendor: H3C

Product: 12500X-AF

Service name: patch1

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu lpu

[Component]

Component: patch1

Description: patch1 package

For information about the command output, see Table 1.

Related commands

boot-loader file

display install backup

install commit

display install inactive

Use display install inactive to display inactive software images in the root directories of file systems.

Syntax

In standalone mode:

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

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays information for all cards. (In standalone 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 in the root directories of the file systems.

<Sysname> display install inactive

Inactive packages on slot 1:

flash:/feature1.bin

# (In IRF mode.) Display brief information about inactive software images in the root directories of the file systems.

<Sysname> display install inactive

Inactive packages on chassis 1 slot 1:

flash:/patch1.bin

Inactive packages on chassis 2 slot 1:

flash:/patch1.bin

# (In standalone mode.) Display detailed information about inactive software images in the root directories of the file systems.

<Sysname> display install inactive verbose

Inactive packages on slot 1:

flash:/feature1.bin

[Package]

Vendor: H3C

Product: 12500X-AF

Service name: feature1

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu

[Component]

Component: feature1

Description: feature1 package

# (In IRF mode.) Display detailed information about inactive software images in the root directories of the file systems.

<Sysname> display install inactive verbose

Inactive packages on chassis 1 slot 1:

flash:/patch1.bin

[Package]

Vendor: H3C

Product: 12500X-AF

Service name: patch1

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu lpu

[Component]

Component: patch1

Description: patch1 package

Inactive packages on chassis 2 slot 1:

flash:/patch1.bin

[Package]

Vendor: H3C

Product: 12500X-AF

Service name: patch1

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu lpu

[Component]

Component: patch1

Description: patch1 package

For information about the command output, see Table 1.

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

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 slot 1................Done.

H3C S12508X-AF 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 chassis 1 slot 1................Done.

H3C S12508X-AF images in IPE:

boot.bin

system.bin

Related commands

display install package

display install job

Use display install job to display ongoing ISSU 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 ISSU 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.

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

<Sysname> display install job

JobID:5

Action:install activate flash:/patch1.bin on chassis 1 slot 1

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

display install log

Use display install log to display ISSU log information.

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 ISSU log entries.

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

Usage guidelines

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

The ISSU 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 ISSU log entries.

<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 IRF mode.) Displays detailed information about all ISSU log entries.

<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:/patch1.bin on chassis 1 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 chassis 1 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 ISSU log entry 1.

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

# (In IRF mode.) Displays detailed information about ISSU log entry 1.

<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:/patch1.bin on chassis 1 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 chassis 1 slot 1.

Get upgrade policy successfully.

Detail of activating packages on chassis 1 slot 1.

Uncompress package to system successfully.

Remove files from system successfully.

Table 2 Command output

Field	Description
Detail of xxx	Detailed information about an ISSU operation.
Get upgrade policy successfully.	Obtained the upgrade policy.
Uncompress package to system successfully.	Decompressed the package successfully.
Remove files from system successfully.	Deleted files from the 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 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.

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

all: Specifies all software image files in the root directories of the file systems on the global active MPU. (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: 12500X-AF

Service name: system

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu

# Display detailed information about system.bin.

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

flash:/system.bin

[Package]

Vendor: H3C

Product: 12500X-AF

Service name: system

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu

[Component]

Component: system

Description: system package

For information about the command output, see Table 1.

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

Use this command to identify available rollback points during an ISSU that uses install commands. The system does not record rollback points during an ISSU that uses issu commands.

Examples

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

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

<Sysname> display install rollback

Install rollback information 1 on chassis 1 slot 1

Updating from flash:/route-1.bin

to flash:/route-2.bin.

Install rollback information 2 on chassis 1 slot 1

Deactivating flash:/route-2.bin

The output shows that the device has two rollback points.

· 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 } [ slot slot-number ]

In IRF mode:

display install which { component name | file filename } [ chassis chassis-number 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 a card by its slot number. If you do not specify a card, this command displays information for all cards. (In standalone 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 standalone 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: 12500X-AF

Service name: system

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu

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

# (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 chassis 1 slot 1...........Done.

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

flash:/system-t0001015.bin

[Package]

Vendor: H3C

Product: 12500X-AF

Service name: system

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu lpu

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: · mpu—MPU. · lpu—Service card. · sfc—Switching fabric module.

display issu rollback-timer

Use display issu rollback-timer to display automatic rollback timer information.

Syntax

display issu rollback-timer

Views

Any view

Predefined user roles

network-admin

network-operator

Usage guidelines

Change to the automatic rollback interval does not take effect on the ongoing ISSU process. The current remaining rollback time might be greater than the specified automatic rollback interval.

Examples

# Display automatic rollback timer information after the issu run switchover command is executed.

<Sysname> display issu rollback-timer

Rollback timer: Working

Rollback interval: 45 minutes

Rollback time remaining : 40 minutes

# Display automatic rollback timer information after the issu accept command is executed.

<Sysname> display issu rollback-timer

Rollback timer: Not working

Rollback interval: 30 minutes

# Display automatic rollback timer information when no ISSU process is taking place.

<Sysname> display issu rollback-timer

Rollback timer: Not working

Rollback interval: 45 minutes

Related commands

issu rollback-timer

display issu state

Use display issu state to display ISSU status information.

Syntax

display issu state

Views

Any view

Predefined user roles

network-admin

network-operator

Usage guidelines

During an ISSU that uses issu commands, you can use this command to verify the ISSU status and determine what to do next.

This command does not apply to an ISSU that uses install commands, because the ISSU state machine is not involved.

Examples

# (In standalone mode.) Display ISSU status information when no upgrade is taking place.

<Sysname> display issu state

ISSU state: Init

Compatibility: Unknown

Work state: Normal

Upgrade method: Card by card

Upgraded slot: None

Current upgrading slot: None

Current version list:

boot: 7.1.070, Test 0001015

system: 7.1.070, Test 0001015

feature1: 7.1.070, Test 0001015

Current software images:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature1-t0001015.bin

# (In standalone mode.) Display ISSU status information while the issu load command is being executed.

<Sysname> display issu state

ISSU state: Loading

Compatibility: Incompatible

Work state: Normal

Upgrade method: Card by card

Upgraded slot: None

Current upgrading slot:

slot 1

Previous version list:

boot: 7.1.070, Test 0001015

system: 7.1.070, Test 0001015

feature1: 7.1.070, Test 0001015

Previous software images:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature1-t0001015.bin

Upgrade version list:

boot: 7.1.070, Test 0001016

system: 7.1.070, Test 0001016

feature1: 7.1.070, Test 0001016

Upgrade software images:

flash:/boot-t0001016.bin

flash:/system-t0001016.bin

flash:/feature1-t0001016.bin

# (In IRF mode.) On a single-chassis IRF fabric, display ISSU status information when no upgrade is taking place.

<Sysname> display issu state

ISSU state: Init

Compatibility: Unknown

Work state: Normal

Upgrade method: Card by card

Upgraded slot: None

Current upgrading slot: None

Current version list:

boot: 7.1.070, Test 0001015

system: 7.1.070, Test 0001015

feature1: 7.1.070, Test 0001015

Current software images:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature1-t0001015.bin

# (In IRF mode.) On a single-chassis IRF fabric, display ISSU status information on the global active MPU after the issu load command is completed.

<Sysname> display issu state

ISSU state: Loaded

Compatibility: Compatible

Work state: Normal

Upgrade method: Card by card

Upgraded slot:

chassis 1 slot 1

Current upgrading slot: None

Previous version list:

boot: 7.1.070, Test 0001015

system: 7.1.070, Test 0001015

feature1: 7.1.070, Test 0001015

Previous software images:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature1-t0001015.bin

Upgrade version list:

boot: 7.1.070, Test 0001016

system: 7.1.070, Test 0001016

feature1: 7.1.070, Test 0001016

Upgrade software images:

flash:/boot-t0001016.bin

flash:/system-t0001016.bin

flash:/feature1-t0001016.bin

# (In IRF mode.) On a dual-chassis IRF fabric, display ISSU status information on the original master after the issu load command is completed.

<S ysname> display issu state

ISSU state: Loaded

Compatibility: Incompatible

Work state: Independent active

Upgrade method: Chassis by chassis

Upgraded chassis:

chassis 2

Current upgrading chassis: None

Previous version list:

boot: 7.1.070, Test 0001015

system: 7.1.070, Test 0001015

patch1: 7.1.070, Test 0001015

Previous software images:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/patch1-t0001015.bin

Upgrade version list:

boot: 7.1.070, Test 0001016

system: 7.1.070, Test 0001016

patch1: 7.1.070, Test 0001016

Upgrade software images:

flash:/boot-t0001016.bin

flash:/system-t0001016.bin

flash:/patch1-t0001016.bin

Table 4 Command output

Field	Description
ISSU state	ISSU status: · Init—The ISSU process has not started or has finished. · Loading—The system is executing the issu load command. · Loaded—The issu load command is completed. · Switching—The system is executing the issu run switchover command. · Switchover—The issu run switchover command is completed. · Accepted—The issu accept command is completed. · Committing—The system is executing the issu commit command. · Rollbacking—A rollback is in progress. · Unknown—An upgrade is in progress. This value might appear when you execute the command on an original standby MPU.
Compatibility	Version compatibility: · Compatible —Upgrade to a compatible version. · Incompatible—Upgrade to an incompatible version. · Unknown—No upgrade is in progress.
Work state	Operating status of the device: · Normal—The device is operating correctly. · Independent active—When you perform an ISSU to an incompatible version, the standby MPU that is upgraded first enters this state. In this state, the two MPUs of the device are running different software versions.
Upgrade method	Upgrade mode: · Card by card—MPUs are upgraded one by one. · Chassis by chassis—The subordinate member is upgraded first, and then the original master is upgraded.
Upgraded slot	Upgraded cards. (In standalone mode.) This field is available in standalone mode. During a rollback, this field displays Unknown.
Current upgrading slot	Cards that are being upgraded. (In standalone mode.) This field is available in standalone mode. During a rollback, this field displays Unknown.
Upgraded chassis	Upgraded members. (In IRF mode.) This field is available in IRF mode. During a rollback, this field displays Unknown.
Current upgrading chassis	Members that are being upgraded. (In IRF mode.) During a rollback, this field displays Unknown. This field is available on single-chassis IRF fabrics.
Current version list	Versions of currently running images. This field is displayed if no upgrade is taking place.
Current software images	File names of currently running images. This field is displayed if no upgrade is taking place.
Previous version list	Versions of the images that were running on the device before the ISSU. If you execute this command on an original standby MPU during an ISSU to an incompatible version, this field displays Unknown.
Previous software images	File names of the images that were running on the device before the ISSU. If you execute this command on an original standby MPU during an ISSU to an incompatible version, this field displays Unknown.
Upgrade version list	Versions of the upgrade images. If you execute this command on an original standby MPU during an ISSU to an incompatible version, this field displays Unknown.
Upgrade software images	File names of the upgrade images. If you execute this command on an original standby MPU during an ISSU for an incompatible version, this field displays Unknown.

‌

Related commands

issu accept

issu commit

issu load

issu rollback

issu run switchover

display version comp-matrix file

Use display version comp-matrix file to display the recommended ISSU 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.

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 ISSU methods. In this example, the specified image is compatible with the running images.

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

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

Identifying the upgrade methods..........Done.

Slot Upgrade Way

0 Service Upgrade

1 Service Upgrade

2 Service Upgrade

Influenced service according to following table on slot 0:

flash:/feature1-t0001015.bin

Feature1

Influenced service according to following table on slot 2:

flash:/feature1-t0001015.bin

Feature1

Influenced service according to following table on slot 1:

flash:/feature1-t0001015.bin

Feature1

Table 5 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	ISSU method: · Service Upgrade. · File Upgrade. · Reboot. · S equence Reboot. This field is displayed only for compatible versions. For more information about ISSU methods, see Fundamentals Configuration Guide.

Related commands

issu load

install abort

Use install abort to abort an ongoing activate or deactivate operation.

Syntax

install abort [ job-id ]

Views

User view

Predefined user roles

network-admin

Parameters

job-id: Specifies the job ID of an ISSU 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. To obtain the ID of a job, use the display install job command.

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

Examples

# Abort all ongoing software image activate and deactivate operations.

<Sysname> install abort

Related commands

display install job

install activate

Use install activate to activate software images, or identify the ISSU method and the possible impact on the device.

Syntax

In standalone mode:

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

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

In IRF mode:

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

install activate patch filename { all | chassis chassis-number 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 a space-separated list of up to 30 feature image files

patch: Specifies a patch image file.

all: Specifies all cards. (In standalone mode.)

all: Specifies all cards. (In IRF mode.)

slot slot-number: Specifies a card by its slot number. (In standalone mode.)

test: Only identifies the ISSU method to be used for the upgrade. If you do not specify this keyword, the command activates the specified software images.

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.

NOTE:

The software images for the device are digitally signed. The system verifies the digital signature of a software image for authenticity and integrity before it activates it. If the digital signature verification fails, the system will not activate the image and you will receive a digital signature verification failure message.

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 MPU to be upgraded, the command copies the files to the MPU automatically.

(In standalone mode.) If you specify the active MPU for the slot slot-number option, the command takes effect on the active MPU and all LPUs. If you specify the standby MPU for the slot slot-number option, the command takes effect only on the standby MPU.

(In IRF mode.) If you specify the global active MPU for the chassis chassis-number slot slot-number option, the command takes effect on the global active MPU and all LPUs. If you specify a standby MPU for the chassis chassis-number slot slot-number option, the command takes effect on the standby MPU.

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

You can install up to 32 .bin files on the device, including one boot image file, one system image file, and up to 30 feature and patch image files.

Examples

# (In standalone mode.) Identify the ISSU method for feature upgrade with feature1.bin on the standby MPU (in slot 1) and the upgrade impact.

<Sysname> install activate feature flash:/feature1.bin slot 1 test

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

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

Upgrade summary according to following table:

flash:/feature1.bin

Running Version New Version

Test 0001015 Test 0001016

Slot Upgrade Way

1 Service Upgrade

Influenced service according to following table:

flash:/feature1.bin

Feature1

The output shows that a service upgrade is recommended. The Feature1 module will be rebooted during the upgrade.

# (In standalone mode.) Activate the system image in system.bin and the feature images in feature1.bin on the standby MPU (in slot 1).

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

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

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

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

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

Verifying the file flash:/system.bin on slot 1.....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 0001015

Slot Upgrade Way

1 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 patch image in patch1.bin on the global standby MPU in slot 1 of chassis 1.

<Sysname> install activate patch flash:/patch1.bin chassis 1 slot 1

Copying file flash:/patch1.bin to chassis1#slot1#flash:/patch1.bin......Done.

Verifying the file flash:/patch1.bin on chassis 1 slot 1.....Done.

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

Table 6 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	ISSU methods: · Service Upgrade. · File Upgrade. · Reboot. · Sequence Reboot. This field is displayed only for an upgrade to a compatible version. For more information about ISSU methods, see Fundamentals Configuration Guide.
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 modifies the main startup software image list to be the same as the current software image list.

You must execute this command after using the following commands:

· The install activate command in an incremental upgrade.

· The install deactivate command.

· The install rollback command.

In a reboot upgrade, the install activate command modifies both the current and startup software image lists. You do not need to commit software changes.

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.

For more information about main and backup startup software images, see Fundamentals Configuration Guide.

Examples

# Commit software changes.

<Sysname> install commit

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

The current software images have been saved as the startup software images.

Current software images on slot 0:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature1-t0001015.bin

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

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

In IRF mode:

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

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

Views

User view

Predefined user roles

network-admin

Parameters

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

patch: Specifies a patch image file.

filename: Specifies a .bin file in the filesystemname/filename.bin format. The value string can have a maximum of 63 characters. 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.

all: Specifies all cards on which the specified patch image file has been activated. (In standalone mode.)

all: Specifies all cards on which the specified patch image file has been activated. (In IRF mode.)

slot slot-number: Specifies a card by its slot number. (In standalone 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.

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

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

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

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

<Sysname> install deactivate patch flash:/route-patch.bin chassis 1 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 [ slot slot-number ] { filename | inactive }

In IRF mode:

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

Views

User view

Predefined user roles

network-admin

Parameters

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command deletes inactive software images from all cards. (In standalone mode.)

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.

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 currently 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 SSH feature 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 ensure a successful ISSU and make sure that the system can start up and operate correctly after an ISSU, 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 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 chassis 1 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 chassis 1 slot 1:

Start to check active package completeness.

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

flash:/boot-t0001015.bin verification successful.

Verifying the file flash:/system-t0001015.bin on chassis 1 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 chassis 2 slot 1:

Start to check active package completeness.

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

flash:/boot-t0001015.bin verification successful.

Verifying the file flash:/system-t0001015.bin on chassis 2 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.

issu accept

Use issu accept to accept the upgrade to a compatible version and delete the automatic rollback timer.

Syntax

issu accept

Views

User view

Predefined user roles

network-admin

Usage guidelines

The system cannot perform automatic rollback for the ISSU process after you execute this command. However, you can use the issu rollback command to perform a manual rollback.

The issu accept command does not apply to an ISSU to an incompatible version.

Examples

# Accept the upgrade to a compatible version.

<Sysname> issu accept

Related commands

issu load

issu run switchover

issu commit

(In standalone mode.) Use issu commit to upgrade the original active MPU to a compatible version and complete the ISSU.

(On a dual-MPU single-chassis IRF fabric.) Use issu commit to upgrade the original active MPU to a compatible version and complete the ISSU.

(On a dual-chassis IRF fabric.) Use issu commit to upgrade the original master and complete the ISSU upgrade.

Syntax

In standalone mode:

issu commit slot slot-number

In IRF mode (single-chassis):

issu commit chassis chassis-number slot slot-number

In IRF mode (dual-chassis):

issu commit chassis chassis-number

Views

User view

Predefined user roles

network-admin

Parameters

slot slot-number: Specifies the slot number of the original active MPU. (In standalone mode.)

chassis chassis-number slot slot-number: Specifies the member ID and slot number of the original active MPU. (On a single-chassis IRF fabric.)

chassis chassis-number: Specifies the member ID of the original master. (On a dual-chassis IRF fabric.)

Usage guidelines

CAUTION:

On a standalone device or a single-member IRF fabric, this command ends the ISSU process. The ISSU process cannot be rolled back automatically or manually after you execute this command. After the ISSU commit operation is completed, the ISSU status changes to Init.

On a two-member IRF fabric, the ISSU process cannot be rolled back automatically or manually after you execute this command. After all members are upgraded, the ISSU status changes to Init.

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 issu commit 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.) Upgrade the original active MPU to a compatible version. In this example, the device has two MPUs.

<Sysname> issu commit slot 0

Upgrade summary according to following table:

flash:/feature1.bin

Running Version New Version

Test 0001015 Test 0001016

Slot Upgrade Way

0 Service Upgrade

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

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

# (In standalone mode.) Finish the upgrade of the MPU to a compatible version. In this example, the device only one MPU.

<Sysname> issu commit slot 0

# (In IRF mode.) Upgrade the original master to a compatible version. In this example, the member ID of the original master is 1.

<Sysname> issu commit chassis 1

Copying file flash:/feature1.bin to chassis1#slot1#flash:/feature1.bin...Done.

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

Upgrade summary according to following table:

flash:/feature1.bin

Running Version New Version

Test 0001015 Test 0001016

Chassis Slot Upgrade Way

1 0 Service Upgrade

1 1 Service Upgrade

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

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

# (In IRF mode.) Upgrade the original active MPU to a compatible version. (In this example, the IRF fabric has a single member and the member has two MPUs.)

<Sysname> issu commit chassis 1 slot 0

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

Upgrade summary according to following table:

flash:/feature1.bin

Running Version New Version

Test 0001015 Test 0001016

Chassis Slot Upgrade Way

1 0 Service Upgrade

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

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

# (In IRF mode.) Finish the upgrade to a compatible version. (In this example, the IRF fabric has a single member and the member has only one MPU.)

<Sysname> issu commit chassis 1 slot 0

For information about the command output, see Table 5.

Related commands

issu accept

issu load

issu run switchover

issu load

(On a standalone device or single-chassis IRF fabric.) Use issu load to upgrade the standby MPU and configure the new images as main startup software images for the MPU.

(On a dual-chassis IRF fabric.) Use issu load to upgrade the subordinate member and configure the new images as main startup software images for the member.

Syntax

In standalone mode:

issu load file { boot filename | system filename | feature filename&<1-30> } * slot slot-number [ reboot ]

issu load file ipe ipe-filename slot slot-number [ reboot ]

In IRF mode (single-chassis):

issu load file { boot filename | system filename | feature filename&<1-30> } * chassis chassis-number slot slot-number [ reboot ]

issu load file ipe ipe-filename chassis chassis-number slot slot-number [ reboot ]

In IRF mode (dual-chassis):

issu load file { boot filename | system filename | feature filename&<1-30> } * chassis chassis-number [ reboot ]

issu load file ipe ipe-filename chassis chassis-number [ reboot ]

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 active MPU (in standalone mode) or global active MPU (in IRF mode). 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 active MPU (in standalone mode) or global active MPU (in IRF mode). 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.

slot slot-number: Specifies the slot number of the standby MPU. If the device has only one MPU, enter the slot number of the MPU to upgrade the entire device. (In standalone mode.)

chassis chassis-number slot slot-number: Specifies the member ID and slot number of the standby MPU. If the member has only one MPU, enter the member ID and slot number of the MPU to upgrade the entire fabric. (On a single-chassis IRF fabric.)

chassis chassis-number: Specifies the member ID of the subordinate member. (On a dual-chassis IRF fabric.)

reboot: Uses the reboot method for the upgrade. For an incremental upgrade, specify this keyword if you want to use the reboot upgrade method. If you do not specify this keyword, the recommended upgrade method is used.

Usage guidelines

You can upgrade all or some of the software images. If you are upgrading only some of the images, make sure the new images are compatible with the images that are not to be upgraded. The upgrade will fail if a conflict exists.

(Standalone device or single-chassis IRF fabric.) This command performs the following operations:

· Checks the version compatibility.

· Identifies the upgrade method.

· Loads the new images to upgrade the specified MPU.

· Sets the new images as the main startup software images for the specified MPU so the upgrade can survive a reboot.

(Dual-chassis IRF fabric.) This command performs the following operations:

· Checks the version compatibility.

· Identifies the upgrade method.

· Loads the new images to upgrade the specified member device.

· Sets the new images as the main startup software images for the specified member device so the upgrade can survive a reboot.

NOTE:

The software images for the device are digitally signed. The system verifies the digital signature of a software image for authenticity and integrity before it sets and loads that image as a main startup image. If the digital signature verification fails, the system will not set or load the image as a main startup image and you will receive a digital signature verification failure message.

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 issu load 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. (In IRF mode.)

Examples

# (In standalone mode.) On a dual-MPU device, upgrade the standby MPU with feature image file flash:/feature1.bin. (In this example, the image is compatible with the running images.)

<Sysname> issu load file feature flash:/feature1.bin slot 1

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

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

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

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

Identifying the upgrade methods….Done.

Upgrade summary according to following table:

flash:/feature1.bin

Running Version New Version

Test 0001015 Test 0001016

Slot Upgrade Way

1 Service Upgrade

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

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

# (In standalone mode.) On a dual-MPU device, use the reboot method to upgrade the standby MPU when the incremental upgrade method is recommended.

<Sysname> issu load file feature flash:/feature1.bin slot 1 reboot

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

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

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

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

Identifying the upgrade methods….Done.

Upgrade summary according to following table:

flash:/feature1.bin

Running Version New Version

Test 0001015 Test 0001016

Slot Upgrade Way

1 Reboot

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

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

# (In standalone mode.) On a dual-MPU device, upgrade the standby MPU with feature image file flash:/feature1.bin. (In this example, the image is incompatible with the running images.)

<Sysname> issu load file feature flash:/feature1.bin slot 1

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

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

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

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

Identifying the upgrade methods….Done.

Upgrade summary according to following table:

flash:/feature1.bin

Running Version New Version

Test 0001015 Test 0001016

Slot Upgrade Way

1 Reboot

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

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

# (In standalone mode.) On a single-MPU device, upgrade the MPU with feature image file flash:/feature1.bin. (In this example, the image is compatible with the running images.)

<Sysname>issu load file feature flash:/feature1.bin slot 0

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

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

Identifying the upgrade methods….Done.

Upgrade summary according to following table:

flash:/feature1.bin

Running Version New Version

Test 0001015 Test 0001016

Slot Upgrade Way

0 Service Upgrade

2 Service Upgrade

3 Service Upgrade

4 Service Upgrade

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

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

# (In standalone mode.) On a single-MPU device, use the reboot method to upgrade the MPU when the incremental upgrade method is recommended.

<Sysname>issu load file feature flash:/feature1.bin slot 0 reboot

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

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

Identifying the upgrade methods….Done.

Upgrade summary according to following table:

flash:/feature1.bin

Running Version New Version

Test 0001015 Test 0001016

Slot Upgrade Way

0 Reboot

2 Reboot

3 Reboot

4 Reboot

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

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

# (In standalone mode.) On a single-MPU device, upgrade the MPU with feature image file flash:/feature1.bin. (In this example, the image is incompatible with the running images.)

<Sysname> issu load file feature flash:/feature1.bin slot 0

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

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

Identifying the upgrade methods….Done.

Upgrade summary according to following table:

flash:/feature1.bin

Running Version New Version

Test 0001015 Test 0001016

Slot Upgrade Way

0 Reboot

2 Reboot

3 Reboot

4 Reboot

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

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

# (In IRF mode.) Upgrade subordinate member 2 with image file flash:/version.ipe.

<Sysname> issu load file ipe flash:/version-t0001015.ipe chassis 2

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

Verifying image file flash:/version-t0001015.ipe on chassis 2 slot 0.................Done.

Verifying image file flash:/version-t0001015.ipe on chassis 2 slot 1.................Done.

Decompressing file BOOT-T0001015.bin to flash:/BOOT-E1133.bin.............Done.

Decompressing file SYSTEM-T0001015.bin to flash:/SYSTEM-E1133.bin...........Done.

Decompression completed.

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

Upgrade summary according to following table:

flash:/BOOT-T0001015.bin

Running Version New Version

Test 0001015 Test 0001016

flash:/SYSTEM-E1133.bin

Running Version New Version

Test 0001015 Test 0001016

Chassis Slot Upgrade Way

2 0 Reboot

2 1 Reboot

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

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

Table 7 Command output

Field	Description
Verifying the file	The system was verifying the validity of the file.
Copying file	(In standalone mode.) The system was copying the upgrade file to the standby MPU. This field is displayed if you specified the standby MPU for the command. (In IRF mode.) The system was copying the upgrade file to a global standby MPU. This field is displayed if you specified a global standby MPU for the command.
Upgrade Way	ISSU method: · Service Upgrade. · File Upgrade. · Reboot. · Sequence Reboot. This field is displayed only for an upgrade to a compatible version. For more information about ISSU methods, see Fundamentals Configuration Guide.

issu one-step

Use issu one-step to perform an ISSU in one step.

Syntax

In standalone mode:

issu one-step file { boot filename | system filename | feature filename&<1-30> } * [ slot slot-number ] [ reboot ]

issu one-step file ipe ipe-filename [ slot slot-number ] [ reboot ]

In IRF mode (single-chassis):

issu one-step file { boot filename | system filename | feature filename&<1-30> } * [ chassis chassis-number slot slot-number ] [ reboot ]

issu one-step file ipe ipe-filename [ chassis chassis-number slot slot-number ] [ reboot ]

In IRF mode (dual-chassis):

issu one-step file { boot filename | system filename | feature filename&<1-30> } * [ chassis chassis-number ] [ reboot ]

issu one-step file ipe ipe-filename [ chassis chassis-number ] [ reboot ]

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.

slot slot-number: Specifies the slot number of the standby MPU. The standby MPU will become the active MPU after the ISSU. If the device has only one MPU, enter the slot number of the MPU. If you do not specify a slot number on a dual-MPU device, the device selects an MPU as the active MPU after the ISSU. (In standalone mode.)

chassis chassis-number slot slot-number: Specifies the member ID and slot number of the standby MPU. The standby MPU will become the active MPU after the ISSU. If the member has only one MPU, enter the member ID and slot number of the MPU. If the member has two MPUs but you do not specify a slot number, the system selects an MPU as the active MPU after the ISSU. (On a single-chassis IRF fabric.)

chassis chassis-number: Specifies the member ID of the subordinate member. If you do not specify this option, the device automatically specifies the subordinate member as the master device after the ISSU. (On a dual-chassis IRF fabric.)

reboot: Uses the reboot method for the upgrade. For an incremental upgrade or ISSU reboot upgrade, specify this keyword if you want to use the reboot upgrade method. If you do not specify this keyword, the recommended upgrade method is used.

Usage guidelines

This command starts and finishes an ISSU. During the operation, you cannot perform a rollback or any other tasks.

Both the current software version and the new software version must support one-step ISSU.

You may upgrade all or some of the software images. If you are upgrading only some of the images, make sure the new images are compatible with the images that are not to be upgraded. The upgrade will fail if a conflict exists.

(In IRF mode.) At reboot, a subordinate device automatically synchronizes the master device's configuration and status data. Before using this command, identify whether the synchronization is complete on all subordinate devices by using the display system stable state command. The synchronization is complete if the System State field displays Stable.

NOTE:

Examples

# Perform an ISSU in one step by using flash:/boot.bin, flash:/system.bin, and flash:/feature1.bin.

<Sysname> issu one-step file boot flash:/boot.bin system flash:/system.bin feature flash:/feature1.bin

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

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

# Use the reboot method to perform an ISSU in one step.

<Sysname> issu one-step file boot flash:/boot.bin system flash:/system.bin feature flash:/feature1.bin flash:/feature1.bin reboot

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

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

issu rollback

Use issu rollback to cancel the ISSU and roll back to the original software versions.

Syntax

issu rollback

Views

User view

Predefined user roles

network-admin

Usage guidelines

The device supports automatic rollback and manual rollback. This command performs a manual rollback.

You can perform a manual rollback while an ISSU is in one of the following states:

· Loaded.

· Switching (during an upgrade to a compatible version).

· Switchover (during an upgrade to a compatible version).

· Accepted.

If the ISSU is in Loading state, the rollback might fail. Use the display version command to examine the rollback result after the rollback is completed.

If a rollback occurs while an ISSU is in Switching state, the entire system reboots automatically.

(In IRF mode.) A rollback performed for a dual-chassis IRF fabric after you execute the issu run switchover command cancels only the upgrades. The master/subordinate switchover operation is not canceled.

Examples

# Roll back to the original software versions.

<Sysname> issu rollback

This command will quit the ISSU process and roll back to the previous version. Continue? [Y/N]:y

Related commands

issu accept

issu commit

issu load

issu run switchover

issu rollback-timer

Use issu rollback-timer to set the automatic rollback timer.

Use undo issu rollback-timer to restore the default.

Syntax

issu rollback-timer minutes

undo issu rollback-timer

Default

The automatic rollback timer is 45 minutes

Views

System view

Predefined user roles

network-admin

Parameters

minutes: Specifies the automatic rollback interval in minutes. The value range is 0 to 120. Setting it to 0 disables automatic rollback.

Usage guidelines

The automatic software version rollback feature is only available during an ISSU to a compatible version in the following scenarios:

· An IRF fabric has two members.

· A single-chassis IRF fabric has two MPUs.

· A standalone device has two MPUs.

The system starts the automatic rollback timer when you execute the issu run switchover command in a scenario where automatic rollback is supported. If you do not execute the issu accept or issu commit command before the timer expires, the system automatically rolls back to the software version used before the ISSU.

Change to the automatic rollback interval does not take effect on the ongoing ISSU process.

Examples

# Set the automatic rollback timer to 50 minutes.

<Sysname> system-view

[Sysname] issu rollback-timer 50

Related commands

issu rollback

issu run switchover

Use issu run switchover to perform an ISSU switchover.

Syntax

issu run switchover

Views

User view

Predefined user roles

network-admin

Usage guidelines

In standalone mode:

Use this command if the device has two MPUs.

· For a compatible upgrade, this command performs operations depending on the ISSU method.

¡ Incremental upgrade—Performs a process-level active/standby switchover for the processes to be upgraded.

¡ Reboot upgrade—Reboots the current active MPU with the old software version and upgrades the LPUs and switching fabric modules. The upgraded MPU then becomes the new active MPU.

· For an incompatible upgrade, this command reboots the current active MPU, the LPUs, and the switching fabric modules to use the new software version. The upgraded MPU then becomes the new active MPU. After the reboot, the original active MPU, the LPUs, and the switching fabric modules are upgraded, and the ISSU process ends.

In IRF mode:

Use this command only on a dual-chassis IRF fabric or a dual-MPU single-member IRF fabric.

· (On a dual-MPU single-chassis IRF fabric.) The function of this command is as follows:

¡ For a compatible upgrade, this command performs operations depending on the ISSU method.

- Incremental upgrade—Performs a process-level active/standby switchover for the processes to be upgraded.

- Reboot upgrade—Reboots the current active MPU with the old software version and upgrades the LPUs and switching fabric modules. The upgraded MPU then becomes the new active MPU.

¡ For an incompatible upgrade, this command reboots the current active MPU, the LPUs, and the switching fabric modules to use the new software version. After the reboot, the following operations take place in turn:

- The upgraded MPU becomes the new active MPU.

- The original active MPU, the LPUs, and the switching fabric modules are upgraded.

- The ISSU process ends.

· (On a dual-chassis IRF fabric.) The function of this command is as follows:

¡ For a compatible upgrade, this command performs operations depending on the ISSU method.

- Incremental upgrade—Performs a process-level master/subordinate switchover for the processes to be upgraded.

- Reboot upgrade—Reboots the current master with the old software version to cause the subordinate member to become the new master.

¡ For an incompatible upgrade, the issu load command splits the IRF fabric into two fabrics, with the upgraded member forming a new fabric. The issu run switchover command reboots the old IRF fabric's member with the upgrade images to join the new IRF fabric as the subordinate member.

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 issu run switchover 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.

When you execute the issu run switchover command during an ISSU to a compatible version, the system starts the automatic rollback timer. If you do not execute the issu accept or issu commit command before the timer expires, the system automatically rolls back to the original software versions.

Examples

# (In standalone mode.) On a dual-MPU device, perform an active/standby switchover and upgrade the LPUs and switching fabric modules to a compatible version.

<Sysname> issu run switchover

Upgrade summary according to following table:

flash:/feature1.bin

Running Version New Version

Test 0001015 Test 0001016

Slot Switchover Way

0 Active standby process switchover

Slot Upgrade Way

2 Service Upgrade

3 Service Upgrade

4 Service Upgrade

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

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

# (In standalone mode.) On a dual-MPU device, perform an active/standby switchover, and upgrade the current active MPU and the LPUs and switching fabric modules to an incompatible version.

<Sysname> issu run switchover

Upgrade summary according to following table:

flash:/feature1.bin

Running Version New Version

Test 0001015 Test 0001016

Slot Upgrade Way

0 Reboot

2 Reboot

3 Reboot

4 Reboot

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

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

# (In IRF mode.) Perform a switchover.

<Sysname> issu run switchover

Upgrade summary according to following table:

flash:/boot-t0001015.bin

Running Version New Version

Test 0001015 Test 0001016

flash:/system-t0001015.bin

Running Version New Version

Test 0001015 Test 0001016

Chassis Slot Switchover Way

2 1 Global active standby MPU switchover

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

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

Table 8 Command output

Field	Description
Switchover Way	Switchover method: · Active standby process switchover—Switch from the active process to the standby process. · (In standalone mode.) Active standby MPU switchover—Switch from the active MPU to the standby MPU. · (In IRF mode.) Global active standby MPU switchover—Switch from the global active MPU to a global standby MPU.

Field

Description

Switchover Way

Switchover method:

· Active standby process switchover—Switch from the active process to the standby process.

· (In standalone mode.) Active standby MPU switchover—Switch from the active MPU to the standby MPU.

· (In IRF mode.) Global active standby MPU switchover—Switch from the global active MPU to a global standby MPU.

For more information about the command output, see Table 5.

Related commands

issu load

reset install log-history oldest

Use reset install log-history oldest to clear ISSU log entries.

Syntax

reset install log-history oldest log-number

Views

User view

Predefined user roles

network-admin

Parameters

log-number: Specifies the number of ISSU 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 ISSU log entries.

<Sysname> reset install log-history oldest 2

Related commands

display install log

reset install rollback oldest

Use reset install rollback oldest to clear ISSU rollback points.

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

CAUTION:

This command clears the specified rollback point and all rollback points earlier than the specified rollback point. You will be unable to roll back the configuration to the status when any of these rollback points was created.

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

ISSU commands

display issu state

display version comp-matrix file

install deactivate

install rollback to

issu accept

issu commit

issu load

issu rollback-timer

Cloud & AI

InterConnect

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Resources

Partner Business Management

Company Information

News & Events

Contact Us