· Separation of service features from basic functions—Device software is segmented into boot, system, and feature images. The images can be upgraded individually.

· Independence between service features—Features run independently. One feature can be added or upgraded without affecting the operation of the system or other features.

· Support for hotfix—Patch images are available to fix system bugs without a system reboot.

· Hardware redundancy—On a dual-MPU device or a multichassis IRF fabric, one MPU can be upgraded while other MPUs are providing services.

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

NOTE:

To minimize downtime, H3C recommends that you install at least two MPUs. This is important for the reboot method. If there is only one MPU, service interruption is not avoidable.

Table 1 shows the ISSU methods for different scenarios. These ISSU methods use different upgrade procedures and have different impact on the running services. The key to a successful ISSU is to use the recommended method and follow the correct procedure.

Before an ISSU, use the display version comp-matrix file command to view compatibility between the old and new software versions and identify the recommended ISSU method.

· For a compatible version, the recommended ISSU method is indicated by the Upgrade Way field.

· For an incompatible version, the recommended ISSU method "Incompatible upgrade" is displayed after the version dependency information.

For more information about the correct procedures for using these methods, see "Performing an ISSU by using issu series commands" and "Performing an ISSU by using install series commands."

Table 1 ISSU methods

ISSU method		Application scenario	ISSU method indicated by the display version comp-matrix file command
Incremental upgrade	Service-level	Upgrade to a compatible version	Service Upgrade
Incremental upgrade	File-level	Upgrade to a compatible version	File Upgrade
ISSU reboot		Upgrade to a compatible version	ISSU Reboot
Reboot		Upgrade to a compatible version	Reboot Sequence Reboot
Incompatible upgrade		Upgrade to an incompatible version	Incompatible upgrade

ISSU methods for a compatible version

The following are ISSU methods for a compatible version:

· 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 can provide services during the upgrade.

¡ File-level incremental upgrade—This method involves only hidden system program files. The system can operate and provide services 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 memory and uses the new software to reboot the CPU. During an ISSU reboot upgrade, the data 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 meet the requirements.

Compared with an incremental upgrade, an ISSU reboot upgrade affects all modules that use the CPU and takes a longer time.

· Reboot (in standalone mode).

A reboot upgrade reboots cards to load the new software.

If the device has two MPUs and both MPUs need to be rebooted for the 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 module might be Sequence Reboot. This method reboots one switching fabric module at a time and proceeds to reboot another switching fabric module only when the previously upgraded one restarts up. This method can implement in-service switching fabric module upgrade when the device has multiple switching fabric modules that support this method.

· Reboot (in IRF mode).

A reboot upgrade reboots cards to load the new software.

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

ISSU method for an incompatible version

The incompatible upgrade method is the only method for an ISSU to an incompatible version. This method reboots the device to load the new software. To reduce service interruption during the upgrade, implement redundant hardware.

ISSU command series

To perform an ISSU, you can use either of the install series commands or the issu series commands.

Table 2 Comparison between the two command series

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 card.
Effect scope of the upgrade operation	Large.	Small.
Technical skill requirements	Low, suitable for 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.

Preparing for an ISSU

To ensure a successful ISSU, read this chapter carefully before you perform an ISSU, and make sure all requirements in this chapter are met.

Hardware restrictions

ISSU reboot is not supported on an LPU that has 512 MB of storage space.

If the device supports sequential upgrade for switching fabric modules, you must make sure the device has at least two correctly operating switching fabric modules.

ISSU prerequisites

Before you perform an ISSU, complete the following tasks:

1. Read the software release notes to verify the following items:

¡ The software images to be used for the upgrade.

¡ Compatibility between the new software images.

¡ Compatibility between the new software images and the running software images.

¡ Licensing requirements for the new software images.

2. If the new software images require licenses, make sure the device has the required licenses.

¡ When you install a license, the system automatically searches the storage media for feature images covered by the license. If only one image is found, the system automatically installs the image. If two or more images are found, the system automatically installs the image found first.

¡ When you uninstall a license, the system automatically searches for the images of the license and uninstalls the running ones.

To manage a license whose activation file is locked to the device, make sure one of the following requirements are met:

¡ Both the active and standby MPUs are in position.

