Login
- Table of Contents
-
- 01-Fundamentals Command Reference
- 00-Preface
- 01-CLI commands
- 02-RBAC commands
- 03-Login management commands
- 04-FTP and TFTP commands
- 05-File system management commands
- 06-Configuration file management commands
- 07-Software upgrade commands
- 08-ISSU commands
- 09-Emergency shell commands
- 10-Automatic configuration commands
- 11-Device management commands
- 12-Security zone commands
- 13-Tcl commands
- 14-Python commands
- 15-License management commands
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 08-ISSU commands | 124.51 KB |
ISSU 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
Parameters
slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays information for all cards. (In standalone mode.)
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command displays information for all cards. (In IRF mode.)
verbose: Displays detailed information. If you do not specify this keyword, the command displays only image names.
Examples
# (In standalone mode.) Display active software images.
<Sysname> display install active
Active packages on slot 0:
cfa0:/boot.bin
cfa0:/system.bin
cfa0:/feature.bin
# (In IRF mode.) Display active software images.
<Sysname> display install active
Active packages on chassis 1 slot 0:
cfa0:/boot.bin
cfa0:/system.bin
cfa0:/feature.bin
# (In standalone mode.) Display detailed information about active software images.
<Sysname> display install active verbose
Active packages on slot 0:
cfa0:/boot.bin
[Package]
Vendor: H3C
Product: sr66x1
Service name: boot
Platform version: 7.1.064
Product version: Ess 7602P02
Supported board: rse3 fip300 4exp fip600 16exp fip240 sfe1
[Component]
Component: boot
Description: boot package
cfa0:/system.bin
[Package]
Vendor: H3C
Product: sr66x1
Service name: system
Platform version: 7.1.064
Product version: Ess 7602P02
Supported board: rse3 fip300 4exp fip600 16exp fip240 sfe1
[Component]
Component: system
Description: system package
cfa0:/feature.bin
[Package]
Vendor: H3C
Product: sr66x1
Service name: test
Platform version: 7.1.064
Product version: Ess 7602P02
Supported board: rse3 fip300 4exp fip600 16exp fip240 sfe1
[Component]
Component: test
Description: test package
# (In IRF mode.) Display detailed information about active software images.
<Sysname> display install active verbose
Active packages on chassis 1 slot 0:
cfa0:/boot.bin
[Package]
Vendor: H3C
Product: sr66x1
Service name: boot
Platform version: 7.1.064
Product version: Ess 7602P02
Supported board: rse3 fip300 4exp fip600 16exp fip240 sfe1
[Component]
Component: boot
Description: boot package
cfa0:/system.bin
[Package]
Vendor: H3C
Product: sr66x1
Service name: system
Platform version: 7.1.064
Product version: Ess 7602P02
Supported board: rse3 fip300 4exp fip600 16exp fip240 sfe1
[Component]
Component: system
Description: system package
cfa0:/feature.bin
[Package]
Vendor: H3C
Product: sr66x1
Service name: test
Platform version: 7.1.064
Product version: Ess 7602P02
Supported board: rse3 fip300 4exp fip600 16exp fip240 sfe1
[Component]
Component: test
Description: test package
|
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. · boot patch—Patch image for the boot image. · system patch—Patch image for the system image. · Any other value indicates a feature image. |
|
Supported board |
Card types supported by the software image. |
|
[Component] |
Information about components included in the image file. |
Related commands
install active
display install backup
Use display install backup to display backup startup software images.
Syntax
In standalone mode:
display install backup [ slot slot-number ] [ verbose ]
In IRF mode:
display install backup [ chassis chassis-number slot slot-number ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays information for all cards. (In standalone mode.)
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command displays information for all cards. (In IRF mode.)
verbose: Displays detailed information. If you do not specify this keyword, the command displays only image names.
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
# (In standalone mode.) Display the backup startup software images.
<Sysname> display install backup
Backup startup software images on slot 0:
cfa0:/boot-a0201.bin
cfa0:/system-a0201.bin
# (In IRF mode.) Display the backup startup software images.
<Sysname> display install backup
Backup startup software images on chassis 1 slot 0:
cfa0:/boot-a0201.bin
cfa0:/system-a0201.bin
# Display detailed information about backup startup software images.
<Sysname> display install backup verbose
Backup startup software images on slot 0:
cfa0:/boot-a0201.bin
[Package]
Vendor: H3C
Product: sr66x1
Service name: boot
Platform version: 7.1.064
Product version: Ess 7602P02
Supported board: rse3 fip300 4exp fip600 16exp fip240 sfe1
[Component]
Component: boot
Description: boot package
cfa0:/system-a0201.bin
[Package]
Vendor: H3C
Product: sr66x1
Service name: system
Platform version: 7.1.064
Product version: Ess 7602P02
Supported board: rse3 fip300 4exp fip600 16exp fip240 sfe1
[Component]
Component: system
Description: system package
For information about the command output, see Table 1.
Related commands
boot-loader file
display install committed
display install committed
Use display install committed to display main startup software images.
Syntax
In standalone mode:
display install committed [ slot slot-number ] [ verbose ]
In IRF mode:
display install committed [ chassis chassis-number slot slot-number ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays information for all cards. (In standalone mode.)
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command displays information for all cards. (In IRF mode.)
verbose: Displays detailed information. If you do not specify this keyword, the command displays only image names.
Usage guidelines
Some install commands do not modify the main startup image list. For the software image changes to take effect after reboot, you must execute the install commit command to update the main startup image list with the image changes. You can use the display install committed command to verify the operation results.
Both the install commit and boot-loader file commands modify the main startup software image list.
Examples
# Display the main startup software images.
<Sysname> display install committed
Committed packages on slot 0:
cfa0:/boot-a0201.bin
cfa0:/system-a0201.bin
cfa0:/feature.bin
# Display detailed information about main startup software images.
<Sysname> display install committed verbose
Committed packages on slot 0:
cfa0:/boot-a0201.bin
[Package]
Vendor: H3C
Product: sr66x1
Service name: boot
Platform version: 7.1.064
Product version: Ess 7602P02
Supported board: rse3 fip300 4exp fip600 16exp fip240 sfe1
[Component]
Component: boot
Description: boot package
cfa0:/system-a0201.bin
[Package]
Vendor: H3C
Product: sr66x1
Service name: system
Platform version: 7.1.064
Product version: Ess 7602P02
Supported board: rse3 fip300 4exp fip600 16exp fip240 sfe1
[Component]
Component: system
Description: system package
cfa0:/ssh-feature.bin
[Package]
Vendor: H3C
Product: sr66x1
Service name: ssh
Platform version: 7.1.064
Product version: Ess 7602P02
Supported board: rse3 fip300 4exp fip600 16exp fip240 sfe1
[Component]
Component: ssh
Description: ssh package
For information about the command output, see Table 1.
Related commands
boot-loader file
display install backup
install commit
display install inactive
Use display install inactive to display inactive software images in the root directories of file systems.
Syntax
In standalone mode:
display install inactive [ slot slot-number ] [ verbose ]
In IRF mode:
display install inactive [ chassis chassis-number slot slot-number ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays information for all cards. (In standalone mode.)
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command displays information for all cards. (In IRF mode.)
verbose: Displays detailed information. If you do not specify this keyword, the command displays only image names.
Examples
# Display brief information about inactive software images in the root directories of the file systems.
<Sysname> display install inactive
Inactive packages on slot 0:
cfa0:/ssh-feature.bin
# Display detailed information about inactive software images in the root directories of the file systems.
<Sysname> display install inactive verbose
Inactive packages on slot 0:
cfa0:/ssh-feature.bin
[Package]
Vendor: H3C
Product: sr66x1
Service name: ssh
Platform version: 7.1.064
Product version: Ess 7602P02
Supported board: rse3 fip300 4exp fip600 16exp fip240 sfe1
[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 an .ipe file in the filesystemname/filename.ipe format. The file must be saved in the root directory of a file system on the device. The value string excluding the file system location section (if any) can have a maximum of 63 characters.
Examples
# Display information about .ipe file cfa0:/test.ipe.
<Sysname> display install ipe-info cfa0:/test.ipe
Verifying the file cfa0:/test.ipe on the device................Done.
H3C SR6604-X images in IPE:
boot.bin
system.bin
Related commands
display install package
display install job
Use display install job to display ongoing ISSU activate or deactivate operations.
Syntax
display install job
Views
Any view
Predefined user roles
network-admin
network-operator
Examples
# (In standalone mode.) Display ongoing ISSU activate or deactivate operations.
<Sysname> display install job
JobID:5
Action:install activate cfa0:/ssh-feature.bin on slot 0
The output shows that the device is executing the install activate cfa0:/ssh-feature.bin slot 0 command.
# (In IRF mode.) Display ongoing ISSU activate or deactivate operations.
JobID:5
Action:install activate cfa0:/ssh-feature.bin on chassis 1 slot 0
The output shows that the device is executing the install activate cfa0:/ssh-feature.bin chassis 1 slot 0 command.
display install log
Use display install log to display ISSU log information.
Syntax
display install log [ log-id ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
log-id: Specifies a log entry by its ID. If you do not specify this argument, the command displays all ISSU log entries.
verbose: Displays detailed ISSU log information. If you do not specify this keyword, the command displays brief ISSU log information.
Usage guidelines
The device creates one log entry for each ISSU operation to track the ISSU process and operation result.
The ISSU log can contain a maximum of 50 entries. The latest entry overwrites the oldest entry if the log is full.
Examples
# Display all ISSU log entries.
<Sysname> display install log
Install job 1 started by user root at 04/28/2016 08:39:29.
Job 1 completed successfully at 04/28/2016 08:39:30.
Install job 1 started by user root at 04/28/2016 08:39:29.
Install activate cfa0:/ssh.bin on slot 0
Job 1 completed successfully at 04/28/2016 08:39:30.
Install job 1 started by user root at 04/28/2016 08:39:29.
Job 1 completed successfully at 04/28/2016 08:39:30.
-----------------------------------------------------------
Install job 2 started by user root at 04/28/2016 08:40:29.
Job 2 completed successfully at 04/28/2016 08:40:30.
Install job 2 started by user root at 04/28/2016 08:40:29.
Install activate cfa0:/route.bin on slot 0
Job 2 completed successfully at 04/28/2016 08:40:30.
Install job 2 started by user root at 04/28/2016 08:40:29.
Job 2 completed successfully at 04/28/2016 08:40:30.
# Displays detailed information about ISSU log entry 1.
<Sysname> display install log 1 verbose
Install job 1 started by user root at 04/28/2016 08:39:29.
Job 1 completed successfully at 04/28/2016 08:39:30.
Install job 1 started by user root at 04/28/2016 08:39:29.
Install activate cfa0:/ssh.bin on slot 0
Job 1 completed successfully at 04/28/2016 08:39:30.
Install job 1 started by user root at 04/28/2016 08:39:29.
Job 1 completed successfully at 04/28/2016 08:39:30.
Detail of activating packages on slot 0.
Get upgrade policy successfully.
Detail of activating packages on slot 0.
Uncompress package to system successfully.
Remove files from system successfully.
Table 2 Command output
|
Field |
Description |
|
Detail of xxx |
Detailed information about an ISSU operation. |
|
Get upgrade policy successfully. |
Obtained the upgrade policy. |
|
Uncompress package to system successfully. |
Decompressed the package successfully. |
|
Remove files from system successfully. |
Deleted files from the system successfully. |
Related commands
reset install log-history oldest
display install package
Use display install package to display software image file information.
Syntax
display install package { filename | all } [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
filename: Specifies a .bin file in the filesystemname/filename.bin format. The file must be saved in the root directory of a file system on the device. The value string excluding the file system location section (if any) can have a maximum of 63 characters.
all: Specifies all software image files in the root directories of the active MPU's file systems. (In standalone mode.)
all: Specifies all software image files in the root directories of the file systems on the global active MPU. (In IRF mode.)
verbose: Displays detailed information. If you do not specify this keyword, the command displays only basic software image information.
Examples
# Display information about system.bin.
<Sysname> display install package cfa0:/system.bin
cfa0:/system.bin
[Package]
Vendor: H3C
Product: sr66x1
Service name: system
Platform version: 7.1.064
Product version: Ess 7602P02
Supported board: rse3 fip300 4exp fip600 16exp fip240 sfe1
# Display detailed information about system.bin.
<Sysname> display install package cfa0:/system.bin verbose
cfa0:/system.bin
[Package]
Vendor: H3C
Product: sr66x1
Service name: system
Platform version: 7.1.064
Product version: Ess 7602P02
Supported board: rse3 fip300 4exp fip600 16exp fip240 sfe1
[Component]
Component: system
Description: system package
For information about the command output, see Table 1.
display install which
Use display install which to display all software image files that include a specific component or file.
Syntax
In standalone mode:
display install which { component name | file filename } [ slot slot-number ]
In IRF mode:
display install which { component name | file filename } [ chassis chassis-number slot slot-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
component name: Specifies a component name.
file filename: Specifies a file in the filename.extension format, a case-insensitive string of up to 63 characters. It cannot contain path information.
slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays information for all cards. (In standalone mode.)
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command displays information for all cards. (In IRF mode.)
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 pkg_ctr.
<Sysname> display install which file pkg_ctr
Verifying the file cfa0:/system-d2601006.bin on slot 0..........................Done.
Found pkg_ctr in cfa0:/system-d2601006.bin on slot 0.
cfa0:/system-d2601006.bin
[Package]
Vendor: H3C
Product: sr66x1
Service name: system
Platform version: 7.1.064
Product version: Ess 7602P02
Verifying the file cfa0:/boot-d2601007.bin on slot 0.....Done.
Table 3 Command output
|
Field |
Description |
|
Verifying the file |
The system was verifying the validity of the file. |
|
[Package] |
Detailed information about the software image. |
|
Service name |
Image type: · boot—Boot image. · system—System image. · patch—Patch image. · Any other value indicates a feature image. |
|
Supported board |
Card types supported by the software image. |
display issu rollback-timer
Use display issu rollback-timer to display automatic rollback timer information.
Syntax
display issu rollback-timer
Views
Any view
Predefined user roles
network-admin
network-operator
Usage guidelines
Change to the automatic rollback interval does not take effect on the ongoing ISSU process. The current remaining rollback time might be greater than the specified automatic rollback interval.
Examples
# Display automatic rollback timer information.
<Sysname> display issu rollback-timer
Rollback timer: Not working
Rollback interval: 0 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 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.064, Ess 7602P01
system: 7.1.064, Ess 7602P01
ssh: 7.1.064, Ess 7602P01
Previous software images:
cfa0:/boot.bin
cfa0:/system.bin
cfa0:/ssh.bin
Upgrade version list:
system: 7.1.064, Ess 7602P02
ssh: 7.1.064, Ess 7602P02
Upgrade software images:
cfa0:/system04.bin
cfa0:/ssh04.bin
Table 4 Command output
|
Field |
Description |
|
ISSU state |
ISSU status: · Init—The ISSU process has not started or has finished. · Loading—The system is executing the issu load command. · Loaded—The issu load command is completed. · Switching—The system is executing the issu run switchover command. · Switchover—The issu run switchover command is completed. · Accepted—The issu accept command is completed. · Committing—The system is executing the issu commit command. · Unknown—An upgrade is in progress. This value might appear when you execute the command on an original standby MPU. |
|
Compatibility |
Version compatibility: · Compatible—Upgrade to a compatible version. · Unknown—No upgrade is in progress. |
|
Work state |
Operating status of the device: Normal—The device is operating correctly. |
|
Upgrade method |
Upgrade mode: Chassis by chassis—Subordinate members are upgraded first, and then the original master. |
|
Upgraded slot |
Upgraded cards. (In standalone mode.) |
|
Current upgrading slot |
Cards that are being upgraded. (In standalone mode.) |
|
Upgraded chassis |
Upgraded members. (In IRF mode.) |
|
Current upgrading chassis |
Members that are being upgraded. (In IRF mode.) |
|
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 run switchover
display version comp-matrix
Use display version comp-matrix to display version compatibility information and identify the recommended upgrade method.
Syntax
display version comp-matrix
display version comp-matrix file { boot filename | system filename | feature filename&<1-30> } *
display version comp-matrix file ipe ipe-filename
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
boot: Specifies a boot image file.
system: Specifies a system image file.
feature: Specifies feature image files. You can specify a space-separated list of up to 30 feature image files.
filename: Specifies a .bin file in the filesystemname/filename.bin format. The file must be saved in the root directory of a file system on the active MPU (in standalone mode) or global active MPU (in IRF mode). This argument cannot contain slot or chassis information and can have a maximum of 63 characters.
ipe ipe-filename: Specifies an .ipe file in the filesystemname/filename.ipe format. The file must be saved in the root directory of a file system on the active MPU (in standalone mode) or global active MPU (in IRF mode). This argument cannot contain slot or chassis information and can have a maximum of 63 characters.
To display compatibility information for the running software images, do not specify any image files for the command. If you specify the upgrade image files, the command displays the following information:
· Compatibility information for upgrade images.
· Recommended ISSU methods for upgrading the running images to the upgrade images.
Examples
# Display compatibility information for the running images.
<Sysname> display version comp-matrix
Boot image: cfa0:/cmw710-boot-a7122.bin
Version:
7.1.064
System image: cfa0:/cmw710-system-a7122.bin
Version:
7.1.064-Ess 7602P02
Version compatibility list:
7.1.064-Ess 7602P02
Version dependency boot list:
7.1.064
Feature image: cfa0:/cmw710-cfa-a7124.bin
Version:
7.1.064-Ess 7602P02
Version compatibility list:
7.1.064-Ess 7602P02
Version dependency system list:
7.1.064-Ess 7602P02
# (In standalone mode.) Display compatibility information for a feature upgrade image as well as the recommended ISSU methods. (In this example, the specified image is compatible with the running images.)
<Sysname> display version comp-matrix file feature cfa0:/cmw710-cfa-a7125.bin
Verifying the file cfa0:/cmw710-cfa-a7125.bin on slot 0.....Done.
Identifying the upgrade methods...Done.
Feature image: cfa0:/cmw710-cfa-a7125.bin
Version:
7.1.064-Ess 7602P02
Version compatibility list:
7.1.064-Ess 7602P02
Version dependency system list:
7.1.064-Ess 7602P02
Slot Upgrade Way
0 File Upgrade
Influenced service according to following table on slot 0:
flash:/cmw710-cfa-a7125.bin
CFA
# (In IRF mode.) Display compatibility information for a feature upgrade image as well as the recommended ISSU methods. (In this example, the specified image is compatible with the running images.)
<Sysname> display version comp-matrix file feature cfa0:/cmw710-cfa-a7122.bin
Verifying the file cfa0:/cmw710-cfa-a7122.bin on chassis 1 slot 0.....Done.
Feature image: cfa0:/cmw710-cfa-a7122.bin
Version:
7.1.064-Ess 7602P02
Version compatibility list:
7.1.064-Ess 7602P02
Version dependency system list:
7.1.064-Ess 7602P02
Chassis Slot Upgrade Way
1 0 File Upgrade
2 0 File Upgrade
Influenced service according to following table on chassis 1 slot 0:
flash:/cmw710-cfa-a7122.bin
CFA
Influenced service according to following table on chassis 2 slot 0:
flash:/cmw710-cfa-a7122.bin
CFA
|
Field |
Description |
|
Verifying the file |
The system was verifying the validity of the file. |
|
Version compatibility list |
· Under a system image, this field shows all system image versions that are compatible with the system image. · Under a feature image, this field shows all feature image versions that are compatible with the feature image. |
|
Version dependency boot list |
Boot image versions that support the system image. To install the system image, you must install one of the boot image versions that are in the list. |
|
Version dependency system list |
System image versions that support the feature image. To install the feature image, you must install one of the system image versions that is in the list. |
|
Influenced service according to following table |
Services that will be affected by the upgrade. |
|
Upgrade Way |
ISSU method to be used for a compatible version: · Service Upgrade. · File Upgrade. · Reboot. · Sequence Reboot. This method is available only for switching fabric modules. For more information about ISSU methods, see Fundamentals Configuration Guide. |
Related commands
issu load
install abort
Use install abort to abort an ongoing ISSU operation.
Syntax
install abort [ job-id ]
Views
User view
Predefined user roles
network-admin
Parameters
job-id: Specifies the job ID of an ISSU operation. If you do not specify this argument, the command aborts all ongoing software image activate and deactivate operations.
Usage guidelines
The system creates a software image management job each time you use the install activate, install add, install commit, install deactivate, or install remove command. Each job represents one command and is assigned a unique job ID. You can abort only ongoing activate and deactivate operations.
When you abort an ongoing activate or deactivate operation, the system rolls back to the status it was in before the operation was started.
To obtain the ID of a job, use the display install job command.
Examples
# Abort all ongoing ISSU operations.
<Sysname> install abort
Related commands
display install job
install activate
Use install activate to activate software images, or identify the ISSU method and the possible impact on the device.
Syntax
In standalone mode:
install activate { boot filename | system filename | feature filename&<1-30> } * slot slot-number [ test ]
install activate patch filename { all | slot slot-number }
In IRF mode:
install activate { boot filename | system filename | feature filename&<1-30> } * chassis chassis-number slot slot-number [ test ]
install activate patch filename { all | chassis chassis-number slot slot-number }
Views
User view
Predefined user roles
network-admin
Parameters
boot: Specifies a boot image file. This keyword is not supported in the current software version.
system: Specifies a system image file. This keyword is not supported in the current software version.
feature: Specifies feature image files. You can specify a space-separated list of up to 30 feature image files.
patch: Specifies a patch image file.
filename: Specifies a .bin file in the filesystemname/filename.bin format. A boot, system, or feature image file must be saved in the root directory of a file system on the device. A patch image file must be saved in the root directory of a file system on the active MPU (in standalone mode) or global active MPU (in IRF mode). The value string excluding the file system location section (if any) can have a maximum of 63 characters.
all: Specifies all cards.
slot slot-number: Specifies a card by its slot number. (In standalone mode.)
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. (In IRF mode.)
test: Only identifies the ISSU method to be used for the upgrade. If you
do not specify this keyword, the command activates the specified software images.
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.
Read the software release notes to identify the licensing requirements for the upgrade software image file. If the upgrade software image file requires a license but the license is not installed or valid, install the license first.
In standalone mode, follow these guidelines:
· If you specify the active MPU, the command takes effect on the active MPU and all LPUs.
· If you specify the standby MPU, the command takes effect only on the standby MPU.
· If the specified files are not saved on the MPU to be upgraded, the command copies the images to the MPU automatically.
In IRF mode, follow these guidelines:
· If you specify the global active MPU, the command takes effect on the global active MPU and all LPUs.
· If you specify a global standby MPU, the command takes effect on the global standby MPU.
· If the specified files are not saved on the MPU to be upgraded, the command copies the images to the MPU automatically.
· At reboot, a subordinate device automatically synchronizes the master device's configuration and status data. You must wait for the synchronization to complete before using the install activate command on the subordinate device. To identify whether the synchronization is complete, use the display system stable state command. The synchronization is complete if the System State field displays Stable.
Examples
# (In standalone mode.) Identify the ISSU method for feature upgrade with ssh2.bin on the standby MPU (in slot 1) and the upgrade impact.
<Sysname> install activate feature cfa0:/ssh2.bin slot 1 test
Copying file cfa0:/ssh2.bin to slot1#cfa0:/ssh2.bin......Done.
Verifying the file cfa0:/ssh2.bin on slot 1.....Done.
Identifying the upgrade methods...Done.
Upgrade summary according to following table:
cfa0:/ssh2.bin
Running Version New Version
None Ess 7602P02
Slot Upgrade Way
1 Service Upgrade
Influenced service according to following table on slot 1:
cfa0:/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.
# (In IRF mode.) Identify the ISSU method for feature upgrade with ssh2.bin on the global standby MPU in slot 1 of IRF member 1 and the upgrade impact.
<Sysname> install activate feature cfa0:/ssh2.bin chassis 1 slot 1 test
Copying file cfa0:/ssh2.bin to chassis1#slot1#cfa0:/ssh2.bin......Done.
Verifying the file cfa0:/ssh2.bin on chassis 1 slot 1.....Done.
Identifying the upgrade methods...Done.
Upgrade summary according to following table:
cfa0:/ssh2.bin
Running Version New Version
None Ess 7602P02
Chassis Slot Upgrade Way
1 1 Service Upgrade
Influenced service according to following table on chassis 1 slot 1:
cfa0:/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.
# (In standalone mode.) Activate the feature images in feature.bin on the standby MPU (in slot 1).
<Sysname> install activate feature cfa0:/feature.bin slot 1
Copying file cfa0:/feature.bin to slot1#cfa0:/feature.bin......Done.
Verifying the file cfa0:/feature.bin on slot 1.....Done.
Identifying the upgrade methods...Done.
Upgrade summary according to following table:
cfa0:/feature.bin
Running Version New Version
None Ess 7602P02
Slot Upgrade Way
1 Service Upgrade
Upgrading software images to compatible versions. Continue? [Y/N]:y
This operation might take several minutes, please wait.......................................................................Done.
# (In IRF mode.) Activate the feature images in feature.bin on the global standby MPU in slot 1 of IRF member 1.
<Sysname> install activate feature cfa0:/feature.bin chassis 1 slot 1
Copying file cfa0:/feature.bin to chassis1#slot1#cfa0:/feature.bin......Done.
Verifying the file cfa0:/feature.bin on chassis 1 slot 1.....Done.
Identifying the upgrade methods...Done.
Upgrade summary according to following table:
cfa0:/route-feature.bin
Running Version New Version
None Ess 7602P02
Chassis Slot Upgrade Way
1 1 Service Upgrade
Upgrading software images to compatible versions. Continue? [Y/N]:y
This operation might take several minutes, please wait.......................................................................Done.
Table 6 Command output
|
Field |
Description |
|
Verifying the file |
The system was verifying the validity of the file. |
|
Upgrade summary according to following table |
Upgrade summary. |
|
Running Version |
Version number of the running software. |
|
New Version |
Version number of the new software. |
|
Upgrade Way |
ISSU methods: · Service Upgrade. · File Upgrade. · Reboot. · Sequence Reboot—This method applies only when the device has switching fabric modules that support this upgrade method. This field is displayed only for an upgrade to a compatible version. For more information about ISSU methods, see Fundamentals Configuration Guide. |
|
Influenced service according to following table |
Services influenced by the upgrade. |
Related commands
display install active
install commit
install deactivate
install add
Use install add to decompress an .ipe file.
Syntax
install add ipe-filename filesystem
Views
User view
Predefined user roles
network-admin
Parameters
ipe-filename: Specifies an .ipe file in the filesystemname/filename.ipe format. The file must be saved in the root directory of a file system on the device. The value string excluding the file system location section (if any) can have a maximum of 63 characters.
filesystem: Specifies the destination file system for the software images in the filesystemname format.
Usage guidelines
To use install commands for upgrade, you must use .bin image files. If the upgrade file is an .ipe file, use this command to decompress the .ipe file before you start the upgrade.
To identify software images that are included in an .ipe file, use the display install ipe-info command.
Examples
# Decompress all.ipe to the CF card.
<Sysname> install add cfa0:/all.ipe cfa0:
Verifying the file cfa0:/all.ipe on chassis 1 slot 0...Done.
Decompressing file boot.bin to cfa0:/boot.bin.......................Done.
Decompressing file system.bin to cfa0:/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
Read the software release notes to identify the licensing requirements for the upgrade software image file. If the upgrade software image file requires a license but the license is not installed or valid, install the license first.
This command modifies the main startup software image list to be the same as the current software image list.
You must execute this command after using the following commands:
· The install activate command in an incremental upgrade.
· The install deactivate command.
In a reboot upgrade, the install activate command modifies both the current and startup software image lists. You do not need to commit software changes.
Both the install commit and boot-loader file commands modify the main startup software image list. To modify the backup startup image list or add inactive images as main startup images, however, you must use the boot-loader file command.
For more information about main and backup startup software images, see Fundamental Configuration Guide.
Examples
# Commit software changes.
<Sysname> install commit
This operation will take several minutes, please wait...........................Done.
Related commands
install activate
install deactivate
install deactivate
Use install deactivate to deactivate feature images and patch images.
Syntax
In standalone mode:
install deactivate feature filename&<1-30> slot slot-number
install deactivate patch filename { all | slot slot-number }
In IRF mode:
install deactivate feature filename&<1-30> chassis chassis-number slot slot-number
install deactivate patch filename { all | chassis chassis-number slot slot-number }
Views
User view
Predefined user roles
network-admin
Parameters
feature: Specifies feature image files. You can specify a space-separated list of up to 30 feature image files.
patch: Specifies a patch image file.
filename: Specifies a .bin file in the filesystemname/filename.bin format. The file must be saved in the root directory of a file system on the specified slot. This argument cannot contain slot or chassis information and can have a maximum of 63 characters.
all: Specifies all cards on which the specified patch image file has been activated.
slot slot-number: Specifies a card by its slot number. (In standalone mode.)
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. (In IRF mode.)
Usage guidelines
You can deactivate only active feature and patch images.
To prevent deactivated images from running after a reboot, you must commit the software changes by using the install commit command.
At reboot, a subordinate device automatically synchronizes the master device's configuration and status data. You must wait for the synchronization to complete before using the install deactivate command on the subordinate device. To identify whether the synchronization is complete, use the display system stable state command. The synchronization is complete if the System State field displays Stable.
Examples
# (In standalone mode.) Deactivate the patch images in patch.bin on slot 0.
<Sysname> install deactivate patch cfa0:/patch.bin slot 0
This operation might take several minutes, please wait...Done.
# (In IRF mode.) Deactivate the feature images in feature.bin on slot 0 of IRF member 1.
<Sysname> install deactivate feature cfa0:/feature.bin chassis 1 slot 0
This operation might take several minutes, please wait...Done.
Related commands
display install active
display install inactive
install remove
Use install remove to delete an inactive software image file.
Syntax
In standalone mode:
install remove [ slot slot-number ] { filename | inactive }
In IRF mode:
install remove [ chassis chassis-number slot slot-number ] { filename | inactive }
Views
User view
Predefined user roles
network-admin
Parameters
slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command deletes inactive software images from all cards. (In standalone mode.)
chassis chassis-number slot slot-number: Specifies a card on an IRF member device. The chassis-number argument represents the member ID of the IRF member device. The slot-number argument represents the slot number of the card. If you do not specify a card, this command deletes inactive software images from all cards. (In IRF mode.)
filename: Specifies a .bin file in the filesystemname/filename.bin format. The file must be saved in the root directory of a file system. This argument can have a maximum of 63 characters.
inactive: Deletes all inactive software image files in the root directories of the specified file systems.
Usage guidelines
You can use this command only to delete inactive software image files that are saved in root directories of file systems.
This command permanently deletes the image file from the device. You cannot use the install abort command to abort the operation.
Examples
# Delete the inactive software image file cfa0:/ssh-feature.bin.
<Sysname> install remove cfa0:/ssh-feature.bin
install verify
Use install verify to verify the software change commit status, image integrity, and image consistency.
Syntax
install verify
Views
User view
Predefined user roles
network-admin
Usage guidelines
To ensure a successful ISSU and make sure the system can start up and operate correctly after an ISSU, execute this command to verify the following items:
· Integrity—Verify that the boot, system, and feature images are integral.
· Consistency—Verify that the same active images are running across the entire system.
· Software commit status—Verify that the active images are committed as needed.
If a software image fails the verification, perform the following tasks to resolve the problem:
· To ensure software integrity, download and install the software images again.
· To guarantee software image consistency or change software commit status, use the install activate, install deactivate, and install commit commands as appropriate.
Examples
# (In standalone mode.) Verify the software change confirmation status and software image integrity and consistency.
<Sysname> install verify
Active packages on slot 0 are the reference packages.
Packages will be compared with the reference packages.
This operation will take several minutes, please wait...
Verifying packages on slot 0:
Start to check active package completeness.
Verifying the file cfa0:/boot-a0101.bin on slot 0.....................Done.
cfa0:/boot-a0101.bin verification successful.
Verifying the file cfa0:/system-a0101.bin on slot 0.....................Done.
cfa0:/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.
Active packages on chassis 1 slot 0 are the reference packages.
Packages will be compared with the reference packages.
This operation will take several minutes, please wait...
Verifying packages on chassis 1 slot 0:
Start to check active package completeness.
Verifying the file cfa0:/boot-a0101.bin on chassis 1 slot 0.....................Done.
cfa0:/boot-a0101.bin verification successful.
Verifying the file cfa0:/system-a0101.bin on chassis 1 slot 0.....................Done.
cfa0:/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.
Syntax
issu accept
Views
User view
Predefined user roles
network-admin
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 the original master to a compatible version and complete the ISSU upgrade.
Syntax
issu commit chassis chassis-number
Views
User view
Predefined user roles
network-admin
Parameters
chassis chassis-number: Specifies the member ID of the original master.
Usage guidelines
At reboot, a subordinate device automatically synchronizes the master device's configuration and status data. You must wait for the synchronization to complete before using the issu commit command on the subordinate device. To identify whether the synchronization is complete, use the display system stable state command. The synchronization is complete if the System State field displays Stable.
Examples
# On a multichassis IRF fabric, upgrade the original master during an ISSU to a compatible version.
<Sysname> issu commit chassis 1
Copying file cfa0:/feature.bin to chassis1#slot0#cfa0:/feature.bin...Done.
Verifying the file cfa0:/feature.bin on chassis 1 slot 0..............Done.
Upgrade summary according to following table:
cfa0:/feature.bin
Running Version New Version
None Ess 7602P02
Chassis Slot Upgrade Way
1 0 Service Upgrade
Upgrading software images to compatible versions. Continue? [Y/N]:y
This operation might take several minutes, please wait...Done.
For information about the command output, see Table 5.
Related commands
issu accept
issu load
issu run switchover
issu load
Use issu load to upgrade subordinate members and configure the new images as main startup software images for those members.
Syntax
issu load file { boot filename | system filename | feature filename&<1-30> } * chassis chassis-number&<1-3>
issu load file ipe ipe-filename chassis chassis-number&<1-3>
Views
User view
Predefined user roles
network-admin
Parameters
boot: Specifies a boot image file.
system: Specifies a system image file.
feature: Specifies feature image files. You can specify a space-separated list of up to 30 feature image files.
filename: Specifies a .bin file in the filesystemname/filename.bin format. The file must be saved in the root directory of a file system on the global active MPU.
ipe ipe-filename: Specifies an .ipe file in the filesystemname/filename.ipe format. The file must be saved in the root directory of a file system on the global active MPU.
chassis chassis-number: Specifies the member ID of a subordinate member. For a compatible upgrade, you can specify only one member ID.
Usage guidelines
You may upgrade all or some of the software images. If you are upgrading only some of the images, make sure the new images are compatible with the images that are not to be upgraded. The upgrade will fail if a conflict exists.
This command performs the following operations:
· Checks the version compatibility.
· Identifies the upgrade method.
· Loads the new images for the upgrade.
· Configures the images as main startup software images so the upgrade can survive a reboot.
At reboot, a subordinate device automatically synchronizes the master device's configuration and status data. You must wait for the synchronization to complete before using the issu load command on the subordinate device. To identify whether the synchronization is complete, use the display system stable state command. The synchronization is complete if the System State field displays Stable.
Examples
# Upgrade member device 2 (a subordinate member) with 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
Verifying the file cfa0:/feature.bin on chassis 1 slot 0...Done.
Copying file cfa0:/feature.bin to chassis2#slot0#cfa0:/feature.bin...Done.
Verifying the file cfa0:/feature.bin on chassis 2 slot 0...Done.
Upgrade summary according to following table:
cfa0:/feature.bin
Running Version New Version
None Ess 7602P02
Chassis Slot Upgrade Way
2 0 Service Upgrade
Upgrading software images to compatible versions. Continue? [Y/N]:y
This operation might take several minutes, please wait...Done.
Table 7 Command output
|
Field |
Description |
|
Verifying the file |
The system was verifying the validity of the file. |
|
Upgrade Way |
ISSU method: · Service Upgrade. · File Upgrade. · Reboot. · Sequence Reboot—This method is only available for switching fabric modules. For more information about ISSU methods, see Fundamentals Configuration Guide. |
issu rollback-timer
Use issu rollback-timer to set the automatic rollback timer.
Use undo issu rollback-timer to restore the default.
Syntax
issu rollback-timer minutes
undo issu rollback-timer
Default
The automatic rollback timer is set to 45 minutes.
Views
System view
Predefined user roles
network-admin
Parameters
minutes: Specifies the automatic rollback interval, in the range of 0 to 120 minutes. Setting it to 0 disables automatic rollback.
Usage guidelines
Automatic rollback is complicated. As a best practice, disable automatic rollback.
Change to the automatic rollback interval does not take effect on the ongoing ISSU process.
Examples
# Set the automatic rollback timer to 0 minutes.
<Sysname> system-view
[Sysname] issu rollback-timer 0
issu run switchover
Use issu run switchover to perform an ISSU switchover.
Syntax
issu run switchover
Views
User view
Predefined user roles
network-admin
Usage guidelines
This command performs operations depending on the ISSU method.
· Incremental upgrade—Performs a process-level master/subordinate switchover for the processes to be upgraded.
· Reboot upgrade—Reboots the current master with the old software version to cause the upgraded subordinate member to become the new master.
During a reboot upgrade, the LPUs and switching fabric modules reboot to load the new software from the upgraded MPU. A transient service outage occurs on the cards.
At reboot, a subordinate device automatically synchronizes the master device's configuration and status data. You must wait for the synchronization to complete before using the issu run switchover command on the subordinate device. To identify whether the synchronization is complete, use the display system stable state command. The synchronization is complete if the System State field displays Stable.
Examples
# Perform a switchover during an ISSU.
<Sysname> issu run switchover
Upgrade summary according to following table:
cfa0:/feature.bin
Running Version New Version
None Ess 7602P02
Chassis Slot Switchover Way
1 0 Active standby process switchover
Upgrading software images to compatible versions. Continue? [Y/N]:y
This operation might take several minutes, please wait...Done.
Table 8 Command output
|
Field |
Description |
|
Verifying the file |
The system was verifying the validity of the file. |
|
Switchover Way |
Switchover method: · Active standby process switchover—Switch from the active process to the standby process. · Global active standby MPU switchover—Switch from the global active MPU to a global standby MPU. |
For more information about the command output, see Table 5.
Related commands
issu load
reset install log-history oldest
Use reset install log-history oldest to clear ISSU log entries.
Syntax
reset install log-history oldest log-number
Views
User view
Predefined user roles
network-admin
Parameters
log-number: Specifies the number of ISSU log entries to be deleted.
Usage guidelines
This command clears the specified number of log entries, beginning with the oldest log entry.
Examples
# Clear the two oldest ISSU log entries.
<Sysname> reset install log-history oldest 2
Related commands
display install log
