· 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—Some hardware can be upgraded while the other peer hardware is providing services.

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

ISSU methods

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

The device supports the ISSU methods in Table 1.

Table 1 ISSU methods

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 is not available. As a best practice, schedule the downtime carefully to minimize the upgrade impact on the services. The Reboot method reboots both the control and data planes to complete the software upgrade. (In standalone mode.) The Reboot method reboots member devices to complete the software upgrade. While one member device is rebooting, the other member devices can provide services. (In IRF mode.)

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 is not available. As a best practice, schedule the downtime carefully to minimize the upgrade impact on the services.

The Reboot method reboots both the control and data planes to complete the software upgrade. (In standalone mode.)

The Reboot method reboots member devices to complete the software upgrade. While one member device is rebooting, the other member devices can provide services. (In IRF mode.)

ISSU commands

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

Table 2 Command set comparison

Item	issu commands	install commands
Upgrade types	· Compatible. · Incompatible.	Compatible.
Patch install/uninstall	Not supported.	Supported.
Upgrade mode	Chassis by chassis.	Card by card.
Applicable scenarios and image types	Boot and system images, for dual-member IRF fabrics	Feature and patch images, in standalone or IRF mode.
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 availability of ISSU

1. 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 image file.

2. If the upgrade software image file requires a license but the license is not installed or valid, install the license first.

When you install a license, the system searches the file system for a matching software image file. If it finds a matching software image file, it stops searching and installs the images in the file.

When you uninstall a license, the system checks whether the software images are running. If the images are running, the system uninstalls the images automatically.

Verifying the device operating status

Verify the following items:

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

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

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

Preparing the upgrade images

1. Use the dir command to verify that sufficient storage space is available 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 file system on the device.

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. Verify that the running software version is in the list.

3. Check the Upgrade Way field to identify the recommended ISSU method. For more information about ISSU methods, see Table 1.

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	· Use the link-delay command to set the link-down event suppression interval to 0 seconds so the interfaces report physical state changes to the CPU immediately. · Enable link-aggregation traffic redirection to ensure traffic continuity on aggregate links. · Configure the irf mac-address persistent timer or irf mac-address persistent always command.

Determining the upgrade procedure

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

2. Identify the hardware redundancy condition.

ISSU can maintain service continuity only when the IRF fabric has multiple members.

IMPORTANT:

If hardware redundancy is not available, service discontinuity is not avoidable. Make sure you understand the impact of the upgrade on the network.

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.

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

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

¡ install commands—install activate and install deactivate.

If the System State field displays Stable, the system is stable.

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

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

Adjusting and saving the running configuration

1. Remove the configured commands that the new software version does not support.

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

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.

Performing an ISSU by using issu commands

On a multichassis IRF fabric, always start ISSU with a subordinate member.

Step	Command	Remarks
1. Enter system view.	system-view	N/A
1. Disable automatic rollback.	issu rollback-timer 0	Automatic rollback is complicated. As a best practice, disable automatic rollback.
2. Return to user view.	quit	N/A
3. Verify that the system is stable.	display system stable state	The system is stable if the System State field displays Stable. For a successful ISSU, you must make sure the system is stable before you proceed to the next step.
4. Load the upgrade images as main startup software images on subordinate members.	· Use .bin files: issu load file { boot filename \| system filename \| feature filename&<1-30> } * chassis chassis-number [ reboot ] · Use an .ipe file: issu load file ipe ipe-filename chassis chassis-number&<1-3> [ reboot ]	Specify the member ID of a subordinate member for the chassis-number argument. Every time you use this command, first execute the display system stable state command to verify system stability.
5. Verify that the system is stable.	display system stable state	The system is stable if the System State field displays Stable. For a successful ISSU, you must make sure the system is stable before you proceed to the next step.
6. Perform an ISSU switchover.	issu run switchover	N/A
7. (Optional.) Accept the upgrade.	issu accept	N/A
8. Verify that the system is stable.	display system stable state	The system is stable if the System State field displays Stable. For a successful ISSU, you must make sure the system is stable before you proceed to the next step.
9. Upgrade the remaining members to complete the ISSU.	issu commit chassis chassis-number	Repeat the previous step and this step 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.
10. Verify that the ISSU is finished.	display issu state	If the ISSU state field displays Init, the ISSU is finished.