¡ Only the active MPU is in position, but the standby MPUs have operated for at least 24 hours after the license operation.

If neither of the requirements are met before you manage licenses, license management operations might fail.

For more information about license management, see "Managing licenses."

3. Use the display device command to verify that the system is operating correctly. If there are any problems with the system, troubleshoot the system before performing an ISSU.

4. Use the display mdc command to verify that all MDCs are in active state.

5. Verify that the storage media on the MPUs have sufficient free space for the new image files.

6. Verify that the following settings are configured:

Feature	Setting requirements
BFD	BFD is disabled for protocols including LDP, RSVP, OSPF, ISIS, RIP, BGP, VRRP, and NQA.
GR/NSR	GR or NSR is enabled for protocols including LDP, RSVP, OSPF, ISIS, BGP, and FSPF.
Ethernet link aggregation	Long LACP timeout interval is used (the lacp period short command is not configured) on all member ports in dynamic aggregation groups.
IRF	Configure IRF bridge MAC persistence as follows: · To upgrade an IRF fabric to a compatible version, configure the irf mac-address persistent timer or irf mac-address persistent always command. · To upgrade the IRF fabric to an incompatible version, configure the irf mac-address persistent always command if the bridge MAC address is the MAC address of the device for which you want to execute the issu load command.

7. If a feature is not supported in the new images, delete all relevant configurations.

To uninstall an image, delete the configurations for the image and save the running configuration.

8. Use the save command to save the running configuration.

9. Use FTP or TFTP to transfer the upgrade software image files to the device:

¡ In standalone mode, save the files to the root directory of the active MPU's storage medium. The system automatically copies the files when it upgrade the standby MPU.

¡ In IRF mode, save the files to the root directory of the global active MPU's storage medium. The system automatically copies the files when it upgrades the standby MPUs.

10. Use the display version comp-matrix command to verify the compatibility between the new and old images. If they are compatible, you can use the install series or issu series commands. If they are not compatible, you can only use the issu series commands.

NOTE:

You cannot use both install and issu series commands for one ISSU process. However, you can use the display install and reset install commands when you use the issu series commands to upgrade software.

11. Verify that the device is not in the process of a hardware upgrade and does not have a hardware problem.

12. Log in to the device through the console port.

If you use Telnet or SSH, you might be disconnected from the device before the ISSU is completed.

Performing an ISSU by using issu series commands

ISSU guidelines

During an ISSU, use the following guidelines:

· In a multiuser environment, make sure no other administrators access the device while you are performing an ISSU.

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

· Do not execute any commands that are not for the ISSU.

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

· You only need to perform the upgrade on the default MDC. The system completes software upgrade for all the other MDCs automatically.

· You may use issu commands to upgrade all or some of the software images. If you are upgrading only some of the images, make sure the new images are compatible with the images that are not to be upgraded. The upgrade will fail if a conflict exists.

· In an IRF fabric, a subordinate device automatically synchronizes the master device's configuration and status data. You must wait for the synchronization to complete before using the issu load command on the subordinate device. To check the synchronization progress, use the display device and display mdc commands. The synchronization is completed when the following requirements are met:

¡ All cards of the subordinate device are in normal state.

¡ All MDCs are in active state.

· Use the switchto mdc command to check whether an automatic configuration process is in progress. If the message Automatic configuration is running, press CTRL_C or CTRL_D to break. appears, an automatic configuration process is in progress. To perform an ISSU, wait for the process to complete or abort the process. For more information about automatic configuration, see "Using automatic configuration."

· After an ISSU, you must log in to the device again before you can configure the device.

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 LPUs and switching fabric modules as needed. You do not need to install or upgrade the software of the LPUs and switching fabric modules separately.

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

Performing an ISSU for a dual-MPU device

Before upgrade, use the display version comp-matrix file command to verify the compatibility between the new and old images and identify the recommended upgrade methods.

