07-Software upgrade commands
Chapters Download (60.71 KB)
As a best practice, store the startup images in the factory default file system. If you store the startup images in a hot swappable storage medium, do not remove the hot swappable storage medium during the startup process.
Use boot-loader file to specify startup image files.
Syntax
boot-loader file boot filename system filename [ feature filename&<1-30> ] { all | chassis chassis-number slot slot-number } { backup | main }
boot-loader file ipe-filename { all | chassis chassis-number slot slot-number } { backup | main }
Views
User view
Predefined user roles
network-admin
Parameters
boot: Specifies a boot image file.
system: Specifies a system image file.
feature: Specifies a space-separated list of up to 30 feature image files.
filename: Specifies a .bin file in the filesystemname/filename.bin format. The file must be stored in the root directory of a file system on the device. Excluding the file system location section (if any), the value string can have a maximum of 63 characters. For more information about specifying a file, see file system management in Fundamentals Configuration Guide.
ipe-filename: Specifies an .ipe image package file in the filesystemname/filename.ipe format. The file must be stored in the root directory of a file system on the device. Excluding the file system location section (if any), the value string can have a maximum of 63 characters. For more information about specifying a file, see file system management in Fundamentals Configuration Guide.
all: Specifies all hardware components to which the specified images apply.
chassis chassis-number slot slot-number: Specifies an MPU or security card in the IRF fabric. The chassis-number argument represents the IRF member ID of the device that holds the MPU or security card. The slot-number argument represents the slot number of the MPU or security card.
backup: Specifies the files as backup startup image files. Backup images are used only when main images are not available.
main: Specifies the files as main startup image files. The device always first attempts to start up with main startup files.
Usage guidelines
The boot-loader file command overwrites the entire startup image list. To add new startup feature images, specify all feature image files in the old startup image list, including feature image files. The new startup image list will contain only the feature image files that are specified in the command.
Before you specify startup image files, register and activate a license for each upgrade image that requires a license. If a license-based software image lacks a license, the command execution result is as follows:
· If .bin files are specified, the command cannot be executed.
· If an .ipe file is specified, the command sets all images as startup images except for the image that does not have a license.
For more information about licensing, see Fundamentals Configuration Guide.
To load the specified startup software images, you must reboot the system.
If the upgrade images are not found in the file system on the slot specified to upgrade, the system automatically copies the images to that file system. The destination directory is the root directory of the file system. If the destination root directory already contains a startup image with the same name as an upgrade image, you must choose whether to overwrite the image.
Examples
# Specify flash:/all.ipe as the main startup image file.
<Sysname> boot-loader file flash:/all.ipe all main
Verifying the file flash:/all.ipe on chassis 1 slot 1........................Done.
F5080lpu images in IPE:
Boot.bin
System.bin
This command will set the main startup software images. Please do not reboot any MPU during the upgrade. Continue? [Y/N]:
Add images to chassis 1 slot 1.
File flash:/Boot.bin already exists on chassis 1 slot 1.
File flash:/System.bin already exists on chassis 1 slot 1.
Overwrite the existing files? [Y/N]:
Decompressing file Boot.bin to flash:/Boot.bin........................Done.
Decompressing file System.bin to flash:/System.bin...............................Done.
Verifying the file flash:/boot.bin on chassis 1 slot 1...Done.
Verifying the file flash:/system.bin on chassis 1 slot 1.............Done.
File sda0:/Boot.bin already exists on chassis 1 slot 2.
Do you want to overwrite the file?
Y: Overwrite the file.
N: Not overwrite the file.
A: From now on, overwrite or not overwrite without prompt.
Please make a choice. [Y/N/A]:y
Loading..................................Done.
File sda0:/System.bin already exists on chassis 1 slot 2.
Do you want to overwrite the file?
Y: Overwrite the file.
N: Not overwrite the file.
A: From now on, overwrite or not overwrite without prompt.
Please make a choice. [Y/N/A]:y
Loading................................Done.
Verifying the file sda0:/Boot.bin on chassis 1 slot 2...Done.
Verifying the file sda0:/System.bin on chassis 1 slot 2............Done.
The images that have passed all examinations will be used as the main startup software images at the next reboot on chassis 1 slot 2.
Specify the startup software image files for F5080lpu to load from the parent device? [Y/N]:y
The images that have passed all examinations will be used as the load software image files for F5080lpu.
Decompression completed.
Do you want to delete flash:/all.ipe now? [Y/N]:
Related commands
display boot-loader
Use boot-loader update to synchronize startup images.
Syntax
boot-loader update { all | chassis chassis-number slot slot-number }
Views
User view
Predefined user roles
network-admin
Parameters
all: Synchronizes startup images from the global active MPU to all standby MPUs.
chassis chassis-number slot slot-number: Specifies a standby MPU. The chassis-number argument represents the IRF member ID of the device that holds the MPU. The slot-number argument represents the slot number of the MPU.
Usage guidelines
You can use this command to synchronize startup images after adding new MPUs.
If any of the startup software images require a license, register and activate a license for the image on the new MPU before executing this command. Use the display license feature command to verify the licensing state of software images.
The images used for synchronization are in the main or backup startup software images list instead of the current software images list (see the display boot-loader command).
· 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.
The startup images synchronized to a standby MPU are set as main startup images, regardless of whether the source startup images are main or backup.
If a patch installation or ISSU has been performed, use the install commit command to update the main startup images on the global active MPU before software synchronization. This command ensures startup image consistency between the global active MPU and standby MPUs.
Startup image synchronization fails if any software image being synchronized is not available or is corrupted.
Examples
# Synchronize startup images from the active MPU all standby MPUs.
<Sysname> boot-loader update all
This command will update all the standby MPU. Please do not reboot any MPU during the upgrade. Continue? [Y/N]:y
Updating. Please wait...
Verifying the file flash:/boot.bin on slot 1....Done.
Verifying the file flash:/system.bin on slot 1......................................Done.
Successfully updated the startup software images of all the standby MPU.
display boot-loader
install commit
Use bootrom backup to back up the BootWare image in the Normal area to the Backup area on a BootWare.
Syntax
bootrom backup chassis chassis-number slot slot-number-list [ all | part ]
Views
User view
Predefined user roles
network-admin
Parameters
chassis chassis-number: Specifies an IRF member device by its member ID.
slot slot-number-list: Specifies a space-separated list of up to seven slot number items. An item specifies a card by its slot number or a range of cards in the form of start-slot-number to end-slot-number on the specified IRF member device. The end slot number must be equal to or greater than the start slot number.
all: Backs up the entire BootWare image, including the basic segment and the extended segment. If you do not specify the all or part keyword, this command backs up the entire BootWare image.
part: Backs up the extended BootWare image section.
Usage guidelines
A BootWare is divided into a Normal area and a Backup area. The BootWare image is stored in the Normal area and backed up to the Backup area. At startup, the system reads the BootWare image automatically from the Normal area. If the image is inaccessible, the system reads the BootWare image from the Backup area.
If the BootWare image in the Normal area is corrupted or requires a version rollback, use the bootrom restore command to copy the BootWare image in the Backup area to the Normal area.
Examples
# Back up the entire BootWare image from the Normal area to the Backup area.
<Sysname> bootrom backup chassis 1 slot 1
Now backing up the Boot ROM, please wait...
......Done.
Related commands
bootrom restore
Use bootrom read to back up the BootWare image in the Normal area of a BootWare to the default file system.
Syntax
bootrom read chassis chassis-number slot slot-number-list [ all | part ]
Views
User view
Predefined user roles
network-admin
Parameters
chassis chassis-number: Specifies an IRF member device by its member ID.
slot slot-number-list: Specifies a space-separated list of up to seven slot number items. An item specifies a card by its slot number or a range of cards in the form of start-slot-number to end-slot-number on the specified IRF member device. The end slot number must be equal to or greater than the start slot number.
all: Backs up the entire BootWare image, including the basic segment and the extended segment. If you do not specify the all or part keyword, this command backs up the entire BootWare image.
part: Backs up the extended BootWare image section.
Usage guidelines
For each BootWare image you are backing up, this command creates two files (basicbtm.bin and extendbtm.bin) in the flash memory for the basic segment and the extended segment. If the BootWare image in the Normal area of a BootWare is corrupted or requires a version rollback, use the bootrom update command to read the two backup files from the flash memory to the BootWare.
Examples
# Back up the BootWare image from the Normal area of BootWare to the flash memory.
<Sysname> bootrom read chassis 1 slot 1
Now reading the Boot ROM, please wait...
.........Done.
Related commands
bootrom update
Use bootrom restore to replace the BootWare image in the Normal area with the BootWare image in the Backup area for image restoration or version rollback.
Syntax
bootrom restore chassis chassis-number slot slot-number-list [ all | part ]
Views
User view
Predefined user roles
network-admin
Parameters
chassis chassis-number: Specifies an IRF member device by its member ID.
slot slot-number-list: Specifies a space-separated list of up to seven slot number items. An item specifies a card by its slot number or a range of cards in the form of start-slot-number to end-slot-number on the specified IRF member device. The end slot number must be equal to or greater than the start slot number.
all: Restores the entire BootWare image, including the basic segment and the extended segment. If you do not specify the all or part keyword, this command restores the entire BootWare image.
part: Restores the extended BootWare image section.
Examples
# Restore the entire BootWare image.
<Sysname> bootrom restore chassis 1 slot 1
This command will restore the Boot ROM file on the specified board(s), Continue? [Y/N]:y
Now restoring the Boot ROM, please wait.........Done.
Related commands
bootrom backup
Use bootrom update to load the BootWare image from a file system to the Normal BootWare area.
Syntax
bootrom update file file chassis chassis-number slot slot-number-list [ all | part ]
Views
User view
Predefined user roles
network-admin
Parameters
file file: Specifies the file that contains the BootWare image. The file argument represents the file name, a string of 1 to 63 characters.
chassis chassis-number: Specifies an IRF member device by its member ID.
slot slot-number-list: Specifies a space-separated list of up to seven slot number items. An item specifies a card by its slot number or a range of cards in the form of start-slot-number to end-slot-number on the specified IRF member device. The end slot number must be equal to or greater than the start slot number.
all: Loads the entire BootWare image, including the basic segment and the extended segment. If you do not specify the all or part keyword, this command restores the entire BootWare image.
part: Loads the extended BootWare image section.
Usage guidelines
BootWare images are contained in the .bin Comware boot image file or .btw file. You can specify a Comware boot image file in this command to upgrade the BootWares in the system before you upgrade the Comware images. If you do not upgrade BootWares before upgrading Comware images, the system automatically upgrades BootWares as necessary when loading Comware images.
The new BootWare images take effect after you reboot the card.
Examples
# Use the file a.bin in the root directory of the flash memory to upgrade the BootWare image.
<Sysname> bootrom update file flash:/a.bin chassis 1 slot 1
This command will update the Boot ROM file on the specified board(s), Continue? [Y/N]:y
Now updating the Boot ROM, please wait................Done.
Related commands
boot-loader file
Use bootrom-update security-check enable to enable BootWare image validity check.
Use undo bootrom-update security-check enable to disable BootWare image validity check.
Syntax
bootrom-update security-check enable
undo bootrom-update security-check enable
Default
BootWare image validity check is enabled.
Views
System view
Predefined user roles
network-admin
Usage guidelines
Before a BootWare image upgrade starts, this feature examines the upgrade BootWare image for file validity and incompatibility with hardware. If the BootWare image passes the check, the upgrade process starts. If the check fails, the system does not perform the upgrade.
Examples
# Enable BootWare image validity check.
<Sysname> system-view
[Sysname] bootrom-update security-check enable
Use display boot-loader to display current software images and startup software images.
Syntax
display boot-loader [ chassis chassis-number [ slot slot-number ] ]
Views
Any view
Predefined user roles
network-admin
network-operator
Parameters
chassis chassis-number [ slot slot-number ]: Specifies an IRF member device or an MPU in an IRF member device. The chassis-number argument represents the IRF member ID of the device. The slot-number argument represents the slot number of the MPU on the device. If you do not specify an IRF member device, this command displays the software images on each MPU in the IRF fabric. If you specify an IRF member device without specifying an MPU, this command displays the software images on each MPU on the specified member device.
Examples
# Display the current software images and startup software images.
<Sysname> display boot-loader
Software images on chassis 1 slot 1:
Current software images:
flash:/f5080mpu-cmw710-boot-E9608P03.bin
flash:/f5080mpu-cmw710-system-E9608P03.bin
Main startup software images:
flash:/f5080mpu-cmw710-boot-E9608P03.bin
flash:/f5080mpu-cmw710-system-E9608P03.bin
Backup startup software images:
None
Software images on chassis 1 slot 2:
Current software images:
sda0:/f5080lpu-cmw710-boot-e9608p03.bin
sda0:/f5080lpu-cmw710-system-e9608p03.bin
Main startup software images:
sda0:/f5080lpu-cmw710-boot-e9608p03.bin
sda0:/f5080lpu-cmw710-system-e9608p03.bin
Backup startup software images:
sda0:/F5080LPU-CMW710-BOOT-E9608P03.bin
sda0:/F5080LPU-CMW710-SYSTEM-E9608P03.bin
Table 1 Command output
|
Field |
Description |
|
Current software images |
Comware images that have been loaded. |
|
Main startup software images |
Primary Comware images for the next startup. |
|
Backup startup software images |
Backup Comware images for the next startup. |
Related commands
boot-loader file
