01-Fundamentals Configuration Guide

HomeSupportResource CenterSwitchesH3C S7500X Switch SeriesH3C S7500X Switch SeriesTechnical DocumentsConfigureConfiguration GuidesH3C S7500X Switch Series Configuration Guides-Release758X-6W10001-Fundamentals Configuration Guide
07-Software upgrade configuration
Title Size Download
07-Software upgrade configuration 137.61 KB

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

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 released for fixing bugs without rebooting the device. A patch image does not add new features or functions.

Patch images have the following types:

-       Incremental patch images—A new incremental patch image can cover all, part, or none of the functions provided by an old incremental patch image. A new incremental patch image can coexist with an old incremental 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 of the boot, system, and feature images 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 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.

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 file naming conventions

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

 

Upgrade methods

Upgrading method

Software types

Remarks

Upgrading from the CLI without using ISSU

·          BootWare image

·          Comware images (excluding incremental 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 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.

IMPORTANT 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

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.

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

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.

(Required.) Specifying startup images and completing the upgrade (in standalone mode)

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

N/A

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

 

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.

 

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

·          Use .bin files for upgrade:
boot-loader file boot
filename system filename [ feature filename&<1-30> ] [ patch
filename&<1-16> ] { 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 [ patch
filename&<1-16> ] { all | slot slot-number } { backup | main }

¡  Use .bin files for upgrade:
boot-loader file boot
filename system filename [ feature filename&<1-30> ] [ patch
filename&<1-16> ] { 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.

 

Upgrading PEXs from the parent fabric (IRF 3.1)

About PEX upgrade

Perform this task to upgrade PEXs from the parent fabric in an IRF 3.1 system. You can also log in to a PEX through its console port and upgrade the PEX. 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 a file transfer service (for example, 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.

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 pex_images folder in the root directory of a file system on the parent fabric.

You can transfer the file only on the default MDC.

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

Procedure

Perform this task in user view.

 

Task

Command

Upgrade PEXs from the parent fabric.

boot-loader pex file ipe ipe-filename transfer-service ftp { all | chassis chassis-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.

Installing patches for PEXs from the parent fabric

Preprequisites

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

Perform this task in user view.

 

Task

Command

Install patches.

install activate pex patch filename { all | chassis chassis-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

Perform this task in user view.

 

Task

Command

Uninstall patches.

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

 

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

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.

 

Displaying and maintaining software image settings

Execute display commands in any 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 ] ]

 

Software upgrade examples

Software upgrade example (in standalone mode)

Network requirements

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

Software upgrade example (in IRF mode)

Network requirements

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