Table of Contents

Related Documents

08-ISSU commands

Title	Size	Download
08-ISSU commands	233.38 KB

ISSU commands

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

Because change to the automatic-rollback interval does not take effect for the ongoing ISSU process (if any), the current remaining rollback time might be greater than the configured automatic-rollback interval.

Examples

# Display automatic-rollback timer information after the issu load 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 going on.

<Sysname> display issu rollback-timer

Rollback timer: Not working

Rollback interval: 45 minutes

Related commands

issu rollback-timer

display issu state

Use display issu state to display ISSU status information.

Syntax

display issu state

Views

Any view

Predefined user roles

network-admin

network-operator

Usage guidelines

The key to an ISSU is to follow the proper upgrade procedure. You can use this command to view the ISSU status and thereby determine what to do next.

Examples

# In standalone mode or IRF mode (single-member), display ISSU status information when no upgrade is going on.

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

system: Comware V700R001B34D001

ssh: Comware V700R001B34D001

Current software images:

cfa0:/boot.bin

cfa0:/system.bin

cfa0:/ssh.bin

# In standalone mode, display ISSU status information when the issu load command is being executed.

<Sysname> display issu state

ISSU state: Loading

Compatibility: Incompatible

Work state: Normal

Upgrade method: Card by card

Upgraded slot: None

Current upgrading slot:

slot 1

Previous version list:

boot: 7.1.033

system: Comware V700R001B33D001

ssh: Comware V700R001B33D001

Previous software images:

cfa0:/boot.bin

cfa0:/system.bin

cfa0:/ssh.bin

Upgrade version list:

boot: 7.1.034

system: Comware V700R001B34D001

ssh: Comware V700R001B34D001

Upgrade software images:

cfa0:/boot02.bin

cfa0:/system04.bin

cfa0:/ssh04.bin

# In IRF mode (single-member), display ISSU status information when the issu load command is being executed.

<Sysname> display issu state

ISSU state: Loading

Compatibility: Incompatible

Work state: Normal

Upgrade method: Card by card

Upgraded slot: None

Current upgrading slot:

chassis 1 slot 1

Previous version list:

boot: 7.1.033

system: Comware V700R001B33D001

ssh: Comware V700R001B33D001

Previous software images:

cfa0:/boot.bin

cfa0:/system.bin

cfa0:/ssh.bin

Upgrade version list:

boot: 7.1.034

system: Comware V700R001B34D001

ssh: Comware V700R001B34D001

Upgrade software images:

cfa0:/boot02.bin

cfa0:/system04.bin

cfa0:/ssh04.bin

# In IRF mode (single-member), 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.033

system: Comware V700R001B33D001

ssh: Comware V700R001B33D001

Previous software images:

cfa0:/boot.bin

cfa0:/system.bin

cfa0:/ssh.bin

Upgrade version list:

boot: 7.1.034

system: Comware V700R001B34D001

ssh: Comware V700R001B34D001

Upgrade software images:

cfa0:/system02.bin

cfa0:/ssh02.bin

# In IRF mode (multi-member), display ISSU status information on the original master after the issu load command is completed.

<Sysname> display issu state

ISSU state: Loaded

Compatibility: Incompatible

Work state: Independent active

Upgrade method: Chassis by chassis

Upgraded chassis:

chassis 2

Current upgrading chassis: None

Previous version list:

boot: 7.1.033

system: Comware V700R001B33D001

ssh: Comware V700R001B33D001

Previous software images:

cfa0:/boot.bin

cfa0:/system.bin

cfa0:/ssh.bin

Upgrade version list:

boot: 7.1.034

system: Comware V700R001B34D001

ssh: Comware V700R001B34D001

Upgrade software images:

cfa0:/system04.bin

cfa0:/ssh04.bin

Table 1 Command output

Field	Description
ISSU state	ISSU status: · Init—The ISSU process has not been 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 going on. · Unknown—An upgrade is going on. This field might appear when you execute the command on an original standby MPU.
Compatibility	Version compatibility: · Compatible. · Incompatible. · Unknown—No upgrade is going on.
Work state	Operating mode of the device: · Normal—The device is operating normally. · Independent active—When you perform an ISSU for an incompatible version, the standby MPU that is upgraded first enters this mode. In this mode, the two MPUs of the device are running different software versions.
Upgrade method	Upgrade mode: · Card by card—MPU-based upgrade. One MPU is upgraded first, and then the other MPU is upgraded. · Chassis by chassis—IRF member-based upgrade. One or more subordinate members are upgraded first, and then the original master and the remaining subordinate members are upgraded. (In IRF mode.)
Upgraded slot	Upgraded cards.
Current upgrading slot	Cards that are being upgraded.
Upgraded chassis	Upgraded members. (In IRF mode.)
Current upgrading chassis	Members that are being upgraded.
Previous version list	Software versions running on the device before the ISSU. If you execute this command on an original standby MPU during an ISSU for an incompatible version, the value of this field is Unknown.
Previous software images	Software images running on the device before the ISSU. If you execute this command on an original standby MPU during an ISSU for an incompatible version, the value of this field is Unknown.
Upgrade version list	Software versions to upgrade to. If you execute this command on an original standby MPU during an ISSU for an incompatible version, the value of this field is Unknown.
Upgrade software images	Software images used for the upgrade. If you execute this command on an original standby MPU during an ISSU for an incompatible version, the value of this field is Unknown.

Related commands

· issu load

· issu run switchover

· issu accept

· issu commit

· issu rollback

display version comp-matrix

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

Syntax

display version comp-matrix

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

display version comp-matrix file ipe ipe-filename

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

boot: Specifies a boot image file.

system: Specifies a system image file.

feature: Specifies a feature image file. { filename }&<1-30> indicates that you can specify up to 30 feature image files.

filename: Specifies the name of a software image file in the format storage medium name:/xxx.bin, for example, flash:/a.bin. It can be a case-insensitive string of 1 to 63 characters and cannot contain slot information. The specified file must be saved in the root directory of a storage medium on the active MPU. (In standalone mode.)

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

ipe ipe-filename: Specifies the name of an IPE file in the format storage medium name:/xxx.ipe, for example, flash:/a.ipe. It can be a case-insensitive string of 1 to 63 characters. The specified file must be saved in the root directory of a storage medium on the active MPU. (In standalone mode.)

Usage guidelines

If you do not specify any file, the command displays the compatibility information of the running software versions.

If you specify one or more file names, the command displays the compatibility information of the specified software images and the ISSU methods to be used to upgrade the running versions to the specified versions.

