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

For an incremental upgrade or ISSU reboot upgrade, you can alternatively use the warm rebooting method. For more information about warm rebooting, see "Managing the device." Support for warm rebooting depends on the device model.

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 Sequence 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. Sequence Reboot is available only for switching fabric modules. This method reboots upgraded switching fabric modules one by one. It moves to the next module only when the previous module completes reboot. Sequence Reboot is available only for switching fabric modules and LPUs. This method requires you to reboot switching fabric modules and LPUs one by one to upgrade them. You must wait for the rebooted module or LPU to start up before rebooting the next module or LPU.

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

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

Sequence Reboot is available only for switching fabric modules. This method reboots upgraded switching fabric modules one by one. It moves to the next module only when the previous module completes reboot.

Sequence Reboot is available only for switching fabric modules and LPUs. This method requires you to reboot switching fabric modules and LPUs one by one to upgrade them. You must wait for the rebooted module or LPU to start up before rebooting the next module or LPU.

ISSU commands

ISSU includes the install and issu command sets. After you identify the recommended ISSU method, use Table 2 to choose the command set you want to use.

Table 2 Command set comparison

Item	issu commands	install commands
Upgrade types	· Compatible. · Incompatible.	Compatible.
Upgrade mode	Chassis by chassis.	MPU by MPU.
Impact on the system	Large.	Small.
Technical skill requirements	Low. As a best practice, use this command set.	High. Administrators must have extensive system knowledge and understand the impact of each upgrade task on the network.

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.

· You cannot use both install and issu commands for the same ISSU.

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

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

· Before executing the issu load command for the first time, use the display system stable state command to verify that the system is stable. If the System State field displays Stable, the system is stable.

· Before executing the following commands, use the display system stable state command to verify that the system is stable:

¡ issu commands—issu load, issu run switchover, and issu commit.

¡ install commands—install activate and install deactivate.

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 by using a single command. 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 by using a single command. For more information about incremental and non-incremental patch image files, see "Upgrading software."

· The following protocols will recalculate topology after an ISSU reboot if a peer keepalive timeout has occurred:

¡ Multicast protocols—PIM, IGMP, MLD, IGMP snooping, and MLD snooping.

¡ Routing protocols—OSPF, IS-IS, and BGP.

¡ MPLS protocols—LDP and RSVP.

¡ FCoE—FIP snooping and FSPF.

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

After an ISSU, use the display boot-loader command to verify that the new software images have been successfully loaded. The startup software images must always be in the flash memory and cannot be deleted. If you delete them, the device cannot restart after being rebooted.

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

Verify the following items:

· Use the display device command to verify that all installed components are in Master, Standby, or Normal state.

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

· Use the switchto mdc command to log in to each MDC and verify that no automatic configuration process is in progress. If an automatic configuration process is in progress on an MDC, wait for the process to complete. If automatic configuration is not deployed for the MDC, quit the automatic configuration process as prompted. For more information about automatic configuration, see "Using automatic configuration."

· Use the display cluster command to verify that all member devices are operating correctly.

· Use the display cpu-usage command to verify that no CPU usage alarm exists on the device. As a best practice, verify that the CPU usage is lower than the CPU usage recovery threshold on each component.

· Use the display memory and display memory-threshold commands to verify that no memory alarm exists on the device. As a best practice, verify that the free memory is greater than the normal state threshold on each component.

· Use the display fan command to verify that all fans are in Normal state.

· Use the display power command to verify that all power supplies are in Normal state.

· Use the display environment command to verify that the temperature of each component is lower than the high-temperature warning threshold.

· Use the display counters rate inbound interface command to verify that all interfaces are forwarding packets correctly.

· Use the display interface | include CRC command to verify that all interfaces are forwarding packets 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 global active MPU.

Identifying the ISSU methods

1. 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. Make sure all member ports are Selected ports.

Determining the upgrade procedure

1. Use Table 2 to choose an upgrade command set, depending on the ISSU method.

2. Identify the hardware redundancy condition.

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

