Software upgrade enables you to upgrade a software version, add new features, and fix software bugs. This chapter describes software types and release forms, compares software upgrade methods, and provides the procedures for upgrading software from the CLI.

Software types

The following software types are available:

· BootWare image—Also called the Boot ROM image. This image contains a basic segment and an extended segment.

¡ The basic segment is the minimum code that bootstraps the system.

¡ The extended segment enables hardware initialization and provides system management menus. When the device cannot start up correctly, you can use the menus to load software and the startup configuration file or manage files.

Typically, the BootWare image is integrated into the Boot image to avoid software compatibility errors.

· Comware image—Includes the following image subcategories:

¡ Boot image—A .bin file that contains the Linux operating system kernel. It provides process management, memory management, file system management, and the emergency shell.

¡ System image—A .bin file that contains the Comware kernel and standard features, including device management, interface management, configuration management, and routing.

¡ Feature image—A .bin file that contains advanced or customized software features. You can purchase feature images as needed.

¡ Patch image—A .bin file that is released for fixing bugs without rebooting the device. A patch image does not add or remove features.

Patch images have the following types:

- Incremental patch images—A new incremental patch image can cover all, part, or none of the functions provided by an old incremental patch image. A new incremental patch image can coexist with an old incremental patch image on the device only when the former covers none of the functions provided by the latter.

- Non-incremental patch images—A new non-incremental patch image covers all functions provided by an old non-incremental patch image. Each of the boot, system, and feature images can have one non-incremental patch image, and these patch images can coexist on the device. The device uninstalls the old non-incremental patch image before installing a new non-incremental patch image.

An incremental patch image and a non-incremental patch image can coexist on the device.

Comware images that have been loaded are called current software images. Comware images specified to load at the next startup are called startup software images.

BootWare image, boot image, and system image are required for the device to operate.

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

Software release forms

Software images are released in one of the following forms:

· Separate .bin files. You must verify compatibility between software images.

· As a whole in one .ipe package file. The images in an .ipe package file are compatible. The system decompresses the file automatically, loads the .bin images and sets them as startup software images.

NOTE:

Software image file names use the model-comware version-image type-release format. This document uses boot.bin and system.bin as boot and system image file names.

Upgrade methods

Upgrade method	Software types	Remarks
Upgrading from the CLI by using the boot loader method	· BootWare image · Comware images (excluding patches)	This method is disruptive. You must reboot the entire device to complete the upgrade.
Performing an upgrade by using install commands	Comware images	This method installs new features or patches or upgrades the boot, system, or feature images.
Upgrading from the BootWare menu	· BootWare image · Comware images	Use this method when the device device, PEX, or security engine cannot start up correctly. To use this method, first connect to the console port and power cycle the device, PEX, or security engine. Then, press Ctrl+B at prompt to access the BootWare menu. For more information about upgrading software from the BootWare menu, see the release notes for the software version. IMPORTANT: Use this method only when you do not have any other choice.

This chapter covers only upgrading software from the CLI by using the boot loader method.

Software image loading

Startup software images

To upgrade software, you must specify the upgrade files as the startup software images for the device to load at next startup. You can specify two lists of software images: one main and one backup. The device first loads the main startup software images. If the main startup software images are not available, the devices loads the backup startup software images.

Image loading process at startup

At startup, the device performs the following operations after loading and initializing BootWare:

1. Loads main images.

2. If any main image does not exist or is invalid, loads the backup images.

3. If any backup image does not exist or is invalid, checks the main or backup boot image.

4. If the main or backup boot image exist and is valid, enters the emergency shell.

5. If both the main and backup boot images do not exist or are invalid, the device cannot start up.

Handling the emergency shell process or image loading failure

After the device enters the emergency shell, connect to the console port and load a system image so you can access the Comware system. For more information about using the emergency shell, see "Using the emergency shell."

If the device fails to load the images, connect to the console port, power cycle the device, and use the BootWare menu to load new startup images.

Restrictions and guidelines: Software upgrade

As a best practice, store the startup images in a fixed storage medium. If you store the startup images in a hot swappable storage medium, do not remove the hot swappable storage medium during the startup process.

