· Compatible upgrade—The new software version is compatible with the running software version. This upgrade type supports the ISSU methods in Table 1.

· Incompatible upgrade—The new software version is incompatible with the running software version. The two versions cannot run concurrently.

This upgrade type supports only one upgrade method (also called incompatible upgrade). This method requires a cold reboot to upgrade both control and data planes. Incompatible upgrade disrupts service if hardware redundancy is not available.

For information about identifying the ISSU method, see "Identifying the ISSU methods."

Table 1 ISSU methods for compatible upgrade

ISSU method	Description
Incremental upgrade: · Service Upgrade · File Upgrade	Upgrades only user mode processes that have differences between the new and old software versions. Backup processes and a main/backup process switchover are required for service continuity. · Service upgrade—Upgrades service features. The upgrade does not affect the operation of the features that are not being upgraded. · File upgrade—Upgrades hidden system program files. The system can provide services during the upgrade.
ISSU Reboot	Reboots CPUs to complete software upgrade. During the reboot, the data plane can still forward traffic. Before rebooting CPUs, this method saves all hardware data, configuration settings, running data, and status information to memory. For services that require regular communication with their peers, this method uses protocol agents to maintain their connectivity and status. After the reboot, all data is restored to CPUs. This method is typically used for critical processes, including kernel mode processes and user mode processes that cannot be upgraded by using incremental upgrade.
Reboot	CAUTION: The Reboot method disrupts service if hardware redundancy is not available. As a best practice, schedule the downtime carefully to minimize the upgrade impact on the services. Reboots MPUs to complete the software upgrade. While one MPU is rebooting, the other MPU can provide services. Reboots MPUs to complete the software upgrade. While one MPU is rebooting, the other MPUs can provide services.

ISSU commands

You can use the issu command set for ISSU.

The issu command set has the following characteristics:

· Applies to both compatible and incompatible upgrades.

· Does not support patch installation or uninstallation.

· Upgrades member devices one by one.

· Has a large impact on the system.

· Has less technical skill requirements and is the recommended command set.

Restrictions and guidelines: ISSU

IMPORTANT:

· For a successful ISSU, you must remove all commands that the new version does not support and save the running configuration. To identify the feature changes between the current version and the new version, read the release notes for the device.

· To ensure correct system operation, you must remove the commands configured for features to be uninstalled and save the running configuration before uninstalling the features.

During an ISSU, follow these restrictions and guidelines:

· Do not perform any of the following tasks:

¡ Reboot, add, or remove cards.

¡ Perform tasks that are irrelevant to the ISSU, such as modifying the configuration and displaying information.

¡ Modify, delete, or rename image files.

· For better service continuity, strictly follow the recommended ISSU procedure. Make sure a step is completed before you proceed to the next step.

· Before executing the following commands, use the display system stable state command to verify that the system is stable: issu load, issu run switchover, and issu commit. If the System State field displays Stable, the system is stable.

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

· You can install up to 32 .bin files on the device, including one boot image file, one system image file, and up to 30 feature and patch image files.

· A patch image file can be incremental or non-incremental. You can install up to 30 incremental patch image files. Because each boot, system, or feature image can have one non-incremental patch image file, you can install up to 16 non-incremental patch image files. For more information about incremental and non-incremental patch image files, see "Upgrading software."

After an ISSU, you must log in to the device again before you can use the changed or added commands.

Prerequisites for ISSU

To perform a successful ISSU, make sure all the preparation requirements are met.

Logging in to the device through the console port

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.

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

Identifying availability of ISSU and licensing requirements

Read the software release notes to identify the following items:

· Support of the device for ISSU between the current software version and the new software version.

· Licensing requirements for the upgrade software images. If the upgrade software images require licenses, make sure the device has the required licenses. For more information about license installation, see "Managing licenses."

Verifying the device operating status

Use the display device command to verify that all components are operating correctly.

Preparing the upgrade images

