ISSU commands -- display install active

Use display install active to display active software images.

Syntax

Centralized devices:

display install active [ verbose ]

Distributed devices in standalone mode:Centralized IRF devices:

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

Distributed devices 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. (Distributed devices in standalone mode.)

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

slot slot-number: Specifies an IRF member device by its member ID or specifies a PEX by its virtual slot number. On an IRF fabric, this command displays information for all member devices if you do not specify a member device. On an IRF 3 system, this command displays information for all IRF member devices and PEXs if you do not specify an IRF member device or PEX. (Centralized IRF devices.) (IRF 3 capable.)

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. (Distributed devices in IRF mode.) (IRF 3 incapable.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member device or specifies a PEX. The chassis-number argument represents the member ID of the IRF member device or the virtual chassis number of the PEX. The slot-number argument represents the slot number of the card or PEX. On an IRF fabric, this command displays information for all cards if you do not specify a card. On an IRF 3 system, this command displays information for all cards and PEXs if you do not specify a card or PEX. (Distributed devices in IRF mode.) (IRF 3 capable.)

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

Examples

# (Centralized devices.) Display active software images.

<Sysname> display install active

Active packages on the device:

flash:/boot.bin

flash:/system.bin

flash:/feature1.bin

# (Distributed devices in standalone mode.) (Centralized IRF devices.) Display active software images.

<Sysname> display install active

Active packages on slot 1:

flash:/boot.bin

flash:/system.bin

flash:/feature1.bin

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

# (Centralized devices.) Display detailed information about active software images.

<Sysname> display install active verbose

Active packages on the device:

flash:/boot.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: boot

Platform version: 7.1.070

Product version: Test 0001015

Supported board: cen

[Component]

Component: boot

Description: boot package

Software image signature: HP

flash:/system.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: system

Platform version: 7.1.070

Product version: Test 0001015

Supported board: cen

[Component]

Component: system

Description: system package

Software image signature: HP

flash:/feature1.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: test

Platform version: 7.1.070

Product version: Test 0001015

Supported board: cen

[Component]

Component: test

Description: test package

Software image signature: HP

# (Distributed devices in standalone mode.) (Centralized IRF devices.) Display detailed information about active software images.

<Sysname> display install active verbose

Active packages on slot 1:

flash:/boot.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: boot

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu

[Component]

Component: boot

Description: boot package

Software image signature: HP

flash:/system.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: system

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu

[Component]

Component: system

Description: system package

Software image signature: HP

flash:/feature1.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: test

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu

[Component]

Component: test

Description: test package

Software image signature: HP

# (Distributed devices 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: xxxx

Service name: boot

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu lpu

[Component]

Component: boot

Description: boot package

Software image signature: HP

flash:/system.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: system

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu lpu

[Component]

Component: system

Description: system package

Software image signature: HP

flash:/patch1.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: test

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu lpu

[Component]

Component: test

Description: test package

Software image signature: HP

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: · cen—Centralized device. · mpu—MPU. · lpu—Service card. · sfc—Switching fabric module.
[Component] | Information about components included in the image file.
Software image signature | Signature for the software image: · HP. · HP-US. · HPE. The Comware system can be upgraded from a version with the HP or HP-US signature to a version with the HPE signature. To upgrade the Comware system from a version without a signature to a version with the HPE signature, you must first complete one of the following tasks: · Patch the Comware system. · Upgrade the Comware system to a version with the HP or HP-US signature.

Related commands

install active

ISSU commands -- display install backup

Use display install backup to display backup startup software images.

Syntax

Centralized devices:

display install backup [ verbose ]

Centralized IRF devices:

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

Distributed devices in standalone mode:

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

Distributed devices in IRF mode:

display install backup [ chassis chassis-number slot slot-number [ cpu cpu-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. (Distributed devices in standalone mode.)

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

slot slot-number: Specifies an IRF member device by its member ID or specifies a PEX that has storage media by its virtual slot number. On an IRF fabric, this command displays information for all member devices if you do not specify a member device. On an IRF 3 system, this command displays information for all parent devices and all PEXs with storage media if you do not specify a parent device or PEX. (Centralized IRF devices.) (IRF 3 capable.)

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. (Distributed devices in IRF mode.) (IRF 3 incapable.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member device or specifies a PEX that has storage media. The chassis-number argument represents the member ID of the IRF member device or the virtual chassis number of the PEX. The slot-number argument represents the slot number of the card or PEX. On an IRF fabric, this command displays information for all cards if you do not specify a card. On an IRF 3 system, this command displays information for all cards and all PEXs with storage media if you do not specify a card or PEX. (Distributed devices in IRF mode.) (IRF 3 capable.)

cpu cpu-number: Specifies a CPU by its number. Use this option to display information for a security engine.

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

# (Centralized devices.) Display the backup startup software images.

<Sysname> display install backup

Backup startup software images on the device:

flash:/boot.bin

flash:/system.bin

# (Distributed devices in standalone mode.) (Centralized IRF devices.) Display the backup startup software images.

<Sysname> display install backup

Backup startup software images on slot 1:

flash:/boot.bin

flash:/system.bin

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

# (Centralized devices.) Display detailed information about backup startup software images.

<Sysname> display install backup verbose

Backup startup software images on the device:

flash:/boot.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: boot

Platform version: 7.1.070

Product version: Test 0001015

Supported board: cen

[Component]

Component: boot

Description: boot package

Software image signature: HP

flash:/system.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: system

Platform version: 7.1.070

Product version: Test 0001015

Supported board: cen

[Component]

Component: system

Description: system package

Software image signature: HP

# (Distributed devices in standalone mode.) (Centralized IRF devices.) 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: xxxx

Service name: boot

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu

[Component]

Component: boot

Description: boot package

Software image signature: HP

flash:/system.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: system

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu

[Component]

Component: system

Description: system package

Software image signature: HP

# (Distributed devices 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: xxxx

Service name: boot

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu lpu

[Component]

Component: boot

Description: boot package

Software image signature: HP

flash:/system.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: system

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu lpu

[Component]

Component: system

Description: system package

Software image signature: HP

Backup startup software images on chassis 2 slot 1:

flash:/boot.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: boot

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu lpu

[Component]

Component: boot

Description: boot package

Software image signature: HP

flash:/system.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: system

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu lpu

[Component]

Component: system

Description: system package

Software image signature: HP

For information about the command output, see Table 1.

Related commands

boot-loader file

display install committed

ISSU commands -- display install committed

Use display install committed to display main startup software images.

Syntax

Centralized devices:

display install committed [ verbose ]

Centralized IRF devices:

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

Distributed devices in standalone mode:

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

Distributed devices in IRF mode:

display install committed [ chassis chassis-number slot slot-number [ cpu cpu-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. (Distributed devices in standalone mode.)

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

slot slot-number: Specifies an IRF member device by its member ID or specifies a PEX by its virtual slot number. On an IRF fabric, this command displays information for all member devices if you do not specify a member device. On an IRF 3 system, this command displays information for all IRF member devices and PEXs if you do not specify an IRF member device or PEX. (Centralized IRF devices.) (IRF 3 capable.)

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. (Distributed devices in IRF mode.) (IRF 3 incapable.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member device or specifies a PEX. The chassis-number argument represents the member ID of the IRF member device or the virtual chassis number of the PEX. The slot-number argument represents the slot number of the card or PEX. On an IRF fabric, this command displays information for all cards if you do not specify a card. On an IRF 3 system, this command displays information for all cards and PEXs if you do not specify a card or PEX. (Distributed devices in IRF mode.) (IRF 3 capable.)

cpu cpu-number: Specifies a CPU by its number. Use this option to display information for a security engine.

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

# (Centralized devices.) Display the main startup software images.

<Sysname> display install committed

Committed packages on the device:

flash:/boot.bin

flash:/system.bin

flash:/feature1.bin

# (Distributed devices in standalone mode.) (Centralized IRF devices.) Display the main startup software images.

<Sysname> display install committed

Committed packages on slot 1:

flash:/boot.bin

flash:/system.bin

flash:/feature1.bin

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

# (Centralized devices.) Display detailed information about main startup software images.

<Sysname> display install committed verbose

Committed packages on the device:

flash:/boot.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: boot

Platform version: 7.1.070

Product version: Test 0001015

Supported board: cen

[Component]

Component: boot

Description: boot package

Software image signature: HP

flash:/system.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: system

Platform version: 7.1.070

Product version: Test 0001015

Supported board: cen

[Component]

Component: system

Description: system package

Software image signature: HP

flash:/feature1.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: feature1

Platform version: 7.1.070

Product version: Test 0001015

Supported board: cen

[Component]

Component: feature1

Description: feature1 package

Software image signature: HP

# (Distributed devices in standalone mode.) (Centralized IRF devices.) 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: xxxx

Service name: boot

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu

[Component]

Component: boot

Description: boot package

Software image signature: HP

flash:/system.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: system

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu

[Component]

Component: system

Description: system package

Software image signature: HP

flash:/feature1.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: feature1

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu

[Component]

Component: feature1

Description: feature1 package

Software image signature: HP

# (Distributed devices 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: xxxx

Service name: boot

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu lpu

[Component]

Component: boot

Description: boot package

Software image signature: HP

flash:/system.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: system

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu lpu

[Component]

Component: system

Description: system package

Software image signature: HP

flash:/patch1.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: patch1

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu lpu

[Component]

Component: patch1

Description: patch1 package

Software image signature: HP

Committed packages on chassis 2 slot 1:

flash:/boot.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: boot

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu lpu

[Component]

Component: boot

Description: boot package

Software image signature: HP

flash:/system.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: system

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu lpu

[Component]

Component: system

Description: system package

Software image signature: HP

flash:/patch1.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: patch1

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu lpu

[Component]

Component: patch1

Description: patch1 package

Software image signature: HP

For information about the command output, see Table 1.

Related commands

boot-loader file

display install backup

install commit

ISSU commands -- display install inactive

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

Syntax

Centralized devices:

display install inactive [ verbose ]

Centralized IRF devices:

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

Distributed devices in standalone mode:

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

Distributed devices in IRF mode:

display install inactive [ chassis chassis-number slot slot-number [ cpu cpu-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. (Distributed devices in standalone mode.)

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

slot slot-number: Specifies an IRF member device by its member ID or specifies a PEX that has storage media by its virtual slot number. On an IRF fabric, this command displays information for all member devices if you do not specify a member device. On an IRF 3 system, this command displays information for all parent devices and PEXs if you do not specify a parent device or PEX. (Centralized IRF devices.) (IRF 3 capable.)

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. (Distributed devices in IRF mode.) (IRF 3 incapable.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member device or specifies a PEX that has storage media. The chassis-number argument represents the member ID of the IRF member device or the virtual chassis number of the PEX. The slot-number argument represents the slot number of the card or PEX. On an IRF fabric, this command displays information for all cards if you do not specify a card. On an IRF 3 system, this command displays information for all cards and PEXs if you do not specify a card or PEX. (Distributed devices in IRF mode.) (IRF 3 capable.)

cpu cpu-number: Specifies a CPU by its number. Use this option to display information for a security engine.

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

Examples

# (Centralized devices.) Display brief information about inactive software images in the root directories of the file systems.

<Sysname> display install inactive

Inactive packages on the device:

flash:/feature1.bin

# (Distributed devices in standalone mode.) (Centralized IRF devices.) 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

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

# (Centralized devices.) Display detailed information about inactive software images in the root directories of the file systems.

<Sysname> display install inactive verbose

Inactive packages on the device:

flash:/feature1.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: feature1

Platform version: 7.1.070

Product version: Test 0001015

Supported board: cen

[Component]

Component: feature1

Description: feature1 package

Software image signature: HP

# (Distributed devices in standalone mode.) (Centralized IRF devices.) 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: xxxx

Service name: feature1

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu

[Component]

Component: feature1

Description: feature1 package

Software image signature: HP

# (Distributed devices 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: xxxx

Service name: patch1

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu lpu

[Component]

Component: patch1

Description: patch1 package

Software image signature: HP

Inactive packages on chassis 2 slot 1:

flash:/patch1.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: patch1

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu lpu

[Component]

Component: patch1

Description: patch1 package

Software image signature: HP

For information about the command output, see Table 1.

Related commands

install deactivate

ISSU commands -- 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 Fundamentals Configuration Guide.

Examples

# (Centralized devices.) Display information about .ipe file flash:/test.ipe.

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

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

XX images in IPE:

boot.bin

system.bin

Software image signature: HP

# (Distributed devices in standalone mode.) (Centralized IRF devices.) 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.

XX images in IPE:

boot.bin

system.bin

Software image signature: HP

# (Distributed devices 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.

XX images in IPE:

boot.bin

system.bin

Software image signature: HP

Related commands

display install package

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

# (Centralized devices.) Display ongoing ISSU activate, deactivate, and rollback operations.

<Sysname> display install job

JobID:5

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

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

# (Distributed devices in standalone mode.) (Centralized IRF devices.) 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.

# (Distributed devices 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.

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

# (Centralized devices.) 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 the device

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

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

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

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

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

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

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

Install activate flash:/route.bin on the device

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

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

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

# (Distributed devices in standalone mode.) (Centralized IRF devices.) 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.

# (Distributed devices 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.

# (Centralized devices.) 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 the device

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

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

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

Detail of activating packages on the device.

Get upgrade policy successfully.

Detail of activating packages on the device.

Uncompress package to system successfully.

Remove files from system successfully.

# (Distributed devices in standalone mode.) (Centralized IRF devices.) 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.

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

ISSU commands -- 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 Fundamentals Configuration Guide.

all: Specifies all software image files in the root directories of the device's file systems. (Centralized devices.)

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

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

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

Service name: system

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu

Software image signature: HP

# Display detailed information about 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.070

Product version: Test 0001015

Supported board: mpu

[Component]

Component: system

Description: system package

Software image signature: HP

For information about the command output, see Table 1.

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

# (Distributed devices in standalone mode.) (Centralized IRF devices.) 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

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

ISSU commands -- display install which

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

Syntax

Centralized devices:

display install which { component name | file filename }

Centralized IRF devices:

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

Distributed devices in standalone mode:

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

Distributed devices in IRF mode:

display install which { component name | file filename } [ chassis chassis-number slot slot-number [ cpu cpu-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. (Distributed devices in standalone mode.)

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

slot slot-number: Specifies an IRF member device by its member ID or specifies a PEX that has storage media by its virtual slot number. On an IRF fabric, this command displays information for all member devices if you do not specify a member device. On an IRF 3 system, this command displays information for all parent devices and PEXs if you do not specify a parent device or PEX. (Centralized IRF devices.) (IRF 3 capable.)

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. (Distributed devices in IRF mode.) (IRF 3 incapable.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member device or specifies a PEX that has storage media. The chassis-number argument represents the member ID of the IRF member device or the virtual chassis number of the PEX. The slot-number argument represents the slot number of the card or PEX. On an IRF fabric, this command displays information for all cards if you do not specify a card. On an IRF 3 system, this command displays information for all cards and PEXs if you do not specify a card or PEX. (Distributed devices in IRF mode.) (IRF 3 capable.)

cpu cpu-number: Specifies a CPU by its number. Use this option to display information for a security engine.

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

# (Distributed devices in standalone mode.) (Centralized IRF devices.) 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: xxxx

Service name: system

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu

Software image signature: HP

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

# (Distributed devices 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: xxxx

Service name: system

Platform version: 7.1.070

Product version: Test 0001015

Supported board: mpu lpu

Software image signature: HP

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: · cen—Centralized device. · mpu—MPU. · lpu—Service card. · sfc—Switching fabric module.
Software image signature | Signature for the software image: · HP. · HP-US. · HPE. The Comware system can be upgraded from a version with the HP or HP-US signature to a version with the HPE signature. To upgrade the Comware system from a version without a signature to a version with the HPE signature, you must first complete one of the following tasks: · Patch the Comware system. · Upgrade the Comware system to a version with the HP or HP-US signature.

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

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

# (Centralized devices.) Display ISSU status information when no ISSU process is taking place.

<Sysname> display issu state

ISSU state: Init

Compatibility: Unknown

Work state: Normal

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

# (Centralized devices.) Display ISSU status information while the issu load command is being executed.

<Sysname> display issu state

ISSU state: Loading

Compatibility: Incompatible

Work state: Normal

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

# (Centralized IRF devices.) (Distributed devices 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

# (Centralized IRF devices.) (Distributed devices 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

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

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

# (Distributed devices in IRF mode.) On a multichassis 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 (centralized devices)

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. · Accepted—The issu accept command is completed. · Committing—The system is executing the issu commit command. · Rollbacking—A rollback is in progress.
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. The value of this field is fixed at Normal because this command can be executed only when the device is operating correctly.
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.
Previous software images | File names of the images that were running on the device before the ISSU.
Upgrade version list | Versions of the upgrade images.
Upgrade software images | File names of the upgrade images.

‌

Table 5 Command output (centralized IRF devices)

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 is displayed if you execute the command on an original subordinate member.
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, a subordinate member that is upgraded first enters this state. In this state, member devices are not running the same software versions.
Upgrade method | Upgrade mode. The value of this field is fixed at Card by card. In this mode, member devices are upgraded one by one.
Upgraded slot | Upgraded members. During a rollback, this field displays Unknown.
Current upgrading slot | Members that are being upgraded. During a rollback, this field displays Unknown.
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 the command on an original subordinate member while the member is being upgraded 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 the command on an original subordinate member while the member is being upgraded to an incompatible version, this field displays Unknown.
Upgrade version list | Versions of the upgrade images. If you execute the command on an original subordinate member while the member is being upgraded to an incompatible version, this field displays Unknown.
Upgrade software images | File names of the upgrade images. If you execute the command on an original subordinate member while the member is being upgraded to an incompatible version, this field displays Unknown.

‌

Table 6 Command output (distributed devices)

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 ?span style='font:7.0pt "Times New Roman"'> For a compatible upgrade of a multichassis IRF fabric, one or more subordinate members are upgraded first, and then the original master and the remaining subordinate members are upgraded. ?span style='font:7.0pt "Times New Roman"'> For an incompatible upgrade of a multichassis IRF fabric, one subordinate member is upgraded first, and then the original master and the remaining subordinate members.
Upgraded slot | Upgraded cards. (Distributed devices 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. (Distributed devices in standalone mode.) This field is available in standalone mode. During a rollback, this field displays Unknown.
Upgraded chassis | Upgraded members. (Distributed devices 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. (Distributed devices 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

ISSU commands -- display version comp-matrix

Use display version comp-matrix to display version compatibility information and identify the recommended upgrade method.

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

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

ipe-filename: Specifies an .ipe file in the filesystemname/filename.ipe format. The file must be stored in the root directory of a file system on the device. The value string excluding the file system location section (if any) can have a maximum of 63 characters. For more information about specifying a file, see Fundamentals Configuration Guide.

Usage guidelines

To display compatibility information for the running software images, do not specify any image files for the command. If you specify the upgrade image files, the command displays the following information:

· Compatibility information for upgrade images.

· Recommended ISSU methods for upgrading the running images to the upgrade images.

On an IRF 3 system, the following rules apply:

· This command displays the following information if you do not specify any files:

?span style='font:7.0pt "Times New Roman"'> Compatibility information for the running images of the parent device.

?span style='font:7.0pt "Times New Roman"'> Compatibility information for the running images of PEXs.

· If you specify one or more files stored on parent devices, the command displays the following information:

?span style='font:7.0pt "Times New Roman"'> Compatibility information for the specified images on the parent device.

?span style='font:7.0pt "Times New Roman"'> Compatibility information for the specified images on the PEXs. The prerequisite is that you use the issu pex command to specify the images used for PEX upgrade before using this command.

?span style='font:7.0pt "Times New Roman"'> Recommended ISSU methods for upgrading the running images to the specified images.

· This command does not display information about software compatibility between the parent device and the PEXs. For this compatibility information, see the release notes.

On a device installed with security engines, the following rules apply:

· This command displays the following information if you do not specify any files:

?span style='font:7.0pt "Times New Roman"'> Compatibility information for the running images of the device.

?span style='font:7.0pt "Times New Roman"'> Compatibility information for the running images of the security engines.

· If you specify one or more files stored on parent devices, the command displays the following information:

?span style='font:7.0pt "Times New Roman"'> Compatibility information for the specified images on the device.

?span style='font:7.0pt "Times New Roman"'> Compatibility information for the specified images on the security engines. You must use the issu blade command to specify the images used for security engine upgrade before using this command.

?span style='font:7.0pt "Times New Roman"'> Recommended ISSU methods for upgrading the running images to the specified images.

· This command does not display information about compatibility between the device's images and the security engines' images. For the compatibility information, see the release notes.

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

Examples

# Display compatibility information for the running images.

<Sysname> display version comp-matrix

Boot image: flash:/boot-t0001015.bin

Version:

7.1.070

System image: flash:/system-t0001015.bin

Version:

7.1.070-Test 0001015

Version compatibility list:

7.1.070-Test 0001015

Version dependency boot list:

7.1.070

Feature image: flash:/feature1-t0001015.bin

Version:

7.1.070-Test 0001015

Version compatibility list:

7.1.070-Test 0001015

Version dependency system list:

7.1.070-Test 0001015

# (Centralized devices.) Display compatibility information for upgrade images as well as the recommended ISSU method. (In this example, the specified images are incompatible with the running images.)

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

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

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

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

Boot image: flash:/boot-t0001015.bin

Version:

7.1.070

System image: flash:/system-t0001015.bin

Version:

7.1.070-Test 0001015

Version compatibility list:

7.1.070-Test 0001015

Version dependency boot list:

7.1.070

Feature image: flash:/feature1-t0001017.bin

Version:

7.1.070-Test 0001017

Version compatibility list:

7.1.070-Test 0001017

Version dependency system list:

7.1.070-Test 0001017

Incompatible upgrade.

# (Centralized IRF devices.) Display compatibility information for upgrade images as well as the recommended ISSU method. (In this example, the specified images are compatible with the running images.)

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

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

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

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

Boot image: flash:/boot-t0001015.bin

Version:

7.1.070

System image: flash:/system-t0001015.bin

Version:

7.1.070-Test 0001015

Version compatibility list:

7.1.070-Test 0001015

Version dependency boot list:

7.1.070

Feature image: flash:/feature1-t0001015.bin

Version:

7.1.070-Test 0001015

Version compatibility list:

7.1.070-Test 0001014

7.1.070-Test 0001015

Version dependency system list:

7.1.070-Test 0001015

Slot Upgrade Way

1 File Upgrade

# (Distributed devices in standalone mode.) Display compatibility information for a feature upgrade image as well as 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.

Feature image: flash:/feature1-t0001015.bin

Version:

7.1.070-Test 0001015

Version compatibility list:

7.1.070-Test 0001014

7.1.070-Test 0001015

Version dependency system list:

7.1.070-Test 0001015

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

# Display compatibility information for the running images on the parent device, and compatibility information for the running images on the PEXs.

<Sysname> display version comp-matrix

Boot image: flash:/boot-t0001015.bin

Version:

7.1.070

System image: flash:/system-t0001015.bin

Version:

7.1.070-Test 0001015

Version compatibility list:

7.1.070-Test 0001015

Version dependency boot list:

7.1.070

Compatible info of S5120HI:

Boot image: flash:/rpu-s5120hi-boot-t0001015.bin

Version:

7.1.070

System image: flash:/rpu-s5120hi-system-t0001015.bin

Version:

7.1.070-Test 0001015

Version compatibility list:

7.1.070-Test 0001015

Version dependency boot list:

7.1.070

Feature image: flash:/rpu-s5120hi-devkit-t0001015.bin

Version:

7.1.070-Test 0001015

Version compatibility list:

7.1.070-Test 0001015

Version dependency system list:

7.1.070-Test 0001015

# (Centralized IRF devices.) (IRF 3 capable.) Display the following information:

· Compatibility information for the upgrade images that are used for the parent device upgrade.

· Compatibility information for the upgrade images that are used for the S5120HI PEX upgrade.

· Recommended ISSU methods for the upgrades.

In this example, the specified images are incompatible with the running images.

<Sysname> issu pex PEX-S5120HI file boot flash:/s5120hi-boot-t0001015.bin system flash:/s5120hi-system-t0001015.bin feature flash:/s5120hi-feature1-t0001017.bin

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

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

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

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

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

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

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

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

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

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

Boot image: flash:/boot-t0001015.bin

Version:

7.1.070

System image: flash:/system-t0001015.bin

Version:

7.1.070-Test 0001015

Version compatibility list:

7.1.070-Test 0001015

Version dependency boot list:

7.1.070

Feature image: flash:/feature1-t0001017.bin

Version:

7.1.070-Test 0001017

Version compatibility list:

7.1.070-Test 0001017

Version dependency system list:

7.1.070-Test 0001017

Compatible info of S5120HI:

Boot image: flash:/rpu-s5120hi-boot-t0001015.bin

Version:

7.1.070

System image: flash:/rpu-s5120hi-system-t0001015.bin

Version:

7.1.070-Test 0001015

Version compatibility list:

7.1.070-Test 0001015

Version dependency boot list:

7.1.070

Feature image: flash:/s5120hi-feature1-t0001017.bin

Version:

7.1.070-Test 0001017

Version compatibility list:

7.1.070-Test 0001017

Version dependency system list:

7.1.070-Test 0001017

Incompatible upgrade.

# (Centralized IRF devices.) (IRF 3 capable.) Display the following information:

· Compatibility information for the upgrade images that are used for the parent device upgrade.

· Compatibility information for the upgrade image that are used for the S5120HI PEX upgrade.

· Recommended ISSU methods for the upgrades.

In this example, the specified images are compatible with the running images.

<Sysname> issu pex PEX-S5120HI file feature flash:/s5120hi-feature1-t0001015.bin

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

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

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

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

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

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

Boot image: flash:/boot-t0001015.bin

Version:

7.1.070

System image: flash:/system-t0001015.bin

Version:

7.1.070-Test 0001015

Version compatibility list:

7.1.070-Test 0001014

7.1.070-Test 0001015

Version dependency boot list:

7.1.070

Feature image: flash:/feature1-t0001015.bin

Version:

7.1.070-Test 0001015

Version compatibility list:

7.1.070-Test 0001014

7.1.070-Test 0001015

Version dependency system list:

7.1.070-Test 0001014

7.1.070-Test 0001015

Compatible info of S5120HI:

Feature image: flash:/s5120hi-feature1-t0001015.bin

Version:

7.1.070-Test 0001015

Version compatibility list:

7.1.070-Test 0001014

7.1.070-Test 0001015

Version dependency system list:

7.1.070-Test 0001014

7.1.070-Test 0001015

Slot Upgrade Way

1 File Upgrade

102 File Upgrade

# (Distributed devices in IRF mode.) (IRF 3 capable.) Display the following information:

· Compatibility information for a feature upgrade image that is used for the parent device upgrade.

· Compatibility information for a feature upgrade image that is used for the S5120HI PEX upgrade.

· Recommended ISSU methods for the upgrades.

In this example, the specified images are compatible with the running images.

<Sysname> issu pex PEX-S5120HI file feature flash:/s5120hi-feature1-t0001015.bin

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

Copying file flash:/s5120hi-feature1-t0001015.bin to chassis2#slot0#flash:/s5120hi-feature1-t0001015.bin...Done.

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

Verifying the file flash:/cmw710-feature1-a0070.bin on chassis 1 slot 0.....Done.

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

Feature image: flash:/cmw710-feature1-a0070.bin

Version:

7.1.070

Version compatibility list:

7.1.070-Test 0001014

7.1.070-Test 0001015

Version dependency system list:

7.1.070

Compatible info of S5120HI:

Feature image: flash:/s5120hi-feature1-t0001015.bin

Version:

7.1.070

Version compatibility list:

7.1.070-Test 0001014

7.1.070-Test 0001015

Version dependency system list:

7.1.070-Test 0001015

Chassis Slot Upgrade Way

1 0 Service Upgrade

1 7 Service Upgrade

1 9 Service Upgrade

2 0 Service Upgrade

2 1 Service Upgrade

2 6 Service Upgrade

101 0 Service Upgrade

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

flash:/cmw710-feature1-t0001015.bin

Feature1

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

flash:/cmw710-feature1-t0001015.bin

Feature1

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

flash:/cmw710-feature1-t0001015.bin

Feature1

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

flash:/cmw710-feature1-t0001015.bin

Feature1

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

flash:/cmw710-feature1-t0001015.bin

Feature1

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

flash:/cmw710-feature1-t0001015.bin

Feature1

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

flash:/cmw710-feature1-t0001015.bin

Feature1

Table 7 Command output

Field | Description
Verifying the file | The system was verifying the validity of the file.
Version compatibility list | · Under a system image, this field shows all system image versions that are compatible with the system image. · 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 are 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.
Compatible info of S5120HI: | Compatibility information for the PEXs.
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. · ISSU Reboot. · 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

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

ISSU commands -- install activate

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

Syntax

Centralized devices:

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

install activate patch filename

Centralized IRF devices:

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

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

Distributed devices in standalone mode:

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

install activate patch filename { all | slot slot-number [ cpu cpu-number ] }

Distributed devices in IRF mode:

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

install activate patch filename { all | chassis chassis-number slot slot-number [ cpu cpu-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.

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 Fundamentals Configuration Guide.

all: Specifies all cards. (Distributed devices in standalone mode.)

all: Specifies all member devices. (Centralized IRF devices.) (IRF 3 incapable.)

all: Specifies all member devices and PEXs. (Centralized IRF devices.) (IRF 3 capable.)

all: Specifies all cards. (Distributed devices in IRF mode.) (IRF 3 incapable.)

all: Specifies all cards and PEXs. (Distributed devices in IRF mode.) (IRF 3 capable.)

slot slot-number: Specifies a card by its slot number. (Distributed devices in standalone mode.)

slot slot-number: Specifies an IRF member device by its member ID. (Centralized IRF devices.) (IRF 3 incapable.)

slot slot-number: Specifies an IRF member device by its member ID or specifies a PEX by its virtual slot number. (Centralized IRF devices.) (IRF 3 capable.)

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. (Distributed devices in IRF mode.) (IRF 3 incapable.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member device or specifies a PEX. The chassis-number argument represents the member ID of the IRF member device or the virtual chassis number of the PEX. The slot-number argument represents the slot number of the card or PEX. (Distributed devices in IRF mode.) (IRF 3 capable.)

cpu cpu-number: Specifies a CPU by its number. Use this option to activate images or identify the ISSU method for a security engine.

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.

Centralized devices:

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.

Distributed devices in standalone mode:Distributed devices in IRF mode:

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

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

If the specified files are not stored on the security engine to be upgraded, the command copies the files to the security engine automatically.

(Distributed devices 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.

(Distributed devices 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.

(Distributed devices 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.

Centralized IRF devices:

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

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

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

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

# (Centralized devices.) Identify the ISSU method for feature upgrade with feature1.bin and the upgrade impact on the device.

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

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

Upgrade summary according to following table:

flash:/feature1.bin

Running Version New Version

Test 0001015 Test 0001016

Upgrade Way: 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.

# (Distributed devices 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.

# (Centralized IRF devices.) Identify the ISSU method for feature upgrade with feature1.bin on subordinate member 2 and the upgrade impact.

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

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

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

Upgrade summary according to following table:

flash:/feature1.bin

Running Version New Version

Test 0001015 Test 0001016

Slot Upgrade Way

2 Reboot

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.

# (Centralized devices.) Activate the system image in system.bin and the feature images in feature1.bin.

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

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

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

Upgrade summary according to following table:

flash:/system.bin

Running Version New Version

Test 0001015 Test 0001016

flash:/feature1.bin

Running Version New Version

NONE Test 0001016

Upgrade Way: Service Upgrade

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

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

# (Distributed devices 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:/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.

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

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

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

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

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

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

Upgrade summary according to following table:

flash:/system.bin

Running Version New Version

Test 0001015 Test 0001016

flash:/feature1.bin

Running Version New Version

None Test 0001016

Slot Upgrade Way

2 Service Upgrade

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

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

# (Distributed devices 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 8 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. · ISSU Reboot. · 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

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

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 Fundamentals Configuration Guide.

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.

ISSU commands -- 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 or ISSU 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.

Related commands

install activate

install deactivate

install rollback

ISSU commands -- install deactivate

Use install deactivate to deactivate feature images and patch images.

Syntax

Centralized devices:

install deactivate feature filename&<1-30>

install deactivate patch filename

Centralized IRF devices:

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

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

Distributed devices in standalone mode:

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

install deactivate patch filename { all | slot slot-number [ cpu cpu-number ] }

Distributed devices in IRF mode:

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

install deactivate patch filename chassis chassis-number { all | slot slot-number [ cpu cpu-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 Fundamentals Configuration Guide.

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

all: Specifies all member devices on which the specified patch image file has been activated. (Centralized IRF devices.) (IRF 3 incapable.)

all: Specifies all member devices and PEXs on which the specified patch image file has been activated. (Centralized IRF devices.) (IRF 3 capable.)

all: Specifies all cards on which the specified patch image file has been activated. (Distributed devices in IRF mode.) (IRF 3 incapable.)

all: Specifies all cards and PEXs on which the specified patch image file has been activated. (Distributed devices in IRF mode.) (IRF 3 capable.)

slot slot-number: Specifies a card by its slot number. (Distributed devices in standalone mode.)

slot slot-number: Specifies an IRF member device by its member ID. (Centralized IRF devices.) (IRF 3 incapable.)

slot slot-number: Specifies an IRF member device by its member ID or specifies a PEX by its virtual slot number. (Centralized IRF devices.) (IRF 3 capable.)

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. (Distributed devices in IRF mode.) (IRF 3 incapable.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member device or specifies a PEX. The chassis-number argument represents the member ID of the IRF member device or the virtual chassis number of the PEX. The slot-number argument represents the slot number of the card or PEX. (Distributed devices in IRF mode.) (IRF 3 capable.)

cpu cpu-number: Specifies a CPU by its number. Use this option to deactivate images for a security engine.

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.

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

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

Examples

# (Centralized devices.) Deactivate the patch images in the route-patch.bin file.

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

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

# (Distributed devices in standalone mode.) (Centralized IRF devices.) 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.

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

ISSU commands -- install remove

Use install remove to delete an inactive software image file.

Syntax

Centralized devices:

install remove { filename | inactive }

Centralized IRF devices:

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

Distributed devices in standalone mode:

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

Distributed devices in IRF mode:

install remove [ chassis chassis-number slot slot-number [ cpu cpu-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. (Distributed devices in standalone mode.)

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

slot slot-number: Specifies an IRF member device by its member ID or specifies a PEX that has storage media by its virtual slot number. On an IRF fabric, this command deletes inactive software images from all member devices if you do not specify a member device. On an IRF 3 system, this command deletes inactive software images from all parent devices and PEXs if you do not specify a parent device or PEX. (Centralized IRF devices.) (IRF 3 capable.)

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 deletes inactive software images from all cards. (Distributed devices in IRF mode.) (IRF 3 incapable.)

chassis chassis-number slot slot-number: Specifies a card on an IRF member device or specifies a PEX that has storage media. The chassis-number argument represents the member ID of the IRF member device or the virtual chassis number of the PEX. The slot-number argument represents the slot number of the card or PEX. On an IRF fabric, this command deletes inactive software images from all cards if you do not specify a card. On an IRF 3 system, this command deletes inactive software images from all cards and PEXs if you do not specify a card or PEX. (Distributed devices in IRF mode.) (IRF 3 capable.)

cpu cpu-number: Specifies a CPU by its number. Specify this option to delete inactive images from a security engine.

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

ISSU commands -- 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 or ISSU 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

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

# (Centralized devices.) Verify the software change confirmation status and software image integrity and consistency.

<Sysname> install verify

Active packages on the device are the reference packages.

Packages will be compared with the reference packages.

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

Verifying packages on the device:

Start to check active package completeness.

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

flash:/boot-t0001015.bin verification successful.

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

flash:/system-t0001015.bin verification successful.

Start to check active package consistency.

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

Active packages are consistent with the reference packages.

Verification is done.

# (Distributed devices 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.

# (Centralized IRF devices.) Verify the software change confirmation status and software image integrity and consistency.

<Sysname> install verify

Active packages on slot 1 are the reference packages.

Packages will be compared with the reference packages.

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

Verifying packages on slot 1:

Start to check active package completeness.

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

flash:/boot-t0001015.bin verification successful.

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

flash:/system-t0001015.bin verification successful.

Start to check active package consistency.

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

Active packages are consistent with the reference packages.

Verifying packages on slot 2:

Start to check active package completeness.

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

flash:/boot-t0001015.bin verification successful.

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

flash:/system-t0001015.bin verification successful.

Start to check active package consistency.

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

Active packages are consistent with the reference packages.

Verification is done.

# (Distributed devices 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 commands -- 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 commands -- issu blade

Use issu blade to specify images used for security engine upgrade.

Syntax

issu blade blade-model file { boot filename | system filename | feature filename&<1-30> } *

issu blade blade-model file ipe ipe-filename

Views

User view

Predefined user roles

network-admin

Parameters

blade-model: Specifies the security engine model. You must enter the complete security engine model name for the device to identify the security engine correctly. For available security engine models, enter boot-loader blade ?.

boot: Specifies a boot image file.

system: Specifies a system image file.

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

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

ipe 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 Fundamentals Configuration Guide.

Usage guidelines

Use this command if you want to upgrade security engines during an ISSU that uses issu commands.

This command sets software images for all security engines of the specified model. After verifying validity of the source file, the system performs the following operations:

1. If you specify an .ipe file, the system automatically decompresses the .bin image files from the .ipe file to the same directory as the .ipe file.

2. Copies the .bin files to all security engines of the specified model.

3. Displays a prompt for you to delete the following files:

?span style='font:7.0pt "Times New Roman"'> Source .ipe file (if any).

?span style='font:7.0pt "Times New Roman"'> Source .bin files if the .bin files are not on a security engine of the specified model.

This command only specifies images used for security engine upgrade. This command does not load the upgrade images. The security engines will load the upgrade images when the MPUs are upgraded. For more information, see Fundamentals Configuration Guide.

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.

Examples

# Specify flash:/test.bin as the upgrade image for the Blade-m9k security engine.

<Sysname> issu blade Blade-m9k file feature flash:/test.bin

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

File cfa0:/test.bin already exists on slot 2.1.

Overwrite the existing files? [Y/N]:Y

Copying file flash:/test.bin to slot2.1#cfa0:/test.bin...Done.

File cfa0:/test.bin already exists on slot 3.1.

Overwrite the existing files? [Y/N]:Y

Copying file flash:/test.bin to slot3.1#cfa0:/test.bin...Done.

Delete flash:/test.bin from slot 0? [Y/N]:N

# Specify slot2.1#cfa0:/test.bin as the upgrade image for the Blade-m9k security engine.

<Sysname> issu blade Blade-m9k file feature slot2.1#cfa0:/test.bin

Verifying the file cfa0:/test.bin on slot 2.1...Done.

File cfa0:/test.bin already exists on slot 3.1.

Overwrite the existing files? [Y/N]:Y

Copying file cfa0:/test.bin to slot3.1#cfa0:/test.bin...Done.

Delete flash:/test.bin from slot 0? [Y/N]:N.

# Specify flash:/test.ipe as the upgrade image for the Blade-m9k security engine.

<Sysname> issu blade Blade-m9k file ipe flash:/test.ipe

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

File flash:/blade3fwm9k-cmw710-test-a0002.bin already exists on slot 0.

Overwrite the existing files? [Y/N]:Y

Decompressing file blade3fwm9k-cmw710-test-a0002.bin to flash:/blade3fwm9k-cmw710-test-a0002.bin...Done.

File cfa0:/blade3fwm9k-cmw710-test-a0002.bin already exists on slot 2.1.

Overwrite the existing files? [Y/N]:Y

Copying file flash:/blade3fwm9k-cmw710-test-a0002.bin to slot2.1#cfa0:/blade3fwm9k-cmw710-test-a0002.bin...Done.

File cfa0:/blade3fwm9k-cmw710-test-a0002.bin already exists on slot 3.1.

Overwrite the existing files? [Y/N]:N

Delete flash:/blade3fwm9k-cmw710-test-a0002.bin from slot 0? [Y/N]:N

Delete flash:/test.ipe from slot 0? [Y/N]:N

Related commands

issu load

ISSU commands -- issu commit

(Centralized devices.) Use issu commit to complete an ISSU upgrade to a compatible version.

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

(Centralized IRF devices.) Use issu commit to upgrade the original master and the subordinate members that have not been upgraded and complete the ISSU upgrade.

(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 multichassis IRF fabric.) Use issu commit to upgrade the original master and the subordinate members that have not been upgraded and complete the ISSU upgrade.

Syntax

Centralized devices:

issu commit

Distributed devices in standalone mode:Centralized IRF devices:

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. (Distributed devices in standalone mode.)

slot slot-number: Specifies the member ID of the original master or a subordinate member that has not been upgraded. (Centralized IRF devices.)

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 or a subordinate member that has not been upgraded. (On a multichassis IRF fabric.)

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

(Centralized devices.) 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.

(Centralized IRF devices.) Use this command to upgrade the original master and the subordinate members that have not been upgraded, one by one. You must wait for one upgraded member to start up again and join the IRF fabric before upgrading another member. After all members are upgraded, the ISSU status changes to Init, and the ISSU process ends and cannot be rolled back.

(Distributed devices in standalone mode.) (Distributed devices in IRF mode.) 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 the original master and the subordinate members that have not been upgraded, one by one. After all members are upgraded, the ISSU status changes to Init, and the ISSU process ends and cannot be rolled back. You must wait for one upgraded subordinate member to start up again and join the IRF fabric before upgrading another subordinate member.

Examples

# (Centralized devices.) Finish the ISSU to a compatible version.

<Sysname> issu commit

# (Centralized IRF devices.) After member 2 is upgraded and becomes the new master, upgrade the original master (member 3) and the other subordinate members that have not been upgraded (member 4 and member 1).

<Sysname> issu commit slot 3

Upgrade summary according to following table:

flash:/feature1.bin

Running Version New Version

Test 0001015 Test 0001016

Slot Upgrade Way

3 Service Upgrade

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

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

<Sysname> issu commit slot 4

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

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

Upgrade summary according to following table:

flash:/feature1.bin

Running Version New Version

Test 0001015 Test 0001016

Slot Upgrade Way

4 Service Upgrade

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

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

<Sysname> issu commit slot 1

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

Copying file flash:/feature1.bin to slot1#flash:/feature1.bin...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.

# (Distributed devices 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.

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

# (Distributed devices in IRF mode.) Upgrade the members that have not been upgraded during an ISSU to a compatible version. In this example, the IRF fabric has four members, and only the member with the ID 2 has been upgraded.

<Sysname> issu commit chassis 3

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

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

Upgrade summary according to following table:

flash:/feature1.bin

Running Version New Version

Test 0001015 Test 0001016

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

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

<Sysname> issu commit chassis 4

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

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

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

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

Upgrade summary according to following table:

flash:/feature1.bin

Running Version New Version

Test 0001015 Test 0001016

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

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

<Sysname> issu commit chassis 1

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

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

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

1 2 Service Upgrade

1 3 Service Upgrade

1 4 Service Upgrade

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

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

# (Distributed devices 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.

# (Distributed devices 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 7.

Related commands

issu accept

issu load

issu run switchover

ISSU commands -- issu load

(Centralized devices.) Use issu load to upgrade the software images of the device and configure the new images as main startup software images.

(Centralized IRF devices.) Use issu load to upgrade the software images of subordinate members and configure the new images as main startup software images for those members.

(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 multichassis IRF fabric.) Use issu load to upgrade subordinate members and configure the new images as main startup software images for those members.

Syntax

Centralized devices:

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

issu load file ipe ipe-filename [ reboot ]

Distributed devices 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 ]

Centralized IRF devices:

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

issu load file ipe ipe-filename slot slot-number&<1-9> [ 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 (multichassis):

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

issu load file ipe ipe-filename chassis chassis-number&<1-3> [ 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 device/master device/active MPU/global active MPU. 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 Fundamentals Configuration Guide.

ipe-filename: Specifies an .ipe file in the filesystemname/filename.ipe format. The file must be stored in the root directory of a file system on the device/master device/active MPU/global active MPU. 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 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. (Distributed devices in standalone mode.)

slot slot-number: Specifies the member ID of a subordinate member. You can specify a space-separated list of up to nine member IDs. On a single-chassis IRF fabric, enter the member ID of the member device to upgrade the entire fabric. On a multichassis IRF fabric, you can specify only one member ID for a compatible upgrade and can specify multiple member IDs for an incompatible upgrade. As a best practice, specify half of the subordinate members if the member devices form a ring. Make sure the specified subordinate members are directly connected by physical links. (Centralized IRF devices.)

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 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. (On a multichassis 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

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.

(Centralized devices.) This command performs the following operations:

· Checks the version compatibility.

· Identifies the upgrade method.

· Loads the new images to upgrade the device.

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

(Centralized IRF devices.) This command performs the following operations:

· Checks the version compatibility.

· Identifies the upgrade method.

· Loads the new images to upgrade the member devices.

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

(On a 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.

(On a multichassis 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 devices.

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

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. (Distributed devices in IRF mode.) (Centralized IRF devices.)

Examples

# (Centralized devices.) Upgrade the device software with boot image file flash:/boot.bin, system image file flash:/system.bin, and feature image file flash:/feature1.bin. In this example, these images are compatible with the running images.

<Sysname> issu load 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

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

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

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

Identifying the upgrade methods….Done.

Upgrade summary according to following table:

flash:/boot.bin

Running Version New Version

Test 0001015 Test 0001016

flash:/system.bin

Running Version New Version

Test 0001015 Test 0001016

flash:/feature1.bin

Running Version New Version

None Test 0001016

Upgrade Way: Service Upgrade

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

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

# (Centralized devices.) Use the reboot method to upgrade the device software when the incremental upgrade method is recommended.

<Sysname> issu load file boot flash:/boot.bin system flash:/system.bin feature 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

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

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

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

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

Identifying the upgrade methods….Done.

Upgrade summary according to following table:

flash:/boot.bin

Running Version New Version

Test 0001015 Test 0001016

flash:/system.bin

Running Version New Version

Test 0001015 Test 0001016

flash:/feature1.bin

Running Version New Version

None Test 0001016

Upgrade Way: Reboot

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

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

# (Centralized devices.) Upgrade the device software with boot image file flash:/boot.bin, system image file flash:/system.bin, and feature image file flash:/feature1.bin. In this example, these images are incompatible with the running images.

<Sysname> issu load 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

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

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

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

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

Identifying the upgrade methods….Done.

Upgrade summary according to following table:

flash:/boot.bin

Running Version New Version

Test 0001015 Test 0001016

flash:/system.bin

Running Version New Version

Test 0001015 Test 0001016

flash:/feature1.bin

Running Version New Version

None Test 0001016

Upgrade Way: Reboot

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

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

# (Centralized IRF devices.) Upgrade member device 2 (a subordinate member) 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 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:/feature1.bin on slot 1...Done.

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

Verifying the file flash:/feature1.bin on slot 2...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

2 Service Upgrade

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

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

# (Centralized IRF devices.) Use the reboot method to upgrade member device 2 (a subordinate member) when the incremental upgrade method is recommended.

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

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

Verifying the file flash:/feature1.bin on slot 2...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

2 Reboot

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

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

# (Centralized IRF devices.) Upgrade member devices 3 and 4 (subordinate members) 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 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:/feature1.bin on slot 1...Done.

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

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

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

Verifying the file flash:/feature1.bin on slot 4...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

3 Reboot

4 Reboot

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

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

# (Distributed devices 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.

# (Distributed devices 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.

# (Distributed devices 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.

# (Distributed devices 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.

# (Distributed devices 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.

# (Distributed devices 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.

# (Distributed devices 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 9 Command output

Field | Description
Verifying the file | The system was verifying the validity of the file.
Copying file | (Distributed devices 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. (Centralized IRF devices.) The system was copying the upgrade file to a subordinate member. This field is displayed if you specified a subordinate member for the command. (Distributed devices 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. · ISSU Reboot. · 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 commands -- issu one-step

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

Syntax

Centralized devices:

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

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

Distributed devices 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 ]

Centralized IRF devices:

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

issu one-step file ipe ipe-filename slot slot-number&<1-9> [ 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 (multichassis):

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

issu one-step file ipe ipe-filename [ chassis chassis-number&<1-3> ] [ 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 device/master device/active MPU/global active MPU. 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 Fundamentals Configuration Guide.

ipe-filename: Specifies an .ipe file in the filesystemname/filename.ipe format. The file must be stored in the root directory of a file system on the device/master device/active MPU/global active MPU. 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 Fundamentals Configuration Guide.

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. (Distributed devices in standalone mode.)

slot slot-number: Specifies the member ID of a subordinate member. On a single-chassis IRF fabric, enter the member ID of the member device. On a multichassis IRF fabric, you can specify only one member ID for a compatible upgrade. The member device will become the master device after the ISSU. For an incompatible upgrade, you can specify a space-separated list of up to nine member IDs. As a best practice, specify half of the subordinate members if the member devices form a ring. Make sure the specified subordinate members are directly connected by physical links. The device automatically selects one of the specified subordinate members as the master device after the ISSU. (Centralized IRF devices.)

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 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. The device automatically selects one of the specified subordinate members as the master device after the ISSU. (On a multichassis 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.

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.

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. (Distributed devices in IRF mode.) (Centralized IRF devices.)

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 commands -- issu pex

Use issu pex to specify images used for PEX upgrade.

Syntax

issu pex pex-model file { boot filename | system filename | feature filename&<1-30> } *

issu pex pex-model file ipe ipe-filename

Views

User view

Predefined user roles

network-admin

Parameters

pex-model: Specifies the PEX model, a case-insensitive string of up to 63 characters. You must enter the complete PEX model name for the device to identify the PEX correctly. For available PEX models, enter boot-loader pex ?.

boot: Specifies a boot image file.

system: Specifies a system image file.

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

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

ipe 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 Fundamentals Configuration Guide.

Usage guidelines

Use this command if you want to upgrade PEXs during an ISSU that uses issu commands.

This command only specifies images used for PEX upgrade. This command does not load the upgrade images. The PEXs will load the upgrade images when the MPUs are upgraded. For more information, see Fundamentals Configuration Guide.

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.

If the PEXs have a storage medium, the system performs the following operations after verifying validity of the source file:

1. If you specify an .ipe file, the system automatically decompresses the .bin image files from the .ipe file to the same directory as the .ipe file.

2. Copies the .bin files to all PEXs of the specified model.

3. Displays a prompt for you to delete the following files:

?span style='font:7.0pt "Times New Roman"'> Source .ipe file (if any).

?span style='font:7.0pt "Times New Roman"'> Source .bin files if the .bin files are not on a PEX of the specified model.

If the PEXs do not have a storage medium, the system performs the following operations after verifying validity of the source file:

1. If you specify an .ipe file, the system automatically decompresses the .bin image files from the .ipe file to the same directory as the .ipe file.

2. Copies the .bin files to all other MPUs.

Examples

# (Centralized IRF devices.) Specify flash:/devkit.bin as the image for upgrading S5120HI PEXs. S5120HI PEXs do not have a storage medium.

<Sysname> issu pex PEX-S5120HI file feature flash:/devkit.bin

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

# (Centralized IRF devices.) Specify flash:/test.ipe as the image source for upgrading S5120HI PEXs. S5120HI PEXs do not have a storage medium.

<Sysname> issu pex PEX-S5120HI file ipe flash:/test.ipe

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

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

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

Overwrite the existing files? [Y/N]:Y

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

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

File flash:/devkit.bin already exists on slot 2.

File flash:/manufacture.bin already exists on slot 2.

Overwrite the existing files? [Y/N]:Y

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

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

# (Centralized IRF devices.) Specify flash:/devkit.bin as the image for upgrading S5500 PEXs. S5500 PEXs have storage media.

<Sysname> issu pex PEX-S5500 file feature flash:/devkit.bin

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

File flash:/devkit.bin already exists on slot 110.

Overwrite the existing files? [Y/N]:Y

Copying file flash:/devkit.bin to slot110#flash:/devkit.bin...Done.

Delete flash:/devkit.bin from slot 1? [Y/N]:Y

# (Centralized IRF devices.) Specify flash:/test.ipe as the image source for upgrading S5500 PEXs. S5500 PEXs have storage media.

<Sysname> issu pex PEX-S5500 file ipe flash:/test.ipe

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

Decompressing file devkit-patch.bin to flash:/devkit-patch.bin...Done.

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

Copying file flash:/devkit-patch.bin to slot110#flash:/devkit-patch.bin...Done.

Copying file flash:/manufacture.bin to slot110#flash:/manufacture.bin...Done.

Delete flash:/devkit-patch.bin from slot 1? [Y/N]:Y

Delete flash:/manufacture.bin from slot 1? [Y/N]:Y

Delete flash:/test.ipe from slot 1? [Y/N]:Y

# (Distributed devices in IRF mode.) Specify flash:/devkit.bin as the image for upgrading S5120HI PEXs. S5120HI PEXs do not have a storage medium.

<Sysname> issu pex PEX-S5120HI file feature flash:/devkit.bin

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

File flash:/devkit.bin already exists on chassis 1 slot 0.

Overwrite the existing files? [Y/N]:Y

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

# (Distributed devices in IRF mode.) Specify flash:/test.ipe as the image source for upgrading S5120HI PEXs. S5120HI PEXs do not have a storage medium.

<Sysname> issu pex PEX-S5120HI file ipe flash:/test.ipe

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

File flash:/devkit.bin already exists on chassis 1 slot 0.

File flash:/manufacture.bin already exists on chassis 1 slot 0.

Overwrite the existing files? [Y/N]:Y

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

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

File flash:/devkit.bin already exists on chassis 1 slot 1.

File flash:/manufacture.bin already exists on chassis 1 slot 1.

Overwrite the existing files? [Y/N]:Y

Copying file flash:/devkit.bin to chasis1#slot1#flash:/devkit.bin. ...Done.

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

# (Distributed devices in IRF mode.) Specify flash:/devkit.bin as the image for upgrading S5500 PEXs. S5500 PEXs have storage media.

<Sysname> issu pex PEX-S5500 file feature flash:/devkit.bin

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

File flash:/devkit.bin already exists on chassis 101 slot 0.

Overwrite the existing files? [Y/N]:Y

Copying file flash:/devkit.bin to chassis101#slot0#flash:/devkit.bin...Done.

Delete flash:/devkit.bin from chassis 1 slot 0? [Y/N]:Y

# (Distributed devices in IRF mode.) Specify flash:/test.ipe as the image source for upgrading S5500 PEXs.

<Sysname> issu pex PEX-S55500 file ipe flash:/test.ipe

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

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

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

Copying file flash:/devkit.bin to chassis101#slot0#flash:/devkit.bin...Done.

Copying file flash:/manufacture.bin to chassis101#slot0#flash:/manufacture.bin...Done.

Delete flash:/devkit.bin from chassis 1 slot 1? [Y/N]:Y

Delete flash:/manufacture.bin from chassis 1 slot 1? [Y/N]:Y

Delete flash:/test.ipe from chassis 1 slot 1? [Y/N]:Y

Related commands

issu load

ISSU commands -- issu pex-group

Use issu pex-group to create a PEX group and add PEXs to the PEX group.

Use undo issu pex-group to delete a PEX group or remove PEXs from a PEX group.

Syntax

Centralized IRF devices:

issu pex-group group-id slot { slot-id1 [ to slot-id2 ] }&<1-10>

undo issu pex-group { group-id | slot { slot-id1 [ to slot-id2 ] }&<1-10> }

Distributed devices in IRF mode:

issu pex-group group-id chassis { chassis-id1 [ to chassis-id2 ] }&<1-10>

undo issu pex-group { group-id | chassis { chassis-id1 [ to chassis-id2 ] }&<1-10> }

Default

No PEX group exists. PEXs reboot one by one during an ISSU reboot.

Views

System view

Predefined user roles

network-admin

Parameters

group-id: Specifies a group ID in the range of 1 to 2.

slot { slot-id1 [ to slot-id2 ] }&<1-10>: Specifies a space-separated list of up to 10 slot number items. An item specifies a PEX by its virtual slot number or specifies a range of PEXs in the form of start-slot-number to end-slot-number. The end slot number must be equal to or greater than the start slot number. (Centralized IRF devices.)

chassis { chassis-id1 [ to chassis-id2 ] }&<1-10>: Specifies a space-separated list of up to 10 chassis number items. An item specifies a PEX by its virtual chassis number or specifies a range of PEXs in the form of start-chassis-number to end-chassis-number. The end chassis number must be equal to or greater than the start chassis number. (Distributed devices in IRF mode.)

Usage guidelines

To use the ISSU reboot method to upgrade five or more PEXs, configure PEX groups to reduce the upgrade time.

· If you do not configure PEX groups, the PEXs reboot one by one during the upgrade. A PEX starts to reboot only after the previous PEX restarts up.

· If you configure PEX groups, the PEX groups reboot in order of group ID, and the PEXs in a PEX group reboot at the same time. After the final PEX that is in a PEX group starts up, the PEXs that do not belong to a PEX group reboot one by one.

For the PEX group settings to take effect after a reboot, save the running configuration after you configure PEX groups.

Examples

# (Centralized IRF devices.) Add the PEXs in the slot range of 100 to 105 and slot 107 to PEX group 1.

<Sysname> system-view

[Sysname] issu pex-group 1 slot 100 to 105 107

# (Distributed devices in IRF mode.) Add the PEXs in the virtual chassis range of 100 to 105 and virtual chassis 107 to PEX group 1.

<Sysname> system-view

[Sysname] issu pex-group 1 chassis 100 to 105 107

Related commands

issu load

issu pex

issu run switchover

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

(Centralized IRF devices.) A rollback performed for a multichassis IRF fabric after you execute the issu run switchover command cancels all operations performed during the ISSU process, including the master/subordinate switchover.

(Distributed devices in IRF mode.) A rollback performed for a multichassis 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 commands -- 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 set to 45 minutes.

Views

System view

Predefined user roles

network-admin

Parameters

minutes: Specifies the automatic rollback interval, in the range of 0 to 120 minutes. 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 multiple 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 commands -- 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

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

?span style='font:7.0pt "Times New Roman"'> Incremental upgrade—Performs a process-level active/standby switchover for the processes to be upgraded.

?span style='font:7.0pt "Times New Roman"'> Reboot upgrade or ISSU 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.

Centralized IRF devices:

Use this command on a multichassis IRF fabric.

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

?span style='font:7.0pt "Times New Roman"'> Incremental upgrade—Performs a process-level master/subordinate switchover for the processes to be upgraded.

?span style='font:7.0pt "Times New Roman"'> Reboot upgrade or ISSU upgrade—Reboots the current master with the old software version, causing the upgraded subordinate member to be elected as the new master.

· For an incompatible upgrade, the issu load command splits the IRF fabric into two fabrics, with the upgraded members forming a new fabric. The issu run switchover command reboots the members in the old IRF fabric with the upgrade images to upgrade the members. After startup, the members join the new IRF fabric as subordinate members.

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.

Distributed devices in IRF mode:

Use this command only on a multichassis 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:

?span style='font:7.0pt "Times New Roman"'> 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 or ISSU 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.

?span style='font:7.0pt "Times New Roman"'> 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 multichassis IRF fabric.) The function of this command is as follows:

?span style='font:7.0pt "Times New Roman"'> 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 or ISSU upgrade—Reboots the current master with the old software version to cause the upgraded subordinate member to become the new master.

?span style='font:7.0pt "Times New Roman"'> For an incompatible upgrade, the issu load command splits the IRF fabric into two fabrics, with the upgraded members forming a new fabric. The issu run switchover command reboots the old IRF fabric's members with the upgrade images to join the new IRF fabric as subordinate members.

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.

During a reboot upgrade to a compatible version, the LPUs and switching fabric modules reboot to load the new software from the upgraded MPU. A transient service outage occurs on the cards.

Examples

# (Distributed devices 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.

# (Distributed devices 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.

# (Centralized IRF devices.) 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:/feature1.bin

Running Version New Version

Test 0001015 Test 0001016

Slot Switchover Way

1 Active standby process switchover

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

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

# (Centralized IRF devices.) On a multichassis IRF fabric, perform a master/subordinate switchover, and upgrade members that have not been upgraded (member 1 and member 2) during an ISSU 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

1 Reboot

2 Reboot

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

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

# (Distributed devices 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 10 Command output

Field | Description
Switchover Way | Switchover method: · Active standby process switchover—Switch from the active process to the standby process. · (Distributed devices in standalone mode.) Active standby MPU switchover—Switch from the active MPU to the standby MPU. · (Distributed devices in IRF mode.) Global active standby MPU switchover—Switch from the global active MPU to a global standby MPU. · (Centralized IRF devices.) Master subordinate switchover—Switch from the master to a subordinate member.

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

Related commands

issu load

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

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

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