Software upgrade enables you to add new features and fix bugs. This chapter describes types of software and methods to upgrade software from the CLI without using ISSU. For a comparison of all software upgrade methods, see "Upgrade methods."

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

In an IRF 3 system, the parent devices and PEXs use separate software images. You must specify software images for the parent devices and PEXs separately. For more information about IRF 3, see Virtual Technologies Configuration Guide.

Unless otherwise stated, the term "IRF system" refers to both IRF 2 fabrics and IRF 3 systems. The term "IRF fabric" refers to both a standalone IRF 2 fabric and the parent fabric in an IRF 3 system.

NOTE:

In an IRF 3 system, the master device on the parent fabric is also the master of the entire system.

‌

Software types

The following software types are available:

· BootWare image—Also called a Boot ROM image. This image is a .bin file that 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. You can use these menus to load software and the startup configuration file or manage files when the device cannot start up correctly.

· 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 software features. Users purchase feature images as needed.

¡ Patch image—A .bin file irregularly released for fixing bugs without rebooting the device. A patch image does not add new features or functions.

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 an MPU to operate. These images might be released separately or as a whole in one .ipe package file. If an .ipe file is used, the system decompresses the file automatically, loads the .bin images and sets them as startup software images. Typically, the BootWare and startup software images for the device are released in an .ipe file named main.ipe.

Software file naming conventions

Software image file names use the chassis-comware version-image type-release format, for example, S7500E-CMW710-SYSTEM-E752201.bin and S7500E-CMW710-BOOT-E752201.bin. This document uses boot.bin and system.bin as boot and system image file names.

Comware image redundancy and loading procedure

You can specify two lists of Comware software images: one main and one backup.

The system always attempts to start up with the main images. If any main image does not exist or is invalid, the system tries the backup images. Figure 1 shows the entire Comware image loading procedure.

In this procedure, both the main and backup image lists have feature and patch images. If an image list does not have feature or patch images, the system starts up with the boot and system images after they pass verification.

If both the main and backup boot images are nonexistent or invalid, access the BootWare menu during the system startup to upgrade software.

After accessing 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."

Figure 1 Comware image loading procedure

System startup process

Upon power-on, the BootWare image runs to initialize hardware, and then the startup software images run to start up the entire system, as shown in Figure 2.

Figure 2 System startup process

PEX startup process

PEX startup process differs depending on the availability of storage media on PEXs.

· If a PEX has a file system, it can start up from the local file system or from the file system on the parent device.

· If a PEX does not have a file system, it must start up from the file system on the parent device.

The S6300, S5130-EI, and S5130-HI switches can act as PEXs in an IRF 3 system. These switches have file systems.

NOTE:

The PEX startup images on the PEX's local file system are called local startup images. The PEX startup images on the parent devices are called remote startup images.

The PEX startup process is as follows:

1. Upon power-on, the PEX runs the BootWare image to initialize hardware and display hardware parameters.

2. The PEX attempts to load software images from its local file system (see Figure 4):

a. The PEX searches the local file system for startup images:

- If all the images exist and are valid, the PEX goes to step b.

- If any images do not exist or are invalid, the PEX goes to step 3.

b. The system verifies the compatibility of the PEX startup software images with the running software images of the glabal active MPU:

- If all the images are compatible, the PEX starts up with the images in the local file system.

- If any incompatibility exists, the PEX goes to step 3.

3. The PEX attempts to load software images from the glabal active MPU (see Figure 5):

a. The PEX searches the file system on the glabal active MPU for the startup images:

- If all the images exist and are valid, the PEX goes to step b.

- If any images do not exist or are invalid, the startup process fails. You must specify new PEX startup images from the CLI or from the PEX's BootWare menus.

b. The PEX verifies the compatibility of the PEX startup software images with the running software images on the glabal active MPU:

- If the images are compatible, the PEX loads the PEX software images from the glabal active MPU.

- If any incompatibility exists, the startup process fails. You must specify new PEX startup images from the CLI or from the PEX's BootWare menus.

Figure 3 Generic PEX startup process

Figure 4 PEX startup from the local file system

Figure 5 PEX startup from the parent device's file system

Upgrade methods