1. Use the dir command to verify that every file system has sufficient free storage space for the upgrade images. If the storage space is not sufficient, delete unused files by using the delete /unreserved file-url command. If the files to be deleted will be used, back up the files before deleting them. You will be unable to restore a deleted file if the /unreserved keyword is used. For more information, see "Managing file systems."

2. Use FTP or TFTP to transfer upgrade image files (in .bin or .ipe) to the root directory of a file system on the active MPU.

3. Use FTP or TFTP to transfer upgrade image files (in .bin or .ipe) to the root directory of a file system on the global active MPU.

Identifying the ISSU methods

1. To upgrade security engines, execute the issu blade command to specify security engine startup images.

2. Execute the display version comp-matrix file command to identify the recommended ISSU methods.

¡ For a compatible upgrade, check the Upgrade Way field to identify the recommended ISSU methods.

¡ For an incompatible upgrade, check the end of command output for the Incompatible upgrade string.

For more information about ISSU methods, see Table 1.

Verifying feature status

For service continuity during an ISSU, configure the following feature settings:

Feature	Setting requirements
GR and NSR	Enable GR or NSR for protocols including LDP, RSVP, OSPF, ISIS, BGP, and FSPF.
BFD	Disable BFD for protocols including LDP, RSVP, OSPF, ISIS, RIP, BGP, VRRP, and NQA.
Ethernet link aggregation	Use the long LACP timeout interval (the lacp period short command is not configured) on all member ports in dynamic aggregation groups.
IRF	Before performing an incompatible upgrade for the IRF fabric, verify that IRF MAD is disabled. To use IRF MAD, enable IRF MAD after finishing the upgrade. Configure IRF bridge MAC persistence as follows: · Compatible upgrade—Configure the irf mac-address persistent timer or irf mac-address persistent always command. · Incompatible upgrade—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.

Determining the upgrade procedure

1. Identify the hardware redundancy condition.

ISSU can maintain service continuity only when the following conditions are met:

¡ The IRF fabric has multiple members and uses the ring topology.

¡ The device has two MPUs that are operating correctly.

¡ The IRF fabric has two or more MPUs that are operating correctly.

IMPORTANT:

If hardware redundancy is not available, service discontinuity is not avoidable during a reboot upgrade or an incompatible upgrade. Make sure you understand the impact of the upgrade on the network.

Adjusting and saving the running configuration

1. Remove all commands that the new software version does not support from the running configuration. To identify all feature changes between the current version and the new version, read the release notes for the device.

2. To uninstall a feature image, remove the commands configured for the feature.

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

Performing an ISSU by using issu commands

Performing an incremental upgrade

To perform a service upgrade or file upgrade, execute the following commands in user view:

1. Verify that the system is stable.

display system stable state

The system is stable if the System State field displays Stable. For a successful ISSU, you must make sure the system is stable before you proceed to the next step.

2. Load the upgrade images as the main startup software images.

¡ Use .bin files:

issu load file { boot filename | system filename | feature filename&<1-30> | patch filename&<1-16> } * [ reboot ]

¡ Use an .ipe file:

issu load file ipe ipe-filename [ patch filename&<1-16> ] [ reboot ]

3. Verify that the system is stable.

display system stable state

The system is stable if the System State field displays Stable. For a successful ISSU, you must make sure the system is stable before you proceed to the next step. If the system reported an error in the previous step, verify that the system is stable and then use the issu rollback command to roll back the upgrade.

4. Complete the ISSU process.

issu commit

5. Verify that the ISSU is finished.

display issu state

If the ISSU state field displays Init, the ISSU is finished.

Performing a reboot, ISSU reboot, or incompatible upgrade

To perform a reboot, ISSU reboot, or incompatible upgrade, execute the following commands in user view:

1. Verify that the system is stable.

display system stable state

The system is stable if the System State field displays Stable. For a successful ISSU, you must make sure the system is stable before you proceed to the next step.

2. Load the upgrade images as the main startup software images.