Examples

# Display the compatibility information of the running software versions.

<Sysname> display version comp-matrix

Boot image: cfa0:/cmw710-boot-a7122.bin

Version:

7.1.034

System image: cfa0:/cmw710-system-a7122.bin

Version:

V700R001B34D001

Version compatibility list:

V700R001B34D001

Version dependency boot list:

7.1.034

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

Version: V700R001B34D003

Version compatibility list:

V700R001B34D003

Version dependency system list:

V700R001B34D001

V700R001B34D002

# In standalone mode, display the compatibility information of cmw710-cfa-a7125.bin and the ISSU methods to be used to upgrade the software to the specified version. (This example assumes the specified version is compatible with the running version.)

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

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

Version:

V700R001B34D002

Version compatibility list:

V700R001B34D001

V700R001B34D002

Version dependency system list:

V700R001B34D001

V700R001B34D002

Slot Upgrade Way

0 Service Upgrade

0.1 File Upgrade

1 Service Upgrade

1.1 File Upgrade

4 Service Upgrade

Influenced service according to following table on slot 0:

cfa0:/cmw710-cfa-a7125.bin

CFA

Influenced service according to following table on slot 1:

cfa0:/cmw710-cfa-a7125.bin

CFA

Influenced service according to following table on slot 4:

cfa0:/cmw710-cfa-a7125.bin

CFA

# In IRF mode, display the compatibility information of cmw710-cfa-a7122.bin and the ISSU methods to be used to upgrade the software to the specified version. (This example assumes the specified version is compatible with the running version.)

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

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

Version:

V700R001B34D002

Version compatibility list:

V700R001B34D001

V700R001B34D002

Version dependency system list:

V700R001B34D001

V700R001B34D002

Chassis Slot Upgrade Way

1 1 Service Upgrade

1 1.1 File Upgrade

1 7 Service Upgrade

1 9 Service Upgrade

2 1 Service Upgrade

2 1.1 File Upgrade

2 4 Service Upgrade

2 6 Service Upgrade

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

cfa0:/cmw710-cfa-a7122.bin

CFA

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

cfa0:/cmw710-cfa-a7122.bin

CFA

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

cfa0:/cmw710-cfa-a7122.bin

CFA

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

cfa0:/cmw710-cfa-a7122.bin

CFA

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

cfa0:/cmw710-cfa-a7122.bin

CFA

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

cfa0:/cmw710-cfa-a7122.bin

CFA

Table 2 Command output

Field	Description
Version compatibility list	History versions that are compatible with this version.
Version dependency boot list	Boot image versions that support the image.
Version dependency system list	System image versions that support the image.
Influenced service according to following table	Services that will be affected by the upgrade. This field is displayed only for compatible versions.
Incompatible upgrade	You are upgrading the software to an incompatible version.
Chassis	Member ID of the device in the IRF fabric. This field is displayed only for compatible versions in IRF mode.
Slot	Slot number of the card. This field is displayed only for compatible versions.
Upgrade Way	ISSU method to be used for a compatible version: · Service Upgrade—Service-level incremental upgrade. · File Upgrade—File-level incremental upgrade. · ISSU Reboot. · Reboot. · Sequence Reboot—This method is only available for switching fabric cards. For more information about ISSU methods, see Fundamentals Configuration Guide. This field is displayed only for compatible versions.

Related commands

issu load

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

If you execute this command for an ISSU to an incompatible version, an error message appears.

After you execute this command, the automatic-rollback timer is deleted and the system does not perform automatic rollback for the ISSU process anymore. However, you can use the issu rollback command to manually roll back to the original software configuration.

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

Examples

# Accept the upgrade to a compatible version.

<Sysname> issu accept

Related commands

· issu load

· issu run switchover

issu commit

In standalone mode:

· If the device has two MPUs, use issu commit to upgrade the original active MPU to a compatible version.

· If the device has only one MPU, use issu commit to finish the upgrade of the MPU to a compatible version.

After this command is completed, the ISSU status transitions to Init, and the ISSU process ends and cannot be rolled back anymore.

In IRF mode:

· When the IRF fabric has only one member and the member has two MPUs, use issu commit to upgrade the original global active MPU to a compatible version. After this command is completed, the ISSU status transitions to Init, and the ISSU process ends and cannot be rolled back anymore.

· When the IRF fabric has only one member and the member has only one MPU, use issu commit to finish the ISSU to a compatible version. After this command is completed, the ISSU status transitions to Init, and the ISSU process ends and cannot be rolled back anymore.

· When the IRF fabric has multiple members, use issu commit to upgrade ungraded subordinate members (including the original master) to a compatible version. After using this command to upgrade one subordinate member, you must wait for the subordinate member to restart up and join the IRF fabric before upgrading another subordinate member. After all members are upgraded, the ISSU status transitions to Init, and the ISSU process ends and cannot be rolled back anymore.

Syntax

In standalone mode:

issu commit slot slot-number

In IRF mode (single-member):

issu commit chassis chassis-number slot slot-number

In IRF mode (multi-member):

issu commit chassis chassis-number

Views

User view

Predefined user roles

network-admin

Parameters

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

chassis chassis-number slot slot-number: Specifies the member ID and slot number of the original active MPU. (In IRF mode, single-member.)

chassis chassis-number: Specifies the member ID of the original master or an unupgraded subordinate member. (In IRF mode, multi-member.)

Examples

# In standalone mode, upgrade the original active MPU to a compatible version. (In this example the device has two MPUs.)

<Sysname> issu commit slot 0

Upgrade summary according to following table:

cfa0:/feature.bin

Running Version New Version

Alpha 7122 Alpha 7123

Slot Upgrade Way

0 Service Upgrade

0.1 File Upgrade

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

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

<Sysname> issu commit slot 0

# In IRF mode, upgrade the unupgraded members to a compatible version. (In this example the IRF fabric has multiple members.)

<Sysname> issu commit chassis 3

Upgrade summary according to following table:

cfa0:/feature.bin

Running Version New Version

Alpha 7122 Alpha 7123

Chassis Slot Upgrade Way

3 0 Service Upgrade

3 0.1 File Upgrade

3 1 Service Upgrade

3 1.1 File Upgrade

3 2 Service Upgrade

3 3 Service Upgrade

3 4 Service Upgrade

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

<Sysname> issu commit chassis 4

Upgrade summary according to following table:

cfa0:/feature.bin

Running Version New Version

Alpha 7122 Alpha 7123

Chassis Slot Upgrade Way

