Contents

Software upgrade commands· 1

boot-loader file· 1

boot-loader update· 2

display boot-loader 3

display cpld version· 4

display update cpld status· 5

firmware update· 6

update cpld· 7

 

Software upgrade commands

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.

boot-loader file

Use boot-loader file to specify startup image files.

Syntax

boot-loader file boot filename system filename [ feature filename&<1-30> ] [ patch filename&<1-30> ] { all | chassis chassis-number slot slot-number } { backup | main }

boot-loader file ipe-filename [ patch filename&<1-30> ] { 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.

patch: Specifies a space-separated list of up to 30 incremental patch image files or 16 non-incremental patch image files. Because the boot, system, and feature images each can have one non-incremental patch image file, you can specify a maximum of 16 non-incremental patch 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 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 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 cluster. The chassis-number argument represents the cluster 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.

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:/boot.bin and flash:/system.bin as the main startup boot and system image files.

<Sysname> boot-loader file boot flash:/boot.bin system flash:/system.bin all main

This command will set the main startup software images. Continue? [Y/N]:y

Verifying the file flash:/boot.bin on chassis 1 slot 8.........Done.

Verifying the file flash:/system.bin on chassis 1 slot 8..................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 8.

Related commands

display boot-loader

boot-loader update

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

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 to a slot.

<Sysname> boot-loader update chassis 1 slot 8

This command will update all the standby MPU. Continue? [Y/N]:y

Updating. Please wait...

Verifying the file flash:/boot.bin on chassis 1 slot 8.........Done.

Verifying the file flash:/system.bin on chassis 1 slot 8....................Done.

Successfully updated the startup software images of chassis 1 slot 8.

Related commands

display boot-loader

install commit

display boot-loader

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 a cluster member device or an MPU in a cluster member device. The chassis-number argument represents the cluster member ID of the device. The slot-number argument represents the slot number of the MPU on the device. If you do not specify a cluster member device, this command displays the software images on each MPU in the cluster. If you specify a cluster 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 8:

Current software images:

  flash:/CR19000-CMW710-BOOT-A130137-MPUC.bin

  flash:/CR19000-CMW710-SYSTEM-A130137-MPUC.bin

Main startup software images:

  flash:/CR19000-CMW710-BOOT-A130137-MPUC.bin

  flash:/CR19000-CMW710-SYSTEM-A130137-MPUC.bin

Backup startup software images:

  None

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

display cpld version

Use display cpld version to display CPLD version information.

Syntax

display cpld version [ chassis chassis-number [ slot slot-number ] ]

Views

User view

Predefined user roles

network-admin

Parameters

chassis chassis-number: Specifies a cluster member by its chassis number. If you do not specify a cluster member, this command displays CPLD version information for all cluster members.

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command displays CPLD version information for all cards on the device.

Usage guidelines

This command displays version information about running CPLDs and helps you determine whether the CPLDs require an update.

Examples

# Display version information about all CPLDs.

<Sysname> display cpld version

Location     RunningVersion  FileVersion  VersionComparison  FileName

--------------------------------------------------------------------------------

1/0/0/1      3.0               3.0            Same                 CRAMPU16E02003.vme

1/0/0/2      3.0               3.0            Same                 CRAMPU16E03003.vme

1/0/0/3      3.0               3.0            Same                 CRAMPU16E04003.vme

1/5/0/1      3.0               3.0            Same                 CRACQ12HM01003.vme

1/5/0/2      2.0               2.0            Same                 CRALPUSP01002.vme

1/5/0/3      129.0             1.0            Earlier             CRALPUSP02001.vme

1/5/0/4      255.0             1.0            Earlier             CRALPUSP03001.vme

1/6/0/1      4.0               3.0            Later                CRACQ12HM01003.vme

1/6/0/2      2.0               3.0            Earlier              CRAFP04HA02003.vme

1/6/0/3      2.0               4.0            Earlier              CRAFP04HA03004.vme

1/6/0/4      1.0               1.0            Same                  CRAFP04HA04001.vme

1/6/2/1      3.0               3.0            Same                  CRAXP12A01003.vme

1/10/0/1     3.0               3.0            Same                  CRACQ12HM01003.vme

1/10/0/2     4.0               0.0            N/A                   no file

Table 2 Command output

Field	Description
Location	Location of the CPLD in the format of chassis number/slot number/subslot number/CPLD number.
RunningVersion	Version of the running CPLD.
FileVersion	Version of the CPLD logic in the software package.
VersionComparison	Indicates whether the running CPLD version is earlier than the version of the CPLD logic in the software package. ·     Earlier. ·     Later. ·     Same. ·     N/A—No CPLD logic file exists in the software package.
FileName	Name of the CPLD logic file.

 

Related commands

display update cpld status

update cpld

display update cpld status

Use display update cpld status to display CPLD update status.

Syntax

display update cpld status

Views

User view

Predefined user roles

network-admin

Usage guidelines

A CPLD update does not stop because of the loss of a device management connection. If you lose the connection to the device during a CPLD update, use this command to verify whether the update has been completed after you reconnect to the device.

Examples

# Display CPLD update status when no CPLD update has been performed.

<Sysname> display update cpld status

No CPLD update has been performed since the last system boot or switchover.

# Display CPLD update status when a CPLD update is in progress.

<Sysname> display update cpld status

CPLD update is in progress.

 

[2020-03-12 08:06:20] Started, 2 CPLDs total.

[2020-03-12 08:06:20] #1 CPLD 1/10/0/1: successful (2.0 to 3.0)

[2020-03-12 08:06:37] #2 CPLD 1/10/0/2: 86%...

# Display CPLD update status when a CPLD update has been completed.

<Sysname> display update cpld status

No CPLD update is in progress. Last update status:

 

[2020-03-12 08:06:20] Started, 2 CPLDs total.

[2020-03-12 08:06:20] #1 CPLD 1/10/0/1: successful (2.0 to 3.0)

[2020-03-12 08:06:37] #2 CPLD 1/10/0/2: successful (2.0 to 4.0)

[2020-03-12 08:08:17] Finished, 2 success, 0 skipped, 0 failure, 0 error.

 

The update took 1 min 57 sec.

Related commands

display cpld version

update cpld

firmware update

Use firmware update to upgrade the CPLD firmware.

Syntax

firmware update chassis chassis-number slot slot-number subslot subslot-number { cpld cpld-number | cpu cpu-number | module module-number } file filename

Views

User view

Predefined user roles

network-admin

Parameters

chassis chassis-number slot slot-number: Specifies a card on a cluster member device. The chassis-number argument represents the cluster member ID. The slot-number argument represents the slot number of the card.

subslot subslot-number: Specifies a subcard by its subslot number. If you do not specify a subcard, the command upgrades firmware for all subcards on the base card.

cpld cpld-number: Specifies a complex programmable logical device (CPLD) by its number.

cpu cpu-number: Specifies a CPU by its number.

module module-number: Specifies a module by its number.

file filename: Specifies an upgrade file in the filesystemname/filename.extension 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 Fundamentals Configuration Guide.

Usage guidelines

Use this command to upgrade firmware that cannot be upgraded using the boot-loader command.

To complete the firmware upgrade, you must power cycle the card or subcard.

To power cycle a card or subcard, use one of the following methods:

·     Power cycle the device.

·     Remove and reinsert the card or subcard.

·     Execute the power-supply off command, and then execute the power-supply on command.

Examples

# Upgrade CPLD 1 in slot 1.

<Sysname> firmware update chassis 1 slot 8 subslot 0 cpld 1 file flash:/package.bin

Updating firmware for CPLD on the specified card or subcard. Continue?[Y/N]:Y

Updating the firmware........Done.

update cpld

Use update cpld to bulk update CPLDs.

Syntax

update cpld [ chassis chassis-number [ slot slot-number [ cpu cpu-number | subslot subslot-number ] [ index cpld-index ] ] ] [ dry-run | allow-downgrade | ignore-version | ignore-status ] *

Views

User view

Predefined user roles

network-admin

Parameters

chassis chassis-number: Specifies a cluster member by its chassis number. If you do not specify a cluster member, this command updates the CPLDs on all chassis numbers.

slot slot-number: Specifies a card by its slot number. If you do not specify a card, this command updates the CPLDs on all cards in the cluster.

cpu cpu-number: Specifies a CPU by its number. This option is available only if multiple CPUs are available on the specified slot.

subslot subslot-number: Specifies a subcard by its subslot number. If you do not specify a subcard, the command updates the CPLDs on all subcards on a card.

index cpld-index: Specifies a CPLD by its number. If you do not specify a CPLD, this command updates all the CPLDs on a subcard or card.

dry-run: Performs a dry run update.

allow-downgrade: Allows downgrades. If you do not specify this option or the ignore-version option, only upgrades are allowed.

ignore-version: Ignores CPLD version checks and always updates the CPLD, regardless of whether the CPLD version in the upgrade file is higher than, lower than, or the same as the running CPLD.

ignore-status: Ignores subcard status. If you specify this option, an update can be performed regardless of the subcard status. If you do not specify this option, an update can be performed only if the affected subcard is in normal state.

Usage guidelines

This command can update all CPLDs in a cluster, update the CPLDs for a single chassis, card or subcard, or update a single CPLD.

As a best practice, perform the following tasks before performing a real CPLD update:

1.     Execute the display cpld version command to view CPLD version information.

2.     Execute the update cpld command with the dry-run option.

The CPLD update can take a long time. During the update, do not perform the following tasks:

·     Power off the device.

·     Reboot the affected card or subcard.

·     Remove and reinstall the affected card or subcard.

If you perform any of the preceding tasks, the card or subcard might be damaged.

During the CPLD update, Ctrl+C and other shortcut keys are not usable.

After the CPLD update is completed, you must power cycle the affected card or subcard for the update to take effect. When the affected card or subcard is in normal state, you can use the display cpld version command to verify that each CPLD is the desired version.

A CPLD update does not stop because of the loss of a device management connection. If you lose the connection to the device during a CPLD update, use the display update cpld status command to verify whether the update has been completed after you reconnect to the device.

Examples

# Upgrade all CPLDs for a card.

<Sysname> update cpld chassis 1 slot 10

WARNING: The update will take a long time; please do NOT power down

or reset the device, card or subcard during the update.

Removing a card or subcard is also prohibited. Continue? [Y/N]:y

Please wait...

[2020-03-12 08:06:20] Started, 2 CPLDs total.

[2020-03-12 08:06:20] #1 CPLD 1/10/0/1: successful (2.0 to 3.0)

[2020-03-12 08:06:37] #2 CPLD 1/10/0/2: successful (2.0 to 4.0)

[2020-03-12 08:08:17] Finished, 2 success, 0 skipped, 0 failure, 0 error.

 

The update took 1 min 57 sec.

After the update, please power cycle the related card or subcard, or remove and reinstall the related card or subcard for the new version to take effect.

Table 3 Command output

Field	Description
#1 CPLD 1/10/0/1	The system is updating the first CPLD. 1/10/0/1 indicates chassis number/slot number/subslot number/CPLD number.
successful (2.0 to 3.0)	The CPLD was successfully updated from 2.0 to 3.0. Other update results include: ·     failed (please try again). ·     skipped (subslot powered off). ·     skipped (update file not found). ·     skipped (already version x.0)—The CPLD version in the file is the same as the running CPLD version, and the ignore-version option has not been specified. ·     skipped (version x.0 later than file y.0)—The CPLD version in the upgrade file is earlier than the running CPLD version, and both the ignore-version and allow-downgrade options have not been specified.
2 success, 0 skipped, 0 failure, 0 error	Number of successful, skipped, and failed CPLD update operations, and number of CPLD update operations with communication errors.

 

Related commands

display cpld version

display update cpld status