Table of Contents

Related Documents

08-ISSU commands

Title	Size	Download
08-ISSU commands	231.75 KB

ISSU commands

Field	Description
Active packages on slot n	Active software images on the card in the specified slot. (In standalone mode.)
Active packages on chassis m slot n	Active software images on the card in the specified slot of the specified member. (In IRF mode.)
flash:/boot.bin	Software image package path.
[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.
Platform version	Comware version number.
Product version	Release number of the product.
Supported board	Cards supported by the software image: · cen—Mother board. · mpu—MPU. · lc—LPU. · sfc—Switching fabric module.
[Component]	Information about components included in the image file.

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 this option, the command is applied to all cards in the device. (In standalone mode.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member. If you do not specify this option, the command is applied to all cards in the IRF fabric. (In IRF mode.)

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

Usage guidelines

To change the backup startup software image list, you must use the boot-loader file command.

For more information about setting backup startup software images, see Fundamental Configuration Guide.

Examples

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

<Sysname> display install backup

Backup startup software images on slot 1:

flash:/boot-a0201.bin

flash:/system-a0201.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-a0201.bin

flash:/system-a0201.bin

# Display detailed information about backup startup software images.

<Sysname> display install backup verbose

Backup startup software images on chassis 1 slot 1:

flash:/boot-a0201.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: boot

Platform version: 7.1

Product version: Beta 1330

Supported board: mpu

[Component]

Component: boot

Description: boot package

flash:/system-a0201.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: system

Platform version: 7.1

Product version: Beta 1330

Supported board: mr, lc, sfc

[Component]

Component: system

Description: system package

For information about the command output, see Table 1.

Related commands

· boot-loader file

· display install committed

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 this option, the command is applied to all cards in the device. (In standalone mode.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member. If you do not specify this option, the command is applied to all cards in the IRF fabric. (In IRF mode.)

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

Usage guidelines

When you execute the install commit command, the system refreshes the main startup software image set to use the currently active software images as the main startup software images.

The boot-loader file command can also change the main startup software image set.

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

Examples

# Display the main startup software images.

<Sysname> display install committed

Committed packages on slot 1:

flash:/boot-a0201.bin

flash:/system-a0201.bin

flash:/feature.bin

# Display detailed information about main startup software images.

<Sysname> display install committed verbose

Committed packages on slot 1:

flash:/boot-a0201.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: boot

Platform version: 7.1

Product version: Beta 1330

Supported board: mr, lc, sfc

[Component]

Component: boot

Description: boot package

flash:/system-a0201.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: system

Platform version: 7.1

Product version: Beta 1330

Supported board: mr, lc, sfc

[Component]

Component: system

Description: system package

flash:/feature.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: test

Platform version: 7.1

Product version: Beta 1330

Supported board: mr, lc, sfc

[Component]

Component: test

Description: test 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.

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 this option, the command is applied to all cards in the device. (In standalone mode.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member. If you do not specify this option, the command is applied to all cards in the IRF fabric. (In IRF mode.)

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

Usage guidelines

This command searches the root directories of the storage media for inactive images and displays information about the inactive images.

Examples

# Display brief information about inactive software images in the root directory of each storage medium.

<Sysname> display install inactive

Inactive packages on slot 1:

flash:/feature.bin

# Display detailed information about inactive software images in the root directory of each storage medium.

<Sysname> display install inactive verbose

Inactive packages on slot 1:

flash:/feature.bin

[Package]

Vendor: H3C

Product: XXXX

Service name: test

Platform version: 7.1

Product version: Beta 1330

Supported board: mr, lc, sfc

[Component]

Component: test

Description: test 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 the name of an .ipe file in the root directory of a storage medium. It must be a case-insensitive string of up to 63 characters that uses one of the following formats:

· storage-medium:/base-filename.ipe on the active MPU (in standalone mode) or global active MPU (in IRF mode).

· slotn#storage-medium:/base-filename.ipe on the standby MPU, for example, slot1#flash:/a.ipe. (In standalone mode.)

· chassismslotn#storage-medium:/base-filename.ipe on a standby MPU, for example, chassis1slot1#flash:/a.ipe. (In IRF mode.)

Usage guidelines

An .ipe file contains one or more software images. You can use the software images for a software upgrade.

Examples

# Display information about the .ipe file flash:/test.ipe.

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

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

H3C Device images in IPE:

Images in IPE:

boot.bin

system.bin

Related commands

display install package

display install job

Use display install job to display the ongoing ISSU activate, deactivate, or rollback operation.

Syntax

display install job

Views

Any view

Predefined user roles

network-admin

network-operator

Examples

# (In standalone mode.) Display the ongoing ISSU activate, deactivate, or rollback operation.

<Sysname> display install job

JobID:5

Action:install activate flash:/ssh-feature.bin on slot 1

The output shows that the device is executing the install activate flash:/ssh-feature.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:/ssh-feature.bin on chassis 1 slot 1

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

display install log

Use display install log to display ISSU logs.

Syntax

display install log [ log-id ] [ verbose ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

log-id: Specifies a log by its ID. If you do not specify this argument, all software upgrade-related logs are displayed.

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

Usage guidelines

The device tracks every ISSU operation by generating a log for it, whether the operation is successful or not. A log is uniquely identified by an ID.

The device supports up to 50 ISSU logs. When the number of logs reaches this limit, the oldest log will be replaced by a newly generated log.

Examples

# Display all ISSU logs.

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

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

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.

# Displays detailed information about ISSU log 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:29.

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

Install activate flash:/ssh.bin on slot 1

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 the name of a software image file in the root directory of a storage medium. It must be a case-insensitive string of up to 63 characters that uses one of the following formats:

· storage-medium:/base-filename.bin on the active MPU (in standalone mode) or global active MPU (in IRF mode).

· slotn#storage-medium:/base-filename.bin on the standby MPU, for example, slot1#flash:/a.bin. (In standalone mode.)

· chassismslotn#storage-medium:/base-filename.bin on a standby MPU, for example, chassis1slot1#flash:/a.bin. (In IRF mode.)

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

all: Specifies all software image files in the root directories of the storage media 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 software image file system.bin.

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

flash:/system.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: system

Platform version: 7.1.022

Product version: Beta 1330

Supported board: mpu

# Display detailed information about software image file system.bin.

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

flash:/system.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: system

Platform version: 7.1.022

Product version: Beta 1330

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.

Usage guidelines

You can use the display install rollback command to view available rollback points.

Using issu series commands for an ISSU clears all rollback points created by an install command.

Examples

# 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

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 name in the basename.extension format without storage medium or directory information. The file name must be a case-insensitive string of up to 63 characters.

slot slot-number: Specifies a card by its slot number. If you do not specify this option, the command is applied to all cards in the device. (In standalone mode.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member. If you do not specify this option, the command is applied to all cards in the IRF fabric. (In IRF mode.)

Usage guidelines

This command only supports full match for file names. To get package information for a file or component, you must enter the complete form of the component or file name.

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

When the system notifies you of a component or file error, use this command to display all software image files that include the component or file on certain storage media. This helps you determine whether a software upgrade is required.

Examples

# Display all software image files that include file sshc.cli.

<Sysname> display install which file sshc.cli

File sshc.cli is in following packages on slot 1:

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

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

flash:/system.bin

[Package]

Vendor: xxx

Product: xxxx

Service name: ssh

Platform version: 7.1.022

Product version: Beta 1330

Supported board: mr, lc, sfc

For information about the command output, see Table 1.

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

# (On a standalone device or single-chassis IRF fabric.) Display ISSU status information when no upgrade is in process.

<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.041, Demo 2402

system: 7.1.041, Demo 2402

ssh: 7.1.041, Demo 2402

Current software images:

flash:/boot.bin

flash:/system.bin

flash:/ssh.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.041, Demo 2402

system: 7.1.041, Demo 2402

ssh: 7.1.041, Demo 2402

Previous software images:

flash:/boot.bin

flash:/system.bin

flash:/ssh.bin

Upgrade version list:

boot: 7.1.041, Demo 2403

system: 7.1.041, Demo 2403

ssh: 7.1.041, Demo 2403

Upgrade software images:

flash:/boot02.bin

flash:/system04.bin

flash:/ssh04.bin

# (On a single-chassis IRF fabric.) Display ISSU status information when 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:

chassis 1 slot 1

Previous version list:

boot: 7.1.041, Demo 2402

system: 7.1.041, Demo 2402

ssh: 7.1.041, Demo 2402

Previous software images:

flash:/boot.bin

flash:/system.bin

flash:/ssh.bin

Upgrade version list:

boot: 7.1.041, Demo 2403

system: 7.1.041, Demo 2403

ssh: 7.1.041, Demo 2403

Upgrade software images:

flash:/boot02.bin

flash:/system04.bin

flash:/ssh04.bin

# (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.041, Demo 2402

system: 7.1.041, Demo 2402

ssh: 7.1.041, Demo 2402

Previous software images:

flash:/boot.bin

flash:/system.bin

flash:/ssh.bin

Upgrade version list:

system: 7.1.041, Demo 2403

ssh: 7.1.041, Demo 2403.

Upgrade software images:

flash:/system02.bin

flash:/ssh02.bin

# (On a multichassis IRF fabric.) Display ISSU status information on the original master after the issu load command is completed.

<Sysname> 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.041, Demo 2402

system: 7.1.041, Demo 2402

ssh: 7.1.041, Demo 2402

Previous software images:

flash:/boot.bin

flash:/system.bin

flash:/ssh.bin

Upgrade version list:

system: 7.1.041, Demo 2403

ssh: 7.1.041, Demo 2403

Upgrade software images:

flash:/system04.bin

flash:/ssh04.bin

Table 2 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 process. · Unknown—An upgrade is in process. This value might appear when you execute the command on an original standby MPU.
Compatibility	Version compatibility: · Compatible. · Incompatible. · Unknown—No upgrade is in process.
Work state	Operating state of the device: · Normal—The device is operating correctly. · Independent active—When you perform an ISSU for an incompatible version, the standby MPU that is upgraded first enters this mode. In this mode, the two MPUs of the device are running different software versions.
Upgrade method	Upgrade mode: · Card by card—MPUs are upgraded one at a time. · Chassis by chassis—One or more subordinate members are upgraded first, and then the original master and the remaining subordinate members are upgraded. This mode is available only for a multichassis IRF fabric.
Upgraded slot	Upgraded cards. During a rollback, the value of this field is Unknown. (In standalone mode.)
Current upgrading slot	Cards that are being upgraded. During a rollback, the value of this field is Unknown. (In standalone mode.)
Upgraded chassis	Upgraded members. During a rollback, the value of this field is Unknown. (In IRF mode.)
Current upgrading chassis	Members that are being upgraded. During a rollback, the value of this field is Unknown. (In IRF mode.)
Previous version list	Software versions running on the device before the ISSU. If you execute this command on an original standby MPU during an ISSU for an incompatible version, the value of this field is Unknown.
Previous software images	Software images running on the device before the ISSU. If you execute this command on an original standby MPU during an ISSU for an incompatible version, the value of this field is Unknown.
Upgrade version list	Software versions to upgrade to. If you execute this command on an original standby MPU during an ISSU for an incompatible version, the value of this field is Unknown.
Upgrade software images	Software images used for the upgrade. If you execute this command on an original standby MPU during an ISSU for an incompatible version, the value of this field is Unknown.

Related commands

· issu accept

· issu commit

· issu load

· issu rollback

· issu run switchover

display version comp-matrix

Use display version comp-matrix to display version compatibility information.

Syntax

display version comp-matrix

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 feature image files. You can specify a space-separated list of up to 30 feature image files.

filename: Specifies the name of a software image file on the active MPU (in standalone mode) or global active MPU (in IRF mode), in the format of storage-medium:/base-filename.bin. It must be a case-insensitive string of up to 63 characters and cannot contain chassis or slot information. The file must be saved in the root directory.

ipe-filename: Specifies the name of an .ipe file on the active MPU (in standalone mode) or global active MPU (in IRF mode), in the format of storage-medium:/base-filename.ipe. It must be a case-insensitive string of up to 63 characters and cannot contain chassis or slot information. The file must be saved in the root directory.

Usage guidelines

If you do not specify any image files, the command displays compatibility information for the running software images.

If you specify image files, the command displays compatibility information for the specified images. The command also displays the recommended ISSU methods for upgrading the running images to the specified images.

Examples

# Display compatibility information for the running images.

<Sysname> display version comp-matrix

Boot image: flash:/boot-a7122.bin

Version:

7.1.031

System image: flash:/system-a7122.bin

Version:

V700R003B41D001

Version compatibility list:

V700R003B41D001

Version dependency boot list:

7.1.031

Feature image: flash:/cmw710-cfa-a7124.bin

Version:

V700R003B41D002

Version compatibility list:

V700R003B41D001

Version dependency system list:

V700R003B41D001

V700R003B41D002

# Display compatibility information for flash:/boot-e2205.bin, flash:/system-e2205.bin, and flash:/dhcp-e2205.re.bin, as well as the recommended ISSU method. (In this example, the specified versions are incompatible with the running images.)

<Sysname> display version comp-matrix file boot flash:/boot-e2205.bin system flash:/system-e2205.bin feature flash:/dhcp-e2205.re.bin

Verifying the file flash:/dhcp-e2205.re.bin on slot 0...Done.

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

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

Boot image: flash:/boot-e2205.bin

Version:

7.1.035

System image: flash:/system-e2205.bin

Version:

V700R003B02D002

Version compatibility list:

V700R003B02D002

Version dependency boot list:

7.1.035

Feature image: flash:/dhcp-e2205.re.bin

Version:

V700R003B02D002

Version compatibility list:

V700R003B02D002

Version dependency system list:

V700R003B02D002

V700R003B02D004

Incompatible upgrade.

# (In standalone mode.) Display compatibility information for cmw710-cfa-a7125.bin and the recommended ISSU methods. (In this example, the specified version is compatible with the running version.)

<Sysname> display version comp-matrix file feature flash:/cmw710-cfa-a7125.bin

Verifying the file flash:/cmw710-cfa-a7125.bin on slot 0.....Done.

Feature image: flash:/cmw710-cfa-a7125.bin

Version:

V700R003B31D002

Version compatibility list:

V700R003B31D001

V700R003B31D002

Version dependency system list:

V700R003B31D001

V700R003B31D002

Slot Upgrade Way

0 Service Upgrade

1 Service Upgrade

1.1 Service Upgrade

4 Service Upgrade

Influenced service according to following table on slot 0:

flash:/cmw710-cfa-a7125.bin

CFA

Influenced service according to following table on slot 4:

flash:/cmw710-cfa-a7125.bin

CFA

Influenced service according to following table on slot 1:

flash:/cmw710-cfa-a7125.bin

CFA

Influenced service according to following table on slot 1.1:

flash:/cmw710-cfa-a7125.bin

CFA

# (In IRF mode.) Display compatibility information for cmw710-cfa-a7122.bin and the recommended ISSU methods. (In this example, the specified version is compatible with the running version.)

<Sysname> display version comp-matrix file feature flash:/cmw710-cfa-a7122.bin

Verifying the file flash:/cmw710-cfa-a7125.bin on slot 0.....Done.

Feature image: flash:/cmw710-cfa-a7122.bin

Version:

V700R003B41D002

Version compatibility list:

V700R003B41D001

V700R003B41D002

Version dependency system list:

V700R003B41D001

V700R003B41D002

Chassis Slot Upgrade Way

1 0 Service Upgrade

1 0.1 Service Upgrade

1 7 Service Upgrade

1 9 Service Upgrade

2 0 Service Upgrade

2 0.1 Service Upgrade

2 1 Service Upgrade

2 6 Service Upgrade

Influenced service according to following table on chassis 1 slot 0:

flash:/cmw710-cfa-a7122.bin

CFA

Influenced service according to following table on chassis 1 slot 7:

flash:/cmw710-cfa-a7122.bin

CFA

Influenced service according to following table on chassis 1 slot 9:

flash:/cmw710-cfa-a7122.bin

CFA

Influenced service according to following table on chassis 1 slot 0.1:

flash:/cmw710-cfa-a7122.bin

CFA

Influenced service according to following table on chassis 2 slot 0:

flash:/cmw710-cfa-a7122.bin

CFA

Influenced service according to following table on chassis 2 slot 1:

flash:/cmw710-cfa-a7122.bin

CFA

Influenced service according to following table on chassis 2 slot 6:

flash:/cmw710-cfa-a7122.bin

CFA

Influenced service according to following table on chassis 2 slot 0.1:

flash:/cmw710-cfa-a7122.bin

CFA

Table 3 Command output

Field	Description
Verifying the file	The system was verifying the validity of the file.
Version compatibility list	· When displayed under a system image, this field shows all system image versions that are compatible with the system image. · When displayed under a feature image, this field shows all feature image versions that are compatible with the feature image.
Version dependency boot list	Boot image versions that support the system image. To install the system image, you must install one of the boot image versions that is in the list.
Version dependency system list	System image versions that support the feature image. To install the feature image, you must install one of the system image versions that is in the list.
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.
Chassis	Member ID of the device in the IRF fabric. This field is displayed only for compatible versions in IRF mode.
Slot	Slot number of the card. This field is displayed only for compatible versions.
Upgrade Way	ISSU methods: · Service Upgrade—Service-level incremental upgrade. · File Upgrade—File-level incremental upgrade. · ISSU Reboot—Reboots CPUs to complete the upgrade. · Reboot—Reboots the entire device to complete the upgrade. · Sequence Reboot—Upgrades the switching fabric modules one by one. This method applies only when the device has switching fabric modules that support this upgrade method. 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 ISSU operation.

Syntax

install abort

Views

User view

Predefined user roles

network-admin

Usage guidelines

After you issue the install activate, install add, install commit, install deactivate, install remove, or install rollback to command, the system creates a software image management job. To monitor and manage software image management jobs, the system assigns each job a unique job ID. Each job ID represents a single command.

You can abort only a software image activate or deactivate operation that is being executed.

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

Examples

# Abort a software image operation.

<Sysname> install abort

Related commands

display install job

install activate

Use install activate to activate software images, or identify the recommended 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 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 chassis chassis-number slot slot-number

Views

User view

Predefined user roles

network-admin

Parameters

boot: Specifies a boot image file. For more information about software images, see Fundamental Configuration Guide.

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.

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

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

chassis chassis-number slot slot-number: Specifies a card on an IRF member. (In IRF mode.)

test: Only checks for 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.

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 standalone mode, follow these guidelines:

· If you specify the active MPU, the command takes effect on the active MPU and all LPUs.

· If you specify the standby MPU, the command takes effect only on the standby MPU.

· If the specified files are not saved on the MPU to be upgraded, the command copies the images to the MPU automatically.

In IRF mode, follow these guidelines:

· If you specify the global active MPU, the command takes effect on the global active MPU and all LPUs.

· If you specify a standby MPU, the command takes effect on the standby MPU.

· If the specified files are not saved on the MPU to be upgraded, the command copies the images to the MPU 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 check the synchronization progress, use the display device and display mdc commands. The synchronization is completed when the following requirements are met:

· All cards of the subordinate device are in normal state.

· All MDCs are in active state.

Examples

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

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

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

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

Upgrade summary according to following table:

flash:/ssh2.bin

Running Version New Version

Beta 1330 Beta 1331

Slot Upgrade Way

1 Service Upgrade

Influenced service according to following table:

flash:/ssh2.bin

SSH IFMGR CFA LAGG

The output shows that an incremental upgrade is recommended. The SSH, IFMGR, CFA, and LAGG modules will be rebooted during the upgrade.

# (In IRF mode.) Identify the ISSU method for feature upgrade with ssh2.bin on the standby MPU in slot 1 of IRF member 1 and the upgrade impact.

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

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

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

Upgrade summary according to following table:

flash:/ssh2.bin

Running Version New Version

Beta 1330 Beta 1331

Chassis Slot Upgrade Way

1 1 Service Upgrade

Influenced service according to following table:

flash:/ssh2.bin

SSH IFMGR CFA LAGG

The output shows that an incremental upgrade is recommended. The SSH, IFMGR, CFA, and LAGG modules will be rebooted during the upgrade.

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

<Sysname> install activate system flash:/system.bin feature flash:/feature.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:/feature.bin to slot1#flash:/feature.bin......Done.

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

Upgrade summary according to following table:

flash:/system.bin

Running Version New Version

Beta 1330 Beta 1331

flash:/feature.bin

Running Version New Version

None Beta 1330

Slot Upgrade Way

1 Service Upgrade

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

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

# (In IRF mode.) Activate the feature images in file feature.bin on the global standby MPU in slot 0 of IRF member 1.

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

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

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

Upgrade summary according to following table:

flash:/route-feature.bin

Running Version New Version

None Beta 1330

Chassis Slot Upgrade Way

1 1 Service Upgrade

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

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

Table 4 Command output

Field	Description
Copying file A to B......Done.	The system is automatically copying files for the upgrade. This message is displayed only when you activate an image for a standby MPU.
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.
Chassis	Member ID of the device in the IRF fabric. (In IRF mode.)
Slot	Number of the slot where the card resides.
Upgrade Way	ISSU methods: · Service Upgrade—Service-level incremental upgrade. · File Upgrade—File-level incremental upgrade. The upgrade involves only hidden program files and does not affect the operation of the system or services. · ISSU Reboot—Reboots CPUs to complete the upgrade. · Reboot—Reboots the entire device to complete the upgrade. · Sequence Reboot—Upgrades the switching fabric modules one by one. This method applies only when the device has switching fabric modules that support this upgrade method. 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 medium-name:

Views

User view

Predefined user roles

network-admin

Parameters

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

medium-name: Specifies the name of the destination storage medium for the software images.

· To specify a storage medium on the standby MPU in standalone mode, use the format slotslot-number#storage-medium.

· To specify a storage medium on a global standby MPU in IRF mode, use the format chassischassis-number#slotslot-number#storage-medium.

Usage guidelines

To use install commands for upgrade, 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:/route.ipe flash:

Verifying the file flash:/route.ipe on slot 0......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 confirm the software changes.

Syntax

install commit

Views

User view

Predefined user roles

network-admin

Usage guidelines

Before you use this command, view the release notes to determine whether the images require licenses. If the images require a license, make sure the device has valid licenses installed for the images.

During a reboot or ISSU reboot upgrade, the install activate command changes both the running software and the main startup software image set. You do not need to use the install commit command to confirm the software changes.

During an incremental upgrade, the install activate command changes only the running software. For the changes to take effect after a reboot, you must use the install commit command to confirm the software changes.

The install deactivate and install rollback commands change only the running software. To keep the changes after a reboot, you must use the install commit command to confirm the software changes.

Both the install commit and boot-loader file commands change main startup software images. To change backup startup images 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 and image sets, see Fundamental Configuration Guide.

Examples

# Confirm the 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> slot slot-number

install deactivate patch filename slot slot-number

In IRF mode:

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

install deactivate patch filename chassis chassis-number 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.

filename: Specifies the name of a software image file on the active MPU (in standalone mode) or global active MPU (in IRF mode). Use the format storage-medium:/base-filename.bin. It can be a case-insensitive string of up to 63 characters and cannot contain chassis or slot information. The file must be stored in the root directory.

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

chassis chassis-number slot slot-number: Specifies a card on an IRF member. ( In IRF mode.)

Usage guidelines

You can deactivate only feature and patch images that are active.

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

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 check the synchronization progress, use the display device and display mdc commands. The synchronization is completed when the following requirements are met:

· All cards of the subordinate device are in normal state.

· All MDCs are in active state.

Examples

# (In standalone mode.) Deactivate the patch images in route-patch.bin on slot 0.

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

# (In IRF mode.) Deactivate the patch images in route-patch.bin on slot 0 of IRF member 1.

<Sysname> install deactivate feature flash:/route-feature.bin chassis 1 slot 0

Related commands

· display install active

· display install inactive

install remove

Use install remove to remove inactive software images.

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 this option, the command is applied to all cards in the device. (In standalone mode.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member. If you do not specify this option, the command is applied to all cards in the IRF fabric. (In IRF mode.)

filename: Specifies the name of a software image file on the active MPU (in standalone mode) or global active MPU (in IRF mode). Use the format storage-medium:/base-filename.bin. It must be a case-insensitive string of up to 63 characters and cannot contain chassis or slot information. The file must be saved in the root directory.

inactive: Removes all inactive software image files in the root directories of the specified storage media.

Usage guidelines

This command deletes only inactive software image files saved in the root directories of the specified storage media.

Removing a software image deletes the image file from the device permanently. You cannot use the install rollback to command to revert the operation, or use the install abort command to abort the operation.

Examples

# Remove inactive software image file flash:/ssh-feature.bin.

<Sysname> install remove flash:/ssh-feature.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 software images that were running before the ISSU.

Usage guidelines

The system creates a rollback point for each service or file upgrade that is performed through an activate or deactivate operation. The rollback points are retained until any of the following events occur:

· An ISSU reboot or reboot upgrade is performed.

· The install commit command is executed.

After an ISSU reboot or reboot upgrade is performed, you can roll back the running software images only to the status before any activate or deactivate operations were performed.

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

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

The device supports a maximum of 50 rollback points. The earliest rollback point is removed if this limit has been reached when a rollback point is created.

Patch images do not support rollback.

Examples

# Roll back the software to rollback point 1.

<Sysname>install rollback to 1

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

<Sysname> display install active

Active packages on slot 1:

flash:/boot-a0201.bin

flash:/system-a0201.bin

flash:/ssh-feature-a0201.bin

<Sysname> display install rollback

Install rollback information 1 on slot 1:

Updating from no package

to flash:/ssh-feature-a0201.bin.

The output shows that currently three images are active but only two of them are confirmed. Image flash:/ssh-feature-a0201.bin is not confirmed yet.

<Sysname> install rollback to original

<Sysname> display install active

Active packages on slot 1:

flash:/boot-a0201.bin

flash:/system-a0201.bin

<Sysname> display install committed

Committed packages on slot 1:

flash:/boot-a0201.bin

flash:/system-a0201.bin

The output shows the SSH feature has been rolled back to the original version. Image flash:/ssh-feature-a0201.bin has been removed.

Related commands

display install rollback

install verify

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

Syntax

install verify

Views

User view

Predefined user roles

network-admin

Usage guidelines

If some software images are not integral or some activated/deactivated software images are not confirmed, a switchover might not occur as expected, and the MPUs might run different versions of software images after a reboot or even cannot reboot correctly. (In standalone mode.)

To solve the problem, perform one of the following tasks:

· Download and install the software images again to ensure software integrity.

· Use the install activate, install deactivate, and install commit commands as appropriate to guarantee software image consistency.

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-a0101.bin on slot 0.....................Done.

flash:/boot-a0101.bin verification successful.

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

flash:/system-a0101.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-a0101.bin on slot 1.....................Done.

flash:/boot-a0101.bin verification successful.

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

flash:/system-a0101.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 chassis 1 slot 0:

Start to check active package completeness.

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

flash:/boot-a0101.bin verification successful.

Verifying the file flash:/system-a0101.bin on chassis 1 slot 0.........Done.

flash:/system-a0101.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 1 slot 1:

Start to check active package completeness.

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

flash:/boot-a0101.bin verification successful.

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

flash:/system-a0101.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.

You can execute the issu commit command to finish the ISSU process without executing this command.

The issu accept command does not apply to the ISSU to an incompatible version. The system will display an error message if you execute this command during this type of ISSU.

Examples

# Accept the upgrade to a compatible version.

<Sysname> issu accept

Related commands

· issu load

· issu run switchover

issu commit

Use issu commit to complete an ISSU upgrade to a compatible version.

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 (multichassis):

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. (Single-chassis IRF fabric.)

chassis chassis-number: Specifies the member ID of the original master or a subordinate member that has not been upgraded. (Multichassis IRF fabric.)

Usage guidelines

On a standalone device or a single-member IRF fabric, this command ends the ISSU process. When this command is completed, the ISSU status changes to Init, and the ISSU process cannot be rolled back.

On a multichassis IRF fabric, use this command to upgrade subordinate members (including the original master) in turn. You must wait for the upgraded subordinate member to start up again and join the IRF fabric before upgrading another subordinate member. After all members are upgraded, the ISSU status changes to Init. The ISSU process ends and cannot be rolled back.

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 check the synchronization progress, use the display device and display mdc commands. The synchronization is completed when the following requirements are met:

· All cards of the subordinate device are in normal state.

· All MDCs are in active state.

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:/feature.bin

Running Version New Version

Alpha 7122 Alpha 7123

Slot Upgrade Way

0 Service Upgrade

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

# (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 members that have not been upgraded to a compatible version. (In this example, the member ID of the original master is 3. Members with the IDs 1 and 4 are not upgraded either.)

<Sysname> issu commit chassis 3

Copying file flash:/feature.bin to chassis3#slot1#flash:/feature.bin...Done.

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

Upgrade summary according to following table:

flash:/feature.bin

Running Version New Version

Alpha 7122 Alpha 7123

Chassis Slot Upgrade Way

3 0 Service Upgrade

3 1 Service Upgrade

3 2 Service Upgrade

3 3 Service Upgrade

3 4 Service Upgrade

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

<Sysname> issu commit chassis 4

Copying file flash:/feature.bin to chassis4#slot0#flash:/feature.bin...Done.

Verifying the file flash:/feature.bin on chassis 4 slot 0..............Done.

Copying file flash:/feature.bin to chassis4#slot1#flash:/feature.bin...Done.

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

Upgrade summary according to following table:

flash:/feature.bin

Running Version New Version

Alpha 7122 Alpha 7123

Chassis Slot Upgrade Way

4 0 Service Upgrade

4 1 Service Upgrade

4 2 Service Upgrade

4 3 Service Upgrade

4 4 Service Upgrade

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

<Sysname> issu commit chassis 1

Copying file flash:/feature.bin to chassis1#slot0#flash:/feature.bin...Done.

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

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

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

Upgrade summary according to following table:

flash:/feature.bin

Running Version New Version

Alpha 7122 Alpha 7123

Chassis Slot Upgrade Way

1 0 Service Upgrade

1 1 Service Upgrade

1 2 Service Upgrade

1 3 Service Upgrade

1 4 Service Upgrade

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

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

Upgrade summary according to following table:

flash:/feature.bin

Running Version New Version

Alpha 7122 Alpha 7123

Chassis Slot Upgrade Way

1 0 Service Upgrade

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

# (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 3.

Related commands

· issu accept

· issu load

· issu run switchover

issu load

On a standalone device, use issu load to load the upgrade images from the active MPU to the standby MPU as the main startup software images.

On an IRF fabric, use issu load to load the upgrade images from the global active MPU to standby MPUs as the main startup software images.

Syntax

In standalone mode:

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

issu load file ipe ipe-filename slot slot-number

In IRF mode (single-chassis):

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

issu load file ipe ipe-filename chassis chassis-number slot slot-number

In IRF mode (multichassis):

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

issu load file ipe ipe-filename chassis chassis-number&<1-3>

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.

filename: Specifies the name of a software image file on the active MPU (in standalone mode) or global active MPU (in IRF mode). Use the format storage-medium:/base-filename.bin. It must be a case-insensitive string of up to 63 characters and cannot contain chassis or slot information. The file must be saved in the root directory.

ipe-filename: Specifies the name of an .ipe file on the active MPU (in standalone mode) or global active MPU (in IRF mode). Use the format storage-medium:/base-filename.ipe. It must be a case-insensitive string of up to 63 characters and cannot contain chassis or slot information. The file must be saved in the root directory.

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. (Single-chassis IRF fabric.)

chassis chassis-number: Specifies the member ID of a subordinate member. For a compatible upgrade, you can specify only one member ID. For an incompatible upgrade, you can specify a space-separated list of up to three member IDs. (Multichassis IRF fabric.)

Usage guidelines

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.

To ensure a successful upgrade, perform the following tasks before you execute this command:

1. Use the display device command to verify that all cards are not in Fault state.

2. Use the display mdc command to verify that all MDCs are in active state.

When you execute this command, the system automatically checks the version compatibility, and then upgrades the specified MPUs with the specified software images.

Examples

# (In standalone mode.) Upgrade the standby MPU with the feature image file flash:/feature.bin. (In this example, the image is compatible with the running images.)

<Sysname> issu load file feature flash:/feature.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:/feature.bin on slot 0...Done.

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

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

Upgrade summary according to following table:

flash:/feature.bin

Running Version New Version

Alpha 7122 Alpha 7123

Slot Upgrade Way

1 Service Upgrade

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

# (In standalone mode.) Upgrade the standby MPU with the feature image file flash:/feature.bin. (In this example, the image is incompatible with the running images.)

<Sysname> issu load file feature flash:/feature.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:/feature.bin on slot 0...Done.

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

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

Upgrade summary according to following table:

flash:/feature.bin

Running Version New Version

Alpha 7122 Alpha 7123

Slot Upgrade Way

1 Reboot

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

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

<Sysname>issu load file feature flash:/feature.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:/feature.bin on slot 0...Done.

Upgrade summary according to following table:

flash:/feature.bin

Running Version New Version

Alpha 7122 Alpha 7123

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

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

<Sysname> issu load file feature flash:/feature.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:/feature.bin on slot 0...Done.

Upgrade summary according to following table:

flash:/feature.bin

Running Version New Version

Alpha 7122 Alpha 7123

Slot Upgrade Way

0 Reboot

2 Reboot

3 Reboot

4 Reboot

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

# (In IRF mode.) Upgrade member device 2 (a subordinate member) with the feature image file flash:/feature.bin. (In this example, the image is compatible with the running images. The member ID of the master is 1.)

<Sysname> issu load file feature flash:/feature.bin 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 the file flash:/feature.bin on chassis 1 slot 0...Done.

Copying file flash:/feature.bin to chassis2#slot0#flash:/feature.bin...Done.

Verifying the file flash:/feature.bin on chassis 2 slot 0...Done.

Copying file flash:/feature.bin to chassis2#slot1#flash:/feature.bin...Done.

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

Upgrade summary according to following table:

flash:/feature.bin

Running Version New Version

Alpha 7122 Alpha 7123

Chassis Slot Upgrade Way

2 0 Service Upgrade

2 1 Service Upgrade

2 2 Service Upgrade

2 3 Service Upgrade

2 4 Service Upgrade

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

# (In IRF mode.) Upgrade member devices 3 and 4 (subordinate members) with the feature image file flash:/feature.bin. (In this example, the image is incompatible with the running images. The member ID of the master is 1.)

<Sysname>issu load file feature flash:/feature.bin chassis 3 4

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

Copying file flash:/feature.bin to chassis3#slot0#flash:/feature.bin...Done.

Verifying the file flash:/feature.bin on chassis 3 slot 0...Done.

Copying file flash:/feature.bin to chassis3#slot1#flash:/feature.bin...Done.

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

Copying file flash:/feature.bin to chassis4#slot0#flash:/feature.bin...Done.

Verifying the file flash:/feature.bin on chassis 4 slot 0...Done.

Copying file flash:/feature.bin to chassis4#slot1#flash:/feature.bin...Done.

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

Upgrade summary according to following table:

flash:/feature.bin

Running Version New Version

Alpha 7122 Alpha 7123

Chassis Slot Upgrade Way

3 0 Reboot

3 1 Reboot

3 2 Reboot

3 3 Reboot

3 4 Reboot

4 0 Reboot

4 1 Reboot

4 2 Reboot

4 3 Reboot

4 4 Reboot

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

# (On a dual-MPU single-chassis IRF fabric.) Upgrade the global standby MPU on member device 1 with the feature image file flash:/feature.bin. (In this example, the image is compatible with the running images.)

<Sysname>issu load file feature flash:/feature.bin chassis 1 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:/feature.bin on chassis 1 slot 0...Done.

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

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

Upgrade summary according to following table:

flash:/feature.bin

Running Version New Version

Alpha 7122 Alpha 7123

Chassis Slot Upgrade Way

1 1 Service Upgrade

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

# (On a dual-MPU single-chassis IRF fabric.) Upgrade the global standby MPU on member device 1 with the feature image file flash:/feature.bin. (In this example, the image is incompatible with the running images.)

<Sysname>issu load file feature flash:/feature.bin chassis 1 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:/feature.bin on chassis 1 slot 0...Done.

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

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

Upgrade summary according to following table:

flash:/feature.bin

Running Version New Version

Alpha 7122 Alpha 7123

Chassis Slot Upgrade Way

1 1 Reboot

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

# (On a single-MPU single-chassis IRF fabric.) Upgrade the MPU on member device 1 with the feature image file flash:/feature.bin. (In this example, the image is compatible with the running images.)

<Sysname>issu load file feature flash:/feature.bin chassis 1 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:/feature.bin on chassis 1 slot 0...Done.

Upgrade summary according to following table:

flash:/feature.bin

Running Version New Version

Alpha 7122 Alpha 7123

Chassis Slot Upgrade Way

1 0 Service Upgrade

1 2 Service Upgrade

1 3 Service Upgrade

1 4 Service Upgrade

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

# (On a single-MPU single-chassis IRF fabric.) Upgrade the MPU on member device 1 with the feature image file flash:/feature.bin. (In this example, the image is incompatible with the running images.)

<Sysname>issu load file feature flash:/feature.bin chassis 1 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:/feature.bin on chassis 1 slot 0...Done.

Upgrade summary according to following table:

flash:/feature.bin

Running Version New Version

Alpha 7122 Alpha 7123

Chassis Slot Upgrade Way

1 0 Reboot

1 2 Reboot

1 3 Reboot

1 4 Reboot

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

Table 5 Command output

Field	Description
Copying file A to B......Done.	The system is automatically copying files for the upgrade. This message is displayed only when you activate a image for a standby MPU.
Verifying the file	The system was verifying the validity of the file.
Chassis	Member ID of the device in the IRF fabric. (In IRF mode.)
Slot	Slot number of the card.
Upgrade Way	ISSU method: · Service Upgrade—Service-level incremental upgrade. · File Upgrade—File-level incremental upgrade. · ISSU Reboot—Reboots CPUs to complete the upgrade. · Reboot—Reboots the entire device to complete the upgrade. · Sequence Reboot—Upgrades the switching fabric modules one by one. This method applies only when the device has switching fabric modules that support this upgrade method. This field is displayed only for compatible versions. For more information about ISSU methods, see Fundamentals Configuration Guide.

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:

· Loading.

· Loaded.

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

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

· Accepted.

If you perform a manual rollback while the ISSU is in Loading state, the rollback might fail. Use the display version command to check the operation result.

When an ISSU to an incompatible version is in Switching state, you cannot perform a manual rollback.

When the ISSU is in Committing state, rollback is not supported.

For a multichassis IRF fabric, a rollback performed after you execute the issu run switchover command cancels only the upgrades. The master/subordinate switchover operation is not canceled.

If multiple cards have been upgraded, a rollback operation rolls back all upgraded cards to their original versions.

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 interval is 45 minutes.

Views

System view

Predefined user roles

network-admin

Parameters

minutes: Specifies the automatic-rollback interval in minutes, in the range of 0 to 120. Setting it to 0 disables automatic rollback.

Usage guidelines

Automatic software version rollback is only available on a dual-MPU device (in standalone mode), a multichassis IRF fabric, or a single-chassis dual-MPU IRF fabric during an ISSU to a compatible version.

When you execute the issu run switchover command in a scenario where automatic rollback is supported, 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.

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 on a standalone device or single-chassis IRF fabric to perform an active/standby switchover during an ISSU process.

Use issu run switchover on a multichassis IRF fabric to perform an active/standby switchover during an ISSU process.

Syntax

issu run switchover

Views

User view

Predefined user roles

network-admin

Usage guidelines

Use this command only if the system has a minimum of two MPUs.

In a compatible upgrade, the command upgrades the LPUs and switching fabric modules in addition to the MPUs.

In an incompatible upgrade, the command upgrades all cards except for the upgraded MPU or member device.

To ensure a successful upgrade, perform the following tasks before you execute this command in IRF mode:

1. Use the display device command to verify that all cards are not in Fault state.

2. Use the display mdc command to verify that all MDCs are in active state.

Examples

# (On a dual-MPU standalone 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:/feature.bin

Running Version New Version

Alpha 7122 Alpha 7123

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

# (On a dual-MPU standalone 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:/feature.bin

Running Version New Version

Alpha 7122 Alpha 7123

Slot Upgrade Way

0 Reboot

2 Reboot

3 Reboot

4 Reboot

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

# (On a multichassis IRF fabric.) Perform a master/subordinate switchover during an ISSU to a compatible version.

<Sysname> issu run switchover

Upgrade summary according to following table:

flash:/feature.bin

Running Version New Version

Alpha 7122 Alpha 7123

Chassis Slot Switchover Way

1 0 Active standby process switchover

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

# (On a multichassis IRF fabric.) Perform a master/subordinate switchover and upgrade members that have not been upgraded during an ISSU to an incompatible version. In this example, the master (with the ID 1) and the subordinate member with the ID 2 have not been upgraded.

<Sysname> issu run switchover

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

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

Copying file flash:/feature.bin to chassis2#slot0#flash:/feature.bin...Done.

Verifying the file flash:/feature.bin on chassis 2 slot 0...Done.

Copying file flash:/feature.bin to chassis2#slot1#flash:/feature.bin...Done.

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

Upgrade summary according to following table:

flash:/feature.bin

Running Version New Version

Alpha 7122 Alpha 7123

Chassis Slot Upgrade Way

1 0 Reboot

1 1 Reboot

1 2 Reboot

1 3 Reboot

1 4 Reboot

2 0 Reboot

2 1 Reboot

2 2 Reboot

2 3 Reboot

2 4 Reboot

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

# (On a dual-MPU single-chassis IRF fabric.) Perform a master/subordinate switchover and upgrade the LPUs and switching fabric modules during an ISSU to a compatible version.

<Sysname> issu run switchover

Upgrade summary according to following table:

flash:/feature.bin

Running Version New Version

Alpha 7122 Alpha 7123

Chassis Slot Switchover Way

1 0 Active standby process switchover

Chassis Slot Upgrade Way

1 2 Service Upgrade

1 3 Service Upgrade

1 4 Service Upgrade

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

# (On a dual-MPU single-chassis IRF fabric.) Perform a master/subordinate switchover during an ISSU to an incompatible version.

<Sysname> issu run switchover

Upgrade summary according to following table:

flash:/feature.bin

Running Version New Version

Alpha 7122 Alpha 7123

Chassis Slot Upgrade Way

1 0 Reboot

1 2 Reboot

1 3 Reboot

1 4 Reboot

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

Table 6 Command output

Field	Description
Copying file A to B......Done.	The system is automatically copying files for the upgrade. This message is displayed during an ISSU to an incompatible version only when the switchover operation upgrades cards that are not upgraded yet.
Verifying the file	The system was verifying the validity of the file.
Switchover Way	Switchover method: · Active standby process switchover—Switch from the active process to the standby process. · Active standby MPU switchover—Switch from the active MPU to the standby MPU. (In standalone mode.) · Global active standby MPU switchover—Switch from the global active MPU to a global standby MPU. (In IRF mode.)

For information about other fields' descriptions, see Table 3.

Related commands

issu load

reset install log-history oldest

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

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.

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

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

Using issu series commands for an ISSU clears all rollback points created by an install command.

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

install deactivate

install rollback to

issu commit

issu load

issu rollback-timer

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