The In-Service Software Upgrade (ISSU) function enables a fast software upgrade without (or with the least) service interruption. During an ISSU, you can perform version rollback and use display commands to view the version compatibility and upgrade status.

ISSU is implemented on the basis of the following design advantages:

· Separation of service features from basic functions. The software of the device includes a boot image, a system image, some feature images, and some patch images (if any). The boot image and system image provide the operating system. Feature images provide service features. Usually, you only need to add new service features or upgrade existing service features, without affecting the basic system functions.

· Independence between service features. When you add or upgrade one service feature, the other service features and the system operation are not affected.

· Support for hotfix. By installing patch images, you can fix system bugs without rebooting the device.

· Hardware redundancy. When the device has two MPUs and is operating in standalone mode, the standby MPU can take over while the active MPU needs to reboot for an upgrade. When the device is operating in IRF mode, a standby MPU of the IRF fabric can take over while the global active MPU needs to reboot for an upgrade.

· For more information about images, see "Upgrading software."

ISSU methods

The device provides several ISSU methods for upgrades to compatible versions. When you perform an ISSU, the device compares the compatibility between the old and new software versions and selects an ISSU method based on the version compatibility.

Before an ISSU, you can check for the ISSU method to be used for the upgrade and view the possible impact of the upgrade. Whichever ISSU method is used, the ISSU procedure and commands are the same.

The device provides the following categories of ISSU methods:

· Incremental upgrade

An incremental upgrade analyzes the differences between the new and old software versions and upgrades only the different parts. An incremental upgrade takes the least time and imposes the least effect on the device.

Incremental upgrade methods include:

¡ Service-level incremental upgrade—This method involves only the upgraded service modules. The other service modules provide services normally during the upgrade.

¡ File-level incremental upgrade—This method involves only hidden system program files. The system operates and provides services normally during the upgrade.

· ISSU reboot

An ISSU reboot upgrade saves the current system information (including the operation data, configuration data, hardware data, and status information) to the memory and uses the new software to reboot the CPU. During an ISSU reboot upgrade, the data forwarding plane of the system keeps forwarding packets. After startup, the CPU continues to provide services on the basis of the saved system information. For services that require regular protocol message exchanges to maintain connections, this method starts protocol agents to satisfy the requirements.

Compared with an incremental upgrade, an ISSU reboot upgrade affects all modules that use the CPU and takes a longer time. An ISSU reboot upgrade is usually performed when the new and old software versions are partially compatible.

· Reboot (in standalone mode)

A reboot upgrade reboots cards to load the new software.

When the device has two MPUs and both MPUs need to be rebooted for upgrade, upgrade the standby MPU first to implement in-service upgrade. If the device has only one MPU, service interruption is unavoidable during the upgrade.

Specially, the upgrade method of a switching fabric card might be Sequence Reboot. This method reboots one switching fabric card at a time and proceeds to reboot another switching fabric card only when the previously upgraded one restarts up. This method can implement in-service switching fabric card upgrade when the device has multiple switching fabric cards that support this method.

· Reboot (in IRF mode)

A reboot upgrade reboots cards to load the new software.

When a member device of the IRF fabric has two MPUs and both MPUs need to be rebooted for upgrade, upgrade the standby MPU first to implement in-service upgrade. If a member of the IRF fabric has only one MPU, service interruption is unavoidable during the upgrade.

ISSU command series

To perform an ISSU, you can use either of the install series commands or the issu series commands. Table 1 compares these two series of commands.

Table 1 Comparison between the two series of commands

Item	issu series commands	install series commands
Required compatibility between the old and new software versions	Compatible or incompatible.	Compatible.
Support installing and uninstalling patches?	No.	Yes.
Upgrade mode	Upgrade an IRF fabric as per member device.	Advanced upgrade mode, upgrade the system as per MPU.
Effect scope of the upgrade operation	Large.	Small.
Requirement for administrators	Low, applicable to most administrators.	High. Administrators must have a profound understanding of the system and the effects of each upgrade action.
Recommended for common administrators?	Yes.	No.

ISSU prerequisites

· Read the software release notes to determine which software images need to be upgraded, whether these software images are compatible with one another, and whether these software images are compatible with the software images running on the device. Then, based on the compatibility, determine the command series to use.

· Make sure the storage media on the MPUs have sufficient free space for the new image files or the IPE file.

· Use the display device command to examine the operation status of the system and make sure the system is operating properly. If there is any problem with the system, troubleshoot the system before performing an ISSU.

· Make sure the LACP timeout interval is the long timeout interval (the lacp period short command is not configured) on all member ports of the dynamic aggregation groups.

· Use the display mdc command to examine the operation status of the MDCs and make sure all MDCs are in active state.

· Use the save command to save the running configuration.

· In standalone mode, use FTP or TFTP to download or upload the software image files or the IPE file to the root directory of the active MPU's storage medium. Before the standby MPU is upgraded, the system will ask you whether you want to copy the files to the standby MPU. For more information about FTP and TFTP, see "Configuring FTP" and "Configuring TFTP."

· In IRF mode, use FTP or TFTP to download or upload the software image files or the IPE file to the root directory of the global active MPU's storage medium. Before a standby MPU of the IRF fabric is upgraded, the system will ask you whether you want to copy the files to the standby MPU.

ISSU restrictions and guidelines

· Before an ISSU:

¡ Enable GR or NSR for protocols including LDP, RSVP, OSPF, ISIS, BGP, and FSPF. Otherwise, services might be interrupted during the upgrade.

¡ Disable BFD for protocols including LDP, RSVP, OSPF, ISIS, RIP, BGP, VRRP, and NQA. Otherwise, services might be interrupted during the upgrade.

¡ Log in to the device through the console port. If you are using Telnet or SSH, you might be disconnected from the device before the ISSU is completed.

¡ To achieve better service continuity, make sure the device has two MPUs and both MPUs are operating properly. When the device has only one MPU and the reboot method is used, service interruption is unavoidable. (In standalone mode.)

¡ To achieve better service continuity, make sure the IRF fabric has two or more MPUs and all MPUs are operating properly. When the IRF fabric has only one MPU and the reboot method is used, service interruption is unavoidable. (In IRF mode.)

¡ If the switching fabric cards of the device support sequential upgrade, make sure the device has two or more such cards and the cards are operating properly.

¡ Make sure nothing is wrong with the hardware and no hardware upgrade is going on. Otherwise, an upgrade failure or system exception might occur.

· During an ISSU:

¡ Do not reboot, install, or remove any card, and make sure the network topology is stable.

¡ Do not execute any command that is not relevant to the ISSU process.

¡ Make sure you are the only one who is logged in to the device and no other administrators will log in during the upgrade.

· Do not modify, delete, or rename any image files.

· The issu series configuration commands and the install series configuration commands are mutually exclusive. You can use only one series of configuration commands for one ISSU process. However, you can use the install series displaying and maintaining commands with the issu series configuration commands.

· To configure the device after an ISSU, you must relog in to the device.

· All MDCs on a device run the same image files. To upgrade the MDCs, you only need to perform the upgrade on the default MDC for once.

Performing an ISSU by using issu series commands

Performing an ISSU in standalone mode

When you use the issu series commands to install or upgrade the software of MPUs, the device automatically install or upgrade the software of the service cards as needed. You do not need to install or upgrade the software of the service cards separately.

The ISSU procedure varies depending on whether the device has a single or two MPUs.

Performing an ISSU for a dual-MPU device

· If a new image is on the Version compatibility list, the new and old images are compatible.

· If a new image is not on the Version compatibility list, the new and old images are incompatible.

