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

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

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

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

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

ISSU methods

ISSU methods are automatically determined depending on the compatibility between software versions.

ISSU supports the following upgrade types:

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

· Incompatible upgrade—The running software version is incompatible with the new 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 method."

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.
Reboot	CAUTION: The Reboot method disrupts service if hardware redundancy (MPU- or device-level) is not available. As a best practice, schedule the downtime carefully to minimize the upgrade impact on the services. The Reboot method reboots MPUs to complete the software upgrade. While one MPU is rebooting, the other MPUs can provide services.

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.

Reboot

CAUTION:

The Reboot method disrupts service if hardware redundancy (MPU- or device-level) is not available. As a best practice, schedule the downtime carefully to minimize the upgrade impact on the services.

The Reboot method reboots MPUs to complete the software upgrade. While one MPU is rebooting, the other MPUs can provide services.

ISSU commands

ISSU includes the install and issu command sets. After you identify the 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 install/uninstall	Not supported.	Supported.
Upgrade mode	Chassis by chassis.	MPU by MPU.
Applicable image types and application scenarios	· Multichassis IRF fabrics. · Multiparent IRF 3 systems. You can upgrade the boot image, system image, and feature images.	· IRF 3 system where only PEXs need to be upgraded. You can upgrade the boot image, system image, and feature images. · Standalone device, IRF fabric, or IRF 3 system where only feature images need to be upgraded. · Standalone device, IRF fabric, or IRF 3 system that needs to be patched.
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.

Preparing for ISSU

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

Identifying ISSU availability and licensing requirements

If the IRF 3 fabric has one tier of PEXs and a PEX is connected to only one parent device, ISSU is not supported. To upgrade the parent devices and PEXs, you must use the boot-loader file command. For more information about PEXs, see Virtual Technologies Configuration Guide.

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 before ISSU. 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 no cards are in Fault state.

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

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

Preparing the upgrade images

1. Use the dir command to verify that all MPUs have sufficient storage space for the upgrade images. Use the display mdc resource command to verify that all MDCs have sufficient 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 the file system."

2. Use FTP or TFTP to transfer upgrade image files (in .bin or .ipe) to the root directory of a storage medium on any one of the MPUs.

Identifying the ISSU method

1. Execute the display version comp-matrix file command for the upgrade image version compatibility information.

2. Check the Version compatibility list field.

¡ If the running software version is in the list, a compatible upgrade is required.

¡ If the running software version is not in the list, an incompatible upgrade is required.

3. Identify the ISSU method.

¡ If a compatible upgrade is required, check the Upgrade Way field to identify the ISSU method. For more information about ISSU methods, see Table 1.

¡ If an incompatible upgrade is required, check the end of command output for the Incompatible upgrade string.

Verifying feature status

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

Feature	Setting requirements
GR/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	· Set the physical state change suppression interval to 0 on Ethernet interfaces so their physical state changes are immediately reported to the CPU. · Enable link-aggregation traffic redirection to ensure continuous traffic service. · Enable the IRF bridge MAC address to be permanent.

Determining the upgrade procedure

IMPORTANT:

To ensure a successful ISSU, strictly follow the recommended ISSU procedure. Make sure a step is completed successfully before you proceed with the next step.

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

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

Understanding ISSU guidelines

During an ISSU, use the following guidelines:

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

· Do not perform any of the following tasks during an ISSU:

¡ Reboot, add, or remove cards.

¡ Execute commands that are irrelevant to the ISSU.

¡ Modify, delete, or rename image files.

· You cannot use both install and issu commands for an ISSU. However, you can use display issu commands with both command sets. For more information, see "Displaying and maintaining ISSU."

· You do not need to upgrade LPUs separately. They are upgraded automatically when MPUs are upgraded.

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

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

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

Logging in to the device through the console port

Log in to the device through the console port after you finish all the preparation tasks and read all the ISSU guidelines.

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

Adjusting and saving the running configuration

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

IMPORTANT:

For a successful ISSU, you must identify all feature changes between the current version and the new version and remove all commands that the new version does not support.

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

IMPORTANT:

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

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

Performing an ISSU by using issu commands

Perform this task only on a multichassis IRF fabric or a multiparent IRF 3 system.

Always start ISSU with a subordinate member.

Performing a compatible upgrade

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Disable automatic rollback.	issu rollback-timer 0	By default, the automatic rollback timer is set to 45 minutes. As a best practice, do not use the automatic rollback feature. This feature is complicated.
3. Return to user view.	quit	N/A
4. (Optional.) Specify PEX startup images.	· Use .bin files: issu pex pex-model file { boot filename \| system filename \| feature filename&<1-30> } * · Use an .ipe file: issu pex pex-model file ipe ipe-filename	Perform this step if you want to upgrade PEXs.
5. Load the upgrade images as main startup software images on subordinate members.	· Use .bin image files: issu load file { boot filename \| system filename \| feature filename&<1-30> } * chassis chassis-number · Use an .ipe image file: issu load file ipe ipe-filename chassis chassis-number&<1-3>	Specify the member ID of a subordinate member for the chassis-number argument. The command also upgrades single-homed PEXs that are attached to the specified subordinate members.
6. Perform a switchover.	issu run switchover	This command also upgrades multihomed PEXs.
7. (Optional.) Accept the upgrade.	issu accept	N/A
8. Upgrade the remaining members to complete the ISSU.	issu commit chassis chassis-number	Repeat the issu commit command to upgrade the remaining members one by one, including the original master. IMPORTANT: After executing the command for one member, you must wait for the member to restart and join the IRF fabric before you execute the command for another member.
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

Perform this task in user view.

Step	Command	Remarks
1. (Optional.) Specify PEX startup images.	· Use .bin files: issu pex pex-model file { boot filename \| system filename \| feature filename&<1-30> } * · Use an .ipe file: issu pex pex-model file ipe ipe-filename	Perform this step if you want to upgrade PEXs.
2. Load the upgrade images as main startup software images on subordinate members.	· Use .bin image files: issu load file { boot filename \| system filename \| feature filename&<1-30> } * chassis chassis-number&<1-3> · Use an .ipe image file: issu load file ipe ipe-filename chassis chassis-number&<1-3>	IMPORTANT: Because incompatible versions cannot run simultaneously, the upgraded subordinate devices will be isolated and cannot forward traffic until a master/subordinate switchover occurs. As a best practice in 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. Specify the member ID of a subordinate member for the chassis-number argument. This command also upgrades the PEXs that are attached only to the specified subordinate members.
3. Perform a master/subordinate switchover to complete the ISSU process.	issu run switchover	This command upgrades the remaining members and PEXs.

Performing an ISSU by using install commands

ISSU task list

Tasks at a glance	Remarks
(Optional.) Decompressing an .ipe file	To use install commands for upgrade, you must use .bin image files. If the upgrade file is an .ipe file, perform this task before you use install commands for upgrade.
(Required.) Perform one of the following tasks to update software: · Installing or upgrading software images ¡ Installing or upgrading images for PEXs ¡ Installing or upgrading feature images ¡ Installing patch images · Uninstalling feature or patch images ¡ Uninstalling feature images ¡ Uninstalling patch images	Perform an activate operation to install new images or upgrade existing images. Perform a deactivate operation to uninstall feature or patch images. An image is added to or removed from the current software image list when it is activated or deactivated.
(Optional.) Aborting a software activate/deactivate operation	You can perform this task while an image is being activated or deactivated. This task is available only for service upgrade or file upgrade.
(Optional.) Committing software changes	This task updates the main startup image list with the changes. If service upgrade or file upgrade is performed, you must perform this task for the changes to take effect after a reboot.
(Optional.) Verifying software images	Perform this task to verify that the software changes are correct.
(Optional.) Deleting inactive software images	Perform this task to delete images

Decompressing an .ipe file

Perform this task in user view.

Step	Command
1. (Optional.) Identify images that are included in the .ipe file.	display install ipe-info
2. Decompress the .ipe file.	install add ipe-filename medium-name:

Installing or upgrading software images

Use one of the following methods to perform this task:

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

In standalone mode:

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

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

In IRF mode:

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

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

When you install or upgrade images on an active MPU, the system automatically upgrades its LPUs. You do not need to upgrade their software separately.

