Login
- Table of Contents
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 07-ISSU Commands | 120.89 KB |
|
|
NOTE: ISSU configuration is applicable to switches operating in IRF mode only. For more information about the IRF mode, see IRF Configuration Guide. |
display issu rollback-timer
Syntax
display issu rollback-timer [ | { begin | exclude | include } regular-expression ]
View
Any view
Default level
1: Monitor level
Parameters
|: Filters command output by specifying a regular expression. For more information about regular expressions, see Fundamentals Configuration Guide.
begin: Displays the first line that matches the specified regular expression and all lines that follow.
exclude: Displays all lines that do not match the specified regular expression.
include: Displays all lines that match the specified regular expression.
regular-expression: Specifies a regular expression, a case-sensitive string of 1 to 256 characters.
Description
Use the display issu rollback-timer command to display information about the rollback timer.
The rollback timer takes effect for the next ISSU upgrade process. Therefore, the remaining time of the rollback timer may be greater than the rollback timer value.
Related commands: issu rollback-timer.
Examples
# Display information about the rollback timer.
<Sysname> display issu rollback-timer
RollBack timer is in process.
Configured Rollback Timer: 45 minutes.
Left: 36 minutes.current rollback-timer :45 minutes.
Table 1 Output description
|
Field |
Description |
|
RollBack timer is in process |
The system is performing an ISSU upgrade and the rollback timer runs normally. |
|
Configured Rollback Timer |
Configured rollback timer value. |
|
Left |
Remaining time in minutes before the rollback timer expires (it is displayed only when the rollback timer is started). |
|
RollBack timer is not in process |
ISSU upgrade is not started or the rollback timer has been deleted (execution of the issu accept or issu commit command deletes the rollback timer). |
display issu state
Syntax
display issu state [ | { begin | exclude | include } regular-expression ]
View
Any view
Default level
1: Monitor level
Parameters
|: Filters command output by specifying a regular expression. For more information about regular expressions, see Fundamentals Configuration Guide.
begin: Displays the first line that matches the specified regular expression and all lines that follow.
exclude: Displays all lines that do not match the specified regular expression.
include: Displays all lines that match the specified regular expression.
regular-expression: Specifies a regular expression, a case-sensitive string of 1 to 256 characters.
Description
Use the display issu state command to display the ISSU state.
The ISSU upgrade process is completed through the execution of a series of commands, which must be executed by following specific sequence. The display issu state command enables you to view the current ISSU state, upgrade version, old version, version compatibility state, and upgrade method to determine the next operation to be executed.
Examples
# Display the current ISSU state.
<Sysname> display issu state
ISSU state: Switchover
Compatibility: Compatible
Work State: Normal
Upgrade Method: Board by board
Previous version: S9500E-CMW520-A1399
Previous boot file is cfa0:/s9500e_issu_hotfix.bin
Upgrade version: S9500E-CMW520-A1322
Upgrade boot file is cfa0:/s9500e_v1r3b01d005_release.bin
Table 2 Output description
|
Field |
Description |
|
ISSU state |
ISSU state: · Init—An ISSU upgrade process does not start yet or an ISSU upgrade process has completed. · Load—The standby main processing unit (MPU) or a member switch is being upgraded or has been upgraded. The rollback timer is created successfully and runs normally. · Switchover—The upgraded standby MPU has become the new active MPU, or an upgraded member switch has become the new master. · Accept—The upgrading operation of the new active MPU or new master is accepted, and the rollback timer is automatically deleted. No auto-rollback is performed during this ISSU upgrade process. · Commit—Multiple standby MPUs or member switches are available in the system, and at least one standby MPU or member switch has not been upgraded to the new version. In this state, neither manual nor auto-rollback is performed. |
|
Compatibility |
Version compatibility check result: · Compatible—The fundamental modules that support the operation of the switch and the service modules are compatible. The ISSU upgrade between the two versions can proceed successfully. · Partial compatible—The fundamental modules that support the operation of the switch are compatible, and some protocol modules are incompatible. The system automatically disables the incompatible modules and the ISSU upgrade between the two versions can proceed successfully. · Incompatible—The fundamental modules that support the operation of the switch are incompatible. In this case, the force keyword is required when you execute the issu load command. After starting up with the new software version, the standby MPU operates in independent active mode, and the interface cards can be upgraded only through the reboot upgrade method. · Unknown—The specified version file does not support ISSU or cannot be upgraded through ISSU. |
|
Work State |
Switch operation mode: · Normal · Independent active—If you force the switch into the upgrade process when the software versions are incompatible, the standby MPU that is upgraded first will enter the independent active mode, which allows multiple MPUs in the same system to run different software versions. |
|
Upgrade Method |
Upgrade method: · Board by board—MPU-based ISSU upgrade. In other words, first upgrade the standby MPU of the master, and then upgrade all the other MPUs one by one. · Chassis by Chassis—Member switch-based ISSU upgrade. In other words, upgrade the slaves first, and then the former master. |
|
Previous version |
Version of the old system software |
|
Previous boot file |
Path of the old system software image |
|
Upgrade version |
Version of the new system software (NA indicates that the version of the new software is not obtained.) |
|
Upgrade boot file |
Path of the new system software image |
display version comp-matrix
Syntax
display version comp-matrix [ file upgrading-filename ] [ | { begin | exclude | include } regular-expression ]
View
Any view
Default level
1: Monitor level
Parameters
file upgrading-filename: Displays compatibility information between the software version of the specified file and that of the current running file. The upgrading-filename argument specifies a file name, which is a string of 1 to 63 characters. If you enter a relative path, the system automatically converts it to an absolute path. The absolute path should contain no more than 63 characters; otherwise, the command cannot be successfully executed.
|: Filters command output by specifying a regular expression. For more information about regular expressions, see Fundamentals Configuration Guide.
begin: Displays the first line that matches the specified regular expression and all lines that follow.
exclude: Displays all lines that do not match the specified regular expression.
include: Displays all lines that match the specified regular expression.
regular-expression: Specifies a regular expression, a case-sensitive string of 1 to 256 characters.
Description
Use the display version comp-matrix command to display version compatibility information.
If you provide the upgrading-filename argument, this command displays the compatibility information between the software version of the specified file and that of the current running file.
If you do not provide the upgrading-filename argument, this command displays information about the compatibility database (which records the serial numbers of history software versions and the compatibility information between the software version of this file and the history software versions) of the current running system software image, that is, compatibility information between the current software version and other versions.
Examples
# Display the version compatibility database information about the current running system software image.
<Sysname> display version comp-matrix
Number of Matrices in Table = 1
Matrix for H3C S9505E
==========================================
Start Flag (0xDEADBABE)
My Image ver: S9500E-CMW520-B1226
Peer Version Compatibility
------------ -------------
S9500E-CMW520-B1226 (Base)
S9500E-CMW520-B1225 (Compatible)
# Display version compatibility information between the current running software and the specified software.
<Sysname> display version comp-matrix file S9500E-CMW520-B1225.bin
Matrix for H3C S9505E
==========================================
Start Flag (0xDEADBABE)
My Image ver: S9500E-CMW520-B1226
Peer Version Compatibility
------------ -------------
S9500E-CMW520-B1225 (Compatible)
Chassis 1 Slot 3: Hotfix
Chassis 1 Slot 4: Hotfix
Table 3 Output description
|
Field |
Description |
|
My Image ver |
Version number of the current MPU. |
|
Peer Version Compatibility |
Version compatibility information: · Base—The current running version. · Compatible—Completely compatible with the current running version. · Base-Level-Compatible—Partially compatible with the current running version. · Incompatible—Incompatible with the current running version. · Unknown-Compatible—The specified version file does not support ISSU or cannot be upgraded through ISSU. |
|
Slot 3: Reboot |
The card in slot 3 will reboot during the upgrade process and the service on this card will be interrupted for a short time. |
|
Slot 4: Hotfix |
The card in slot 4 will be upgraded by installing the corresponding hotfix and the ISSU upgrade will not interrupt the services on the card. |
issu accept
Syntax
issu accept chassis chassis-number [ slot slot-number ]
View
System view
Default level
2: System level
Parameters
chassis chassis-number: Specifies the member ID of an upgraded IRF member switch. The value must be the same as that specified in the issu load command.
chassis chassis-number slot slot-number: Specifies a card on an IRF member switch. The chassis-number argument represents the ID of the IRF member switch, and the slot-number argument represents the number of the slot that holds the card. You can display the member ID and slot number with the display device command. For more information about IRF, see IRF Configuration Guide.
Description
Use the issu accept chassis chassis-number command to accept the ISSU upgrade. Use this command when you apply the member switch-based ISSU upgrade method.
Use the issu accept chassis chassis-number slot slot-number command to accept the ISSU upgrade. Use this command when you apply the MPU-based ISSU upgrade method.
With this command executed, the system deletes the rollback timer and does not perform the auto-rollback operation in this upgrade process. However, you can execute a manual rollback at the Command-line interface (CLI).
Execution of the issu accept command is the third step in the ISSU upgrade process. This step is optional and you can skip this command and execute the issu commit command to complete the upgrade process.
Related commands: issu commit and issu load.
Examples
# In the member switch-based ISSU upgrade process, accept the upgrade of the upgraded member switch with the member ID of 2.
<Sysname> system-view
[Sysname] issu accept chassis 2
# In the MPU-based ISSU upgrade process, accept the upgrade of the upgraded MPU in slot 1 on chassis 1.
<Sysname> system-view
[Sysname] issu accept chassis 1 slot 1
issu commit
Syntax
issu commit chassis chassis-number [ slot slot-number ]
View
System view
Default level
2: System level
Parameters
chassis chassis-number: Specifies the member ID of a switch that is not upgraded yet.
chassis chassis-number slot slot-number: Specifies a card on an IRF member switch. The chassis-number argument represents the ID of the IRF member switch, and the slot-number argument represents the number of the slot that holds the card. You can display the member ID and slot number with the display device command. For more information about IRF, see IRF Configuration Guide.
Description
Use the issu commit chassis chassis-number command to upgrade the MPU that is not upgraded yet. Use this command when you apply the member switch-based ISSU upgrade method.
Use the issu commit chassis chassis-number slot slot-number command to upgrade the MPU that is not upgraded yet. Use this command when you apply the MPU-based ISSU upgrade method.
Execution of the issu accept command is the fourth step in the ISSU upgrade process.
Execution of the issu commit command completes the ISSU upgrade process, and you cannot perform a version rollback operation with the issu rollback command.
When you use the member switch-based ISSU upgrade method, if there are multiple member switches that are not upgraded yet, upgrade them one by one to avoid IRF fabric partition and upgrade failure. In other words, upgrade one member, wait for the switch to reboot and join the IRF fabric again, and then execute this command to upgrade another member switch.
When you use the MPU-based ISSU upgrade method, if two MPUs on the same member switch need to be upgraded, upgrade them one by one; otherwise, all interfaces cards on this member switch will reboot.
Related commands: issu accept and issu load.
Examples
# In the member switch-based ISSU upgrade process, upgrade the un-upgraded member switch with the member ID of 1 of the current IRF member switch.
<Sysname> system-view
[Sysname] issu commit chassis 1
The specified chassis will reboot and be upgraded. Continue? [Y/N]:y
# In the MPU-based ISSU upgrade process, upgrade the un-upgraded MPU in slot 0 on chassis 1 of the current IRF member switch.
<Sysname> system-view
[Sysname] issu commit chassis 1 slot 0
The specified board will reboot and be upgraded. Continue? [Y/N]:y
issu load
Syntax
issu load file upgrading-filename chassis chassis-number [ slot slot-number ] [ force ]
issu load file upgrading-filename { chassis chassis-number } &<2-10> force
View
System view
Default level
2: System level
Parameters
file upgrading-filename: Upgrade filename, a string of 1 to 63 characters. The file can be saved only on the storage media of the active MPU on the master. If you enter a relative path, the system automatically converts it to an absolute path. The absolute path should contain no more than 63 characters; otherwise, the command cannot be successfully executed. The file name is in the format of [drive:/]file-name, where:
· The items in square brackets [ ] are optional.
· drive specifies the storage medium of the file. The value is the name of the storage medium. If a switch has only one storage medium, you can execute this command without providing this argument.
· file-name specifies the filename, which is usually suffixed by .app or .bin.
chassis chassis-number: Specifies the member ID of the slave of an IRF fabric. After the ISSU upgrade is completed, the slave becomes the master.
chassis chassis-number slot slot-number: Specifies the standby MPU on the master of an IRF fabric. chassis-number is the member ID of the master, and slot-number is the slot number of the standby MPU on the master. After the ISSU upgrade is completed, this MPU becomes the global active MPU.
{ chassis chassis-number } &<2-10>: Specifies the member IDs of the member switches to be upgraded at the same time. &<2-10> means that you can specify the chassis chassis-number option 2 to 10 times.
force: Forces the standby MPU into the upgrade process for incompatible version. If the file specified by upgrading-filename is incompatible with the current system software image, you must provide this key word; otherwise, the upgrade process cannot be started. If the file specified by upgrading-filename is compatible with the current system software image, the upgrade process can be started no matter whether this keyword is provided or not.
Description
Use the issu load file upgrading-filename chassis chassis-number [ force ] command to upgrade a slave during a member switch-based ISSU upgrade process.
Use the issu load file upgrading-filename chassis chassis-number slot slot-number [ force ] command to upgrade the standby MPU of the master during an MPU-based ISSU upgrade process.
Use the issu load file upgrading-filename { chassis chassis-number } &<2-10> force command to upgrade multiple member switches at the same time during a member switches-based ISSU upgrade for a four-member IRF.
Executing the issu load command is the first step in the ISSU upgrade process.
You can upgrade an IRF fabric with ISSU by using the following methods as appropriate:
· MPU-based ISSU upgrade, for compatible and partially compatible versions only.
· Member switch-based ISSU upgrade for compatible and partially compatible versions.
· Member switch-based ISSU upgrade for incompatible versions.
· Member switches-based ISSU upgrade, for incompatible versions only.
For more information about these methods, see Fundamentals Configuration Guide.
Before executing the issu load command, make sure that the new system software image and the old system software image exist on the active MPUs and the standby MPUs of the master and slaves, and the files are saved on the root directory of the storage medium of the same type. Otherwise, the system cannot perform the ISSU upgrade.
If the IRF fabric has two members, the daisy chain connection is OK. If the IRF fabric has more than two members, use the ring connection; otherwise, the IRF fabric will be partitioned during upgrade and the upgrade process will be out of control.
Before executing the issu load command, make sure that all active MPUs and standby MPUs use the same system software image.
Before executing the issu load command, make sure that all MPUs run software of the same version.
Avoid modifying the current configuration (especially the IRF port configuration), rebooting a card, plugging and unplugging the cables connecting physical IRF ports, performing an active and standby switchover, deleting/modifying the system software image, or loading/unloading a hotfix during the ISSU upgrade; otherwise, upgrade failure may occur.
If the current and new system software images are incompatible, manually save the current configuration with the save command to avoid configuration lost after the upgrade.
Member switches-based ISSU upgrade is a good choice for upgrading a four-member IRF fabric when the version compatibility check result is incompatible. Make sure that the slaves to be upgraded first are physically connected.
Examples
# In the member switch-based ISSU upgrade process, upgrade the slave with the member ID of 2 by using upgrade file test.bin, which is partially compatible with the current running system software image on the master.
<Sysname> system-view
[Sysname] issu load file flash:/test.bin chassis 2
This command will begin ISSU, and the specified chassis will reboot and be upgraded. Please save the current running configuration first; otherwise, the configuration may be lost.Continue? [Y/N]:y
# In the MPU-based ISSU upgrade process, upgrade the standby MPU of the master with the member ID of 1 by using upgrade file test.bin, which is partially compatible with the current running system software image on the global active MPU.
<Sysname> system-view
[Sysname] issu load file flash:/test.bin chassis 1 slot 1
This command will begin ISSU, and the specified board will reboot and be upgraded. Please save the current running configuration first; otherwise, the configuration may be lost.Continue? [Y/N]:y
# In the member switches-based ISSU upgrade process, upgrade the slaves with the member IDs 2 and 3 by using upgrade file test.bin, which is incompatible with the current running system software image on the master.
<Sysname> system-view
[Sysname] issu load file test.bin chassis 2 chassis 3 force
This command will begin ISSU, and the specified chassis will reboot and be upgraded. Please save the current running configuration first; otherwise, the configuration may be lost.Continue? [Y/N]:y
issu rollback
Syntax
issu rollback [ chassis chassis-number [ slot slot-number ] ]
View
System view
Default level
2: System level
Parameters
chassis chassis-number: Specifies the member ID of an upgraded switch. The value must be the same as that specified in the issu load command.
chassis chassis-number slot slot-number: Specifies the location of the upgraded MPU. The values must be the same as those specified in the issu load command. chassis-number is the member ID of the master of an IRF fabric, and slot-number is the slot number of the upgraded MPU on the master.
Description
Use the issu rollback command to cancel the ISSU upgrade and roll back to the previous version.
During the execution of any issu command, you cannot perform the rollback operation.
Before executing the issu load command or after executing the issu commit command, you cannot perform the rollback operation.
To cancel the ISSU upgrade for an incompatible version, you do not need to specify any parameter for the issu rollback command.
Related commands: issu load.
Examples
# Cancel a member switch-based ISSU upgrade. (Suppose that the member ID specified in the issu load command is 2.)
<Sysname> system-view
[Sysname] issu rollback chassis 2
This command will quit the issu process and the specified chassis will rollback to the previous version. Continue? [Y/N]:y
# Cancel an MPU-based ISSU upgrade. (Suppose that the MPU location specified in the issu load command is slot 1 in chassis 1.)
<Sysname> system-view
[Sysname] issu rollback chassis 1 slot 1
This command will quit the issu process and the specified board will roll back to the previous version. Continue? [Y/N]:y
# Cancel a member switches-based ISSU upgrade.
<Sysname> system-view
[Sysname] issu rollback
The system will rollback the software and reboot the upgraded chassis. Continue? [Y/N]:y
issu rollback-timer
Syntax
issu rollback-timer minutes
undo issu rollback-timer
View
System view
Default level
1: Monitor level
Parameters
minutes: Rollback timer value in minutes, which is in the range 0 to 120. The value of 0 indicates that the version rollback function is disabled and the rollback timer is not created when you execute the issu load command.
Description
Use the issu rollback-timer command to set the rollback timer value.
Use the undo issu rollback-timer command to restore the default.
By default, the rollback timer value is 45 minutes.
After the first step (with the issu load command executed) of the ISSU upgrade process, the system automatically creates a version rollback timer. If you do not execute the issu accept or issu commit command before the specified rollback timer expires, the system automatically stops the ISSU process and reverts to the previous software version.
You may need to use the version rollback function in some cases, for example, when the new system software image is broken.
If you execute the issu rollback-timer command during an ISSU upgrade process, the rollback timer takes effect for the next ISSU upgrade process.
After executing the issu load or issu run switch command, when the standby MPU is in the reboot process and the upgrading process of the standby MPU is not complete, if the rollback timer expires or you perform a manual rollback at this time, the version rollback will fail. Therefore, make sure the following:
· Do not set the rollback timer to a small value, for example, the rollback timer cannot be shorter than the system boot time.
· Do not perform version rollback immediately after executing the issu load or issu run switch command.
Examples
# Set the rollback timer value to 30 minutes.
<Sysname> system-view
[Sysname] issu rollback-timer 30
issu run switchover
Syntax
issu run switchover [ chassis chassis-number [ slot slot-number ] ]
View
System view
Default level
2: System level
Parameters
chassis chassis-number: Specifies the member ID of an upgraded switch. The value must be the same as that specified in the issu load command.
chassis chassis-number slot slot-number: Specifies the location of the upgraded MPU. The values must be the same as those specified in the issu load command. chassis-number is the member ID of the master of an IRF fabric, and slot-number is the slot number of the upgraded MPU on the master.
Description
Use the issu run switchover command to manually trigger an active/standby or master/slave switchover.
In the member switch-based ISSU upgrade process, the current master reboots with the previous version and the upgraded slave becomes the new master after the master/slave switchover.
In the MPU-based ISSU upgrade process, the current global active MPU reboots with the previous version and the standby MPU of the master becomes the global active MPU after the active and standby switchover, and then the interface cards are upgraded by installing hotfixes.
If the previous and new versions are incompatible, a good practice is to use the member switches-based upgrade method. During such an upgrade, the issu run switchover command will make the original master and the slaves that are not upgraded yet reboot with the new version to complete the ISSU upgrade.
If you do not execute the issu accept or issu commit command before the specified rollback timer expires, the system automatically stops the ISSU process and reverts to the previous software version.
Avoid configuring the system, performing an active and standby switchover, and plugging/unplugging a card during the ISSU upgrade.
For the MPU-based ISSU upgrade method, make sure that all interface cards have their upgrade hotfixes. Otherwise, if the interface cards upgrade by rebooting, the IRF fabric is partitioned and the upgrade fails.
Execution of this command may cause the reboot of an interface card or a member switch, and the services are thus interrupted.
Related commands: issu load.
|
|
CAUTION: · Before performing a master/slave switchover, make sure that upgraded slave switch has the highest priority among the IRF member switches. You can view the member switch priorities by executing the display irf command, and use the irf member priority command to modify the priority of the upgraded slave switch to make it has the highest priority. For more information about the display irf and irf member priority commands, see IRF Command Reference. · When the issu run switchover command is executed, each interface card loads a new hotfix for upgrading from the current active MPU. When the current active MPU reboots, the standby MPU becomes the active MPU, the hotfixes on the interface cards are activated, and then the interface cards are upgraded. If any interface card fails to obtain a hotfix, the interface card is upgraded by rebooting. · If you do not execute the issu accept or issu commit command before the rollback timer expires, the ISSU upgrade ends automatically, and the software reverts to the previous version. |
Examples
# In the member switch-based ISSU upgrade process, perform a manual master/slave switchover to make the upgraded slave with the member ID of 2 become the new master of an IRF fabric.
<Sysname> system-view
[Sysname] issu run switchover chassis 2
Master will reboot, switch the specified chassis to master. Continue? [Y/N]:y
# In the MPU-based ISSU upgrade process, perform a manual active and standby switchover to make the upgraded MPU in slot 1 on chassis 1 become the global active MPU.
<Sysname> system-view
[Sysname] issu run switchover chassis 1 slot 1
Master will reboot, switch the specified board to master and update the line card. Continue? [Y/N]:y
# In the member switches-based ISSU upgrade process, perform a manual master/slave switchover to make an upgraded slave (the one with the highest priority) becomes the new master.
<Sysname> system-view
[Sysname] issu run switchover chassis 2
Master will reboot, switch the specified chassis to master. Continue? [Y/N]:y