To perform an ISSU for a compatible version, execute the following commands:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. (Optional.) Display automatic-rollback timer information.	display issu rollback-timer	If you don't think the ISSU can be finished before the timer expires, adjust the timer.
3. (Optional.) Set the automatic rollback timer.	issu rollback-timer minutes	By default, the automatic-rollback interval is 45 minutes. This timer is started when you execute the issu run switchover command. If you do not execute the issu accept or issu commit command before this timer expires, the system automatically rolls back to the original software configuration.
4. Return to user view.	quit	N/A
5. Upgrade the standby MPU and configure the upgrade images as the main startup software images for the standby MPU.	· Approach 1: issu load file { boot filename \| system filename \| feature filename&<1-30> } * slot slot-number · Approach 2: issu load file ipe ipe-filename slot slot-number	Specify the slot number of the standby MPU for the slot slot-number option.
6. Perform an active/standby switchover and upgrade the interface cards.	issu run switchover	N/A
7. (Optional.) Accept the upgrade and delete the automatic-rollback timer.	issu accept	N/A
8. Complete the ISSU process or roll back to the original software configuration.	· To upgrade the original active MPU and complete the ISSU: issu commit slot slot-number · To roll back to the original software configuration: issu rollback	Specify the slot number of the original active MPU for the slot slot-number option. After the issu commit command is completed, the ISSU process ends and the ISSU status transitions to Init. During this ISSU process, you can use the issu rollback command at any point to roll back to the original software configuration. For more information about rollback, see Fundamentals Command Reference.

To perform an ISSU for an incompatible version, execute one of the following commands in user view:

Step	Commands	Remarks
1. Upgrade the standby MPU and configure the upgrade images as the main startup software images for the standby MPU.	· Approach 1: issu load file { boot filename \| system filename \| feature filename&<1-30> } * slot slot-number · Approach 2: issu load file ipe ipe-filename slot slot-number	Specify the slot number of the standby MPU for the slot slot-number option.
2. Complete the ISSU process or roll back to the original software configuration.	· To complete the ISSU process, perform an active/standby switchover to upgrade all cards except for the upgraded MPU: issu run switchover · To roll back to the original software configuration: issu rollback	After the issu run switchover command is completed, the ISSU process ends and the ISSU status transitions to Init. During this ISSU process, automatic rollback is not supported, but you can use the issu rollback command to manually roll back to the original software configuration. For more information about rollback, see Fundamentals Command Reference.

Step

Commands

Remarks

1. Upgrade the standby MPU and configure the upgrade images as the main startup software images for the standby MPU.

· Approach 1:
issu load file { boot filename | system filename | feature filename&<1-30> } * slot slot-number

· Approach 2:
issu load file ipe ipe-filename slot slot-number

Specify the slot number of the standby MPU for the slot slot-number option.

2. Complete the ISSU process or roll back to the original software configuration.

· To complete the ISSU process, perform an active/standby switchover to upgrade all cards except for the upgraded MPU:
issu run switchover

· To roll back to the original software configuration:
issu rollback

After the issu run switchover command is completed, the ISSU process ends and the ISSU status transitions to Init.

During this ISSU process, automatic rollback is not supported, but you can use the issu rollback command to manually roll back to the original software configuration. For more information about rollback, see Fundamentals Command Reference.

Performing an ISSU for a single-MPU device

Before upgrade, use the display version comp-matrix file { boot filename | system filename | feature filename&<1-30> } * or the display version comp-matrix file ipe ipe-filename command to display the compatibility between the new and old images and the upgrade methods to be used. If a new image is on the Version compatibility list and the value of the Upgrade Way field is Service Upgrade or File Upgrade, the new and old images are compatible and an incremental upgrade applies.

To perform an incremental upgrade to a compatible version, execute the following commands in user view:

Step	Command	Remarks
1. Upgrade the MPU and configure the upgrade images as the main startup software images for the MPU.	· Approach 1: issu load file { boot filename \| system filename \| feature filename&<1-30> } * slot slot-number · Approach 2: issu load file ipe ipe-filename slot slot-number	Specify the slot number of the only MPU for the slot slot-number option.
2. Complete the ISSU process or roll back to the original software configuration.	· To complete the ISSU process: issu commit slot slot-number · To roll back to the original software configuration: issu rollback	Specify the slot number of the only MPU for the slot slot-number option. After the issu commit command is completed, the ISSU process ends and the ISSU status transitions to Init. During this ISSU process, automatic rollback is not supported, but you can use the issu rollback command to manually roll back to the original software configuration. For more information about rollback, see Fundamentals Command Reference.

Step

Command

Remarks

1. Upgrade the MPU and configure the upgrade images as the main startup software images for the MPU.

· Approach 1:
issu load file { boot filename | system filename | feature filename&<1-30> } * slot slot-number

· Approach 2:
issu load file ipe ipe-filename slot slot-number

Specify the slot number of the only MPU for the slot slot-number option.

2. Complete the ISSU process or roll back to the original software configuration.

· To complete the ISSU process:
issu commit slot slot-number

· To roll back to the original software configuration:
issu rollback

Specify the slot number of the only MPU for the slot slot-number option.

After the issu commit command is completed, the ISSU process ends and the ISSU status transitions to Init.

To perform a reboot upgrade or ISSU reboot upgrade to a compatible version, or an ISSU for an incompatible version, execute one of the following commands in user view:

Task	Command	Remarks
Upgrade the MPU and configure the upgrade images as the main startup software images for the MPU.	· Approach 1: issu load file { boot filename \| system filename \| feature filename&<1-30> } * slot slot-number · Approach 2: issu load file ipe ipe-filename slot slot-number	Specify the slot number of the only MPU for the slot slot-number option. This single command starts and finishes the ISSU process. When this command is completed, the ISSU process ends and the ISSU status transitions to Init. No rollback can be performed during the ISSU process.

Task

Command

Remarks

Upgrade the MPU and configure the upgrade images as the main startup software images for the MPU.

· Approach 1:
issu load file { boot filename | system filename | feature filename&<1-30> } * slot slot-number

· Approach 2:
issu load file ipe ipe-filename slot slot-number

Specify the slot number of the only MPU for the slot slot-number option.

This single command starts and finishes the ISSU process. When this command is completed, the ISSU process ends and the ISSU status transitions to Init. No rollback can be performed during the ISSU process.

Performing an ISSU in IRF mode

The ISSU procedure varies by the number of member devices. For an IRF fabric with a single member, the ISSU procedure varies by the number of MPUs.

Performing an ISSU for a multi-member IRF fabric

ISSU for a multi-member IRF fabric should be performed as per member in two steps: first upgrade a subordinate member, and then upgrade the master and the other subordinate members.

· If a new image is on the Version compatibility list, the new and old images are compatible.

· If a new image is not on the Version compatibility list, the new and old images are incompatible.

To perform an ISSU for a compatible version, execute the following commands:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. (Optional.) Display automatic-rollback timer information.	display issu rollback-timer	If you don't think the ISSU can be finished before the timer expires, adjust the timer.
3. (Optional.) Set the automatic rollback timer.	issu rollback-timer minutes	By default, the automatic-rollback interval is 45 minutes. This timer is started when you execute the issu run switchover command. If you do not execute the issu accept or issu commit command before this timer expires, the system automatically rolls back to the original software configuration.
4. Return to user view.	quit	N/A
5. Upgrade subordinate members and configure the upgrade images as the main startup software images for the subordinate members.	· Approach 1: issu load file { boot filename \| system filename \| feature filename&<1-30> } * chassis chassis-number · Approach 2: issu load file ipe ipe-filename chassis chassis-number&<1-3>	Specify the member IDs of the subordinate members to be upgraded for the chassis chassis-number&<1-3> option.
6. Perform a master/subordinate switchover.	issu run switchover	N/A
7. (Optional.) Accept the upgrade and delete the automatic-rollback timer.	issu accept	N/A
8. Complete the ISSU process or roll back to the original software configuration.	· To complete the ISSU process, upgrade the unupgraded subordinate members (including the original master) using the following command: issu commit chassis chassis-number · To roll back to the original software configuration: issu rollback	After using the issu commit command to upgrade one subordinate member, you must wait for the subordinate member to restart up and join the IRF fabric before upgrading another subordinate member. After all members are upgraded, the ISSU process ends and the ISSU status transitions to Init. During this ISSU process, you can use the issu rollback command at any point to roll back to the original software configuration. For more information about rollback, see Fundamentals Command Reference.