Installing or upgrading images for PEXs

Perform this task in an IRF 3 system when only PEXs need to be upgraded.

Perform this task in user view.

Step	Command	Remarks
1. (Optional.) Identify the ISSU method and possible impact of the upgrade.	install activate { boot filename \| system filename \| feature filename&<1-30> } * chassis chassis-number slot slot-number test	Specify the virtual chassis number of a PEX for the chassis-number argument.
2. Activate images.	install activate { boot filename \| system filename \| feature filename&<1-30> } * chassis chassis-number slot slot-number	Specify the virtual chassis number of a PEX for the chassis-number argument.

Installing or upgrading feature images

You can perform this task on a standalone device, an IRF fabric, or an IRF 3 system.

Perform this task in user view.

Step	Command	Remarks
1. (Optional.) Identify the ISSU method and 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	The device does not support the boot filename or system filename option. To upgrade a PEX, specify the virtual chassis number of the PEX for the chassis-number argument.
2. 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	The device does not support the boot filename or system filename option. To upgrade a PEX, specify the virtual chassis number of the PEX for the chassis-number argument.

Step

Command

Remarks

1. (Optional.) Identify the ISSU method and 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

The device does not support the boot filename or system filename option.

To upgrade a PEX, specify the virtual chassis number of the PEX for the chassis-number argument.

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

The device does not support the boot filename or system filename option.

To upgrade a PEX, specify the virtual chassis number of the PEX for the chassis-number argument.

Installing patch images

You can perform this task on a standalone device, an IRF fabric, or an IRF 3 system.

If a system image has multiple versions of patch images, you only need to install the latest version. You do not need to uninstall older patch images before you install a new patch image.

Perform this task in user view.

Task	Command	Remarks
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 }	To patch a PEX, specify the virtual chassis number of the PEX for the chassis-number argument.

Task

Command

Remarks

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 }

To patch a PEX, specify the virtual chassis number of the PEX for the chassis-number argument.

Uninstalling feature or patch images

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

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

Boot and system images cannot be uninstalled.

Uninstalling feature images

Perform this task in user view.

Task	Command	Remarks
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	To deactivate feature images on a PEX, perform the following tasks: · Specify the virtual chassis number of the PEX for the chassis-number argument. · Specify the virtual slot number of the PEX for the slot-number argument.

Task

Command

Remarks

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

To deactivate feature images on a PEX, perform the following tasks:

· Specify the virtual chassis number of the PEX for the chassis-number argument.

· Specify the virtual slot number of the PEX for the slot-number argument.

Uninstalling patch images

Perform this task in user view.

Task	Command	Remarks
Deactivate patch images.	· In standalone mode: install deactivate patch filename slot slot-number · In IRF mode: install deactivate patch filename chassis chassis-number slot slot-number	To deactivate patch images on a PEX, perform the following tasks: · Specify the virtual chassis number of the PEX for the chassis-number argument. · Specify the virtual slot number of the PEX for the slot-number argument.

Task

Command

Remarks

Deactivate patch images.

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

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

To deactivate patch images on a PEX, perform the following tasks:

· Specify the virtual chassis number of the PEX for the chassis-number argument.

· Specify the virtual slot number of the PEX for the slot-number argument.

Aborting a software activate/deactivate operation

This task is available only for service upgrade or file upgrade performed through activate or deactivate operation. After the operation is aborted, the system runs with the software images that it was running with before the operation.

Task	Command
Abort a software activate/deactivate operation.	· Method 1: Press Ctrl+C while a software image is being activated or deactivated. · Method 2: Abort a software activate/deactivate operation in user view. install abort [ job-id ]

Task

Command

Abort a software activate/deactivate operation.

· Method 1: Press Ctrl+C while a software image is being activated or deactivated.

· Method 2: Abort a software activate/deactivate operation in user view.
install abort [ job-id ]

Committing software changes

When you activate or deactivate images for an incremental upgrade, or install or uninstall patches, 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.

Perform this task in user view.

Task	Command	Remarks
Commit the software changes.	install commit	This command commits all software changes, including software changes for PEXs.

Verifying software images

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.

If an image is not integral, consistent, or committed, use the install activate, install deactivate, and install commit commands as appropriate to resolve the issue.

Perform this task in user view.

Task	Command	Remarks
Verify software images.	install verify	This command takes effect for both the parent devices and PEXs.

Deleting inactive software images

This task permanently deletes inactive image files from the device.

Perform this task in user view.

Task	Command	Remarks
Delete inactive software images.	· In standalone mode: install remove [ slot slot-number ] { filename \| inactive } · In IRF mode: install remove [ chassis chassis-number slot slot-number ] { filename \| inactive }	To delete inactive software images from a PEX, perform the following tasks: · Specify the virtual chassis number of the PEX for the chassis-number argument. · Specify the virtual slot number of the PEX for the slot-number argument.

Task

Command

Remarks

Delete inactive software images.

· In standalone mode:
install remove [ slot slot-number ] { filename | inactive }

· In IRF mode:
install remove [ chassis chassis-number slot slot-number ] { filename | inactive }

To delete inactive software images from a PEX, perform the following tasks:

· Specify the virtual chassis number of the PEX for the chassis-number argument.

· Specify the virtual slot number of the PEX for the slot-number argument.

Displaying and maintaining ISSU

Standalone mode

The commands in this section applies to devices in standalone mode.

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

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

IRF mode

The commands in this section applies to devices 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.	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 and deactivate 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 all software image files that include a specific component or file.	display install which { component name \| file filename } [ chassis chassis-number slot slot-number ]	N/A
Display ISSU status information.	display issu state	This command applies only to an ISSU that uses the issu series commands.
Display version compatibility information and identify the upgrade method.	display version comp-matrix	N/A
Clear ISSU log entries.	reset install log-history oldest log-number	N/A

Troubleshooting ISSU in IRF mode

Failure to execute the issu load/issu run switchover/issu commit/install activate/install deactivate command

Symptom

The following commands cannot be executed:

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

· install commands—install activate and install deactivate.

Solution

To resolve this issue:

1. Use the display device command to verify that all cards are not in Fault state.

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

3. If the problem persists, contact H3C Support.

Examples of using issu commands for ISSU on a dual-member IRF fabric

HTTP feature upgrade to a compatible version

Upgrade requirements

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

Upgrade the HTTP feature from R0201 to R0202. The two versions are compatible.

Figure 1 Network diagram

Upgrade procedure

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

<Sysname> tftp 2.2.2.2 get http-r0202.bin

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

Dload Upload Total Spent Left Speed

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

# Display active software images.

<Sysname> display install active

Active packages on chassis 1 slot 6:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 1 slot 7:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 2 slot 6:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 2 slot 7:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

# Identify the ISSU method and possible impact of the upgrade.

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

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

Feature image: flash:/http-r0202.bin

Version:

V700R001B45D002

Version Compatibility List:

V700R001B45D001

V700R001B45D002

Version Dependency System List:

V700R001B45D001

V700R001B45D002

Chassis Slot Upgrade Way

1 6 Service Upgrade

1 7 Service Upgrade

2 6 Service Upgrade

2 7 Service Upgrade

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

flash:/http-r0202.bin

HTTP CFA

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

flash:/http-r0202.bin

HTTP CFA

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

flash:/http-r0202.bin

HTTP CFA

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

flash:/http-r0202.bin

HTTP CFA

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

# Disable automatic rollback.

<Sysname> system-view

[Sysname] issu rollback-timer 0

# Enable link-aggregation traffic redirection.

[Sysname] link-aggregation lacp traffic-redirect-notification enable

# Enable the IRF bridge MAC address to be permanent.

[Sysname] irf mac-address persistent always

# Set the physical state change suppression interval to 0 on the interfaces.

[Sysname] interface gigabitethernet1/3/0/1

[Sysname-GigabitEthernet1/3/0/1] link-delay 0 mode updown

[Sysname-GigabitEthernet1/3/0/1] quit

[Sysname] interface gigabitethernet2/3/0/1

[Sysname-GigabitEthernet2/3/0/1] link-delay 0 mode updown

[Sysname-GigabitEthernet2/3/0/1] quit

[Sysname] quit

# Upgrade the HTTP feature on the subordinate member.

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

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

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

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

