Table of Contents

Related Documents

08-ISSU commands

Title	Size	Download
08-ISSU commands	137.69 KB

ISSU commands

Field	Description
Active packages on slot n	Active software images on the specified member. The argument n indicates the member ID of the member.
[Package]	Detailed information about the software image.
Service name	Image type: · boot—Boot image. · system—System image. · system-patch—Patch image for the system image. · boot-patch—Patch image for the boot image. · Any other value indicates a feature image.
Supported board	Cards supported by the software image. The mpu string indicates a member device.
[Component]	Information about components included in the image file.

display install backup

Use display install backup to display backup startup software images.

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

slot slot-number: Specifies an IRF member device by its member ID. This command displays information for all member devices if you do not specify a member device.

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

Usage guidelines

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

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

Examples

# Display the backup startup software images.

<Sysname> display install backup

Backup startup software images on slot 1:

flash:/boot-a0201.bin

flash:/system-a0201.bin

# Display detailed information about backup startup software images.

<Sysname> display install backup verbose

Backup startup software images on slot 1:

flash:/boot-a0201.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: boot

Platform version: 7.1.022

Product version: Beta 1330

Supported board: mpu

[Component]

Component: boot

Description: boot package

flash:/system-a0201.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: system

Platform version: 7.1.022

Product version: Beta 1330

Supported board: mpu

[Component]

Component: system

Description: system package

For information about the command output, see Table 1.

Related commands

· boot-loader file

· display install committed

display install committed

Use display install committed to display main startup software images.

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

slot slot-number: Specifies an IRF member device by its member ID. This command displays information for all member devices if you do not specify a member device.

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

Usage guidelines

After you execute the install commit command, use the display install committed command to verify that the main startup image list has been updated with the software image change.

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

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

Examples

# Display the main startup software images.

<Sysname> display install committed

Committed packages on slot 1:

flash:/boot-a0201.bin

flash:/system-a0201.bin

flash:/system-patch.bin

# Display detailed information about main startup software images.

<Sysname> display install committed verbose

Committed packages on slot 1:

flash:/boot-a0201.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: boot

Platform version: 7.1.022

Product version: Beta 1330

Supported board: mpu

[Component]

Component: boot

Description: boot package

flash:/system-a0201.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: system

Platform version: 7.1.022

Product version: Beta 1330

Supported board: mpu

[Component]

Component: system

Description: system package

For information about the command output, see Table 1.

Related commands

· boot-loader file

· display install backup

· install commit

display install inactive

Use display install inactive to display inactive software images.

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

slot slot-number: Specifies an IRF member device by its member ID. This command displays information for all member devices if you do not specify a member device.

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

Usage guidelines

This command displays inactive images in the root directories of the storage media.

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

Product version: Beta 1330

Supported board: mpu

[Component]

Component: ssh

Description: ssh package

For information about the command output, see Table 1.

Related commands

install deactivate

display install ipe-info

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

Syntax

display install ipe-info ipe-filename

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