4 0 Service Upgrade

4 0.1 File Upgrade

4 1 Service Upgrade

4 1.1 File Upgrade

4 2 Service Upgrade

4 3 Service Upgrade

4 4 Service Upgrade

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

<Sysname> issu commit chassis 1

Upgrade summary according to following table:

cfa0:/feature.bin

Running Version New Version

Alpha 7122 Alpha 7123

Chassis Slot Upgrade Way

1 0 Service Upgrade

1 0.1 File Upgrade

1 1 Service Upgrade

1 1.1 File Upgrade

1 2 Service Upgrade

1 3 Service Upgrade

1 4 Service Upgrade

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

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

<Sysname> issu commit chassis 1 slot 0

Upgrade summary according to following table:

cfa0:/feature.bin

Running Version New Version

Alpha 7122 Alpha 7123

Chassis Slot Upgrade Way

1 0 Service Upgrade

1 0.1 File Upgrade

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

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

<Sysname> issu commit chassis 1 slot 0

For field descriptions, see Table 2.

Related commands

· issu load

· issu run switchover

· issu accept

issu load

In standalone mode, use issu load to upgrade the boot, system, and feature images of the standby MPU and configure the upgrade images as the main startup software images for the standby MPU.

In IRF mode:

· When the IRF fabric has only one member, use issu load to upgrade the boot, system, and feature images of a global standby MPU and configure the upgrade images as the startup software images for the standby MPU.

· When the IRF fabric has multiple members, use issu load to upgrade the boot, system, and feature images of subordinate members and configure the upgrade images as the main startup software images for the subordinate members.

Syntax

In standalone mode:

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

issu load file ipe ipe-filename slot slot-number

In IRF mode (single-member):

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

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

In IRF mode (multi-member):

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

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

Views

User view

Predefined user roles

network-admin

Parameters

boot: Specifies a boot image file.

system: Specifies a system image file.

feature: Specifies a feature image file. { filename }&<1-30> indicates that you can specify up to 30 feature image files.

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

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 whole device. (In standalone mode.)

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

chassis chassis-number: Specifies the member ID of a subordinate member. &<1-3> means that you can specify up to three member IDs. When the IRF fabric has multiple members, you can specify only one member ID if the old version and the new version are compatible and can specify multiple member IDs if the old version and the new version are incompatible. (In IRF mode, multi-member.)

Usage guidelines

In standalone mode, when the device has only one MPU, specify the slot number of the MPU for this command. When the device has two MPUs, specify the slot number of the standby MPU for this command. In either case, this command performs the following operations:

· Examines the compatibility of the specified images with the running versions. The result might be compatible or incompatible.

· Determines the ISSU methods.

The ISSU methods available for a compatible version include:

¡ Incremental upgrade. During the upgrade, the involved processes will be upgrade.

¡ ISSU reboot. During the upgrade, CPUs will be rebooted.

¡ Reboot. During the upgrade, the device (if single-MPU) or the standby MPU (if dual-MPU) will be rebooted.

The ISSU method for an incompatible version is always reboot.

· Uses the ISSU methods to upgrade the specified MPU, and configures the upgrade software images as the main startup software images for the specified MPU.

In IRF mode:

An IRF fabric might have a single member or multiple members, and a single-member IRF fabric might have one or two MPUs:

· When the IRF fabric has only one member and the member has only one MPU, specify the member ID and slot number of the only MPU for this command.

· When the IRF fabric has only one member and the member has two MPUs, specify the member ID and slot number of the standby MPU for this command.

· When the IRF fabric has multiple members, specify one or more subordinate members for this command.

In any of these cases, the command performs the following operations:

· Examines the compatibility of the specified images with the running versions. The result might be compatible or incompatible.

· Determines the ISSU methods.

The ISSU methods available for a compatible version include:

¡ Incremental upgrade. During the upgrade, the involved processes will be upgrade.

¡ ISSU reboot. During the upgrade, CPUs will be rebooted.

¡ Reboot. During the upgrade, the specified MPU or member devices will be rebooted.

The ISSU method for an incompatible version is always reboot.

· Uses the ISSU methods to upgrade the specified MPU or member devices, and configures the upgrade software images as the main startup software images for the specified MPU or member devices.

For more information about ISSU methods, see Fundamentals Configuration Guide.

Examples

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

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

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

Upgrade summary according to following table:

cfa0:/feature.bin

Running Version New Version

Alpha 7122 Alpha 7123

Slot Upgrade Way

1 Service Upgrade

1.1 File Upgrade

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

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

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

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

Upgrade summary according to following table:

cfa0:/feature.bin

Running Version New Version

Alpha 7122 Alpha 7123

Slot Upgrade Way

1 Reboot

1.1 Reboot

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

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

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

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

Upgrade summary according to following table:

cfa0:/feature.bin

Running Version New Version

Alpha 7122 Alpha 7123

Slot Upgrade Way

0 Service Upgrade

0.1 File Upgrade

2 Service Upgrade

3 Service Upgrade

4 Service Upgrade

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

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

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

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

Upgrade summary according to following table:

cfa0:/feature.bin

Running Version New Version

Alpha 7122 Alpha 7123

Slot Upgrade Way

0 Reboot

0.1 Reboot

2 Reboot

3 Reboot

4 Reboot

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

# In IRF mode (multi-member), upgrade member device 2 (a subordinate member) with the feature image file cfa0:/feature.bin. (In this example the image is compatible with the running images.)

<Sysname> issu load file feature cfa0:/feature.bin chassis 2

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

Upgrade summary according to following table:

cfa0:/feature.bin

Running Version New Version

Alpha 7122 Alpha 7123

Chassis Slot Upgrade Way

2 0 Service Upgrade

2 0.1 File Upgrade

2 1 Service Upgrade

2 1.1 File Upgrade

2 2 Service Upgrade

2 3 Service Upgrade

2 4 Service Upgrade

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

# In IRF mode (multi-member), upgrade member devices 3 and 4 (subordinate members) with the feature image file cfa0:/feature.bin. (In this example the image is incompatible with the running images.)

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

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

Upgrade summary according to following table:

cfa0:/feature.bin

Running Version New Version

Alpha 7122 Alpha 7123

Chassis Slot Upgrade Way

3 0 Reboot

3 0.1 Reboot

3 1 Reboot

3 1.1 Reboot

3 2 Reboot

3 3 Reboot

3 4 Reboot

4 0 Reboot

4 0.1 Reboot

4 1 Reboot

4 1.1 Reboot

