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-Password recovery control command
- 12-Python commands
- 13-License management commands
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 08-ISSU commands | 132.11 KB |
ISSU commands
display install active
Use display install active to display active software images.
Syntax
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:/feature.bin
# Display detailed information about active software images.
Active packages on slot 1:
flash:/BOOT-test.bin
[Package]
Vendor: H3C
Product: S7500EXS
Service name: boot
Platform version: 7.1.045
Product version: Beta 7176P01
Supported board: mpu
[Component]
Component: boot
Description: boot package
flash:/SYSTEM-test.bin
[Package]
Vendor: H3C
Product: S7500EXS
Service name: system
Platform version: 7.1.045
Product version: Beta 7176P01
Supported board: mpu
[Component]
Component: system
Description: system package
|
Field |
Description |
|
Active packages on xxx |
Active software images on the specified slot. |
|
[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 |
Device types supported by the software image. The value is fixed at mpu. This value represents member devices. |
|
[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 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 all PEXs with storage media 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
Backup startup images are used only when the main boot or system image is missing or corrupt. For more information, see Fundamental Configuration Guide.
To modify the backup startup image list, you must use the boot-loader file command.
Examples
# Display the backup startup software images.
<Sysname> display install backup
Backup startup software images on slot 1:
flash:/boot-test.bin
flash:/system-test.bin
# Display detailed information about backup startup software images.
<Sysname> display install backup verbose
Backup startup software images on slot 1:
flash:/boot-test.bin
[Package]
Vendor: H3C
Product: S7500EXS
Service name: boot
Platform version: 7.1.045
Product version: Beta 7176P01
Supported board: mpu
[Component]
Component: boot
Description: boot package
flash:/system-test.bin
[Package]
Vendor: H3C
Product: S7500EXS
Service name: system
Platform version: 7.1.045
Product version: Beta 7176P01
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
After you execute the install commit command, use the display install committed command to verify that the main startup image list has been updated with the software image change.
Both the install commit and boot-loader file commands modify the main startup software image list.
Examples
# Display the main startup software images.
<Sysname> display install committed
Committed packages on slot 1:
flash:/ BOOT-test.bin
flash:/ SYSTEM-test.bin
# Display detailed information about main startup software images.
<Sysname> display install committed verbose
Committed packages on slot 1:
flash:/BOOT-test.bin
[Package]
Vendor: H3C
Product: S7500EXS
Service name: boot
Platform version: 7.1.045
Product version: Beta 7176P01
Supported board: mpu
[Component]
Component: boot
Description: boot package
flash:/SYSTEM-test.bin
[Package]
Vendor: H3C
Product: S7500EXS
Service name: system
Platform version: 7.1.045
Product version: Beta 7176P01
Supported board: mpu
[Component]
Component: system
Description: system package
For information about the command output, see Table 1.
Related commands
· boot-loader file
· display install backup
· install commit
display install inactive
Use display install inactive to display inactive software images.
Syntax
display install inactive [ slot slot-number ] [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
slot slot-number: Specifies an IRF member device by its member ID 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
This command displays inactive images in the root directories of the storage media.
Examples
# Display brief information about inactive software images in the root directories of the storage media.
<Sysname> display install inactive
Inactive packages on slot 1:
flash:/ssh-feature.bin
# Display detailed information about inactive software images in the root directories of the storage media.
<Sysname> display install inactive verbose
Inactive packages on slot 1:
flash:/ssh-feature.bin
[Package]
Vendor: H3C
Product: XXXX
Service name: ssh
Platform version: 7.1.045
Product version: Beta 7176P01
Supported board: mpu
[Component]
Component: ssh
Description: ssh package
For information about the command output, see Table 1.
Related commands
install deactivate
display install ipe-info
Use display install ipe-info to display the software images included in an .ipe file.
Syntax
display install ipe-info ipe-filename
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
ipe-filename: Specifies the file path of an .ipe image package file, a case-insensitive string. The file must be stored in the root directory of a storage medium on a member device. The maximum length is 1 to 63 characters for the storage-medium:/base-filename.ipe segments of the file path. This length limit does not include the IRF member ID segment in front of the storage medium segment. For more information about specifying a file path, see "Managing the file system."
Examples
# Display information about the .ipe file flash:/test.ipe.
<Sysname> display install ipe-info flash:/test.ipe
Verifying the file flash:/test.ipe on slot 1.....Done.
H3C Device 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:/ssh-feature.bin on slot 1
The output shows that the device is executing the install activate flash:/ssh-feature.bin slot 1 command.
display install log
Use display install log to display ISSU log information.
Syntax
display install log [ 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 software upgrade-related 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 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 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.
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:/ssh.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.
Related commands
reset install log-history oldest
display install package
Use display install package to display software image file information.
Syntax
display install package { filename | all } [ verbose ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
filename: Specifies the file path of a .bin software image file, a case-insensitive string. The file must be stored in the root directory of a storage medium on a member device. The maximum length is 1 to 63 characters for the storage-medium:/base-filename.ipe segments of the file path. This length limit does not include the IRF member ID segment in front of the storage medium segment. For more information about specifying a file path, see "Managing the file system."
all: Specifies all software image files in the root directories of the storage media on the master.
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.045
Product version: Beta 7176P01
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.045
Product version: Beta 7176P01
Supported board: mpu
[Component]
Component: system
Description: system package
For more 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 name in base-filename.extension format, a case-insensitive string of 1 to 63 characters. It cannot contain path information.
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.
Usage guidelines
A component is a collection of features. The features of a component are installed or uninstalled at the same time.
When the system displays a component or file error, use this command to identify the relevant image files before you make a software upgrade decision.
This command searches only the root directory of the storage medium.
Examples
# Display all software image files that include sshc.cli.
<Sysname> display install which file sshc.cli
File sshc.cli is in following packages on slot 1:
Verifying the file flash:/system.bin on slot 1...Done.
Verifying the file flash:/boot.bin on slot 1...Done.
flash:/system.bin
[Package]
Vendor: xxx
Product: xxxx
Service name: ssh
Platform version: 7.1.045
Product version: Beta 7176P01
Supported board: mpu
Table 2 Command output
|
Field |
Description |
|
Verifying the file |
The system was verifying the validity of the file. |
For more information about other fields in the command output, see Table 1.
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.045, Beta 7176P01
system: 7.1.045, Beta 7176P01
Current software images:
flash:/BOOT-test.bin
flash:/SYSTEM-test.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.045, Beta 7176P01
system: 7.1.045, Beta 7176P01
Previous software images:
flash:/boot.bin
flash:/system.bin
Upgrade version list:
boot: 7.1.045, Beta 7176P02
system: 7.1.045, Beta 7176P02
Upgrade software images:
flash:/BOOT-test.bin
flash:/SYSTEM-test.bin
Table 3 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. |
|
Compatibility |
Version compatibility: · Compatible. · Incompatible. · Unknown—No upgrade is in process. |
|
Work state |
Operating state of the device: · Normal—The device is operating correctly. · Independent active—When you perform an ISSU for an incompatible version, member devices that are first upgraded enter this state. In this state, member devices in the IRF fabric are not running the same software versions. |
|
Upgrade method |
Upgrade mode. The value can be Card by card. The member devices are upgraded one by one. |
|
Previous version list |
Software versions running on the device before the ISSU. |
|
Previous software images |
Software images running on the device before the ISSU. |
|
Upgrade version list |
Software versions to upgrade to. |
|
Upgrade software images |
Software images used for the upgrade. |
Related commands
· issu accept
· issu commit
· issu load
· issu run switchover
display version comp-matrix
Use display version comp-matrix to display version compatibility information and identify the upgrade method.
Syntax
display version comp-matrix
display version comp-matrix file { boot filename | system filename | feature filename&<1-30> } *
display version comp-matrix file ipe ipe-filename
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
boot: Specifies a boot image file.
system: Specifies a system image file.
feature: Specifies feature image files. You can specify a space-separated list of up to 30 feature image files.
filename: Specifies the name of a software image file on the master, in the format storage-medium:/base-filename.bin. It must be a case-insensitive string of 1 to 63 characters and cannot contain slot information.
ipe ipe-filename: Specifies the name of an .ipe file on the master, in the format storage-medium:/base-filename.ipe. It must be a case-insensitive string of 1 to 63 characters and cannot contain slot information.
Usage guidelines
On an IRF 3 system, 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 file names, 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.
Examples
# Display compatibility information for the running images.
<Sysname> display version comp-matrix
Boot image: flash:/cmw710-boot-test.bin
Version:
7.1.045
System image: flash:/cmw710-system-test.bin
Version:
V700R001B45D001
Version compatibility list:
V700R001B45D001
Version dependency boot list:
7.1.045
# Display compatibility information for flash:/boot-e2205.bin and flash:/system-e2205.bin, as well as the recommended ISSU method. (In this example, the specified images are incompatible with the running images.)
<Sysname> display version comp-matrix file boot flash:/boot-e2205.bin system flash:/system-e2205.bin
Verifying the file flash:/boot-e2205.bin on slot 1............Done.
Verifying the file flash:/system-e2205.bin on slot 1............Done.
Boot image: flash:/boot-e2205.bin
Version:
7.1.045
System image: flash:/system-e2205.bin
Version:
V200R001B45D012
Version compatibility list:
V200R001B45D012
Version dependency boot list:
7.1.045
Incompatible upgrade.
# Display compatibility information for cmw710-cfa-test.bin and the recommended ISSU methods. (In this example, the specified image is compatible with the running images.)
<Sysname> display version comp-matrix file feature flash:/cmw710-cfa-test.bin
Verifying the file flash:/boot-e2205.bin system on slot 1............Done.
Feature image: flash:/cmw710-cfa-test.bin
Version:
V700R001B45D002
Version compatibility list:
V700R001B45D001
V700R001B45D002
Version dependency system list:
V700R001B45D001
V700R001B45D002
Slot Upgrade Way
1 Service Upgrade
2 Service Upgrade
Influenced service according to following table on slot 1:
flash:/cmw710-cfa-a7125.bin
CFA
Influenced service according to following table on slot 2:
flash:/cmw710-cfa-a7125.bin
CFA
# 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:/cmw710-boot-test.bin
Version:
7.1.045
System image: flash:/cmw710-system-test.bin
Version:
D2404001
Version compatibility list:
D2404001
Version dependency boot list:
7.1.045
Compatible info of S5120HI:
Boot image: flash:/rpu-s5120hi-boot.bin
Version:
7.1.045
System image: flash:/rpu-s5120hi-system.bin
Version:
T2206
Version compatibility list:
T2206
Version dependency boot list:
7.1.045
# Display the following information:
· Compatibility information for the upgrade images used for parent device upgrade.
· Compatibility information for the upgrade images used for S6300HI PEX upgrade.
· Recommended ISSU methods for the upgrades.
In this example, the specified images are incompatible with the running images.
<Sysname> issu pex PEX-S6300HI file feature flash:/s6300hi-http-d2403.bin
Verifying the file flash:/s6300hi-http-d2403.bin on slot 1.....Done.
Copying file flash:/s6300hi-http-d2403.bin to slot1#flash:/s6300hi-http-d2403.bin...Done.
<Sysname> display version comp-matrix file feature flash:/cmw710-cfa-a0041.bin
Verifying the file flash:/cmw710-cfa-a0041.bin system on slot 1............Done.
Verifying the file flash:/s6300hi-http-d2403.bin on slot 1.....Done.
Feature image: flash:/cmw710-cfa-a0041.bin
Version:
A0042
Version compatibility list:
A0041
A0042
Version dependency system list:
A0041
Compatible info of S6300HI:
Feature image: flash:/s6300hi-http-d2403.bin
Version:
D2403
Version compatibility list:
D2402
D2403
Version dependency system list:
D2402
Slot Upgrade Way
6 Service Upgrade
101 Service Upgrade
Influenced service according to following table on slot 1:
flash:/cmw710-cfa-a7122.bin
CFA
Influenced service according to following table on slot 101:
flash:/cmw710-cfa-a7122.bin
HTTP
|
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 S6300HI: |
Compatibility information for the PEXs. |
|
Influenced service according to following table |
Services that will be affected by the upgrade. This field is displayed only for compatible versions. |
|
Incompatible upgrade |
You are upgrading the software to an incompatible version. |
|
Slot |
Member ID of the member device. This field is displayed only for compatible versions. |
|
Upgrade Way |
ISSU method to be used for a compatible version: · Service Upgrade—Service-level incremental upgrade. · File Upgrade—File-level incremental upgrade. · Reboot—Upgrades software by rebooting both data and control planes. This method disrupts services. 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 ISSU operation.
Syntax
install abort [ job-id ]
Views
User view
Predefined user roles
network-admin
Parameters
job-id: Specifies the job ID of an ISSU operation. If you do not specify this argument, the command aborts all ongoing software image activate and deactivate operations.
Usage guidelines
The system creates a software image management job each time you use the install activate, install add, install commit, install deactivate, or install remove command. Each job represents one command and is assigned a unique job ID. You can abort only ongoing activate and deactivate operations.
To obtain the ID of a job, use the display install job command.
Examples
# Abort a software image operation.
<Sysname> install abort
Related commands
display install job
install activate
Use install activate to activate software images, or identify the ISSU method and 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.
system: Specifies a system image file.
feature: Specifies feature image files. You can specify a space-separated list of up to 30 feature image files.
patch: Specifies a patch image file.
filename: Specifies the file path of a .bin software image file. The file must be stored in the root directory of a storage medium on the master. If the storage medium is partitioned, the files must be saved in the root directory of the first partition. The value must be a case-insensitive string of 1 to 63 characters and cannot contain slot information.
all: Specifies all IRF member devices and all 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.
Usage guidelines
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 you specify a subordinate member for the command, the command copies the upgrade 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 check the synchronization progress, use the display device command. The synchronization is completed if all member devices are in normal state.
Examples
# Identify the ISSU method for feature upgrade with ssh2.bin on member device 2 as well as the upgrade impact.
<Sysname> install activate feature flash:/ssh2.bin slot 2 test
Copying file flash:/ssh2.bin to slot2#flash:/ssh2.bin......Done.
Verifying the file flash:/ssh2.bin on slot 2.....Done.
Upgrade summary according to following table:
flash:/ssh2.bin
Running Version New Version
Alpha 7122 Alpha 7123
Slot Upgrade Way
2 Service Upgrade
Influenced service according to following table:
flash:/ssh2.bin
SSH IFMGR CFA LAGG
The output shows that a service upgrade is recommended. The SSH, IFMGR, CFA, and LAGG modules will be rebooted during the upgrade.
# Activate the system image in system.bin and the feature images in feature.bin on member device 2.
<Sysname> install activate system flash:/system.bin feature flash:/feature.bin slot 2
Copying file flash:/system.bin to slot2#flash:/system.bin......Done.
Verifying the file flash:/system.bin on slot 2.....Done.
Copying file flash:/feature.bin to slot2#flash:/feature.bin......Done.
Verifying the file flash:/feature.bin on slot 2.....Done.
Upgrade summary according to following table:
flash:/system.bin
Running Version New Version
Alpha 7122 Alpha 7123
flash:/feature.bin
Running Version New Version
None Alpha 7122
Slot Upgrade Way
2 Service Upgrade
Upgrading software images to compatible versions. Continue? [Y/N]:y
This operation maybe take several minutes, please wait.......................................................................Done.
Table 5 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. |
|
Slot |
Member ID of the member device. |
|
Upgrade Way |
ISSU methods: · Service Upgrade—Service-level incremental upgrade. · File Upgrade—File-level incremental upgrade. The upgrade involves only hidden program files and does not affect the operation of the system or services. · Reboot—Upgrading software by rebooting both data and control planes. This method disrupts services. This field is displayed only for an upgrade to a compatible version. |
|
Influenced service according to following table |
Services influenced by the upgrade. |
Related commands
· display install active
· install commit
· install deactivate
install add
Use install add to decompress an .ipe file.
Syntax
install add ipe-filename medium-name:
Views
User view
Predefined user roles
network-admin
Parameters
ipe-filename: Specifies the file path of an .ipe image package file. The file must be stored in the root directory of a storage medium on the master. If the storage medium is partitioned, the files must be saved in the root directory of the first partition. The value must be a case-insensitive string of 1 to 63 characters and cannot contain slot information.
medium-name: Specifies the name of the destination storage medium for the software images.
· To specify the flash memory on the master, specify only the storage medium, for example, flash.
· To specify the flash memory on a subordinate member, use the format slotslot-number#storage-medium.
Usage guidelines
To use install commands for upgrade, you must use .bin image files. If the upgrade file is an .ipe file, use this command to decompress the .ipe file before you start the upgrade.
To identify software images that are included in an .ipe file, use the display install ipe-info command.
Examples
# Decompress all.ipe to the 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 revises the main startup software image list to be the same as the committed image list. Software changes take effect at the next startup.
You must execute this command after using the following commands:
· The install activate command in an incremental upgrade.
· The install deactivate command.
In a reboot upgrade, the install activate command revises both the current and startup software image lists. You do not need to commit software changes.
Both the install commit and boot-loader file commands change main startup software images. To change backup startup images or add inactive images as main startup images, however, you must use the boot-loader file command.
For more information about main and backup startup software images, see Fundamental Configuration Guide.
Examples
# Commit software changes.
<Sysname> install commit
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 feature image files. You can specify a space-separated list of up to 30 feature image files.
patch: Specifies a patch image file.
filename: Specifies the file path of a .bin software image file on the target slot, a case-insensitive string of 1 to 63 characters in the storage-medium:/base-filename.bin format. The file must be stored in the root directory of a storage medium on the master. The file path cannot include slot information.
all: Specifies all IRF member devices and all PEXs.
slot slot-number: Specifies an IRF member device by its member ID or specifies a PEX by its virtual slot number.
Usage guidelines
You can deactivate only active feature and patch images.
To prevent deactivated images from running after a reboot, you must commit the software changes by using the install commit command.
At reboot, a subordinate device automatically synchronizes the master device's configuration and status data. You must wait for the synchronization to complete before using the install deactivate command on the subordinate device. To check the synchronization progress, use the display device command. The synchronization is completed if all member devices are in normal state.
Examples
# Deactivate the patch images in route-patch.bin on member device 1.
<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 inactive software images.
Syntax
install remove [ slot slot-number ] { filename | inactive }
Views
User view
Predefined user roles
network-admin
Parameters
slot slot-number: Specifies an IRF member device by its member ID or specifies a PEX 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 IRF member devices and PEXs if you do not specify an IRF member device or PEX.
filename: Specifies the file path of a .bin software image file on the target slot, a case-insensitive string of 1 to 63 characters in the storage-medium:/base-filename.bin. The file must be stored in the root directory of a storage medium on the master. The file path cannot include slot information.
inactive: Deletes all inactive software image files in the root directories of the specified storage media.
Usage guidelines
This command permanently deletes the software image file from the device. You cannot use the install abort command to abort the operation.
Examples
# Delete inactive software image file flash:/ssh-feature.bin.
<Sysname> install remove flash:/ssh-feature.bin
install verify
Use install verify to verify the software change confirmation status and software image integrity and consistency.
Syntax
install verify
Views
User view
Predefined user roles
network-admin
Usage guidelines
If some software images are not integral or some activated/deactivated software images are not confirmed, the following problems might occur:
· A switchover might not occur as expected.
· The IRF members might run software images of different versions after a reboot or even cannot reboot correctly.
To solve the problems, perform one of the following tasks:
· Download and install the software images again to ensure software integrity.
· Use the install activate, install deactivate, and install commit commands as appropriate to guarantee software image consistency.
Examples
# Verify the software change confirmation status and software image integrity and consistency.
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.bin on slot 1.........
..Done.
flash:/Boot.bin verification successful.
Verifying the file flash:/System.bin on slot 1.......
................................................................................
..Done.
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
You can execute the issu commit command to finish the ISSU process without executing this command.
The issu accept command does not apply to the ISSU to an incompatible version. The system will display an error message if you execute this command during this type of ISSU.
Examples
# Accept the upgrade to a compatible version.
<Sysname> issu accept
Related commands
· issu load
· issu run switchover
issu commit
Use issu commit to upgrade 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
To use this command to upgrade multiple members, 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 and cannot be rolled back.
At reboot, a subordinate device automatically synchronizes the master device's configuration and status data. You must wait for the synchronization to complete before using the issu commit command on the subordinate device. To check the synchronization progress, use the display device command. The synchronization is completed if all member devices are in normal state.
Examples
# After member 2 is upgraded and becomes the new master, upgrade the original master (member 3) and the other subordinate members that have not been upgraded (member 4 and member 1).
Upgrade summary according to following table:
flash:/feature.bin
Running Version New Version
Alpha 7122 Alpha 7123
Slot Upgrade Way
3 Service Upgrade
Upgrading software images to compatible versions. Continue? [Y/N]:y
<Sysname> issu commit slot 4
Copying file flash:/feature.bin to slot4#flash:/feature.bin...Done.
Upgrade summary according to following table:
flash:/feature.bin
Running Version New Version
Alpha 7122 Alpha 7123
Slot Upgrade Way
4 Service Upgrade
Upgrading software images to compatible versions. Continue? [Y/N]:y
<Sysname> issu commit slot 1
Copying file flash:/feature.bin to slot1#flash:/feature.bin...Done.
Upgrade summary according to following table:
flash:/feature.bin
Running Version New Version
Alpha 7122 Alpha 7123
Slot Upgrade Way
1 Service Upgrade
Upgrading software images to compatible versions. Continue? [Y/N]:y
For information about the command output, see Table 4.
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>
issu load file ipe ipe-filename slot slot-number&<1-9>
Views
User view
Predefined user roles
network-admin
Parameters
boot: Specifies a boot image file.
system: Specifies a system image file.
feature: Specifies feature image files. You can specify a space-separated list of up to 30 feature image files.
filename: Specifies the file path of a .bin software image file, a case-insensitive string of 1 to 63 characters in the storage-medium:/base-filename.bin format. The file must be stored in the root directory of a storage medium on the master. If the storage medium is partitioned, the files must be saved in the root directory of the first partition. The file path cannot include slot information.
ipe ipe-filename: Specifies the file path of an .ipe file, a case-insensitive string of 1 to 63 characters in the format storage-medium:/base-filename.ipe. The file must be stored in the root directory of a storage medium on the master. If the storage medium is partitioned, the files must be saved in the root directory of the first partition. The file path cannot include slot information.
slot slot-number: Specifies the member ID of a subordinate member. You can specify a space-separated list of up to nine member IDs. If the IRF fabric has only one member, enter the member ID of this member to upgrade the entire fabric. 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.
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.
For successful upgrade, use the display device command to verify that all member devices are in normal state.
On a single-chassis IRF fabric, this command performs the following operations:
· Check the version compatibility.
· Identify the upgrade method.
· Load the new images to upgrade the member device.
· Set the new images as the main startup software images so the upgrade can survive a reboot.
On a multichassis IRF fabric, this command performs the following operations:
· Check the version compatibility.
· Identify the upgrade method.
· Load the new images to upgrade the specified member devices.
· Set the new images as the main startup software images for the specified member devices so the upgrade can survive a reboot.
Examples
# Upgrade member device 2 (a subordinate member) with the feature image file flash:/feature.bin. (In this example, the image is compatible with the running images.)
<Sysname> issu load file feature flash:/feature.bin slot 2
This operation will delete the rollback point information for the previous upgrade and maybe get unsaved configuration lost. Continue? [Y/N]:Y
Copying file flash:/feature.bin to slot2#flash:/feature.bin......Done.
Upgrade summary according to following table:
flash:/feature.bin
Running Version New Version
Alpha 7122 Alpha 7123
Slot Upgrade Way
2 Service Upgrade
Upgrading software images to compatible versions. Continue? [Y/N]:y
# Upgrade member devices 3 and 4 (subordinate members) with the feature image file flash:/feature.bin. (In this example, the image is incompatible with the running images.)
<Sysname> issu load file feature flash:/feature.bin slot 3 4
This operation will delete the rollback point information for the previous upgrade and maybe get unsaved configuration lost. Continue? [Y/N]:Y
Copying file flash:/feature.bin to slot3#flash:/feature.bin......Done.
Copying file flash:/feature.bin to slot4#flash:/feature.bin......Done.
Upgrade summary according to following table:
flash:/feature.bin
Running Version New Version
Alpha 7122 Alpha 7123
Slot Upgrade Way
3 Reboot
4 Reboot
Upgrading software images to incompatible versions. Continue? [Y/N]:y
Table 6 Command output
|
Field |
Description |
|
Verifying the file |
The system was verifying the validity of the file. This field is displayed only if an .ipe file is specified for the command. |
|
Slot |
Member ID of the member device. |
|
Upgrade Way |
ISSU method: · Service Upgrade—Service-level incremental upgrade. · File Upgrade—File-level incremental upgrade. · Reboot—Upgrading software by rebooting both data and control planes. This method disrupts services. 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 feature image files. You can specify a space-separated list of up to 30 feature image files.
filename: Specifies the file path of a .bin software image file, a case-insensitive string. The file must be stored in the root directory of a storage medium on a member device. The maximum length is 63 characters for the storage-medium:/base-filename.bin segments of the file path. For more information about specifying a file path, see "Managing the file system."
ipe ipe-filename: Specifies the file path of an .ipe image package file, a case-insensitive string. The file must be stored in the root directory of a storage medium on a member device. The maximum length is 63 characters for the storage-medium:/base-filename.ipe segments of the file path.
Usage guidelines
Use this command if you want to upgrade PEXs during an ISSU that uses issu commands.
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 sets software images for all PEXs of the specified model.
If the PEXs have a storage medium, 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.
If the PEXs do not have a storage medium, 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 other member devices.
The PEXs will be upgraded with the upgrade images during the ISSU process.
Examples
# Specify flash:/devkit.bin as the image for upgrading S5120HI PEXs. S5120HI PEXs do not have a storage medium.
<Sysname> issu pex PEX-S5120HI file feature flash:/devkit.bin
Verifying the file flash:/devkit.bin on slot 1...Done.
<Sysname>
# Specify flash:/devkit.bin as the image for upgrading S6300 PEXs. S6300 PEXs have storage media.
<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 for upgrading S5120HI PEXs. S5120HI PEXs do not have a storage medium.
<Sysname> issu pex PEX-S5120HI file ipe flash:/test.ipe
Verifying the file flash:/test.ipe on slot 1............Done.
File flash:/devkit.bin already exists on slot 1.
File flash:/manufacture.bin already exists on slot 1.
Overwrite the existing files? [Y/N]:Y
Decompressing file devkit.bin to flash:/devkit.bin. .....Done.
Decompressing file manufacture.bin to flash:/manufacture.bin.....Done.
File flash:/devkit.bin already exists on slot 2.
File flash:/manufacture.bin already exists on slot 2.
Overwrite the existing files? [Y/N]:Y
Copying file flash:/devkit.bin to slot2#flash:/devkit.bin. ...Done.
Copying file flash:/manufacture.bin to slot2#flash:/manufacture.bin....Done.
# Specify flash:/test.ipe as the image for upgrading S6300 PEXs. S6300 PEXs have storage media.
<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 interval is 45 minutes.
Views
System view
Predefined user roles
network-admin
Parameters
minutes: Specifies the automatic rollback interval in minutes, in the range of 0 to 120. Setting it to 0 disables automatic rollback.
Usage guidelines
As a best practice, do not use the automatic rollback feature. This feature is complicated.
Examples
# Disable automatic rollback.
<Sysname> system-view
[Sysname] issu rollback-timer 0
Related commands
issu rollback
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 check the synchronization progress, use the display device command. The synchronization is completed if all member devices are in normal state.
Examples
# Perform an ISSU switchover during an ISSU to a compatible version.
Upgrade summary according to following table:
flash:/feature.bin
Running Version New Version
Alpha 7122 Alpha 7123
Slot Switchover Way
1 Active standby process switchover
Upgrading software images to compatible versions. Continue? [Y/N]:
# Perform an ISSU switchover and upgrade members that have not been upgraded (member 1 and member 2) during an ISSU to an incompatible version.
Copying file flash:/feature.bin to slot2#flash:/feature.bin...Done.
Upgrade summary according to following table:
flash:/feature.bin
Running Version New Version
Alpha 7122 Alpha 7123
Slot Upgrade Way
1 Reboot
2 Reboot
Upgrading software images to incompatible versions. Continue? [Y/N]:y
Table 7 Command output
|
Field |
Description |
|
Verifying the file |
The system was verifying the validity of the file. |
|
Switchover Way |
Switchover method: · Active standby process switchover—Switch from the active process to the standby process. · Global active standby MPU switchover—Switch from the master to a subordinate member. |
For more information about the command output, see Table 4.
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.
Examples
# Clear the two oldest ISSU log entries.
<Sysname> reset install log-history oldest 2
Related commands
display install log