Verifying the file flash:/http-r0202.bin on Chassis 2 slot 6...Done.

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

Verifying the file flash:/http-r0202.bin on Chassis 2 slot 7...Done.

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Chassis Slot Upgrade Way

2 6 Service Upgrade

2 7 Service Upgrade

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

# Perform a main/backup HTTP process switchover.

<Sysname> issu run switchover

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Chassis Slot Switchover Way

1 6 Active standby process switchover

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

# Upgrade the feature on the original master.

<Sysname> issu commit chassis 1

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

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

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Chassis Slot Upgrade Way

1 6 Service Upgrade

1 7 Service Upgrade

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

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

<Sysname> display install active

Active packages on chassis 1 slot 6:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on chassis 1 slot 7:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on chassis 2 slot 6:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on chassis 2 slot 7:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

HTTP feature upgrade to an incompatible version

Upgrade requirements

As shown in Figure 2, the IRF fabric has two members. Each member has one MPU in slot 6 (active MPU) and one MPU in slot 7 (standby MPU).

Upgrade the HTTP feature from R0201 to R0202. The two versions are incompatible.

Figure 2 Network diagram

Upgrade procedure

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

<Sysname> tftp 2.2.2.2 get http-r0202.bin

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

Dload Upload Total Spent Left Speed

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

# Display active software images.

<Sysname> display install active

Active packages on chassis 1 slot 6:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 1 slot 7:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 2 slot 6:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 2 slot 7:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

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

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

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

Feature image: flash:/http-r0202.bin

Version:

V700R001B45D002

Version Compatibility List:

V700R001B45D002

Version Dependency System List:

V700R001B45D001

V700R001B45D002

Incompatible upgrade.

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

# Enable link-aggregation traffic redirection.

[Sysname] link-aggregation lacp traffic-redirect-notification enable

# Enable the IRF bridge MAC address to be permanent.

[Sysname] irf mac-address persistent always

# Set the physical state change suppression interval to 0 on the interfaces.

[Sysname] interface gigabitethernet1/3/0/1

[Sysname-GigabitEthernet1/3/0/1] link-delay 0 mode updown

[Sysname-GigabitEthernet1/3/0/1] quit

[Sysname] interface gigabitethernet2/3/0/1

[Sysname-GigabitEthernet2/3/0/1] link-delay 0 mode updown

[Sysname-GigabitEthernet2/3/0/1] quit

[Sysname] quit

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

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

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

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

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

Verifying the file flash:/http-r0202.bin on Chassis 2 slot 6...Done.

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

Verifying the file flash:/http-r0202.bin on Chassis 2 slot 7...Done.

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Chassis Slot Upgrade Way

2 6 Reboot

2 7 Reboot

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

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

<Sysname> issu run switchover

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

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

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Chassis Slot Upgrade Way

1 6 Reboot

1 7 Reboot

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

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

<Sysname> display install active

Active packages on chassis 1 slot 6:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on chassis 1 slot 7:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on chassis 2 slot 6:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on chassis 2 slot 7:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Examples of using issu commands for ISSU on a four-member IRF fabric

Feature upgrade to a compatible version

Upgrade requirements

As shown in Figure 3, the IRF fabric has four members. Each member has one active MPU (slot 6), one standby MPU (slot 7), and one LPU (slot 3).

Upgrade a feature from soft-version1 to soft-version2 on the IRF fabric. The two versions are compatible.

Figure 3 Network diagram

Upgrade procedure

# Download the upgrade image file from the TFTP server.

<Sysname> tftp 2.2.2.2 get soft-version2.bin

Press CTRL+C to abort.

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

Dload Upload Total Spent Left Speed

100 13312 0 13312 0 0 295k 0 --:--:-- --:--:-- --:--:-- 309k

# Display active software images.

<Sysname> display install active

Active packages on chassis 1 slot 3:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version1.bin

Active packages on chassis 1 slot 6:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version1.bin

Active packages on chassis 1 slot 7:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version1.bin

Active packages on chassis 2 slot 3:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version1.bin

Active packages on chassis 2 slot 6:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version1.bin

Active packages on chassis 2 slot 7:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version1.bin

Active packages on chassis 3 slot 3:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version1.bin

Active packages on chassis 3 slot 6:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version1.bin

Active packages on chassis 3 slot 7:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version1.bin

Active packages on chassis 4 slot 3:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version1.bin

Active packages on chassis 4 slot 6:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version1.bin

Active packages on chassis 4 slot 7:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version1.bin

# Identify the ISSU method and possible impact of the upgrade.

<Sysname> display version comp-matrix file feature flash:/soft-version2.bin

Verifying the file flash:/soft-version2.bin on chassis 1 slot 6...Done.

Feature image: flash:/soft-version2.bin

Version:

7.1.045-Release 7168

Version compatibility list:

7.1.045-Release 7168

Version dependency system list:

7.1.045-Release 7168

Chassis Slot Upgrade Way

1 3 Service Upgrade

1 6 Service Upgrade

1 7 Service Upgrade

2 3 Service Upgrade

2 6 Service Upgrade

2 7 Service Upgrade

3 3 Service Upgrade

3 6 Service Upgrade

3 7 Service Upgrade

4 3 Service Upgrade

4 6 Service Upgrade

4 7 Service Upgrade

The output shows that service upgrade is recommended. The feature module will be rebooted during the upgrade.

# Disable automatic rollback.

<Sysname> system-view

[Sysname] issu rollback-timer 0

# Enable link-aggregation traffic redirection.

[Sysname] link-aggregation lacp traffic-redirect-notification enable

# Enable the IRF bridge MAC address to be permanent.

[Sysname] irf mac-address persistent always

# Set the physical state change suppression interval to 0 on the interfaces.

[Sysname] interface gigabitethernet1/3/0/1

[Sysname-GigabitEthernet1/3/0/1] link-delay 0 mode updown

[Sysname-GigabitEthernet1/3/0/1] quit

[Sysname] interface gigabitethernet2/3/0/1

[Sysname-GigabitEthernet2/3/0/1] link-delay 0 mode updown

[Sysname-GigabitEthernet2/3/0/1] quit

[Sysname] interface gigabitethernet3/3/0/1

[Sysname-GigabitEthernet3/3/0/1] link-delay 0 mode updown

[Sysname-GigabitEthernet3/3/0/1] quit

[Sysname] interface gigabitethernet4/3/0/1

[Sysname-GigabitEthernet4/3/0/1] link-delay 0 mode updown

[Sysname-GigabitEthernet4/3/0/1] quit

[Sysname] quit

# Upgrade the feature on subordinate member 2.

<Sysname> issu load file feature flash:/soft-version2.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:/soft-version2.bin on chassis 1 slot 6...Done.

Copying file flash:/soft-version2.bin to chassis2#slot6#flash:/soft-version2.bin

...Done.

Verifying the file flash:/soft-version2.bin on chassis 2 slot 6...Done

Copying file flash:/soft-version2.bin to chassis2#slot7#flash:/soft-version2.bin

...Done.

Verifying the file flash:/soft-version2.bin on chassis 2 slot 7...Done.

Upgrade summary according to following table:

flash:/soft-version2.bin

Running Version New Version

None Release 7168

Chassis Slot Upgrade Way

2 3 Service Upgrade

2 6 Service Upgrade

2 7 Service Upgrade

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

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

# Perform a main/backup feature process switchover.

<Sysname> issu run switchover

Upgrade summary according to following table:

flash:/soft-version2.bin

Running Version New Version

None Release 7168

Chassis Slot Switchover Way

1 6 Active standby process switchover

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

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

# Upgrade the feature on the original master and the other subordinate members.

<Sysname> issu commit chassis 1

Copying file flash:/soft-version2.bin to chassis1#slot7#flash:/soft-version2.bin

...Done.

Verifying the file flash:/soft-version2.bin on chassis 1 slot 7...Done.

Upgrade summary according to following table:

flash:/soft-version2.bin

Running Version New Version

None Release 7168

Chassis Slot Upgrade Way

1 3 Service Upgrade

1 6 Service Upgrade

1 7 Service Upgrade

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

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

<Sysname> issu commit chassis 3

Copying file flash:/soft-version2.bin to chassis3#slot6#flash:/soft-version2.bin