4 2 Reboot

4 3 Reboot

4 4 Reboot

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

# In IRF mode (single-member, dual-MPU), upgrade the standby MPU on member device 1 with the feature image file cfa0:/feature.bin. (In this example the image is compatible with the running images.)

<Sysname>issu load file feature cfa0:/feature.bin chassis 1 slot 1

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

Upgrade summary according to following table:

cfa0:/feature.bin

Running Version New Version

Alpha 7122 Alpha 7123

Chassis Slot Upgrade Way

1 1 Service Upgrade

1 1.1 File Upgrade

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

# In IRF mode (single-member, dual-MPU), upgrade the standby MPU on member device 1 with the feature image file cfa0:/feature.bin. (In this example the image is incompatible with the running images.)

<Sysname>issu load file feature cfa0:/feature.bin chassis 1 slot 1

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

Upgrade summary according to following table:

cfa0:/feature.bin

Running Version New Version

Alpha 7122 Alpha 7123

Chassis Slot Upgrade Way

1 1 Reboot

1 1.1 Reboot

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

# In IRF mode (single-member, single-MPU), upgrade the MPU on member device 1 with the feature image file cfa0:/feature.bin. (In this example the image is compatible with the running images.)

<Sysname>issu load file feature cfa0:/feature.bin chassis 1 slot 0

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

Upgrade summary according to following table:

cfa0:/feature.bin

Running Version New Version

Alpha 7122 Alpha 7123

Chassis Slot Upgrade Way

1 0 Service Upgrade

1 0.1 File Upgrade

1 2 Service Upgrade

1 3 Service Upgrade

1 4 Service Upgrade

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

# In IRF mode (single-member, single-MPU), upgrade the MPU on member device 1 with the feature image file cfa0:/feature.bin. (In this example the image is incompatible with the running images.)

<Sysname>issu load file feature cfa0:/feature.bin chassis 1 slot 0

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

Upgrade summary according to following table:

cfa0:/feature.bin

Running Version New Version

Alpha 7122 Alpha 7123

Chassis Slot Upgrade Way

1 0 Reboot

1 0.1 Reboot

1 2 Reboot

1 3 Reboot

1 4 Reboot

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

Table 3 Command output

Field	Description
Chassis	Member ID of the device in the IRF fabric. (In IRF mode.)
Slot	Slot number of the card.
Upgrade Way	ISSU method: · Service Upgrade—Service-level incremental upgrade. · File Upgrade—File-level incremental upgrade. · ISSU Reboot. · Reboot. · Sequence Reboot—This method is only available for switching fabric cards. For more information about ISSU methods, see Fundamentals Configuration Guide.

issu rollback

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

Syntax

issu rollback

Views

User view

Predefined user roles

network-admin

Usage guidelines

The device supports automatic rollback and manual rollback. You trigger a manual rollback with this command.

The result of this command depends on when you execute this command:

· When the ISSU status is Loading, the ISSU process quits and no rollback occurs.

· When the ISSU status is Loaded or Accepted, the system rolls back to the original software configuration.

· When the ISSU status is Switching or Switchover and the ISSU is for a compatible version, the system rolls back to the original software configuration.

· When the ISSU status is Switching and the ISSU is for an incompatible version, manual rollback is not supported.

· When the ISSU status is Committing, neither automatic rollback nor manual rollback is supported.

When the IRF fabric has multiple members, a rollback performed after you execute the issu run switchover command cancels only the upgrades. The master/subordinate switchover operation is not canceled. (In IRF mode.)

Examples

# Roll back to the original software configuration.

<Sysname> issu rollback

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

Related commands

· issu load

· issu run switchover

· issu accept

· issu commit

issu rollback-timer

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

Use undo issu rollback-timer to restore the default.

Syntax

issu rollback-timer minutes

undo issu rollback-timer

Default

The automatic-rollback interval is 45 minutes.

Views

System view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

The automatic software version rollback function is only available on a dual-MPU device, a multi-member IRF fabric, or a single-member dual-MPU IRF fabric during an ISSU to a compatible version.

When you execute the issu run switchover command in a scenario where automatic rollback is supported, the system starts the automatic-rollback timer. If you do not execute the issu accept or issu commit command before the timer expires, the system automatically rolls back to the original software configuration, the software configuration prior to the ISSU.

Change to the automatic-rollback interval does not take effect for the ongoing ISSU process (if any).

Examples

# Set the automatic-rollback timer to 50 minutes.

<Sysname> system-view

[Sysname] issu rollback-timer 50

Related commands

issu rollback

issu run switchover

In standalone mode:

· If the new and old versions are compatible, use issu run switchover to perform an active/standby switchover and upgrade the interface cards.

· If the new and old versions are incompatible, use issu run switchover to perform an active/standby switchover and upgrade all cards except for the upgraded MPU.

In IRF mode:

· If the IRF fabric has only one member and the new and old versions are compatible, use issu run switchover to perform an active/standby switchover and upgrade the interface cards.

· If the IRF fabric has only one member and the new and old versions are incompatible, use issu run switchover to perform an active/standby switchover and upgrade all cards except for the upgraded MPU.

· If the IRF fabric has multiple members and the new and old versions are compatible, use issu run switchover to perform a master/subordinate switchover.

· If the IRF fabric has multiple members and the new and old versions are incompatible, use issu run switchover to perform a master/subordinate switchover and upgrade all members that have not been upgraded.

Syntax

issu run switchover

Views

User view

Predefined user roles

network-admin

Usage guidelines

In standalone mode, this command is not necessary when the device has only one MPU. When the device has two MPUs, this command performs the following operations:

· For a compatible version, the operations depend 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 to cause the upgraded MPU to become the new active MPU and upgrades the interface cards.

· For an incompatible version—Reboots the current active MPU and the interface cards with the new software version, causing the upgraded MPU to become the new active MPU. After the reboot, the original active MPU and the interface cards are upgraded and the ISSU process ends.

In IRF mode, this command is not necessary when the IRF fabric has only one member and the member has only one MPU.

When the IRF fabric has only one member and the member has two MPUs, this command performs the following operations:

· For a compatible version, the operations depend 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 to cause the upgraded MPU to become the new active MPU and upgrades the interface cards.

When the IRF fabric has multiple members, this command performs the following operations:

· For a compatible version, the operations depend 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.

· For an incompatible version—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 and upgrades the old IRF fabric. After startup, the old fabric's members join the new IRF fabric as subordinate members and the ISSU process ends.

