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-Device management commands
- 10-Tcl commands
- 11-Python commands
- 12-License management commands
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 08-ISSU commands | 138.73 KB |
ISSU commands
display install active
Use display install active to display active software images.
display install active [ slot slot-number ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies an IRF member device by its member ID or specifies a PEX by its virtual slot number. On an IRF fabric, this command displays information for all member devices if you do not specify a member device. On an IRF 3 system, this command displays information for all IRF member devices and PEXs if you do not specify an IRF member device or PEX.
verbose: Displays detailed information. If you do not specify this keyword, the command displays only image names.
Examples
# Display active software images.
<Sysname> display install active
Active packages on slot 1:
flash:/boot.bin
flash:/system.bin
flash:/feature1.bin
# Display detailed information about active software images.
<Sysname> display install active verbose
Active packages on slot 1:
flash:/boot.bin
[Package]
Vendor: H3C
Product: S7500EXSV2
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: S7500EXSV2
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: S7500EXSV2
Service name: test
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu
[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—Member device.
|
|
[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
display install backup [ slot slot-number ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies an IRF member device by its member ID or specifies a PEX that has storage media by its virtual slot number. On an IRF fabric, this command displays information for all member devices if you do not specify a member device. On an IRF 3 system, this command displays information for all parent devices and all PEXs with storage media if you do not specify a parent device or PEX.
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, use the boot-loader file command.
Examples
# Display the backup startup software images.
<Sysname> display install backup
Backup startup software images on slot 1:
flash:/boot.bin
flash:/system.bin
# 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: S7500EXSV2
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: S7500EXSV2
Service name: system
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu
[Component]
Component: system
Description: system package
For information about the command output, see Table 1.
Related commands
boot-loader file
display install committed
display install committed
Use display install committed to display main startup software images.
Syntax
display install committed [ slot slot-number ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies an IRF member device by its member ID or specifies a PEX by its virtual slot number. On an IRF fabric, this command displays information for all member devices if you do not specify a member device. On an IRF 3 system, this command displays information for all IRF member devices and PEXs if you do not specify an IRF member device or PEX.
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
# Display the main startup software images.
<Sysname> display install committed
Committed packages on slot 1:
flash:/boot.bin
flash:/system.bin
flash:/feature1.bin
# 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: S7500EXSV2
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: S7500EXSV2
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: S7500EXSV2
Service name: feature1
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu
[Component]
Component: feature1
Description: feature1 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
display install inactive [ slot slot-number ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies an IRF member device by its member ID or specifies a PEX that has storage media by its virtual slot number. On an IRF fabric, this command displays information for all member devices if you do not specify a member device. On an IRF 3 system, this command displays information for all parent devices and PEXs if you do not specify a parent device or PEX.
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 1:
flash:/feature1.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 1:
flash:/feature1.bin
[Package]
Vendor: H3C
Product: S7500EXSV2
Service name: feature1
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu
[Component]
Component: feature1
Description: feature1 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 Fundamental Configuration Guide.
Examples
# 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-XS 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
# 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.
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/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.
# 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.
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 Fundamental Configuration Guide.
all: Specifies all software image files in the root directories of the master's file systems.
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: S7500EXSV2
Service name: system
Platform version: 7.1.070
Product version: Alpha 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: S7500EXSV2
Service name: system
Platform version: 7.1.070
Product version: Alpha 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
display install which { component name | file filename } [ slot slot-number ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
component name: Specifies a component name.
file filename: Specifies a file in the filename.extension format, a case-insensitive string of up to 63 characters. It cannot contain path information.
slot slot-number: Specifies an IRF member device by its member ID or specifies a PEX that has storage media by its virtual slot number. On an IRF fabric, this command displays information for all member devices if you do not specify a member device. On an IRF 3 system, this command displays information for all parent devices and PEXs if you do not specify a parent device or PEX.
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
# 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: S7500EXSV2
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.
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—Member device.
|
display issu state
Use display issu state to display ISSU status information.
Syntax
display issu state
Views
Any view
Predefined user roles
network-admin
network-operator
Usage guidelines
During an ISSU that uses issu commands, you can use this command to verify the ISSU status and determine what to do next.
This command does not apply to an ISSU that uses install commands, because the ISSU state machine is not involved.
Examples
# Display ISSU status information when no upgrade is taking place.
<Sysname> display issu state
ISSU state: Init
Compatibility: Unknown
Work state: Normal
Upgrade method: Card by card
Upgraded slot: None
Current upgrading slot: None
Current version list:
boot: 7.1.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
# 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
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 process. This value is displayed if you execute the command on an original subordinate member. |
|
Compatibility |
Version compatibility: · Compatible—Upgrade to a compatible version. · Incompatible—Upgrade to an incompatible version. · Unknown—No upgrade is in process. |
|
Work state |
Operating status of the device: · Normal—The device is operating correctly. · Independent active—When you perform an ISSU to an incompatible version, a subordinate member that is upgraded first enters this state. In this state, member devices are not running the same software versions. |
|
Upgrade method |
Upgrade mode. The value of this field is fixed at Card by card. In this mode, member devices are upgraded one by one. |
|
Current version list |
Versions of currently running images. This field is displayed if no upgrade is taking place. |
|
Current software images |
File names of currently running images. This field is displayed if no upgrade is taking place. |
|
Previous version list |
Versions of the images that were running on the device before the ISSU. If you execute the command on an original subordinate member while the member is being upgraded to an incompatible version, this field displays Unknown. |
|
Previous software images |
File names of the images that were running on the device before the ISSU. If you execute the command on an original subordinate member while the member is being upgraded to an incompatible version, this field displays Unknown. |
|
Upgrade version list |
Versions of the upgrade images. If you execute the command on an original subordinate member while the member is being upgraded to an incompatible version, this field displays Unknown. |
|
Upgrade software images |
File names of the upgrade images. If you execute the command on an original subordinate member while the member is being upgraded to an incompatible version, this field displays Unknown. |
Related commands
issu accept
issu commit
issu load
display version comp-matrix
Use display version comp-matrix to display version compatibility information and identify the recommended upgrade method.
Syntax
display version comp-matrix
display version comp-matrix file { boot filename | system filename | feature filename&<1-30> } *
display version comp-matrix file ipe ipe-filename
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
boot: Specifies a boot image file.
system: Specifies a system image file.
feature: Specifies a space-separated list of up to 30 feature image files.
filename: Specifies a .bin file in the filesystemname/filename.bin format. The file must be stored in the root directory of a file system on the device. The value string excluding the file system location section (if any) can have a maximum of 63 characters. For more information about specifying a file, see Fundamental 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 Fundamental Configuration Guide.
To display compatibility information for the running software images, do not specify any image files for the command. If you specify the upgrade image files, the command displays the following information:
· Compatibility information for upgrade images.
· Recommended ISSU methods for upgrading the running images to the upgrade images.
On an IRF 3 system, the following rules apply:
· This command displays the following information if you do not specify any files:
¡ Compatibility information for the running images of the parent device.
¡ Compatibility information for the running images of PEXs.
· If you specify one or more files stored on parent devices, the command displays the following information:
¡ Compatibility information for the specified images on the parent device.
¡ Compatibility information for the specified images on the PEXs. The prerequisite is that you use the issu pex command to specify the images used for PEX upgrade before using this command.
¡ Recommended ISSU methods for upgrading the running images to the specified images.
· This command does not display information about software compatibility between the parent device and the PEXs. For this compatibility information, see the release notes.
If one or more images are incompatible, the incompatible upgrade method applies. The entire system needs to be rebooted during an incompatible upgrade.
Examples
# Display compatibility information for the running images.
<Sysname> display version comp-matrix
Boot image: flash:/boot-t0001015.bin
Version:
7.1.070
System image: flash:/system-t0001015.bin
Version:
7.1.070-Test 0001015
Version compatibility list:
7.1.070-Test 0001015
Version dependency boot list:
7.1.070
Feature image: flash:/feature1-t0001015.bin
Version:
7.1.070-Test 0001015
Version compatibility list:
7.1.070-Test 0001015
Version dependency system list:
7.1.070-Test 0001015
# Display compatibility information for upgrade images as well as the recommended ISSU method. (In this example, the specified images are compatible with the running images.)
<Sysname> display version comp-matrix file boot flash:/boot-t0001015.bin system flash:/system-t0001015.bin feature flash:/feature1-t0001015.bin
Verifying the file flash:/feature1-t0001015.bin on slot 1.....Done.
Verifying the file flash:/boot-t0001015.bin on slot 1.....Done.
Verifying the file flash:/system-t0001015.bin on slot 1.....Done.
Boot image: flash:/boot-t0001015.bin
Version:
7.1.070
System image: flash:/system-t0001015.bin
Version:
7.1.070-Test 0001015
Version compatibility list:
7.1.070-Test 0001015
Version dependency boot list:
7.1.070
Feature image: flash:/feature1-t0001015.bin
Version:
7.1.070-Test 0001015
Version compatibility list:
7.1.070-Test 0001014
7.1.070-Test 0001015
Version dependency system list:
7.1.070-Test 0001015
Slot Upgrade Way
1 File Upgrade
# Display compatibility information for the running images on the parent device, and compatibility information for the running images on the PEXs.
<Sysname> display version comp-matrix
Boot image: flash:/boot-t0001015.bin
Version:
7.1.070
System image: flash:/system-t0001015.bin
Version:
7.1.070-Test 0001015
Version compatibility list:
7.1.070-Test 0001015
Version dependency boot list:
7.1.070
Compatible info of S6300:
Boot image: flash:/rpu-S6300-boot-t0001015.bin
Version:
7.1.070
System image: flash:/rpu-S6300-system-t0001015.bin
Version:
7.1.070-Test 0001015
Version compatibility list:
7.1.070-Test 0001015
Version dependency boot list:
7.1.070
Feature image: flash:/rpu-S6300-devkit-t0001015.bin
Version:
7.1.070-Test 0001015
Version compatibility list:
7.1.070-Test 0001015
Version dependency system list:
7.1.070-Test 0001015
# Display the following information:
· Compatibility information for the upgrade images that are used for the parent device upgrade.
· Compatibility information for the upgrade images that are used for the S6300PEX upgrade.
· Recommended ISSU methods for the upgrades.
In this example, the specified images are incompatible with the running images.
<Sysname> issu pex PEX-S6300 file boot flash:/S6300-boot-t0001015.bin system flash:/S6300-system-t0001015.bin feature flash:/S6300-feature1-t0001017.bin
Verifying the file flash:/S6300-feature1-t0001017.bin on slot 1...Done.
Verifying the file flash:/S6300-boot-t0001015.bin on slot 1...Done.
Verifying the file flash:/S6300-system-t0001015.bin on slot 1...Done.
<Sysname> display version comp-matrix file boot flash:/boot-t0001015.bin system flash:/system-t0001015.bin feature flash:/feature1-t0001017.bin
Verifying the file flash:/feature1-t0001017.bin on slot 1.....Done.
Verifying the file flash:/boot-t0001015.bin on slot 1.....Done.
Verifying the file flash:/system-t0001015.bin on slot 1.....Done.
Verifying the file flash:/S6300-boot-t0001015.bin on slot 1...Done.
Verifying the file flash:/S6300-system-t0001015.bin on slot 1...Done.
Verifying the file flash:/S6300-feature1-t0001017.bin on slot 1...Done.
Boot image: flash:/boot-t0001015.bin
Version:
7.1.070
System image: flash:/system-t0001015.bin
Version:
7.1.070-Test 0001015
Version compatibility list:
7.1.070-Test 0001015
Version dependency boot list:
7.1.070
Feature image: flash:/feature1-t0001017.bin
Version:
7.1.070-Test 0001017
Version compatibility list:
7.1.070-Test 0001017
Version dependency system list:
7.1.070-Test 0001017
Compatible info of S6300:
Boot image: flash:/rpu-S6300-boot-t0001015.bin
Version:
7.1.070
System image: flash:/rpu-S6300-system-t0001015.bin
Version:
7.1.070-Test 0001015
Version compatibility list:
7.1.070-Test 0001015
Version dependency boot list:
7.1.070
Feature image: flash:/S6300-feature1-t0001017.bin
Version:
7.1.070-Test 0001017
Version compatibility list:
7.1.070-Test 0001017
Version dependency system list:
7.1.070-Test 0001017
Incompatible upgrade.
# Display the following information:
· Compatibility information for the upgrade images that are used for the parent device upgrade.
· Compatibility information for the upgrade image that are used for the S6300 PEX upgrade.
· Recommended ISSU methods for the upgrades.
In this example, the specified images are compatible with the running images.
<Sysname> issu pex PEX-S6300 file feature flash:/S6300-feature1-t0001015.bin
Verifying the file flash:/S6300-feature1-t0001015.bin on slot 1.....Done.
<Sysname> display version comp-matrix file boot flash:/boot-t0001015.bin system flash:/system-t0001015.bin feature flash:/feature1-t0001015.bin
Verifying the file flash:/feature1-t0001015.bin on slot 1.....Done.
Verifying the file flash:/boot-t0001015.bin on slot 1.....Done.
Verifying the file flash:/system-t0001015.bin on slot 1.....Done.
Verifying the file flash:/S6300-feature1-t0001015.bin on slot 1.....Done.
Boot image: flash:/boot-t0001015.bin
Version:
7.1.070
System image: flash:/system-t0001015.bin
Version:
7.1.070-Test 0001015
Version compatibility list:
7.1.070-Test 0001014
7.1.070-Test 0001015
Version dependency boot list:
7.1.070
Feature image: flash:/feature1-t0001015.bin
Version:
7.1.070-Test 0001015
Version compatibility list:
7.1.070-Test 0001014
7.1.070-Test 0001015
Version dependency system list:
7.1.070-Test 0001014
7.1.070-Test 0001015
Compatible info of S6300:
Feature image: flash:/S6300-feature1-t0001015.bin
Version:
7.1.070-Test 0001015
Version compatibility list:
7.1.070-Test 0001014
7.1.070-Test 0001015
Version dependency system list:
7.1.070-Test 0001014
7.1.070-Test 0001015
Slot Upgrade Way
1 File Upgrade
102 File Upgrade
|
Field |
Description |
|
Verifying the file |
The system was verifying the validity of the file. |
|
Version compatibility list |
· Under a system image, this field shows all system image versions that are compatible with the system image. · Under a feature image, this field shows all feature image versions that are compatible with the feature image. |
|
Version dependency boot list |
Boot image versions that support the system image. To install the system image, you must install one of the boot image versions that are in the list. |
|
Version dependency system list |
System image versions that support the feature image. To install the feature image, you must install one of the system image versions that is in the list. |
|
Compatible info of S6300: |
|
|
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
install activate { boot filename | system filename | feature filename&<1-30> } * slot slot-number [ test ]
install activate patch filename { all | slot slot-number }
Views
User view
Predefined user roles
network-admin
Parameters
boot: Specifies a boot image file. This keyword is available when only PEXs need to be upgraded.
system: Specifies a system image file. This keyword is available when only PEXs need to be upgraded.
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 Fundamental Configuration Guide.
all: Specifies all member devices and PEXs.
slot slot-number: Specifies an IRF member device by its member ID or specifies a PEX by its virtual slot number.
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 images activated by using the install activate patch filename all command still run in memory after a reboot. For other images to take effect after a reboot, you must commit the software change by using the install commit command.
If the specified files are not stored on the member device to be upgraded, the command copies the images to the member device automatically.
At reboot, a subordinate device automatically synchronizes the master device's configuration and status data. You must wait for the synchronization to complete before using the install activate command on the subordinate device. To identify whether the synchronization is complete, use the display system stable state command. The synchronization is complete if the System State field displays Stable.
Examples
# Identify the ISSU method for feature upgrade with feature1.bin on subordinate member 2 and the upgrade impact.
<Sysname> install activate feature flash:/feature1.bin slot 2 test
Copying file flash:/feature1.bin to slot2#flash:/feature1.bin......Done.
Verifying the file flash:/feature1.bin on slot 2.....Done.
Upgrade summary according to following table:
flash:/feature1.bin
Running Version New Version
Test 0001015 Test 0001016
Slot Upgrade Way
2 Reboot
Influenced service according to following table:
flash:/feature1.bin
Feature1
The output shows that a service upgrade is recommended. The Feature1 module will be rebooted during the upgrade.
# Activate the system image in system.bin and the feature images in feature1.bin on member device 2.
<Sysname> install activate system flash:/system.bin feature flash:/feature1.bin slot 2
Copying file flash:/system.bin to slot2#flash:/system.bin......Done.
Verifying the file flash:/system.bin on slot 2.....Done.
Copying file flash:/feature1.bin to slot2#flash:/feature1.bin......Done.
Verifying the file flash:/feature1.bin on slot 2.....Done.
Upgrade summary according to following table:
flash:/system.bin
Running Version New Version
Test 0001015 Test 0001016
flash:/feature1.bin
Running Version New Version
None Test 0001016
Slot Upgrade Way
2 Service Upgrade
Upgrading software images to compatible versions. Continue? [Y/N]:y
This operation might take several minutes, please wait.......................................................................Done.
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 Fundamental 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 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
install deactivate feature filename&<1-30> slot slot-number
install deactivate patch filename { all | slot slot-number }
Views
User view
Predefined user roles
network-admin
Parameters
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 Fundamental Configuration Guide.
all: Specifies all member devices and PEXs on which the specified patch image file has been activated.
slot slot-number: Specifies an IRF member device by its member ID or specifies a PEX by its virtual slot number.
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 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
# Deactivate the patch images in the route-patch.bin file for a slot.
<Sysname> install deactivate patch flash:/route-patch.bin slot 1
Related commands
display install active
display install inactive
install remove
Use install remove to delete an inactive software image file.
Syntax
install remove [ slot slot-number ] { filename | inactive }
Views
User view
Predefined user roles
network-admin
Parameters
slot slot-number: Specifies an IRF member device by its member ID or specifies a PEX that has storage media by its virtual slot number. On an IRF fabric, this command deletes inactive software images from all member devices if you do not specify a member device. On an IRF 3 system, this command deletes inactive software images from all parent devices and PEXs if you do not specify a parent device or PEX.
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 Fundamental 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
# Verify the software change confirmation status and software image integrity and consistency.
<Sysname> install verify
Active packages on slot 1 are the reference packages.
Packages will be compared with the reference packages.
This operation will take several minutes, please wait...
Verifying packages on slot 1:
Start to check active package completeness.
Verifying the file flash:/boot-t0001015.bin on slot 1.....................Done.
flash:/boot-t0001015.bin verification successful.
Verifying the file flash:/system-t0001015.bin on slot 1.....................Done.
flash:/system-t0001015.bin verification successful.
Start to check active package consistency.
Active packages are consistent with committed packages on their own board.
Active packages are consistent with the reference packages.
Verifying packages on slot 2:
Start to check active package completeness.
Verifying the file flash:/boot-t0001015.bin on slot 2.....................Done.
flash:/boot-t0001015.bin verification successful.
Verifying the file flash:/system-t0001015.bin on slot 2.....................Done.
flash:/system-t0001015.bin verification successful.
Start to check active package consistency.
Active packages are consistent with committed packages on their own board.
Active packages are consistent with the reference packages.
Verification is done.
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 slot slot-number
Views
User view
Predefined user roles
network-admin
Parameters
slot slot-number: Specifies the member ID of the original master or a subordinate member that has not been upgraded.
Usage guidelines
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.
Use this command to upgrade the original master and the subordinate members that have not been upgraded, one by one. You must wait for one upgraded member to start up again and join the IRF fabric before upgrading another member. After all members are upgraded, the ISSU status changes to Init, and the ISSU process ends.
Examples
# After member 2 is upgraded and becomes the new master, upgrade the original master (member 3) and the other subordinate members that have not been upgraded (member 4 and member 1).
<Sysname> issu commit slot 3
Upgrade summary according to following table:
flash:/feature1.bin
Running Version New Version
Test 0001015 Test 0001016
Slot Upgrade Way
3 Service Upgrade
Upgrading software images to compatible versions. Continue? [Y/N]:
<Sysname> issu commit slot 4
Verifying the file flash:/feature1.bin on slot 4..............Done.
Copying file flash:/feature1.bin to slot4#flash:/feature1.bin...Done.
Upgrade summary according to following table:
flash:/feature1.bin
Running Version New Version
Test 0001015 Test 0001016
Slot Upgrade Way
4 Service Upgrade
Upgrading software images to compatible versions. Continue? [Y/N]:
<Sysname> issu commit slot 1
Verifying the file flash:/feature1.bin on slot 1..............Done.
Copying file flash:/feature1.bin to slot1#flash:/feature1.bin...Done.
Upgrade summary according to following table:
flash:/feature1.bin
Running Version New Version
Test 0001015 Test 0001016
Slot Upgrade Way
1 Service Upgrade
Upgrading software images to compatible versions. Continue? [Y/N]:
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 the software images of 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> } * slot slot-number&<1-9> [ reboot ]
issu load file ipe ipe-filename slot slot-number&<1-9> [ 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 master 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 Fundamental 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 master 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 Fundamental Configuration Guide.
slot slot-number: Specifies the member ID of a subordinate member. You can specify a space-separated list of up to nine member IDs. On a single-chassis IRF fabric, enter the member ID of the member device to upgrade the entire fabric. On a multichassis IRF fabric, you can specify only one member ID for a compatible upgrade and can specify multiple member IDs for an incompatible upgrade. As a best practice, specify half of the subordinate members if the member devices form a ring. Make sure the specified subordinate members are directly connected by physical links.
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 member devices.
· Sets the new images as the 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 flash:/feature1.bin. (In this example, the image is compatible with the running images.)
<Sysname> issu load file feature flash:/feature1.bin slot 2
This operation will delete the rollback point information for the previous upgrade and maybe get unsaved configuration lost. Continue? [Y/N]:Y
Verifying the file flash:/feature1.bin on slot 1...Done.
Copying file flash:/feature1.bin to slot2#flash:/feature1.bin......Done.
Verifying the file flash:/feature1.bin on slot 2...Done.
Identifying the upgrade methods….Done.
Upgrade summary according to following table:
flash:/feature1.bin
Running Version New Version
Test 0001015 Test 0001016
Slot Upgrade Way
2 Service Upgrade
Upgrading software images to compatible versions. Continue? [Y/N]:y
# Use the reboot method to upgrade member device 2 (a subordinate member) when the incremental upgrade method is recommended.
<Sysname> issu load file feature flash:/feature1.bin slot 2 reboot
This operation will delete the rollback point information for the previous upgrade and maybe get unsaved configuration lost. Continue? [Y/N]:Y
Verifying the file flash:/feature1.bin on slot 1...Done.
Copying file flash:/feature1.bin to slot2#flash:/feature1.bin......Done.
Verifying the file flash:/feature1.bin on slot 2...Done.
Identifying the upgrade methods….Done.
Upgrade summary according to following table:
flash:/feature1.bin
Running Version New Version
Test 0001015 Test 0001016
Slot Upgrade Way
2 Reboot
Upgrading software images to compatible versions. Continue? [Y/N]:y
# Upgrade member devices 3 and 4 (subordinate members) with feature image file flash:/feature1.bin. (In this example, the image is incompatible with the running images.)
<Sysname> issu load file feature flash:/feature1.bin slot 3 4
This operation will delete the rollback point information for the previous upgrade and maybe get unsaved configuration lost. Continue? [Y/N]:Y
Verifying the file flash:/feature1.bin on slot 1...Done.
Copying file flash:/feature1.bin to slot3#flash:/feature1.bin......Done.
Verifying the file flash:/feature1.bin on slot 3...Done.
Copying file flash:/feature1.bin to slot4#flash:/feature1.bin......Done.
Verifying the file flash:/feature1.bin on slot 4...Done.
Identifying the upgrade methods….Done.
Upgrade summary according to following table:
flash:/feature1.bin
Running Version New Version
Test 0001015 Test 0001016
Slot Upgrade Way
3 Reboot
4 Reboot
Table 7 Command output
|
Field |
Description |
|
Verifying the file |
The system was verifying the validity of the file. |
|
Copying file |
The system was copying the upgrade file to a subordinate member. This field is displayed if you specified a subordinate member 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 pex
Use issu pex to specify images used for PEX upgrade.
Syntax
issu pex pex-model file { boot filename | system filename | feature filename&<1-30> } *
issu pex pex-model file ipe ipe-filename
Views
User view
Predefined user roles
network-admin
Parameters
pex-model: Specifies the PEX model, a case-insensitive string of up to 63 characters. You must enter the complete PEX model name for the device to identify the PEX correctly. For available PEX models, enter boot-loader pex ?.
boot: Specifies a boot image file.
system: Specifies a system image file.
feature: Specifies a space-separated list of up to 30 feature image files.
filename: Specifies a .bin file in the filesystemname/filename.bin format. The file must be stored in the root directory of a file system on the device. The value string excluding the file system location section (if any) can have a maximum of 63 characters. For more information about specifying a file, see Fundamental Configuration Guide.
ipe ipe-filename: Specifies an .ipe file in the filesystemname/filename.ipe format. The file must be stored in the root directory of a file system on the device. The value string excluding the file system location section (if any) can have a maximum of 63 characters. For more information about specifying a file, see Fundamental Configuration Guide.
Usage guidelines
Use this command if you want to upgrade PEXs during an ISSU that uses issu commands.
This command only specifies images used for PEX upgrade. This command does not load the upgrade images. The PEXs will load the upgrade images when the parent devices are upgraded. For more information, see Fundamentals Configuration Guide.
You may upgrade all or some of the software images. If you are upgrading only some of the images, make sure the new images are compatible with the images that are not to be upgraded. The upgrade will fail if a conflict exists.
The system performs the following operations after verifying validity of the source file:
1. If you specify an .ipe file, the system automatically decompresses the .bin image files from the .ipe file to the same directory as the .ipe file.
2. Copies the .bin files to all PEXs of the specified model.
3. Displays a prompt for you to delete the following files:
¡ Source .ipe file (if any).
¡ Source .bin files if the .bin files are not on a PEX of the specified model.
Examples
# Specify flash:/devkit.bin as the image for upgrading S6300 PEXs.
<Sysname> issu pex PEX-S6300 file feature flash:/devkit.bin
Verifying the file flash:/devkit.bin on slot 1...Done.
File flash:/devkit.bin already exists on slot 110.
Overwrite the existing files? [Y/N]:Y
Copying file flash:/devkit.bin to slot110#flash:/devkit.bin...Done.
Delete flash:/devkit.bin from slot 1? [Y/N]:Y
# Specify flash:/test.ipe as the image source for upgrading S6300 PEXs.
<Sysname> issu pex PEX-S6300 file ipe flash:/test.ipe
Verifying the file flash:/test.ipe on slot 1...........Done.
Decompressing file devkit-patch.bin to flash:/devkit-patch.bin...Done.
Decompressing file manufacture.bin to flash:/manufacture.bin.....Done.
Copying file flash:/devkit-patch.bin to slot110#flash:/devkit-patch.bin...Done.
Copying file flash:/manufacture.bin to slot110#flash:/manufacture.bin...Done.
Delete flash:/devkit-patch.bin from slot 1? [Y/N]:Y
Delete flash:/manufacture.bin from slot 1? [Y/N]:Y
Delete flash:/test.ipe from slot 1? [Y/N]:Y
Related commands
issu load
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
Use this command on a multichassis IRF fabric.
· 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, causing the upgraded subordinate member to be elected as the new master.
· For an incompatible upgrade, the issu load command splits the IRF fabric into two fabrics, with the upgraded members forming a new fabric. The issu run switchover command reboots the members in the old IRF fabric with the upgrade images to upgrade the members. After startup, the members join the new IRF fabric as subordinate members.
At reboot, a subordinate device automatically synchronizes the master device's configuration and status data. You must wait for the synchronization to complete before using the issu run switchover command on the subordinate device. To identify whether the synchronization is complete, use the display system stable state command. The synchronization is complete if the System State field displays Stable.
Examples
# On a multichassis IRF fabric, perform a master/subordinate switchover during an ISSU to a compatible version.
<Sysname> issu run switchover
Upgrade summary according to following table:
flash:/feature1.bin
Running Version New Version
Test 0001015 Test 0001016
Slot Switchover Way
1 Active standby process switchover
Upgrading software images to compatible versions. Continue? [Y/N]:
# On a multichassis IRF fabric, perform a master/subordinate switchover, and upgrade members that have not been upgraded (member 1 and member 2) during an ISSU to an incompatible version.
<Sysname> issu run switchover
Copying file flash:/feature1.bin to slot2#flash:/feature1.bin...Done.
Verifying the file flash:/feature1.bin on slot 2...Done.
Upgrade summary according to following table:
flash:/feature1.bin
Running Version New Version
Test 0001015 Test 0001016
Slot Upgrade Way
1 Reboot
2 Reboot
Upgrading software images to incompatible versions. Continue? [Y/N]:
Table 8 Command output
|
Field |
Description |
|
Copying file |
The system was copying the upgrade file to a subordinate member. This field is displayed if you specified a subordinate member for the command during an incompatible upgrade. |
|
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. · Master subordinate switchover—Switch from the master to a subordinate member. |
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