...Done.

Verifying the file flash:/soft-version2.bin on chassis 3 slot 6...Done

Copying file flash:/soft-version2.bin to chassis3#slot7#flash:/soft-version2.bin

...Done.

Verifying the file flash:/soft-version2.bin on chassis 3 slot 7...Done.

Upgrade summary according to following table:

flash:/soft-version2.bin

Running Version New Version

None Release 7168

Chassis Slot Upgrade Way

3 3 Service Upgrade

3 6 Service Upgrade

3 7 Service Upgrade

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

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

<Sysname> issu commit chassis 4

Copying file flash:/soft-version2.bin to chassis4#slot6#flash:/soft-version2.bin

...Done.

Verifying the file flash:/soft-version2.bin on chassis 4 slot 6...Done

Copying file flash:/soft-version2.bin to chassis4#slot7#flash:/soft-version2.bin

...Done.

Verifying the file flash:/soft-version2.bin on chassis 4 slot 7...Done

Upgrade summary according to following table:

flash:/soft-version2.bin

Running Version New Version

None Release 7168

Chassis Slot Upgrade Way

4 3 Service Upgrade

4 6 Service Upgrade

4 7 Service Upgrade

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

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

# Verify that all members are running the new image.

<Sysname> display install active

Active packages on chassis 1 slot 3:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version2.bin

Active packages on chassis 1 slot 6:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version2.bin

Active packages on chassis 1 slot 7:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version2.bin

Active packages on chassis 2 slot 3:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version2.bin

Active packages on chassis 2 slot 6:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version2.bin

Active packages on chassis 2 slot 7:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version2.bin

Active packages on chassis 3 slot 3:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version2.bin

Active packages on chassis 3 slot 6:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version2.bin

Active packages on chassis 3 slot 7:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version2.bin

Active packages on chassis 4 slot 3:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version2.bin

Active packages on chassis 4 slot 6:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version2.bin

Active packages on chassis 4 slot 7:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version2.bin

Feature upgrade to an incompatible version (upgrading one subordinate member first)

Upgrade requirements

As shown in Figure 4, the IRF fabric has four members. Each member has one active MPU (slot 6), one standby MPU (slot 7), and one LPU (slot 3).

Upgrade a feature from soft-version1 to soft-version2 on the IRF fabric. The two versions are incompatible.

Figure 4 Network diagram

Upgrade procedure

# Download the upgrade image file from the TFTP server.

<Sysname> tftp 2.2.2.2 get soft-version2.bin

Press CTRL+C to abort.

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

Dload Upload Total Spent Left Speed

100 13312 0 13312 0 0 295k 0 --:--:-- --:--:-- --:--:-- 309k

# Display active software images.

<Sysname> display install active

Active packages on chassis 1 slot 3:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version1.bin

Active packages on chassis 1 slot 6:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version1.bin

Active packages on chassis 1 slot 7:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version1.bin

Active packages on chassis 2 slot 3:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version1.bin

Active packages on chassis 2 slot 6:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version1.bin

Active packages on chassis 2 slot 7:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version1.bin

Active packages on chassis 3 slot 3:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version1.bin

Active packages on chassis 3 slot 6:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version1.bin

Active packages on chassis 3 slot 7:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version1.bin

Active packages on chassis 4 slot 3:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version1.bin

Active packages on chassis 4 slot 6:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version1.bin

Active packages on chassis 4 slot 7:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version1.bin

# Identify the ISSU method and possible impact of the upgrade.

<Sysname> display version comp-matrix file feature flash:/soft-version2.bin

Verifying the file flash:/soft-version2.bin on chassis 1 slot 6...Don

Feature image: flash:/soft-version2.bin

Version:

7.1.045-Release 7168

Version compatibility list:

7.1.045-Release 7168

Version dependency system list:

7.1.045-Release 7168

Upgrade Way: Incompatible upgrade.

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

# Disable automatic rollback.

<Sysname> system-view

[Sysname] issu rollback-timer 0

# Enable link-aggregation traffic redirection.

[Sysname] link-aggregation lacp traffic-redirect-notification enable

# Enable the IRF bridge MAC address to be permanent.

[Sysname] irf mac-address persistent always

# Set the physical state change suppression interval to 0 on the interfaces.

[Sysname] interface gigabitethernet1/3/0/1

[Sysname-GigabitEthernet1/3/0/1] link-delay 0 mode updown

[Sysname-GigabitEthernet1/3/0/1] quit

[Sysname] interface gigabitethernet2/3/0/1

[Sysname-GigabitEthernet2/3/0/1] link-delay 0 mode updown

[Sysname-GigabitEthernet2/3/0/1] quit

[Sysname] interface gigabitethernet3/3/0/1

[Sysname-GigabitEthernet3/3/0/1] link-delay 0 mode updown

[Sysname-GigabitEthernet3/3/0/1] quit

[Sysname] interface gigabitethernet4/3/0/1

[Sysname-GigabitEthernet4/3/0/1] link-delay 0 mode updown

[Sysname-GigabitEthernet4/3/0/1] quit

[Sysname] quit

# Upgrade the feature on subordinate member 2. 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:/soft-version2.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:/soft-version2.bin on chassis 1 slot 6...Done.

Copying file flash:/soft-version2.bin to chassis2#slot6#flash:/soft-version2.bin

...Done.

Verifying the file flash:/soft-version2.bin on chassis 2 slot 6...Done.

Copying file flash:/soft-version2.bin to chassis2#slot7#flash:/ soft-version2.bin

...Done.

Verifying the file flash:/soft-version2.bin on chassis 2 slot 7...Done.

Upgrade summary according to following table:

flash:/soft-version2.bin

Running Version New Version

Release 7168 Release 7168

Chassis Slot Upgrade Way

2 3 Reboot

2 6 Reboot

2 7 Reboot

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

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

<Sysname> issu run switchover

Copying file flash:/soft-version2.bin to chassis1#slot7#flash:/soft-version2.bin

...Done.

Verifying the file flash:/soft-version2.bin on chassis 1 slot 7...Done.

Copying file flash:/soft-version2.bin to chassis3#slot6#flash:/soft-version2.bin

...Done.

Verifying the file flash:/soft-version2.bin on chassis 3 slot 6...Done.

Copying file flash:/soft-version2.bin to chassis3#slot7#flash:/soft-version2.bin

...Done.

Verifying the file flash:/soft-version2.bin on chassis 3 slot 7...Done.

Copying file flash:/soft-version2.bin to chassis4#slot6#flash:/soft-version2.bin

...Done.

Verifying the file flash:/soft-version2.bin on chassis 4 slot 6...Done.

Copying file flash:/soft-version2.bin to chassis4#slot7#flash:/soft-version2.bin

...Done.

Verifying the file flash:/soft-version2.bin on chassis 4 slot 7...Done.

Upgrade summary according to following table:

flash:/soft-version2.bin

Running Version New Version

Release 7168 Release 7168

Chassis Slot Upgrade Way

1 3 Reboot

1 6 Reboot

1 7 Reboot

3 3 Reboot

3 6 Reboot

3 7 Reboot

4 3 Reboot

4 6 Reboot

4 7 Reboot

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

# Verify that all members are running the new image.

<Sysname> display install active

Active packages on chassis 1 slot 3:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version2.bin

Active packages on chassis 1 slot 6:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version2.bin

Active packages on chassis 1 slot 7:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version2.bin

Active packages on chassis 2 slot 3:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version2.bin

Active packages on chassis 2 slot 6:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version2.bin

Active packages on chassis 2 slot 7:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version2.bin

Active packages on chassis 3 slot 3:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version2.bin

Active packages on chassis 3 slot 6:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version2.bin

Active packages on chassis 3 slot 7:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version2.bin

Active packages on chassis 4 slot 3:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version2.bin

Active packages on chassis 4 slot 6:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version2.bin

Active packages on chassis 4 slot 7:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version2.bin

Feature upgrade to an incompatible version (upgrading multiple subordinate members first)

Upgrade requirements

As shown in Figure 5, the IRF fabric has four members. Each member has one active MPU (slot 6), one standby MPU (slot 7), and one LPU (slot 3).