Upgrading device software by using the boot loader method

Restrictions and guidelines

When you upgrade software, you do not need to upgrade interface cards separately. The software images for interface cards are integrated in the software images for MPUs. The interface cards are upgraded automatically when you upgrade MPUs.

Software upgrade tasks at a glance

To upgrade software, perform one of the following tasks:

· Upgrading the device

· Synchronizing startup images from the active MPU to standby MPUs

Upgrading the device

1. (Optional.) Preloading the BootWare image to BootWare.

¡ Preloading the BootWare image to BootWare (in standalone mode)

¡ Preloading the BootWare image to BootWare (in IRF mode)

If a BootWare upgrade is required, you can perform this task to shorten the subsequent upgrade time. This task helps reduce upgrade problems caused by unexpected power failure. If you skip this task, the device upgrades the BootWare automatically when it upgrades the startup software images.

2. Specifying startup images and completing the upgrade

Synchronizing startup images from the active MPU to standby MPUs

· Enabling automatic software synchronization from the active MPU to the standby MPU

This feature enables a newly added MPU to synchronize the software images running on the active MPU. By default, this feature is enabled.

In IRF mode, use the irf auto-update enable command to synchronize software from the global active MPU to the standby MPUs.

· Synchronizing startup images from the active MPU to the standby MPU (in standalone mode)

Perform this task when the startup images on the standby MPU are not the same version as those on the active MPU.

· Synchronizing startup images from the global active MPU to global standby MPUs (in IRF mode)

Perform this task when the startup images on a global standby MPU are not the same version as those on the global active MPU.

Prerequisites

1. Use the display version command to verify the current BootWare image version and startup software version.

2. Use the release notes for the upgrade software version to evaluate the upgrade impact on your network and verify the following items:

¡ Software and hardware compatibility.

¡ Version and size of the upgrade software.

¡ Compatibility of the upgrade software with the current BootWare image and startup software image.

3. Use the release notes to verify whether the software images require a license. If licenses are required, register and activate licenses for each license-based software image. For more information about licensing, see "Managing licenses."

4. Use the dir command to verify that all MPUs have sufficient storage space for the upgrade images. If the storage space is not sufficient, delete unused files by using the delete command. For more information, see "Managing file systems."

5. Use FTP or TFTP to transfer the upgrade image file to the root directory of a file system. For more information about FTP and TFTP, see "Configuring FTP" or "Configuring TFTP." For more information about file systems, see "Managing file systems."

Preloading the BootWare image to BootWare (in standalone mode)

6. Load the upgrade BootWare image to the Normal area of BootWare.

bootrom update file file slot slot-number-list [ subslot subslot-number-list ] [ all | part ]

Specify the downloaded software image file for the file argument.

The new BootWare image takes effect at a reboot.

Preloading the BootWare image to BootWare (in IRF mode)

7. Load the upgrade BootWare image to the Normal area of BootWare.

bootrom update file file chassis chassis-number slot slot-number-list [ subslot subslot-number-list ] [ all | part ]

Specify the downloaded software image file for the file argument.

The new BootWare image takes effect at a reboot.

Specifying startup images and completing the upgrade

Perform the following steps in user view:

1. Specify main or backup startup images for all MPUs.

In standalone mode:

¡ Use an .ipe file:

boot-loader file ipe-filename all { backup | main }

¡ Use .bin files:

boot-loader file boot filename system filename [ feature filename&<1-30> ] { all | slot slot-number } { backup | main }

In IRF mode:

¡ boot-loader file ipe-filename all { backup | main }

¡ boot-loader file boot filename system filename [ feature filename&<1-30> ] { all | chassis chassis-number slot slot-number } { backup | main }

The command copies the specified startup images to the root directory of the default file system on each MPU.

As a best practice in a multichassis IRF fabric, specify the all keyword for the command. If you use the slot slot-number option to upgrade member devices one by one, version inconsistencies occur among the member devices during the upgrade.

2. Save the running configuration.

save

This step ensures that any configuration you have made can survive a reboot.

3. Reboot the device.