· 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:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. (Optional.) Set the automatic rollback timer.	issu rollback-timer minutes	By default, the automatic-rollback interval is 45 minutes. This timer starts 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 images.
3. Return to user view.	quit	N/A
4. Upgrade the standby MPU and configure the upgrade images as the main startup software images for the standby MPU.	· Use .bin files: issu load file { boot filename \| system filename \| feature filename&<1-30> } * slot slot-number · Use an .ipe file: issu load file ipe ipe-filename slot slot-number	Specify the slot number of the standby MPU for the slot slot-number option.
5. Perform an active/standby switchover and upgrade the LPUs and switching fabric modules.	issu run switchover	N/A
6. (Optional.) Accept the upgrade and delete the automatic-rollback timer.	issu accept	N/A
7. Complete the ISSU process or roll back to the original software images.	· To upgrade the original active MPU and complete the ISSU: issu commit slot slot-number · To roll back to the original software images: 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 to roll back to the original software images. 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.	· Use .bin files: issu load file { boot filename \| system filename \| feature filename&<1-30> } * slot slot-number · Use an .ipe file: 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 images.	· 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 images: 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 images. 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.

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

· Use an .ipe file:
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 images.

· 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 images:
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 images. 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 command to verify the compatibility between the new and old images and identify the recommended upgrade methods.

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

· If the value of the Upgrade Way field is Service Upgrade or File Upgrade, an incremental upgrade is recommended.

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.	· Use .bin files: issu load file { boot filename \| system filename \| feature filename&<1-30> } * slot slot-number · Use an .ipe file: issu load file ipe ipe-filename slot slot-number	N/A
2. Complete the ISSU process or roll back to the original software images.	· To complete the ISSU process: issu commit slot slot-number · To roll back to the original software images: issu rollback	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 images. 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.

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

· Use an .ipe file:
issu load file ipe ipe-filename slot slot-number

N/A

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

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

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

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.	· Use .bin files: issu load file { boot filename \| system filename \| feature filename&<1-30> } * slot slot-number · Use an .ipe file: 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.

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

· Use an .ipe file:
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 number of member devices. For an IRF fabric with a single member, the ISSU procedure varies by number of MPUs.

Performing an ISSU for a multichassis IRF fabric

ISSU for a multichassis 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.

Before upgrade, use the display version comp-matrix file command to verify the compatibility between the new and old images and identify the recommended upgrade methods.

· 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:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. (Optional.) Set the automatic rollback timer.	issu rollback-timer minutes	By default, the automatic-rollback interval is 45 minutes. This timer starts 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 images.
3. Return to user view.	quit	N/A
4. Upgrade subordinate members and configure the upgrade images as the main startup software images for the subordinate members.	· Use .bin files: issu load file { boot filename \| system filename \| feature filename&<1-30> } * chassis chassis-number · Use an .ipe file: 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.
5. Perform a master/subordinate switchover.	issu run switchover	N/A
6. (Optional.) Accept the upgrade and delete the automatic-rollback timer.	issu accept	N/A
7. Complete the ISSU process or roll back to the original software images.	· To complete the ISSU process, upgrade the subordinate members that have not been upgraded (including the original master) using the following command: issu commit chassis chassis-number · To roll back to the original software images: 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 to roll back to the original software images. 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.	· Use .bin files: issu load file { boot filename \| system filename \| feature filename&<1-30> } * chassis chassis-number&<1-3> · Use an .ipe file: 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 that you specify 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 images.	· To complete the ISSU process, perform a master/subordinate switchover to upgrade all members that have not been upgraded: issu run switchover · To roll back to the original software images: 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 to manually roll back to the original software images. 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.

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

· Use an .ipe file:
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 that you specify 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 images.

· To complete the ISSU process, perform a master/subordinate switchover to upgrade all members that have not been upgraded:
issu run switchover

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

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

Performing an ISSU for a dual-MPU single-chassis 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.

Before upgrade, use the display version comp-matrix file command to verify the compatibility between the new and old images and identify the recommended upgrade methods.

· 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:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. (Optional.) Set the automatic rollback timer.	issu rollback-timer minutes	By default, the automatic-rollback interval is 45 minutes. This timer starts 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 images.
3. Return to user view.	quit	N/A
4. Upgrade the global standby MPU and configure the upgrade images as the startup software images for the MPU.	· Use .bin files: issu load file { boot filename \| system filename \| feature filename&<1-30> } * chassis chassis-number slot slot-number · Use an .ipe file: 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.
5. Perform an active/standby switchover and upgrade the LPUs and switching fabric modules.	issu run switchover	N/A
6. (Optional.) Accept the upgrade and delete the automatic-rollback timer.	issu accept	N/A
7. Complete the ISSU process or roll back to the original software images.	· 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 images: issu rollback	Specify the member ID and slot number of the original global active 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, you can use the issu rollback command to roll back to the original software images. 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.	· Use .bin files: 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 images.	· To upgrade the original global active MPU, the LPUs, and the switching fabric modules, and complete the ISSU process: issu run switchover · To roll back to the original software images: 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 to manually roll back to the original software images. 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.