Upgrade a feature from soft-version1 to soft-version2 on the IRF fabric. The two versions are incompatible.

Figure 5 Network diagram

Upgrade procedure

# Download the upgrade image file from the TFTP server.

<Sysname> tftp 2.2.2.2 get soft-version2.bin

Press CTRL+C to abort.

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

Dload Upload Total Spent Left Speed

100 13312 0 13312 0 0 295k 0 --:--:-- --:--:-- --:--:-- 309k

# Display active software images.

<Sysname> display install active

Active packages on chassis 1 slot 3:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version1.bin

Active packages on chassis 1 slot 6:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version1.bin

Active packages on chassis 1 slot 7:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version1.bin

Active packages on chassis 2 slot 3:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version1.bin

Active packages on chassis 2 slot 6:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version1.bin

Active packages on chassis 2 slot 7:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version1.bin

Active packages on chassis 3 slot 3:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version1.bin

Active packages on chassis 3 slot 6:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version1.bin

Active packages on chassis 3 slot 7:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version1.bin

Active packages on chassis 4 slot 3:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version1.bin

Active packages on chassis 4 slot 6:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version1.bin

Active packages on chassis 4 slot 7:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version1.bin

# Identify the ISSU method and possible impact of the upgrade.

<Sysname> display version comp-matrix file feature flash:/soft-version2.bin

Verifying the file flash:/soft-version2.bin on chassis 2 slot 4...Done

Feature image: flash:/soft-version2.bin

Version:

7.1.045-Release 7168

Version compatibility list:

7.1.045-Release 7168

Version dependency system list:

7.1.045-Release 7168

Upgrade Way: Incompatible upgrade.

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

# Disable automatic rollback.

<Sysname> system-view

[Sysname] issu rollback-timer 0

# Enable link-aggregation traffic redirection.

[Sysname] link-aggregation lacp traffic-redirect-notification enable

# Enable the IRF bridge MAC address to be permanent.

[Sysname] irf mac-address persistent always

# Set the physical state change suppression interval to 0 on the interfaces.

[Sysname] interface gigabitethernet1/3/0/1

[Sysname-GigabitEthernet1/3/0/1] link-delay 0 mode updown

[Sysname-GigabitEthernet1/3/0/1] quit

[Sysname] interface gigabitethernet2/3/0/1

[Sysname-GigabitEthernet2/3/0/1] link-delay 0 mode updown

[Sysname-GigabitEthernet2/3/0/1] quit

[Sysname] interface gigabitethernet3/3/0/1

[Sysname-GigabitEthernet3/3/0/1] link-delay 0 mode updown

[Sysname-GigabitEthernet3/3/0/1] quit

[Sysname] interface gigabitethernet4/3/0/1

[Sysname-GigabitEthernet4/3/0/1] link-delay 0 mode updown

[Sysname-GigabitEthernet4/3/0/1] quit

[Sysname] quit

# Upgrade the feature on all subordinate members. After the upgrade, the subordinate members will leave the original IRF fabric and form a new IRF fabric.

<Sysname> issu load file feature flash:/soft-version2.bin chassis 2 3 4

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:/soft-version2.bin on chassis 1 slot 6...Done

Copying file flash:/soft-version2.bin to chassis2#slot6#flash:/soft-version2.bin

...Done.

Copying file flash:/soft-version2.bin to chassis2#slot7#flash:/soft-version2.bin

...Done.

Copying file flash:/soft-version2.bin to chassis3#slot6#flash:/soft-version2.bin

...Done.

Copying file flash:/soft-version2.bin to chassis3#slot7#flash:/soft-version2.bin

...Done.

Copying file flash:/soft-version2.bin to chassis4#slot6#flash:/soft-version2.bin

...Done.

Copying file flash:/soft-version2.bin to chassis4#slot7#flash:/soft-version2.bin

...Done.

Verifying the file flash:/soft-version2.bin on chassis 2 slot 6............Done.

Verifying the file flash:/soft-version2.bin on chassis 2 slot 7............Done.

Verifying the file flash:/soft-version2.bin on chassis 3 slot 6............Done.

Verifying the file flash:/soft-version2.bin on chassis 3 slot 7............Done.

Verifying the file flash:/soft-version2.bin on chassis 4 slot 6............Done.

Verifying the file flash:/soft-version2.bin on chassis 4 slot 7............Done.

Upgrade summary according to following table:

flash:/soft-version2.bin

Running Version New Version

Release 7168 Release 7168

Chassis Slot Upgrade Way

2 3 Reboot

2 6 Reboot

2 7 Reboot

3 3 Reboot

3 6 Reboot

3 7 Reboot

4 3 Reboot

4 6 Reboot

4 7 Reboot

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

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

<Sysname> issu run switchover

Copying file flash:/soft-version2.bin to chassis1#slot7#flash:/soft-version2.bin

...Done.

Verifying the file flash:/soft-version2.bin on chassis 1 slot 7............Done.

Upgrade summary according to following table:

flash:/soft-version2.bin

Running Version New Version

Release 7168 Release 7168

Chassis Slot Upgrade Way

1 3 Reboot

1 6 Reboot

1 7 Reboot

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

# Verify that all members are running the new image.

<Sysname> display install active

Active packages on chassis 1 slot 3:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version2.bin

Active packages on chassis 1 slot 6:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version2.bin

Active packages on chassis 1 slot 7:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version2.bin

Active packages on chassis 2 slot 3:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version2.bin

Active packages on chassis 2 slot 6:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version2.bin

Active packages on chassis 2 slot 7:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version2.bin

Active packages on chassis 3 slot 3:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version2.bin

Active packages on chassis 3 slot 6:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version2.bin

Active packages on chassis 3 slot 7:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version2.bin

Active packages on chassis 4 slot 3:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version2.bin

Active packages on chassis 4 slot 6:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version2.bin

Active packages on chassis 4 slot 7:

flash:/cmw710-boot-test.bin

flash:/cmw710-system-test.bin

flash:/soft-version2.bin

Examples of using issu commands for ISSU on an IRF 3 system

HTTP feature upgrade to a compatible version

Upgrade requirements

As shown in Figure 6, the IRF 3 system contains a two-chassis parent fabric and an S5120HI PEX.

· The PEX is connected to both the master and the subordinate member.

· The master has two MPUs (active in slot 6 and standby in slot 7) and two LPUs (in slot 8 and slot 12).

· The subordinate member has one MPU (in slot 6) and one LPU (in slot 8).

Upgrade the HTTP feature as follows:

· From a0041 to the compatible version a0042 on the parent IRF fabric.

· From d2402 to the compatible version d2403 on the PEX.

Figure 6 Network diagram

Upgrade procedure

# Download the image file that contains the d2403 HTTP feature for PEX upgrade from the TFTP server.

<Sysname> tftp 2.2.2.2 get s5120hi-http-d2403.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

# Download the image file that contains the a0042 HTTP feature for parent IRF fabric upgrade from the TFTP server.

<Sysname> tftp 2.2.2.2 get http-a0042.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

# Display active software images.

<Sysname> display install active

Active packages on chassis 1 slot 6:

flash:/boot-a0041.bin

flash:/system-a0041.bin

flash:/http-a0041.bin

Active packages on chassis 1 slot 7:

flash:/boot-a0041.bin

flash:/system-a0041.bin

flash:/http-a0041.bin

Active packages on chassis 1 slot 8:

flash:/boot-a0041.bin

flash:/system-a0041.bin

flash:/http-a0041.bin

Active packages on chassis 1 slot 12:

flash:/boot-a0041.bin

flash:/system-a0041.bin

flash:/http-a0041.bin

Active packages on chassis 2 slot 6:

flash:/boot-a0041.bin

flash:/system-a0041.bin

flash:/http-a0041.bin

Active packages on chassis 2 slot 8:

flash:/boot-a0041.bin

flash:/system-a0041.bin

flash:/http-a0041.bin

Active packages on chassis 101 slot 0:

flash:/s5120hi-boot.bin

flash:/s5120hi-system.bin

flash:/s5120hi-http-d2402.bin

# Disable automatic rollback.

<Sysname> system-view

[Sysname] issu rollback-timer 0

# Enable link-aggregation traffic redirection.

[Sysname] link-aggregation lacp traffic-redirect-notification enable