reboot

4. (Optional.) Verify the software image settings.

display boot-loader [ slot slot-number ]

Verify that the current software images are the same as the startup software images.

Enabling automatic software synchronization from the active MPU to the standby MPU

About this task

This feature is available only when the device is operating in standalone mode. To synchronize software from the global active MPU to other MPUs on an IRF fabric, use the irf auto-update enable command. For more information about software auto-update, see IRF in Virtual Technologies Configuration Guide.

When the standby MPU starts up, this feature examines its startup software images for version inconsistency with the current software images on the active MPU. If the software versions are different, the standby MPU performs the following operations:

1. Copies the current software images of the active MPU.

2. Specifies the images as startup software images.

3. Reboots with these images.

Restrictions and guidelines

For a successful synchronization in a multiuser environment, make sure no other users reboot or swap MPUs during the synchronization process.

To track the synchronization process, configure the information center to output synchronization status logs to configuration terminals. For more information, see Network Management and Monitoring Configuration Guide.

This feature is related to the startup software version check feature for the standby MPU.

· Enabling both features ensures the standby MPU always runs the same software images as the active MPU. However, the standby MPU might fail to synchronize the software images of the active MPU if their software images have critical differences.

· If you disable the startup software version check feature, the standby MPU can start up with a different software version than the active MPU. However, the device might not be able to operate correctly.

· If you enable the startup software version check feature but disable automatic software synchronization, the standby MPU cannot start up in the case of a version inconsistency.

Procedure

1. Enter system view.

system-view

2. Enable startup software version check for the standby MPU.

undo version check ignore

By default, startup software version check is enabled.

3. Enable automatic software synchronization for the standby MPU.

version auto-update enable

By default, automatic software synchronization is enabled.

Synchronizing startup images from the active MPU to the standby MPU (in standalone mode)

About this task

Perform this task when the startup images on the standby MPU are not the same version as those on the active MPU.

This task synchronizes startup images that are running on the active MPU to the standby MPU. If any of the startup images does not exist or is invalid, the synchronization fails.

The startup images synchronized to the standby MPU are set as main startup images, regardless of whether the source startup images are main or backup.

Restrictions and guidelines

If an upgrade by using install commands or patch installation has been performed on the active MPU, use the install commit command to update the set of main startup images on the active MPU before software synchronization. This command ensures startup image consistency between the active MPU and the standby MPU.

Procedure

Perform the following steps in user view:

1. Synchronize startup images from the active MPU to the standby MPU.

boot-loader update { all | slot slot-number }

The command execution results are the same, regardless of whether you specify the all keyword or the slot slot-number option.

2. Reboot the standby MPU.

reboot slot slot-number [ force ]

Synchronizing startup images from the global active MPU to global standby MPUs (in IRF mode)

About this task

Perform this task when the startup images on a global standby MPU are not the same version as those on the global active MPU.

This task synchronizes startup images that are running on the global active MPU to standby MPUs. If any of the startup images does not exist or is invalid, the synchronization fails.

The startup images synchronized to the standby MPUs are set as main startup images, regardless of whether the source startup images are main or backup.

Restrictions and guidelines

If an upgrade by using install commands or patch installation has been performed on the global active MPU, use the install commit command to update the set of main startup images on the global active MPU before software synchronization. This command ensures startup image consistency between the global active MPU and standby MPUs.

Procedure

Perform the following steps in user view:

1. Synchronize startup images from the global active MPU to global standby MPUs.

boot-loader update { all | chassis chassis-number slot slot-number }

By default, this feature is enabled.

2. Reboot a global standby MPU.

reboot [ chassis chassis-number [ slot slot-number ] ] [ force ]

Upgrading device software by using install commands

Upgrade tasks at a glance

1. (Optional.) Decompressing an .ipe file

2. Installing or upgrading software images

3. (Optional.) Deactivating software images

1. (Optional.) Committing software changes

2. Verifying software images

3. (Optional.) Deleting inactive software images

Decompressing an .ipe file

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

display install ipe-info

2. Decompress the .ipe file.

install add ipe-filename filesystem

