This chapter describes types of software and how to upgrade software from the CLI in the non-ISSU approach. For a comparison of all software upgrade methods, see "Upgrade methods."

Overview

Software upgrade enables you to have new features and fix bugs. Before performing an upgrade, use the release notes for the new software version to verify software and hardware compatibility and evaluate upgrade impacts.

Software types

The following software types are available:

· BootWare image—A .bin file that comprises a basic section and an extended section. The basic section is the minimum code that bootstraps the system. The extended section enables hardware initialization and provides system management menus. You can use these menus to load application software and the startup configuration file or manage files when the device cannot correctly start up.

· 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 minimum feature modules required for device operation and some basic features, including device management, interface management, configuration management, and routing. To have advanced features, you must purchase feature packages.

¡ Feature package—Includes a set of advanced software features. Users purchase feature packages as needed.

¡ Patch packages—Irregularly released packages for fixing bugs without rebooting the device. A patch package does not add new features or functions.

Comware software 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 system to work. These images might be released separately or as a whole in one .ipe package file. If an .ipe file is used, the system automatically decompresses the file, loads the .bin boot and system 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.

Comware image redundancy and loading procedure

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

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

This procedure assumes that the main image set and the backup image set have feature packages and patch packages. If an image set does not have feature packages or patch packages, the system can use the image set to start up after the boot image and the system image passes verification.

If neither the main boot image nor the backup boot image exists or is valid, connect to the console port and re-power on the device to access the Boot menu for loading a boot image. For more information about downloading and loading a boot image, see S12500 release notes.

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

Upgrade methods

Upgrading method	Software types	Remarks
Upgrading from the CLI:
Non-ISSU approach	· BootWare image · Comware images (excluding patches)	You must reboot the entire device to complete the upgrade. This approach causes service interruption.
ISSU approach	Comware images	The ISSU approach enables a software upgrade without service interruption. Use this approach for an IRF fabric or MPU-redundant device. For more information about ISSU, see "Performing ISSU."
Upgrading from the Boot menu	· BootWare image · Comware software images	Use this method when the device cannot correctly start up. IMPORTANT: Upgrade an IRF fabric from the CLI rather than the Boot menu. The Boot menu approach requires that you upgrade the member devices one by one and has a larger impact on services than the CLI approach.

This chapter covers only the non-ISSU approach to upgrading software from the CLI.

Non-ISSU upgrade procedure summary

To upgrade software in the non-ISSU approach:

1. Download the upgrade software image file.

2. (Optional.) Preload the BootWare image to the 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 automatically upgrades the BootWare when upgrading the startup software images.

The BootWare image preloaded into the BootWare does not affect the device running status.

3. Specify the image file as the startup software image file.

4. If you are upgrading a standalone device, reboot the device. If you are upgrading an IRF fabric, reboot the entire IRF fabric.

5. Verify the upgrade.

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

3. Use the dir command to verify that all MPUs have sufficient storage space for the upgrade images, and use the delete command to delete unused files. For more information, see "Managing the file system."

4. Configure FTP and TFTP settings.

5. In standalone mode, download the upgrade image file to the root directory of the Flash memory or the CF card on the active MPU. In IRF mode, download the file to the root directory of the Flash memory or the CF card on the global active MPU. If the CF card has been partitioned, save the file to the root directory of the first partition.

For more information about FTP and TFTP configuration and operations, see "Configuring FTP" or "Configuring TFTP."

Preloading the BootWare image to BootWare

Perform this task in user view.

Task	Command	Remarks
Load the upgrade BootWare image from the root directory of a storage medium (Flash memory or CF card) to the Normal area of BootWare.	· In standalone mode: bootrom update file filename slot slot-number-list · In IRF mode: bootrom update file filename chassis chassis-number slot slot-number-list	Specify the downloaded software image file for the filename argument. The new BootWare image takes effect at a reboot.

Task

Command

Remarks

Load the upgrade BootWare image from the root directory of a storage medium (Flash memory or CF card) to the Normal area of BootWare.

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

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

Specify the downloaded software image file for the filename argument.

The new BootWare image takes effect at a reboot.

Specifying the startup image file and completing the upgrade

Perform this task in user view.

