08-ISSU commands
Chapters Download (131.65 KB)
Use display install active to display active software images.
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.
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.
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 chassis 1 slot 1:
flash:/boot.bin
flash:/system.bin
flash:/patch1.bin
# Display detailed information about active software images.
<Sysname> display install active verbose
Active packages on chassis 1 slot 1:
flash:/boot.bin
[Package]
Vendor: H3C
Product: xxxx
Service name: boot
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu lpu
[Component]
Component: boot
Description: boot package
flash:/system.bin
[Package]
Vendor: H3C
Product: xxxx
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: xxxx
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. · sfc—Switching fabric module. |
|
[Component] |
Information about components included in the image file. |
Related commands
install active
Use display install backup to display backup startup software images.
Syntax
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.
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.
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
# 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
# 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: xxxx
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: xxxx
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: xxxx
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: xxxx
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
Use display install committed to display main startup software images.
Syntax
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.
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.
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 chassis 1 slot 1:
flash:/boot.bin
flash:/system.bin
flash:/patch1.bin
# 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: xxxx
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: xxxx
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: xxxx
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: xxxx
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: xxxx
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: xxxx
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
Use display install inactive to display inactive software images in the root directories of file systems.
Syntax
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.
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.
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 chassis 1 slot 1:
flash:/patch1.bin
Inactive packages on chassis 2 slot 1:
flash:/patch1.bin
# 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: xxxx
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: xxxx
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
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
# 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.
XX images in IPE:
boot.bin
system.bin
Related commands
display install package
Use display install job to display ongoing ISSU activate, deactivate, and rollback operations.
Syntax
display install job
Views
Any view
Predefined user roles
network-admin
network-operator
Examples
# Display ongoing ISSU activate, deactivate, and rollback operations.
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.
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
# 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.
# 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
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.
all: Specifies all software image files in the root directories of the file systems on the global active MPU.
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: xxxx
Service name: system
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu
# Display detailed information about system.bin.
<Sysname> display install package flash:/system.bin verbose
flash:/system.bin
[Package]
Vendor: H3C
Product: xxxx
Service name: system
Platform version: 7.1.070
Product version: Test 0001015
Supported board: mpu
[Component]
Component: system
Description: system package
For information about the command output, see Table 1.
Use display install rollback to display rollback point information.
Syntax
display install rollback [ point-id ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
point-id: Specifies a rollback point ID. If you do not specify a rollback point ID, the command displays all rollback points.
Usage guidelines
Use this command to identify available rollback points during an ISSU that uses install commands. The system does not record rollback points during an ISSU that uses issu commands.
Examples
# Display all rollback points.
<Sysname> display install rollback
Install rollback information 1 on chassis 1 slot 1
Updating from flash:/route-1.bin
to flash:/route-2.bin.
Install rollback information 2 on chassis 1 slot 1
Deactivating flash:/route-2.bin
The output shows that the device has two rollback points.
· At rollback point 1, flash:/route-1.bin was upgraded to flash:/route-2.bin.
· At rollback point 2, flash:/route-2.bin was deactivated.
Related commands
install rollback
reset install rollback oldest
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 } [ 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.
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.
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 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: xxxx
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. · sfc—Switching fabric module. |
Use display issu blade to display the image files to be used for security engines in the ISSU.
Syntax
display issu blade [ blade-model ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
blade-model: Specifies a security engine model that the device supports. For the device to identify the security engine correctly, you must enter the complete security engine model name. For available security engine models, enter display issu blade ?. This argument is case insensitive. If you do not specify this argument, the command displays the image files for all supported security engine models.
Usage guidelines
The image files will be used to upgrade security engines during an ISSU that uses issu commands.
Examples
# Display the image files to be used for security engines in the ISSU.
<Sysname> display issu blade
Issu software image files for BLADEs:
Blade model: Blade3fw
cfa0:/BLADE3FWM9000-CMW710-BOOT-E9140.bin
cfa0:/BLADE3FWM9000-CMW710-SYSTEM-E9140.bin
Blade model: Blade4fw
None
Related commands
issu blade
Use display issu pex to display the image files to be used for PEXs in the ISSU.
Syntax
display issu pex [ pex-model ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
pex-model: Specifies a PEX model that the device supports. For the device to identify the PEXs correctly, you must enter the complete PEX model name. For available PEX models, enter display issu pex ?. This argument is case insensitive. If you do not specify this argument, the command displays the image files for all supported PEX models.
Usage guidelines
The image files will be used to upgrade PEXs during an ISSU that uses issu commands.
Examples
# Display the image files to be used for PEXs in the ISSU.
<Sysname> display issu pex
Upgrade image files used to upgrade PEXs in the following ISSU steps:
PEX model: PEX-S5120HI
flash:/rpu-s5120hi-boot.bin
flash:/rpu-s5120hi-system.bin
PEX model: PEX-S5820
flash:/boot.bin
flash:/system.bin
Related commands
issu pex
Use display issu rollback-timer to display automatic rollback timer information.
Syntax
display issu rollback-timer
Views
Any view
Predefined user roles
network-admin
network-operator
Usage guidelines
Change to the automatic rollback interval does not take effect on the ongoing ISSU process. The current remaining rollback time might be greater than the specified automatic rollback interval.
Examples
# Display automatic rollback timer information after the issu run switchover command is executed.
<Sysname> display issu rollback-timer
Rollback timer: Working
Rollback interval: 45 minutes
Rollback time remaining : 40 minutes
# Display automatic rollback timer information after the issu accept command is executed.
<Sysname> display issu rollback-timer
Rollback timer: Not working
Rollback interval: 30 minutes
# Display automatic rollback timer information when no ISSU process is taking place.
<Sysname> display issu rollback-timer
Rollback timer: Not working
Rollback interval: 45 minutes
Related commands
issu rollback-timer
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
# 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
# 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
# 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
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. · Rollbacking—A rollback is in progress. · 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. |
|
Upgraded slot |
Upgraded cards. During a rollback, this field displays Unknown. |
|
Current upgrading slot |
Cards that are being upgraded. During a rollback, this field displays Unknown. |
|
Upgraded chassis |
Upgraded members. This field is available in IRF mode. During a rollback, this field displays Unknown. |
|
Current upgrading chassis |
Members that are being upgraded. During a rollback, this field displays Unknown. This field is available on single-chassis IRF fabrics. |
|
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
issu rollback
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.
On a device installed with security engines, use the issu blade command to specify the images used for security engine upgrade before using this command.
If one or more images are incompatible, the incompatible upgrade method applies. The entire system needs to be rebooted during an incompatible upgrade.
Examples
|
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. · ISSU Reboot. · Reboot. · Sequence Reboot. This field is displayed only for compatible versions. For more information about ISSU methods, see Fundamentals Configuration Guide. |
Related commands
issu load
Use issu accept to accept the upgrade to a compatible version and delete the automatic rollback timer.
Syntax
issu accept
Views
User view
Predefined user roles
network-admin
Usage guidelines
The system cannot perform automatic rollback for the ISSU process after you execute this command. However, you can use the issu rollback command to perform a manual rollback.
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
Use issu blade to specify images used for security engine upgrade.
Syntax
issu blade blade-model file { boot filename | system filename | feature filename&<1-30> } *
issu blade blade-model file ipe ipe-filename
Views
User view
Predefined user roles
network-admin
Parameters
blade-model: Specifies the security engine model. You must enter the complete security engine model name for the device to identify the security engine correctly. For available security engine models, enter boot-loader blade ?.
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 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.
Usage guidelines
Use this command if you want to upgrade security engines during an ISSU that uses issu commands.
This command sets software images for all security engines of the specified model. After verifying validity of the source file, the system performs the following operations:
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 security engines 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 security engine of the specified model.
This command only specifies images used for security engine upgrade. This command does not load the upgrade images. The security engines will load the upgrade images when the MPUs 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.
Examples
# Specify flash:/test.bin as the upgrade image for the Blade-m9k security engine.
<Sysname> issu blade Blade-m9k file feature flash:/test.bin
Verifying the file flash:/test.bin on slot 0...Done.
File cfa0:/test.bin already exists on slot 2.1.
Overwrite the existing files? [Y/N]:Y
Copying file flash:/test.bin to slot2.1#cfa0:/test.bin...Done.
File cfa0:/test.bin already exists on slot 3.1.
Overwrite the existing files? [Y/N]:Y
Copying file flash:/test.bin to slot3.1#cfa0:/test.bin...Done.
Delete flash:/test.bin from slot 0? [Y/N]:N
The images will be used as the issu images at the next issu on the device.
# Specify slot2.1#cfa0:/test.bin as the upgrade image for the Blade-m9k security engine.
<Sysname> issu blade Blade-m9k file feature slot2.1#cfa0:/test.bin
Verifying the file cfa0:/test.bin on slot 2.1...Done.
File cfa0:/test.bin already exists on slot 3.1.
Overwrite the existing files? [Y/N]:Y
Copying file cfa0:/test.bin to slot3.1#cfa0:/test.bin...Done.
Delete flash:/test.bin from slot 0? [Y/N]:N.
The images will be used as the issu images at the next issu on the device.
# Specify flash:/test.ipe as the upgrade image for the Blade-m9k security engine.
<Sysname> issu blade Blade-m9k file ipe flash:/test.ipe
Verifying the file flash:/test.ipe on slot 0...Done.
File flash:/blade3fwm9k-cmw710-test-a0002.bin already exists on slot 0.
Overwrite the existing files? [Y/N]:Y
Decompressing file blade3fwm9k-cmw710-test-a0002.bin to flash:/blade3fwm9k-cmw710-test-a0002.bin...Done.
File cfa0:/blade3fwm9k-cmw710-test-a0002.bin already exists on slot 2.1.
Overwrite the existing files? [Y/N]:Y
Copying file flash:/blade3fwm9k-cmw710-test-a0002.bin to slot2.1#cfa0:/blade3fwm9k-cmw710-test-a0002.bin...Done.
File cfa0:/blade3fwm9k-cmw710-test-a0002.bin already exists on slot 3.1.
Overwrite the existing files? [Y/N]:N
Delete flash:/blade3fwm9k-cmw710-test-a0002.bin from slot 0? [Y/N]:N
Delete flash:/test.ipe from slot 0? [Y/N]:N
The images will be used as the issu images at the next issu on the device.
Related commands
issu load
Use issu commit to upgrade the original active MPU to a compatible version and complete the ISSU.
(On a dual-MPU single-chassis IRF fabric.) Use issu commit to upgrade the original active MPU to a compatible version and complete the ISSU.
(On a multichassis IRF fabric.) Use issu commit to upgrade the original master and the subordinate members that have not been upgraded and complete the ISSU upgrade.
Syntax
In IRF mode (single-chassis):
issu commit chassis chassis-number slot slot-number
In IRF mode (multichassis):
issu commit chassis chassis-number
Views
User view
Predefined user roles
network-admin
Parameters
chassis chassis-number slot slot-number: Specifies the member ID and slot number of the original active MPU. (On a single-chassis IRF fabric.)
chassis chassis-number: Specifies the member ID of the original master or a subordinate member that has not been upgraded. (On a multichassis IRF fabric.)
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.
On a dual-MPU single-member IRF fabric, this command ends the ISSU process. When this command is completed, the ISSU status changes to Init, and the ISSU process cannot be rolled back.
On a multichassis IRF fabric, use this command to upgrade the original master and the subordinate members that have not been upgraded, one by one. After all members are upgraded, the ISSU status changes to Init, and the ISSU process ends and cannot be rolled back. You must wait for one upgraded subordinate member to start up again and join the IRF fabric before upgrading another subordinate member.
Examples
# 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.
# Upgrade the original active MPU to a compatible version. (In this example, the IRF fabric has a single member and the member has two MPUs.)
<Sysname> issu commit chassis 1 slot 0
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
Upgrading software images to compatible versions. Continue? [Y/N]:y
This operation might take several minutes, please wait...Done.
# Finish the upgrade to a compatible version. (In this example, the IRF fabric has a single member and the member has only one MPU.)
<Sysname> issu commit chassis 1 slot 0
For information about the command output, see Table 5.
Related commands
issu accept
issu load
issu run switchover
(On a single-chassis IRF fabric.) Use issu load to upgrade the standby MPU and configure the new images as main startup software images for the MPU.
(On a multichassis IRF fabric.) Use issu load to upgrade subordinate members and configure the new images as main startup software images for those members.
Syntax
In IRF mode (single-chassis):
issu load file { boot filename | system filename | feature filename&<1-30> } * chassis chassis-number slot slot-number [ reboot ]
issu load file ipe ipe-filename chassis chassis-number slot slot-number [ reboot ]
In IRF mode (multichassis):
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 global active MPU. 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 global active MPU. 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.
slot slot-number: Specifies the slot number of the standby MPU. If the device has only one MPU, enter the slot number of the MPU to upgrade the entire device.
chassis chassis-number slot slot-number: Specifies the member ID and slot number of the standby MPU. If the member has only one MPU, enter the member ID and slot number of the MPU to upgrade the entire fabric. (On a single-chassis IRF fabric.)
chassis chassis-number: Specifies the member ID of a subordinate member. For a compatible upgrade, you can specify only one member ID. For an incompatible upgrade, you can specify a space-separated list of up to three member IDs. (On a multichassis IRF fabric.)
reboot: Uses the reboot method for the upgrade. For an incremental upgrade or ISSU reboot 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.
(On a single-chassis IRF fabric.)This command performs the following operations:
· Checks the version compatibility.
· Identifies the upgrade method.
· Loads the new images to upgrade the specified MPU.
· Sets the new images as the main startup software images for the specified MPU so the upgrade can survive a reboot.
(Multichassis IRF fabric.) 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
# 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 6 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 the standby MPU. This field is displayed if you specified the standby MPU for the command. 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. · ISSU Reboot. · Reboot. · Sequence Reboot. This field is displayed only for an upgrade to a compatible version. For more information about ISSU methods, see Fundamentals Configuration Guide. |
Use issu rollback to cancel the ISSU and roll back to the original software versions.
Syntax
issu rollback
Views
User view
Predefined user roles
network-admin
The device supports automatic rollback and manual rollback. This command performs a manual rollback.
You can perform a manual rollback while an ISSU is in one of the following states:
· Loaded.
· Switching (during an upgrade to a compatible version).
· Switchover (during an upgrade to a compatible version).
· Accepted.
If the ISSU is in Loading state, the rollback might fail. Use the display version command to examine the rollback result after the rollback is completed.
If a rollback occurs while an ISSU is in Switching state, the entire system reboots automatically.
A rollback performed for a multichassis IRF fabric after you execute the issu run switchover command cancels only the upgrades. The master/subordinate switchover operation is not canceled.
Examples
# Roll back to the original software versions.
<Sysname> issu rollback
This command will quit the ISSU process and roll back to the previous version. Continue? [Y/N]:y
Related commands
issu accept
issu commit
issu load
issu run switchover
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 only available during an ISSU to a compatible version in the following scenarios:
· An IRF fabric has multiple members.
· A single-chassis IRF fabric has two MPUs.
The system starts the automatic rollback timer when you execute the issu run switchover command in a scenario where automatic rollback is supported. If you do not execute the issu accept or issu commit command before the timer expires, the system automatically rolls back to the software version used before the ISSU.
Change to the automatic rollback interval does not take effect on the ongoing ISSU process.
Examples
# Set the automatic rollback timer to 50 minutes.
<Sysname> system-view
[Sysname] issu rollback-timer 50
Related commands
issu rollback
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 only on a multichassis IRF fabric or a dual-MPU single-member IRF fabric.
· (On a dual-MPU single-chassis IRF fabric.) 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 active/standby switchover for the processes to be upgraded, and upgrades the LPUs and switching fabric modules.
- Reboot upgrade or ISSU upgrade—Reboots the current active MPU with the old software version and upgrades the LPUs and switching fabric modules. The upgraded MPU then becomes the new active MPU.
¡ For an incompatible upgrade, this command reboots the current active MPU, the LPUs, and the switching fabric modules to use the new software version. After the reboot, the following operations take place in turn:
- The upgraded MPU becomes the new active MPU.
- The original active MPU, the LPUs, and the switching fabric modules are upgraded.
- The ISSU process ends.
· (On a multichassis IRF fabric.) 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 or ISSU upgrade—Reboots the current master with the old software version to cause the upgraded subordinate member to become the new master.
¡ For an incompatible 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.
When you execute the issu run switchover command during an ISSU to a compatible version, the system starts the automatic rollback timer. If you do not execute the issu accept or issu commit command before the timer expires, the system automatically rolls back to the original software versions.
During a reboot upgrade to a compatible version, the LPUs and switching fabric modules reboot to load the new software from the upgraded MPU. A transient service outage occurs on the cards.
Examples
# 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 7 Command output
|
Field |
Description |
|
Switchover Way |
Switchover method: · Active standby process switchover—Switch from the active process to the standby process. · Active standby MPU switchover—Switch from the active MPU to the standby MPU. · 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
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
Use reset install rollback oldest to clear ISSU rollback points.
Syntax
reset install rollback oldest point-id
Views
User view
Predefined user roles
network-admin
Parameters
point-id: Specifies a rollback point by its ID.
Usage guidelines
This command clears the specified rollback point and all rollback points older than the specified rollback point.
Examples
# Clear rollback point 2 and all rollback points older than rollback point 2.
<Sysname> reset install rollback oldest 2
Related commands
display install rollback