Installing or upgrading software images

About installing or upgrading features and patches

You can install a new feature or patch image, or upgrade an existing boot, system, or feature image.

The device requires a boot image and a system image to operate correctly. You can uninstall only feature and patch images.

Software image installation and upgrade methods

Use one of the following methods to activate software images:

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

· Image by image—Activate one image on all slots before activating another image. Before using this method, read the release notes to make sure the upgrade images are compatible with the current images. If the upgrade images are not compatible with the current images, the upgrade might fail.

Restrictions and guidelines

In standalone mode:

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

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

In IRF mode:

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

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

You do not need to upgrade LPUs or switching fabric modules separately. They are upgraded automatically when MPUs are upgraded.

The activate operation only updates the current software image list. For the image changes to take effect after a reboot, you must perform a commit operation to update the main startup image list.

Installing or upgrading boot, system, and feature images

To activate boot, system, and feature images, execute the following commands in user view:

1. Verify that the system is stable.

display system stable state

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

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

Installing patch images

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

1. Verify that the system is stable.

display system stable state

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

2. Activate patch images.

In standalone mode:

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

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

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

In IRF mode:

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

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

Deactivating software images

Restrictions and guidelines

You can deactivate only feature and patch images.

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

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

Deactivating feature images

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

1. Verify that the system is stable.

display system stable state

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

2. Deactivate feature images.

In standalone mode:

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

In IRF mode:

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

Deactivating patch images

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

1. Verify that the system is stable.

display system stable state

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

2. Deactivate patch images.

In standalone mode:

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

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

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

In IRF mode:

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

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

Committing software changes

About committing software changes

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

Procedure

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

install commit

Verifying software images

About software image verification

Perform this task to verify the following items:

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

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

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

Procedure

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

1. Verify software images.

install verify

2. Activate or deactivate images as required.

install { activate | deactivate }

3. Commit the software changes.

install commit

Deleting inactive software images

About deleting inactive software images

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

Restrictions and guidelines

This task deletes image files permanently.

Procedure

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

In standalone mode:

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

In IRF mode:

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

Upgrading firmware

About this task

Perform this task to upgrade firmware for components that cannot be upgraded when you upgrade Comware. Examples of these components include complex programmable logical devices (CPLDs), field programmable gate arrays (FPGAs), and 3G modems.

Restrictions and guidelines

After you upgrade firmware for a component, you must power cycle the card where the component resides for the upgrade to take effect.

You can power cycle a card by using one of the following methods:

· Power cycle the device that holds the card.

· Remove and reinstall the card.

· Power cycle the card from the CLI:

¡ power-supply off

¡ power-supply on

Support for these methods depends on the card model.

Procedure

To upgrade firmware, execute the following command in user view:

In standalone mode:

firmware update slot slot-number [ subslot subslot-number ] { cpld cpld-number | fpga fpga-number | module module-number } file filename

In IRF mode:

firmware update chassis chassis-number slot slot-number [ subslot subslot-number ] { cpld cpld-number | fpga fpga-number | module module-number } file filename

Display and maintenance commands for software images

(In standalone mode.) Execute display commands in any view and reset commands in user view.

Task	Command
Display running software images and startup software images.	display boot-loader [ slot slot-number ]
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 in the root directories of file systems.	display install inactive [ slot slot-number ] [ verbose ]
Display the software images included in an .ipe file.	display install ipe-info ipe-filename
Display ongoing activate and deactivate operations.	display install job
Display software image file information.	display install package { filename \| all } [ verbose ]
Display the software image file that includes a specific component or file.	display install which { component name \| file filename } [ slot slot-number ]

‌

(In IRF mode.) Execute display commands in any view and reset commands in user view.

