Contents

Upgrading software· 1

Overview·· 1

Software types· 1

Software file naming conventions· 2

Comware image redundancy and loading procedure· 2

System startup process· 3

Command and hardware compatibility· 3

Upgrade methods· 3

Preparing for the upgrade· 4

Upgrade task list 5

Preloading the Boot ROM image to Boot ROM·· 5

Specifying startup images and completing the upgrade· 5

IRF-incapable devices· 5

IRF-capable devices· 6

Restoring or downgrading the Boot ROM image· 7

Displaying and maintaining software image settings· 8

Software upgrade example (IRF-incapable devices) 8

Network requirements· 8

Configuration procedure· 8

Software upgrade example (IRF-capable devices) 9

Network requirements· 9

Configuration procedure· 9

Upgrading software

Overview

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. For a comparison of all software upgrade methods, see "Upgrade methods."

Software types

The following software types are available:

·     Boot ROM 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. You can use these menus to load software and the startup configuration file or manage files when the device cannot start up correctly. For easy software compatibility management, the Boot ROM image is packaged in the .bin Boot image file. The Boot ROM image is upgraded automatically when the Boot image is upgraded.

·     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, and file system management.

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

¡     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 Comware images. Comware images specified to load at the next startup are called startup Comware images.

Boot ROM image, boot image, and system image are required for the system 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 Boot ROM and startup Comware images for the device are released in an .ipe file.

Software file naming conventions

Software image file names use the chassis-comware version-image type-release format, for example, wx5510-cmw710-system-d5104.bin and wx5510-cmw710-boot-d5104.bin.

Comware image redundancy and loading procedure

You can specify one main list and one backup list of Comware images.

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 Boot ROM menu during the system startup to upgrade software.

Figure 1 Comware image loading procedure

 

System startup process

Upon power-on, the Boot ROM 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

 

Command and hardware compatibility

The WX1800H series, WX2500H series, and WX3000H series access controllers do not support the slot keyword or the slot-number argument.

Upgrade methods

Upgrading method	Software types	Remarks
Upgrading from the CLI	·     Boot ROM image ·     Comware images (excluding patches)	This method is disruptive. You must reboot the entire device to complete the upgrade.
Upgrading from the Boot ROM menu	·     Boot ROM image ·     Comware 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. Then, press Ctrl+B at prompt to access the Boot ROM menu. For more information about upgrading software from the Boot ROM menu, see the release notes for the software version.  IMPORTANT: Upgrade an IRF fabric from the CLI instead of the Boot ROM menu, if possible. The Boot ROM menu method increases the service downtime, because it requires that you upgrade the member devices one by one.

 

Preparing for the upgrade

1.     Use the display version command to verify the current Boot ROM 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 Boot ROM 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.     On an IRF-incapable or standalone device, use the dir command to verify that the device has sufficient storage space for the upgrade images. On an IRF fabric, use the dir command to verify that all IRF member devices 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.     On an IRF-incapable or standalone device, use FTP or TFTP to transfer the upgrade image file to the root directory of the file system. On an IRF fabric, use FTP or TFTP to transfer the upgrade image file to the root directory of the file system on the master device.

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

Upgrade task list

Tasks at a glance	Remarks
(Optional.) Preloading the Boot ROM image to	If a Boot ROM 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 Boot ROM automatically when it upgrades the startup Comware images. The Boot ROM image preloaded into the Boot ROM takes effect only after you reboot the device.
(Required.) Specifying startup images and completing the upgrade	Perform this task to upgrade a standalone device or an IRF fabric.
(Optional.) Restoring or downgrading the Boot ROM image	N/A

 

Preloading the Boot ROM image to Boot ROM

Perform this task in user view.

To preload the Boot ROM image to Boot ROM:

 

Step	Command	Remarks
1.     (Optional.) Back up the current Boot ROM image in the Normal area of Boot ROM.	·     Back up the image to the Backup area of Boot ROM: bootrom backup slot slot-number-list [ all | part ] ·     Back up the image to the file system: bootrom read slot slot-number-list [ all | part ]	Use either command to back up the Boot ROM image for a future version rollback or image restoration.
2.     Load the upgrade Boot ROM image to the Normal area of Boot ROM.	bootrom update file file-url slot slot-number-list [ all | part ]	Specify the downloaded software image file for the file-url argument. The new Boot ROM image takes effect at a reboot.

 