During a reboot upgrade to a compatible version, the interface cards reboot to load the new software from the upgraded MPU. Traffic traveling through the interface cards will be interrupted while the interface cards reboot and recover.

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

Examples

# In standalone mode, perform an active/standby switchover and upgrade the interface cards to a compatible version. (In this example the device has two MPUs.)

<Sysname> issu run switchover

Upgrade summary according to following table:

cfa0:/feature.bin

Running Version New Version

Alpha 7122 Alpha 7123

Slot Switchover Way

0 Active standby process switchover

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

# In standalone mode, perform an active/standby switchover and upgrade the current active MPU and the interface cards to an incompatible version. (In this example the device has two MPUs.)

<Sysname> issu run switchover

Upgrade summary according to following table:

cfa0:/feature.bin

Running Version New Version

Alpha 7122 Alpha 7123

Slot Upgrade Way

0 Reboot

0.1 Reboot

2 Reboot

3 Reboot

4 Reboot

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

# In IRF mode (multi-member), perform a master/subordinate switchover during an ISSU to a compatible version.

<Sysname> issu run switchover

Upgrade summary according to following table:

cfa0:/feature.bin

Running Version New Version

Alpha 7122 Alpha 7123

Chassis Slot Switchover Way

1 0 Active standby process switchover

1 0.1 Active standby process switchover

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

# In IRF mode (multi-member), perform a master/subordinate switchover and upgrade unupgraded members (member 1 and member 2) during an ISSU to an incompatible version.

<Sysname> issu run switchover

Upgrade summary according to following table:

cfa0:/feature.bin

Running Version New Version

Alpha 7122 Alpha 7123

Chassis Slot Upgrade Way

1 0 Reboot

1 0.1 Reboot

1 1 Reboot

1 1.1 Reboot

1 2 Reboot

1 3 Reboot

1 4 Reboot

2 0 Reboot

2 0.1 Reboot

2 1 Reboot

2 1.1 Reboot

2 2 Reboot

2 3 Reboot

2 4 Reboot

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

# In IRF mode (single-member, dual MPU), perform a master/subordinate switchover and upgrade the interface cards during an ISSU to a compatible version.

<Sysname> issu run switchover

Upgrade summary according to following table:

cfa0:/feature.bin

Running Version New Version

Alpha 7122 Alpha 7123

Chassis Slot Switchover Way

1 0 Active standby process switchover

1 0.1 Active standby process switchover

Chassis Slot Upgrade Way

1 2 Service Upgrade

1 3 Service Upgrade

1 4 Service Upgrade

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

# In IRF mode (single-member, dual MPU), perform a master/subordinate switchover during an ISSU to an incompatible version.

<Sysname> issu run switchover

Upgrade summary according to following table:

cfa0:/feature.bin

Running Version New Version

Alpha 7122 Alpha 7123

Chassis Slot Upgrade Way

1 0 Reboot

1 0.1 Reboot

1 2 Reboot

1 3 Reboot

1 4 Reboot

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

Table 4 Command output

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

Field

Description

Switchover Way

Switchover method:

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

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

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

For descriptions of other fields, see Table 2.

Related commands

issu load

install series commands

display install active

Use display install active to display active software images.

Syntax

In standalone mode:

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

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

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

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

Examples

# In standalone mode, display active software images.

<Sysname> display install active

Active packages on slot 1:

flash:/boot.bin

flash:/system.bin

flash:/ssh-feature.bin

Active packages on slot 1.1:

flash:/boot.bin

flash:/system.bin

flash:/ssh-feature.bin

# In IRF mode, display active software images.

<Sysname> display install active

Active packages on chassis 1 slot 1:

flash:/boot.bin

flash:/system.bin

flash:/ssh-feature.bin

Active packages on chassis 1 slot 1.1:

flash:/boot.bin

flash:/system.bin

flash:/ssh-feature.bin

# In standalone mode, display detailed information about active software images.

<Sysname> display install active verbose

Active packages on slot 1:

flash:/boot.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: boot

Platform version: 7.1.025

Product version: Beta 1330

Supported board: mr, lc, sfc

[Component]

Component: boot

Description: boot package

flash:/system.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: system

Platform version: 7.1.025

Product version: Beta 1330

Supported board: mr, lc, sfc

[Component]

Component: system

Description: system package

flash:/ssh-feature.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: ssh

Platform version: 7.1.025

Product version: Beta 1330

Supported board: mr, lc, sfc

[Component]

Component: ssh

Description: ssh package

# In IRF mode, display detailed information about active software images.

<Sysname> display install active verbose

Active packages on chassis 1 slot 1:

flash:/boot.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: boot

Platform version: 7.1.025

Product version: Beta 1330

Supported board: mr, lc, sfc

[Component]

Component: boot

Description: boot package

flash:/system.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: system

Platform version: 7.1.025

Product version: Beta 1330

Supported board: mr, lc, sfc

[Component]

Component: system

Description: system package

flash:/ssh-feature.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: ssh

Platform version: 7.1.025

Product version: Beta 1330

Supported board: mr, lc, sfc

[Component]

Component: ssh

Description: ssh package

Table 5 Command output

