Contents

Upgrading software· 1

About software upgrade· 1

Software types· 1

Software release forms· 2

Upgrade methods· 2

Software image loading· 2

Restrictions and guidelines: Software upgrade· 3

Upgrading device software by using the boot loader method· 3

Restrictions and guidelines· 3

Software upgrade tasks at a glance· 3

Prerequisites· 4

Specifying startup images and completing the upgrade· 4

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

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

Upgrading the CPLD firmware· 6

Display and maintenance commands for software images· 6

Software upgrade examples· 6

Example: Upgrading device software (in standalone mode) 6

Example: Upgrading device software (in IRF mode) 7

Upgrading software

About software upgrade

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 ISSU from the CLI	Comware images	This method enables a software upgrade with a minimum amount of downtime. Use this method if possible. For more information about ISSU, see "Performing an ISSU."
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.

Software upgrade is supported only on the default MDC.

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

Specifying startup images and completing the upgrade

Synchronizing startup images from the active MPU to 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."

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.

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 ISSU 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 ISSU 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 the CPLD firmware

About this task

Perform this task to upgrade firmware for the complex programmable logical device (CPLD), which does not run Comware and must be upgraded separately.

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 power cycling the device that holds the card or remove and reinstall the card.

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 file filename

In IRF mode:

firmware update chassis chassis-number slot slot-number [ subslot subslot-number ] cpld cpld-number file filename

Display and maintenance commands for software images

Execute display commands in any view.

 

Task	Command
Display running software images and startup software images.	In standalone mode: display boot-loader [ slot slot-number ] In IRF mode: display boot-loader [ 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