# Enable the IRF bridge MAC address to be permanent.

[Sysname] irf mac-address persistent always

# Set the physical state change suppression interval to 0 on the interfaces.

[Sysname] interface gigabitethernet1/3/0/1

[Sysname-GigabitEthernet1/3/0/1] link-delay 0 mode updown

[Sysname-GigabitEthernet1/3/0/1] quit

[Sysname] interface gigabitethernet2/3/0/1

[Sysname-GigabitEthernet2/3/0/1] link-delay 0 mode updown

[Sysname-GigabitEthernet2/3/0/1] quit

[Sysname] quit

# Specify PEX startup images.

<Sysname> issu pex PEX-S5120HI file feature flash:/s5120hi-http-d2403.bin

Verifying the file flash:/s5120hi-http-d2403.bin on chassis 1 slot 6...Done.

Copying file flash:/s5120hi-http-d2403.bin to chassis1#slot7#flash:/s5120hi-http-d2403...Done.

Copying file flash:/s5120hi-http-d2403.bin to chassis2#slot6#flash:/s5120hi-http-d2403...Done.

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

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

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

Verifying the file flash:/s5120hi-http-d2403.bin on chassis 1 slot 6...Done.

Feature image: flash:/http-a0042.bin

Version:

A0042

Version compatibility list:

A0041

A0042

Version dependency system list:

A0041

Compatible info of S5120HI:

Feature image: flash:/s5120hi-http-d2403.bin

Version:

D2403

Version compatibility list:

D2402

D2403

Version dependency system list:

D2402

Chassis Slot Upgrade Way

1 6 Service Upgrade

1 7 Service Upgrade

1 8 Service Upgrade

1 12 Service Upgrade

2 6 Service Upgrade

2 8 Service Upgrade

101 0 Service Upgrade

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

flash:/http-a0042.bin

HTTP CFA

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

flash:/http-a0042.bin

HTTP CFA

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

flash:/http-a0042.bin

HTTP

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

flash:/http-a0042.bin

HTTP

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

flash:/http-a0042.bin

HTTP CFA

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

flash:/http-a0042.bin

HTTP

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

flash:/s5120hi-http-d2403.bin

HTTP

The output shows that an incremental upgrade is recommended and the following items will be rebooted during the upgrade:

· HTTP and CFA modules on the MPUs.

· HTTP module on the LPUs.

· HTTP module on the PEX.

# Upgrade the HTTP feature on the subordinate member.

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

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

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

Verifying the file flash:/s5120hi-http-d2403.bin on chassis 1 slot 6...Done.

flash:/http-a0042.bin already exists on chassis 2 slot 6.

Overwrite it?[Y/N]:Y

Successfully copied flash:/http-a0042.bin to chassis2#slot6#flash:/http-a0042.bin.

Verifying the file flash:/http-a0042.bin on chassis 2 slot 6...Done.

flash:/http-a0042.bin already exists on chassis 2 slot 8.

Overwrite it?[Y/N]:Y

Successfully copied flash:/http-a0042.bin to chassis2#slot8#flash:/http-a0042.bin.

Verifying the file flash:/http-a0042.bin on chassis 2 slot 8...Done.

Upgrade summary according to following table:

flash:/http-a0042.bin

Running Version New Version

Alpha 0041 Alpha 0042

Chassis Slot Upgrade Way

2 6 Service Upgrade

2 8 Service Upgrade

2 12 Service Upgrade

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

# Perform a main/backup HTTP process switchover and upgrade the PEX.

<Sysname> issu run switchover

Upgrade summary according to following table:

flash:/http-a0042.bin

Running Version New Version

Alpha 0041 Alpha 0042

Chassis Slot Switchover Way

1 6 Active standby process switchover

Chassis Slot Upgrade Way

101 0 Service Upgrade

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

# Upgrade the HTTP feature on the master.

<Sysname> issu commit chassis 1

Upgrade summary according to following table:

flash:/http-a0042.bin

Running Version New Version

Alpha 0041 Alpha 0042

Chassis Slot Upgrade Way

1 6 Service Upgrade

1 7 Service Upgrade

1 8 Service Upgrade

1 12 Service Upgrade

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

# Verify that the IRF members and the PEX are all running the new HTTP images.

<Sysname>display install active

Active packages on chassis 1 slot 6:

flash:/boot-a0041.bin

flash:/system-a0041.bin

flash:/http-a0042.bin

Active packages on chassis 1 slot 7:

flash:/boot-a0041.bin

flash:/system-a0041.bin

flash:/http-a0042.bin

Active packages on chassis 1 slot 8:

flash:/boot-a0041.bin

flash:/system-a0041.bin

flash:/http-a0042.bin

Active packages on chassis 1 slot 12:

flash:/boot-a0041.bin

flash:/system-a0041.bin

flash:/http-a0042.bin

Active packages on chassis 2 slot 6:

flash:/boot-a0041.bin

flash:/system-a0041.bin

flash:/http-a0042.bin

Active packages on chassis 2 slot 8:

flash:/boot-a0041.bin

flash:/system-a0041.bin

flash:/http-a0042.bin

Active packages on chassis 2 slot 12:

flash:/boot-a0041.bin

flash:/system-a0041.bin

flash:/http-a0042.bin

Active packages on chassis 101 slot 0:

flash:/s5120hi-boot.bin

flash:/s5120hi-system.bin

flash:/s5120hi-http-d2403.bin

HTTP feature upgrade to an incompatible version

Upgrade requirements

As shown in Figure 7, the IRF 3 system contains a two-chassis parent fabric and an S5120HI PEX.

· The PEX is connected to both the master and the subordinate member.

· The master has two MPUs (active in slot 6 and standby in slot 7) and two LPUs (in slot 8 and in slot 12).

· The subordinate member has one MPU (in slot 6) and one LPU (in slot 8).

Upgrade the HTTP feature as follows:

· From a0041 to the incompatible version a0043 on the parent IRF fabric.

· From d2402 to the incompatible version d2404 on the PEX.

Figure 7 Network diagram

Upgrade procedure

# Download the image file that contains the d2404 HTTP feature for PEX upgrade from the TFTP server.

<Sysname> tftp 2.2.2.2 get s5120hi-http-d2404.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

# Download the image file that contains the a0043 HTTP feature for parent IRF fabric upgrade from the TFTP server.

<Sysname> tftp 2.2.2.2 get flash:/http-a0043.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

# Display active software images.

<Sysname> display install active

Active packages on chassis 1 slot 6:

flash:/boot-a0041.bin

flash:/system-a0041.bin

flash:/http-a0041.bin

Active packages on chassis 1 slot 7:

flash:/boot-a0041.bin

flash:/system-a0041.bin

flash:/http-a0041.bin

Active packages on chassis 1 slot 8:

flash:/boot-a0041.bin

flash:/system-a0041.bin

flash:/http-a0041.bin

Active packages on chassis 1 slot 12:

flash:/boot-a0041.bin

flash:/system-a0041.bin

flash:/http-a0041.bin

Active packages on chassis 2 slot 6:

flash:/boot-a0041.bin

flash:/system-a0041.bin

flash:/http-a0041.bin

Active packages on chassis 2 slot 8:

flash:/boot-a0041.bin

flash:/system-a0041.bin

flash:/http-a0041.bin

flash:/s5120hi-http-d2402.bin

Active packages on chassis 101 slot 0:

flash:/s5120hi-boot.bin

flash:/s5120hi-system.bin

flash:/s5120hi-http-d2402.bin

# Enable link-aggregation traffic redirection.

<Sysname> system-view

[Sysname] link-aggregation lacp traffic-redirect-notification enable

# Enable the IRF bridge MAC address to be permanent.

[Sysname] irf mac-address persistent always

# Set the physical state change suppression interval to 0 on the interfaces.

[Sysname] interface gigabitethernet1/3/0/1

[Sysname-GigabitEthernet1/3/0/1] link-delay 0 mode updown

[Sysname-GigabitEthernet1/3/0/1] quit

[Sysname] interface gigabitethernet2/3/0/1

[Sysname-GigabitEthernet2/3/0/1] link-delay 0 mode updown

[Sysname-GigabitEthernet2/3/0/1] quit

[Sysname] quit

