- Table of Contents
-
- 01-Fundamentals Configuration Guide
- 00-Preface
- 01-CLI configuration
- 02-RBAC configuration
- 03-Login management configuration
- 04-FTP and TFTP configuration
- 05-File system management configuration
- 06-Configuration file management configuration
- 07-Software upgrade configuration
- 08-ISSU configuration
- 09-Emergency shell configuration
- 10-Automatic configuration
- 11-Device management configuration
- 12-Tcl configuration
- 13-Python configuration
- 14-License management
- Related Documents
-
Title | Size | Download |
---|---|---|
08-ISSU configuration | 510.31 KB |
Restrictions and guidelines: ISSU
Logging in to the device through the console port
Identifying availability of ISSU and licensing requirements
Verifying the device operating status
Determining the upgrade procedure
Adjusting and saving the running configuration
Performing an ISSU by using issu commands
Performing a compatible upgrade on a dual-MPU device (in standalone mode)
Performing an incompatible upgrade on a dual-MPU device (in standalone mode)
Performing an incremental upgrade on a single-MPU device (in standalone mode)
Performing a compatible upgrade on a multichassis IRF fabric (in IRF mode)
Performing an incompatible upgrade on a multichassis IRF fabric (in IRF mode)
Performing a compatible upgrade on a dual-MPU single-chassis IRF fabric (in IRF mode)
Performing an incompatible upgrade on a dual-MPU single-chassis IRF fabric (in IRF mode)
Performing an incremental upgrade on a single-MPU single-chassis IRF fabric (in IRF mode)
Performing an ISSU by using install commands
Aborting a software activate or deactivate operation
Deleting inactive software images
Display and maintenance commands for ISSU
Examples of using issu commands for ISSU (in standalone mode)
Example: Upgrading a feature to a compatible version
Example: Upgrading a feature to an incompatible version
Examples of using issu commands for ISSU (in IRF mode)
Example: Upgrading a feature to a compatible version
Example: Upgrading a feature to an incompatible version
Examples of using install commands for ISSU (in standalone mode)
Examples of using install commands for ISSU (in IRF mode)
Performing an ISSU
About ISSU
The In-Service Software Upgrade (ISSU) feature upgrades the Comware software with a minimum amount of downtime.
Unless otherwise stated, the term "upgrade" refers to both software upgrade and downgrade in ISSU.
ISSU advantages
The Comware software includes the boot image, the system image, and feature images. ISSU supports upgrading the images individually.
When you use ISSU to upgrade a feature, only the related feature images are affected. Other features can continue to provide services.
ISSU supports installing patch images to fix system bugs without a system reboot.
ISSU methods
ISSU methods are determined at software release depending on the compatibility between software versions.
ISSU supports the following upgrade types:
· 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 Sequence Reboot |
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. (In standalone mode.) Reboots MPUs to complete the software upgrade. While one MPU is rebooting, the other MPU can provide services. (In IRF mode.) 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. |
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. |
Patch installation and uninstallation |
Not supported. |
Supported. |
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
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. However, you can use display issu commands with both command sets. For more information, see "Display and maintenance commands for 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 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.
· 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.
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 components are operating correctly.
· 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."
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. (In standalone mode.) 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. (In IRF mode.) 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. |
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. 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:
¡ (In IRF mode.) The IRF fabric has multiple members and uses the ring topology.
¡ (In standalone mode.) The device has two MPUs that are operating correctly.
¡ (In IRF mode.) The IRF fabric 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 dual-MPU device (in standalone mode)
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 MPU software images as main startup software images on the standby MPU.
¡ Use .bin files:
issu load file { boot filename | system filename | feature filename&<1-30> | patch filename&<1-16> } * slot slot-number [ reboot ]
¡ Use an .ipe file:
issu load file ipe ipe-filename [ patch filename&<1-16> ] slot slot-number [ reboot ]
4. 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.
5. Perform an ISSU switchover.
issu run switchover
This command also upgrades the LPUs and switching fabric modules. It also starts the automatic rollback timer. When the timer expires, the system automatically rolls back to the original software images.
6. (Optional.) Accept the upgrade and delete the automatic rollback timer.
issu accept
Execute this command before the automatic rollback timer expires.
7. 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.
8. Upgrade the original active MPU to complete the ISSU process.
issu commit slot slot-number
Execute this command before the automatic rollback timer expires.
9. 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 device (in standalone mode)
To perform an incompatible upgrade on a dual-MPU device, 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 MPU software 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> } * slot slot-number [ reboot ]
¡ Use an .ipe file:
issu load file ipe ipe-filename [ patch filename&<1-16> ] slot slot-number [ 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.
4. Perform an ISSU switchover to upgrade the remaining cards.
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 device (in standalone mode)
To perform an incremental upgrade on a single-MPU device, 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 MPU upgrade software images as main startup software images to upgrade the MPU.
¡ Use .bin files:
issu load file { boot filename | system filename | feature filename&<1-30> | patch filename&<1-16> } * slot slot-number [ reboot ]
¡ Use an .ipe file:
issu load file ipe ipe-filename [ patch filename&<1-16> ] slot slot-number [ 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.
4. Complete the ISSU process.
issu commit 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 device (in standalone mode)
To perform a reboot, ISSU reboot, or incompatible upgrade on a single-MPU device, 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 MPU upgrade software images as main startup software images to upgrade the MPU.
¡ Use .bin files:
issu load file { boot filename | system filename | feature filename&<1-30> | patch filename&<1-16> } * slot slot-number [ reboot ]
¡ Use an .ipe file:
issu load file ipe ipe-filename [ patch filename&<1-16> ] slot slot-number [ 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 (in IRF mode)
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-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 ]
4. 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.
5. Perform an ISSU switchover.
issu run switchover
If the timer expires, the system automatically rolls back to the original software images.
6. (Optional.) Accept the upgrade and delete the automatic rollback timer.
issu accept
Execute this command before the automatic rollback timer expires.
7. 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.
8. 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.
9. 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 (in IRF mode)
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. 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-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.
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. 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 IRF fabric (in IRF mode)
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-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
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.
5. Perform an ISSU switchover.
issu run switchover
This command also upgrades all 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.) Accept the upgrade and delete the automatic rollback timer.
issu accept
Execute this command before the automatic rollback timer expires.
7. 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.
8. 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.
9. 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 (in IRF mode)
To perform an incompatible upgrade on a dual-MPU single-chassis IRF fabric, 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-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 ]
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. 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 IRF fabric (in IRF mode)
To perform an incremental upgrade on a single-MPU single-chassis IRF fabric, 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-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 ]
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. 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 IRF fabric (in IRF mode)
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-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 ]
3. 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
3. (Optional.) Deactivating software images
4. (Optional.) Aborting a software activate or deactivate operation
5. Committing software changes
6. (Optional.) Verifying software images
7. (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
Activating software images
About software image activation
Use this task to install new features or upgrade the boot, system, or feature images.
Software image activation methods
Use one of the following methods to activate 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
In standalone mode:
· To install an image, you must begin with the active MPU.
· To upgrade an image, you must begin with the standby MPU.
In IRF mode:
· 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.
(In standalone mode.) (In IRF mode.) You do not need to upgrade LPUs or switching fabric modules separately. They are upgraded automatically when MPUs are upgraded.
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.
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 or patch image files.
Prerequisites
Before activating patch images, check whether the device is already running patch images.
· If not, activate patch images.
· If yes, read the release notes to identify the functionality differences between the running patch images and the new patch images.
¡ If the new patch images cover all functions provided by the old patch images, activating the new patch images overwrites the old patch images. After activating the new patch images, deactivate and delete the old patch images to remove them from software image lists and release the storage space.
¡ If the new patch images do not cover one or more functions provided by the old patch images, activating the patch images does not affect the old patch images. The device uses both the new patch images and the old patch images. Do not deactivate or delete the old patch images.
Activating boot, system, and feature images
To activate 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.
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
3. Activate 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
Activating patch images
To activate 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.
In standalone mode:
install activate patch filename { all | slot slot-number }
In IRF mode:
install activate patch filename { all | 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.
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
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.
In standalone mode:
install deactivate patch filename { all | slot slot-number }
In IRF mode:
install deactivate patch filename { all | chassis chassis-number slot slot-number }
Aborting a software activate or deactivate operation
About aborting a software activate or deactivate operation
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 committing software changes
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 software image verification
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 deleting inactive software images
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 abort command to abort the operation.
Procedure
To delete inactive software image files, execute the following command in user view:
In standalone mode:
install remove [ slot slot-number ] { filename | inactive }
In IRF mode:
install remove [ chassis chassis-number slot slot-number ] { filename | inactive }
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.
(In standalone mode.) Execute display commands in any view and reset commands in user view.
Task |
Command |
Remarks |
Display active software images. |
display install active [ slot slot-number ] [ verbose ] |
N/A |
Display backup startup software images. |
display install backup [ slot slot-number ] [ verbose ] |
N/A |
Display main startup software images. |
display install committed [ slot slot-number ] [ verbose ] |
N/A |
Display inactive software images in the root directories of file systems. |
display install inactive [ slot slot-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 the software image file that includes a specific component or file. |
display install which { component name | file filename } [ slot slot-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> } * display version comp-matrix file ipe ipe-filename |
N/A |
Clear ISSU log entries. |
reset install log-history oldest log-number |
N/A |
(In IRF mode.) 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 ] [ verbose ] |
N/A |
Display main startup software images. |
display install committed [ chassis chassis-number slot slot-number ] [ verbose ] |
N/A |
Display inactive software images in the root directories of file systems. |
display install inactive [ chassis chassis-number slot slot-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 ] |
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> } * display version comp-matrix file ipe ipe-filename |
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 (in standalone mode)
Example: Upgrading a feature to a compatible version
Network configuration
As shown in Figure 1, the device has one active MPU (slot 0) and one standby MPU (slot 1).
Upgrade the Feature1 feature from T0001015 to T0001016. The two versions are compatible.
Procedure
# Download the image file that contains the T0001016 Feature1 feature from the TFTP server.
<Sysname> tftp 2.2.2.2 get feature1-t0001016.bin
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 256 100 256 0 0 764 0 --:--:-- --:--:-- --:--:-- 810
Writing file...Done.
# Display active software images.
<Sysname> display install active
Active packages on slot 0:
flash:/boot-t0001015.bin
flash:/system-t0001015.bin
flash:/feature1-t0001015.bin
Active packages on slot 1:
flash:/boot-t0001015.bin
flash:/system-t0001015.bin
flash:/feature1-t0001015.bin
# Identify the recommended ISSU methods and possible impact of the upgrade.
<Sysname> display version comp-matrix file feature flash:/feature1-t0001016.bin
Verifying the file flash:/feature1-t0001016.bin on slot 0...Done.
Slot Upgrade Way
0 Service Upgrade
1 Service Upgrade
Influenced service according to following table on slot 0:
flash:/feature1-t0001016.bin
Feature1
Influenced service according to following table on slot 1:
flash:/feature1-t0001016.bin
Feature1
The output shows that service upgrade is recommended. The Feature1 module will be rebooted during the upgrade.
# Upgrade the Feature1 feature on the standby MPU.
· Method 1: Use the recommended method.
<Sysname> issu load file feature flash:/feature1-t0001016.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:/feature1-t0001016.bin on slot 0...Done.
Copying file flash:/feature1-t0001016.bin to slot1#flash:/feature1-t0001016.bin......Done.
Verifying the file flash:/feature1-t0001016.bin on slot 1...Done.
Identifying the upgrade methods...Done.
Upgrade summary according to following table:
flash:/feature1-t0001016.bin
Running Version New Version
Test 0001015 Test 0001016
Slot Upgrade Way
1 Service Upgrade
Upgrading software images to compatible versions. Continue? [Y/N]:y
This operation might take several minutes, please wait...Done.
· Method 2: Use the reboot method.
<Sysname> issu load file feature flash:/feature1-t0001016.bin slot 1 reboot
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:/feature1-t0001016.bin on slot 0...Done.
Copying file flash:/feature1-t0001016.bin to slot1#flash:/feature1-t0001016.bin......Done.
Verifying the file flash:/feature1-t0001016.bin on slot 1...Done.
Identifying the upgrade methods...Done.
Upgrade summary according to following table:
flash:/feature1-t0001016.bin
Running Version New Version
Test 0001015 Test 0001016
Slot Upgrade Way
1 Reboot
Upgrading software images to compatible versions. Continue? [Y/N]:y
This operation might take several minutes, please wait...Done.
# Perform a main/backup Feature1 process switchover.
<Sysname> issu run switchover
Upgrade summary according to following table:
flash:/feature1-t0001016.bin
Running Version New Version
Test 0001015 Test 0001016
Slot Switchover Way
0 Active standby process switchover
Upgrading software images to compatible versions. Continue? [Y/N]:y
This operation might take several minutes, please wait...Done.
# Upgrade the feature on the original active MPU.
· If the upgrade used the recommended method:
<Sysname> issu commit slot 0
Upgrade summary according to following table:
flash:/feature1-t0001016.bin
Running Version New Version
Test 0001015 Test 0001016
Slot Upgrade Way
0 Service Upgrade
Upgrading software images to compatible versions. Continue? [Y/N]:y
This operation might take several minutes, please wait...Done.
· If the upgrade used the reboot method:
<Sysname> issu commit slot 0
Upgrade summary according to following table:
flash:/feature1-t0001016.bin
Running Version New Version
Test 0001015 Test 0001016
Slot Upgrade Way
0 Reboot
Upgrading software images to compatible versions. Continue? [Y/N]:y
This operation might take several minutes, please wait...Done.
# Verify that both MPUs are running the new Feature1 image.
<Sysname> display install active
Active packages on slot 0:
flash:/boot-t0001015.bin
flash:/system-t0001015.bin
flash:/feature1-t0001016.bin
Active packages on slot 1:
flash:/boot-t0001015.bin
flash:/system-t0001015.bin
flash:/feature1-t0001016.bin
Example: Upgrading a feature to an incompatible version
Network configuration
As shown in Figure 2, the device has one active MPU (slot 0) and one standby MPU (slot 1).
Upgrade the Feature1 feature from T0001015 to T0001016. The two versions are incompatible.
Procedure
# Download the image file that contains the T0001016 Feature1 feature from the TFTP server.
<Sysname> tftp 2.2.2.2 get feature1-t0001016.bin
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 256 100 256 0 0 764 0 --:--:-- --:--:-- --:--:-- 810
Writing file...Done.
# Display active software images.
<Sysname> display install active
Active packages on slot 0:
flash:/boot-t0001015.bin
flash:/system-t0001015.bin
flash:/feature1-t0001015.bin
Active packages on slot 1:
flash:/boot-t0001015.bin
flash:/system-t0001015.bin
flash:/feature1-t0001015.bin
# Identify the recommended ISSU methods and possible impact of the upgrade.
<Sysname> display version comp-matrix file feature flash:/feature1-t0001016.bin
Verifying the file flash:/feature1-t0001016.bin on slot 0...Done.
Incompatible upgrade.
The output shows that the two versions are incompatible. The relevant cards will be rebooted for the upgrade.
# Upgrade the Feature1 feature on the standby MPU.
<Sysname> issu load file feature flash:/feature1-t0001016.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:/feature1-t0001016.bin on slot 0...Done.
Copying file flash:/feature1-t0001016.bin to slot1#flash:/feature1-t0001016.bin......Done.
Verifying the file flash:/feature1-t0001016.bin on slot 1...Done.
Identifying the upgrade methods...Done.
Upgrade summary according to following table:
flash:/feature1-t0001016.bin
Running Version New Version
Test 0001015 Test 0001016
Slot Upgrade Way
1 Reboot
Upgrading software images to incompatible versions. Continue? [Y/N]:y
This operation might take several minutes, please wait...Done.
# Upgrade the feature on the original active MPU.
<Sysname> issu run switchover
Upgrade summary according to following table:
flash:/feature1-t0001016.bin
Running Version New Version
Test 0001015 Test 0001016
Slot Upgrade Way
0 Reboot
Upgrading software images to incompatible versions. Continue? [Y/N]:y
This operation might take several minutes, please wait...Done.
# Verify that both MPUs are running the new Feature1 image.
<Sysname> display install active
Active packages on slot 0:
flash:/boot-t0001015.bin
flash:/system-t0001015.bin
flash:/feature1-t0001016.bin
Active packages on slot 1:
flash:/boot-t0001015.bin
flash:/system-t0001015.bin
flash:/feature1-t0001016.bin
Examples of using issu commands for ISSU (in IRF mode)
Example: Upgrading a feature to a compatible version
Network configuration
As shown in Figure 3, the IRF fabric has two members. Each member has one active MPU (slot 0) and one standby MPU (slot 1).
Upgrade the Feature1 feature from T0001015 to T0001016. The two versions are compatible.
Procedure
# Download the image file that contains the T0001016 Feature1 feature from the TFTP server.
<Sysname> tftp 2.2.2.2 get feature1-t0001016.bin
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 256 100 256 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:/feature1-t0001015.bin
Active packages on chassis 1 slot 1:
flash:/boot-t0001015.bin
flash:/system-t0001015.bin
flash:/feature1-t0001015.bin
Active packages on chassis 2 slot 0:
flash:/boot-t0001015.bin
flash:/system-t0001015.bin
flash:/feature1-t0001015.bin
Active packages on chassis 2 slot 1:
flash:/boot-t0001015.bin
flash:/system-t0001015.bin
flash:/feature1-t0001015.bin
# Identify the recommended ISSU methods and possible impact of the upgrade.
<Sysname> display version comp-matrix file feature flash:/feature1-t0001016.bin
Verifying the file flash:/feature1-t0001016.bin on chassis 1 slot 0...Done.
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:/feature1-t0001016.bin
Feature1
Influenced service according to following table on chassis 1 slot 1:
flash:/feature1-t0001016.bin
Feature1
Influenced service according to following table on chassis 2 slot 0:
flash:/feature1-t0001016.bin
Feature1
Influenced service according to following table on chassis 2 slot 1:
flash:/feature1-t0001016.bin
Feature1
The output shows that service upgrade is recommended. The Feature1 module will be rebooted during the upgrade.
# Upgrade the Feature1 feature on the subordinate member.
· Method 1: Use the recommended method.
<Sysname> issu load file feature flash:/feature1-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
Verifying the file flash:/feature1-t0001016.bin on chassis 1 slot 0...Done.
Copying file flash:/feature1-t0001016.bin to chassis2#slot0#flash:/feature1-t0001016.bin......Done.
Verifying the file flash:/feature1-t0001016.bin on chassis 2 slot 0...Done.
Copying file flash:/feature1-t0001016.bin to chassis2#slot1#flash:/feature1-t0001016.bin......Done.
Verifying the file flash:/feature1-t0001016.bin on chassis 2 slot 1...Done.
Identifying the upgrade methods...Done.
Upgrade summary according to following table:
flash:/feature1-t0001016.bin
Running Version New Version
Test 0001015 Test 0001016
Chassis Slot Upgrade Way
2 0 Service Upgrade
2 1 Service Upgrade
Upgrading software images to compatible versions. Continue? [Y/N]:y
This operation might take several minutes, please wait...Done.
· Method 2: Use the reboot method.
<Sysname> issu load file feature flash:/feature1-t0001016.bin chassis 2 reboot
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:/feature1-t0001016.bin on chassis 1 slot 0...Done.
Copying file flash:/feature1-t0001016.bin to chassis2#slot0#flash:/feature1-t0001016.bin......Done.
Verifying the file flash:/feature1-t0001016.bin on chassis 2 slot 0...Done.
Copying file flash:/feature1-t0001016.bin to chassis2#slot1#flash:/feature1-t0001016.bin......Done.
Verifying the file flash:/feature1-t0001016.bin on chassis 2 slot 1...Done.
Identifying the upgrade methods...Done.
Upgrade summary according to following table:
flash:/feature1-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.
# Perform a main/backup Feature1 process switchover.
<Sysname> issu run switchover
Upgrade summary according to following table:
flash:/feature1-t0001016.bin
Running Version New Version
Test 0001015 Test 0001016
Chassis Slot Switchover Way
1 0 Active standby process switchover
Upgrading software images to compatible versions. Continue? [Y/N]:y
This operation might take several minutes, please wait...Done.
# Upgrade the feature on the original master.
· If the upgrade used the recommended method:
<Sysname> issu commit chassis 1
Copying file flash:/feature1-t0001016.bin to chassis1#slot1#flash:/feature1-t0001016.bin......Done.
Verifying the file flash:/feature1-t0001016.bin on chassis 1 slot 1...Done.
Upgrade summary according to following table:
flash:/feature1-t0001016.bin
Running Version New Version
Test 0001015 Test 0001016
Chassis Slot Upgrade Way
1 0 Service Upgrade
1 1 Service Upgrade
Upgrading software images to compatible versions. Continue? [Y/N]:y
This operation might take several minutes, please wait...Done.
· If the upgrade used the reboot method:
<Sysname> issu commit chassis 1
Copying file flash:/feature1-t0001016.bin to chassis1#slot1#flash:/feature1-t0001016.bin......Done.
Verifying the file flash:/feature1-t0001016.bin on chassis 1 slot 1...Done.
Upgrade summary according to following table:
flash:/feature1-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.
# Verify that both members are running the new Feature1 image.
<Sysname> display install active
Active packages on chassis 1 slot 0:
flash:/boot-t0001015.bin
flash:/system-t0001015.bin
flash:/feature1-t0001016.bin
Active packages on chassis 1 slot 1:
flash:/boot-t0001015.bin
flash:/system-t0001015.bin
flash:/feature1-t0001016.bin
Active packages on chassis 2 slot 0:
flash:/boot-t0001015.bin
flash:/system-t0001015.bin
flash:/feature1-t0001016.bin
Active packages on chassis 2 slot 1:
flash:/boot-t0001015.bin
flash:/system-t0001015.bin
flash:/feature1-t0001016.bin
Example: Upgrading a feature to an incompatible version
Network configuration
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 Feature1 feature from T0001015 to T0001016. The two versions are incompatible.
Procedure
# Download the image file that contains the T0001016 Feature1 feature from the TFTP server.
<Sysname> tftp 2.2.2.2 get feature1-t0001016.bin
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 256 100 256 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:/feature1-t0001015.bin
Active packages on chassis 1 slot 1:
flash:/boot-t0001015.bin
flash:/system-t0001015.bin
flash:/feature1-t0001015.bin
Active packages on chassis 2 slot 0:
flash:/boot-t0001015.bin
flash:/system-t0001015.bin
flash:/feature1-t0001015.bin
Active packages on chassis 2 slot 1:
flash:/boot-t0001015.bin
flash:/system-t0001015.bin
flash:/feature1-t0001015.bin
# Identify the recommended ISSU methods and possible impact of the upgrade.
<Sysname> display version comp-matrix file feature flash:/feature1-t0001016.bin
Verifying the file flash:/feature1-t0001016.bin on chassis 1 slot 0...Done.
Incompatible upgrade.
The output shows that the two versions are incompatible. The cards will be rebooted for the upgrade.
# Upgrade the Feature1 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:/feature1-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
Verifying the file flash:/feature1-t0001016.bin on chassis 1 slot 0...Done.
Copying file flash:/feature1-t0001016.bin to chassis2#slot0#flash:/feature1-t0001016.bin......Done.
Verifying the file flash:/feature1-t0001016.bin on chassis 2 slot 0...Done.
Copying file flash:/feature1-t0001016.bin to chassis2#slot1#flash:/feature1-t0001016.bin......Done.
Verifying the file flash:/feature1-t0001016.bin on chassis 2 slot 1...Done.
Identifying the upgrade methods...Done.
Upgrade summary according to following table:
flash:/feature1-t0001016.bin
Running Version New Version
Test 0001015 Test 0001016
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.
# 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:/feature1-t0001016.bin to chassis1#slot1#flash:/feature1-t0001016.bin......Done.
Verifying the file flash:/feature1-t0001016.bin on chassis 1 slot 1...Done.
Upgrade summary according to following table:
flash:/feature1-t0001016.bin
Running Version New Version
Test 0001015 Test 0001016
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...Done.
# Verify that both members are running the new Feature1 image.
<Sysname> display install active
Active packages on chassis 1 slot 0:
flash:/boot-t0001015.bin
flash:/system-t0001015.bin
flash:/feature1-t0001016.bin
Active packages on chassis 1 slot 1:
flash:/boot-t0001015.bin
flash:/system-t0001015.bin
flash:/feature1-t0001016.bin
Active packages on chassis 2 slot 0:
flash:/boot-t0001015.bin
flash:/system-t0001015.bin
flash:/feature1-t0001016.bin
Active packages on chassis 2 slot 1:
flash:/boot-t0001015.bin
flash:/system-t0001015.bin
flash:/feature1-t0001016.bin
Examples of using install commands for ISSU (in standalone mode)
Example: Upgrading a feature
Network configuration
As shown in Figure 5, the device has two MPUs. The active MPU is in slot 0. The standby MPU is in slot 1.
Upgrade the Feature1 feature from T0001015 to T0001016. The two versions are compatible.
Procedure
# Download the .ipe file that contains the T0001016 Feature1 feature image from the TFTP server.
<Sysname> tftp 2.2.2.2 get feature1-t0001016.ipe
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 256 100 256 0 0 764 0 --:--:-- --:--:-- --:--:-- 810
Writing file...Done.
# Decompress the .ipe file.
<Sysname> install add flash:/feature1-t0001016.ipe flash:/
Verifying the file flash:/feature1-t0001016.ipe on slot 0...Done.
Decompressing file feature1-t0001016.bin to flash:/feature1-t0001016.bin.......................Done.
# Display active software images.
<Sysname> display install active
Active packages on slot 0:
flash:/boot-t0001015.bin
flash:/system-t0001015.bin
flash:/feature1-t0001015.bin
Active packages on slot 1:
flash:/boot-t0001015.bin
flash:/system-t0001015.bin
flash:/feature1-t0001015.bin
# Identify the recommended ISSU methods and possible impact of the upgrade.
<Sysname> install activate feature flash:/feature1-t0001016.bin slot 1 test
Copying file flash:/feature1-t0001016.bin to slot1#flash:/feature1-t0001016.bin......Done.
Verifying the file flash:/feature1-t0001016.bin on slot 1...Done.
Upgrade summary according to following table:
flash:/feature1-t0001016.bin
Running Version New Version
Test 0001015 Test 0001016
Slot Upgrade Way
1 Service Upgrade
Influenced service according to following table on slot 1:
flash:/feature1-t0001016.bin
Feature1
<Sysname> install activate feature flash:/feature1-t0001016.bin slot 0 test
Verifying the file flash:/feature1-t0001016.bin on slot 0...Done.
Upgrade summary according to following table:
flash:/feature1-t0001016.bin
Running Version New Version
Test 0001015 Test 0001016
Slot Upgrade Way
0 Service Upgrade
1 Service Upgrade
Influenced service according to following table on slot 0:
flash:/feature1-t0001016.bin
Feature1
The output shows that both MPUs need a service upgrade and the Feature1 module will be rebooted during the upgrade.
# Activate the new Feature1 image to upgrade the Feature1 feature.
<Sysname> install activate feature flash:/feature1-t0001016.bin slot 1
flash:/feature1-t0001016.bin already exists on slot 1.
Overwrite it?[Y/N]:y
Copying file flash:/feature1-t0001016.bin to slot1#flash:/feature1-t0001016.bin......Done.
Verifying the file flash:/feature1-t0001016.bin on slot 1...Done.
Upgrade summary according to following table:
flash:/feature1-t0001016.bin
Running Version New Version
Test 0001015 Test 0001016
Slot Upgrade Way
1 Service Upgrade
Upgrading software images to compatible versions. Continue? [Y/N]:y
This operation might take several minutes, please wait...Done.
<Sysname> install activate feature flash:/feature1-t0001016.bin slot 0
Verifying the file flash:/feature1-t0001016.bin on slot 0...Done.
Upgrade summary according to following table:
flash:/feature1-t0001016.bin
Running Version New Version
Test 0001015 Test 0001016
Slot Upgrade Way
0 Service Upgrade
1 Service Upgrade
Upgrading software images to compatible versions. Continue? [Y/N]:y
This operation might take several minutes, please wait...Done.
# Verify that the new Feature1 image has been activated.
<Sysname> display install active
Active packages on slot 0:
flash:/boot-t0001015.bin
flash:/system-t0001015.bin
flash:/feature1-t0001016.bin
Active packages on slot 1:
flash:/boot-t0001015.bin
flash:/system-t0001015.bin
flash:/feature1-t0001016.bin
# Commit the software changes.
<Sysname> install commit
This operation will take several minutes, please wait...........................Done.
Examples of using install commands for ISSU (in IRF mode)
Example: Upgrading a feature
Network configuration
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).
Upgrade the Feature1 feature from T0001015 to T0001016. The two versions are compatible.
Procedure
# Download the .ipe file that contains the T0001016 Feature1 feature image from the TFTP server.
<Sysname> tftp 2.2.2.2 get feature1-t0001016.ipe
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 256 100 256 0 0 764 0 --:--:-- --:--:-- --:--:-- 810
Writing file...Done.
# Decompress the .ipe file.
<Sysname> install add flash:/feature1-t0001016.ipe flash:
Verifying the file flash:/feature1-t0001016.ipe on slot 1...Done.
Decompressing file feature1-t0001016.bin to flash:/feature1-t0001016.bin.......................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:/feature1-t0001015.bin
Active packages on chassis 1 slot 1:
flash:/boot-t0001015.bin
flash:/system-t0001015.bin
flash:/feature1-t0001015.bin
Active packages on chassis 2 slot 0:
flash:/boot-t0001015.bin
flash:/system-t0001015.bin
flash:/feature1-t0001015.bin
Active packages on chassis 2 slot 1:
flash:/boot-t0001015.bin
flash:/system-t0001015.bin
flash:/feature1-t0001015.bin
# Identify the recommended ISSU methods and possible impact of the upgrade.
<Sysname> install activate feature flash:/feature1-t0001016.bin chassis 2 slot 1 test
Copying file flash:/feature1-t0001016.bin to chassis2#slot1#flash:/feature1-t0001016.bin......Done.
Verifying the file flash:/feature1-t0001016.bin on chassis 2 slot 1...Done.
Upgrade summary according to following table:
flash:/feature1-t0001016.bin
Running Version New Version
Test 0001015 Test 0001016
Chassis Slot Upgrade Way
2 0 Service Upgrade
2 1 Service Upgrade
Influenced service according to following table on chassis 2 slot 0:
flash:/feature1-t0001016.bin
Feature1
Influenced service according to following table on chassis 2 slot 1:
flash:/feature1-t0001016.bin
Feature1
<Sysname> install activate feature flash:/feature1-t0001016.bin chassis 2 slot 0 test
Copying file flash:/feature1-t0001016.bin to chassis2#slot0#flash:/feature1-t0001016.bin......Done.
Verifying the file flash:/feature1-t0001016.bin on chassis 2 slot 0...Done.
Upgrade summary according to following table:
flash:/feature1-t0001016.bin
Running Version New Version
Test 0001015 Test 0001016
Chassis Slot Upgrade Way
2 0 Service Upgrade
Influenced service according to following table on chassis 2 slot 0:
flash:/feature1-t0001016.bin
Feature1
<Sysname> install activate feature flash:/feature1-t0001016.bin chassis 1 slot 1 test
Copying file flash:/feature1-t0001016.bin to chassis1#slot1#flash:/feature1-t0001016.bin......Done.
Verifying the file flash:/feature1-t0001016.bin on chassis 1 slot 1...Done.
Upgrade summary according to following table:
flash:/feature1-t0001016.bin
Running Version New Version
Test 0001015 Test 0001016
Chassis Slot Upgrade Way
1 0 Service Upgrade
1 1 Service Upgrade
Influenced service according to following table on chassis 1 slot 0:
flash:/feature1-t0001016.bin
Feature1
Influenced service according to following table on chassis 1 slot 1:
flash:/feature1-t0001016.bin
Feature1
<Sysname> install activate feature flash:/feature1-t0001016.bin chassis 1 slot 0 test
Verifying the file flash:/feature1-t0001016.bin on chassis 1 slot 0...Done.
Upgrade summary according to following table:
flash:/feature1-t0001016.bin
Running Version New Version
Test 0001015 Test 0001016
Chassis Slot Upgrade Way
1 0 Service Upgrade
Influenced service according to following table on chassis 1 slot 0:
flash:/feature1-t0001016.bin
Feature1
The output shows that all the MPUs need a service upgrade and the Feature1 module will be rebooted during the upgrade.
# Activate the new Feature1 image to upgrade the Feature1 feature.
<Sysname> install activate feature flash:/feature1-t0001016.bin chassis 2 slot 1
Verifying the file flash:/feature1-t0001016.bin on chassis 2 slot 1...Done.
flash:/feature1-t0001016.bin already exists on chassis 2 slot 1.
Overwrite it?[Y/N]:y
Copying file flash:/feature1-t0001016.bin to chassis2#slot1#flash:/feature1-t0001016.bin......Done.
Verifying the file flash:/feature1-t0001016.bin on chassis 2 slot 1...Done.
Upgrade summary according to following table:
flash:/feature1-t0001016.bin
Running Version New Version
Test 0001015 Test 0001016
Chassis Slot Upgrade Way
2 0 Service Upgrade
2 1 Service Upgrade
Upgrading software images to compatible versions. Continue? [Y/N]:y
This operation might take several minutes, please wait...Done.
<Sysname> install activate feature flash:/feature1-t0001016.bin chassis 2 slot 0
flash:/feature1-t0001016.bin already exists on chassis 2 slot 0.
Overwrite it?[Y/N]:y
Copying file flash:/feature1-t0001016.bin to chassis2#slot0#flash:/feature1-t0001016.bin......Done.
Verifying the file flash:/feature1-t0001016.bin on chassis 2 slot 0...Done.
Upgrade summary according to following table:
flash:/feature1-t0001016.bin
Running Version New Version
Test 0001015 Test 0001016
Chassis Slot Upgrade Way
2 0 Service Upgrade
Upgrading software images to compatible versions. Continue? [Y/N]:y
This operation might take several minutes, please wait...Done.
<Sysname> install activate feature flash:/feature1-t0001016.bin chassis 1 slot 1
flash:/feature1-t0001016.bin already exists on chassis 1 slot 1.
Overwrite it?[Y/N]:y
Copying file flash:/feature1-t0001016.bin to chassis1#slot1#flash:/feature1-t0001016.bin......Done.
Verifying the file flash:/feature1-t0001016.bin on chassis 1 slot 1...Done.
Upgrade summary according to following table:
flash:/feature1-t0001016.bin
Running Version New Version
Test 0001015 Test 0001016
Chassis Slot Upgrade Way
1 0 Service Upgrade
1 1 Service Upgrade
Upgrading software images to compatible versions. Continue? [Y/N]:y
This operation might take several minutes, please wait...Done.
<Sysname> install activate feature flash:/feature1-t0001016.bin chassis 1 slot 0
Verifying the file flash:/feature1-t0001016.bin on chassis 1 slot 0...Done.
Upgrade summary according to following table:
flash:/feature1-t0001016.bin
Running Version New Version
Test 0001015 Test 0001016
Chassis Slot Upgrade Way
1 0 Service Upgrade
Upgrading software images to compatible versions. Continue? [Y/N]:y
This operation might take several minutes, please wait...Done.
# Verify that the new Feature1 image has been activated.
<Sysname> display install active
Active packages on chassis 1 slot 0:
flash:/boot-t0001015.bin
flash:/system-t0001015.bin
flash:/feature1-t0001016.bin
Active packages on chassis 1 slot 1:
flash:/boot-t0001015.bin
flash:/system-t0001015.bin
flash:/feature1-t0001016.bin
Active packages on chassis 2 slot 0:
flash:/boot-t0001015.bin
flash:/system-t0001015.bin
flash:/feature1-t0001016.bin
Active packages on chassis 2 slot 1:
flash:/boot-t0001015.bin
flash:/system-t0001015.bin
flash:/feature1-t0001016.bin
# Commit the software changes.
<Sysname> install commit
This operation will take several minutes, please wait...........................Done.