To perform an ISSU for an incompatible version, execute the following commands in user view:

Step	Command	Remarks
1. Upgrade subordinate members and configure the upgrade images as the main startup software images for the subordinate members.	· Approach 1: issu load file { boot filename \| system filename \| feature filename&<1-30> } * chassis chassis-number&<1-3> · Approach 2: issu load file ipe ipe-filename chassis chassis-number&<1-3>	Specify the member IDs of the subordinate members to be upgraded for the chassis chassis-number&<1-3> option. If the member devices of the IRF fabric are connected into a ring topology, H3C recommends you specify a half of the subordinate members for this command to reduce service interruption. Make sure the specified subordinate members are physically connected.
2. Complete the ISSU process or roll back to the original software configuration.	· To complete the ISSU process, perform a master/subordinate switchover to upgrade all unupgraded members: issu run switchover · To roll back to the original software configuration: issu rollback	After all members are upgraded, the ISSU process ends and the ISSU status transitions to Init. During this ISSU process, automatic rollback is not supported, but you can use the issu rollback command at any point to manually roll back to the original software configuration. For more information about rollback, see Fundamentals Command Reference.

Step

Command

Remarks

1. Upgrade subordinate members and configure the upgrade images as the main startup software images for the subordinate members.

· Approach 1:
issu load file { boot filename | system filename | feature filename&<1-30> } * chassis chassis-number&<1-3>

· Approach 2:
issu load file ipe ipe-filename chassis chassis-number&<1-3>

Specify the member IDs of the subordinate members to be upgraded for the chassis chassis-number&<1-3> option. If the member devices of the IRF fabric are connected into a ring topology, H3C recommends you specify a half of the subordinate members for this command to reduce service interruption. Make sure the specified subordinate members are physically connected.

2. Complete the ISSU process or roll back to the original software configuration.

· To complete the ISSU process, perform a master/subordinate switchover to upgrade all unupgraded members:
issu run switchover

· To roll back to the original software configuration:
issu rollback

After all members are upgraded, the ISSU process ends and the ISSU status transitions to Init.

During this ISSU process, automatic rollback is not supported, but you can use the issu rollback command at any point to manually roll back to the original software configuration. For more information about rollback, see Fundamentals Command Reference.

Performing an ISSU for a single-member, dual-MPU IRF fabric

For an IRF fabric that has a single member with two MPUs, ISSU should be performed as per MPU in two steps: first upgrade the standby MPU, and then upgrade the active MPU.

· If a new image is on the Version compatibility list, the new and old images are compatible.

· If a new image is not on the Version compatibility list, the new and old images are incompatible.

To perform an ISSU for a compatible version, execute the following commands:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. (Optional.) Display automatic-rollback timer information.	display issu rollback-timer	If you don't think the ISSU can be finished before the timer expires, adjust the timer.
3. (Optional.) Set the automatic rollback timer.	issu rollback-timer minutes	By default, the automatic-rollback interval is 45 minutes. This timer is started when you execute the issu run switchover command. If you do not execute the issu accept or issu commit command before this timer expires, the system automatically rolls back to the original software configuration.
4. Return to user view.	quit	N/A
5. Upgrade the global standby MPU and configure the upgrade images as the startup software images for the MPU.	· Approach 1: issu load file { boot filename \| system filename \| feature filename&<1-30> } * chassis chassis-number slot slot-number · Approach 2: issu load file ipe ipe-filename chassis chassis-number slot slot-number	Specify the member ID and slot number of the global standby MPU for the chassis chassis-number slot slot-number option.
6. Perform an active/standby switchover and upgrade the interface cards.	issu run switchover	N/A
7. (Optional.) Accept the upgrade and delete the automatic-rollback timer.	issu accept	N/A
8. Complete the ISSU process or roll back to the original software configuration.	· To upgrade the original global active MPU and complete the ISSU process: issu commit chassis chassis-number slot slot-number · To roll back to the original software configuration: issu rollback	Specify the member ID and slot number of the original global active MPU for the chassis-number slot slot-number option. After the issu commit command is completed, the ISSU process ends and the ISSU status transitions to Init. During this ISSU process, you can use the issu rollback command to at any point to roll back to the original software configuration. For more information about rollback, see Fundamentals Command Reference.

To perform an ISSU for an incompatible version, execute the following commands in user view:

Step	Command	Remarks
1. Upgrade the global standby MPU and configure the upgrade images as the startup software images for the MPU.	· Approach 1: issu load file { boot filename \| system filename \| feature filename&<1-30> } * chassis chassis-number slot slot-number · issu load file ipe ipe-filename chassis chassis-number slot slot-number	Specify the member ID and slot number of the global standby MPU for the chassis chassis-number slot slot-number option.
2. Complete the ISSU process or roll back to the original software configuration.	· To upgrade the original global active MPU and the interface cards and complete the ISSU process: issu run switchover · To roll back to the original software configuration: issu rollback	After all cards are upgraded, the ISSU process ends and the ISSU status transitions to Init. During this ISSU process, automatic rollback is not supported, but you can use the issu rollback command at any point to manually roll back to the original software configuration. For more information about rollback, see Fundamentals Command Reference.

Step

Command

Remarks

1. Upgrade the global standby MPU and configure the upgrade images as the startup software images for the MPU.

· Approach 1:
issu load file { boot filename | system filename | feature filename&<1-30> } * chassis chassis-number slot slot-number

· issu load file ipe ipe-filename chassis chassis-number slot slot-number

Specify the member ID and slot number of the global standby MPU for the chassis chassis-number slot slot-number option.

2. Complete the ISSU process or roll back to the original software configuration.

· To upgrade the original global active MPU and the interface cards and complete the ISSU process:
issu run switchover

· To roll back to the original software configuration:
issu rollback

After all cards are upgraded, the ISSU process ends and the ISSU status transitions to Init.

Performing an ISSU for a single-member, single-MPU IRF fabric

To perform an incremental upgrade to a compatible version, execute the following commands in user view:

Step	Command	Remarks
1. Upgrade the MPU and configure the upgrade images as the startup software images for the MPU.	· Approach 1: issu load file { boot filename \| system filename \| feature filename&<1-30> } * chassis chassis-number slot slot-number · Approach 2: issu load file ipe ipe-filename chassis chassis-number slot slot-number	Specify the member ID and slot number of the only MPU for the chassis chassis-number slot slot-number option.
2. Complete the ISSU process or roll back to the original software configuration.	· To complete the ISSU process: issu commit chassis chassis-number slot slot-number · To roll back to the original software configuration: issu rollback	Specify the member ID and slot number of the only MPU for the chassis chassis-number slot slot-number option. After the issu commit command is completed, the ISSU process ends and the ISSU status transitions to Init. During this ISSU process, automatic rollback is not supported, but you can use the issu rollback command to manually roll back to the original software configuration. For more information about rollback, see Fundamentals Command Reference.

Step

Command

Remarks

1. Upgrade the MPU and configure the upgrade images as the startup software images for the MPU.

· Approach 1:
issu load file { boot filename | system filename | feature filename&<1-30> } * chassis chassis-number slot slot-number

· Approach 2:
issu load file ipe ipe-filename chassis chassis-number slot slot-number

Specify the member ID and slot number of the only MPU for the chassis chassis-number slot slot-number option.

2. Complete the ISSU process or roll back to the original software configuration.

