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-Device management commands
- 11-Tcl commands
- 12-Python commands
- 13-License management commands
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 08-ISSU commands | 143.48 KB |
ISSU commands
display install active
Use display install active to display active software images.
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 1:
flash:/boot.bin
flash:/system.bin
flash:/feature1.bin
# (In IRF mode.) Display active software images.
<Sysname> display install active
Active packages on chassis 1 slot 1:
flash:/boot.bin
flash:/system.bin
flash:/patch1.bin
# (In standalone mode.) Display detailed information about active software images.
<Sysname> display install active verbose
Active packages on slot 1:
flash:/boot.bin
[Package]
Vendor: H3C
Product: S7500E
Service name: boot
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu
[Component]
Component: boot
Description: boot package
flash:/system.bin
[Package]
Vendor: H3C
Product: S7500E
Service name: system
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu
[Component]
Component: system
Description: system package
flash:/feature1.bin
[Package]
Vendor: H3C
Product: S7500E
Service name: test
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu
[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 1:
flash:/boot.bin
[Package]
Vendor: H3C
Product: S7500E
Service name: boot
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu lpu
[Component]
Component: boot
Description: boot package
flash:/system.bin
[Package]
Vendor: H3C
Product: S7500E
Service name: system
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu lpu
[Component]
Component: system
Description: system package
flash:/patch1.bin
[Package]
Vendor: H3C
Product: S7500E
Service name: test
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu lpu
[Component]
Component: test
Description: test package
|
Field |
Description |
|
[Package] |
Detailed information about the software image. |
|
Service name |
Image type: · boot—Boot image. · system—System image. · boot patch—Patch image for the boot image. · system patch—Patch image for the system image. · Any other value indicates a feature image. |
|
Supported board |
Hardware types supported by the software image: · mpu—MPU. · lpu—Service card. |
|
[Component] |
Information about components included in the image file. |
Related commands
install active
display install backup
Use display install backup to display backup startup software images.
Syntax
In standalone mode:
display install backup [ slot slot-number ] [ verbose ]
In IRF mode:
display install backup [ chassis chassis-number slot slot-number ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
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 Fundamentals Configuration Guide.
To modify the backup startup image list, 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 1:
flash:/boot.bin
flash:/system.bin
# (In IRF mode.) Display the backup startup software images.
<Sysname> display install backup
Backup startup software images on chassis 1 slot 1:
flash:/boot.bin
flash:/system.bin
# (In standalone mode.) Display detailed information about backup startup software images.
<Sysname> display install backup verbose
Backup startup software images on slot 1:
flash:/boot.bin
[Package]
Vendor: H3C
Product: S7500E
Service name: boot
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu
[Component]
Component: boot
Description: boot package
flash:/system.bin
[Package]
Vendor: H3C
Product: S7500E
Service name: system
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu
[Component]
Component: system
Description: system package
# (In IRF mode.) Display detailed information about backup startup software images.
<Sysname> display install backup verbose
Backup startup software images on chassis 1 slot 1:
flash:/boot.bin
[Package]
Vendor: H3C
Product: S7500E
Service name: boot
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu lpu
[Component]
Component: boot
Description: boot package
flash:/system.bin
[Package]
Vendor: H3C
Product: S7500E
Service name: system
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu lpu
[Component]
Component: system
Description: system package
Backup startup software images on chassis 2 slot 1:
flash:/boot.bin
[Package]
Vendor: H3C
Product: S7500E
Service name: boot
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu lpu
[Component]
Component: boot
Description: boot package
flash:/system.bin
[Package]
Vendor: H3C
Product: S7500E
Service name: system
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu lpu
[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 modify the current software image list but do not modify the main startup image list. For the software image changes to take effect after a reboot, you must execute the install commit command to update the main startup image list with the image changes. You can use the display install committed command to verify the operation results.
Both the install commit and boot-loader file commands modify the main startup software image list.
Examples
# (In standalone mode.) Display the main startup software images.
<Sysname> display install committed
Committed packages on slot 1:
flash:/boot.bin
flash:/system.bin
flash:/feature1.bin
# (In IRF mode.) Display the main startup software images.
<Sysname> display install committed
Committed packages on chassis 1 slot 1:
flash:/boot.bin
flash:/system.bin
flash:/patch1.bin
# (In standalone mode.) Display detailed information about main startup software images.
<Sysname> display install committed verbose
Committed packages on slot 1:
flash:/boot.bin
[Package]
Vendor: H3C
Product: S7500E
Service name: boot
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu
[Component]
Component: boot
Description: boot package
flash:/system.bin
[Package]
Vendor: H3C
Product: S7500E
Service name: system
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu
[Component]
Component: system
Description: system package
flash:/feature1.bin
[Package]
Vendor: H3C
Product: S7500E
Service name: feature1
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu
[Component]
Component: feature1
Description: feature1 package
# (In IRF mode.) Display detailed information about main startup software images.
<Sysname> display install committed verbose
Committed packages on chassis 1 slot 1:
flash:/boot.bin
[Package]
Vendor: H3C
Product: S7500E
Service name: boot
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu lpu
[Component]
Component: boot
Description: boot package
flash:/system.bin
[Package]
Vendor: H3C
Product: S7500E
Service name: system
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu lpu
[Component]
Component: system
Description: system package
flash:/patch1.bin
[Package]
Vendor: H3C
Product: S7500E
Service name: patch1
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu lpu
[Component]
Component: patch1
Description: patch1 package
Committed packages on chassis 2 slot 1:
flash:/boot.bin
[Package]
Vendor: H3C
Product: S7500E
Service name: boot
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu lpu
[Component]
Component: boot
Description: boot package
flash:/system.bin
[Package]
Vendor: H3C
Product: S7500E
Service name: system
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu lpu
[Component]
Component: system
Description: system package
flash:/patch1.bin
[Package]
Vendor: H3C
Product: S7500E
Service name: patch1
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu lpu
[Component]
Component: patch1
Description: patch1 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
# (In standalone mode.) Display brief information about inactive software images in the root directories of the file systems.
<Sysname> display install inactive
Inactive packages on slot 1:
flash:/feature1.bin
# (In IRF mode.) Display brief information about inactive software images in the root directories of the file systems.
<Sysname> display install inactive
Inactive packages on chassis 1 slot 1:
flash:/patch1.bin
Inactive packages on chassis 2 slot 1:
flash:/patch1.bin
# (In standalone mode.) Display detailed information about inactive software images in the root directories of the file systems.
<Sysname> display install inactive verbose
Inactive packages on slot 1:
flash:/feature1.bin
[Package]
Vendor: H3C
Product: S7500E
Service name: feature1
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu
[Component]
Component: feature1
Description: feature1 package
# (In IRF mode.) Display detailed information about inactive software images in the root directories of the file systems.
<Sysname> display install inactive verbose
Inactive packages on chassis 1 slot 1:
flash:/patch1.bin
[Package]
Vendor: H3C
Product: S7500E
Service name: patch1
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu lpu
[Component]
Component: patch1
Description: patch1 package
Inactive packages on chassis 2 slot 1:
flash:/patch1.bin
[Package]
Vendor: H3C
Product: S7500E
Service name: patch1
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu lpu
[Component]
Component: patch1
Description: patch1 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 stored in the root directory of a file system on the device. The value string excluding the file system location section (if any) can have a maximum of 63 characters. For more information about specifying a file, see file system management in Fundamentals Configuration Guide.
Examples
# (In standalone mode.) Display information about .ipe file flash:/test.ipe.
<Sysname> display install ipe-info flash:/test.ipe
Verifying the file flash:/test.ipe on slot 1................Done.
H3C S7500E images in IPE:
boot.bin
system.bin
# (In IRF mode.) Display information about .ipe file flash:/test.ipe.
<Sysname> display install ipe-info flash:/test.ipe
Verifying the file flash:/test.ipe on chassis 1 slot 1................Done.
H3C S7500E images in IPE:
boot.bin
system.bin
Related commands
display install package
display install job
Use display install job to display ongoing ISSU activate and deactivate operations.
Syntax
display install job
Views
Any view
Predefined user roles
network-admin
network-operator
Examples
# (In standalone mode.) Display ongoing ISSU activate and deactivate operations.
<Sysname> display install job
JobID:5
Action:install activate flash:/feature1.bin on slot 1
The output shows that the device is executing the install activate flash:/feature1.bin slot 1 command.
# (In IRF mode.) Display ongoing ISSU activate and deactivate operations.
JobID:5
Action:install activate flash:/patch1.bin on chassis 1 slot 1
The output shows that the device is executing the install activate flash:/patch1.bin chassis 1 slot 1 command.
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
# (In standalone mode.) Display all ISSU log entries.
<Sysname> display install log
Install job 1 started by user root at 04/28/2001 08:39:29.
Job 1 completed successfully at 04/28/2001 08:39:30.
Install job 1 started by user root at 04/28/2001 08:39:29.
Install activate flash:/feature1.bin on slot 1
Job 1 completed successfully at 04/28/2001 08:39:30.
Install job 1 started by user root at 04/28/2001 08:39:29.
Job 1 completed successfully at 04/28/2001 08:39:30.
-----------------------------------------------------------
Install job 2 started by user root at 04/28/2001 08:40:29.
Job 2 completed successfully at 04/28/2001 08:40:30.
Install job 2 started by user root at 04/28/2001 08:40:29.
Install activate flash:/route.bin on slot 1
Job 2 completed successfully at 04/28/2001 08:40:30.
Install job 2 started by user root at 04/28/2001 08:40:29.
Job 2 completed successfully at 04/28/2001 08:40:30.
# (In IRF mode.) Displays detailed information about all ISSU log entries.
<Sysname> display install log
Install job 1 started by user root at 04/28/2001 08:39:29.
Job 1 completed successfully at 04/28/2001 08:39:30.
Install job 1 started by user root at 04/28/2001 08:39:29.
Install activate flash:/patch1.bin on chassis 1 slot 1
Job 1 completed successfully at 04/28/2001 08:39:30.
Install job 1 started by user root at 04/28/2001 08:39:29.
Job 1 completed successfully at 04/28/2001 08:39:30.
-----------------------------------------------------------
Install job 2 started by user root at 04/28/2001 08:40:29.
Job 2 completed successfully at 04/28/2001 08:40:30.
Install job 2 started by user root at 04/28/2001 08:40:29.
Install activate flash:/route.bin on chassis 1 slot 1
Job 2 completed successfully at 04/28/2001 08:40:30.
Install job 2 started by user root at 04/28/2001 08:40:29.
Job 2 completed successfully at 04/28/2001 08:40:30.
# (In standalone mode.) Displays detailed information about ISSU log entry 1.
<Sysname> display install log 1 verbose
Install job 1 started by user root at 04/28/2001 08:39:29.
Job 1 completed successfully at 04/28/2001 08:39:30.
Install job 1 started by user root at 04/28/2001 08:39:29.
Install activate flash:/feature1.bin on slot 1
Job 1 completed successfully at 04/28/2001 08:39:30.
Install job 1 started by user root at 04/28/2001 08:39:29.
Job 1 completed successfully at 04/28/2001 08:39:30.
Detail of activating packages on slot 1.
Get upgrade policy successfully.
Detail of activating packages on slot 1.
Uncompress package to system successfully.
Remove files from system successfully.
# (In IRF mode.) Displays detailed information about ISSU log entry 1.
<Sysname> display install log 1 verbose
Install job 1 started by user root at 04/28/2001 08:39:29.
Job 1 completed successfully at 04/28/2001 08:39:30.
Install job 1 started by user root at 04/28/2001 08:39:29.
Install activate flash:/patch1.bin on chassis 1 slot 1
Job 1 completed successfully at 04/28/2001 08:39:30.
Install job 1 started by user root at 04/28/2001 08:39:29.
Job 1 completed successfully at 04/28/2001 08:39:30.
Detail of activating packages on chassis 1 slot 1.
Get upgrade policy successfully.
Detail of activating packages on chassis 1 slot 1.
Uncompress package to system successfully.
Remove files from system successfully.
Table 2 Command output
|
Field |
Description |
|
Detail of xxx |
Detailed information about an ISSU operation. |
|
Get upgrade policy successfully. |
Obtained the upgrade policy. |
|
Uncompress package to system successfully. |
Decompressed the package successfully. |
|
Remove files from system successfully. |
Deleted files from the system successfully. |
Related commands
reset install log-history oldest
display install package
Use display install package to display software image file information.
Syntax
display install package { filename | all } [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
filename: Specifies a .bin file in the filesystemname/filename.bin format. The file must be stored in the root directory of a file system on the device. The value string excluding the file system location section (if any) can have a maximum of 63 characters. For more information about specifying a file, see file system management in Fundamentals Configuration Guide.
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 flash:/system.bin
flash:/system.bin
[Package]
Vendor: H3C
Product: S7500E
Service name: system
Platform version: 7.1.070
Product version: Release 752102
Supported board: mpu
# Display detailed information about system.bin.
<Sysname> display install package flash:/system.bin verbose
flash:/system.bin
[Package]
Vendor: H3C
Product: S7500E
Service name: system
Platform version: 7.1.070
Product version: Release 752102
Supported board: mpu
[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 image files that include the component or file. Then, you can use the install verify command to identify image file problems.
This command searches only the root directories of the file systems at the specified location.
Examples
# (In standalone mode.) Display the software image file that includes pkg_ctr.
<Sysname> display install which file pkg_ctr
Verifying the file flash:/system-t0001015.bin on slot 1..........................Done.
Found pkg_ctr in flash:/system-t0001015.bin on slot 1.
flash:/system-t0001015.bin
[Package]
Vendor: H3C
Product: S7500E
Service name: system
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu
Verifying the file flash:/boot-d2601007.bin on slot 1.....Done.
# (In IRF mode.) Display the software image file that includes pkg_ctr.
<Sysname> display install which file pkg_ctr
Verifying the file flash:/system-t0001015.bin on chassis 1 slot 1...........Done.
Found pkg_ctr in flash:/system-t0001015.bin on chassis 1 slot 1.
flash:/system-t0001015.bin
[Package]
Vendor: H3C
Product: S7500E
Service name: system
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu lpu
Verifying the file flash:/boot-d2601007.bin on slot 1.....Done.
Table 3 Command output
|
Field |
Description |
|
Verifying the file |
The system was verifying the validity of the file. |
|
[Package] |
Detailed information about the software image. |
|
Service name |
Image type: · boot—Boot image. · system—System image. · patch—Patch image. · Any other value indicates a feature image. |
|
Supported board |
Hardware types supported by the software image: · mpu—MPU. · lpu—Service card. |
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
# (In standalone mode.) Display ISSU status information when no upgrade is taking place.
<Sysname> display issu state
ISSU state: Init
Compatibility: Unknown
Work state: Normal
Upgrade method: Card by card
Upgraded slot: None
Current upgrading slot: None
Current version list:
boot: 7.1.070, Test 0001015
system: 7.1.070, Test 0001015
feature1: 7.1.070, Test 0001015
Current software images:
flash:/boot-t0001015.bin
flash:/system-t0001015.bin
flash:/feature1-t0001015.bin
# (In standalone mode.) Display ISSU status information while the issu load command is being executed.
<Sysname> display issu state
ISSU state: Loading
Compatibility: Incompatible
Work state: Normal
Upgrade method: Card by card
Upgraded slot: None
Current upgrading slot:
slot 1
Previous version list:
boot: 7.1.070, Test 0001015
system: 7.1.070, Test 0001015
feature1: 7.1.070, Test 0001015
Previous software images:
flash:/boot-t0001015.bin
flash:/system-t0001015.bin
flash:/feature1-t0001015.bin
Upgrade version list:
boot: 7.1.070, Test 0001016
system: 7.1.070, Test 0001016
feature1: 7.1.070, Test 0001016
Upgrade software images:
flash:/boot-t0001016.bin
flash:/system-t0001016.bin
flash:/feature1-t0001016.bin
# (In IRF mode.) On a single-chassis IRF fabric, display ISSU status information when no upgrade is taking place.
<Sysname> display issu state
ISSU state: Init
Compatibility: Unknown
Work state: Normal
Upgrade method: Card by card
Upgraded slot: None
Current upgrading slot: None
Current version list:
boot: 7.1.070, Test 0001015
system: 7.1.070, Test 0001015
feature1: 7.1.070, Test 0001015
Current software images:
flash:/boot-t0001015.bin
flash:/system-t0001015.bin
flash:/feature1-t0001015.bin
# (In IRF mode.) On a single-chassis IRF fabric, display ISSU status information on the global active MPU after the issu load command is completed.
<Sysname> display issu state
ISSU state: Loaded
Compatibility: Compatible
Work state: Normal
Upgrade method: Card by card
Upgraded slot:
chassis 1 slot 1
Current upgrading slot: None
Previous version list:
boot: 7.1.070, Test 0001015
system: 7.1.070, Test 0001015
feature1: 7.1.070, Test 0001015
Previous software images:
flash:/boot-t0001015.bin
flash:/system-t0001015.bin
flash:/feature1-t0001015.bin
Upgrade version list:
boot: 7.1.070, Test 0001016
system: 7.1.070, Test 0001016
feature1: 7.1.070, Test 0001016
Upgrade software images:
flash:/boot-t0001016.bin
flash:/system-t0001016.bin
flash:/feature1-t0001016.bin
# (In IRF mode.) On a multichassis IRF fabric, display ISSU status information on the original master after the issu load command is completed.
ISSU state: Loaded
Compatibility: Incompatible
Work state: Independent active
Upgrade method: Chassis by chassis
Upgraded chassis:
chassis 2
Current upgrading chassis: None
Previous version list:
boot: 7.1.070, Test 0001015
system: 7.1.070, Test 0001015
patch1: 7.1.070, Test 0001015
Previous software images:
flash:/boot-t0001015.bin
flash:/system-t0001015.bin
flash:/patch1-t0001015.bin
Upgrade version list:
boot: 7.1.070, Test 0001016
system: 7.1.070, Test 0001016
patch1: 7.1.070, Test 0001016
Upgrade software images:
flash:/boot-t0001016.bin
flash:/system-t0001016.bin
flash:/patch1-t0001016.bin
# (In IRF mode.) On an IRF 3.1 fabric, display ISSU status information on the original master after the issu load command is completed.
<Sysname> display issu state
ISSU state: Loaded
Compatibility: Incompatible
Work state: Independent active
Upgrade method: Chassis by chassis
Upgraded chassis:
chassis 2
Current upgrading chassis:
..chassis 4
Previous version list:
boot: 7.1.070, Test 0001015
system: 7.1.070, Test 0001015
Previous software images:
flash:/boot-t0001015.bin
flash:/system-t0001015.bin
Upgrade version list:
boot: 7.1.070, Test 0001016
system: 7.1.070, Test 0001016
Upgrade software images:
flash:/boot-t0001016.bin
flash:/system-t0001016.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. · Incompatible—Upgrade to an incompatible version. · Unknown—No upgrade is in progress. |
|
Work state |
Operating status of the device: · Normal—The device is operating correctly. · Independent active—When you perform an ISSU to an incompatible version, the standby MPU that is upgraded first enters this state. In this state, the two MPUs of the device are running different software versions. |
|
Upgrade method |
Upgrade mode: · Card by card—MPUs are upgraded one by one. · Chassis by chassis ¡ For a compatible upgrade of a multichassis IRF fabric, one or more subordinate members are upgraded first, and then the original master and the remaining subordinate members are upgraded. ¡ For an incompatible upgrade of a multichassis IRF fabric, one subordinate member is upgraded first, and then the original master and the remaining subordinate members. |
|
Current version list |
Versions of currently running images. This field is displayed if no upgrade is taking place. |
|
Current software images |
File names of currently running images. This field is displayed if no upgrade is taking place. |
|
Previous version list |
Versions of the images that were running on the device before the ISSU. If you execute this command on an original standby MPU during an ISSU to an incompatible version, this field displays Unknown. |
|
Previous software images |
File names of the images that were running on the device before the ISSU. If you execute this command on an original standby MPU during an ISSU to an incompatible version, this field displays Unknown. |
|
Upgrade version list |
Versions of the upgrade images. If you execute this command on an original standby MPU during an ISSU to an incompatible version, this field displays Unknown. |
|
Upgrade software images |
File names of the upgrade images. If you execute this command on an original standby MPU during an ISSU for an incompatible version, this field displays Unknown. |
Related commands
issu accept
issu commit
issu load
display version comp-matrix
Use display version comp-matrix to display the recommended ISSU methods.
Syntax
display version comp-matrix file { boot filename | system filename | feature filename&<1-30>} *
display version comp-matrix file ipe ipe-filename
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
boot: Specifies a boot image file.
system: Specifies a system image file.
feature: Specifies a space-separated list of up to 30 feature image files.
filename: Specifies a .bin file in the filesystemname/filename.bin format. The file must be stored in the root directory of a file system on the device. The value string excluding the file system location section (if any) can have a maximum of 63 characters. For more information about specifying a file, see file system management in Fundamentals Configuration Guide.
ipe-filename: Specifies an .ipe file in the filesystemname/filename.ipe format. The file must be stored in the root directory of a file system on the device. The value string excluding the file system location section (if any) can have a maximum of 63 characters. For more information about specifying a file, see file system management in Fundamentals Configuration Guide.
If one or more images are incompatible, the incompatible upgrade method applies. The entire system needs to be rebooted during an incompatible upgrade.
Examples
# (In standalone mode.) Display the recommended ISSU methods. In this example, the specified image is compatible with the running images.
<Sysname> display version comp-matrix file feature flash:/feature1-t0001015.bin
Verifying the file flash:/feature1-t0001015.bin on slot 0.....Done.
Slot Upgrade Way
0 Service Upgrade
1 Service Upgrade
2 Service Upgrade
Influenced service according to following table on slot 0:
flash:/feature1-t0001015.bin
Feature1
Influenced service according to following table on slot 2:
flash:/feature1-t0001015.bin
Feature1
Influenced service according to following table on slot 1:
flash:/feature1-t0001015.bin
Feature1
|
Field |
Description |
|
Verifying the file |
The system was verifying the validity of the file. |
|
Influenced service according to following table |
Services that will be affected by the upgrade. This field is displayed only for compatible versions. |
|
Incompatible upgrade |
You are upgrading the software to an incompatible version. |
|
Upgrade Way |
ISSU method: · File Upgrade. · Reboot. This field is displayed only for compatible versions. For more information about ISSU methods, see Fundamentals Configuration Guide. |
Related commands
issu load
install abort
Use install abort to abort an ongoing activate or deactivate operation.
Syntax
install abort [ job-id ]
Views
User view
Predefined user roles
network-admin
Parameters
job-id: Specifies the job ID of an ISSU operation. If you do not specify this argument, the command aborts all ongoing software image activate and deactivate operations.
Usage guidelines
The system creates a software image management job each time you use the install activate, install add, install commit, install deactivate, or install remove command. Each job represents one command and is assigned a unique job ID. To obtain the ID of a job, use the display install job command.
When you abort an ongoing activate or deactivate operation, the system rolls back to the status it was in before the operation was started.
Examples
# Abort all ongoing software image activate and deactivate operations.
<Sysname> install abort
Related commands
display install job
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 feature filename&<1-30> * slot slot-number [ test ]
install activate patch filename { all | slot slot-number }
In IRF mode:
install activate 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
feature: Specifies a space-separated list of up to 30 feature image files
patch: Specifies a patch image file.
filename: Specifies a .bin file in the filesystemname/filename.bin format. The file must be stored in the root directory of a file system on the device. The value string excluding the file system location section (if any) can have a maximum of 63 characters. For more information about specifying a file, see file system management in Fundamentals Configuration Guide.
all: Specifies all cards. (In standalone mode.)
all: Specifies all cards. (In IRF mode.)
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.
Before you use this command to activate a software image, read the release notes to identify the licensing requirements for the image. If the image requires a license, make sure the device has a valid license installed for the image.
Images run in memory immediately after they are activated. However, only patch images activated by using the install activate patch filename all command still run in memory after a reboot. For other images to take effect after a reboot, you must commit the software change by using the install commit command.
If the specified files are not stored on the MPU to be upgraded, the command copies the files to the MPU automatically.
(In standalone mode.) If you specify the active MPU for the slot slot-number option, the command takes effect on the active MPU and all LPUs. If you specify the standby MPU for the slot slot-number option, the command takes effect only on the standby MPU.
(In IRF mode.) If you specify the global active MPU for the chassis chassis-number slot slot-number option, the command takes effect on the global active MPU and all LPUs. If you specify a standby MPU for the chassis chassis-number slot slot-number option, the command takes effect on the standby MPU.
(In IRF mode.) At reboot, a subordinate device automatically synchronizes the master device's configuration and status data. You must wait for the synchronization to complete before using the install activate command on the subordinate device. To identify whether the synchronization is complete, use the display system stable state command. The synchronization is complete if the System State field displays Stable.
You can install up to 32 .bin files on the device, including one boot image file, one system image file, and up to 30 feature and patch image files.
Examples
# (In standalone mode.) Identify the ISSU method for feature upgrade with feature1.bin on the standby MPU (in slot 1) and the upgrade impact.
<Sysname> install activate feature flash:/feature1.bin slot 1 test
Copying file flash:/feature1.bin to slot1#flash:/feature1.bin......Done.
Verifying the file flash:/feature1.bin on slot 1.....Done.
Upgrade summary according to following table:
flash:/feature1.bin
Running Version New Version
Test 0001015 Test 0001016
Slot Upgrade Way
1 Service Upgrade
Influenced service according to following table:
flash:/feature1.bin
Feature1
The output shows that a service upgrade is recommended. The Feature1 module will be rebooted during the upgrade.
# (In standalone mode.) Activate the system image in system.bin and the feature images in feature1.bin on the standby MPU (in slot 1).
<Sysname> install activate system flash:/system.bin feature flash:/feature1.bin slot 1
Copying file flash:/system.bin to slot1#flash:/system.bin......Done.
Verifying the file flash:/system.bin on slot 1.....Done.
Copying file flash:/feature1.bin to slot1#flash:/feature1.bin......Done.
Verifying the file flash:/feature1.bin on slot 1.....Done.
Verifying the file flash:/feature1.bin on slot 1.....Done.
Verifying the file flash:/system.bin on slot 1.....Done.
Upgrade summary according to following table:
flash:/system.bin
Running Version New Version
Test 0001015 Test 0001016
flash:/feature1.bin
Running Version New Version
None Test 0001015
Slot Upgrade Way
1 Service Upgrade
Upgrading software images to compatible versions. Continue? [Y/N]:y
This operation might take several minutes, please wait...Done.
# (In IRF mode.) Activate the patch image in patch1.bin on the global standby MPU in slot 1 of chassis 1.
<Sysname> install activate patch flash:/patch1.bin chassis 1 slot 1
Copying file flash:/patch1.bin to chassis1#slot1#flash:/patch1.bin......Done.
Verifying the file flash:/patch1.bin on chassis 1 slot 1.....Done.
This operation might take several minutes, please wait...Done.
Table 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. 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 stored in the root directory of a file system on the device. The value string excluding the file system location section (if any) can have a maximum of 63 characters. For more information about specifying a file, see file system management in Fundamentals Configuration Guide.
filesystem: Specifies the destination file system for the software images, in the filesystemname format.
Usage guidelines
To use the install activate command to activate software images, you must use .bin image files. If the upgrade file is an .ipe file, use this command to decompress the .ipe file before you start the upgrade.
To identify software images that are included in an .ipe file, use the display install ipe-info command.
Examples
# Decompress all.ipe to the flash memory.
<Sysname> install add flash:/all.ipe flash:
Verifying the file flash:/all.ipe on slot 1...Done.
Decompressing file boot.bin to flash:/boot.bin.......................Done.
Decompressing file system.bin to flash:/system.bin.................................Done.
install commit
Use install commit to commit software changes.
Syntax
install commit
Views
User view
Predefined user roles
network-admin
Usage guidelines
Before you use this command, read the release notes to identify software image licensing requirements. Make sure the device has valid licenses for all license-based images.
This command adds the patch image file to the startup software image list that the device used at startup.
· If the device used the main startup software image list at startup, this command adds the patch image file to the main startup software image list.
· If the device used the backup startup software image list at startup, this command adds the patch image file to the backup startup 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 Fundamentals Configuration Guide.
Examples
# Commit software changes.
<Sysname> install commit
This operation will take several minutes, please wait...........................Done.
Related commands
install activate
install deactivate
install 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 a space-separated list of up to 30 feature image files.
patch: Specifies a patch image file.
filename: Specifies a .bin file in the filesystemname/filename.bin format. The value string can have a maximum of 63 characters. The file system name cannot contain file system location information. For more information about specifying a file, see file system management in Fundamentals Configuration Guide.
all: Specifies all cards on which the specified patch image file has been activated. (In standalone mode.)
all: Specifies all cards on which the specified patch image file has been activated. (In IRF mode.)
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
At reboot, a subordinate device automatically synchronizes the master device's configuration and status data. You must wait for the synchronization to complete before using the install deactivate command on the subordinate device. To identify whether the synchronization is complete, use the display system stable state command. The synchronization is complete if the System State field displays Stable.
You can deactivate only active feature and patch images.
Images stop running in memory immediately after they are deactivated. However, only patch images deactivated by using the install deactivate patch filename all command do not run after a reboot. To prevent other deactivated images from running after a reboot, you must commit the software change by using the install commit command.
Examples
# (In standalone mode.) Deactivate the patch images in the route-patch.bin file for a slot.
<Sysname> install deactivate patch flash:/route-patch.bin slot 1
This operation might take several minutes, please wait...Done.
# (In IRF mode.) Deactivate the patch images in the route-patch.bin file for a card.
<Sysname> install deactivate patch flash:/route-patch.bin chassis 1 slot 1
This operation might take several minutes, please wait...Done.
Related commands
display install active
display install inactive
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 value string can have a maximum of 63 characters. The file must be stored in the root directory of a file system on the device. The file system name cannot contain file system location information. For more information about specifying a file, see file system management in Fundamentals Configuration Guide.
inactive: Deletes all inactive software image files in the root directories of the specified file systems.
Usage guidelines
This command permanently deletes the image files from the device.
Examples
# Delete inactive software image file flash:/feature1.bin.
<Sysname> install remove flash:/feature1.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 that the system can start up and operate correctly after an ISSU, execute this command to verify the following items:
· Integrity—Verify that the boot, system, and feature images are integral.
· Consistency—Verify that the same active images are running across the entire system.
· Software commit status—Verify that the active images are committed as needed.
If a software image fails the verification, perform the following tasks to resolve the problem:
· To ensure software integrity, download and install the software images again.
· To guarantee software image consistency or change software commit status, use the install activate, install deactivate, and install commit commands as appropriate.
Examples
# (In standalone mode.) Verify the software change confirmation status and software image integrity and consistency.
<Sysname> install verify
Active packages on slot 1 are the reference packages.
Packages will be compared with the reference packages.
This operation will take several minutes, please wait...
Verifying packages on slot 0:
Start to check active package completeness.
Verifying the file flash:/boot-t0001015.bin on slot 0.....................Done.
flash:/boot-t0001015.bin verification successful.
Verifying the file flash:/system-t0001015.bin on slot 0.....................Done.
flash:/system-t0001015.bin verification successful.
Start to check active package consistency.
Active packages are consistent with committed packages on their own board.
Active packages are consistent with the reference packages.
Verifying packages on slot 1:
Start to check active package completeness.
Verifying the file flash:/boot-t0001015.bin on slot 1.....................Done.
flash:/boot-t0001015.bin verification successful.
Verifying the file flash:/system-t0001015.bin on slot 1.....................Done.
flash:/system-t0001015.bin verification successful.
Start to check active package consistency.
Active packages are consistent with committed packages on their own board.
Active packages are consistent with the reference packages.
Verification is done.
# (In IRF mode.) Verify the software change confirmation status and software image integrity and consistency.
<Sysname> install verify
Active packages on chassis 1 slot 1 are the reference packages.
Packages will be compared with the reference packages.
This operation will take several minutes, please wait...
Verifying packages on chassis 1 slot 1:
Start to check active package completeness.
Verifying the file flash:/boot-t0001015.bin on chassis 1 slot 1.....................Done.
flash:/boot-t0001015.bin verification successful.
Verifying the file flash:/system-t0001015.bin on chassis 1 slot 1.....................Done.
flash:/system-t0001015.bin verification successful.
Start to check active package consistency.
Active packages are consistent with committed packages on their own board.
Active packages are consistent with the reference packages.
Verifying packages on chassis 2 slot 1:
Start to check active package completeness.
Verifying the file flash:/boot-t0001015.bin on chassis 2 slot 1.....................Done.
flash:/boot-t0001015.bin verification successful.
Verifying the file flash:/system-t0001015.bin on chassis 2 slot 1.....................Done.
flash:/system-t0001015.bin verification successful.
Start to check active package consistency.
Active packages are consistent with committed packages on their own board.
Active packages are consistent with the reference packages.
Verification is done.
issu accept
Use issu accept to accept the upgrade to a compatible version.
Syntax
issu accept
Views
User view
Predefined user roles
network-admin
Usage guidelines
The issu accept command does not apply to an ISSU to an incompatible version.
Examples
# Accept the upgrade to a compatible version.
<Sysname> issu accept
Related commands
issu load
issu run switchover
issu commit
Use issu commit to upgrade the original master and the subordinate members that have not been upgraded 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 or a subordinate member that has not been upgraded.
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.
You must wait for one upgraded subordinate member to start up again and join the IRF fabric before upgrading another subordinate member.
Examples
# (In IRF mode.) Upgrade the members that have not been upgraded during an ISSU to a compatible version. In this example, the IRF fabric has four members, and only the member with the ID 2 has been upgraded.
<Sysname> issu commit chassis 3
Copying file flash:/feature1.bin to chassis3#slot1#flash:/feature1.bin...Done.
Verifying the file flash:/feature1.bin on chassis 3 slot 1..............Done.
Upgrade summary according to following table:
flash:/feature1.bin
Running Version New Version
Test 0001015 Test 0001016
Chassis Slot Upgrade Way
3 0 Service Upgrade
3 1 Service Upgrade
3 2 Service Upgrade
3 3 Service Upgrade
3 4 Service Upgrade
Upgrading software images to compatible versions. Continue? [Y/N]:y
This operation might take several minutes, please wait...Done.
<Sysname> issu commit chassis 4
Copying file flash:/feature1.bin to chassis4#slot0#flash:/feature1.bin...Done.
Verifying the file flash:/feature1.bin on chassis 4 slot 0..............Done.
Copying file flash:/feature1.bin to chassis4#slot1#flash:/feature1.bin...Done.
Verifying the file flash:/feature1.bin on chassis 4 slot 1..............Done
Upgrade summary according to following table:
flash:/feature1.bin
Running Version New Version
Test 0001015 Test 0001016
Chassis Slot Upgrade Way
4 0 Service Upgrade
4 1 Service Upgrade
4 2 Service Upgrade
4 3 Service Upgrade
4 4 Service Upgrade
Upgrading software images to compatible versions. Continue? [Y/N]:y
This operation might take several minutes, please wait...Done.
<Sysname> issu commit chassis 1
Copying file flash:/feature1.bin to chassis1#slot0#flash:/feature1.bin...Done.
Verifying the file flash:/feature1.bin on chassis 1 slot 0..............Done.
Copying file flash:/feature1.bin to chassis1#slot1#flash:/feature1.bin...Done.
Verifying the file flash:/feature1.bin on chassis 1 slot 1..............Done.
Upgrade summary according to following table:
flash:/feature1.bin
Running Version New Version
Test 0001015 Test 0001016
Chassis Slot Upgrade Way
1 0 Service Upgrade
1 1 Service Upgrade
1 2 Service Upgrade
1 3 Service Upgrade
1 4 Service Upgrade
Upgrading software images to compatible versions. Continue? [Y/N]:y
This operation might take several minutes, please wait...Done.
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> [ reboot ]
issu load file ipe ipe-filename chassis chassis-number&<1-3> [ reboot ]
Views
User view
Predefined user roles
network-admin
Parameters
boot: Specifies a boot image file.
system: Specifies a system image file.
feature: Specifies a space-separated list of up to 30 feature image files.
filename: Specifies a .bin file in the filesystemname/filename.bin format. The file must be stored in the root directory of a file system on the 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. For more information about specifying a file, see file system management in Fundamentals Configuration Guide.
ipe-filename: Specifies an .ipe file in the filesystemname/filename.ipe format. The file must be stored in the root directory of a file system on the 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. For more information about specifying a file, see file system management in Fundamentals Configuration Guide.
reboot: Uses the reboot method for the upgrade. For an incremental upgrade, specify this keyword if you want to use the reboot upgrade method. If you do not specify this keyword, the recommended upgrade method is used.
Usage guidelines
You may upgrade all or some of the software images. If you are upgrading only some of the images, make sure the new images are compatible with the images that are not to be upgraded. The upgrade will fail if a conflict exists.
This command performs the following operations:
· Checks the version compatibility.
· Identifies the upgrade method.
· Loads the new images to upgrade the specified member devices.
· Sets the new images as the main startup software images for the specified member devices so the upgrade can survive a reboot.
At reboot, a subordinate device automatically synchronizes the master device's configuration and status data. You must wait for the synchronization to complete before using the issu load command on the subordinate device. To identify whether the synchronization is complete, use the display system stable state command. The synchronization is complete if the System State field displays Stable.
Examples
# (In IRF mode.) Upgrade subordinate member 2 with image file flash:/version.ipe.
<Sysname> issu load file ipe flash:/version-t0001015.ipe chassis 2
This operation will delete the rollback point information for the previous upgrade and maybe get unsaved configuration lost. Continue? [Y/N]:y
Verifying image file flash:/version-t0001015.ipe on chassis 2 slot 0.................Done.
Verifying image file flash:/version-t0001015.ipe on chassis 2 slot 1.................Done.
Decompressing file BOOT-T0001015.bin to flash:/BOOT-E1133.bin.............Done.
Decompressing file SYSTEM-T0001015.bin to flash:/SYSTEM-E1133.bin...........Done.
Decompression completed.
Do you want to delete flash:/version-t0001015.ipe now? [Y/N]:n
Upgrade summary according to following table:
flash:/BOOT-T0001015.bin
Running Version New Version
Test 0001015 Test 0001016
flash:/SYSTEM-E1133.bin
Running Version New Version
Test 0001015 Test 0001016
Chassis Slot Upgrade Way
2 0 Reboot
2 1 Reboot
Upgrading software images to compatible versions. Continue? [Y/N]:y
This operation might take several minutes, please wait...Done.
Table 7 Command output
|
Field |
Description |
|
Verifying the file |
The system was verifying the validity of the file. |
|
Copying file |
(In IRF mode.) The system was copying the upgrade file to a global standby MPU. This field is displayed if you specified a global standby MPU for the command. |
|
Upgrade Way |
ISSU method: · Service Upgrade. · File Upgrade. · Reboot. This field is displayed only for an upgrade to a compatible version. 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
The automatic software version rollback feature is complicated. As a best practice, disable this feature before performing an ISSU.
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
· The function of this command is as follows:
¡ For a compatible upgrade, this command performs operations depending on the ISSU method.
- Incremental upgrade—Performs a process-level master/subordinate switchover for the processes to be upgraded.
- Reboot upgrade—Reboots the current master with the old software version to cause the upgraded subordinate member to become the new master.
¡ For an incompatible upgrade, the issu load command splits the IRF fabric into two fabrics, with the upgraded members forming a new fabric. The issu run switchover command reboots the old IRF fabric's members with the upgrade images to join the new IRF fabric as subordinate members.
At reboot, a subordinate device automatically synchronizes the master device's configuration and status data. You must wait for the synchronization to complete before using the issu run switchover command on the subordinate device. To identify whether the synchronization is complete, use the display system stable state command. The synchronization is complete if the System State field displays Stable.
During a reboot upgrade to a compatible version, the LPUs reboot to load the new software from the upgraded MPU. A transient service outage occurs on the cards.
Examples
# (In IRF mode.) Perform a switchover.
<Sysname> issu run switchover
Upgrade summary according to following table:
flash:/boot-t0001015.bin
Running Version New Version
Test 0001015 Test 0001016
flash:/system-t0001015.bin
Running Version New Version
Test 0001015 Test 0001016
Chassis Slot Switchover Way
2 1 Global active standby MPU switchover
Upgrading software images to compatible versions. Continue? [Y/N]:y
This operation might take several minutes, please wait...Done.
Table 8 Command output
|
Field |
Description |
|
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