Task	Command
Display running software images and startup software images.	display boot-loader [ chassis chassis-number slot slot-number ]
Display active software images.	display install active [ chassis chassis-number slot slot-number ] [ verbose ]
Display backup startup software images.	display install backup [ chassis chassis-number slot slot-number ] [ verbose ]
Display main startup software images.	display install committed [ chassis chassis-number slot slot-number ] [ verbose ]
Display inactive software images in the root directories of file systems.	display install inactive [ chassis chassis-number slot slot-number ] [ verbose ]
Display the software images included in an .ipe file.	display install ipe-info ipe-filename
Display ongoing activate and deactivate operations.	display install job
Display software image file information.	display install package { filename \| all } [ verbose ]
Display the software image file that includes a specific component or file.	display install which { component name \| file filename } [ chassis chassis-number slot slot-number ]

‌

Software upgrade examples

Example: Upgrading device software (in standalone mode)

Network configuration

As shown in Figure 1, the device has two MPUs: one active MPU in slot 0 and one standby MPU in slot 1.

Use the file startup-a2105.ipe to upgrade software images for the device.

Figure 1 Network diagram

Procedure

# Configure IP addresses and routes. Make sure the device and the TFTP server can reach each other. (Details not shown.)

# Configure TFTP settings on both the device and the TFTP server. (Details not shown.)

# Display information about the current software images.

<Sysname> display version

# Back up the current software images.

<Sysname> copy boot.bin boot_backup.bin

<Sysname> copy system.bin system_backup.bin

# Specify boot_backup.bin and system_backup.bin as the backup startup image files for both MPUs.

<Sysname> boot-loader file boot flash:/boot_backup.bin system flash:/system_backup.bin slot 0 backup

<Sysname> boot-loader file boot flash:/boot_backup.bin system flash:/system_backup.bin slot 1 backup

# Use TFTP to download the startup-a2105.ipe image file from the TFTP server to the root directory of the flash memory on the active MPU.

<Sysname> tftp 2.2.2.2 get startup-a2105.ipe

# Specify startup-a2105.ipe as the main startup image file for both MPUs.

<Sysname> boot-loader file flash:/startup-a2105.ipe slot 0 main

<Sysname> boot-loader file flash:/startup-a2105.ipe slot 1 main

# Verify the startup image settings.

<Sysname> display boot-loader

# Reboot the device to complete the upgrade.

<Sysname> reboot

Verifying the configuration

# Verify that the device is running the correct software.

<Sysname> display version

Example: Upgrading device software (in IRF mode)

Network configuration

As shown in Figure 2, use the file startup-a2105.ipe to upgrade software images for the IRF fabric.

Each IRF member device has two MPUs: one in slot 0 and one in slot 1. The global active MPU is in slot 0 on the master device.

Figure 2 Network diagram

Procedure

# Configure IP addresses and routes. Make sure the device and the TFTP server can reach each other. (Details not shown.)

# Configure TFTP settings on both the device and the TFTP server. (Details not shown.)

# Display information about the current software images.

<Sysname> display version

# Back up the current software images.

<Sysname> copy boot.bin boot_backup.bin

<Sysname> copy system.bin system_backup.bin

# Specify boot_backup.bin and system_backup.bin as the backup startup image files for all MPUs.

<Sysname> boot-loader file boot flash:/boot_backup.bin system flash:/system_backup.bin chassis 1 slot 0 backup

<Sysname> boot-loader file boot flash:/boot_backup.bin system flash:/system_backup.bin chassis 1 slot 1 backup

<Sysname> boot-loader file boot flash:/boot_backup.bin system flash:/system_backup.bin chassis 2 slot 0 backup

<Sysname> boot-loader file boot flash:/boot_backup.bin system flash:/system_backup.bin chassis 2 slot 1 backup

# Use TFTP to download the startup-a2105.ipe image file from the TFTP server to the root directory of the flash memory on the global active MPU.

<Sysname> tftp 2.2.2.2 get startup-a2105.ipe

# Specify startup-a2105.ipe as the main startup image file for all MPUs.

<Sysname> boot-loader file flash:/startup-a2105.ipe chassis 1 slot 0 main

<Sysname> boot-loader file flash:/startup-a2105.ipe chassis 1 slot 1 main

<Sysname> boot-loader file flash:/startup-a2105.ipe chassis 2 slot 0 main

<Sysname> boot-loader file flash:/startup-a2105.ipe chassis 2 slot 1 main

# Verify the startup image settings.