· To complete the ISSU process:
issu commit chassis chassis-number slot slot-number

· To roll back to the original software configuration:
issu rollback

Specify the member ID and slot number of the only MPU for the chassis chassis-number slot slot-number option.

After the issu commit command is completed, the ISSU process ends and the ISSU status transitions to Init.

To perform a reboot upgrade or ISSU reboot upgrade to a compatible version, or an ISSU for an incompatible version, execute one of the following commands in user view:

Task	Command	Remarks
Upgrade the MPU and configure the upgrade images as the startup software images for the MPU.	· Approach 1: issu load file { boot filename \| system filename \| feature filename&<1-30> } * chassis chassis-number slot slot-number · Approach 2: issu load file ipe ipe-filename chassis chassis-number slot slot-number	Specify the member ID and slot number of the only MPU for the chassis chassis-number slot slot-number option. This single command starts and finishes the ISSU process. When this command is completed, the ISSU process ends and the ISSU status transitions to Init. No rollback can be performed during the ISSU process.

Task

Command

Remarks

Upgrade the MPU and configure the upgrade images as the startup software images for the MPU.

· Approach 1:
issu load file { boot filename | system filename | feature filename&<1-30> } * chassis chassis-number slot slot-number

· Approach 2:
issu load file ipe ipe-filename chassis chassis-number slot slot-number

Specify the member ID and slot number of the only MPU for the chassis chassis-number slot slot-number option.

Displaying and maintaining ISSU

Execute display commands in any view and reset commands in user view.

In standalone mode:

Task	Command
Display version compatibility information.	display version comp-matrix
Display ISSU status information.	display issu state
Display automatic-rollback timer information.	display issu rollback-timer
Display active software images.	display install active [ slot slot-number ] [ verbose ]
Display inactive software images.	display install inactive [ slot slot-number ] [ verbose ]
Display main startup software images.	display install committed [ slot slot-number ] [ verbose ]
Display backup startup software images.	display install backup [ slot slot-number ] [ verbose ]
Display ISSU logs.	display install log [ log-id ] [ verbose ]
Display software image file information.	display install package { filename \| all } [ verbose ]
Display the software images included in an IPE file.	display install ipe-info ipe-file
Display all software image files that include a specific component or file.	display install which [ slot slot-number ] { component name \| file filename }
Clear ISSU logs.	reset install log-history oldest log-number

In IRF mode:

Task	Command
Display version compatibility information.	display version comp-matrix
Display ISSU status information.	display issu state
Display automatic-rollback timer information.	display issu rollback-timer
Display active software images.	display install active [ chassis chassis-number slot slot-number ] [ verbose ]
Display inactive software images.	display install inactive [ chassis chassis-number slot slot-number ] [ verbose ]
Display main startup software images.	display install committed [ chassis chassis-number slot slot-number ] [ verbose ]
Display backup startup software images.	display install backup [ chassis chassis-number slot slot-number ] [ verbose ]
Display ISSU logs.	display install log [ log-id ] [ verbose ]
Display software image file information.	display install package { filename \| all } [ verbose ]
Display the software images included in an IPE file.	display install ipe-info ipe-file
Display all software image files that include a specific component or file.	display install which [ chassis chassis-number slot slot-number] { component name \| file filename }
Clear ISSU logs.	reset install log-history oldest log-number

ISSU examples for using issu series commands (in standalone mode)

HTTP feature upgrade to a compatible version

Upgrade requirement

Device has two MPUs: one is in slot 0 (active MPU) and the other is in slot 1 (standby MPU).

Upgrade the HTTP feature from R0201 to R0202.

Figure 1 Network diagram

Upgrade procedure

# Download the image file that contains the R0202 HTTP feature from the TFTP server.

<Sysname> tftp 2.2.2.2 get http-r0202.bin

% Total % Received % Xferd Average Speed Time Time Time Current

Dload Upload Total Spent Left Speed

100 256k 100 256k 0 0 764k 0 --:--:-- --:--:-- --:--:-- 810k

# Display active software images.

<Sysname> display install active

Active packages on slot 0:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on slot 0.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on slot 1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on slot 1.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

# Check for the ISSU method to be used for the upgrade and view the possible impact of the upgrade.

<Sysname> display version comp-matrix file feature flash:/http-r0202.bin

Feature image: flash:/http-r0202.bin

Version:

V700R001B34D002

Version Compatibility List:

V700R001B34D001

V700R001B34D002

Version Dependency System List:

V700R001B34D001

V700R001B34D002

Slot Upgrade Way

0 Service Upgrade

0.1 File Upgrade

1 Service Upgrade

1.1 File Upgrade

Influenced service according to following table on slot 0:

flash:/http-r0202.bin

HTTP CFA

Influenced service according to following table on slot 1:

flash:/http-r0202.bin

HTTP CFA

The output shows that an incremental upgrade applies and the HTTP and CFA modules will be rebooted during the upgrade process.

# Upgrade the HTTP feature on the standby MPU.

<Sysname> issu load file feature flash:/http-r0202.bin slot 1

This operation will delete the rollback point information for the previous upgrade and maybe get unsaved configuration lost. Continue? [Y/N]:y

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Slot Upgrade Way

1 Service Upgrade

1.1 File Upgrade

Upgrading software images to compatible versions. Continue? [Y/N]: y

# Perform an active/standby switchover.

<Sysname> issu run switchover

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Slot Switchover Way

0 Active standby process switchover

0.1 Active standby process switchover

Upgrading software images to compatible versions. Continue? [Y/N]: y

# Upgrade the feature on the original active MPU.

<Sysname> issu commit slot 0

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Slot Upgrade Way

0 Service Upgrade

0.1 File Upgrade

Upgrading software images to compatible versions. Continue? [Y/N]: y

# Verify that both MPUs are running the new HTTP image.

<Sysname> display install active

Active packages on slot 0:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on slot 0.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on slot 1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on slot 1.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

HTTP feature upgrade to an incompatible version

Upgrade requirement

Device has two MPUs: one is in slot 0 (active MPU) and the other is in slot 1 (standby MPU).

Upgrade the HTTP feature from R0201 to R0202.

Figure 2 Network diagram

Upgrade procedure

# Download the image file that contains the R0202 HTTP feature from the TFTP server.

<Sysname> tftp 2.2.2.2 get http-r0202.bin

% Total % Received % Xferd Average Speed Time Time Time Current

Dload Upload Total Spent Left Speed

100 256k 100 256k 0 0 764k 0 --:--:-- --:--:-- --:--:-- 810k

# Display active software images.

<Sysname> display install active

Active packages on slot 0:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on slot 0.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on slot 1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on slot 1.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

# Check for the ISSU method to be used for the upgrade and view the possible impact of the upgrade.

<Sysname> display version comp-matrix file feature flash:/http-r0202.bin

Feature image: flash:/http-r0202.bin

Version:

V700R001B34D002

Version Compatibility List:

V700R001B34D002

Version Dependency System List:

V700R001B34D001

V700R001B34D002

Incompatible upgrade.

The output shows that the two versions are incompatible. The relevant cards will be rebooted for the upgrade.

# Load the new HTTP image file to upgrade the HTTP feature.

# Upgrade the HTTP feature on the standby MPU.

<Sysname> issu load file feature flash:/http-r0202.bin slot 1

This operation will delete the rollback point information for the previous upgrade and maybe get unsaved configuration lost. Continue? [Y/N]:y

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Slot Upgrade Way

1 Reboot

1.1 Reboot

Upgrading software images to incompatible versions. Continue? [Y/N]: y

# Upgrade the feature on the original active MPU.

<Sysname> issu run switchover

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Slot Upgrade Way

0 Reboot

0.1 Reboot

Upgrading software images to incompatible versions. Continue? [Y/N]: y

# Verify that both MPUs are running the new HTTP image.

<Sysname> display install active