¡ Use .bin files:

issu load file { boot filename | system filename | feature filename&<1-30> | patch filename&<1-16> } * [ reboot ]

¡ Use an .ipe file:

issu load file ipe ipe-filename [ patch filename&<1-16> ] [ reboot ]

3. Verify that the ISSU is finished.

display issu state

If the ISSU state field displays Init, the ISSU is finished.

Performing a compatible upgrade on a multichassis IRF fabric

Restrictions and guidelines

Upgrade a subordinate member device first. Then, upgrade the remaining member devices, including the original master.

Procedure

1. (Optional.) Configure automatic rollback:

a. Enter system view.

system-view

b. Set the automatic rollback timer.

issu rollback-timer minutes

By default, the automatic rollback timer is set to 45 minutes.

The automatic rollback timer starts when you execute the issu run switchover command.

c. Return to user view.

quit

2. (Optional.) Specify security engine startup images.

¡ Use .bin files:

issu blade blade-model file { boot filename | system filename | feature filename&<1-30> | patch filename&<1-16> } *

¡ Use an .ipe file:

issu blade blade-model file ipe ipe-filename [ patch filename&<1-16> ]

Perform this step if you want to upgrade security engines. This step only specifies the images for the security engines to load. It does not upgrade the security engines.

3. Verify that the system is stable.

display system stable state

The system is stable if the System State field displays Stable. For a successful ISSU, you must make sure the system is stable before you proceed to the next step.

4. Load the upgrade images as main startup software images on a subordinate member to upgrade the subordinate member.

¡ Use .bin files:

issu load file { boot filename | system filename | feature filename&<1-30> | patch filename&<1-16> } * chassis chassis-number [ reboot ]

¡ Use an .ipe file:

issu load file ipe ipe-filename [ patch filename&<1-16> ] chassis chassis-number&<1-3> [ reboot ]

The command also upgrades security engines on the specified subordinate members.

5. Verify that the system is stable.

display system stable state

6. Perform an ISSU switchover.

issu run switchover

If the timer expires, the system automatically rolls back to the original software images.

7. (Optional.) Accept the upgrade and delete the automatic rollback timer.

issu accept

Execute this command before the automatic rollback timer expires.

8. Verify that the system is stable.

display system stable state

9. Upgrade the remaining members to complete the ISSU.

issu commit chassis chassis-number

Execute this command before the automatic rollback timer expires. After using this command for one member, wait for the member to restart and join the IRF fabric. Then, repeat the previous step and this step to upgrade the remaining member devices one by one, including the original master.

This command also upgrades the security engines that are attached only to the specified member.

10. Verify that the ISSU is finished.

display issu state

If the ISSU state field displays Init, the ISSU is finished.

Performing an incompatible upgrade on a multichassis IRF fabric

Restrictions and guidelines

Upgrade one or more subordinate member devices first. Then, upgrade the remaining member devices, including the original master.

Procedure

To perform an incompatible upgrade on a multichassis IRF fabric, execute the following commands in user view:

1. (Optional.) Specify security engine startup images.

¡ Use .bin files:

issu blade blade-model file { boot filename | system filename | feature filename&<1-30> | patch filename&<1-16> } *

¡ Use an .ipe file:

issu blade blade-model file ipe ipe-filename [ patch filename&<1-16> ]

Perform this step if you want to upgrade security engines. This step only specifies the images for the security engines to load. It does not upgrade the security engines.

2. Verify that the system is stable.

display system stable state

The system is stable if the System State field displays Stable. For a successful ISSU, you must make sure the system is stable before you proceed to the next step.

3. Load the upgrade images as main startup software images on subordinate members to upgrade the subordinate members.

¡ Use .bin files:

issu load file { boot filename | system filename | feature filename&<1-30> | patch filename&<1-16> } * chassis chassis-number&<1-3> [ reboot ]

¡ Use an .ipe file:

issu load file ipe ipe-filename [ patch filename&<1-16> ] chassis chassis-number&<1-3> [ reboot ]

As a best practice on a ring-topology IRF fabric, specify half of the subordinate members for this command to reduce service interruption. Make sure the specified subordinate members are physically connected.

This command also upgrades security engines on the specified subordinate members.

4. Verify that the system is stable.

display system stable state

5. Perform an ISSU switchover to complete the ISSU process.

issu run switchover

This command upgrades the remaining members and security engines.

6. Verify that the ISSU is finished.

display issu state

If the ISSU state field displays Init, the ISSU is finished.

Performing a compatible upgrade on a dual-MPU single-chassis IRF fabric

1. (Optional.) Configure automatic rollback:

a. Enter system view.

system-view

b. Set the automatic rollback timer.

issu rollback-timer minutes

By default, the automatic rollback timer is set to 45 minutes.

The automatic rollback timer starts when you execute the issu run switchover command.

c. Return to user view.

quit

2. Specify security engine startup images.

¡ Use .bin files:

issu blade blade-model file { boot filename | system filename | feature filename&<1-30> | patch filename&<1-16> } *

¡ Use an .ipe file:

issu blade blade-model file ipe ipe-filename [ patch filename&<1-16> ]

Perform this step if you want to upgrade security engines. This step only specifies the images for the security engines to load. It does not upgrade the security engines.

3. Verify that the system is stable.

display system stable state

The system is stable if the System State field displays Stable. For a successful ISSU, you must make sure the system is stable before you proceed to the next step.

4. Load the upgrade images as main startup software images on the standby MPU to upgrade the standby MPU.

¡ Use .bin files:

issu load file { boot filename | system filename | feature filename&<1-30> | patch filename&<1-16> } * chassis chassis-number slot slot-number [ reboot ]

¡ Use an .ipe file:

issu load file ipe ipe-filename [ patch filename&<1-16> ] chassis chassis-number slot slot-number [ reboot ]

5. Verify that the system is stable.

display system stable state

6. Perform an ISSU switchover.

issu run switchover

This command also upgrades all security engines, LPUs and switching fabric modules. It also starts the automatic rollback timer. If the timer expires, the system automatically rolls back to the original software images.

7. (Optional.) Accept the upgrade and delete the automatic rollback timer.

issu accept

Execute this command before the automatic rollback timer expires.

8. Verify that the system is stable.

display system stable state

The system is stable if the System State field displays Stable. For a successful ISSU, you must make sure the system is stable before you proceed to the next step. If the system reported an error in the previous two steps, verify that the system is stable and then use the issu rollback command to roll back the upgrade.

9. Upgrade the original active MPU to complete the ISSU process.

issu commit chassis chassis-number slot slot-number

Execute this command before the automatic rollback timer expires.

10. Verify that the ISSU is finished.

display issu state

If the ISSU state field displays Init, the ISSU is finished.

Performing an incompatible upgrade on a dual-MPU single-chassis IRF fabric

To perform an incompatible upgrade on a dual-MPU single-chassis IRF fabric, execute the following commands in user view:

1. (Optional.) Specify security engine startup images.

¡ Use .bin files:

issu blade blade-model file { boot filename | system filename | feature filename&<1-30> | patch filename&<1-16> } *

¡ Use an .ipe file:

issu blade blade-model file ipe ipe-filename [ patch filename&<1-16> ]

Perform this step if you want to upgrade security engines. This step only specifies the images for the security engines to load. It does not upgrade the security engines.

2. Verify that the system is stable.

display system stable state

The system is stable if the System State field displays Stable. For a successful ISSU, you must make sure the system is stable before you proceed to the next step.

3. Load the upgrade images as main startup software images on the standby MPU to upgrade the standby MPU.

¡ Use .bin files:

issu load file { boot filename | system filename | feature filename&<1-30> | patch filename&<1-16> } * chassis chassis-number slot slot-number [ reboot ]

¡ Use an .ipe file:

issu load file ipe ipe-filename [ patch filename&<1-16> ] chassis chassis-number slot slot-number [ reboot ]

4. Verify that the system is stable.

display system stable state

5. Perform an ISSU switchover to upgrade the original active MPU, LPUs, and switching fabric modules.

issu run switchover

This command upgrades the security engines.

6. Verify that the ISSU is finished.

display issu state

If the ISSU state field displays Init, the ISSU is finished.

Performing an incremental upgrade on a single-MPU single-chassis IRF fabric

To perform an incremental upgrade on a single-MPU single-chassis IRF fabric, execute the following commands in user view:

1. (Optional.) Specify security engine startup images.

¡ Use .bin files:

issu blade blade-model file { boot filename | system filename | feature filename&<1-30> | patch filename&<1-16> } *

¡ Use an .ipe file:

issu blade blade-model file ipe ipe-filename [ patch filename&<1-16> ]

Perform this step if you want to upgrade security engines. This step only specifies the images for the security engines to load. It does not upgrade the security engines.

2. Verify that the system is stable.

display system stable state

The system is stable if the System State field displays Stable. For a successful ISSU, you must make sure the system is stable before you proceed to the next step.

3. Load the upgrade images as startup software images on the MPU to upgrade the MPU.

¡ Use .bin files:

issu load file { boot filename | system filename | feature filename&<1-30> | patch filename&<1-16> } * chassis chassis-number slot slot-number [ reboot ]

¡ Use an .ipe file:

issu load file ipe ipe-filename [ patch filename&<1-16> ] chassis chassis-number slot slot-number [ reboot ]

The command also upgrades all security engines.

4. Verify that the system is stable.

display system stable state

5. Complete the ISSU process.

issu commit chassis chassis-number slot slot-number

6. Verify that the ISSU is finished.

display issu state

If the ISSU state field displays Init, the ISSU is finished.

Performing a reboot, ISSU reboot, or incompatible upgrade on a single-MPU single-chassis IRF fabric

1. (Optional.) Specify security engine startup images.

¡ Use .bin files:

issu blade blade-model file { boot filename | system filename | feature filename&<1-30> | patch filename&<1-16> } *

¡ Use an .ipe file:

issu blade blade-model file ipe ipe-filename [ patch filename&<1-16> ]

Perform this step if you want to upgrade security engines. This step only specifies the images for the security engines to load. It does not upgrade the security engines.

2. Verify that the system is stable.

display system stable state

The system is stable if the System State field displays Stable. For a successful ISSU, you must make sure the system is stable before you proceed to the next step.

3. Load MPU upgrade images as startup software images on the MPU to upgrade the MPU.

¡ Use .bin files:

issu load file { boot filename | system filename | feature filename&<1-30> | patch filename&<1-16> } * chassis chassis-number slot slot-number [ reboot ]

¡ Use an .ipe file:

issu load file ipe ipe-filename [ patch filename&<1-16> ] chassis chassis-number slot slot-number [ reboot ]

The command also upgrades all security engines.

4. Verify that the ISSU is finished.

display issu state

If the ISSU state field displays Init, the ISSU is finished.

Performing an ISSU by using install commands

ISSU tasks at a glance

1. (Optional.) Decompressing an .ipe file

2. Installing and upgrading software images

3. (Optional.) Deactivating software images

4. (Optional.) Rolling back the running software images

5. (Optional.) Aborting a software activate or deactivate operation

6. (Optional.) Verifying software images

7. Committing software changes

8. (Optional.) Deleting inactive software images

Decompressing an .ipe file

1. (Optional.) Identify images that are included in the .ipe file.

display install ipe-info

2. Decompress the .ipe file.

install add ipe-filename filesystem

Installing and upgrading software images

About this task

Use this task to install new features and patch images or upgrade the running boot, system, or feature images.

Software image installation and upgrade methods

Use one of the following methods to install or upgrade software images:

· Slot by slot—Activate all the images on one slot, and then move to the next slot.

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

Restrictions and guidelines

· To install an image, you must begin with the active MPU.

· To upgrade an image, you must begin with the standby MPU.

· To install an image, you must begin with the master. On each member device, you must begin with the active MPU.

· To upgrade an image, you must begin with a subordinate device. On each member device, you must begin with the standby MPU.

You do not need to install or upgrade images on LPUs or switching fabric modules separately. The system will automatically install or upgrade the images on LPUs and switching fabric modules when it installs or upgrades images on MPUs.

The activate operation for an incremental upgrade or patch images only updates the current software image list. For the image changes to take effect after a reboot, you must perform a commit operation to update the main startup image list.

Installing or upgrading boot, system, and feature images

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

1. Verify that the system is stable.

display system stable state

The system is stable if the System State field displays Stable. For a successful ISSU, you must make sure the system is stable before you proceed to the next step.

2. (Optional.) Identify the recommended ISSU method and the possible impact of the upgrade.

install activate { boot filename | system filename | feature filename&<1-30> } * chassis chassis-number slot slot-number test

3. Activate images.

install activate { boot filename | system filename | feature filename&<1-30> } * chassis chassis-number slot slot-number

Installing patch images

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

1. Verify that the system is stable.

display system stable state

The system is stable if the System State field displays Stable. For a successful installation, you must make sure the system is stable before you proceed to the next step.

2. Activate patch images.

install activate patch filename { all | chassis chassis-number slot slot-number }

The install activate patch filename all command installs the specified patch images on all hardware and the images can survive a reboot. You do not need to execute the install commit command for the installation.

You can specify only one patch image file for the command at a time. However, you can execute the command multiple times to activate multiple patch image files.

Deactivating software images

Restrictions and guidelines

You can deactivate only feature and patch images.

The deactivate operation only removes images from the current software image list. For the image changes to take effect after a reboot, you must perform a commit operation to remove the images from the main startup image list.

Deactivated images are still stored on the storage medium. To permanently delete the images, execute the install remove command. For more information, see "Deleting inactive software images."

Deactivating feature images

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

1. Verify that the system is stable.

display system stable state

The system is stable if the System State field displays Stable. For a successful deactivate operation, you must make sure the system is stable before you proceed to the next step.

2. Deactivate feature images.

install deactivate feature filename&<1-30> chassis chassis-number slot slot-number

Deactivating patch images

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

1. Verify that the system is stable.

display system stable state

The system is stable if the System State field displays Stable. For a successful deactivate operation, you must make sure the system is stable before you proceed to the next step.

2. Deactivate patch images.

install deactivate patch filename { all | chassis chassis-number slot slot-number }

The install deactivate patch filename all command deactivates the specified patch images on all hardware and the image changes can survive a reboot. You do not need to execute the install commit command for the deactivation.

You can specify only one patch image file for the command at a time. However, you can execute the command multiple times to deactivate multiple patch image files.

Rolling back the running software images

About this task

During an incremental upgrade, the system creates a rollback point for each activate or deactivate operation of a boot, system, or feature image. The system can maintain a maximum of 50 rollback points. If this limit has been reached when a rollback point is created, the system removes the earliest rollback point. You can roll back the software to any of the rollback points.

During a reboot or ISSU reboot upgrade, the system does not create rollback points. After an ISSU reboot or reboot upgrade, you can roll back the software only to the status before any activate or deactivate operations were performed.

Restrictions and guidelines

You can perform this task only before committing software changes. A commit operation deletes all rollback points.

For an incremental upgrade rollback to take effect after a reboot, you must perform a commit operation to update the main startup image list.

Procedure

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

1. (Optional.) Display available rollback points.

display install rollback

2. Roll back the software.

install rollback to { point-id | original }

Aborting a software activate or deactivate operation

About this task

While the system is activating or deactivating a software image for a service upgrade or file upgrade, you can abort the activate or deactivate operation. After an operation is aborted, the system runs with the software images that it was running with before the operation.