<Sysname> display boot-loader

# Reboot the IRF fabric to complete the upgrade.

<Sysname> reboot

Verifying the configuration

# Verify that the IRF fabric is running the correct software.

<Sysname> display version

Example: Upgrading a feature by using install commands (in standalone mode)

Upgrade requirements

As shown in Figure 3, the device has two MPUs. The active MPU is in slot 0. The standby MPU is in slot 1.

Upgrade the Feature1 feature from T0001015 to T0001016. The two versions are compatible.

Figure 3 Network diagram

Upgrade procedure

# Download the .ipe file that contains the T0001016 Feature1 feature image from the TFTP server.

<Sysname> tftp 2.2.2.2 get feature1-t0001016.ipe

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

Dload Upload Total Spent Left Speed

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

Writing file...Done.

# Decompress the .ipe file.

<Sysname> install add flash:/feature1-t0001016.ipe flash:/

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

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

# Display active software images.

<Sysname> display install active

Active packages on slot 0:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature1-t0001015.bin

Active packages on slot 1:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature1-t0001015.bin

# Identify the recommended upgrade methods and possible impact of the upgrade.

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

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

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

Upgrade summary according to following table:

flash:/feature1-t0001016.bin

Running Version New Version

Test 0001015 Test 0001016

Slot Upgrade Way

1 Service Upgrade

Influenced service according to following table on slot 1:

flash:/feature1-t0001016.bin

Feature1

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

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

Upgrade summary according to following table:

flash:/feature1-t0001016.bin

Running Version New Version

Test 0001015 Test 0001016

Slot Upgrade Way

0 Service Upgrade

1 Service Upgrade

Influenced service according to following table on slot 0:

flash:/feature1-t0001016.bin

Feature1

The output shows that both MPUs need a service upgrade and the Feature1 module will be rebooted during the upgrade.

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

<Sysname> install activate feature flash:/feature1-t0001016.bin slot 1

flash:/feature1-t0001016.bin already exists on slot 1.

Overwrite it?[Y/N]:y

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

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

Upgrade summary according to following table:

flash:/feature1-t0001016.bin

Running Version New Version

Test 0001015 Test 0001016

Slot Upgrade Way

1 Service Upgrade

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

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

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

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

Upgrade summary according to following table:

flash:/feature1-t0001016.bin

Running Version New Version

Test 0001015 Test 0001016

Slot Upgrade Way

0 Service Upgrade

1 Service Upgrade

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

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

# Verify that the new Feature1 image has been activated.

<Sysname> display install active

Active packages on slot 0:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature1-t0001016.bin

Active packages on slot 1:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature1-t0001016.bin

# Commit the software changes.

<Sysname> install commit

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

Example: Upgrading a feature by using install commands (in IRF mode)

Upgrade requirements

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

Upgrade the Feature1 feature from T0001015 to T0001016. The two versions are compatible.

Figure 4 Network diagram

Upgrade procedure

# Download the .ipe file that contains the T0001016 Feature1 feature image from the TFTP server.

<Sysname> tftp 2.2.2.2 get feature1-t0001016.ipe

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

Dload Upload Total Spent Left Speed

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

Writing file...Done.

# Decompress the .ipe file.

<Sysname> install add flash:/feature1-t0001016.ipe flash:

Verifying the file flash:/feature1-t0001016.ipe on slot 1...Done.

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

# Display active software images.

<Sysname> display install active

Active packages on chassis 1 slot 0:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature1-t0001015.bin

Active packages on chassis 1 slot 1:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature1-t0001015.bin

Active packages on chassis 2 slot 0:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature1-t0001015.bin

Active packages on chassis 2 slot 1:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature1-t0001015.bin

# Identify the recommended upgrade methods and possible impact of the upgrade.

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

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

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

Upgrade summary according to following table:

flash:/feature1-t0001016.bin

Running Version New Version

Test 0001015 Test 0001016

Chassis Slot Upgrade Way

2 0 Service Upgrade

2 1 Service Upgrade

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

flash:/feature1-t0001016.bin

Feature1

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

flash:/feature1-t0001016.bin

