Login
- Table of Contents
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 07-Software upgrade configuration | 163.72 KB |
Contents
Software file naming conventions
Comware image redundancy and loading procedure
Upgrade restrictions and guidelines
Specifying startup images and completing the upgrade
Displaying and maintaining software image settings
Software upgrade example (in standalone mode)
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."
When you upgrade software, you do not need to upgrade interface cards separately.
Software types
The following software types are available:
· BootWare image—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 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 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 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.
Software file naming conventions
Software image file names use the chassis-comware version-image type-release format. This document uses boot.bin and system.bin as boot and system image file names.
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 by using the boot-loader file command |
· BootWare image · Comware images (excluding 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 software 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.
Upgrade an IRF fabric from the CLI instead of the BootWare menu, if possible. The BootWare menu method increases the service downtime. It requires that you upgrade the member devices one by one. |
This chapter only covers upgrading software from the CLI by using the boot-loader file command.
Upgrade restrictions and guidelines
The device starts up from the default file system. The default file system can be the built-in flash memory (factory default) or a CF card. To change the default file system setting, access the BootWare menu. For more information, see the release notes for the device.
As a best practice, store the startup images in the factory-default file system.
If the device is starting up from a CF card, do not remove the CF card during startup.
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. (In standalone mode.) 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."
5. (In IRF mode.) 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."
6. 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."
Upgrade task list
|
Tasks at a glance |
Remarks |
|
(Required.) Specifying startup images and completing the upgrade |
N/A |
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 device. |
· Use an .ipe file for upgrade: · Use .bin files for upgrade: |
Upgrade files must be saved in the root directory of a file system on the device. To avoid configuration failure, make sure no other users are configuring or managing the device. |
|
1. Save the running configuration. |
save |
This step ensures that any configuration you have made can survive a reboot. |
|
2. Reboot the device. |
reboot |
At startup, the MPUs load the startup images. |
|
3. (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. |
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 master device. |
· Use an .ipe file for upgrade: · Use .bin files for upgrade: |
Upgrade files must be saved in the root directory of a file system on the master 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: · Method 1 Use .bin files for upgrade: · Method 2: |
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: · If a patch installation or ISSU has been performed, use the install commit command to update the main startup images on the master device before software synchronization. The command ensures startup image consistency among IRF member devices. · The boot-loader update all 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. 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. |
|
4. Reboot the IRF fabric. |
reboot |
At startup, each device 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. |
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 ] |
Software upgrade example (in standalone mode)
Network requirements
As shown in Figure 3, use the file startup-a2105.ipe to upgrade software images for the device.
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
# 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 the device.
<Sysname> boot-loader file boot flash:/boot_backup.bin system flash:/system_backup.bin slot 0 backup
# Use TFTP to download the image file startup-a2105.ipe from the TFTP server to the root directory of the file system on the device.
<Sysname> tftp 2.2.2.2 get startup-a2105.ipe
# Specify startup-a2105.ipe as the main startup image file for the device.
<Sysname> boot-loader file flash:/startup-a2105.ipe slot 0 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 (in IRF mode)
Network requirements
As shown in Figure 4, use the file startup-a2105.ipe to upgrade software images for the IRF fabric.
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
# 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 IRF member devices.
<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 2 slot 0 backup
# Use TFTP to download the image file startup-a2105.ipe from the TFTP server to the root directory of the file system 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 both IRF member devices.
<Sysname> boot-loader file flash:/startup-a2105.ipe chassis 1 slot 0 main
<Sysname> boot-loader file flash:/startup-a2105.ipe chassis 2 slot 0 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