Procedure

To abort a software activate or deactivate operation, use one of the following methods:

· Execute the install abort [ job-id ] command in user view.

· Press Ctrl+C.

Committing software changes

About this task

When you activate or deactivate images for an incremental upgrade, or activate or deactivate patch images, the main startup image list does not update with the changes. The software changes are lost at reboot. For the changes to take effect after a reboot, you must commit the changes.

Procedure

To commit software changes, execute the following command in user view:

install commit

Verifying software images

About this task

Perform this task to verify the following items:

· Integrity—Verify that the boot, system, and feature images are integral.

· Consistency—Verify that the same active images are running across the entire system.

· Software commit status—Verify that the active images are committed as needed.

Procedure

To verify software images, execute the following commands in user view:

1. Verify software images.

install verify

2. Activate or deactivate images as required.

install { activate | deactivate }

3. Commit the software changes.

install commit

Deleting inactive software images

About this task

After completing an ISSU, you can use this task to delete old image files permanently.

Restrictions and guidelines

This task deletes image files permanently. You cannot use the install rollback to command to revert the operation, or use the install abort command to abort the operation.

Procedure

To delete inactive software image files, execute the following command in user view:

install remove [ chassis chassis-number slot slot-number ] { filename | inactive }

Terminating the ongoing ISSU process forcibly

About this task

Use this feature to terminate the ISSU process if one of the following exceptions occurs and you cannot perform an upgrade or rollback:

· The ISSU status is not Init but the upgrade has stopped.

· The ISSU status is Init but the upgrade has not completed.

Procedure

1. Enter system view.

system-view

2. Terminate the ongoing ISSU process forcibly.

issu quit

Display and maintenance commands for ISSU

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

Task	Command
Display active software images.	display install active [ chassis chassis-number slot slot-number ] [ verbose ]
Display backup startup software images.	display install backup [ chassis chassis-number slot slot-number ] [ verbose ]
Display main startup software images.	display install committed [ chassis chassis-number slot slot-number ] [ verbose ]
Display inactive software images in the root directories of file systems.	display install inactive [ chassis chassis-number slot slot-number ] [ verbose ]
Display the software images included in an .ipe file.	display install ipe-info ipe-filename
Display ongoing ISSU activate, deactivate, and rollback operations.	display install job
Display ISSU log entries.	display install log [ log-id ] [ verbose ]
Display software image file information.	display install package { filename \| all } [ verbose ]
Display rollback point information. (The system does not record rollback points during an ISSU that uses issu commands.)	display install rollback [ point-id ]
Display the software image file that includes a specific component or file.	display install which { component name \| file filename } [ chassis chassis-number slot slot-number ]
Display the image files to be used for security engines in the ISSU.	display issu blade [ blade-model ]
Display automatic rollback timer information.	display issu rollback-timer
Display ISSU status information.	display issu state
Display the ISSU methods.	display version comp-matrix file { boot filename \| system filename \| feature filename&<1-30> } * display version comp-matrix file ipe ipe-filename
Clear ISSU log entries.	reset install log-history oldest log-number
Clear ISSU rollback points.	reset install rollback oldest point-id

‌

01-Fundamentals Configuration Guide

Performing an incremental upgrade

Procedure

Performing an incompatible upgrade on a multichassis IRF fabric

Restrictions and guidelines

Procedure

Performing an incompatible upgrade on a dual-MPU single-chassis IRF fabric

Performing a reboot, ISSU reboot, or incompatible upgrade on a single-MPU single-chassis IRF fabric

Decompressing an .ipe file

About this task

Software image installation and upgrade methods

Restrictions and guidelines

Installing or upgrading boot, system, and feature images

Installing patch images

Restrictions and guidelines

Restrictions and guidelines

Procedure

About this task

Procedure

About this task

Procedure

About this task

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Procedure

Display and maintenance commands for ISSU

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