Specifying startup images and completing the upgrade

IRF-incapable devices

Perform this task in user view.

To specify startup images and complete the upgrade:

 

Step	Command	Remarks
1.     Specify main or backup startup images.	·     Use an .ipe file for upgrade: boot-loader file ipe-filename { backup | main } ·     Use .bin files for upgrade: boot-loader file boot boot-package system system-package [ feature feature-package&<1-30> ] { backup | main }	Upgrade files must be saved in the root directory of the file system. To avoid configuration failure, make sure no other users are configuring or managing the device.
2.     Save the running configuration.	save	This step ensures that any configuration you have made can survive a reboot. This step also ensures that the device loads the binary configuration file at reboot. Loading a binary configuration file is faster than loading a text configuration file. For more information about configuration file formats, see "Managing configuration files."
3.     Reboot the device.	reboot	At startup, the device reads the preloaded Boot ROM image to RAM, and loads the startup images.
4.     (Optional.) Verify the software image settings.	display boot-loader	Verify that the current software images are the same as the startup software images.

 

IRF-capable devices

Perform this task in user view.

To specify startup image files and complete the upgrade:

 

Step	Command	Remarks
1.     Specify main or backup startup images for the master device.	·     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 boot-package system system-package [ feature feature-package&<1-30> ] { all | slot slot-number } { backup | main }	Upgrade files must be saved in the root directory of the file system on an IRF member device. To avoid configuration failure, make sure no other users are configuring or managing the device.
2.     Specify main startup images for each subordinate device.	·     Method 1 Use an .ipe file for upgrade: boot-loader file ipe-filename { all | slot slot-number } { backup | main } ·     Method 2 Use .bin files for upgrade: boot-loader file boot boot-package system system-package [ feature feature-package&<1-30> ] { all | slot slot-number } { backup | main } ·     Method 3: boot-loader update { all | slot slot-number }	Skip this step if you have only one device. When you use the boot-loader update command, make sure you understand the following requirements and upgrade results: ·     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 master device started up with the main startup images. ¡     The backup image list is used if the master device started up with the backup startup images. ·     Startup image synchronization will fail if any software image being synchronized is corrupted or is not available. To avoid configuration failure, make sure no other users are configuring or managing the device.
3.     Save the running configuration.	save	This step ensures that any configuration you have made can survive a reboot. This step also ensures that the device loads the binary configuration file at reboot. Loading a binary configuration file is faster than loading a text configuration file. For more information about configuration file formats, see "Managing configuration files."
4.     Reboot the IRF fabric.	reboot	At startup, each device reads the preloaded Boot ROM image to RAM, and loads 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.

 

Restoring or downgrading the Boot ROM image

To restore or downgrade the Boot ROM image, make sure you have used the bootrom backup command or the bootrom read command to back up the image to the Backup area of Boot ROM or the file system. The bootrom read command creates two Boot ROM image files on the file system: basicbtm.bin for the basic segment and extendbtm.bin for the extended section.

Before performing a downgrade, also verify software compatibility.

Perform the following task in user view to restore or downgrade the Boot ROM image:

 

Step	Command	Remarks
1.     Replace the Boot ROM image in the Normal area of Boot ROM.	bootrom restore slot slot-number-list [ all | part ]	N/A
2.     Reboot the device.	reboot	At startup, the system runs the new Boot ROM image to complete the restoration or downgrade.

 

Displaying and maintaining software image settings

Execute display commands in any view.

 

Task	Command
Display current software images and startup software images.	display boot-loader [ slot slot-number ]

 

Software upgrade example (IRF-incapable devices)

Network requirements

As shown in Figure 3, use file startup-a2105.ipe to upgrade software images for the AC.

Figure 3 Network diagram

 

Configuration procedure

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

# Configure TFTP settings on both the AC 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.

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

# Use TFTP to download the image file startup-a2105.ipe from the TFTP server to the root directory of a file system. The flash memory is used in this example.

<Sysname> tftp 2.2.2.2 get startup-a2105.ipe

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

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

# 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

Software upgrade example (IRF-capable devices)

Network requirements

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

Figure 4 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 both the IRF fabric 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 member devices.

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

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

# Download image file startup-a2105.ipe from the TFTP server to the root directory of a file system on the master device. The CF card is used in this example.

<Sysname> tftp 2.2.2.2 get startup-a2105.ipe

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

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

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

# 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