02-Fundamentals Configuration Guide

HomeSupportConfigure & DeployConfiguration GuidesH3C Access Controllers Configuration Guides(R5426P02)-6W10402-Fundamentals Configuration Guide
07-Software upgrade configuration
Title Size Download
07-Software upgrade configuration 124.89 KB

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

¡     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—Multiple incremental patch images can coexist on the device at the same time. A new patch image can cover all, part, or none of the functions provided by an old patch image.

-     Non-incremental patch images—Only one non-incremental patch image can coexist on the device. The device uninstalls the old non-incremental patch image before installing a new non-incremental patch image. A new non-incremental patch image covers all functions provided by an old 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.

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.

Upgrading from the BootWare menu

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

For more information about upgrading software from the BootWare menu, see the release notes for the software version.

IMPORTANT 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 both the main and backup boot images do not exist or are invalid, the device cannot start up.

Restrictions: Command and hardware compatibility

The WX1800H series, WX2500H series, and WX3000H series access controllers do not support parameters or commands that are available only in IRF mode.

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

Software upgrade tasks at a glance

To upgrade software, perform the following tasks:

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

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 dir command to verify that the device 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 file systems."

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

1.     (Optional.) Back up the current BootWare image in the Normal area of BootWare.

¡     Back up the image to the Backup area of BootWare:

bootrom backup  [ all | part ]

¡     Back up the image to the default file system:

bootrom read  [ all | part ]

Use either command to back up the BootWare image for a future version rollback or image restoration.

The bootrom read command creates two BootWare image files on the default file system: basicbtm.bin for the basic segment and extendbtm.bin for the extended section.

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