ipe-filename: Specifies the name of an .ipe file in the root directory of a storage medium on an IRF member device, in the [slotn#]storage-medium:/base-filename.ipe format. The slotn# section is optional if the file is on the master. The storage-medium:/base-filename.ipe section can have a maximum of 63 characters.

Usage guidelines

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

Examples

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

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

Verifying image file...Done.

Verifying the IPE file and the images.....Done.

Images in IPE:

boot.bin

system.bin

Related commands

display install package

display install job

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

Syntax

display install job

Views

Any view

Predefined user roles

network-admin

network-operator

Examples

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

display install log

Use display install log to display ISSU log information.

Syntax

display install log [ verbose ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

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

# Display all ISSU log entries.

<Sysname> display install log

Install job 1 started by user admin at 01/01/2011 04:53:40.

Job 1 completed successfully at 01/01/2011 04:53:46.

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

Install job 2 started by user admin at 01/01/2011 04:55:23.

Job 2 completed successfully at 01/01/2011 04:55:29.

# Displays detailed information about ISSU log entry 1.

<Sysname> display install log 1 verbose

Install job 1 started by user admin at 01/01/2011 04:53:40.

Job 1 completed successfully at 01/01/2011 04:53:46.

Detail of activating packages on slot 1.

Got upgrade policy successfully.

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

Install job 2 started by user admin at 01/01/2011 04:55:23.

Job 2 completed successfully at 01/01/2011 04:55:29.

Detail of activating packages on slot 1.

Got upgrade policy successfully.

Detail of activating packages on slot 1.

Updated active package list successfully.

Detail of activating packages on slot 1.

Set startup software images successfully.

Detail of activating packages on slot 1.

Start ISSU Reboot successfully.

Related commands

reset install log-history oldest

display install package

Use display install package to display software image file information.

Syntax

display install package { filename | all } [ verbose ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

filename: Specifies the name of a .bin file in the root directory of a storage medium on an IRF member device, in the [slotn#]storage-medium:/base-filename.bin format. The slotn# section is optional if the file is on the master. The storage-medium:/base-filename.bin section can have a maximum of 63 characters.

all: Specifies all software image files in the root directories of the master's storage media.

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

Examples

# Display information about software image file system.bin.

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

flash:/system.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: system

Platform version: 7.1.022

Product version: Beta 1330

Supported board: mpu

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

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

flash:/system.bin

[Package]

Vendor: H3C

Product: xxxx

Service name: system

Platform version: 7.1.022

Product version: Beta 1330

Supported board: mpu

[Component]

Component: system

Description: system package

For information about the command output, see Table 1.

display install rollback

Use display install rollback to display rollback point information.

Syntax

display install rollback

Views

Any view

Predefined user roles

network-admin

network-operator

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

# Display all rollback points.

<Sysname> display install rollback

Install rollback information 1 on slot 1:

Updating from flash:/boot-a2403.bin

to flash:/boot-a2404.bin.

Updating from flash:/system-a2403.bin

to flash:/system-a2404.bin.

The output shows that the device has one rollback point. At this rollback point, flash:/boot-a2403.bin and system-a2403.bin were upgraded to flash:/boot-a2404.bin and system-a2404, respectively.

Related commands

· install rollback

· reset install rollback oldest

display install which

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

Syntax

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

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

component name: Specifies a component name.

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

slot slot-number: Specifies an IRF member device by its member ID. This command displays information for all member devices if you do not specify a member device.

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 relevant image files before you make a software upgrade decision.

This command searches only the root directory of the storage medium.

Examples

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

<Sysname> display install which file sshc.cli

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

flash:/system-1330.bin

[Package]

Vendor: xxx

Product: xxxx

Service name: ssh

Platform version: 7.1.022

Product version: Beta 1330

Supported board: mpu

For information about the command output, see Table 1.

display issu rollback-timer

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

Syntax

display issu rollback-timer

Views

Any view

Predefined user roles

network-admin

network-operator

Usage guidelines

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

Examples

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

<Sysname> display issu rollback-timer

Rollback timer: Working

Rollback interval: 45 minutes

Rollback time remaining : 40 minutes

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

<Sysname> display issu rollback-timer

Rollback timer: Not working

Rollback interval: 30 minutes

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

<Sysname> display issu rollback-timer

Rollback timer: Not working

Rollback interval: 45 minutes

Related commands

issu rollback-timer

display issu state

Use display issu state to display ISSU status information.

Syntax

display issu state

Views

Any view

Predefined user roles

network-admin

network-operator

Usage guidelines

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

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

Examples

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

system: 7.1.041, Demo 2402

Current software images:

flash:/boot.bin

flash:/system.bin

# Display ISSU status information while the issu load command is being executed.

<Sysname> display issu state

ISSU state: Loading

Compatibility: Incompatible

Work state: Normal

Upgrade method: Card by card

Upgraded slot: None

Current upgrading slot:

slot 1

Previous version list:

boot: 7.1.041, Demo 2402

system: 7.1.041, Demo 2402

Previous software images:

flash:/boot.bin

flash:/system.bin

Upgrade version list:

boot: 7.1.041, Demo 2403

system: 7.1.041, Demo 2403

Upgrade software images:

flash:/boot02.bin

flash:/system04.bin

Table 2 Command output

Field	Description
ISSU state	ISSU status: · Init—The ISSU process has not started or has finished. · Loading—The system is executing the issu load command. · Loaded—The issu load command is completed. · Switching—The system is executing the issu run switchover command. · Switchover—The issu run switchover command is completed. · Accepted—The issu accept command is completed. · Committing—The system is executing the issu commit command. · Rollbacking—A rollback is in process.
Compatibility	Version compatibility: · Compatible. · Incompatible. · Unknown—No upgrade is in process.
Work state	Operating state of the device: · Normal—The device is operating correctly. · Independent active—When you perform an ISSU for an incompatible version, the member devices that have been upgraded enter this state. In this state, the member devices of the IRF fabric are running different software versions.
Upgrade method	Upgrade mode. If this field displays Card by card, the upgrade is performed on a member-by-member basis.
Upgraded slot	Upgraded member device.
Current upgrading slot	Member devices that are being upgraded.
Previous version list	Software versions running on the device before the ISSU.
Previous software images	Software images running on the device before the ISSU.
Upgrade version list	Software versions to upgrade to.
Upgrade software images	Software images used for the upgrade.

Related commands

· issu accept

· issu commit

· issu load

· issu rollback

· issu run switchover

display version comp-matrix

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

Syntax

display version comp-matrix

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

display version comp-matrix file ipe ipe-filename

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

boot: Specifies a boot image file.

system: Specifies a system image file.

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

filename: Specifies the name of a .bin file in the root directory of a storage medium on the master, in the storage-medium:/base-filename.bin format. It can be a case-insensitive string of up to 63 characters and cannot contain slot information.

ipe ipe-filename: Specifies the name of an .ipe file in the root directory of a storage medium on the master, in the storage-medium:/base-filename.ipe format. It can be a case-insensitive string of up to 63 characters and cannot contain slot information.

Usage guidelines

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

· Compatibility information for upgrade images.

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

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

<Sysname> display version comp-matrix

Boot image: flash:/boot-r2208p01.bin

Version:

7.1.035P05

System image: flash:/system-r2208p01.bin

Version:

R2208P01

Version compatibility list:

E2206P02

R2207

R2208

R2208P01

Version dependency boot list:

7.1.035P02

7.1.035P03

7.1.035P04

7.1.035P05

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

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

Boot image: flash:/boot-a2403.bin

Version:

7.1.046

System image: flash:/system-a2403.bin

Version:

A2403

Version compatibility list:

A2403

Version dependency boot list:

7.1.046

Incompatible upgrade.

# Display compatibility information for flash:/boot-f2209.bin and flash:/system-f2209.bin, and the recommended ISSU method. (In this example, the specified versions are compatible with the running versions.)

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

Boot image: flash:/boot-f2209.bin

Version:

7.1.035P08

System image: flash:/system-f2209.bin

Version:

F2209

Version compatibility list:

E2206P02

R2207

R2208

R2208P01

F2209

Version dependency boot list:

7.1.035P02

7.1.035P03

7.1.035P04

7.1.035P05

7.1.035P07

7.1.035P08

Slot Upgrade Way

1 ISSU Reboot

2 ISSU Reboot

Table 3 Command output

Field	Description
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 is in the list.
Version dependency system list	System image versions that support the feature image. To install the feature image, you must install one of the system image versions that is in the list.
Influenced service according to following table	Services that will be affected by the upgrade. This field is displayed only for compatible versions.
Incompatible upgrade	You are upgrading the software to an incompatible version.
Slot	Member ID of the device in the IRF fabric. 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—Reboots CPUs to complete the upgrade. · Reboot—Reboots the entire device to complete the upgrade. For more information about ISSU methods, see Fundamentals Configuration Guide.

Related commands

issu load

install abort

Use install abort to abort an ISSU operation.

Syntax

install abort

Views

User view

Predefined user roles

network-admin

Usage guidelines

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

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

Examples

# Abort a software image operation.

<Sysname> install abort

Related commands

display install job

install activate

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

Syntax

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

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

Views

User view

Predefined user roles

network-admin

Parameters

all: Specifies all IRF member devices.

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

patch: Specifies a patch image file.

slot slot-number: Specifies an IRF member device by its member ID.

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

Usage guidelines

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

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

If you specify a subordinate member for the command, the command copies the images to the subordinate member automatically.

At reboot, a subordinate device automatically synchronizes the master device's configuration and status data. You must wait for the synchronization to complete before using the install activate command on the subordinate device. To check the synchronization progress, use the display device command. The synchronization is completed when all member devices are in normal state.

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 or patch image files.

Examples

# Identify the ISSU method for feature upgrade with ssh2.bin on subordinate member 2 and the upgrade impact on the device.

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

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

Upgrade summary according to following table:

flash:/ssh2.bin

Running Version New Version

Beta 1330 Beta 1331

Slot Upgrade Way

2 Service Upgrade

Influenced service according to following table:

flash:/ssh2.bin

SSH IFMGR CFA LAGG

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

# Activate the patch image system-patch.bin on member device 1.

<Sysname> install activate system-patch.bin slot 1

# Activate the system image in file system.bin and feature images in file feature.bin on member device 2.

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

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

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

Upgrade summary according to following table:

flash:/system.bin

Running Version New Version

Beta 1330 Beta 1331

flash:/feature.bin

Running Version New Version

None Beta 1330

Slot Upgrade Way

2 Service Upgrade

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

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

Table 4 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.
Slot	Member ID of the device in the IRF fabric.
Upgrade Way	ISSU methods: · Service Upgrade—Service-level incremental upgrade. · File Upgrade—File-level incremental upgrade. The upgrade involves only hidden program files and does not affect the operation of the system or services. · ISSU Reboot—Reboots CPUs to complete the upgrade. · Reboot—Reboots the entire device to complete the upgrade. This field is displayed only for an upgrade to a compatible version.
Influenced service according to following table	Services influenced by the upgrade.

Related commands

· display install active

· install commit

· install deactivate

install add

Use install add to decompress an .ipe file.

Syntax

install add ipe-filename medium-name:

Views

User view

Predefined user roles

network-admin

Parameters

ipe-filename: Specifies the name of an .ipe file in the root directory of a storage medium on the master, in the storage-medium:/base-filename.ipe format. It can be a case-insensitive string of up to 63 characters and cannot contain slot information.

medium-name: Specifies the name of the storage medium for saving the software images. If the storage medium is on a subordinate member, use the slotn#storage-medium format, for example, slot1#flash.

Usage guidelines

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

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

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 image file..........................Done.

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

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

install commit

Use install commit to commit software changes.

Syntax

install commit

Views

User view

Predefined user roles

network-admin

Usage guidelines

Before you use this command, read the release notes to determine whether the images require licenses. Make sure the device has valid licenses for all license-based images.

This command revises the main startup software image list to be the same as the committed image list. Software changes take effect at the next startup.

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 revises 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 change main startup software images. To change backup startup images or add inactive images as main startup images, however, you must use the boot-loader file command.

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

Examples

# Commit software changes.

<Sysname> install commit

Related commands

· install activate

· install deactivate

· install rollback

install deactivate

Use install deactivate to deactivate feature or patch images.

Syntax

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

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

Views

User view

Predefined user roles

network-admin

Parameters

all: Specifies all IRF member devices.

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

patch: Specifies a patch image file.

slot slot-number: Specifies an IRF member device by its member ID.

Usage guidelines

You can deactivate only active feature and patch images.

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

At reboot, a subordinate device automatically synchronizes the master device's configuration and status data. You must wait for the synchronization to complete before using the install deactivate command on the subordinate device. To check the synchronization progress, use the display device command. The synchronization is completed when all member device are in normal state.

Examples

# Deactivate the patch images in file route-patch.bin on IRF member 1.

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

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

Related commands

· display install active

· display install inactive

install remove

Use install remove to remove inactive software images.

Syntax

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

Views

User view

Predefined user roles

network-admin

Parameters

slot slot-number: Specifies an IRF member device by its member ID. This command deletes inactive software images from all member devices if you do not specify a member device.

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

Usage guidelines

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

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

Examples

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

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

# Remove inactive patch package flash:/ssh-patch.bin.

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

install rollback to

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

Syntax

install rollback to { point-id | original }

Views

User view

Predefined user roles

network-admin

Parameters

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

original: Rolls back to the software images that were running before the ISSU.

Usage guidelines

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

· An ISSU reboot or reboot upgrade is performed.

· The install commit command is executed.

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

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

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

A maximum of 50 rollback points are available for service and file upgrades. The earliest rollback point is removed if this limit has been reached when a rollback point is created.

Patch images do not support rollback.

Examples

# Roll back the software to rollback point 1.

<Sysname>install rollback to 1

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

flash:/system-a0201.bin

flash:/ssh-feature-a0201.bin

<Sysname> display install rollback

Install rollback information 1 on slot 1:

Update from no package

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

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

<Sysname> install rollback to original

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

<Sysname> display install active

Active packages on slot 1:

flash:/boot-a0201.bin

flash:/system-a0201.bin

<Sysname> display install committed

Committed packages on slot 1:

flash:/boot-a0201.bin

flash:/system-a0201.bin

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

Related commands

display install rollback

install verify

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

Syntax

install verify

Views

User view

Predefined user roles

network-admin

Usage guidelines

To ensure a successful ISSU and make sure 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

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

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

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

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.

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 still use the issu rollback command to perform a manual rollback.

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

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

Examples

# Accept the upgrade to a compatible version.

<Sysname> issu accept

Related commands

· issu load

· issu run switchover

issu commit

Use issu commit to upgrade subordinate members (including the original master) during an ISSU to a compatible version.

Syntax

issu commit slot slot-number

Views

User view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

For a multichassis IRF fabric, use this command to upgrade subordinate members one by one. You must wait for the upgraded subordinate member to start up again and join the IRF fabric before upgrading another subordinate member. After all members are upgraded, the ISSU status changes to Init, and the ISSU process ends and cannot be rolled back.

For an IRF fabric with a single member, 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.

At reboot, a subordinate device automatically synchronizes the master device's configuration and status data. You must wait for the synchronization to complete before using the issu commit command on the subordinate device. To check the synchronization progress, use the display device command. The synchronization is completed when all member device are in normal state.

Examples

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

Running Version New Version

Alpha 7122 Alpha 7123

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

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

Upgrade summary according to following table:

flash:/feature.bin

Running Version New Version

Alpha 7122 Alpha 7123

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

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

Upgrade summary according to following table:

flash:/feature.bin

Running Version New Version

Alpha 7122 Alpha 7123

Slot Upgrade Way

1 Service Upgrade

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

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

For information about the command output, see Table 3.

Related commands

· issu accept

· issu load

· issu run switchover

issu load

Use issu load to upgrade the software images of subordinate members and configure the upgrade images as the main startup software images for the subordinate members.

Syntax

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

issu load file ipe ipe-filename slot slot-number&<1-9>

Views

User view

Predefined user roles

network-admin

Parameters

boot: Specifies a boot image file.

system: Specifies a system image file.

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

slot slot-number: Specifies the 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 nine member IDs. If the IRF fabric has only one member, enter the member ID of this member to upgrade the entire fabric.

Usage guidelines

On a single-chassis IRF fabric, specify the member ID of the member for this command.

On a multichassis IRF fabric, specify one or more subordinate members for this command. As a best practice, specify half of the subordinate members for this command to reduce service interruption if the member devices are connected into a ring topology. Make sure the specified subordinate members are physically connected.

This command performs the following tasks:

· Examines the compatibility of the specified images with the running images. 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 member devices will be rebooted.

The ISSU method for an incompatible version is always reboot.

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

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 check the synchronization progress, use the display device command. The synchronization is completed when all member device are in normal state.

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

Examples

# Upgrade member device 2 (subordinate member) with the feature image file flash:/feature.bin. (In this example, the image is compatible with the running images.)

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

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

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

Upgrade summary according to following table:

flash:/feature.bin

Running Version New Version

Alpha 7122 Alpha 7123

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.

# Upgrade member device 3 and 4 (subordinate members) with the feature image file flash:/feature.bin. (In this example, the image is incompatible with the running images.)

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

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

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

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

Upgrade summary according to following table:

flash:/feature.bin

Running Version New Version

Alpha 7122 Alpha 7123

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.

Table 5 Command output

Field	Description
Slot	Member ID of the device in the IRF fabric.
Upgrade Way	ISSU method: · Service Upgrade—Service-level incremental upgrade. · File Upgrade—File-level incremental upgrade. · ISSU Reboot—Reboots CPUs to complete the upgrade. · Reboot—Reboots the entire device to complete the upgrade. For more information about ISSU methods, see Fundamentals Configuration Guide.

Field

Description

Slot

Member ID of the device in the IRF fabric.

Upgrade Way

ISSU method:

· Service Upgrade—Service-level incremental upgrade.

· File Upgrade—File-level incremental upgrade.

· ISSU Reboot—Reboots CPUs to complete the upgrade.

· Reboot—Reboots the entire device to complete the upgrade.

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

issu rollback

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

Syntax

issu rollback

Views

User view

Predefined user roles

network-admin

Usage guidelines

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

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

· Loaded.

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

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

· Accepted.

If you perform a manual rollback while an ISSU is in Loading state, the ISSU process ends without changing the original software versions.

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

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

If the IRF fabric has multiple members, a rollback performed after you execute the issu run switchover command cancels all operations performed during the ISSU process, including the master/subordinate switchover operation.

Examples

# Roll back to the original software versions.

<Sysname> issu rollback

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

Related commands

· issu accept

· issu commit

· issu load

· issu run switchover

issu rollback-timer

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

Use undo issu rollback-timer to restore the default.

Syntax

issu rollback-timer minutes

undo issu rollback-timer

Default

The automatic rollback interval is 45 minutes.

Views

System view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

The automatic software version rollback feature is only available on a multichassis IRF fabric during an ISSU to a compatible version.

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 versions before the ISSU.

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

Examples

# Set the automatic rollback timer to 50 minutes.

<Sysname> system-view

[Sysname] issu rollback-timer 50

Related commands

issu rollback

issu run switchover

Use issu run switchover to perform a master/subordinate switchover. If the new and old versions are incompatible, this command also upgrades all members that have not been upgraded.

Syntax

issu run switchover

Views

User view

Predefined user roles

network-admin

Usage guidelines

Use this command on multichassis IRF fabrics.

· For a compatible version, this command performs tasks 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, causing the upgraded subordinate member to be elected as 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 the members in the old IRF fabric with the upgrade images. 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 check the synchronization progress, use the display device command. The synchronization is completed when all member device are in normal state.

Examples

# On a multichassis IRF fabric, perform a master/subordinate switchover during an ISSU to a compatible version.

<Sysname> issu run switchover

Upgrade summary according to following table:

flash:/feature.bin

Running Version New Version

Alpha 7122 Alpha 7123

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.

# 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

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

Upgrade summary according to following table:

flash:/feature.bin

Running Version New Version

Alpha 7122 Alpha 7123

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.

Table 6 Command output

Field	Description
Switchover Way	Switchover method: · Active standby process switchover—Switch from the active process to the standby process. · Master subordinate switchover—Switch from the master to a subordinate member.

Field

Description

Switchover Way

Switchover method:

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

· Master subordinate switchover—Switch from the master to a subordinate member.

For information about other fields, see Table 3.

Related commands

issu load

reset install log-history oldest

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

Syntax

reset install log-history oldest log-number

Views

User view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

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

Examples

# Clear the two oldest ISSU log entries.

<Sysname> reset install log-history oldest 2

Related commands

display install log

reset install rollback oldest

Use reset install rollback oldest to clear ISSU rollback points.

Syntax

reset install rollback oldest point-id

Views

User view

Predefined user roles

network-admin

Parameters

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

Usage guidelines

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

Examples

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

<Sysname> reset install rollback oldest 2

Related commands

display install rollback

01-Fundamentals Command Reference

ISSU commands

display install log

display issu state

display version comp-matrix

install deactivate

install rollback to

issu accept

issu commit

issu load

issu rollback-timer

Cloud & AI

InterConnect

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Resources

Partner Business Management

Company Information

News & Events

Contact Us