Active packages on slot 0:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on slot 0.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on slot 1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on slot 1.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

HTTP feature rollback example

Rollback requirement

Device has two MPUs: one is in slot 0 (active MPU) and the other is in slot 1 (standby MPU).

Roll back the HTTP feature from R0202 to R0201 after upgrading it from R0201 to R0202.

Figure 3 Network diagram

Rollback procedure

# Download the image file that contains the R0202 HTTP feature from the TFTP server.

<Sysname> tftp 2.2.2.2 get http-r0202.bin

% Total % Received % Xferd Average Speed Time Time Time Current

Dload Upload Total Spent Left Speed

100 256k 100 256k 0 0 764k 0 --:--:-- --:--:-- --:--:-- 810k

# Display active software images.

<Sysname> display install active

Active packages on slot 0:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on slot 0.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on slot 1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on slot 1.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

# Check for the ISSU method to be used for the upgrade and view the possible impact of the upgrade.

<Sysname> display version comp-matrix file feature flash:/http-r0202.bin

Feature image: flash:/http-r0202.bin

Version:

V700R001B34D002

Version Compatibility List:

V700R001B34D001

V700R001B34D002

Version Dependency System List:

V700R001B34D001

V700R001B34D002

Slot Upgrade Way

0 Service Upgrade

0.1 File Upgrade

1 Service Upgrade

1.1 File Upgrade

Influenced service according to following table on slot 0:

flash:/http-r0202.bin

HTTP CFA

Influenced service according to following table on slot 1:

flash:/http-r0202.bin

HTTP CFA

The output shows that an incremental upgrade applies and the HTTP and CFA modules will be rebooted during the upgrade process.

# Upgrade the HTTP feature on the standby MPU.

<Sysname> issu load file feature flash:/http-r0202.bin slot 1

This operation will delete the rollback point information for the previous upgrade and maybe get unsaved configuration lost. Continue? [Y/N]:y

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Slot Upgrade Way

1 Service Upgrade

1.1 File Upgrade

Upgrading software images to compatible versions. Continue? [Y/N]: y

# Perform an active/standby switchover.

<Sysname> issu run switchover

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Slot Switchover Way

0 Active standby process switchover

0.1 Active standby process switchover

Upgrading software images to compatible versions. Continue? [Y/N]: y

# Display active software images.

<Sysname> display install active

Active packages on slot 0:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on slot 0.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on slot 1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on slot 1.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

# Roll back the HTTP feature to R0201.

<Sysname> issu rollback

This command will quit the ISSU process and roll back to the previous version. Continue? [Y/N]:Y

# Verify that both MPUs are running the old HTTP image.

<Sysname> display install active

Active packages on slot 0:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on slot 0.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on slot 1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on slot 1.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

ISSU examples for using issu series commands (in IRF mode)

HTTP feature upgrade to a compatible version

Upgrade requirement

The IRF fabric comprises two members: the master member with the member ID 1 and the subordinate member with the member ID 2. Each member has one MPU in slot 0 (active MPU) and one MPU in slot 1 (standby MPU).

Upgrade the HTTP feature from R0201 to R0202.

Figure 4 Network diagram

Upgrade procedure

# Download the image file that contains the R0202 HTTP feature from the TFTP server.

<Sysname> tftp 2.2.2.2 get http-r0202.bin

% Total % Received % Xferd Average Speed Time Time Time Current

Dload Upload Total Spent Left Speed

100 256k 100 256k 0 0 764k 0 --:--:-- --:--:-- --:--:-- 810k

# Display active software images.

<Sysname> display install active

Active packages on chassis 1 slot 0:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 1 slot 0.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 1 slot 1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 1 slot 1.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 2 slot 0:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 2 slot 0.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 2 slot 1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 2 slot 1.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

# Check for the ISSU method to be used for the upgrade and view the possible impact of the upgrade.

<Sysname> display version comp-matrix file feature flash:/http-r0202.bin

Feature image: flash:/http-r0202.bin

Version:

V700R001B34D002

Version Compatibility List:

V700R001B34D001

V700R001B34D002

Version Dependency System List:

V700R001B34D001

V700R001B34D002

Chassis Slot Upgrade Way

1 0 Service Upgrade

1 0.1 File Upgrade

1 1 Service Upgrade

1 1.1 File Upgrade

2 0 Service Upgrade

2 0.1 File Upgrade

2 1 Service Upgrade

2 1.1 File Upgrade

Influenced service according to following table on chassis 1 slot 0:

flash:/http-r0202.bin

HTTP CFA

Influenced service according to following table on chassis 1 slot 1:

flash:/http-r0202.bin

HTTP CFA

Influenced service according to following table on chassis 2 slot 0:

flash:/http-r0202.bin

HTTP CFA

Influenced service according to following table on chassis 2 slot 1:

flash:/http-r0202.bin

HTTP CFA

The output shows that an incremental upgrade applies and the HTTP and CFA modules will be rebooted during the upgrade process.

# Upgrade the HTTP feature on the subordinate member.

<Sysname> issu load file feature flash:/http-r0202.bin chassis 2

This operation will delete the rollback point information for the previous upgrade and maybe get unsaved configuration lost. Continue? [Y/N]:y

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Chassis Slot Upgrade Way

2 0 Service Upgrade

2 0.1 File Upgrade

2 1 Service Upgrade

2 1.1 File Upgrade

Upgrading software images to compatible versions. Continue? [Y/N]: y

# Perform a master/subordinate switchover.

<Sysname> issu run switchover

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Chassis Slot Switchover Way

1 0 Active standby process switchover

1 0.1 Active standby process switchover

Upgrading software images to compatible versions. Continue? [Y/N]: y

# Upgrade the feature on the original master.

<Sysname> issu commit chassis 1

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Chassis Slot Upgrade Way

1 0 Service Upgrade

1 1.1 File Upgrade

1 1 Service Upgrade

1 1.1 File Upgrade

Upgrading software images to compatible versions. Continue? [Y/N]: y

# Verify that both members are running the new HTTP image.

<Sysname> display install active

Active packages on chassis 1 slot 0:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on chassis 1 slot 0.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on chassis 1 slot 1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on chassis 1 slot 1.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on chassis 2 slot 0:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on chassis 2 slot 0.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on chassis 2 slot 1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on chassis 2 slot 1.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

HTTP feature upgrade to an incompatible version

Upgrade requirement

Upgrade the HTTP feature from R0201 to R0202.

Figure 5 Network diagram

Upgrade procedure

# Download the image file that contains the R0202 HTTP feature from the TFTP server.

<Sysname> tftp 2.2.2.2 get http-r0202.bin

% Total % Received % Xferd Average Speed Time Time Time Current

Dload Upload Total Spent Left Speed

100 256k 100 256k 0 0 764k 0 --:--:-- --:--:-- --:--:-- 810k

# Display active software images.

<Sysname> display install active

Active packages on chassis 1 slot 0:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 1 slot 0.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 1 slot 1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 1 slot 1.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 2 slot 0:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 2 slot 0.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 2 slot 1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 2 slot 1.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

# Check for the ISSU method to be used for the upgrade and view the possible impact of the upgrade.

<Sysname> display version comp-matrix file feature flash:/http-r0202.bin

Feature image: flash:/http-r0202.bin

Version:

V700R001B34D002

Version Compatibility List:

V700R001B34D002

Version Dependency System List:

V700R001B34D001

V700R001B34D002

Incompatible upgrade.

The output shows that the two versions are incompatible. The cards will be rebooted for the upgrade.

# Upgrade the HTTP feature on the subordinate member. After the upgrade, the subordinate member will leave the original IRF fabric and form a new IRF fabric by itself.

<Sysname> issu load file feature flash:/http-r0202.bin chassis 2