# Specify PEX startup images.

<Sysname> issu pex PEX-S5120HI file feature flash:/s5120hi-http-d2404.bin

Verifying the file flash:/s5120hi-http-d2404.bin on chassis 1 slot 6...Done.

Copying file flash:/s5120hi-http-d2404.bin to chassis1#slot7#flash:/s5120hi-http-d2404.bin...Done.

Copying file flash:/s5120hi-http-d2404.bin to chassis2#slot6#flash:/s5120hi-http-d2404.bin...Done.

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

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

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

Verifying the file flash:/s5120hi-http-d2404.bin on chassis 1 slot 6...Done.

Feature image:flash:/http-a0043.bin

Version:

A0043

Version compatibility list:

A0043

Version dependency system list:

A0041

Compatible info of S5120HI:

Feature image: flash:/s5120hi-http-d2404.bin

Version:

D2404

Version compatibility list:

D2404

Version dependency system list:

D2402

Incompatible upgrade.

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

# Upgrade the HTTP feature on the subordinate member.

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

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

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

Verifying the file flash:/s5120hi-http-d2404.bin on chassis 1 slot 6...Done.

Copying file flash:/http-a0043.bin to chassis2#slot6#flash:/http-a0043.bin...Done.

Verifying the file flash:/http-a0043.bin on chassis 2 slot 6...Done.

Upgrade summary according to following table:

flash:/http-a0043.bin

Running Version New Version

Alpha 0041 Alpha 0043

Chassis Slot Upgrade Way

2 6 Reboot

2 8 Reboot

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

After the upgrade, the upgraded subordinate member leaves the current IRF fabric and forms a new IRF fabric.

# Perform an ISSU switchover on the current IRF fabric and upgrade the PEX.

<Sysname> issu run switchover

Copying file flash:/http-a0043.bin to chassis1#slot7#flash:/http-a0043.bin...Done.

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

Upgrade summary according to following table:

flash:/http-a0043.bin

Running Version New Version

Alpha 0041 Alpha 0043

Chassis Slot Upgrade Way

1 6 Reboot

1 7 Reboot

1 8 Reboot

1 12 Reboot

101 0 Reboot

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

After the upgrade, the original master joins the new IRF fabric.

# Verify that the IRF members and the PEX are all running the new HTTP images.

<Sysname> display install active

Active packages on chassis 1 slot 6:

flash:/boot-a0041.bin

flash:/system-a0041.bin

flash:/http-a0043.bin

Active packages on chassis 1 slot 7:

flash:/boot-a0041.bin

flash:/system-a0041.bin

flash:/http-a0043.bin

Active packages on chassis 1 slot 8:

flash:/boot-a0041.bin

flash:/system-a0041.bin

flash:/http-a0043.bin

Active packages on chassis 1 slot 12:

flash:/boot-a0041.bin

flash:/system-a0041.bin

flash:/http-a0043.bin

Active packages on chassis 2 slot 6:

flash:/boot-a0041.bin

flash:/system-a0041.bin

flash:/http-a0043.bin

Active packages on chassis 2 slot 8:

flash:/boot-a0041.bin

flash:/system-a0041.bin

flash:/http-a0043.bin

Active packages on chassis 101 slot 0:

flash:/s5120hi-boot.bin

flash:/s5120hi-system.bin

flash:/s5120hi-http-d2404.bin

Examples of using install commands for ISSU on a standalone device

HTTP feature upgrade example

Upgrade requirements

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

Upgrade the HTTP feature from R0201 to R0202. The two versions are compatible.

Figure 8 Network diagram

Upgrade procedure

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

<Sysname> tftp 2.2.2.2 get http-r0202.ipe

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

Dload Upload Total Spent Left Speed

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

Writing file...Done.

# Decompress the .ipe file.

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

Verifying the file flash:/http-r0202.ipe on slot 6...Done.

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

# Display active software images.

<Sysname> display install active

Active packages on slot 6:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on slot 7:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

# Identify the version compatibility, recommended ISSU methods, and possible impact of the upgrade.

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

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

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

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Slot Upgrade Way

7 Service Upgrade

Influenced service according to following table on slot 7:

flash:/http-r0202.bin

HTTP CFA

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

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

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Slot Upgrade Way

6 Service Upgrade

7 Service Upgrade

Influenced service according to following table on slot 6:

flash:/http-r0202.bin

HTTP CFA

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

# Activate the new HTTP image to upgrade the HTTP feature.

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

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

Overwrite it?[Y/N]:y

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

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

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Slot Upgrade Way

7 Service Upgrade

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

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

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

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

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Slot Upgrade Way

6 Service Upgrade

7 Service Upgrade

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

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

# Verify that the new HTTP image has been activated.

<Sysname> display install active

Active packages on slot 6:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on slot 7:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

# Commit the software changes.

<Sysname> install commit

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

Examples of using install commands for ISSU on an IRF fabric

HTTP feature upgrade example

Upgrade requirements

As shown in Figure 9, the IRF fabric has two members. Each member has one MPU in slot 6 (active MPU) and one MPU in slot 7 (standby MPU).

Upgrade the HTTP feature from R0201 to R0202. The two versions are compatible.

Figure 9 Network diagram

Upgrade procedure

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

<Sysname> tftp 2.2.2.2 get http-r0202.ipe

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

Dload Upload Total Spent Left Speed

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

# Decompress the .ipe file.

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

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

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

# Display active software images.

<Sysname> display install active

Active packages on chassis 1 slot 6:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 1 slot 7:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 2 slot 6:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

Active packages on chassis 2 slot 7:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0201.bin

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

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

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

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

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Chassis Slot Upgrade Way

2 6 Service Upgrade

2 7 Service Upgrade

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

flash:/http-r0202.bin

HTTP CFA

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

flash:/http-r0202.bin

HTTP CFA

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

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

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

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Chassis Slot Upgrade Way

2 6 Service Upgrade

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

flash:/http-r0202.bin

HTTP CFA

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

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

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

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Chassis Slot Upgrade Way

1 6 Service Upgrade

1 7 Service Upgrade

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

flash:/http-r0202.bin

HTTP CFA

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

flash:/http-r0202.bin

HTTP CFA

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

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

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Chassis Slot Upgrade Way

1 6 Service Upgrade

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

flash:/http-r0202.bin

HTTP CFA

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

# Activate the new HTTP image to upgrade the HTTP feature.

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

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

Overwrite it?[Y/N]:y

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

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

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Chassis Slot Upgrade Way

2 6 Service Upgrade

2 7 Service Upgrade

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

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

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

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

Overwrite it?[Y/N]:y

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

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

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Chassis Slot Upgrade Way

2 6 Service Upgrade

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

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

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

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

Overwrite it?[Y/N]:y

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

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

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Chassis Slot Upgrade Way

1 6 Service Upgrade

1 7 Service Upgrade

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

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

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

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

Upgrade summary according to following table:

flash:/http-r0202.bin

Running Version New Version

Alpha 0201 Alpha 0202

Chassis Slot Upgrade Way

1 6 Service Upgrade

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

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

# Verify that the new HTTP image has been activated.

<Sysname> display install active

Active packages on chassis 1 slot 6:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on chassis 1 slot 7:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on chassis 2 slot 6:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

Active packages on chassis 2 slot 7:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/http-r0202.bin

# Commit the software changes.

<Sysname> install commit

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

Examples of using install commands for ISSU on an IRF 3 system

HTTP feature upgrade example

Upgrade requirements

As shown in Figure 10, the IRF 3 system contains a two-chassis parent fabric and an S5120HI PEX.

· The PEX is connected to both the master and the subordinate member.

· The master has two MPUs (active in slot 6 and standby in slot 7) and two LPUs (in slot 8 and slot 12).

· The subordinate member has one MPU (in slot 6) and one LPU (in slot 8).

Upgrade the HTTP feature as follows:

· From a0041 to the compatible version a0042 on the parent IRF fabric.

· From d2402 to the compatible version d2403 on the PEX.

Figure 10 Network diagram

Upgrade procedure

# Download the image file that contains the d2403 HTTP feature for PEX upgrade from the TFTP server.

<Sysname> tftp 2.2.2.2 get s5120hi-http-d2403.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