¡ The cluster has multiple members and uses the ring topology.

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

¡ For sequential upgrade of switching fabric modules, a minimum of two correctly operating switching fabric modules are available.

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.

3. Choose the correct procedure from the procedures described in "Performing an ISSU by using issu commands" or "Performing an ISSU by using install commands."

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 a compatible upgrade on a multichassis cluster

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. 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 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-30> } * chassis chassis-number [ reboot ]

¡ Use an .ipe file:

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

4. (Optional.) Reboot switching fabric modules and LPUs one by one to upgrade them.

issu sequence reboot chassis chassis-number slot slot-number

During a reboot upgrade, use another user line to execute this command as prompted for switching fabric modules and LPUs on the upgraded subordinate member that require a manual sequential reboot. You must wait for one rebooted module or LPU to start up before rebooting the next module or LPU.

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

6. Perform an ISSU switchover.

issu run switchover

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

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 cluster. Then, repeat the previous step and this step to upgrade the remaining member devices one by one, including the original master.

10. (Optional.) Reboot switching fabric modules and LPUs one by one to upgrade them.

issu sequence reboot chassis chassis-number slot slot-number

During a reboot upgrade, use another user line to execute this command as prompted for switching fabric modules and LPUs that require a manual sequential reboot on the members upgraded in the previous step. You must wait for one rebooted module or LPU to start up before rebooting the next module or LPU.

11. 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 cluster

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 cluster, 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 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-30> } * chassis chassis-number&<1-3> [ reboot ]

¡ Use an .ipe file:

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

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

3. Verify that the system is stable.

display system stable state

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

issu run switchover

5. 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 cluster

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. 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-30> } * chassis chassis-number slot slot-number [ reboot ]

¡ Use an .ipe file:

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

4. Verify that the system is stable.

display system stable state

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

6. (Optional.) Reboot switching fabric modules and LPUs one by one to upgrade them.

issu sequence reboot chassis chassis-number slot slot-number

During a reboot upgrade, use another user line to execute this command as prompted for switching fabric modules and LPUs that require a manual sequential reboot. You must wait for one rebooted module or LPU to start up before rebooting the next module or LPU.

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 cluster

To perform an incompatible upgrade on a dual-MPU single-chassis cluster, 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 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-30> } * chassis chassis-number slot slot-number [ reboot ]

¡ Use an .ipe file:

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

3. Verify that the system is stable.

display system stable state

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

issu run switchover

5. 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 cluster

To perform an incremental upgrade on a single-MPU single-chassis cluster, 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 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-30> } * chassis chassis-number slot slot-number [ reboot ]

¡ Use an .ipe file:

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

3. Verify that the system is stable.

display system stable state

4. Complete the ISSU process.

issu commit chassis chassis-number slot slot-number

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 on a single-MPU single-chassis cluster

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 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-30> } * chassis chassis-number slot slot-number [ reboot ]

¡ Use an .ipe file:

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

3. (Optional.) Reboot switching fabric modules and LPUs one by one to upgrade them.

issu sequence reboot chassis chassis-number slot slot-number

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.) Rebooting switching fabric modules and LPUs for a reboot upgrade

4. (Optional.) Deactivating software images

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

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

7. (Optional.) Verifying software images

8. Committing software changes