bootrom update file file  [ 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.

¡     Use an .ipe file:

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

¡     Use .bin files:

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

2.     Save the running configuration.

save

This step ensures that all configuration changes can survive a reboot.

For more information about the command, see configuration file management in Fundamentals Command Reference.

3.     Reboot the device.

reboot

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

display boot-loader

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

Upgrading device software by using the boot loader method (in IRF mode)

Software upgrade tasks at a glance

To upgrade software, perform one of the following tasks:

·     Upgrade the IRF fabirc:

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

b.     Specifying startup images and completing the upgrade

·     (Optional.) Synchronizing startup images from the master device to subordinate devices

Perform this task when the startup images on subordinate devices are not the same version as those on the master device.

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

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

1.     (Optional.) Back up the current BootWare image in the Normal area of BootWare.

¡     Back up the image to the Backup area of BootWare:

bootrom backup slot slot-number-list [ all | part ]

¡     Back up the image to the default file system:

bootrom read slot slot-number-list [ all | part ]

The bootrom read command creates two BootWare image files on the default file system: basicbtm.bin for the basic segment and extendbtm.bin for the extended section.

Use either command to back up the BootWare image for a future version rollback or image restoration.

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

bootrom update file file slot slot-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 member devices.

¡     Use an .ipe file:

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

¡     Use .bin files:

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

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 all configuration changes can survive a reboot.

For more information about the command, see configuration file management in Fundamentals Command Reference.

3.     Reboot the IRF fabric.

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 master device to subordinate devices

About this task

Perform this task when the startup images on subordinate devices are not the same version as those on the master device.

This task synchronizes startup images that are running on the master device to subordinate devices. If any of the startup images does not exist or is invalid, the synchronization fails.

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

Hardware and feature compatibility

Hardware series

Model

Product code

Feature compatibility

WX1800H series

WX1804H

EWP-WX1804H-PWR-CN

No

WX2500H series

WX2508H-PWR-LTE

WX2510H

WX2510H-F

WX2540H

WX2540H-F

WX2560H

EWP-WX2508H-PWR-LTE

EWP-WX2510H-PWR

EWP-WX2510H-F-PWR

EWP-WX2540H

EWP-WX2540H-F

EWP-WX2560H

No

WX3000H series

WX3010H

WX3010H-X

WX3010H-L

WX3024H

WX3024H-L

WX3024H-F

EWP-WX3010H

EWP-WX3010H-X-PWR

EWP-WX3010H-L-PWR

EWP-WX3024H

EWP-WX3024H-L-PWR

EWP-WX3024H-F

No

WX3500H series

WX3508H

WX3510H

WX3520H

WX3520H-F

WX3540H

EWP-WX3508H

EWP-WX3510H

EWP-WX3520H

EWP-WX3520H-F

EWP-WX3540H

Yes

WX5500E series

WX5510E

WX5540E

EWP-WX5510E

EWP-WX5540E

Yes

WX5500H series

WX5540H

WX5560H

WX5580H

EWP-WX5540H

EWP-WX5560H

EWP-WX5580H

Yes

Access controller modules

LSUM1WCME0

EWPXM1WCME0

LSQM1WCMX20

LSUM1WCMX20RT

LSQM1WCMX40

LSUM1WCMX40RT

EWPXM2WCMD0F

EWPXM1MAC0F

LSUM1WCME0

EWPXM1WCME0

LSQM1WCMX20

LSUM1WCMX20RT

LSQM1WCMX40

LSUM1WCMX40RT

EWPXM2WCMD0F

EWPXM1MAC0F

Yes

Hardware series

Model

Product code

Feature compatibility

WX1800H series

WX1804H

WX1810H

WX1820H

WX1840H

EWP-WX1804H-PWR

EWP-WX1810H-PWR

EWP-WX1820H

EWP-WX1840H-GL

No

WX3800H series

WX3820H

WX3840H

EWP-WX3820H-GL

EWP-WX3840H-GL

Yes

WX5800H series

WX5860H

EWP-WX5860H-GL

Yes

Restrictions and guidelines

If an ISSU or patch installation has been performed on the master device, use the install commit command to update the set of main startup images on the master device before software synchronization. This command ensures startup image consistency between the master and subordinate devices.

Procedure

Perform the following steps in user view:

1.     Synchronize startup images from the master to subordinate devices.

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

2.     Reboot the subordinate devices.

reboot slot slot-number [ force ]

Restoring the BootWare image

About this task

Use this task to restore the BootWare image when the BootWare image in the Normal area is corrupted or a version rollback is required.

Restrictions and guidelines

Make sure you have used the bootrom backup command to back up the image to the BootWare Backup area.

Procedure

Perform the following steps in user view:

1.     Restore the BootWare image in the Normal area of BootWare.

In standalone mode:

bootrom restore [ all | part ]

In IRF mode:

bootrom restore slot slot-number-list[ all | part ]

2.     Reboot the device.

reboot

At startup, the system runs the new BootWare image to complete the restoration.

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

In IRF mode:

display boot-loader [ slot slot-number ]

Software upgrade examples

Example: Upgrading device software (IRF 3 incapable)

Network configuration

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

Figure 1 Network diagram

 

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. If the flash memory has insufficient space, you can skip this step.

<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. Skip this step if you have not backed up the current software images.

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

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

<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

Software images on the device:

Current software images:

  flash:/boot.bin

  flash:/system.bin

Main startup software images:

  flash:/boot.bin

  flash:/system.bin

Backup startup software images:

  flash:/boot_backup.bin

  flash:/system_backup.bin

# Reboot the AC to complete the upgrade.

<Sysname> reboot

Verifying the configuration

# Verify that the AC is running the correct software.

<Sysname> display version

Example: Upgrading device software (IRF 3 capable)

Network configuration

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

Figure 2 Network diagram

 

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. If the CFcard has insufficient space, you can skip this step.

<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 IRF member devices. Skip this step if you have not backed up the current software images.

<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

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

<Sysname> tftp 2.2.2.2 get startup-a2105.ipe

# Specify startup-a2105.ipe as the main startup image file for all IRF 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

Verifying the configuration

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

<Sysname> display version

 

  • Cloud & AI
  • InterConnect
  • Intelligent Computing
  • Security
  • SMB Products
  • Intelligent Terminal Products
  • Product Support Services
  • Technical Service Solutions
All Services
  • Resource Center
  • Policy
  • Online Help
All Support
  • Become a Partner
  • Partner Resources
  • Partner Business Management
All Partners
  • Profile
  • News & Events
  • Online Exhibition Center
  • Contact Us
All About Us
新华三官网