01-Fundamentals Configuration Guide

HomeSupportResource CenterH3C S6800[S6860][S6861] (R27xx) & S6820 (R630x) Switch Series Configuration Guide-6W10101-Fundamentals Configuration Guide
07-Software upgrade configuration
Title Size Download
07-Software upgrade configuration 114.31 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, 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 patch image can cover all, part, or none of the functions provided by an old patch image. A new patch image can coexist with an old 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 boot, system, or feature image 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 incremental 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 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 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: Hardware compatibility with software upgrade

Because of memory limitations, S6800 switches labeled with the following product codes cannot run R27XX or later correctly:

·     LS-6800-54QF.

·     LS-6800-54QF-H1.

·     LS-6800-54QT.

·     LS-6800-54QT-H1.

Use R26XX or earlier on these switches.

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

Software upgrade tasks at a glance

To upgrade software, perform one of the following tasks:

1.     Upgrade the IRF fabric:

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

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

The S6820 and S6861 switch series do not support licenses.

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

To load the upgrade BootWare image to the Normal area of BootWare, execute the following command in user view:

bootrom update file file slot slot-number-list [ subslot subslot-number-list ] [ all | part ]

The new BootWare image takes effect at a reboot.

The S6820 S6860, and S6861 switch series do not support the subslot subslot-number-list option.

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 [ patch filename&<1-16> ] { all | slot slot-number } { backup | main }

¡     Use .bin files:

boot-loader file boot filename system filename [ feature filename&<1-30> ] [ patch filename&<1-16> ] { 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 any configuration you have made can survive a reboot.

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 startup image synchronization

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.

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 ]

Upgrading PEXs from the parent fabric (IRF3.1)

About PEX upgrade

Perform this task to upgrade PEXs from the parent fabric in an IRF 3.1 system. You can also upgrade a PEX by logging in to the PEX through its console port. Upgrading PEXs from the parent fabric has the following benefits:

·     It is easy to ensure compatibility between the startup images of PEXs and the startup images of the parent fabric.

·     You do not need to log in to PEXs.

This task makes the parent fabric perform the following operations:

1.     Enables file transfer service FTP and configures all file transfer parameters.

2.     Transfers the .ipe upgrade file to PEXs one by one.

3.     Deletes the file transfer settings and disables the file transfer service.

After the file transfer process is completed, PEXs that successfully received the .ipe file automatically reboot to complete the upgrade. PEXs that failed to receive the .ipe file do not reboot and are not upgraded.

Hardware and feature compatibility

The S6820 switch series does not support this feature.

Restrictions and guidelines

To have sufficient space to store startup image files on a PEX, use the switchto pex command to log in to the PEX and then delete unused files.

Preparing for the upgrade

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

2.     Use the release notes for the upgrade software version to identify the upgrade impact on your network and verify the following items:

¡     Versions and sizes of the upgrade software images.

¡     Compatibility of the upgrade software images with the current BootWare and Comware images.

¡     Software compatibility between the PEX and the parent fabric.

3.     Use FTP or TFTP to transfer the upgrade image file to the root directory of a file system on the parent fabric.

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

Procedure

To upgrade PEXs from the parent fabric, execute the following command in user view:

boot-loader pex file ipe ipe-filename transfer-service ftp { all | slot slot-list }

Installing and uninstalling patches for PEXs from the parent fabric (IRF 3.1)

About installing and uninstalling patches for PEXs from the parent fabric (IRF 3.1)

This task allows you to install or uninstall PEX patches from the parent fabric in an IRF 3.1 system without logging in to the PEXs.

This task makes the parent fabric perform the following operations:

1.     Enables file transfer service FTP and configures all file transfer parameters.

2.     Transfers the patch image file to PEXs one by one.

3.     Deletes the file transfer settings and disables the file transfer service after the file transfer process is completed.

Hardware compatibility with PEX patch installation and uninstallation from the parent fabric (IRF 3.1)

The S6820 switch series does not support this feature.

Installing patches for PEXs from the parent fabric

Prerequisites

To install a non-incremental patch image, first use the install deactivate pex patch command to uninstall the old patch image. To install an incremental patch image, directly install the new patch image.

Use the dir command to verify that the PEX has sufficient storage space for the upgrade images. If the storage space is not sufficient, use the switchto pex command to log in to the PEX and then delete unused files by using the delete command. For more information, see "Managing file systems."

Restrictions and guidelines

Do not install a patch image with the same name as an existing patch image. If you do so, the patch fails to be installed and the existing patch image is lost.

Installing a patch image adds it to the startup image list. You do not need to execute the install commit command or reboot the PEX.

Procedure

To install patches for PEXs, execute the following command in user view:

install activate pex patch filename { all | slot slot-list }

Uninstalling patches for PEXs from the parent fabric

Restrictions and guidelines

After patches are uninstalled, the patch image file is still in the file system of a PEX. To release the storage space, use the switchto pex command to log in to the PEX and then delete the file by using the delete command.

Procedure

To uninstall patches for PEXs, execute the following command in user view:

install deactivate pex patch filename { all | slot slot-list }

The uninstalled patch images are not deleted and are still stored in the file systems of the PEXs.

Display and maintenance commands for 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 examples

Example: Upgrading device software

Network configuration

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

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 all IRF member devices.

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

<Sysname> boot-loader file boot flash:/boot_backup.bin system flash:/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 flash:/startup-a2105.ipe slot 1 main

<Sysname> boot-loader file flash:/startup-a2105.ipe slot 2 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