9. (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 feature and patch images or upgrade the 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 moving to another image. Before using this method, read the release notes to make sure the upgrade images are compatible with the current images. If the upgrade images are not compatible with the current images, the upgrade might fail.

Restrictions and guidelines

· 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 upgrade LPUs or switching fabric modules separately. They are upgraded automatically when MPUs are upgraded.

Installing or upgrading boot, system, and feature images

To install or upgrade boot, system, or 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 [ cpu cpu-number ] test

3. Activate images.

install activate { boot filename | system filename | feature filename&<1-30> } * chassis chassis-number slot slot-number [ cpu cpu-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. Install patch images.

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

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

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.

Rebooting switching fabric modules and LPUs for a reboot upgrade

install sequence reboot chassis chassis-number slot slot-number

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 [ cpu cpu-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 [ cpu cpu-number ] }

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

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.

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

Unless otherwise stated, the display and reset commands can be used during an ISSU, regardless of whether the install or issu commands are used.

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

Task	Command	Remarks
Display active software images.	display install active [ chassis chassis-number slot slot-number ] [ verbose ]	N/A
Display backup startup software images.	display install backup [ chassis chassis-number slot slot-number [ cpu cpu-number ] ] [ verbose ]	N/A
Display main startup software images.	display install committed [ chassis chassis-number slot slot-number [ cpu cpu-number ] ] [ verbose ]	N/A
Display inactive software images in the root directories of file systems.	display install inactive [ chassis chassis-number slot slot-number [ cpu cpu-number ] ] [ verbose ]	N/A
Display the software images included in an .ipe file.	display install ipe-info ipe-filename	N/A
Display ongoing ISSU activate, deactivate, and rollback operations.	display install job	N/A
Display ISSU log entries.	display install log [ log-id ] [ verbose ]	N/A
Display software image file information.	display install package { filename \| all } [ verbose ]	N/A
Display rollback point information.	display install rollback [ point-id ]	The system does not record rollback points during an ISSU that uses issu commands.
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 [ cpu cpu-number ] ]	N/A
Display automatic rollback timer information.	display issu rollback-timer	N/A
Display ISSU status information.	display issu state	This command applies only to an ISSU that uses issu commands.
Display the ISSU methods.	display version comp-matrix file { boot filename \| system filename \| feature filename&<1-30> \| patch filename&<1-30> } * display version comp-matrix file ipe ipe-filename [ patch filename&<1-30> ]	N/A
Clear ISSU log entries.	reset install log-history oldest log-number	N/A
Clear ISSU rollback points.	reset install rollback oldest point-id	N/A

‌

Examples of using issu commands for ISSU

Example: Upgrading the system software to a compatible version

Network configuration

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

Upgrade the boot, system, and feature images from T0001015 to T0001016. The two versions are compatible.

Figure 1 Network diagram

‌

Procedure

# Download the upgrade image files from the TFTP server.

<Sysname> tftp 2.2.2.2 get boot-t0001016.bin

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

Dload Upload Total Spent Left Speed

100 6078464 100 6078464 0 0 764 0 --:--:-- --:--:-- --:--:-- 810

Writing file...Done.

<Sysname> tftp 2.2.2.2 get system-t0001016.bin

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

Dload Upload Total Spent Left Speed

100 97750016 100 97750016 0 0 764 0 --:--:-- --:--:-- --:--:-- 810

Writing file...Done.

<Sysname> tftp 2.2.2.2 get feature-t0001016.bin

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

Dload Upload Total Spent Left Speed

100 1008640 100 1008640 0 0 764 0 --:--:-- --:--:-- --:--:-- 810

Writing file...Done.

# Display active software images.

<Sysname> display install active

Active packages on chassis 1 slot 0:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature-t0001015.bin

Active packages on chassis 1 slot 1:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature-t0001015.bin

Active packages on chassis 2 slot 0:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature-t0001015.bin

Active packages on chassis 2 slot 1:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature-t0001015.bin

# Identify the recommended ISSU methods.

<Sysname> display version comp-matrix file boot flash:/boot-t0001016.bin system flash:/system-t0001016.bin feature flash:/feature-t0001016.bin

Verifying the file flash:/boot-t0001016.bin on chassis 1 slot 0..................................Done.

Verifying the file flash:/system-t0001016.bin on chassis 1 slot 0..................................Done.

Verifying the file flash:/feature-t0001016.bin on chassis 1 slot 0..................................Done.

Identifying the upgrade methods....Done.

Chassis Slot Upgrade Way

1 0 Reboot

1 1 Reboot

2 0 Reboot

2 1 Reboot

The output shows that reboot upgrades are recommended.

# Save the running configuration.

<Sysname> save

# Upgrade the system software on the subordinate member.

<Sysname> issu load file boot flash:/boot-t0001016.bin system flash:/system-t0001016.bin feature flash:/feature-t0001016.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

Copying file flash:/boot-t0001016.bin to chassis2#slot0#flash:/boot-t0001016.bin......Done.

Copying file flash:/system-t0001016.bin to chassis2#slot0#flash:/system-t0001016.bin........................Done.

Copying file flash:/feature-t0001016.bin to chassis2#slot0#flash:/feature-t0001016.bin......Done.

Verifying the file flash:/boot-t0001016.bin on chassis 2 slot 0...Done.

Verifying the file flash:/system-t0001016.bin on chassis 2 slot 0............Done.

Verifying the file flash:/feature-t0001016.bin on chassis 2 slot 0...Done.

Copying file flash:/boot-t0001016.bin to chassis2#slot1#flash:/boot-t0001016.bin......Done.

Copying file flash:/system-t0001016.bin to chassis2#slot1#flash:/system-t0001016.bin........................Done.

Copying file flash:/feature-t0001016.bin to chassis2#slot1#flash:/feature-t0001016.bin......Done.

Verifying the file flash:/boot-t0001016.bin on chassis 2 slot 1...Done.

Verifying the file flash:/system-t0001016.bin on chassis 2 slot 1............Done.

Verifying the file flash:/feature-t0001016.bin on chassis 2 slot 1...Done.

Identifying the upgrade methods….Done.

Upgrade summary according to following table:

flash:/boot-t0001016.bin

Running Version New Version

Test 0001015 Test 0001016

flash:/system-t0001016.bin

Running Version New Version

Test 0001015 Test 0001016

flash:/feature-t0001016.bin

Running Version New Version

Test 0001015 Test 0001016

Chassis Slot Upgrade Way

2 0 Reboot

2 1 Reboot

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

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

# Verify that the ISSU is in a stable state.

<Sysname> display issu state

ISSU state: Loaded

Compatibility: Compatible

Work state: Normal

Upgrade method: Chassis by chassis

Upgraded chassis:

chassis 2

Current upgrading chassis: None

Previous version list:

boot: 7.1.070, Test 0001015

system: 7.1.070, Test 0001015

feature: 7.1.070, Test 0001015

Previous software images:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature-t0001015.bin

Upgrade version list:

boot: 7.1.070, Test 0001016

system: 7.1.070, Test 0001016

feature: 7.1.070, Test 0001016

Upgrade software images:

flash:/boot-t0001016.bin

flash:/system-t0001016.bin

flash:/feature-t0001016.bin

The Loaded state is a stable state, which indicates that the system is waiting for a master/subordinate switchover. Chassis 2 has completed the upgrade, and chassis 1 has not.

# Perform a master/subordinate switchover.

<Sysname> issu run switchover

Upgrade summary according to following table:

flash:/boot-t0001016.bin

Running Version New Version

Test 0001015 Test 0001016

flash:/system-t0001016.bin

Running Version New Version

Test 0001015 Test 0001016

flash:/feature-t0001016.bin

Running Version New Version

Test 0001015 Test 0001016

Chassis Slot Switchover Way

1 0 Master subordinate switchover

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

This operation might take several minutes, please wait.........

# Verify that the ISSU is in a stable state.

<Sysname> display issu state

ISSU state: Switchover

Compatibility: Compatible

Work state: Normal

Upgrade method: Chassis by chassis

Upgraded chassis:

chassis 2

Current upgrading chassis: None

Previous version list:

boot: 7.1.070, Test 0001015

system: 7.1.070, Test 0001015

feature: 7.1.070, Test 0001015

Previous software images:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature-t0001015.bin

Upgrade version list:

boot: 7.1.070, Test 0001016

system: 7.1.070, Test 0001016

feature: 7.1.070, Test 0001016

Upgrade software images:

flash:/boot-t0001016.bin

flash:/system-t0001016.bin

flash:/feature-t0001016.bin

The Switchover state is a stable state, which indicates that the system has completed the master/subordinate switchover and is waiting for a commit operation to upgrade chassis 1.

# Upgrade the system software on the original master.

<Sysname> issu commit chassis 1

Copying file flash:/boot-t0001016.bin to chassis1#slot1#flash:/boot-t0001016.bin......Done.

Copying file flash:/system-t0001016.bin to chassis1#slot1#flash:/system-t0001016.bin........................Done.

Copying file flash:/feature-t0001016.bin to chassis1#slot1#flash:/feature-t0001016.bin......Done.

Verifying the file flash:/boot-t0001016.bin on chassis 1 slot 1...Done.

Verifying the file flash:/system-t0001016.bin on chassis 1 slot 1............Done.

Verifying the file flash:/feature-t0001016.bin on chassis 1 slot 1...Done.

Upgrade summary according to following table:

flash:/boot-t0001016.bin

Running Version New Version

Test 0001015 Test 0001016

flash:/system-t0001016.bin

Running Version New Version

Test 0001015 Test 0001016

flash:/feature-t0001016.bin

Running Version New Version

Test 0001015 Test 0001016

Chassis Slot Upgrade Way

1 0 Reboot

1 1 Reboot

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

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

Verifying the upgrade

# Verify that the ISSU is finished.

<Sysname> display issu state

ISSU state: Init

Compatibility: Unknown

Upgrade method: Chassis by chassis

Upgraded chassis: None

Current upgrading chassis: None

Current version list:

boot: 7.1.070, Test 0001016

system: 7.1.070, Test 0001016

feature: 7.1.070, Test 0001016

Current software images:

flash:/boot-t0001016.bin

flash:/system-t0001016.bin

flash:/feature-t0001016.bin

The ISSU state field displays Init, which indicates that the ISSU is finished.

# Verify that both members are running the new software images.

<Sysname> display install active

Active packages on chassis 1 slot 0:

flash:/boot-t0001016.bin

flash:/system-t0001016.bin

flash:/feature-t0001016.bin

Active packages on chassis 1 slot 1:

flash:/boot-t0001016.bin

flash:/system-t0001016.bin

flash:/feature-t0001016.bin

Active packages on chassis 2 slot 0:

flash:/boot-t0001016.bin

flash:/system-t0001016.bin

flash:/feature-t0001016.bin

Active packages on chassis 2 slot 1:

flash:/boot-t0001016.bin

flash:/system-t0001016.bin

flash:/feature-t0001016.bin

Example: Upgrading the system software to an incompatible version

Network configuration

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

Upgrade the boot, system, and feature images from T0001015 to T0001017. The two versions are incompatible.

Figure 2 Network diagram

‌

Procedure

# Download the upgrade image files from the TFTP server.

<Sysname> tftp 2.2.2.2 get boot-t0001016.bin

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

Dload Upload Total Spent Left Speed

100 6078464 100 6078464 0 0 764 0 --:--:-- --:--:-- --:--:-- 810

Writing file...Done.

<Sysname> tftp 2.2.2.2 get system-t0001016.bin

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

Dload Upload Total Spent Left Speed

100 97750016 100 97750016 0 0 764 0 --:--:-- --:--:-- --:--:-- 810

Writing file...Done.

<Sysname> tftp 2.2.2.2 get feature-t0001016.bin

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

Dload Upload Total Spent Left Speed

100 1008640 100 1008640 0 0 764 0 --:--:-- --:--:-- --:--:-- 810

Writing file...Done.

# Display active software images.

<Sysname> display install active

Active packages on chassis 1 slot 0:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature-t0001015.bin

Active packages on chassis 1 slot 1:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature-t0001015.bin

Active packages on chassis 2 slot 0:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature-t0001015.bin

Active packages on chassis 2 slot 1:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature-t0001015.bin

# Identify the recommended ISSU methods.

<Sysname> display version comp-matrix file boot flash:/boot-t0001017.bin system flash:/system-t0001017.bin feature flash:/feature-t0001017.bin

Verifying the file flash:/boot-t0001017.bin on chassis 1 slot 0..................................Done.

Verifying the file flash:/system-t0001017.bin on chassis 1 slot 0..................................Done.

Verifying the file flash:/feature-t0001017.bin on chassis 1 slot 0..................................Done.

Identifying the upgrade methods....Done.

Incompatible upgrade.

The output shows that an incompatible upgrade is recommended.

# Save the running configuration.

<Sysname> save

# Upgrade the system software on the subordinate member. After the upgrade, the subordinate member will leave the original cluster and form a new cluster by itself.

<Sysname> issu load file boot flash:/boot-t0001017.bin system flash:/system-t0001017.bin feature flash:/feature-t0001017.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

Do you want to delete flash:/all.ipe now? [Y/N]:n

Copying file flash:/boot-t0001017.bin to chassis2#slot0#flash:/boot-t0001017.bin......Done.

Copying file flash:/system-t0001017.bin to chassis2#slot0#flash:/system-t0001017.bin........................Done.

Copying file flash:/feature-t0001017.bin to chassis2#slot0#flash:/feature-t0001017.bin......Done.

Verifying the file flash:/boot-t0001017.bin on chassis 2 slot 0...Done.

Verifying the file flash:/system-t0001017.bin on chassis 2 slot 0............Done.

Verifying the file flash:/feature-t0001017.bin on chassis 2 slot 0...Done.

Copying file flash:/boot-t0001017.bin to chassis2#slot1#flash:/boot-t0001017.bin......Done.

Copying file flash:/system-t0001017.bin to chassis2#slot1#flash:/system-t0001017.bin........................Done.

Copying file flash:/feature-t0001017.bin to chassis2#slot1#flash:/feature-t0001017.bin......Done.

Verifying the file flash:/boot-t0001017.bin on chassis 2 slot 1...Done.

Verifying the file flash:/system-t0001017.bin on chassis 2 slot 1............Done.

Verifying the file flash:/feature-t0001017.bin on chassis 2 slot 1...Done.

Identifying the upgrade methods….Done.

Upgrade summary according to following table:

flash:/boot-t0001017.bin

Running Version New Version

Test 0001015 Test 0001017

flash:/system-t0001017.bin

Running Version New Version

Test 0001015 Test 0001017

flash:/feature-t0001017.bin

Running Version New Version

Test 0001015 Test 0001017

Chassis Slot Upgrade Way

2 0 Reboot

2 1 Reboot

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

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

# Verify that the ISSU is in a stable state.

<Sysname> display issu state

ISSU state: Loaded

Compatibility: Incompatible

Work state: Normal

Upgrade method: Chassis by chassis

Upgraded chassis:

chassis 2

Current upgrading chassis: None

Previous version list:

boot: 7.1.070, Test 0001015

system: 7.1.070, Test 0001015

feature: 7.1.070, Test 0001015

Previous software images:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature-t0001015.bin

Upgrade version list:

boot: 7.1.070, Test 0001017

system: 7.1.070, Test 0001017

feature: 7.1.070, Test 0001017

Upgrade software images:

flash:/boot-t0001017.bin

flash:/system-t0001017.bin

flash:/feature-t0001017.bin

The Loaded state is a stable state, which indicates that the system is waiting for a master/subordinate switchover. Chassis 2 has completed the upgrade, and chassis 1 has not.

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

<Sysname> issu run switchover

Copying file flash:/boot-t0001017.bin to chassis1#slot1#flash:/boot-t0001017.bin......Done.

Copying file flash:/system-t0001017.bin to chassis1#slot1#flash:/system-t0001017.bin........................Done.

Copying file flash:/feature-t0001017.bin to chassis1#slot1#flash:/feature-t0001017.bin......Done.

Verifying the file flash:/boot-t0001017.bin on chassis 1 slot 1...Done.

Verifying the file flash:/system-t0001017.bin on chassis 1 slot 1............Done.

Verifying the file flash:/feature-t0001017.bin on chassis 1 slot 1...Done.

Upgrade summary according to following table:

flash:/boot-t0001017.bin

Running Version New Version

Test 0001015 Test 0001017

flash:/system-t0001017.bin

Running Version New Version

Test 0001015 Test 0001017

flash:/feature-t0001017.bin

Running Version New Version

Test 0001015 Test 0001017

Chassis Slot Upgrade Way

1 0 Reboot

1 1 Reboot

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

This operation might take several minutes, please wait.........

Verifying the upgrade

# Verify that the ISSU is finished.

<Sysname> display issu state

ISSU state: Init

Compatibility: Unknown

Work state: Normal

Upgrade method: Chassis by chassis

Upgraded chassis: None

Current upgrading chassis: None

Current version list:

boot: 7.1.070, Test 0001017

system: 7.1.070, Test 0001017

feature: 7.1.070, Test 0001017

Current software images:

flash:/boot-t0001017.bin

flash:/system-t0001017.bin

flash:/feature-t0001017.bin

The ISSU state field displays Init, which indicates that the ISSU is finished.

# Verify that both members are running the new software images.

<Sysname> display install active

Active packages on chassis 1 slot 0:

flash:/boot-t0001017.bin

flash:/system-t0001017.bin

flash:/feature-t0001017.bin

Active packages on chassis 1 slot 1:

flash:/boot-t0001017.bin

flash:/system-t0001017.bin

flash:/feature-t0001017.bin

Active packages on chassis 2 slot 0:

flash:/boot-t0001017.bin

flash:/system-t0001017.bin

flash:/feature-t0001017.bin

Active packages on chassis 2 slot 1:

flash:/boot-t0001017.bin

flash:/system-t0001017.bin

flash:/feature-t0001017.bin

Example: Rolling back the system software

Network configuration

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

Roll back the boot, system, and feature images from T0001016 to T0001015 after upgrading them from T0001015 to T0001016. T0001016 and T0001015 are compatible.

Figure 3 Network diagram

‌

Procedure

# Download the upgrade image files from the TFTP server.

<Sysname> tftp 2.2.2.2 get boot-t0001016.bin

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

Dload Upload Total Spent Left Speed

100 6078464 100 6078464 0 0 764 0 --:--:-- --:--:-- --:--:-- 810

Writing file...Done.

<Sysname> tftp 2.2.2.2 get system-t0001016.bin

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

Dload Upload Total Spent Left Speed

100 97750016 100 97750016 0 0 764 0 --:--:-- --:--:-- --:--:-- 810

Writing file...Done.

<Sysname> tftp 2.2.2.2 get feature-t0001016.bin

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

Dload Upload Total Spent Left Speed

100 1008640 100 1008640 0 0 764 0 --:--:-- --:--:-- --:--:-- 810

Writing file...Done.

# Display active software images.

<Sysname> display install active

Active packages on chassis 1 slot 0:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature-t0001015.bin

Active packages on chassis 1 slot 1:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature-t0001015.bin

Active packages on chassis 2 slot 0:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature-t0001015.bin

Active packages on chassis 2 slot 1:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature-t0001015.bin

# Identify the recommended ISSU methods.

<Sysname> display version comp-matrix file boot flash:/boot-t0001016.bin system flash:/system-t0001016.bin feature flash:/feature-t0001016.bin

Verifying the file flash:/boot-t0001016.bin on chassis 1 slot 0..................................Done.

Verifying the file flash:/system-t0001016.bin on chassis 1 slot 0..................................Done.

Verifying the file flash:/feature-t0001016.bin on chassis 1 slot 0..................................Done.

Identifying the upgrade methods....Done.

Chassis Slot Upgrade Way

1 0 Reboot

1 1 Reboot

2 0 Reboot

2 1 Reboot

The output shows that reboot upgrades are recommended.

# Save the running configuration.

<Sysname> save

# Upgrade the system software on the subordinate member.

<Sysname> issu load file boot flash:/boot-t0001016.bin system flash:/system-t0001016.bin feature flash:/feature-t0001016.bin chassis 2 reboot