Upgrading method	Software types	Remarks
Upgrading from the CLI without using ISSU	· BootWare image · Comware images (excluding patches)	This method is disruptive. You must reboot the entire device to complete the upgrade.
Performing an ISSU	Comware images	The ISSU method enables a software upgrade without service interruption. Use this method for an IRF fabric or MPU-redundant device. For more information about ISSU, see "Performing ISSU."
Upgrading from the BootWare menu	· BootWare image · Comware software images	Use this method when the device cannot start up correctly. To use this method, first connect to the console port and power cycle the device or PEX. Then press Ctrl+B at prompt to access the BootWare menu. IMPORTANT: Upgrade an IRF system from the CLI instead of the BootWare menu, if possible. The BootWare menu method increases the service downtime, because it requires that you upgrade the member devices one by one.

This chapter only covers upgrading software from the CLI without using ISSU.

Upgrade restrictions and guidelines

The device can start up from the built-in flash memory or the USB disk. As a best practice, store the startup images in the built-in flash memory. If you store the startup images on the USB disk, do not remove the USB disk during the startup process.

Preparing for the upgrade

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 each MPU has 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 the file system."

5. Use FTP or TFTP to transfer the upgrade image file to the root directory of a file system on the active MPU or global active MPU. If the storage medium is partitioned, save the file to the root directory of the first file system on the storage medium. For more information about FTP and TFTP, see "Configuring FTP" or "Configuring TFTP." For more information about partitioning, see "Managing file systems."

Upgrade task list for the parent device

Tasks at a glance	Remarks
(Optional.) Preloading the BootWare image to BootWare	If a BootWare upgrade is required, you can perform this task to shorten the subsequent upgrade time. This task helps avoid upgrade problems caused by unexpected electricity failure. If you skip this task, the device upgrades the BootWare automatically when it upgrades the startup software images. The BootWare image preloaded into the BootWare takes effect only after you reboot the device. You can perform this task to upgrade the BootWare image on the device or on a PEX.
(Required.) Specifying startup images and completing the upgrade (in standalone mode) (Required.) Specifying startup images and completing the upgrade (in IRF mode)	Perform this task to upgrade a standalone device, an IRF fabric, or the parent fabric in an IRF 3 system. Start with the parent fabric when you upgrade the parent fabric and PEXs in an IRF 3 system.
(Optional.) Enabling software synchronization from the active MPU to the standby MPU at startup	By default, software synchronization is enabled. This feature enables automatic software synchronization when the device operates in standalone mode. With software synchronization, you do not need to manually upgrade the standby MPU. To synchronize software from the global active MPU to other MPUs on an IRF fabric, use the irf auto-update enable command.
(Optional.) Upgrading PEXs	Perform this task to upgrade the PEXs in an IRF 3 system.

Preloading the BootWare image to BootWare

Task	Command	Remarks
Load the upgrade BootWare image to the Normal area of BootWare.	In standalone mode: bootrom update file file slot slot-number-list In IRF mode: bootrom update file file chassis chassis-number slot slot-number-list	Specify the downloaded software image file for the file argument. The new BootWare image takes effect at a reboot.

Task

Command

Remarks

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

In standalone mode:
bootrom update file file slot slot-number-list

In IRF mode:
bootrom update file file chassis chassis-number slot slot-number-list

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 (in standalone mode)

Perform this task in user view.

To specify the startup image file and complete the upgrade:

Step	Command	Remarks
1. Specify main or backup startup images for the active MPU.	· Use an .ipe file for upgrade: boot-loader file ipe-filename { all \| slot slot-number } { backup \| main } · Use .bin files for upgrade: boot-loader file boot filename system filename [ feature filename&<1-30> ] { all \| slot slot-number } { backup \| main }	Upgrade files must be saved in the root directory of a file system on the active MPU. If the storage medium is partitioned, save the file to the root directory of the first file system on the storage medium.
2. Specify main or backup startup images for the standby MPU.	· Method 1: ¡ Use an .ipe file for upgrade: boot-loader file ipe-filename { all \| slot slot-number } { backup \| main } ¡ Use .bin files for upgrade: boot-loader file boot filename system filename [ feature filename&<1-30> ] { all \| slot slot-number } { backup \| main } · Method 2: boot-loader update { all \| slot slot-number } · Method 3: See "Enabling software synchronization from the active MPU to the standby MPU at startup."	When you use method 2, make sure you understand the following requirements and upgrade results: · If an ISSU upgrade has been performed, use the install commit command to update the main startup images on the active MPU before software synchronization. The command ensures startup image consistency between the active MPU and the standby MPU. · If the active MPU started up with main startup images, its main startup images are synchronized to the standby MPU. This synchronization occurs regardless of whether any change has occurred to this set of startup images. · If the active MPU started up with backup startup images, its backup startup images are synchronized to the standby MPU. This synchronization occurs regardless of whether any change has occurred to this set of startup images. · Startup image synchronization will fail if any software image being synchronized is corrupted or is not available.
3. Save the running configuration.	save	This step ensures that any configuration you have made can survive a reboot.
4. Reboot the device.	reboot	At startup, the MPUs read the preloaded BootWare image to RAM, and load the startup images.
5. (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.

Specifying startup images and completing the upgrade (in IRF mode)

Perform this task in user view.

To specify the startup image file and complete the upgrade:

Step	Command	Remarks
1. Specify main or backup startup images for the global active MPU.	· Use an .ipe file for upgrade: boot-loader file ipe-filename { all \| chassis chassis-number slot slot-number } { backup \| main } · Use .bin files for upgrade: boot-loader file boot filename system filename [ feature filename&<1-30> ] { all \| chassis chassis-number slot slot-number } { backup \| main }	Upgrade files must be saved in the root directory of a file system on the global active MPU. If the storage medium is partitioned, save the file to the root directory of the first file system on the storage medium.
2. Specify the main startup images for each standby MPU in the IRF fabric.	· Method 1: ¡ Use an .ipe file for upgrade: boot-loader file ipe-filename { all \| chassis chassis-number slot slot-number } { backup \| main } ¡ Use .bin files for upgrade: boot-loader file boot filename system filename [ feature filename&<1-30> ] { all \| chassis chassis-number slot slot-number } { backup \| main } · Method 2: boot-loader update { all \| chassis chassis-number slot slot-number }	Skip this step if you have only one single-MPU device. When you use the boot-loader update command, make sure you understand the following requirements and upgrade results: · If an ISSU upgrade has been performed, use the install commit command to update the main startup images on the active MPU before software synchronization. The command ensures startup image consistency between the active MPU and the standby MPU. · The boot-loader update command uses the main or backup startup image list for synchronization, instead of the current software images list. ¡ The main images list is used if the global active MPU started up with the main startup images. ¡ The backup image list is used if the global active MPU started up with the backup startup images. Startup image synchronization will fail if any software image being synchronized is corrupted or is not available.
3. Save the running configuration.	save	This step ensures that any configuration you have made can survive a reboot.
4. Reboot the IRF fabric.	reboot	At startup, the MPUs read the preloaded BootWare image to RAM, and load the startup images.
5. (Optional.) Verify the software image settings.	display boot-loader [ chassis chassis-number [ slot slot-number ] ]	Verify that the current software images are the same as the startup software images.

Enabling software synchronization from the active MPU to the standby MPU at startup

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

IMPORTANT:

To ensure a successful synchronization in a multiuser environment, prevent users from rebooting or swapping MPUs during the software synchronization process. You can configure the information center to output the synchronization status to configuration terminals (see Network Management and Monitoring Configuration Guide).

To enable software synchronization from the active MPU to the standby MPU at startup:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enable startup software version check for the standby MPU.	undo version check ignore	By default, startup software version check is enabled.
3. Enable software auto-update for the standby MPU.	version auto-update enable	By default, software version auto-update is enabled.

Upgrading PEXs

Preparing for the upgrade

To upgrade PEX software from the CLI without using ISSU:

1. Use the display version command to identify the current BootWare and Comware image versions on the PEX.

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 and Comware software images.

¡ Software compatibility between the PEX and the parent device.

3. Use the dir command to verify that the global active MPU has sufficient storage space for the upgrade images. If the storage space is not sufficient, delete unused files by using the delete command. For a PEX to start up from its local file system, you must make sure its local file system has sufficient space for the upgrade images. For more information, see "Managing the file system."

4. Use FTP or TFTP to transfer the upgrade image file to the root directory of a file system on the global active MPU. If the storage medium is partitioned, save the file to the root directory of the first file system on the storage medium. For more information about FTP and TFTP, see "Configuring FTP" or "Configuring TFTP." For more information about partitioning, see "Managing file systems."

Upgrade procedure

Perform this task in user view.

Step	Command	Remarks
1. Specify main or backup startup images for the PEX to load from the local file system.	· Use an .ipe file for upgrade: boot-loader file ipe-filename chassis chassis-number slot slot-number { backup \| main } · Use .bin files for upgrade: boot-loader file boot filename system filename [ feature filename&<1-30> ] chassis chassis-number slot slot-number { backup \| main }	The boot-loader file command copies the specified images from the global active MPU to the default file system of the PEX. Specify the PEX chassis number for the chassis-number argument. Specify the PEX slot number for the slot-number argument.
2. Specify PEX startup images for the PEX to load from the parent device.	· Use an .ipe file for upgrade: boot-loader pex pex-model file ipe ipe-filename · Use .bin files for upgrade: boot-loader pex pex-model file boot filename system filename [ feature filename&<1-30> ]	To prevent a PEX startup failure after an active/standby or master/subordinate switchover, execute this command after you add a new MPU or member device to the parent device. · For PEXs that lack storage media, you must use this command to set their startup software images. · For PEXs that have a file system, you can use this command to set startup software images for backup. To guarantee that the PEX loads the correct software when a master/subordinate switchover occurs, make sure the PEX startup software images are the same across the MPUs in the IRF fabric.
3. Save the running configuration.	save	This step ensures that any configuration you have made can survive a reboot.
4. Reboot the PEX.	reboot chassis chassis-number slot slot-number	Specify the PEX chassis number for the chassis-number argument. Specify the PEX slot number for the slot-number argument. The PEX device reboots with the new startup images.

Displaying and maintaining software image settings

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

Task	Command
(In standalone mode.) Display current software images and startup software images.	display boot-loader [ slot slot-number ]
(In IRF mode.) Display current software images and startup software images.	display boot-loader [ chassis chassis-number [ slot slot-number ] ]
Display the PEX startup software images on the parent device.	display boot-loader pex [pex-model ]
Clear the PEX startup software image list on the parent device.	reset boot-loader pex pex-model

Software upgrade examples

Non-ISSU software upgrade example (in standalone mode)

Network requirements

As shown in Figure 6, 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 6 Network diagram

Configuration 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

# Use TFTP to download the image file startup-a2105.ipe 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

# Copy the .bin image files decompressed from startup-a2105.ipe and save them to the current directory as boot_backup.bin and system_backup.bin.

<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

# Verify the startup image settings.

<Sysname> display boot-loader

# Reboot the device to complete the upgrade.

<Sysname> reboot

# Verify that the device is running the correct software.

<Sysname> display version

Non-ISSU software upgrade example (in IRF mode)

Network requirements

As shown in Figure 7, 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 7 Network diagram

Configuration 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

# Use TFTP to download the image file startup-a2105.ipe 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

# Copy the .bin image files decompressed from startup-a2105.ipe and save them to the current directory as boot_backup.bin and system_backup.bin.

<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

# Verify the startup image settings.

<Sysname> display boot-loader

# Reboot the IRF fabric to complete the upgrade.

<Sysname> reboot

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

<Sysname> display version

Non-ISSU PEX upgrade example

Network requirements

As shown in Figure 8:

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

· The IRF fabric has two S6300 PEXs . One PEX is in slot 110 and the other is in slot 120.

Use file startup-s6300.ipe to update the PEXs.

Figure 8 Network diagram

Configuration procedure

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

# Configure TFTP settings on the IRF fabric and the TFTP server. (Details not shown.)

# Display information about the current software images.

<Sysname> display version

# Use TFTP to download upgrade file startup-s6300.ipe 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-s6300.ipe

# Specify startup-s6300.ipe as the main startup image file for the PEXs to load from its local file system.

<Sy sname> boot-loader file flash:/startup-s6300.ipe chassis 5 slot 1 main

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

# Copy the .bin image files decompressed from startup-s6300.ipe and save them to the current directory as s6300-boot_backup.bin and s6300-system_backup.bin.

<Sysname> copy s6300-boot.bin s6300-boot_backup.bin

<Sysname> copy s6300-system.bin s6300-system_backup.bin

# Specify s6300-boot_backup.bin and s6300-system_backup.bin as the backup startup image files for the PEXs to load from its local file system.

<Sysname> boot-loader file boot flash:/s6300-boot_backup.bin system flash:/system_ s6300-backup.bin chassis 110 slot 0 backup

<Sysname> boot-loader file boot flash:/s6300-boot_backup.bin system flash:/system_ s6300-backup.bin chassis 120 slot 0 backup

# Verify the startup image settings for the PEXs.

<Sysname> display boot-loader

# Specify startup-s6300.ipe as the PEX startup image file for the PEXs to load from the parent device.

<Sysname> boot-loader pex PEX-S6300 file ipe flash:/startup-s6300.ipe

# Verify the PEX startup image settings on the parent device for the PEXs.

<Sysname> display boot-loader pex

# Reboot the PEXs to complete the upgrade.

<Sysname> reboot chassis 110 slot 0

<Sysname> reboot chassis 120 slot 0

# Verify that the PEXs are running the correct software.

<Sysname> display version

01-Fundamentals Configuration Guide

Network requirements

Configuration procedure

Network requirements

Configuration procedure

Network requirements

Configuration 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