Step	Command	Remarks
1. Specify the upgrade file as the main or backup startup image file for the active MPU.	Approach 1: boot-loader file ipe-filename slot slot-number { backup \| main } Approach 2: boot-loader file boot boot-package system system-package [ feature feature-package&<1-30> ] slot slot-number { backup \| main }	Use either approach. You can also specify a backup startup image file. In approach 1, the file name must take the storage-medium:/base-filename.ipe format, for example, flash:/startup.ipe. In approach 2, all file names must take the storage-medium:/base-filename.bin format, for example, flash:/startup-boot.bin.
1. Specify main or backup startup images for the standby MPU.	Approach 1: boot-loader file ipe-filename slot slot-number { backup \| main } Approach 2: boot-loader file boot boot-package system system-package [ feature feature-package&<1-30> ] slot slot-number { backup \| main } Approach 3: boot-loader update slot slot-number Approach 4: See "Enabling software synchronization from the active MPU to the standby MPU at startup."	Use one of the approaches. For more information about the upgrade methods provided by these commands, see Fundamentals Command Reference. In approach 3: · If the active MPU has started up with main startup images, its main startup images are synchronized to the standby MPU, regardless of whether any change has been made to this set of startup images. · If the active MPU has started up with backup startup images, its backup startup images are synchronized to the standby MPU, regardless of whether any change has been made to this set of startup images. · Startup image synchronization fails if any software image being synchronized is not available or has been corrupted. · If a patch installation or software upgrade has been performed in ISSU approach, use the install commit command to update the set of main startup images on the active MPU before software synchronization for startup image consistency between the active MPU and the standby MPU.
2. Save the running configuration.	save	This step makes sure any configuration you have made can survive a reboot.
3. Reboot the device.	reboot	At startup, the MPUs read the preloaded BootWare image to RAM, load the startup images in the file, and set the images as both current software images and startup software images.
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.

Specifying the startup image file and completing the upgrade (in IRF mode)

Perform this task in user view.

Step	Command	Remarks
1. Specify the upgrade file as the main startup image file for the global active MPU.	Approach 1: boot-loader file ipe-filename chassis chassis-number slot slot-number { backup \| main } Approach 2: boot-loader file boot boot-package system system-package [ feature feature-package&<1-30> ] chassis chassis-number slot slot-number { backup \| main }	Use either approach. You can also specify a backup startup image file. In approach 1, the file name must take the storage-medium:/base-filename.ipe format, for example, flash:/startup.ipe. In approach 2, all file names must take the storage-medium:/base-filename.bin format, for example, flash:/startup-boot.bin.
2. Specify the main startup images for each standby MPU in the IRF fabric.	Approach 1: boot-loader file ipe-filename chassis chassis-number slot slot-number { backup \| main } Approach 2: boot-loader file boot boot-package system system-package [ feature feature-package&<1-30> ] chassis chassis-number slot slot-number { backup \| main } Approach 3: boot-loader update chassis chassis-number slot slot-number	Use one of the approaches. For more information about the upgrade methods provided by these commands, see Fundamentals Command Reference. Skip this step if you have only one single-MPU device. In approach 3: · If the active MPU has started up with main startup images, its main startup images are synchronized to the standby MPU, regardless of whether any change has been made to this set of startup images. · If the active MPU has started up with backup startup images, its backup startup images are synchronized to the standby MPU, regardless of whether any change has been made to this set of startup images. · Startup image synchronization fails if any software image being synchronized is not available or has been corrupted. · If a patch installation or software upgrade has been performed in ISSU approach, use the install commit command to update the set of main startup images on the active MPU before software synchronization for startup image consistency between the active MPU and the standby MPU.
3. Save the running configuration.	save	This step makes sure 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, load the startup images in the file, and set the images as both current software images and startup software 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.

Upgrading MBUS daughter card software

Typically, MBUS daughter card software is automatically upgraded when the startup software images are upgraded. If the auto-upgrade fails, use the mbus update command to upgrade it.

To avoid an upgrade failure, follow these guidelines:

· In an IRF fabric, save the upgrade file on the active MPU in the same chassis as the MBUS daughter card.

· Do not perform any of the following operations during the upgrade:

¡ Perform an active and standby switchover.

¡ Execute the power-supply off command.

¡ Power off or reboot the device.

¡ Reboot or swap the active MPU or the card that hosts the MBUS daughter card.

To upgrade MBUS daughter card software, perform one of the following tasks in user view:

Task	Command
Upgrade the MBUS daughter card software on a card (in standalone mode).	mbus update [ file filename ] slot slot-number
Upgrade the MBUS daughter card software on a card (in IRF mode).	mbus update [ file filename ] chassis chassis-number slot slot-number

Upgrading CPLDs

To ensure a successful CPLD upgrade, follow these guidelines:

· To upgrade the CPU CPLD on an interface card in an IRF fabric, you must save the upgrade file on the active MPU that is in the same chassis as the interface card.

· Do not perform any of the following operations during the upgrade:

¡ Perform an active and standby switchover.

¡ Execute the power-supply off command.

¡ Power off or reboot the device.

¡ Reboot or swap the active MPU or the card that is being upgraded.

· If you are upgrading the OAM module CPLD on an MPU, you must reboot the MPU to run the new CPLD. If you are upgrading a card CPLD or CPU CPLD, the card automatically reboots.

If you install an interface card during a CPLD upgrade, the system can supply power to the card only after the upgrade is complete.

To upgrade a CPLD on an interface card or MPU:

Step	Command	Remarks
1. Set the interface card in offline state.	a. Enter system view. system-view b. Isolate the interface card. In standalone mode: board-offline slot slot-number In IRF mode: board-offline chassis chassis-number slot slot-number c. Return to user view. quit	Skip this step if you are upgrading a CPLD for an MPU. In offline state, an interface card cannot forward traffic.
2. Upgrade a CPLD on an interface card or MPU through the MBUS daughter card.	· In standalone mode: logic update [ file filename ] slot slot-number logicid logicid · In IRF mode: logic update [ file filename ] chassis chassis-number slot slot-number logicid logicid	The logicid argument specifies the CPLD type: · 0—Card (interface card or MPU) CPLD. · 1—OAM module CPLD on an MPU, or CPU CPLD on an interface card.

Step

Command

Remarks

1. Set the interface card in offline state.

a. Enter system view.
system-view

b. Isolate the interface card.
In standalone mode:
board-offline slot slot-number
In IRF mode:
board-offline chassis chassis-number slot slot-number

c. Return to user view.
quit

Skip this step if you are upgrading a CPLD for an MPU.

In offline state, an interface card cannot forward traffic.

2. Upgrade a CPLD on an interface card or MPU through the MBUS daughter card.

· In standalone mode:
logic update [ file filename ] slot slot-number logicid logicid

· In IRF mode:
logic update [ file filename ] chassis chassis-number slot slot-number logicid logicid

The logicid argument specifies the CPLD type:

· 0—Card (interface card or MPU) CPLD.

· 1—OAM module CPLD on an MPU, or CPU CPLD on an interface card.

Upgrading or repairing the power software on an interface card

Upgrade or repair the power software on an interface card if the card is not properly powered.

To ensure a successful upgrade, follow these guidelines:

· In an IRF fabric, the upgrade file must be saved on the active MPU that is in the same chassis as the card you are working with.

· Do not perform any of the following operations during the upgrade:

¡ Perform an active and standby switchover.

¡ Execute the power-supply off command.

¡ Power off the device.

¡ Reboot or swap the active MPU or the card that is being upgraded.

· If the system instructs you to choose a card model during the upgrade, use the card model on the card panel as a reference to make the correct choice. If you fail to enter a choice within 30 seconds or fail to choose the correct model within five attempts, the upgrade fails.

When the upgrade is complete, the card automatically reboots to run the new software.

If you install a card during a power software upgrade, the system can supply power to the card only after the upgrade is complete.

To upgrade the power software on an interface card:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Set the interface card in offline state.	· In standalone mode: board-offline slot slot-number · In IRF mode: board-offline chassis chassis-number slot slot-number	In offline state, a card cannot forward traffic.
3. Return to to user view.	quit	N/A
4. Upgrade the power software on the isolated card.	· In standalone mode: power-logic update [ file filename ] slot slot-id · In IRF mode: power-logic update [ file filename ] chassis chassis-id slot slot-id	The command is not available for MPUs.

Upgrading the power monitor software

Typically, the power monitor software is automatically upgraded when the startup software images are upgraded. If the auto-upgrade fails, use the pmu update command to upgrade it.

This task does no apply to the PSE9000 power module. To identify the power module model, use the display power-supply command (see "Device management commands").

To avoid power monitor software upgrading failures, follow these guidelines:

· The upgrade file must be saved on the switch that holds the power monitoring module to be upgraded.

· In an IRF fabric, save the upgrade file on the active MPU that is in the same chassis as the power monitoring module.

· Do not perform any of the following operations during the upgrade:

¡ Perform an active and standby switchover.

¡ Execute the power-supply off command.

¡ Power off the device.

¡ Reboot or swap the active MPU.

To upgrade the software of a power monitoring module, perform one of the following tasks in user view:

Task	Command
Upgrade the power monitor software (in standalone mode).	pmu update [ file filename ] pmu-id
Upgrade the power monitor software (in IRF mode).	pmu update [ file filename ] chassis chassis-number pmu-id

Upgrading fan monitor software

To avoid fan monitor software upgrading failures, follow these guidelines:

· On the S12508 or S12518 switch, this task is available only for fan trays that use software version 103 and CPLD 002 (or above). For an S12504 switch, this task is available only for fan trays that use software version 202 (or above). To display this information, use the display fan verbose command.

· In IRF mode, save the upgrade file on the active MPU that is in the same chassis as the fan tray you are upgrading.

· Do not perform any of the following operations during the upgrade:

¡ Remove the fan tray before the system displays the upgrade completed message.

¡ Perform an active and standby switchover.

¡ Execute the power-supply off command.

¡ Power off the device.

¡ Reboot or swap the active MPU.

· On the S12508 or S12518 switch, after the fan update command is executed for one fan tray, you must remove and reinstall the fan tray before upgrading the other fan tray.

To upgrade the fan monitor software of a fan tray, perform the following task in user view:

Step	Command	Remarks
1. Upgrade the fan monitor software for the specified fan tray.	· In standalone mode: fan update [ file filename ] tray { top \| bottom } · In IRF mode: fan update [ file filename ] chassis chassis-number tray { top \| bottom }	The S12504 switch has only one fan tray. It does not support the bottom keyword.
2. Remove and reinstall the fan tray.	N/A	If the device is an S12508 or S12518 switch, perform this step. Do not perform this task before the system displays the upgrade completed message.

Step

Command

Remarks

1. Upgrade the fan monitor software for the specified fan tray.

· In standalone mode:

fan update [ file filename ] tray { top | bottom }

· In IRF mode:

fan update [ file filename ] chassis chassis-number tray { top | bottom }

The S12504 switch has only one fan tray. It does not support the bottom keyword.

2. Remove and reinstall the fan tray.

N/A

If the device is an S12508 or S12518 switch, perform this step.

Do not perform this task before the system displays the upgrade completed message.

NOTE:

While a fan tray is being upgraded, you cannot configure the fan tray or the power modules.

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.

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 copies the current software images of the active MPU, specifies them as startup software images, and reboots with these images.

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.

Displaying and maintaining software image settings

Execute display commands in any view.

Task	Command
Display current software images and startup software images (in standalone mode).	display boot-loader [ slot slot-number ]
Display current software images and startup software images (in IRF mode).	display boot-loader [ chassis chassis-number [ slot slot-number ] ]

Non-ISSU software upgrade example (for standalone mode)

Network requirements

The device has two MPUs: one active MPU in slot 0 and one standby MPU in slot 1.

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

Figure 3 Network diagram

Configuration procedure

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

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

# Display information about the current software images.

<Sysname> display version

NOTE:

In the example, the image file is saved to the root directory of Flash memory.

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

<Sysname> tftp 2.2.2.2 get startup-r7122.ipe

# (Optional.) Back up the image file to startup-r7122-backup.ipe. Skip this step if the Flash memory does not have sufficient space.

<Sysname> copy startup-r7122.ipe startup-r7122-backup.ipe

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

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

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

# Specify startup-r7122-backup.ipe as the backup startup image file for both MPUs.

<Sysname> boot-loader file flash:/startup-r7122-backup.ipe slot 0 backup

<Sysname> boot-loader file flash:/startup-r7122-backup.ipe 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 (for IRF mode)

Network requirements

Use the file startup-r7122.ipe to upgrade software images for the IRF fabric in Figure 4.

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 4 Network diagram

Configuration procedure

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

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

# Display information about the current software images.

<Sysname> display version

NOTE:

In this example, the image file is saved to the root directory of Flash memory.

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

<Sysname> tftp 2.2.2.2 get startup-r7122.ipe

# (Optional.) Back up the image file to startup-r7122-backup.ipe on the global active MPU. Skip this step if the Flash memory does not have sufficient space.

<Sysname> copy startup-r7122.ipe startup-r7122-backup.ipe

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

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

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

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

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

# Specify startup-r7122-backup.ipe as the backup startup image file for all MPUs.

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

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

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

<Sysname> boot-loader file flash:/startup-r7122-backup.ipe 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

01-Fundamentals Configuration Guide

Non-ISSU software upgrade example (for standalone mode)

Non-ISSU software upgrade example (for IRF mode)

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program

Global Learning

Partner Sales Resources

Service Business

News & Events

Contact Us