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-Target configuration management configuration
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 07-Software upgrade configuration | 127.74 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
Installing or uninstalling features and patches
About installing or uninstalling features and patches
Installing or upgrading features
Uninstalling features or patches
Rolling back the running software images
Aborting a software activate or deactivate operation
Deleting inactive software images
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, 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. Patches for the boot image, system image, and feature images are released separately. These patches can be installed together or separately.
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
Software upgrade tasks at a glance
To upgrade software, perform one of the following tasks:
1. 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
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. 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. Load the upgrade BootWare image to the Normal area of BootWare.
bootrom update file file slot slot-number-list
|
|
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. |
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 the device.
¡ Use an .ipe file:
boot-loader file ipe-filename [ patch filename&<1-30> ] { all | slot slot-number } { backup | main }
¡ Use .bin files:
boot-loader file boot filename system filename [ feature filename&<1-30> ] [ patch filename&<1-30> ] { all | slot slot-number } { backup | main }
|
|
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 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.
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 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."
Decompressing an .ipe file
5. (Optional.) Identify images that are included in the .ipe file.
display install ipe-info
6. Decompress the .ipe file.
install add ipe-filename filesystem
Execute this command in user view.
Installing or upgrading features
7. (Optional.) Identify the recommended ISSU method and the possible impact of the upgrade.
install activate feature filename&<1-30> slot slot-number test
8. Activate features in the specified files.
install activate feature filename&<1-30> slot slot-number
|
|
NOTE: The software images for the device are digitally signed. The system verifies the digital signature of a feature image for authenticity and integrity before it activates it. If the digital signature verification fails, the system will not activate the image and you will receive a digital signature verification failure message. |
9. Commit the software change.
install commit
For the image changes to take effect after a reboot, you must perform a commit operation.
Installing patches
10. Activate patches in a file.
install activate patch filename { all | slot slot-number }
|
|
NOTE: The software images for the device are digitally signed. The system verifies the digital signature of a patch image for authenticity and integrity before it activates it. If the digital signature verification fails, the system will not activate the image and you will receive a digital signature verification failure message. |
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.
11. Commit the software change.
install commit
Images run in memory immediately after they are activated. 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
12. 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.
13. 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.
To prevent deactivated images from running after a reboot, you must commit the software changes by using the install commit command.
Rolling back the running software images
About software image rollback
During an incremental upgrade, the system creates a rollback point for each activate or deactivate operation of a boot, system, or feature image. The system can maintain a maximum of 50 rollback points. If this limit has been reached when a rollback point is created, the system removes the earliest rollback point. You can roll back the software to any of the rollback points.
During a reboot upgrade, the system does not create rollback points. After a reboot upgrade, you can roll back the software only to the status before any activate or deactivate operations were performed.
Restrictions and guidelines
You can perform this task only before committing software changes. A commit operation deletes all rollback points.
For an incremental upgrade rollback to take effect after a reboot, you must perform a commit operation to update the main startup image list.
Procedure
To roll back the running software images, execute the following commands in user view:
14. (Optional.) Display available rollback points.
display install rollback
15. Roll back the software.
install rollback to { point-id | original }
Aborting a software activate or deactivate operation
About aborting a software activate or deactivate operation
While the system is activating or deactivating a software image for a service upgrade or file upgrade, you can abort the activate or deactivate operation. After an operation is aborted, the system runs with the software images that it was running with before the operation.
Procedure
To abort a software activate or deactivate operation, use one of the following methods:
· Execute the install abort [ job-id ] command in user view.
· Press Ctrl+C.
Verifying software images
About software image verification
Perform this task to verify the following items:
· Integrity—Verify that the boot, system, and feature images are integral.
· Consistency—Verify that the same active images are running across the entire system.
· Software commit status—Verify that the active images are committed as needed.
Procedure
To verify software images, execute the following commands in user view:
16. Verify software images.
install verify
17. Activate or deactivate images as required.
install { activate | deactivate }
18. Commit the software changes.
install commit
Deleting inactive software images
About deleting inactive software images
After completing an ISSU, you can use this task to delete old image files permanently.
Restrictions and guidelines
This task deletes image files permanently. You cannot use the install rollback to command to revert the operation, or use the install abort command to abort the operation.
Procedure
To delete inactive software image files, execute the following command in user view:
install remove [ slot slot-number ] { filename | inactive }
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 backup software images.
display install backup [ 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 the software images included in an .ipe file.
display install ipe-info ipe-filename
· Display ongoing ISSU activate, deactivate, and rollback operations.
display install job
· Display software image file information.
display install package { filename | all } [ verbose ]
· Display rollback points.
display install rollback [ point-id ]
· Display the software image file that includes a specific component or file.
display install which { component name | file filename } [ slot slot-number ]
· 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, use the file startup-a2105.ipe to upgrade software images for the device.
Prerequisites
Configure IP addresses and routes. Make sure the device and the TFTP server can reach each other. (Details not shown.)
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.
<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
# Reboot the device to complete the upgrade.
<Sysname> reboot
# Verify that the device is running the correct software.
<Sysname> display version
Example: Upgrading the system software
Network configuration
As shown in Figure 2, upgrade the Feature1 feature image from T0001015 to T0001016. The two versions are compatible.
Procedure
# Download the .ipe file that contains the T0001016 Feature1 feature image from the TFTP server.
<Sysname> tftp 2.2.2.2 get feature1-t0001016.ipe
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 256 100 256 0 0 764 0 --:--:-- --:--:-- --:--:-- 810
Writing file...Done.
# Decompress the .ipe file.
<Sysname> install add flash:/feature1-t0001016.ipe flash:
Verifying the file flash:/feature1-t0001016.ipe on the device...Done.
Decompressing file feature1-t0001016.bin to flash:/feature1-t0001016.bin.......................Done.
# Display active software images.
<Sysname> display install active
Active packages on the device:
flash:/boot-t0001015.bin
flash:/system-t0001015.bin
flash:/feature1-t0001015.bin
# Identify the recommended ISSU method.
<Sysname> install activate feature flash:/feature1-t0001016.bin test
Verifying the file flash:/feature1-t0001016.bin on the device...Done.
Upgrade summary according to following table:
flash:/feature1-t0001016.bin
Running Version New Version
Test 0001015 Test 0001016
Upgrade Way: Service Upgrade
Influenced service according to following table on the device:
flash:/feature1-t0001016.bin
Feature1
The output shows that a service upgrade is recommended and the Feature1 module will be rebooted during the upgrade process.
# Activate the new Feature1 image to upgrade the Feature1 feature.
<Sysname> install activate feature flash:/feature1-t0001016.bin
Verifying the file flash:/feature1-t0001016.bin on the device...Done.
Upgrade summary according to following table:
flash:/feature1-t0001016.bin
Running Version New Version
Test 0001015 Test 0001016
Upgrade Way: Service Upgrade
Upgrading software images to compatible versions. Continue? [Y/N]:y
This operation might take several minutes, please wait...Done.
# Verify that the new Feature1 image has been activated.
<Sysname> display install active
Active packages on the device:
flash:/boot-t0001015.bin
flash:/system-t0001015.bin
flash:/feature1-t0001016.bin
# Commit the software changes.
<Sysname> install commit
This operation will take several minutes, please wait...........................Done.
The current software images have been saved as the startup software images.
Current software images on the device:
flash:/boot-t0001015.bin
flash:/system-t0001015.bin
flash:/feature1-t0001016.bin