# Download the image file that contains the a0042 HTTP feature for parent IRF fabric upgrade from the TFTP server.

<Sysname> tftp 2.2.2.2 get http-a0042.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

# Display active software images.

<Sysname> display install active

Active packages on chassis 1 slot 6:

flash:/boot-a0041.bin

flash:/system-a0041.bin

flash:/http-a0041.bin

Active packages on chassis 1 slot 7:

flash:/boot-a0041.bin

flash:/system-a0041.bin

flash:/http-a0041.bin

Active packages on chassis 1 slot 8:

flash:/boot-a0041.bin

flash:/system-a0041.bin

flash:/http-a0041.bin

Active packages on chassis 1 slot 12:

flash:/boot-a0041.bin

flash:/system-a0041.bin

flash:/http-a0041.bin

Active packages on chassis 2 slot 6:

flash:/boot-a0041.bin

flash:/system-a0041.bin

flash:/http-a0041.bin

Active packages on chassis 2 slot 8:

flash:/boot-a0041.bin

flash:/system-a0041.bin

flash:/http-a0041.bin

Active packages on chassis 101 slot 0:

flash:/s5120hi-boot.bin

flash:/s5120hi-system.bin

flash:/s5120hi-http-d2402.bin

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

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

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

Upgrade summary according to following table:

flash:/http-a0042.bin

Running Version New Version

Alpha 0041 Alpha 0042

Chassis Slot Upgrade Way

1 6 Service Upgrade

1 8 Service Upgrade

1 12 Service Upgrade

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

flash:/http-a0042.bin

HTTP CFA

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

flash:/http-a0042.bin

HTTP

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

flash:/http-a0042.bin

HTTP

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

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

Upgrade summary according to following table:

flash:/http-a0042.bin

Running Version New Version

Alpha 0041 Alpha 0042

Chassis Slot Upgrade Way

1 7 Service Upgrade

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

flash:/http-a0042.bin

HTTP CFA

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

Verifying the file flash:/http-a0042.bin on chassis 2 slot 6...Done.

Upgrade summary according to following table:

flash:/http-a0042.bin

Running Version New Version

Alpha 0041 Alpha 0042

Chassis Slot Upgrade Way

2 6 Service Upgrade

2 8 Service Upgrade

2 12 Service Upgrade

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

flash:/http-a0042.bin

HTTP CFA

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

flash:/http-a0042.bin

HTTP

<Sysname> install activate feature flash:/s5120hi-http-d2403.bin chassis 101 slot 0 test

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

Upgrade summary according to following table:

flash:/s5120hi-http-d2403.bin

Running Version New Version

Demo 2402 Demo 2403

Chassis Slot Upgrade Way

101 0 Service Upgrade

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

flash:/s5120hi-http-d2403.bin

HTTP

The output shows that an incremental upgrade is recommended and the following items will be rebooted during the upgrade:

· HTTP and CFA modules on the MPUs.

· HTTP module on the LPU.

· HTTP module on the PEX.

# Activate the new HTTP image to upgrade the HTTP feature on the MPU in slot 7 of chassis 1.

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

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

Overwrite it?[Y/N]:Y

Successfully copied flash:/http-a0042.bin to chassis1#slot7#flash:/http-a0042.bin.

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

Upgrade summary according to following table:

flash:/http-a0042.bin

Running Version New Version

Alpha 0041 Alpha 0042

Chassis Slot Upgrade Way

1 7 Service Upgrade

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

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

# Activate the new HTTP image to upgrade the HTTP feature on the MPU in slot 6 of chassis 1 and the LPUs in chassis 1.

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

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

Overwrite it?[Y/N]:Y

Successfully copied flash:/http-a0042.bin to chassis1#slot6#flash:/http-a0042.bin.

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

Upgrade summary according to following table:

flash:/http-a0042.bin

Running Version New Version

Alpha 0041 Alpha 0042

Chassis Slot Upgrade Way

1 6 Service Upgrade

1 8 Service Upgrade

1 12 Service Upgrade

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

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

# Activate the new HTTP image to upgrade the HTTP feature on the cards in chassis 2.

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

flash:/http-a0042.bin already exists on chassis 2 slot 6.

Overwrite it?[Y/N]:Y

Successfully copied flash:/http-a0042.bin to chassis2#slot6# flash:/http-a0042.bin.

Verifying the file flash:/http-a0042.bin on chassis 2 slot 6...Done.

Upgrade summary according to following table:

flash:/http-a0042.bin

Running Version New Version

Alpha 0041 Alpha 0042

Chassis Slot Upgrade Way

2 6 Service Upgrade

2 8 Service Upgrade

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

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

# Display active software images.

<Sysname> display install active

Active packages on chassis 1 slot 6:

flash:/boot-a0041.bin

flash:/system-a0041.bin

flash:/http-a0042.bin

Active packages on chassis 1 slot 7:

flash:/boot-a0041.bin

flash:/system-a0041.bin

flash:/http-a0042.bin

Active packages on chassis 1 slot 8:

flash:/boot-a0041.bin

flash:/system-a0041.bin

flash:/http-a0042.bin

Active packages on chassis 1 slot 12:

flash:/boot-a0041.bin

flash:/system-a0041.bin

flash:/http-a0042.bin

Active packages on chassis 2 slot 6:

flash:/boot-a0041.bin

flash:/system-a0041.bin

flash:/http-a0042.bin

Active packages on chassis 2 slot 8:

flash:/boot-a0041.bin

flash:/system-a0041.bin

flash:/http-a0042.bin

Active packages on chassis 101 slot 0:

flash:/s5120hi-boot.bin

flash:/s5120hi-system.bin

flash:/s5120hi-http-d2402.bin

# Activate the new HTTP image to upgrade the HTTP feature on the PEX.

<Sysname> install activate feature flash:/s5120hi-http-d2403.bin chassis 101 slot 0

flash:/s5120hi-http-d2403.bin already exists on chassis 101 slot 0.

Overwrite it?[Y/N]:Y

Successfully copied s5120hi-http-d2403.bin to chassis101#slot0#flash:/s5120hi-http-d2403.bin.

Verifying the file flash:/s5120hi-http-d2403.bin on chassis 1 slot 6...Done.

Upgrade summary according to following table:

flash:/s5120hi-http-d2403.bin

Running Version New Version

Demo 2402 Demo 2403

Chassis Slot Upgrade Way

101 0 Service Upgrade

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

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

# Display active software images.

<Sysname> display install active

Active packages on chassis 1 slot 6:

flash:/boot-a0041.bin

flash:/system-a0041.bin

flash:/http-a0042.bin

Active packages on chassis 1 slot 7:

flash:/boot-a0041.bin

flash:/system-a0041.bin

flash:/http-a0042.bin

Active packages on chassis 1 slot 8:

flash:/boot-a0041.bin

flash:/system-a0041.bin

flash:/http-a0042.bin

Active packages on chassis 1 slot 12:

flash:/boot-a0041.bin

flash:/system-a0041.bin

flash:/http-a0042.bin

Active packages on chassis 2 slot 6:

flash:/boot-a0041.bin

flash:/system-a0041.bin

flash:/http-a0041.bin

Active packages on chassis 2 slot 8:

flash:/boot-a0041.bin

flash:/system-a0041.bin

flash:/http-a0041.bin

Active packages on chassis 101 slot 0:

flash:/s5120hi-boot.bin

flash:/s5120hi-system.bin

flash:/s5120hi-http-d2403.bin

01-Fundamentals Configuration Guide

ISSU commands

Decompressing an .ipe file

Symptom

Solution

Upgrade requirements

Upgrade procedure

Upgrade requirements

Upgrade procedure

Upgrade requirements

Upgrade procedure

Upgrade requirements

Upgrade procedure

Upgrade requirements

Upgrade procedure

Upgrade requirements

Upgrade procedure

Upgrade requirements

Upgrade procedure

Examples of using install commands for ISSU on a standalone device

Upgrade requirements

Upgrade procedure

Examples of using install commands for ISSU on an IRF fabric

Upgrade requirements

Upgrade procedure

Examples of using install commands for ISSU on an IRF 3 system

Upgrade requirements

Upgrade procedure

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program

Global Learning

Partner Sales Resources

Service Business

News & Events

Contact Us