This operation will delete the rollback point information for the previous upgrade and maybe get unsaved configuration lost. Continue? [Y/N]:y

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Chassis Slot Upgrade Way

2 0 Reboot

2 0.1 Reboot

2 1 Reboot

2 1.1 Reboot

Upgrading software images to incompatible versions. Continue? [Y/N]: y

# Perform a master/subordinate switchover to upgrade the original master. The original master will reboot and join the new IRF fabric.

<Sysname> issu run switchover

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Chassis Slot Upgrade Way

1 0 Reboot

1 0.1 Reboot

1 1 Reboot

1 1.1 Reboot

Upgrading software images to incompatible versions. Continue? [Y/N]: y

# Verify that both members are running the new HTTP image.

<Sysname> display install active

Active packages on chassis 1 slot 0:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on chassis 1 slot 0.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on chassis 1 slot 1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on chassis 1 slot 1.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on chassis 2 slot 0:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on chassis 2 slot 0.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on chassis 2 slot 1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on chassis 2 slot 1.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

HTTP feature rollback example

Rollback requirement

Roll back the HTTP feature from R0202 to R0201 after upgrading it from R0201 to R0202.

Figure 6 Network diagram

Upgrade procedure

# Download the image file that contains the R0202 HTTP feature from the TFTP server.

<Sysname> tftp 2.2.2.2 get http-r0202.bin

% Total % Received % Xferd Average Speed Time Time Time Current

Dload Upload Total Spent Left Speed

100 256k 100 256k 0 0 764k 0 --:--:-- --:--:-- --:--:-- 810k

# Display active software images.

<Sysname> display install active

Active packages on chassis 1 slot 0:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 1 slot 0.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 1 slot 1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 1 slot 1.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 2 slot 0:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 2 slot 0.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 2 slot 1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 2 slot 1.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

# Check for the ISSU method to be used for the upgrade and view the possible impact of the upgrade.

<Sysname> display version comp-matrix file feature flash:/http-r0202.bin

Feature image: flash:/http-r0202.bin

Version:

V700R001B34D002

Version Compatibility List:

V700R001B34D001

V700R001B34D002

Version Dependency System List:

V700R001B34D001

V700R001B34D002

Chassis Slot Upgrade Way

1 0 Service Upgrade

1 0.1 File Upgrade

1 1 Service Upgrade

1 1.1 File Upgrade

2 0 Service Upgrade

2 0.1 File Upgrade

2 1 Service Upgrade

2 1.1 File Upgrade

Influenced service according to following table on chassis 1 slot 0:

flash:/http-r0202.bin

HTTP CFA

Influenced service according to following table on chassis 1 slot 1:

flash:/http-r0202.bin

HTTP CFA

Influenced service according to following table on chassis 2 slot 0:

flash:/http-r0202.bin

HTTP CFA

Influenced service according to following table on chassis 2 slot 1:

flash:/http-r0202.bin

HTTP CFA

The output shows that an incremental upgrade applies and the HTTP and CFA modules will be rebooted during the upgrade process.

# Upgrade the HTTP feature on the subordinate member.

<Sysname> issu load file feature flash:/http-r0202.bin chassis 2

This operation will delete the rollback point information for the previous upgrade and maybe get unsaved configuration lost. Continue? [Y/N]:y

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Chassis Slot Upgrade Way

2 0 Service Upgrade

2 0.1 File Upgrade

2 1 Service Upgrade

2 1.1 File Upgrade

Upgrading software images to compatible versions. Continue? [Y/N]: y

# Perform a master/subordinate switchover.

<Sysname> issu run switchover

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Chassis Slot Switchover Way

1 0 Active standby process switchover

1 0.1 Active standby process switchover

Upgrading software images to compatible versions. Continue? [Y/N]: y

# Display active software images.

<Sysname> display install active

Active packages on chassis 1 slot 0:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 1 slot 0.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 1 slot 1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 1 slot 1.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 2 slot 0:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on chassis 2 slot 0.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on chassis 2 slot 1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on chassis 2 slot 1.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

# Roll back the HTTP feature to R0201.

<Sysname> issu rollback

This command will quit the ISSU process and roll back to the previous version. Continue? [Y/N]: Y

# Verify that both members are running the old HTTP image.

<Sysname> display install active

Active packages on chassis 1 slot 0:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 1 slot 0.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 1 slot 1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 1 slot 1.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 2 slot 0:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 2 slot 0.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 2 slot 1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 2 slot 1.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Performing an ISSU by using install series commands

Performing an ISSU

Obtaining the software images issued in an IPE file

1. Use FTP or TFTP to download or upload the IPE file to the root directory of a storage medium on the active MPU (in standalone mode) or global active MPU (in IRF mode).

2. Use the display install ipe-info command to view which software images are included in the IPE file.

3. Decompress the IPE file by using the following command in user view:

Task	Command
Decompress an IPE file.	install add ipe-file medium-name:

Installing or upgrading software images

When shipped, the device is installed with a boot image, a system image, and some feature images (if any). To upgrade the device software, you might need to perform one or more of the following tasks:

· Upgrade the boot image.

· Upgrade the system image.

· Install new feature images.

· Upgrade the existing feature images.

· Install patch images.

All these tasks can be implemented by using the install activate command. If you use this command for an image that does not exist on the device, you install the image. If you use this command for an image that already exists on the device, you upgrade the image.

Installation and upgrade prerequisites

See "ISSU prerequisites."

Installation and upgrade guidelines

To install or upgrade software images, you must follow the following guidelines as well as the guidelines described in "ISSU restrictions and guidelines":

· To install a new feature image or patch image in standalone mode, you must install it on the active MPU first. To upgrade an image, you must upgrade the image on the standby MPU first.

· To install an image in IRF mode, you must install the image on the master first. To install an image on a member, you must install the image on the active MPU first.

· To upgrade an image in IRF mode, you must upgrade the image on one subordinate member first. To upgrade an image on a member, you must upgrade the image on the standby MPU first.

· When you install or upgrade a software image on the active MPU, the system automatically installs or upgrades the software image on the service cards as needed. You do not need to install or upgrade the software of the service cards separately.

Installation and upgrade procedure

To install or upgrade a boot image, a system image, or feature images, execute the following commands in user view:

Step	Command	Remarks
1. (Optional.) Check for the ISSU method to be used for the upgrade and the possible impact of the upgrade.	· In standalone mode: install activate { boot filename \| system filename \| feature filename&<1-30> } * slot slot-number test · In IRF mode: install activate { boot filename \| system filename \| feature filename&<1-30> } * chassis chassis-number slot slot-number test	N/A
2. Activate the images.	· In standalone mode: install activate { boot filename \| system filename \| feature filename&<1-30> } * slot slot-number · In IRF mode: install activate { boot filename \| system filename \| feature filename&<1-30> } * chassis chassis-number slot slot-number	An image takes effect only after it is activated.
3. (Optional.) Confirm the software changes.	install commit	To keep activated images effective after a reboot, you must confirm the software changes.

To install or upgrade patch images, execute the following commands in user view:

Step	Command	Remarks
1. Activate the patch images.	· In standalone mode: install activate patch filename slot slot-number · In IRF mode: install activate patch filename chassis chassis-number slot slot-number	An image takes effect only after it is activated.
2. (Optional.) Confirm the software changes.	install commit	To keep activated images effective after a reboot, you must confirm the software changes.

Step

Command

Remarks

1. Activate the patch images.

· In standalone mode:
install activate patch filename slot slot-number

· In IRF mode:
install activate patch filename chassis chassis-number slot slot-number

An image takes effect only after it is activated.

2. (Optional.) Confirm the software changes.

install commit

To keep activated images effective after a reboot, you must confirm the software changes.

Uninstalling feature or patch images

You can uninstall only feature images and patch images from the device. Boot and system images cannot be uninstalled.