Performing an ISSU by using install commands

ISSU 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 except for patches ¡ 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 filesystem

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.

When you install an image, you must begin with the master device. When you upgrade an image, you must begin with a subordinate device. (In IRF mode.)

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

Installing or upgrading images except for patches

Perform this task in user view.

Step	Command	Remarks
1. Verify that the system is stable.	display system stable state	The system is stable if the System State field displays Stable. For a successful ISSU, you must make sure the system is stable before you proceed to the next step.
2. (Optional.) Identify the recommended ISSU method and the possible impact of the upgrade.	· In standalone mode: install activate { boot filename \| system filename \| feature filename&<1-30> } * slot slot-number test · In IRF mode: install activate { boot filename \| system filename \| feature filename&<1-30> } * chassis chassis-number slot slot-number test	N/A
3. Activate images.	· In standalone mode: install activate { boot filename \| system filename \| feature filename&<1-30> } * slot slot-number · In IRF mode: install activate { boot filename \| system filename \| feature filename&<1-30> } * chassis chassis-number slot slot-number	N/A

Installing patch images

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.

Step	Command	Remarks
1. Verify that the system is stable.	display system stable state	The system is stable if the System State field displays Stable. For a successful installation, you must make sure the system is stable before you proceed to the next step.
2. Activate patch images.	· In standalone mode: install activate patch filename { all \| slot slot-number } · In IRF mode: install activate patch filename { all \| chassis chassis-number slot slot-number }	N/A

Step

Command

Remarks

1. Verify that the system is stable.

display system stable state

The system is stable if the System State field displays Stable.

For a successful installation, you must make sure the system is stable before you proceed to the next step.

2. Activate patch images.

· In standalone mode:
install activate patch filename { all | slot slot-number }

· In IRF mode:
install activate patch filename { all | chassis chassis-number slot slot-number }

N/A

Uninstalling feature or patch images

You can uninstall only feature and 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 delete the images, execute the install remove command. For more information, see "Deleting inactive software images."

Uninstalling feature images

Perform this task in user view.

Step	Command	Remarks
1. Verify that the system is stable.	display system stable state	The system is stable if the System State field displays Stable. For a successful uninstallation, you must make sure the system is stable before you proceed to the next step.
2. Deactivate feature images.	· In standalone mode: install deactivate feature filename&<1-30> slot slot-number · In IRF mode: install deactivate feature filename&<1-30> chassis chassis-number slot slot-number	N/A

Step

Command

Remarks

1. Verify that the system is stable.

display system stable state

The system is stable if the System State field displays Stable.

For a successful uninstallation, you must make sure the system is stable before you proceed to the next step.

2. Deactivate feature images.

· In standalone mode:
install deactivate feature filename&<1-30> slot slot-number

· In IRF mode:
install deactivate feature filename&<1-30> chassis chassis-number slot slot-number

N/A

Uninstalling patch images

Perform this task in user view.

Step	Command	Remarks
1. Verify that the system is stable.	display system stable state	The system is stable if the System State field displays Stable. For a successful uninstallation, you must make sure the system is stable before you proceed to the next step.
2. Deactivate patch images.	· In standalone mode: install deactivate patch filename { all \| slot slot-number } · In IRF mode: install deactivate patch filename { all \| chassis chassis-number slot slot-number }	N/A

Step

Command

Remarks

1. Verify that the system is stable.

display system stable state

The system is stable if the System State field displays Stable.

For a successful uninstallation, you must make sure the system is stable before you proceed to the next step.

2. Deactivate patch images.

· In standalone mode:
install deactivate patch filename { all | slot slot-number }