· Use .bin files:
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 images.

· To upgrade the original global active MPU, the LPUs, and the switching fabric modules, and complete the ISSU process:
issu run switchover

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

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

Performing an ISSU for a single-MPU single-chassis IRF fabric

Before upgrade, use the display version comp-matrix file command to verify the compatibility between the new and old images and identify the recommended upgrade methods.

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

· If the value of the Upgrade Way field is Service Upgrade or File Upgrade, an incremental upgrade is recommended.

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.	· Use .bin files: issu load file { boot filename \| system filename \| feature filename&<1-30> } * chassis chassis-number slot slot-number · Use an .ipe file: 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 images.	· To complete the ISSU process: issu commit chassis chassis-number slot slot-number · To roll back to the original software images: 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 images. 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.

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

· Use an .ipe file:
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 images.

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

· To roll back to the original software images:
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.	· Use .bin files: issu load file { boot filename \| system filename \| feature filename&<1-30> } * chassis chassis-number slot slot-number · Use an .ipe file: 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.

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

· Use an .ipe file:
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

The display and reset commands described in this section apply to all ISSU processes, regardless of whether the install or issu series commands are used.

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

In standalone mode:

Task	Command	Remarks
Display version compatibility information.	display version comp-matrix	N/A
Display ISSU status and upgrade related information.	display issu state	This command applies only to an ISSU that uses the issu series commands.
Display automatic-rollback timer information.	display issu rollback-timer	N/A
Display active software images.	display install active [ slot slot-number ] [ verbose ]	N/A
Display inactive software images.	display install inactive [ slot slot-number ] [ verbose ]	N/A
Display main startup software images.	display install committed [ slot slot-number ] [ verbose ]	N/A
Display backup startup software images.	display install backup [ slot slot-number ] [ verbose ]	N/A
Display ongoing ISSU activate, deactivate, and rollback operations.	display install job	N/A
Display ISSU logs.	display install log [ log-id ] [ verbose ]	N/A
Display software image file information.	display install package { filename \| all } [ verbose ]	N/A
Display the software images included in an .ipe file.	display install ipe-info ipe-filename	N/A
Display rollback point information.	display install rollback [ point-id ]	N/A
Display all software image files that include a specific component or file.	display install which { component name \| file filename } [ slot slot-number ]	N/A
Clear ISSU logs.	reset install log-history oldest log-number	N/A
Clear ISSU rollback points.	reset install rollback oldest point-id	N/A

In IRF mode:

Task	Command	Remarks
Display version compatibility information.	display version comp-matrix	N/A
Display ISSU status and upgrade related information.	display issu state	This command applies only to an ISSU that uses the issu series commands.
Display automatic-rollback timer information.	display issu rollback-timer	N/A
Display active software images.	display install active [ chassis chassis-number slot slot-number ] [ verbose ]	N/A
Display inactive software images.	display install inactive [ chassis chassis-number slot slot-number ] [ verbose ]	N/A
Display main startup software images.	display install committed [ chassis chassis-number slot slot-number ] [ verbose ]	N/A
Display backup startup software images.	display install backup [ chassis chassis-number slot slot-number ] [ verbose ]	N/A
Display ongoing ISSU activate, deactivate, and rollback operations.	display install job	N/A
Display ISSU logs.	display install log [ log-id ] [ verbose ]	N/A
Display software image file information.	display install package { filename \| all } [ verbose ]	N/A
Display the software images included in an .ipe file.	display install ipe-info ipe-filename	N/A
Display rollback point information.	display install rollback [ point-id ]	N/A
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 ]	N/A
Clear ISSU logs.	reset install log-history oldest log-number	N/A
Clear ISSU rollback points.	reset install rollback oldest point-id	N/A