Uninstalled images are still saved on the storage medium. To permanently remove the images from the device, execute the install remove command. Make sure you remove only images that are no longer useful.

To uninstall an image that was installed for an incremental upgrade, deactivate it and then confirm the software change. If you do not confirm the deactivation, the deactivated image will become active after a reboot. To uninstall an image that was installed for a reboot upgrade or ISSU reboot upgrade, you only need to deactivate it.

To uninstall feature images, execute the following commands in user view:

Step	Command
1. Deactivate feature images.	· In standalone mode: install deactivate feature filename&<1-30> slot slot-number · In IRF mode: install deactivate feature filename&<1-30> chassis chassis-number slot slot-number
2. (Optional.) Confirm the software changes.	install commit

Step

Command

1. Deactivate feature images.

· In standalone mode:
install deactivate feature filename&<1-30> slot slot-number

· In IRF mode:
install deactivate feature filename&<1-30> chassis chassis-number slot slot-number

2. (Optional.) Confirm the software changes.

install commit

To uninstall patch images, execute the following commands in user view:

Step	Command
1. Deactivate patch images.	· In standalone mode: install deactivate patch filename slot slot-number · In IRF mode: install deactivate patch filename chassis chassis-number slot slot-number
2. (Optional.) Confirm the software changes.	install commit

Step

Command

1. Deactivate patch images.

· In standalone mode:
install deactivate patch filename slot slot-number

· In IRF mode:
install deactivate patch filename chassis chassis-number slot slot-number

2. (Optional.) Confirm the software changes.

install commit

Rolling back the software configuration

Every time you activate or deactivate a software image for an incremental upgrade or downgrade, the system creates a rollback point to record the current software configuration. Before you execute the install commit command to confirm the software changes (executing this command also removes all rollback points), you can roll back the software configuration to a rollback point to cancel all software image upgrade-related operations performed after the rollback point. You can also roll back the software configuration to the original software configuration, the software configuration before you perform an ISSU.

For an incremental upgrade, up to 50 rollback points are supported. After the limit is reached, the oldest rollback point is deleted to make room for a newly created one.

For ISSU reboot upgrades and reboot upgrades, the system does not record and maintain any rollback point, and you can roll back the software configuration only to the original software configuration.

To make a rollback for an incremental upgrade take effect after a reboot, you must confirm the rollback operation using the install commit command. A rollback for a reboot upgrade or an ISSU reboot upgrade does not need to be confirmed by using the install commit command.

To roll back the software configuration, execute the following commands in user view:

Step	Command	Remarks
1. Roll back the software configuration to an earlier rollback point or the original software configuration.	install rollback to { point-id \| original }	To view available rollback points, use the display install rollback command.
2. (Optional.) Confirm the software changes.	install commit	N/A

Aborting a software image operation

When the system is activating or deactivating a software image for an incremental upgrade, you can press Ctrl+C or use the install abort [ job-id ] command in user view to abort the operation.

After you abort an operation, the system runs with the software images that it used before the activate or deactivate operation.

Verifying the software change confirmation status and software image integrity and consistency

If some software images are not integral or some activated/deactivated software images are not confirmed, a switchover might not occur as expected, and the MPUs might run different versions of software images after a reboot or even cannot restart up correctly. (In standalone mode.)

To solve the problem, download and install the software images again to ensure software integrity, or use the install activate, install deactivate, and install commit commands as appropriate to guarantee software image consistency.

To check the integrity and consistency of software images, execute the following command in user view:

Task	Command
Verify the software change confirmation status and software image integrity and consistency.	install verify

Removing inactive software images

You can remove inactive software images from the device.

IMPORTANT:

Removing a software image deletes the image file from the device permanently. This operation can neither be reverted by using the install rollback to command nor be aborted by using the install abort command. Make sure you remove only images that are no longer useful.

To remove inactive software images, execute one of the following commands as appropriate in user view:

Task	Command
Remove inactive software images. (In standalone mode.)	install remove [ slot slot-number ] { package \| inactive }
Remove inactive software images. (In IRF mode.)	install remove [ chassis chassis-number slot slot-number ] { package \| inactive }

Displaying and maintaining ISSU

Execute display commands in any view and reset commands in user view.

In standalone mode:

Task	Command
Display active software images.	display install active [ slot slot-number ] [ verbose ]
Display inactive software images.	display install inactive [ slot slot-number ] [ verbose ]
Display main startup software images.	display install committed [ slot slot-number ] [ verbose ]
Display backup startup software images.	display install backup [ slot slot-number ] [ verbose ]
Display ongoing ISSU activate, deactivate, and rollback operations.	display install job
Display ISSU logs.	display install log [ log-id ] [ verbose ]
Display software image file information.	display install package { filename \| all } [ verbose ]
Display the software images included in an IPE file.	display install ipe-info ipe-file
Display rollback point information.	display install rollback [ point-id ]
Display all software image files that include a specific component or file.	display install which { component name \| file filename } [ slot slot-number ]
Clear ISSU logs.	reset install log-history oldest log-number
Clear ISSU rollback points.	reset install rollback oldest point-id

In IRF mode:

Task	Command
Display active software images.	display install active [ chassis chassis-number slot slot-number ] [ verbose ]
Display inactive software images.	display install inactive [ chassis chassis-number slot slot-number ] [ verbose ]
Display main startup software images.	display install committed [ chassis chassis-number slot slot-number ] [ verbose ]
Display backup startup software images.	display install backup [ chassis chassis-number slot slot-number ] [ verbose ]
Display ongoing ISSU activate, deactivate, and rollback operations.	display install job
Display ISSU logs.	display install log [ log-id ] [ verbose ]
Display software image file information.	display install package { filename \| all } [ verbose ]
Display the software images included in an IPE file.	display install ipe-info ipe-file
Display rollback point information.	display install rollback [ point-id ]
Display all software image files that include a specific component or file.	display install which { component name \| file filename } [ chassis chassis-number slot slot-number]
Clear ISSU logs.	reset install log-history oldest log-number
Clear ISSU rollback points.	reset install rollback oldest point-id

ISSU examples for using install series commands (in standalone mode)

HTTP feature upgrade example

Upgrade requirement

Device has two MPUs: one is in slot 0 (active MPU) and the other is in slot 1 (standby MPU).

Upgrade the HTTP feature from R0201 to R0202.

Figure 7 Network diagram

Upgrade procedure

# Download the IPE file that contains the R0202 HTTP feature image from the TFTP server.

<Sysname> tftp 2.2.2.2 get http-r0202.ipe

% Total % Received % Xferd Average Speed Time Time Time Current

Dload Upload Total Spent Left Speed

100 256k 100 256k 0 0 764k 0 --:--:-- --:--:-- --:--:-- 810k

# Decompress the IPE file.

<Sysname> install add flash:/http-r0202.ipe flash:/

# Display active software images.

<Sysname> display install active

Active packages on slot 0:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on slot 0.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on slot 1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on slot 1.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

# Check for the ISSU methods to be used for the upgrade and view the possible impact of the upgrade.

<Sysname> install activate feature flash:/http-r0202.bin slot 1 test

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Slot Upgrade Way

1 Service Upgrade

1.1 File Upgrade

Influenced service according to following table on slot 1:

flash:/http-r0202.bin

HTTP CFA

<Sysname> install activate feature flash:/http-r0202.bin slot 0 test

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Slot Upgrade Way

0 Service Upgrade

0.1 File Upgrade

1 Service Upgrade

1.1 File Upgrade

Influenced service according to following table on slot 0:

flash:/http-r0202.bin

HTTP CFA

The output shows that both MPUs need a service upgrade and the HTTP and CFA modules will be rebooted during the upgrade process.

# Activate the HTTP image to upgrade the HTTP feature.

<Sysname> install activate feature flash:/http-r0202.bin slot 1

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Slot Upgrade Way

1 Service Upgrade