· In IRF mode:
install deactivate patch filename { all | chassis chassis-number slot slot-number }

N/A

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

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

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
Verify software images.	install verify

Deleting inactive software images

This task delete image files permanently. You cannot use the install abort command to abort the operation.

Perform this task in user view.

Task	Command
Delete an inactive software image file.	· In standalone mode: install remove [ slot slot-number ] { filename \| inactive } · In IRF mode: install remove [ chassis chassis-number slot slot-number ] { filename \| inactive }

Task

Command

Delete an inactive software image file.

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

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

Displaying and maintaining ISSU

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

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

Task	Command
Display active software images. (In standalone mode.)	display install active [ slot slot-number ] [ verbose ]
Display active software images. (In IRF mode.)	display install active [ chassis chassis-number slot slot-number ] [ verbose ]
Display backup startup software images. (In standalone mode.)	display install backup [ slot slot-number ] [ verbose ]
Display backup startup software images. (In IRF mode.)	display install backup [ chassis chassis-number slot slot-number ] [ verbose ]
Display main startup software images. (In standalone mode.)	display install committed [ slot slot-number ] [ verbose ]
Display main startup software images. (In IRF mode.)	display install committed [ chassis chassis-number slot slot-number ] [ verbose ]
Display inactive software images. (In standalone mode.)	display install inactive [ slot slot-number ] [ verbose ]
Display inactive software images. (In IRF mode.)	display install inactive [ chassis chassis-number slot slot-number ] [ verbose ]
Display the software images included in an .ipe file.	display install ipe-info ipe-filename
Display ongoing ISSU activate 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. (In standalone mode.)	display install which { component name \| file filename } [ slot slot-number ]
Display all software image files that include a specific component or file. (In IRF mode.)	display install which { component name \| file filename } [ chassis chassis-number slot slot-number ]
Display automatic rollback timer information.	display issu rollback-timer
Display ISSU status information. (This command applies only to an ISSU that uses the issu series commands.)	display issu state
Display version compatibility information and identify the upgrade method.	display version comp-matrix
Clear ISSU log entries.	reset install log-history oldest log-number

Examples of using issu commands for ISSU

Upgrade requirements

As shown in Figure 1, the IRF fabric has two members.

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

Figure 1 Network diagram

Upgrade procedure

1. Prepare for the upgrade:

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

<Sysname> tftp 2.2.2.2 get feature1-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 0:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/feature1-r0201.bin

Active packages on chassis 2 slot 0:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/feature1-r0201.bin

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

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

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

Feature image: flash:/feature1-r0202.bin

Version:

7.1.064-ESS 7606

Version Compatibility List:

7.1.064-ESS 7606

Version Dependency System List:

7.1.064-ESS 7606

Chassis Slot Upgrade Way

1 0 Service Upgrade

2 0 Service Upgrade

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

flash:/feature1-r0202.bin

feature1 cfad

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

flash:/feature1-r0202.bin

feature1 cfad

The output shows that service upgrade is recommended. The related modules will be rebooted during the upgrade.

2. Upgrade the feature1 feature:

# 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 link-down event suppression interval to 0 seconds on the Ethernet interfaces.

[Sysname] interface gigabitethernet1/1/1/1

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

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

[Sysname] interface gigabitethernet2/1/1/1

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

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

[Sysname] quit

# Upgrade the feature1 feature on the subordinate member.

<Sysname> issu load file feature flash:/feature1-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:/feature1-r0202.bin on chassis 1 slot 0...Done.

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

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

Upgrade summary according to following table:

flash:/feature1-r0202.bin

Running Version New Version

None Ess 7606

Chassis Slot Upgrade Way

2 0 Service Upgrade

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

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

# Perform a main/backup feature1 process switchover.

<Sysname> issu run switchover

Upgrade summary according to following table:

flash:/feature1-r0202.bin

Running Version New Version

None Ess 7606

Chassis Slot Switchover Way

1 0 Active standby process switchover

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

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

# Upgrade the feature on the original master.