ISSU examples for using issu series commands in standalone mode

HTTP feature upgrade to a compatible version

Upgrade requirements

As shown in Figure 1, the device has two MPUs. The active MPU is in slot 0. The standby MPU is in slot 1.

Upgrade the HTTP feature from R0201 to R0202, which is a compatible version.

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 1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

# Identify the ISSU recommended method for the upgrade and view the possible impact of the upgrade.

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

Verifying the file flash:/http-r0202.bin on slot 0...Done.

Feature image: flash:/http-r0202.bin

Version:

V700R001B31D002

Version Compatibility List:

V700R001B31D001

V700R001B31D002

Version Dependency System List:

V700R001B31D001

V700R001B31D002

Slot Upgrade Way

0 Service Upgrade

1 Service 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 is recommended. 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

Verifying the file flash:/http-r0202.bin on slot 0...Done.

Copying file flash:/http-r0202.bin to slot1#flash:/http-r0202.bin......Done.

Verifying the file flash:/http-r0202.bin on slot 1...Done.

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Slot Upgrade Way

1 Service 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

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

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 1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

HTTP feature upgrade to an incompatible version

Upgrade requirements

As shown in Figure 2, the device has two MPUs. The active MPU is in slot 0. The standby MPU is in slot 1.

Upgrade the HTTP feature from R0201 to R0202, which is an incompatible version.

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 1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

# Identify the recommended ISSU method for the upgrade and view the possible impact of the upgrade.

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

Verifying the file flash:/http-r0202.bin on slot 0...Done.

Feature image: flash:/http-r0202.bin

Version:

V700R001B31D002

Version Compatibility List:

V700R001B31D002

Version Dependency System List:

V700R001B31D001

V700R001B31D002

Incompatible upgrade.

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

# 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

Verifying the file flash:/http-r0202.bin on slot 0...Done.

Copying file flash:/http-r0202.bin to slot1#flash:/http-r0202.bin......Done.

Verifying the file flash:/http-r0202.bin on slot 1...Done.

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Slot Upgrade Way

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

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 1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

HTTP feature rollback example

Rollback requirement

As shown in Figure 3, the device has two MPUs. The active MPU is in slot 0. The standby MPU is in slot 1.

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

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 1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

# Identify the recommended ISSU method for the upgrade and view the possible impact of the upgrade.

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

Verifying the file flash:/http-r0202.bin on slot 0...Done.

Feature image: flash:/http-r0202.bin

Version:

V700R001B31D002

Version Compatibility List:

V700R001B31D001

V700R001B31D002

Version Dependency System List:

V700R001B31D001

V700R001B31D002

Slot Upgrade Way

0 Service Upgrade

1 Service 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 is recommended. 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

Verifying the file flash:/http-r0202.bin on slot 0...Done.

Copying file flash:/http-r0202.bin to slot1#flash:/http-r0202.bin......Done.

Verifying the file flash:/http-r0202.bin on slot 1...Done.

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Slot Upgrade Way

1 Service 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

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 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 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 requirements

As shown in Figure 4, the IRF fabric has two members. 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, which is a compatible version.

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 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 1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

# Identify the recommended ISSU method for the upgrade and view the possible impact of the upgrade.

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

Verifying the file flash:/http-r0202.bin on Chassis 1 slot 0...Done.

Feature image: flash:/http-r0202.bin

Version:

V700R001B31D002

Version Compatibility List:

V700R001B31D001

V700R001B31D002

Version Dependency System List:

V700R001B31D001

V700R001B31D002

Chassis Slot Upgrade Way

1 0 Service Upgrade

1 1 Service Upgrade

2 0 Service Upgrade

2 1 Service 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 is recommended. 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

Verifying the file flash:/http-r0202.bin on chassis 1 slot 0...Done.

Copying file flash:/http-r0202.bin to chassis2#slot0#flash:/http-r0202.bin......Done.

Verifying the file flash:/http-r0202.bin on chassis 2 slot 0...Done.

Copying file flash:/http-r0202.bin to chassis2#slot1#flash:/http-r0202.bin......Done.

Verifying the file flash:/http-r0202.bin on chassis 2 slot 1...Done.

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 1 Service 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

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

# Upgrade the feature on the original master.

<Sysname> issu commit chassis 1