Field	Description
Active packages on slot n	Active software images on the card in the specified slot. (In standalone mode.)
Active packages on chassis m slot n	Active software images on the card in the specified slot of the specified member. (In IRF mode.)
[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	Cards supported by the software image: · mr—MPU. · lc—Interface card. · sfc—Switching fabric card.
[Component]	Information about components included in the image file.

Related commands

install active

display install backup

Use display install backup to display backup startup software images.

Syntax

In standalone mode:

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

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

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

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

Usage guidelines

Only the boot-loader file command changes the backup startup software image set.

For more information about backup startup software images and the backup startup software image set, see Fundamental Configuration Guide.

Examples

# In standalone mode, display the backup startup software images.

<Sysname> display install backup

Backup startup software images on slot 1:

flash:/boot-r7122.bin

flash:/system-r7122.bin

Backup startup software images on slot 1.1:

flash:/boot-r7122.bin

flash:/system-r7122.bin

# In IRF mode, display the backup startup software images.

<Sysname> display install backup

Backup startup software images on chassis 1 slot 1:

flash:/boot-r7122.bin

flash:/system-r7122.bin

Backup startup software images on chassis 1 slot 1.1:

flash:/boot-r7122.bin

flash:/system-r7122.bin

# Display detailed information about backup startup software images.

<Sysname> display install backup verbose

Backup startup software images on slot 1:

flash:/boot-r7122.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: boot

Platform version: 7.1.025

Product version: Beta 1330

Supported board: mr, lc, sfc

[Component]

Component: boot

Description: boot package

flash:/system-r7122.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: system

Platform version: 7.1.025

Product version: Beta 1330

Supported board: mr, lc, sfc

[Component]

Component: system

Description: system package

For command output descriptions, see Table 5.

Related commands

· display install committed

· boot-loader file

display install committed

Use display install committed to display main startup software images.

Syntax

In standalone mode:

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

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

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

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

Usage guidelines

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

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

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

Examples

# Display the main startup software images.

<Sysname> display install committed

Committed packages on slot 1:

flash:/boot-r7122.bin

flash:/system-r7122.bin

flash:/feature.bin

Committed packages on slot 1.1:

flash:/boot-r7122.bin

flash:/system-r7122.bin

flash:/feature.bin

# Display detailed information about main startup software images.

<Sysname> display install committed verbose

Committed packages on slot 1:

flash:/boot-r7122.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: boot

Platform version: 7.1.025

Product version: Beta 1330

Supported board: mr, lc, sfc

[Component]

Component: boot

Description: boot package

flash:/system-r7122.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: system

Platform version: 7.1.025

Product version: Beta 1330

Supported board: mr, lc, sfc

[Component]

Component: system

Description: system package

flash:/ssh-feature.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: ssh

Platform version: 7.1.025

Product version: Beta 1330

Supported board: mr, lc, sfc

[Component]

Component: ssh

Description: ssh package

For command output descriptions, see Table 5.

Related commands

· display install backup

· install commit

· boot-loader file

display install inactive

Use display install inactive to display inactive software images.

Syntax

In standalone mode:

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

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

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

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

Examples

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

<Sysname> display install inactive

Inactive packages on slot 1:

flash:/ssh-feature.bin

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

<Sysname> display install inactive verbose

Inactive packages on slot 1:

flash:/ssh-feature.bin

[Package]

Vendor: H3C

Product: XXXX

Service name: ssh

Platform version: 7.1.025

Product version: Beta 1330

Supported board: mr, lc, sfc

[Component]

Component: ssh

Description: ssh package

For information about the command output, see Table 5.

Related commands

install deactivate

display install ipe-info

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

Syntax

display install ipe-info ipe-file

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

ipe-file: Specifies the name of an existing IPE file, a string of 1 to 63 characters. It must include the storage medium name and the extension .ipe, for example, flash:/new.ipe. If the specified IPE file does not exist, the command fails.

Usage guidelines

An IPE file contains one or more software images. You can select software images from an IPE and use them for software upgrade.

Examples

# Display information about IPE file flash:/12500-ssh.ipe.

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

Images in IPE:

ssh.bin

The output shows that IPE file flash:/12500-ssh.ipe contains only one software image: SSH feature image ssh.bin.

Related commands

display install package

display install job

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

Syntax

display install job

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Examples

# In standalone mode, display ongoing ISSU activate, deactivate, and rollback operations.

<Sysname> display install job

JobID:5

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

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

# In IRF mode, display ongoing ISSU activate, deactivate, and rollback operations.

<Sysname> display install job

JobID:5

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

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

display install log

Use display install log to display ISSU logs.

Syntax

display install log [ log-id ] [ verbose ]

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

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

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

Usage guidelines

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

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

Examples

# Display all ISSU logs.

<Sysname> display install log

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

Job 1 completed successfully at 04/28/2010 08:39:29.

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

Install activate flash:/ssh.bin on slot 1

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

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

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

Job 2 completed successfully at 04/28/2010 08:40:29.

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

Install activate flash:/route.bin on slot 1

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

# Displays detailed information about ISSU log 1.

<Sysname> display install log 1 verbose

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

Job 1 completed successfully at 04/28/2010 08:39:29.

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

Install activate flash:/ssh.bin on slot 1

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

Detail of activating packages on slot 1.

Got upgrade policy successfully.

Detail of activating packages on slot 1.

Uncompressed package to system successfully.

Removed files from system successfully.

Related commands

reset install log-history oldest

display install package

Use display install package to display software image file information.

Syntax

display install package { filename | all } [ verbose ]

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

filename: Specifies the name of a software image file, a case-insensitive string of 1 to 63 characters. This file must be saved in the root directory of an MPU's Flash and use the extension .bin. If the file is saved on the active MPU, enter its name in the format flash:/xxx.bin. If the file is saved on the standby MPU, enter its name in the format slotn#flash:/xxx.bin, where n represents the number of the slot holding the standby MPU. (In standalone mode.)

filename: Specifies the name of a software image file, a case-insensitive string of 1 to 63 characters. This file must be saved in the root directory of a member device's Flash and use the extension .bin. If the file is saved on the active MPU of the master, enter its name in the format flash:/xxx.bin. If the file is saved on a subordinate device, enter its name in the format chassism#slotn#flash:/xxx.bin, where m represents the member ID of the subordinate device and m represents the number of the slot holding the MPU. (In IRF mode.)

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

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

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

Examples

# Display information about software image file system.bin.

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

flash:/system.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: system

Platform version: 7.1.022

Product version: Beta 1330

Supported board: mr, lc, sfc

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

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

flash:/system.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: system

Platform version: 7.1.022

Product version: Beta 1330

Supported board: mr, lc, sfc

[Component]

Component: system

Description: system package

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

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

mdc-admin

mdc-operator

Parameters

point-id: Specifies a rollback point ID.

Usage guidelines

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

Examples

# Display all rollback points.

<Sysname> display install rollback

Install rollback information 1 on slot 0:

Updating from flash:/route-1.bin

to flash:/route-2.bin.

Install rollback information 2 on slot 0:

Deactivating flash:/route-2.bin

The output shows that the device has two rollback points in total:

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

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

Related commands

· install rollback

· reset install rollback oldest

display install which

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

Syntax

In standalone mode:

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

In IRF mode:

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

Views

Any view

Predefined user roles

network-admin

network-operator

mdc-admin

mdc-operator

Parameters

component name: Specifies a component name.

file filename: Specifies a file name, a case-insensitive string of 1 to 63 characters. You do not need to specify the path information.

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

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

Usage guidelines

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

Examples

# Display all software image files that include file sshc.cli and information about the software image files.

<Sysname> display install which file sshc.cli

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

flash:/ssh-feature.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: ssh

Platform version: 7.1.022

Product version: Beta 1330

Supported board: mr, lc, sfc

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

install abort

Use install abort to abort an ISSU operation.

Syntax

install abort

Views

User view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

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

You can abort only a software image activate or deactivate operation that is being executed for an incremental upgrade or downgrade.

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

Examples

# Abort a software image operation.

<Sysname> install abort

Related commands

display install job

install activate

Use install activate to activate software images, or check for the ISSU method to be used for the upgrade and view the possible impact of the upgrade.

Syntax

In standalone mode:

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

install activate patch filename slot slot-number

In IRF mode:

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

install activate patch filename chassis chassis-number slot slot-number

Views

User view

Predefined user roles

network-admin

mdc-admin

Parameters

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

system: Specifies a system image file.

feature: Specifies a feature image file. The filename&<1-30> option indicates that you can specify up to 30 feature image files.

patch: Specifies a patch image file.

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

slot slot-number: Specifies an MPU by its slot number.(In standalone mode.)

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

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

Usage guidelines

The device supports these categories of ISSU methods: incremental upgrade, ISSU reboot, and reboot. When you perform an ISSU, the device compares the compatibility between the old and new software versions and selects an ISSU method based on the version compatibility. You can also use the install activate command with the test keyword to check for the ISSU method to be used for the upgrade and view the possible impact of the upgrade. For more information about ISSU methods and ISSU guidelines, see Fundamentals Configuration Guide.

An image takes effect only after it is activated.

To keep an activated image active after a reboot, you must confirm the software change by using the install commit command.

Examples

# In standalone mode, check for the ISSU method to be used for feature upgrade of the MPU in slot 1 with image file ssh2.bin and view the possible impact of the upgrade.

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

Upgrade summary according to following table:

flash:/ssh2.bin

Running Version New Version

Beta 1330 Beta 1331

Slot Upgrade Way

1 Service Upgrade

1.1 File Upgrade

Influenced service according to following table:

flash:/ssh2.bin

SSH IFMGR CFA LAGG

The output shows that a service upgrade will be used for the upgrade, and the SSH, IFMGR, CFA, and LAGG modules will be rebooted during the upgrade process.

# In IRF mode, check for the ISSU method to be used for feature upgrade of the MPU in slot 0 on IRF member 1, with image file ssh2.bin, and view the possible impact of the upgrade.

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

Upgrade summary according to following table:

flash:/ssh2.bin

Running Version New Version

Beta 1330 Beta 1331

Chassis Slot Upgrade Way

1 0 Service Upgrade

1 0.1 File Upgrade

1 4 Service Upgrade

Influenced service according to following table:

flash:/ssh2.bin

SSH IFMGR CFA LAGG

The output shows that a service upgrade will be used for the upgrade, and the SSH, IFMGR, CFA, and LAGG modules will be rebooted during the upgrade process.

# In standalone mode, activate the system image in file system.bin and feature images in file feature.bin on the MPU in slot 1.

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

Upgrade summary according to following table:

flash:/system.bin

Running Version New Version

Beta 1330 Beta 1331

flash:/feature.bin

Running Version New Version

None Beta 1330

Slot Upgrade Way

1 Service Upgrade

1.1 File Upgrade

2 Service Upgrade

3 ISSU Reboot

4 Reboot

5 Sequence Reboot

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

# In IRF mode, activate the feature images in file route-feature.bin on the MPU in slot 0 of IRF member 1.

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

Upgrade summary according to following table:

flash:/route-feature.bin

Running Version New Version

None Beta 1330

Chassis Slot Upgrade Way

1 0 Service Upgrade

1 0.1 File Upgrade

1 4 Service Upgrade

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

Table 6 Command output

Field	Description
Upgrade summary according to following table	Upgrade summary.
Running Version	Version number of the running software.
New Version	Version number of the new software.
Chassis	Member ID of the device in the IRF fabric. (In IRF mode.)
Slot	Number of the slot where the card resides.
Upgrade Way	ISSU methods: · Service Upgrade—Service-level incremental upgrade. This type of upgrade affects only the upgraded service modules. It does not affect the system or the other service modules. · File Upgrade—File-level incremental upgrade. The upgrade involves only hidden program files and does not affect the operation of the system or services. · ISSU Reboot. · Reboot. · Sequence Reboot—Upgrading the switching fabric cards one by one. This method applies only when the device has switching fabric cards that support this upgrade method. When the switching fabric cards need to be rebooted for upgrade, the system upgrades one switching fabric card at a time, and continues to upgrade another switching fabric card only after the upgraded switching fabric card restarts up. This method ensures uninterrupted services.
Influenced service according to following table	Services influenced by the upgrade.

Related commands

· install commit

· install deactivate

· display install active

install add

Use install add to decompress an IPE file.

Syntax

install add ipe-file medium-name:

Views

User view

Predefined user roles

network-admin

mdc-admin

Parameters

ipe ipe-filename: Specifies the name of an IPE file in the format storage medium name:/xxx.ipe, for example, flash:/new.ipe. It can be a string of 1 to 63 characters.

medium-name: Specifies the name of the storage medium for saving the software images. To specify a storage medium on the active MPU, enter its name directly, flash or cfa0. To specify a storage medium on the standby MPU, prefix its name with the string slotn#, where n represents the number of the slot holding the standby MPU, for example, slot1#flash or slot1#cfa0. (In standalone mode.)

medium-name: Specifies the name of the storage medium for saving the software images. To specify a storage medium on the master's active MPU, enter its name directly, flash or cfa0. To specify a storage medium on any other MPU, prefix its name with the chassism#slotn#, where m represents the member ID of the subordinate device and m represents the number of the slot holding the MPU, for example, chassis1#slot1#flash or chassism#slotn#cfa0. (In IRF mode.)

Usage guidelines

An IPE file contains a set of software images that can run together. By obtaining an IPE file, you obtain all the software images, without the requirement for considering the compatibility between the images.

The software images decompressed from the IPE file will be saved to the root directory of the specified medium.

To view which software images are included in an IPE file, use the display install ipe-info command.

Examples

# Decompress IPE file route.ipe to the Flash.

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

install commit

Use install commit to confirm the software changes.

Syntax

install commit

Views

User view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

The install activate, install deactivate, and install rollback commands change only the current software configuration. To make the changes survive a reboot, you must use the install commit command to confirm the software changes.

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

The boot-loader file command can also change the main startup software image set. The differences between these two commands are that the boot-loader file command can change the backup startup software image set as well and can add inactive software images to the image sets.

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

Examples

# Confirm the software changes.

<Sysname> install commit

Related commands

· install activate

· install deactivate

· install rollback

install deactivate

Use install deactivate to deactivate feature images and patch images.

Syntax

In standalone mode:

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

install deactivate patch filename slot slot-number

In IRF mode:

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

install deactivate patch filename chassis chassis-number slot slot-number

Views

User view

Predefined user roles

network-admin

mdc-admin

Parameters

filename: Specifies the name of a software image file in the format storage medium name:/xxx.bin, for example, flash:/a.bin. It can be a case-insensitive string of 1 to 63 characters. The filename&<1-30> option indicates that you can specify up to 30 feature or patch image files.

slot slot-number: Specifies an MPU by its slot number. (In standalone mode.)

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

Usage guidelines

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

To keep deactivated images inactive after a reboot, you must confirm the software change by using the install commit command.

Examples

# In standalone mode, deactivate the patch images in file route-patch.bin on the MPU in slot 0.

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

# In IRF mode, deactivate the patch images in file route-patch.bin on the MPU in slot 0 of IRF member 1.

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

Related commands

· display install active

· display install inactive

install remove

Use install remove to remove inactive software images.

Syntax

In standalone mode:

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

In IRF mode:

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

Views

User view

Predefined user roles

network-admin

mdc-admin

Parameters

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

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

filename: Specifies the name of a software image file in the format storage medium name:/xxx.bin, for example, flash:/a.bin. It can be a case-insensitive string of 1 to 63 characters. The specified file must be saved in the root directory of a storage medium on the active MPU. (In standalone mode.)

filename: Specifies the name of a software image file in the format storage medium name:/xxx.bin, for example, flash:/a.bin. It can be a case-insensitive string of 1 to 63 characters. The specified file must be saved in the root directory of a storage medium on the global active MPU. (In IRF mode.)

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

Usage guidelines

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

Removing a software image deletes the image file from the device permanently. This operation can neither be reverted by using the install rollback to command nor be aborted by using the install abort command.

Examples

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

<Sysname> install remove flash:/ssh-feature.bin

install rollback to

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

Syntax

install rollback to { point-id | original }

Views

User view

Predefined user roles

network-admin

mdc-admin

Parameters

point-id: Specifies a rollback point ID. To view available rollback points, use the display install rollback command.

original: Rolls back to the software configuration before you perform an ISSU.

Usage guidelines

Every time you activate or deactivate a software image for an incremental upgrade, the system creates a rollback point to record the current software configuration. Before you execute the install commit command to confirm the software changes (executing this command also removes all rollback points), you can roll back the software configuration to a rollback point to cancel all software image upgrade-related operations performed after the rollback point. You can also roll back the software configuration to the original software configuration, the software configuration before you perform an ISSU.

For incremental upgrades, up to 50 rollback points are supported. After the limit is reached, the oldest rollback point is deleted to make room for a newly created one.

For ISSU upgrades and reboot upgrades, the system does not record and maintain any rollback point, and you can roll back the software configuration only to the original software configuration.

Examples

# Roll back the software configuration to rollback point 1.

<Sysname>install rollback to 1

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

<Sysname> display install active

Active packages on slot 0:

flash:/boot-r7122.bin

flash:/system-r7122.bin

flash:/ssh-feature-r7122.bin

Active packages on slot 0.1:

flash:/boot-r7122.bin

flash:/system-r7122.bin

flash:/ssh-feature-r7122.bin

<Sysname> display install rollback

Install rollback information 1 on slot 0:

Updating from flash:/ssh-feature-r7122.bin

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

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

<Sysname> install rollback to original

<Sysname> display install active

Active packages on slot 0:

flash:/boot-r7122.bin

flash:/system-r7122.bin

Active packages on slot 0.1:

flash:/boot-r7122.bin

flash:/system-r7122.bin

<Sysname> display install committed

Committed packages on slot 0:

flash:/boot-r7122.bin

flash:/system-r7122.bin

Committed packages on slot 0.1:

flash:/boot-r7122.bin

flash:/system-r7122.bin

The output shows the device is rolled back to the original software configuration and image flash:/ssh-feature-r7122.bin has been removed.

Related commands

display install rollback

install verify

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

Syntax

install verify

Views

User view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

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

To solve the problem, download and install the software images again to ensure software integrity, or use the install activate, install deactivate, and install commit commands as appropriate to guarantee software image consistency.

Examples

# In standalone mode, verify the software change confirmation status and software image integrity and consistency.

<Sysname> install verify

Active packages on slot 1 are the reference packages.

Packages will be compared with the reference packages.

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

Verifying packages on slot 0:

Start to check active package completeness.

flash:/boot-a0101.bin verification successful.

flash:/system-a0101.bin verification successful.

Start to check active package consistency.

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

Active packages are consistent with the reference packages.

Verifying packages on slot 1:

Start to check active package completeness.

flash:/boot-a0101.bin verification successful.

flash:/system-a0101.bin verification successful.

Start to check active package consistency.

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

Active packages are consistent with the reference packages.

Verification is done.

# In IRF mode, verify the software change confirmation status and software image integrity and consistency.

<Sysname> install verify

Active packages on slot 1 are the reference packages.

Packages will be compared with the reference packages.

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

Verifying packages on chassis 1 slot 0:

Start to check active package completeness.

flash:/boot-a0101.bin verification successful.

flash:/system-a0101.bin verification successful.

Start to check active package consistency.

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

Active packages are consistent with the reference packages.

Verifying packages on chassis 1 slot 1:

Start to check active package completeness.

flash:/boot-a0101.bin verification successful.

flash:/system-a0101.bin verification successful.

Start to check active package consistency.

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

Active packages are consistent with the reference packages.

Verification is done.

reset install log-history oldest

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

Syntax

reset install log-history oldest log-number

Views

User view

Predefined user roles

network-admin

mdc-admin

Parameters

log-number: Specifies the number of ISSU logs to be deleted.

Usage guidelines

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

Examples

# Clear the two oldest ISSU logs.

<Sysname> reset install log-history oldest 2

Related commands

display install log

reset install rollback oldest

Use reset install rollback oldest to clear ISSU rollback points.

Syntax

reset install rollback oldest point-id

Views

User view

Predefined user roles

network-admin

mdc-admin

Parameters

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

Usage guidelines

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

Examples

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

<Sysname> reset install rollback oldest 2

Related commands

display install rollback

01-Fundamentals Command Reference

ISSU commands

ISSU series commands

display install committed

display install inactive

display install rollback

install abort

install commit

install deactivate

install rollback to

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program

Global Learning

Partner Sales Resources

Service Business

News & Events

Contact Us