<Sysname> issu commit chassis 1

Upgrade summary according to following table:

flash:/feature1-r0202.bin

Running Version New Version

None Ess 7606

Chassis Slot Upgrade Way

1 0 Service Upgrade

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

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

Verifying the configuration

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

<Sysname> display install active

Active packages on chassis 1 slot 0:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/feature1-r0202.bin

Active packages on chassis 2 slot 0:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/feature1-r0202.bin

Examples of using install commands for ISSU (in standalone mode)

Upgrade requirements

As shown in Figure 2, the device has two MPUs and one LPU.

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

Figure 2 Network diagram

Upgrade procedure

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

<Sysname> tftp 2.2.2.2 get feature1-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:/feature1-r0202.ipe flash:/

Verifying the file flash:/feature1-r0202.ipe on slot 0...Done.

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

# Display active software images.

<Sysname> display install active

Active packages on slot 0:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/feature1-r0201.bin

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

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

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

Upgrade summary according to following table:

flash:/feature1-r0202.bin

Running Version New Version

None Ess 7606

Slot Upgrade Way

0 Service Upgrade

Influenced service according to following table on slot 0:

flash:/feature1-r0202.bin

feature1 cfad

The output shows that the recommended ISSU method is service upgrade. The related modules will be rebooted during the upgrade.

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

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

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

Upgrade summary according to following table:

flash:/feature1-r0202.bin

Running Version New Version

None Ess 7606

Slot Upgrade Way

0 Service Upgrade

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

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

# Verify that the new feature1 image has been activated.

<Sysname> display install active

Active packages on slot 0:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/feature1-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 (in IRF mode)

Upgrade requirements

As shown in Figure 3, the IRF fabric has two members.

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

Figure 3 Network diagram

Upgrade procedure

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

<Sysname> tftp 2.2.2.2 get feature1-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:/feature1-r0202.ipe flash:

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

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

# Display active software images.

<Sysname> display install active

Active packages on chassis 1 slot 0:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/feature1-r0201.bin

Active packages on chassis 2 slot 0:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/feature1-r0201.bin

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

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

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

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

Upgrade summary according to following table:

flash:/feature1-r0202.bin

Running Version New Version

None Ess 7606

Chassis Slot Upgrade Way

2 0 Service Upgrade

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

flash:/feature1-r0202.bin

feature1 cfad

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

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

Upgrade summary according to following table:

flash:/feature1-r0202.bin

Running Version New Version

None Ess 7606

Chassis Slot Upgrade Way

1 0 Service Upgrade

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

flash:/feature1-r0202.bin

feature1 cfad

The output shows that the recommended ISSU method is service upgrade. The related modules will be rebooted during the upgrade.

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

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

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

Overwrite it?[Y/N]:y

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

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

Upgrade summary according to following table:

flash:/feature1-r0202.bin

Running Version New Version

None Ess 7606

Chassis Slot Upgrade Way

2 0 Service Upgrade

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

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

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

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

Upgrade summary according to following table:

flash:/feature1-r0202.bin

Running Version New Version

None Ess 7606

Chassis Slot Upgrade Way

1 0 Service Upgrade

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

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

# Verify that the new feature1 image has been activated.

<Sysname> display install active

Active packages on chassis 1 slot 0:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/feature1-r0202.bin

Active packages on chassis 2 slot 0:

flash:/boot-r0201.bin

flash:/system-r0201.bin

flash:/feature1-r0202.bin

# Commit the software changes.

<Sysname> install commit

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

01-Fundamentals Configuration Guide

ISSU commands

Decompressing an .ipe file

Examples of using issu commands for ISSU

Upgrade procedure

Verifying the configuration

Examples of using install commands for ISSU (in standalone mode)

Upgrade requirements

Upgrade procedure

Examples of using install commands for ISSU (in IRF mode)

Upgrade requirements

Upgrade procedure

Cloud & AI

InterConnect

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Resources

Partner Business Management

Company Information

News & Events

Contact Us