Feature1

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

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

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

Upgrade summary according to following table:

flash:/feature1-t0001016.bin

Running Version New Version

Test 0001015 Test 0001016

Chassis Slot Upgrade Way

2 0 Service Upgrade

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

flash:/feature1-t0001016.bin

Feature1

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

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

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

Upgrade summary according to following table:

flash:/feature1-t0001016.bin

Running Version New Version

Test 0001015 Test 0001016

Chassis Slot Upgrade Way

1 0 Service Upgrade

1 1 Service Upgrade

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

flash:/feature1-t0001016.bin

Feature1

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

flash:/feature1-t0001016.bin

Feature1

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

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

Upgrade summary according to following table:

flash:/feature1-t0001016.bin

Running Version New Version

Test 0001015 Test 0001016

Chassis Slot Upgrade Way

1 0 Service Upgrade

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

flash:/feature1-t0001016.bin

Feature1

The output shows that all the MPUs need a service upgrade and the Feature1 module will be rebooted during the upgrade.

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

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

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

flash:/feature1-t0001016.bin already exists on chassis 2 slot 1.

Overwrite it?[Y/N]:y

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

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

Upgrade summary according to following table:

flash:/feature1-t0001016.bin

Running Version New Version

Test 0001015 Test 0001016

Chassis Slot Upgrade Way

2 0 Service Upgrade

2 1 Service Upgrade

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

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

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

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

Overwrite it?[Y/N]:y

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

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

Upgrade summary according to following table:

flash:/feature1-t0001016.bin

Running Version New Version

Test 0001015 Test 0001016

Chassis Slot Upgrade Way

2 0 Service Upgrade

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

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

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

flash:/feature1-t0001016.bin already exists on chassis 1 slot 1.

Overwrite it?[Y/N]:y

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

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

Upgrade summary according to following table:

flash:/feature1-t0001016.bin

Running Version New Version

Test 0001015 Test 0001016

Chassis Slot Upgrade Way

1 0 Service Upgrade

1 1 Service Upgrade

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

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

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

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

Upgrade summary according to following table:

flash:/feature1-t0001016.bin

Running Version New Version

Test 0001015 Test 0001016

Chassis Slot Upgrade Way

1 0 Service Upgrade

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

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

# Verify that the new Feature1 image has been activated.

<Sysname> display install active

Active packages on chassis 1 slot 0:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature1-t0001016.bin

Active packages on chassis 1 slot 1:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature1-t0001016.bin

Active packages on chassis 2 slot 0:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature1-t0001016.bin

Active packages on chassis 2 slot 1:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature1-t0001016.bin

# Commit the software changes.

<Sysname> install commit

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

01-Fundamentals Configuration Guide

Startup software images

Image loading process at startup

Handling the emergency shell process or image loading failure

Upgrading the device

Synchronizing startup images from the active MPU to standby MPUs

Preloading the BootWare image to BootWare (in standalone mode)

Preloading the BootWare image to BootWare (in IRF mode)

About this task

Restrictions and guidelines

Procedure

Synchronizing startup images from the active MPU to the standby MPU (in standalone mode)

About this task

Restrictions and guidelines

Procedure

Synchronizing startup images from the global active MPU to global standby MPUs (in IRF mode)

About this task

Restrictions and guidelines

Procedure

About installing or upgrading features and patches

Software image installation and upgrade methods

Restrictions and guidelines

Installing or upgrading boot, system, and feature images

Installing patch images

Restrictions and guidelines

Deactivating feature images

Deactivating patch images

About committing software changes

Procedure

About software image verification

Procedure

About deleting inactive software images

Restrictions and guidelines

Procedure

Upgrading firmware

About this task

Restrictions and guidelines

Procedure

Example: Upgrading device software (in standalone mode)

Network configuration

Procedure

Verifying the configuration

Example: Upgrading device software (in IRF mode)

Network configuration

Procedure

Verifying the configuration

Example: Upgrading a feature by using install commands (in standalone mode)

Upgrade requirements

Upgrade procedure

Example: Upgrading a feature by using install commands (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