Login
- Table of Contents
-
- 01-Fundamentals Configuration Guide
- 00-Preface
- 01-CLI configuration
- 02-RBAC configuration
- 03-Login management configuration
- 04-FTP and TFTP configuration
- 05-File system management configuration
- 06-Configuration file management configuration
- 07-Software upgrade configuration
- 08-Automatic configuration
- 09-Preprovisioning feature configuration
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 07-Software upgrade configuration | 119.05 KB |
Contents
Digitally signed software images
Restrictions and guidelines: Software upgrade
Upgrading device software by using the boot loader method
Software upgrade tasks at a glance
Preloading the BootWare image to BootWare
Specifying startup images and completing the upgrade
Enabling automatic software synchronization from the active MPU to the standby MPU
Synchronizing startup images from the active MPU to the standby MPU
Installing or uninstalling features and patches
About installing or uninstalling features and patches
Installing or upgrading features
Uninstalling features or patches
Verifying and maintaining software images
Displaying software images and version information
Displaying and clearing startup software image upgrade records
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 and non-incremental.
- 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 exist 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 |
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.
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, the device cannot start up.
Digitally signed software images
The software images for the device are digitally signed for authenticity and integrity verification. This mechanism ensures that the software installed on the system is from a trusted source and has not been tampered with in the transfer, storage, or installation phase.
The system performs software digital signature verification for authenticity and integrity in the following situations:
· Before the system loads a software image during startup. If the digital signature verification fails, the system will not load the image and you will receive a digital signature verification failure message.
· When you specify a software image to upgrade the device from the BootWare menu. If the digital signature verification fails, the system will not set the image for upgrade and you will receive a digital signature verification failure message.
· Before the system loads a BootWare image to the Normal area of BootWare. If the digital signature verification fails, the system will not load the image and you will receive a digital signature verification failure message.
· When you specify a software image as a startup image through the boot loader. The system will verify the digital signature of the image before it updates the startup image list with the specified image. If the digital signature verification fails, the system will not update the startup image list and you will receive a digital signature verification failure message.
· Before the system activates a feature or patch image. If the digital signature verification fails, the system will not activate the image and you will receive a digital signature verification failure message.
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
Restrictions and guidelines
When you upgrade software, you do not need to upgrade interface cards separately. The software images for interface cards are integrated in the software images for MPUs. The interface cards are upgraded automatically when you upgrade MPUs.
Software upgrade tasks at a glance
To upgrade software, perform one of the following tasks:
· Upgrading the device
· Synchronizing startup images from the active MPU to standby MPUs
Upgrading the device
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
Synchronizing startup images from the active MPU to standby MPUs
· Enabling automatic software synchronization from the active MPU to the standby MPU
This feature enables a newly added MPU to synchronize the software images running on the active MPU. By default, this feature is enabled.
· Synchronizing startup images from the active MPU to the standby MPU
Perform this task when the startup images on the standby MPU are not the same version as those on the active MPU.
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 MPUs 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. Enter system view.
system-view
2. (Optional.) Enable BootWare image validity check.
bootrom-update security-check enable
By default, this feature is enabled.
This feature examines BootWare images for file type errors, file corruption, and hardware incompatibility. As a best practice, enable it to ensure a successful upgrade.
3. Return to user view.
quit
4. (Optional.) Back up the image to the Backup area of BootWare:
bootrom backup slot slot-number-list
Use this command to back up the BootWare image for a future version rollback or image restoration.
5. Load the upgrade BootWare image to the Normal area of BootWare.
bootrom update file file slot slot-number-list
Specify the downloaded software image file for the file argument.
|
|
NOTE: The system verifies the signature of a BootWare image before it loads that image to the Normal area of BootWare. If the digital signature verification fails, the system will not load the image and you will receive a digital signature verification failure message. |
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 MPUs.
¡ Use an .ipe file:
boot-loader file ipe-filename all { backup | main }
¡ Use .bin files:
boot-loader file boot filename system filename [ feature filename&<1-30> ] { all | slot slot-number } { backup | main }
The command copies the specified startup images to the root directory of the default file system on each MPU.
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.
|
|
NOTE: The system will verify the digital signature of the specified images before it updates the startup image list with the specified images. If the digital signature verification fails, the system will not update the startup image list and you will receive a digital signature verification failure message. |
2. Save the running configuration.
save
This step ensures that any configuration you have made can survive a reboot.
3. Reboot the device.
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.
Enabling automatic software synchronization from the active MPU to the standby MPU
About this task
This feature ensures version consistency between standby MPUs and the active MPU.
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.
Restrictions and guidelines
For a successful synchronization in a multiuser environment, make sure no other users reboot or swap MPUs during the synchronization process.
To track the synchronization process, configure the information center to output synchronization status logs to configuration terminals. For more information, see Network Management and Monitoring Configuration Guide.
This feature is related to the startup software version check feature for the standby MPU.
· Enabling both features ensures the standby MPU always runs the same software images as the active MPU. However, the standby MPU might fail to synchronize the software images of the active MPU if their software images have critical differences.
· If you disable the startup software version check feature, the standby MPU can start up with a different software version than the active MPU. However, the device might not be able to operate correctly.
· If you enable the startup software version check feature but disable automatic software synchronization, the standby MPU cannot start up in the case of a version inconsistency.
Procedure
1. Enter system view.
system-view
2. Enable startup software version check for the standby MPU.
undo version check ignore
By default, startup software version check is enabled.
3. Enable automatic software synchronization for the standby MPU.
version auto-update enable
By default, automatic software synchronization is enabled.
Synchronizing startup images from the active MPU to the standby MPU
About this task
Perform this task when the startup images on the standby MPU are not the same version as those on the active MPU.
This task synchronizes startup images that are running on the active MPU to the standby MPU. If any of the startup images does not exist or is invalid, the synchronization fails.
The startup images synchronized to the standby MPU are set as main startup images, regardless of whether the source startup images are main or backup.
Procedure
Perform the following steps in user view:
1. Synchronize startup images from the active MPU to the standby MPU.
boot-loader update { all | slot slot-number }
The command execution results are the same, regardless of whether you specify the all keyword or the slot slot-number option.
2. Reboot the standby MPU.
reboot slot slot-number [ force ]
Installing or uninstalling features and patches
About installing or uninstalling features and patches
You can install a new feature or patch image, or upgrade an existing feature image.
Restrictions and guidelines
To ensure a successful image installation or upgrade, do not reboot the device or perform a master/subordinate switchover during the image installation or upgrade.
After installing a feature image, you must log in to the device again to use the commands provided in the image.
Prerequisites
Use FTP or TFTP commands to transfer the image file to the default file system on the master device. You do not need to transfer or copy the image file to subordinate member devices. The system will automatically copy the image file to the subordinate members when you activate the images on them. For more information about FTP and TFTP, see "Configuring FTP" and "Configuring TFTP."
Installing or upgrading features
1. Activate features in the specified files.
install activate feature filename&<1-30> slot slot-number
|
|
NOTE: The system verifies the signature of a feature image before it activates that image. If the digital signature verification fails, the system will not load the image and you will receive a digital signature verification failure message. |
2. Commit the software change.
install commit
For the image changes to take effect after a reboot, you must perform a commit operation.
Installing patches
1. Activate patches in a file.
install activate patch filename { all | slot slot-number }
You can specify only one patch image file for this command at a time. However, you can execute this command multiple times to install multiple patch image files.
The install activate patch filename all command installs the specified patch images on all hardware and the images can survive a reboot. You do not need to execute the install commit command for the installation.
2. Commit the software change.
install commit
Images run in memory immediately after they are activated. However, only patch images activated by using the install activate patch filename all command can survive a reboot. For other images to take effect after a reboot, you must execute this command to commit the software change.
Uninstalling features or patches
Restrictions and guidelines
After uninstalling a feature image, you must log in to the device again for the commands in the image to be removed.
Procedure
1. Deactivate the features or patches installed from an image file.
install deactivate feature filename&<1-30> slot slot-number
install deactivate patch filename { all | slot slot-number }
You can specify only one patch image file for this command at a time. However, you can execute this command multiple times to deactivate multiple patch image files.
Images deactivated by using the install deactivate patch filename all command do not run after a reboot. To prevent other deactivated images from running after a reboot, you must commit the software change by using the install commit command.
2. Commit the software change.
install commit
This step removes the image file from the startup image list but does not delete the image file from the default file system.
The device will not load features and patches from the image files at startup.
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.
bootrom restore slot slot-number-list
2. Reboot the device.
reboot
At startup, the system runs the new BootWare image to complete the restoration.
Verifying and maintaining software images
Displaying software images and version information
Perform display tasks in any view.
· Display current software images and startup software images.
display boot-loader [ slot slot-number ]
· Display active software images.
display install active [ slot slot-number ] [ verbose ]
· Display main startup software images.
display install committed [ slot slot-number ] [ verbose ]
· Display inactive software images in the root directories of file systems.
display install inactive [ slot slot-number ] [ verbose ]
· Display system version information.
display version
Displaying and clearing startup software image upgrade records
To display startup software image upgrade records, execute the following command in any view:
display version-update-record
To clear startup software image upgrade records, execute the following command in system view:
reset version-update-record
Software upgrade examples
Example: Upgrading device software
Network configuration
As shown in Figure 1, 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.
Prerequisites
By default, interfaces on the device are disabled (in ADM or Administratively Down state). To have an interface operate, you must use the undo shutdown command to enable that interface.
Configure IP addresses and routes. Make sure the device and the TFTP server can reach each other.
Procedure
# 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 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
# Use TFTP to download the startup-a2105.ipe image file 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
# 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