Copying file flash:/http-r0202.bin to chassis1#slot1#flash:/http-r0202.bin......Done.

Verifying the file flash:/http-r0202.bin on chassis 1 slot 1...Done.

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 Service 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 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 1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

HTTP feature upgrade to an incompatible version

Upgrade requirements

As shown in Figure 5, the IRF fabric has two members. 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, which is an incompatible version.

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 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 1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

# Identify the recommended ISSU method for the upgrade and view the possible impact of the upgrade.

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

Verifying the file flash:/http-r0202.bin on Chassis 1 slot 0...Done.

Feature image: flash:/http-r0202.bin

Version:

V700R001B31D002

Version Compatibility List:

V700R001B31D002

Version Dependency System List:

V700R001B31D001

V700R001B31D002

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

Verifying the file flash:/http-r0202.bin on chassis 1 slot 0...Done.

Copying file flash:/http-r0202.bin to chassis2#slot0#flash:/http-r0202.bin......Done.

Verifying the file flash:/http-r0202.bin on chassis 2 slot 0...Done.

Copying file flash:/http-r0202.bin to chassis2#slot1#flash:/http-r0202.bin......Done.

Verifying the file flash:/http-r0202.bin on chassis 2 slot 1...Done.

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 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

Copying file flash:/http-r0202.bin to chassis1#slot1#flash:/http-r0202.bin......Done.

Verifying the file flash:/http-r0202.bin on chassis 1 slot 1...Done.

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 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 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 1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

HTTP feature rollback example

Rollback requirement

As shown in Figure 6, the IRF fabric has two members. 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 after upgrading it from R0201 to R0202. R0202 and R0201 are compatible.

Figure 6 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 chassis 1 slot 0:

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 2 slot 0:

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

# Identify the recommended ISSU method for the upgrade and view the possible impact of the upgrade.

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

Verifying the file flash:/http-r0202.bin on Chassis 1 slot 0...Done.

Feature image: flash:/http-r0202.bin

Version:

V700R001B31D002

Version Compatibility List:

V700R001B31D001

V700R001B31D002

Version Dependency System List:

V700R001B31D001

V700R001B31D002

Chassis Slot Upgrade Way

1 0 Service Upgrade

1 1 Service Upgrade

2 0 Service Upgrade

2 1 Service 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 is recommended. 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

Verifying the file flash:/http-r0202.bin on chassis 1 slot 0...Done.

Copying file flash:/http-r0202.bin to chassis2#slot0#flash:/http-r0202.bin......Done.

Verifying the file flash:/http-r0202.bin on chassis 2 slot 0...Done.

Copying file flash:/http-r0202.bin to chassis2#slot1#flash:/http-r0202.bin......Done.

Verifying the file flash:/http-r0202.bin on chassis 2 slot 1...Done.

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 1 Service Upgrade

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

# Perform a master/subordinate switchover.

<Sysname> issu run switchover

Copying file flash:/http-r0202.bin to chassis1#slot1#flash:/http-r0202.bin......Done.

Verifying the file flash:/http-r0202.bin on chassis 1 slot 1...Done.

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

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 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 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 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 1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Performing an ISSU by using install series commands

ISSU guidelines

During an ISSU, use the following guidelines:

· In a multiuser environment, make sure no other administrators access the device while you are performing an ISSU.

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

· Do not execute any commands that are not for ISSU.

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

· You only need to perform the upgrade on the default MDC. The system completes software upgrade for all the other MDCs automatically.

· After an ISSU, you must log in to the device again before you can configure the device.

Performing an ISSU

Obtaining and decompressing an .ipe file

If the images required for the ISSU are distributed in an .ipe file, you must obtain and decompress the .ipe file before starting the ISSU.

Follow these steps:

1. Use FTP or TFTP to transfer 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-filename medium-name:

Installing or upgrading software images

You can install or upgrade a software image with 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.

To install or upgrade multiple images with the install activate command, use one of the following methods:

· Slot by slot—For each slot, use a single command to activate all the images.

· Image by image—Activate one image on all slots before activating another image.

In standalone mode:

· To install a feature image or patch image, you must install it on the active MPU first.

· To upgrade an image, you must upgrade the image on the standby MPU first.

In IRF mode:

· To install a feature image or patch image, 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 a feature image or patch image, 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 feature or patch image on the active MPU, the system automatically installs or upgrades the image on the LPUs and switching fabric modules as needed. You do not need to install or upgrade the image for the cards separately.

For an incremental upgrade, you must confirm the software changes to keep activated images effective after a reboot. However, you do not need to confirm software changes for a reboot or ISSU reboot upgrade, because the install activate command changes the startup software image sets.

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

Step	Command
1. (Optional.) Identify the recommended ISSU method for the upgrade and view 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
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
3. (Optional.) Confirm the software changes.	install commit

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

Step	Command
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
2. (Optional.) Confirm the software changes.	install commit

Step

Command

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

2. (Optional.) Confirm the software changes.

install commit

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.

To uninstall an image during an incremental upgrade, deactivate the image 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 during a reboot or ISSU reboot upgrade, you only need to deactivate the image. The deactivated image does not become active after a reboot.

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 images

Every time you activate or deactivate a software image, the system creates a rollback point to record the running software images. Executing the install commit command confirms the software changes and removes all rollback points. Before rollback points are removed, you can perform the following operations:

· Roll back the software to a rollback point to cancel all software image upgrade-related operations performed after the rollback point.

· Roll back the software to the original software images.

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

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

Patch images do not support rollback.

For a rollback performed during an incremental upgrade to take effect after a reboot, confirm the rollback by using the install commit command. A rollback performed during a reboot or ISSU reboot upgrade does not need to be confirmed.

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

Step	Command	Remarks
1. Roll back the software to an earlier rollback point or the original software images.	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 activate/deactivate 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 command in user view to abort the operation.

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

Verifying software images

When you verify software images, the following image properties are checked:

· Integrity—Whether the boot images, system images, and feature images on the device are integral.

· Consistency—Whether all MPUs have the same active images.

· Confirmation status—Whether the active images on an MPU are confirmed.

If an image is not integral, consistent, or confirmed, use the install activate, install deactivate, and install commit commands as appropriate to solve the problem.

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 to free storage space.

If a file has been specified as a startup software image file, you cannot remove it by using the install remove command.

IMPORTANT:

Removing a software image deletes the image file from the device permanently. You cannot use the install rollback to command to revert the operation, or use the install abort command to abort the operation.

To remove inactive software images, execute either of the following commands 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

See "Displaying and maintaining ISSU."

ISSU examples for using install series commands in standalone mode

HTTP feature upgrade example

Upgrade requirements

As shown in Figure 7, the device has two MPUs. The active MPU is in slot 0. The standby MPU is in slot 1.

Upgrade the HTTP feature from R0201 to R0202, which is a compatible version.

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:/

Verifying the file flash:/http-r0202.bin on slot 0...Done.

Decompressing file http-r0202.bin to flash:/http-r0202.bin.......................Done.

# 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 1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

# Identify the recommended ISSU methods for the upgrade and view the possible impact of the upgrade.

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

Copying file flash:/http-r0202.bin to slot1#flash:/http-r0202.bin......Done.

Verifying the file flash:/http-r0202.bin on slot 1...Done.

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Slot Upgrade Way

1 Service 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

Verifying the file flash:/http-r0202.bin on slot 0...Done.

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Slot Upgrade Way

0 Service Upgrade

2 Service 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

flash:/http-r0202.bin already exists on slot 1.

Overwrite it?[Y/N]:y

Copying file flash:/http-r0202.bin to slot1#flash:/http-r0202.bin......Done.

Verifying the file flash:/http-r0202.bin on slot 1...Done.

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Slot Upgrade Way

1 Service Upgrade

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

This operation maybe take several minutes, please wait......................Done.

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

Verifying the file flash:/http-r0202.bin on slot 0...Done.

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Slot Upgrade Way

0 Service Upgrade

2 Service Upgrade

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

This operation maybe take several minutes, please wait......................Done.

# 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 1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

# Confirm the software change.

<Sysname> install commit

This operation will take several minutes, please wait...........................Done.

HTTP feature rollback example

Rollback requirement

As shown in Figure 7, the device has two MPUs. The active MPU is in slot 0. The standby MPU is in slot 1.