1.1 File Upgrade

Upgrading software images to compatible versions. Continue? [Y/N]: y

<Sysname> install activate feature flash:/http-r0202.bin slot 0

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Slot Upgrade Way

0 Service Upgrade

0.1 File Upgrade

1 Service Upgrade

1.1 File Upgrade

Upgrading software images to compatible versions. Continue? [Y/N]: y

# Verify that the new HTTP image has been activated.

<Sysname> display install active

Active packages on slot 0:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on slot 0.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on slot 1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on slot 1.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

# Confirm the software change.

<Sysname> install commit

HTTP feature rollback example

Rollback requirement

As shown in Figure 7, Device has two MPUs: one is in slot 0 (active MPU) and the other is in slot 1 (standby MPU).

Roll back the HTTP feature from R0202 to R0201.

Rollback procedure

# Display active software images.

<Sysname> display install active

Active packages on slot 0:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on slot 0.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on slot 1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on slot 1.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

# Display available rollback points.

<Sysname> display install rollback

Install rollback information 1 on slot 0:

Updating from flash:/http-r0201.bin

to flash:/http-r0202.bin.

Install rollback information 2 on slot 1:

Updating from flash:/http-r0201.bin

to flash:/http-r0202.bin.

# Roll back the HTTP feature to R0201.

<Sysname> install rollback to original

# Display active software images.

<Sysname> display install active

Active packages on slot 0:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on slot 0.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on slot 1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on slot 1.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.binn

# Confirm the software change.

<Sysname> install commit

ISSU examples for using install series commands (in IRF mode)

HTTP feature upgrade example

Upgrade requirement

Upgrade the HTTP feature from R0201 to R0202.

Figure 8 Network diagram

Upgrade procedure

# Download the IPE file that contains the R0202 HTTP feature image from the TFTP server.

<Sysname> tftp 2.2.2.2 get http-r0202.ipe

% Total % Received % Xferd Average Speed Time Time Time Current

Dload Upload Total Spent Left Speed

100 256k 100 256k 0 0 764k 0 --:--:-- --:--:-- --:--:-- 810k

# Decompress the IPE file.

<Sysname> install add flash:/http-r0202.ipe flash:

# Display active software images.

<Sysname> display install active

Active packages on chassis 1 slot 0:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 1 slot 0.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 1 slot 1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 1 slot 1.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 2 slot 0:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 2 slot 0.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 2 slot 1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 2 slot 1.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

# Check for the ISSU methods to be used for the upgrade and view the possible impact of the upgrade.

<Sysname> install activate feature flash:/http-r0202.bin chassis 2 slot 1 test

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Chassis Slot Upgrade Way

2 1 Service Upgrade

2 1.1 File Upgrade

Influenced service according to following table on chassis 2 slot 1:

flash:/http-r0202.bin

HTTP CFA

<Sysname> install activate feature flash:/http-r0202.bin chassis 2 slot 0 test

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Chassis Slot Upgrade Way

2 0 Service Upgrade

2 0.1 File Upgrade

Influenced service according to following table on chassis 2 slot 0:

flash:/http-r0202.bin

HTTP CFA

<Sysname> install activate feature flash:/http-r0202.bin chassis 1 slot 1 test

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Chassis Slot Upgrade Way

1 1 Service Upgrade

1 1.1 File Upgrade

Influenced service according to following table on chassis 1 slot 1:

flash:/http-r0202.bin

HTTP CFA

<Sysname> install activate feature flash:/http-r0202.bin chassis 1 slot 0 test

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Chassis Slot Upgrade Way

1 0 Service Upgrade

1 0.1 File Upgrade

Influenced service according to following table on chassis 1 slot 0:

flash:/http-r0202.bin

HTTP CFA

The output shows that all the MPUs need a service upgrade and the HTTP and CFA modules will be rebooted during the upgrade process.

# Activate the HTTP image to upgrade the HTTP feature.

<Sysname> install activate feature flash:/http-r0202.bin chassis 2 slot 1

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Chassis Slot Upgrade Way

2 1 Service Upgrade

2 1.1 File Upgrade

Upgrading software images to compatible versions. Continue? [Y/N]: y

<Sysname> install activate feature flash:/http-r0202.bin chassis 2 slot 0

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Chassis Slot Upgrade Way

2 0 Service Upgrade

2 0.1 File Upgrade

Upgrading software images to compatible versions. Continue? [Y/N]: y

<Sysname> install activate feature flash:/http-r0202.bin chassis 1 slot 1

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Chassis Slot Upgrade Way

1 1 Service Upgrade

1 1.1 File Upgrade

Upgrading software images to compatible versions. Continue? [Y/N]: y

<Sysname> install activate feature flash:/http-r0202.bin chassis 1 slot 0

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Chassis Slot Upgrade Way

1 0 Service Upgrade

1 0.1 File Upgrade

Upgrading software images to compatible versions. Continue? [Y/N]: y

# Verify that the new HTTP image has been activated.

<Sysname> display install active

Active packages on chassis 1 slot 0:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on chassis 1 slot 0.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on chassis 1 slot 1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on chassis 1 slot 1.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on chassis 2 slot 0:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on chassis 2 slot 0.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on chassis 2 slot 1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on chassis 2 slot 1.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

# Confirm the software change.

<Sysname> install commit

HTTP feature rollback example

Rollback requirement

As shown in Figure 8, the IRF fabric comprises two members: the master member with the member ID 1 and the subordinate member with the member ID 2. Each member has one MPU in slot 0 (active MPU) and one MPU in slot 1 (standby MPU).

Roll back the HTTP feature from R0202 to R0201.

Rollback procedure

# Display active software images.

<Sysname> display install active

Active packages on chassis 1 slot 0:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on chassis 1 slot 0.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on chassis 1 slot 1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on chassis 1 slot 1.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on chassis 2 slot 0:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on chassis 2 slot 0.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on chassis 2 slot 1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on chassis 2 slot 1.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

# Display available rollback points.

<Sysname> display install rollback

Install rollback information 1 on chassis 1 slot 0:

Updating from flash:/http-r0201.bin

to flash:/http-r0202.bin.

Install rollback information 2 on chassis 1 slot 1:

Updating from flash:/http-r0201.bin

to flash:/http-r0202.bin.

Install rollback information 3 on chassis 2 slot 0:

Updating from flash:/http-r0201.bin

to flash:/http-r0202.bin.

Install rollback information 4 on chassis 2 slot 1:

Updating from flash:/http-r0201.bin

to flash:/http-r0202.bin.

# Roll back the HTTP feature to R0201.

<Sysname> install rollback to original

# Display active software images.

<Sysname> display install active

Active packages on chassis 1 slot 0:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 1 slot 0.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 1 slot 1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 1 slot 1.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 2 slot 0:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 2 slot 0.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 2 slot 1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 2 slot 1.1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

# Confirm the software change.

<Sysname> install commit

01-Fundamentals Configuration Guide

Performing an ISSU in standalone mode

ISSU examples for using issu series commands (in standalone mode)

Upgrade requirement

Upgrade procedure

Upgrade requirement

Upgrade procedure

Rollback requirement

Rollback procedure

ISSU examples for using issu series commands (in IRF mode)

Upgrade requirement

Upgrade procedure

Upgrade requirement

Upgrade procedure

Rollback requirement

Upgrade procedure

Obtaining the software images issued in an IPE file

Installation and upgrade prerequisites

Installation and upgrade guidelines

Installation and upgrade procedure

Upgrade requirement

Upgrade procedure

HTTP feature rollback example

Rollback requirement

Rollback procedure

ISSU examples for using install series commands (in IRF mode)

Upgrade requirement

Upgrade procedure

HTTP feature rollback example

Rollback requirement

Rollback procedure

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program

Global Learning

Partner Sales Resources

Service Business

News & Events

Contact Us