The HTTP feature has been upgraded from R0201 to R0202, but the software change has not been confirmed.

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 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 1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

# Confirm the software change.

<Sysname> install commit

This operation will take several minutes, please wait...........................Done.

ISSU examples for using install series commands in IRF mode

HTTP feature upgrade example

Upgrade requirements

As shown in Figure 8, the IRF fabric has two members. 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, which is a compatible version.

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:

Verifying the file flash:/http-r0202.ipe on chassis 1 slot 0...Done.

Decompressing file http-r0202.bin to flash:/http-r0202.bin.......................Done.

# 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 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 1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

# Identify the recommended ISSU methods for the upgrade and view the possible impact of the upgrade.

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

Copying file flash:/http-r0202.bin to chassis2#slot1#flash:/http-r0202.bin......Done.

Verifying the file flash:/http-r0202.bin on chassis 2 slot 1...Done.

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 2 Service Upgrade

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

flash:/http-r0202.bin

HTTP CFA

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

flash:/http-r0202.bin

HTTP CFA

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

Copying file flash:/http-r0202.bin to chassis2#slot0#flash:/http-r0202.bin......Done.

Verifying the file flash:/http-r0202.bin on chassis 2 slot 0...Done.

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

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

Copying file flash:/http-r0202.bin to chassis1#slot1#flash:/http-r0202.bin......Done.

Verifying the file flash:/http-r0202.bin on chassis 1 slot 1...Done.

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 2 Service Upgrade

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 1 slot 2:

flash:/http-r0202.bin

HTTP CFA

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

Verifying the file flash:/http-r0202.bin on chassis 1 slot 0...Done.

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

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

flash:/http-r0202.bin

HTTP CFA

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

# Activate the HTTP image to upgrade the HTTP feature.

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

flash:/http-r0202.bin already exists on chassis 2 slot 1.

Overwrite it?[Y/N]:y

Copying file flash:/http-r0202.bin to chassis2#slot1#flash:/http-r0202.bin......Done.

Verifying the file flash:/http-r0202.bin on chassis 2 slot 1...Done.

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 2 Service Upgrade

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

This operation maybe take several minutes, please wait......................Done.

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

flash:/http-r0202.bin already exists on chassis 2 slot 0.

Overwrite it?[Y/N]:y

Copying file flash:/http-r0202.bin to chassis2#slot0#flash:/http-r0202.bin......Done.

Verifying the file flash:/http-r0202.bin on chassis 2 slot 0...Done.

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

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

This operation maybe take several minutes, please wait......................Done.

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

flash:/http-r0202.bin already exists on chassis 1 slot 1.

Overwrite it?[Y/N]:y

Copying file flash:/http-r0202.bin to chassis1#slot1#flash:/http-r0202.bin......Done.

Verifying the file flash:/http-r0202.bin on chassis 1 slot 1...Done.

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 2 Service Upgrade

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

This operation maybe take several minutes, please wait......................Done.

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

Verifying the file flash:/http-r0202.bin on chassis 1 slot 0...Done.

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

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

This operation maybe take several minutes, please wait......................Done.

# 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 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 1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

# Confirm the software change.

<Sysname> install commit

This operation will take several minutes, please wait...........................Done.

HTTP feature rollback example

Rollback requirement

As shown in Figure 8, the IRF fabric has two members. Each member has one MPU in slot 0 (active MPU) and one MPU in slot 1 (standby MPU).

The HTTP feature has been upgraded from R0201 to R0202, but the software change has not been confirmed.

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 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 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 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 1:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

# Confirm the software change.

<Sysname> install commit

This operation will take several minutes, please wait...........................Done.

01-Fundamentals Configuration Guide

ISSU guidelines

ISSU examples for using issu series commands in standalone mode

Upgrade requirements

Upgrade procedure

Upgrade requirements

Upgrade procedure

Rollback requirement

Rollback procedure

ISSU examples for using issu series commands in IRF mode

Upgrade requirements

Upgrade procedure

Upgrade requirements

Upgrade procedure

Rollback requirement

Rollback procedure

Obtaining and decompressing an .ipe file

Upgrade requirements

Upgrade procedure

HTTP feature rollback example

Rollback requirement

Rollback procedure

ISSU examples for using install series commands in IRF mode

Upgrade requirements

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