Table of Contents

Related Documents

06-Software Upgrade Commands

Title	Size	Download
06-Software Upgrade Commands	174.76 KB

Software upgrade commands

The switch supports the FIPS mode that complies with NIST FIPS 140-2 requirements. Support for features, commands, and parameters might differ in FIPS mode and non-FIPS mode. For more information about FIPS mode, see Security Configuration Guide.

boot-loader

Syntax

In standalone mode:

boot-loader file file-url slot slot-number { main | backup }

In IRF mode:

boot-loader file file-url chassis chassis-number slot slot-number { main | backup }

View

User view

Default level

3: Manage level

Parameters

file file-url: Specifies a system software image file. The file-url argument specifies the file path, a string of 1 to 63 characters. If you enter a relative path, the system automatically converts it to an absolute path. The absolute path can contain up to 63 characters. The file path uses the drive:/file-name format or the file-name format, where:

· The drive argument specifies the storage medium where the file is saved. Table 1 shows how the storage medium of an MPU is identified.

Table 1 MPU identifications

MPU role	Identification format	Example	Remarks
· Active MPU in standalone mode · Global active MPU in IRF mode	StorageMediumName	flash	N/A
Standby MPU in standalone mode	slotslot-number#StorageMediumName	slot1#flash	slot-number—Slot number of the MPU.
All MPUs but the global active MPU in IRF mode	chassischassis-number#slotslot-number#StorageMediumName	chassis2#slot1#flash	chassis-number—IRF member ID. slot-number—Slot number of the MPU.

· The file-name argument specifies the file name, which typically uses the .bin extension.

slot slot-number: Specifies the slot number of an MPU. (In standalone mode.)

chassis chassis-number slot slot-number: Specifies an MPU in the IRF fabric. The chassis-number argument represents the IRF member ID, and the slot-number argument represents the slot number of the MPU. You can display the member ID and slot number with the display device command. (In IRF mode.)

main: Specifies the file as the main system software image file. The main system software image has higher priority than the backup system software image at startup.

backup: Specifies the file as the backup system software image file. The backup system software image is used at startup only if the main system software image is unavailable.

Description

Use boot-loader to specify a startup system software image file for an MPU.

To successfully execute the boot-loader command, make sure you have saved the image file to the root directory of the Flash or CF card on the MPU.

If the CF card has been partitioned, save the file to the root directory of the first partition.

Names of the startup system software image files on MPUs can be different, but their versions must be the same for a correct startup.

In FIPS mode, the specified file must pass authenticity verification before it can be set as a startup system software image file.

Related commands: display boot-loader.

Examples

In standalone mode:

# In non-FIPS mode, specify test.bin as the main startup system software image for the active MPU (in slot 0). This example assumes that this file has been saved in the root directory of the Flash on the active MPU.

<Sysname> boot-loader file test.bin slot 0 main

This command will set the boot file of the specified board. Continue? [Y/N]:y

The specified file will be used as the main boot file at the next reboot on slot 0!

# In non-FIPS mode, specify test.bin as the main startup system software image for the standby MPU (in slot 1). This example assumes that this file has been saved in the root directory of the Flash on the standby MPU.

<Sysname> boot-loader file slot1#flash:/test.bin slot 1 main

This command will set the boot file of the specified board. Continue? [Y/N]:y

The specified file will be used as the main boot file at the next reboot on slot 1!

# In FIPS mode, specify test.bin as the main startup system software image for the active MPU (in slot 0). This example assumes that this file has been saved in the root directory of the Flash on the active MPU.

<Sysname> boot-loader file test.bin slot 0 main

Verifying boot file ......

This command will set the boot file of the specified board. Continue? [Y/N]:y

The specified file will be used as the main boot file at the next reboot on slot 0!

In IRF mode:

# In non-FIPS mode, specify test.bin as the main startup system software image for the global active MPU (in slot 0 on member switch 1). This example assumes that the file has been saved in the root directory of the Flash on the MPU.

<Sysname> boot-loader file test.bin chassis 1 slot 0 main

This command will set the boot file of the specified board. Continue? [Y/N]:y

The specified file will be used as the main boot file at the next reboot on chassis 1 slot 0!

# In non-FIPS mode, specify test.bin as the main startup system software image for the global standby MPU in slot 1 on member switch 1. This example assumes that the file has been saved in the root directory of the Flash on the MPU.

<Sysname> boot-loader file chassis1#slot1#flash:/test.bin chassis 1 slot 1 main

This command will set the boot file of the specified board. Continue? [Y/N]:y

The specified file will be used as the main boot file at the next reboot on chassis 1 slot 1!

# In FIPS mode, specify test.bin as the main startup system software image for the global active MPU (in slot 0 on member switch 1). This example assumes that the file has been saved in the root directory of the Flash on the MPU.

<Sysname> boot-loader file test.bin chassis 1 slot 0 main

Verifying boot file ......

This command will set the boot file of the specified board. Continue? [Y/N]:y

The specified file will be used as the main boot file at the next reboot on chassis 1 slot 0!

boot-loader update slot

Syntax

boot-loader update slot slot-number

View

User view

Default level

3: Manage level

Parameters

slot slot-number: Specifies the slot number of the standby MPU.

Description

Use boot-loader update slot to synchronize the main startup system software image file from the active MPU to the standby MPU.

This command is supported only when the system operates in standalone mode.

In FIPS mode, the file must pass authenticity verification before it can be set as the main startup system software image file on the standby MPU.

Examples

# Synchronize the main startup system software image file from the active MPU to the standby MPU in slot 1.

<Sysname> boot-loader update slot 1

bootrom update

Syntax

In standalone mode:

bootrom update file file-url slot slot-number-list

In IRF mode:

bootrom update file file-url chassis chassis-number slot slot-number-list

View

User view

Default level

3: Manage level

Parameters

file file-url: Specifies a BootWare image file for the upgrade. The file-url argument specifies the image file path, a string of 1 to 63 characters. The BootWare image file can be saved only on the Flash or CF card. For more information about file path naming, see "boot-loader."

slot slot-number-list: Specifies a space-separated list of up to seven slot number items. Each item specifies a card by its slot number or a range of cards in the form of start-slot-number to end-slot-number. For example, slot 0 to 1 2.

chassis chassis-number: Specifies an IRF member switch by its member ID. (In IRF mode.)

Description

Use bootrom update to upgrade the BootWare image for cards.

To successfully execute the bootrom update file file-url command, make sure the upgrade file has been saved to the correct location, as follows:

· To upgrade an MPU, save the upgrade file in the root directory of a storage medium (the Flash or CF card) on the MPU.

· To upgrade interface cards or switching fabric modules:

¡ In standalone mode—Save the upgrade file in the root directory of a storage medium on the active MPU.

¡ In IRF mode—Save the upgrade file in the root directory of the storage medium on the active MPU of the member switch that hosts the cards.

If the storage medium has been partitioned, save the upgrade file to the root directory of the first partition.

Names of the BootWare image files on each MPU can be different, but their versions must be the same for a correct startup.

In FIPS mode, the file must pass authenticity verification before it can be set as the BootWare image file.

Examples

# In non-FIPS mode, use the a.btw file to upgrade the BootWare image on the active MPU in slot 0.

<Sysname> bootrom update file a.btw slot 0

This command will update bootrom file on the specified board(s), Continue? [Y/

N]:y

Now updating bootrom, please wait...

# In FIPS mode, use the a.btw file to upgrade the BootWare image on the standby MPU in slot 1.

<Sysname> bootrom update file a.btw slot 1

Verifying bootrom file ......

This command will update bootrom file on the specified board(s), Continue? [Y/

N]:y

Now updating bootrom, please wait...

display boot-loader

Syntax

In standalone mode:

display boot-loader [ slot slot-number ] [ | { begin | exclude | include } regular-expression ]

In IRF mode:

display boot-loader [ chassis chassis-number [ slot slot-number ] ] [ | { begin | exclude | include } regular-expression ]

View

Any view

Default level

2: System level

Parameters

slot slot-number: Specifies the slot number of an MPU. If no MPU is specified, this command displays the system software images on each MPU. (In standalone mode.)

chassis chassis-number [ slot slot-number ]: Specifies an IRF member switch or an MPU in an IRF member switch. The chassis-number argument represents the IRF member ID of the switch, and the slot-number argument represents the slot number of the MPU on the switch. If no IRF member switch is specified, this command displays the system software images on each MPU in the IRF fabric. If an IRF member switch is specified, but no MPU is specified, this command displays the system software images on each MPU on the specified member switch. (In IRF mode.)

|: Filters command output by specifying a regular expression. For more information about regular expressions, see Fundamentals Configuration Guide.

begin: Displays the first line that matches the specified regular expression and all lines that follow.

include: Displays all lines that match the specified regular expression.

regular-expression: Specifies a regular expression, a case-sensitive string of 1 to 256 characters.

Description

Use display boot-loader to display system software image information, including the current system software image and the startup system software images.

Related commands: boot-loader.

Examples

# In standalone mode, display system software images on each MPU.

<Sysname> display boot-loader

The next primary boot file of board 0 is: cfa0:/test.bin

The next backup boot file of board 0 is: flash:/backup.bin

The current boot file of board 0 is: cfa0:/test.bin

# In IRF mode, display system software images on each MPU.

<Sysname> display boot-loader

The next primary boot file of chassis 1 slot 0 is: cfa0:/test.bin

The next backup boot file of chassis 1 slot 0 is: flash:/backup.bin

The current boot file of chassis 1 slot 0 is: cfa0:/test.bin

display patch

Syntax

display patch [ | { begin | exclude | include } regular-expression ]

View

Any view

Default level

3: Manage level

Parameters

|: Filters command output by specifying a regular expression. For more information about regular expressions, see Fundamentals Configuration Guide.

begin: Displays the first line that matches the specified regular expression and all lines that follow.

include: Displays all lines that match the specified regular expression.

regular-expression: Specifies a regular expression, a case-sensitive string of 1 to 256 characters.

Description

Use display patch to display patch files that have been installed.

If a patch file is loaded from a patch package file, this command also displays the package file version.

Examples

# In standalone mode, display patch files that have been installed.

<Sysname> display patch

The following patch packages are loaded:

flash:/s12500-b90h01a.bin, B90H01a, loaded on slot(s):

1, 4, 5, 6, 7, 8, 9, 10

flash:/s12500-b90h01b.bin, B90H01b, loaded on slot(s):

flash:/s12500-b90h01c.bin, B90H01c, loaded on slot(s):

# In IRF mode, display patch files that have been installed.

<Sysname> display patch

The following patch packages are loaded:

flash:/s12500-b90h02a.bin, H001, loaded on slot(s):

Chassis 1, slot(s): 0

flash:/s12500-b90h02b.bin, H002, loaded on slot(s):

Chassis 1, slot(s): 3

flash:/s12500-b90h02c.bin, H003, loaded on slot(s):

Chassis 3, slot(s): 6, 11

Table 2 Command output

Field	Description
flash:/s12500-b90h01a.bin	Directory of the installed patch file.
B90H01a	Version of the patch package.
loaded on slot(s):	Slot number of the card on which the patches have been loaded.

display patch information

Syntax

display patch information [ | { begin | exclude | include } regular-expression ]

View

Any view

Default level

3: Manage level

Parameters

|: Filters command output by specifying a regular expression. For more information about regular expressions, see Fundamentals Configuration Guide.

begin: Displays the first line that matches the specified regular expression and all lines that follow.

include: Displays all lines that match the specified regular expression.

regular-expression: Specifies a regular expression, a case-sensitive string of 1 to 256 characters.

Description

Use display patch information to display hotfix information.

Examples

# In standalone mode, display hotfix information.

<Sysname> display patch information

The location of patches: flash:

Slot Version Temporary Common Current Active Running Start-Address

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

0 MR 0 0 0 0 0 0x3995b70

3 LC 0 0 0 0 0 0x225bab4

# In IRF mode, display hotfix information.

<Sysname> display patch information

Chassis Slot Version Temporary Common Current Active Running Start-Address

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

1 0 MR 0 0 0 0 0 0x378d834

1 3 LC 0 0 0 0 0 0x21d6bf0

Table 3 Command output

Field	Description
The location of patches	Patch file location. You can use the patch location command to change the location.
Chassis		IRF member ID. This field appears only when the switch is operating in IRF mode.
Slot	Slot number of the card. If the card has only one CPU, this field displays the card slot number. If the card has multiple CPUs, the primary CPU is identified by the card slot number, and an auxiliary CPU is identified by slot-number.cpu-id.
Version	Patch version. If no patch is installed, the flag suffix of the patch is displayed.
Temporary	Number of temporary patches. These patches are interim solutions for fixing critical bugs. They are not formally released.
Common	Number of common patches. These patches are formally released to users. A common patch always includes the functions of its previous temporary patches.
Current	Total number of patches.
Running	Number of patches in RUNNING state.
Active	Number of patches in ACTIVE state.
Start-Address	Start address of the patch memory area in the memory.

fan update

Syntax

In standalone mode:

fan update [ file file-url ] tray { top | bottom }

In IRF mode:

fan update [ file file-url ] chassis chassis-number tray { top | bottom }

View

User view

Default level

2: System level

Parameters

file file-url: Specifies the upgrade fan monitor file. The file-url argument represents upgrade file name, a string of 1 to 63 characters. With no file name specified, the fan monitor file contained in the current system software image is used.

tray { top | bottom }: Specifies the fan tray whose fan monitor software is to be upgraded. The top keyword specifies the upper fan tray and the bottom keyword specifies the lower fan tray.

chassis chassis-number: Specifies the IRF member switch bearing the fan tray whose fan monitor software is to be upgraded. The chassis-number argument takes the ID of the IRF member switch. (In IRF mode.)

Description

Use fan update to upgrade the fan monitor software of a fan tray.

This command is available only for fan trays that use software version 103 and CPLD 002 (or above). To display this information, use the display fan verbose command.

When the system displays the upgrade completed message, remove and reinstall the fan tray to reset it and run the upgraded software. After these operations are completed, you can continue to upgrade the other fan tray.

To avoid damage to the fan monitor module, do not perform the following operations while the fan monitor software is being upgraded:

· Remove the fan tray before the system displays the upgrade completed message.

· Perform an active and standby switchover.

· Power off or reboot the switch.

· Reboot or swap the active MPU.

While a fan tray is being upgraded, you cannot configure the fan tray or the power modules.

Examples

# Upgrade the fan monitor software of the top fan tray by using the fan monitor software contained in the current system software image.

<Sysname> fan update tray top

logic update bymbus

Syntax

In standalone mode:

logic update bymbus [ file filename ] slot slot-number logicid logicid

In IRF mode:

logic update bymbus [ file filename ] chassis chassis-number slot slot-number logicid logicid

View

User view

Default level

2: System level

Parameters

file filename: Specifies the CPLD upgrade file. The filename argument represents the upgrade file name, a string of 1 to 63 characters. If no file is specified, the command uses the CPLD file contained in the current system software image file.

slot slot-number: Specifies a card by its slot number. (In standalone mode.)

logicid logicid: Specifies one of the following CPLD types:

· 0—Card (interface card or MPU) CPLD.

· 1—OAM module CPLD on an MPU, or CPU CPLD on an interface card.

chassis chassis-number slot slot-number: Specifies a card on an IRF member switch. The chassis-number argument represents the ID of the IRF member switch, and the slot-number argument represents the slot number of the card. (In IRF mode.)

Description

Use logic update bymbus to upgrade the CPLD for a card through the maintenance bus (MBUS) daughter card.

Before upgrading the CPLD on an interface card, use the board-offline command to set the card in offline state. In this state, the card cannot forward traffic. To display the card state, use the display device command.

To ensure a successful upgrade, do not perform any of the following operations during the upgrade:

· Perform an active and standby switchover.

· Power off or reboot the switch.

· Reboot or swap the active MPU.

The card automatically reboots to complete the CPLD upgrade.

If an interface card is inserted during a CPLD upgrade through MBUS, the system can supply power to the card only after the upgrade is complete.

Examples

# Upgrade the card CPLD of the card in slot 2 through MBUS.

<Sysname> logic update bymbus slot 2 logicid 0

mbus update

Syntax

In standalone mode:

mbus update [ file file-url ] slot slot-number

In IRF mode:

mbus update [ file file-url ] chassis chassis-number slot slot-number

View

User view

Default level

2: System level

Parameters

file file-url: Specifies a file for upgrading the MBUS daughter card software. The file-url argument represents the upgrade file name, a string of 1 to 63 characters. If no file is specified, this command uses the MBUS daughter card software contained in the current system software image.

slot slot-number: Specifies a card by its slot number. (In standalone mode.)

Description

Use mbus update to upgrade the MBUS daughter card software of the card in the specified slot.

To ensure a successful upgrade, do not perform any of the following operations during the upgrade:

· Perform an active and standby switchover.

· Power off or reboot the switch.

· Reboot or swap the active MPU.

Examples

# Upgrade the MBUS daughter card software of the card in slot 2.

<Sysname> mbus update file cfa0:/mbus_v101.bin slot 2

oam-bootrom update

Syntax

In standalone mode:

oam-bootrom update file file-url slot slot-number

In IRF mode:

oam-bootrom update file file-url chassis chassis-number slot slot-number

View

User view

Default level

2: System level

Parameters

file file-url: Specifies the BootWare image file used for the upgrade, where the file-url argument represents the upgrade file name. The file can be saved only on the Flash or CF card.

slot slot-number: Specifies an MPU by its slot number. (In standalone mode.)

chassis chassis-number slot slot-number: Specifies an MPU on an IRF member switch. The chassis-number argument represents the ID of the IRF member switch, and the slot-number argument represents the slot number of the MPU. (In IRF mode.)

Description

Use oam-bootrom update to upgrade the extended BootWare segment of the OAM module on an MPU.

Examples

# Use the test.btw file to upgrade the extended BootWare segment of the OAM module on the MPU in slot 1.

<Sysname> oam-bootrom update file flash:/test.btw slot 1

patch active

Syntax

In standalone mode:

patch active patch-number slot slot-number

In IRF mode:

patch active patch-number chassis chassis-number slot slot-number

View

System view

Default level

3: Manage level

Parameters

patch-number: Specifies the sequence number of a patch, in the range of 1 to 200. If no sequence number is specified, this command validates all DEACTIVE patches. If a sequence number is specified, this command activates the specified patch and all its previous DEACTIVE patches.

slot slot-number: Specifies a card by its slot number. (In standalone mode.)

Description

Use patch active to activate patches.

Before executing this command, you must use the patch load command to load patches.

The patch active command changes the state of DEACTIVE patches to ACTIVE state and runs the patches. To continue to run these patches after a reboot, use the patch run command to change their state to RUNNING. If not, the state of ACTIVE patches changes back to DEACTIVE at a reboot.

Examples

# In standalone mode, activate patch 3 and all its previous DEACTIVE patches on the card in slot 5.

<Sysname> system-view

[Sysname] patch active 3 slot 5

# In IRF mode, activate all DEACTIVE patches on the card in slot 2 of IRF member switch 1.

<Sysname> system-view

[Sysname] patch active chassis 1 slot 2

patch deactive

Syntax

In standalone mode:

patch deactive patch-number slot slot-number

In IRF mode:

patch deactive patch-number chassis chassis-number slot slot-number

View

System view

Default level

3: Manage level

Parameters

patch-number: Specifies the sequence number of a patch, in the range of 1 to 200. If no sequence number is specified, this command deactivates all ACTIVE patches. If a sequence number is specified, this command deactivates the specified patch and all its subsequent ACTIVE patches.

slot slot-number: Specifies a card by its slot number. (In standalone mode.)

Description

Use patch deactive to stop running patches.

This command is not applicable to patches in RUNNING state.

Examples

# In standalone mode, stop running patch 3 and all its subsequent ACTIVE patches on the card in slot 5.

<Sysname> system-view

[Sysname] patch deactive 3 slot 5

# In IRF mode, stop running all ACTIVE patches on the card in slot 5 of IRF member switch 1.

<Sysname> system-view

[Sysname] patch deactive chassis 1 slot 5

patch delete

Syntax

In standalone mode:

patch delete patch-number slot slot-number

In IRF mode:

patch delete patch-number chassis chassis-number slot slot-number

View

System view

Default level

3: Manage level

Parameters

patch-number: Specifies the sequence number of a patch, in the range of 1 to 200. If no sequence number is specified, this command removes all patches in the patch memory area. If a sequence number is specified, this command removes the specified patch and all its subsequent patches.

slot slot-number: Specifies a card by its slot number. (In standalone mode.)

Description

Use patch delete to remove patches from the patch memory area.

This command does not delete patches from the storage media. After being removed from the patch memory area, the patches change to the IDLE state.

Examples

# In standalone mode, remove patch 3 and all its subsequent patches from the patch memory area on the card in slot 5.

<Sysname> system-view

[Sysname] patch delete 3 slot 5

# In IRF mode, remove all patches from the patch memory area on the card in slot 5 of IRF member switch 1.

<Sysname> system-view

[Sysname] patch delete chassis 1 slot 5

patch install

Syntax

patch install { patch-location | file filename }

undo patch install

View

System view

Default level

3: Manage level

Parameters

patch-location: Specifies the patch file path, a string of 1 to 64 characters. The file must be saved in the root directory of a storage medium. If a partitioned CF card is used, save the file in the root directory of the first partition. Provide this argument if the patch file is not packaged in a patch package file, and make sure the file name is correct.

file filename: Specifies a patch package file name.

Description

Use patch install to install and run patches in one step.

Use undo patch install to remove all ACTIVE and RUNNING patches from the patch memory area.

If a patch package file is used, save the file to the root directory of a storage medium on each MPU before patch installation. If a patch file is used, save the file as follows:

· In standalone mode, save the patch files for the active MPU, interface cards, or switching fabric modules to the root directory of the storage media on the active MPU, and save the patch files for the standby MPU to the root directory of the storage media on the standby MPU.

· In IRF mode, save the patch files for the active MPU, interface cards, or switching fabric modules to the root directory of the storage media on each member switch's active MPU, and save the patch files for the standby MPU to the root directory of the storage media on each member switch's standby MPU.

If a partitioned CF card is used, save the file to the root directory of the first partition.

If a slot is empty, the system will record the information. When a card is plugged into the slot, the system will install the corresponding patch on the card.

In FIPS mode, the patch file or the patch package file must pass authenticity verification before the command is executed.

The patch install command changes the state of installed patches from IDLE to ACTIVE or RUNNING, depending on your choice during the command execution process. If you choose to have installed patches continue to run after a reboot, the installed patches are set in RUNNING state and remain in this state after a reboot. If not, the installed patches are set in ACTIVE state and change to the DEACTIVE state at a reboot.

The undo patch install command change the state of ACTIVE and RUNNING patches to IDLE, but does not delete them from the storage media.

The patch install patch-location command can change the patch file location that has been specified with the patch location command. In contrast, the patch install file filename does not.

Examples

# Install the patches located on the Flash and make the patches take effect after the switch reboot.

<Sysname> system-view

[Sysname] patch install flash:

Patches will be installed. Continue? [Y/N]:y

Do you want to run patches after reboot? [Y/N]:y

Installing patches…

Installation completed, and patches will continue to run after reboot.

[Sysname]

patch load

Syntax

In standalone mode:

patch load slot slot-number [ file filename ]

In IRF mode:

patch load chassis chassis-number slot slot-number [ file filename ]

View

System view

Default level

3: Manage level

Parameters

slot slot-number: Specifies a card by its slot number. (In standalone mode.)

file filename: Specifies a patch package file name. If a package file is specified, the system loads patches from the patch package file. If no package file is specified, the system attempts to load patch files from Flash and CF card in order.

Description

Use patch load to load patches from a storage medium (Flash or CF card) to the patch memory area.

To use a patch package file, save the patch package file to the root directory of a storage medium on each MPU before patch installation. If a patch file is used, save the file as follows:

· In standalone mode, save the patch files for the active MPU, interface cards, or switching fabric modules to the root directory of a storage medium on the active MPU, and save the patch files for the standby MPU to the root directory of a storage medium on the standby MPU.

· In IRF mode, save the patch files for the active MPU, interface cards, or switching fabric modules to the root directory of a storage medium on each member switch's active MPU, and save the patch files for the standby MPU to the root directory of a storage medium on each member switch's standby MPU.

In FIPS mode, the patch package file or the patch file must pass authenticity verification before it can be loaded.

Examples

# In standalone mode, load patches from patch files for the card in slot 3.

<Sysname> system-view

[Sysname] patch load slot 3

# In IRF mode, load patches from a patch package file for the card in slot 3 on IRF member switch 1.

<Sysname> system-view

[Sysname] patch load chassis 1 slot 3 file flash:/patchpackege.bin

patch location

Syntax

patch location patch-location

View

System view

Default level

3: Manage level

Parameters

patch-location: Specifies the patch file location, a string of 1 to 64 characters.

Description

Use patch location to configure the patch file location.

By default, the patch file location is flash:.

For reliable patch loading, H3C recommends saving patch files to the root directory of the Flash. To use the CF card, you must specify the directory for saving patch files.

If you execute the patch install patch-location command, the directory specified for the patch-location argument replaces the directory specified with the patch location command after the upgrade is complete.

Examples

# Specify the root directory of the CF card as the patch file location.

<Sysname> system-view

[Sysname] patch location cfa0:

patch run

Syntax

In standalone mode:

patch run patch-number [ slot slot-number ]

In IRF mode:

patch run patch-number [ chassis chassis-number slot slot-number ]

View

System view

Default level

3: Manage level

Parameters

patch-number: Specifies the sequence number of a patch, in the range of 1 to 200. If no sequence number is specified, this command confirms all ACTIVE patches (including ACTIVE patches for auxiliary CPUs) and changes their state to RUNNING. If a sequence number is specified, this command confirms the specified ACTIVE patch and all its previous patches, and changes their state to RUNNING.

slot slot-number: Specifies a card by its slot number. If no slot is specified, the command applies to all cards. (In standalone mode.)

Description

Use patch run to confirm ACTIVE patches.

This command is applicable to patches in ACTIVE state only.

After being confirmed, ACTIVE patches are set in RUNNING state and can continue to run after a reboot. If not being confirmed, ACTIVE patches are set in DEACTIVE state at a reboot.

Examples

# In standalone mode, confirm patch 3 and all its previous ACTIVE patches on the card in slot 5.

<Sysname> system-view

[Sysname] patch run 3 slot 5

# In IRF mode, confirm all ACTIVE patches on the card in slot 5 of IRF member switch 1.

<Sysname> system-view

[Sysname] patch run chassis 1 slot 5

pmu update

Syntax

In standalone mode:

pmu update [ file file-url ] pmu-id

In IRF mode:

pmu update [ file file-url ] chassis chassis-number pmu-id

View

User view

Default level

3: Manage level

Parameters

file file-url: Specifies an upgrade file for the power monitoring module software. The file-url argument represents the upgrade file name, a string of of 1 to 63 characters. If no file is specified, this command uses the power monitoring module software file contained in the current system software image file. In IRF mode, the file specified for the file-url argument must be saved on the switch that hosts the power monitoring module. Otherwise, the upgrade fails.

chassis chassis-number: Specifies the IRF member switch that hosts the power monitoring module you are upgrading. The chassis-number argument represents the IRF member ID of the switch. (In IRF mode.)

pum-id: Specifies the power monitoring module ID, which is 1 on an S12508 switch and either 1 or 2 on an S12518 switch.

Description

Use pmu update to upgrade the software of a power monitoring module.

To ensure a successful upgrade, do not perform any of the following operations during the upgrade:

· Perform an active and standby switchover.

· Power off or reboot the switch.

· Reboot or swap the active MPU.

Examples

# In standalone mode, upgrade the software of the power monitoring module on the switch.

<Sysname> pmu update file cfa0:/test.bin 1

# In IRF mode, upgrade the software of power monitoring module 1 on member switch 1.

<Sysname> pmu update file cfa0:/test.bin chassis 1 1

power-logic update

Syntax

In standalone mode:

power-logic update [ file file-url ] slot slot-number

In IRF mode:

power-logic update [ file file-url ] chassis chassis-number slot slot-number

View

User view

Default level

3: Manage level

Parameters

file file-url: Specifies a file for upgrading the power software on a card. The file-url argument represents the upgrade file name, a string of 1 to 63 characters. If the argument is not specified, this command uses the upgrade file contained in the current system software image.

slot slot-number: Specifies the slot number of the card. (In standalone mode.)

chassis chassis-number slot slot-number: Specifies a card in an IRF member switch. The chassis-number argument represents the IRF member ID of the switch. The slot-number argument represents the slot number of the card. (In IRF mode.)

Description

Use power-logic update to upgrade the power software on a card.

You cannot use this command to upgrade the power software on an MPU.

Before the upgrade, use the board-offline command to set the card in offline state. To display the card state, use the display device command.

To ensure a successful upgrade, follow these guidelines:

· In an IRF fabric, the upgrade file must be saved on the active MPU that is in the same chassis as the card you are working with.

· Do not perform any of the following operations during the upgrade:

¡ Perform an active and standby switchover.

¡ Execute the power-supply off command.

¡ Power off the device.

¡ Reboot or swap the active MPU or the card that is being upgraded.

· If the system instructs you to choose a card model during the upgrade, use the card model on the card panel as a reference to make the correct choice. If you fail to enter a choice within 30 seconds or fail to choose the correct model within five attempts, the upgrade fails.

When the upgrade is complete, the card automatically reboots to run the new software.

If you install a card during a power software upgrade, the system can supply power to the card only after the upgrade is complete.

Examples

# Upgrade the power software on the card in slot 2.

<Sysname> power-logic update slot 2

Comware V5-to-V7 migration commands

v5to7 upgrade

Syntax

v5to7 upgrade boot boot-image-url system system-image-url configuration-file config-file-url

View

User view

Default level

3: Manage level

Parameters

boot-image-url: Comware V7 boot image file path. This file must be saved in cfa0:/ on the active MPU (in standalone mode) or the global active MPU (in IRF mode).

system-image-url: Specifies the file path of a Comware V7 system image. This file must be saved in cfa0:/ on the active MPU (in standalone mode) or the global active MPU (in IRF mode).

config-file-url: Specifies the file path of a Comware V7 configuration file. To continue to use the Comware V5 configuration, use the configuration migration tool to convert the Comware V5 configuration file to a Comware V7 configuration file. This file must be saved in cfa0:/ on the active MPU (in standalone mode) or the global active MPU (in IRF mode).

NOTE:

For simplicity, this document uses "cfa0:/" to represent the root directory of each MPU's CF card. If the CF card is partitioned, "cfa0:/" represents the root directory of the CF card.

Description

Use v5to7 upgrade to migrate from Comware V5 to Comware V7.

This command sets the specified Comware V7 images and configuration file as the main startup software images and configuration file, and it reboots the device with these files to complete the migration.

This command automatically copies the specified Comware V7 files to cfa0:/ on the standby MPU (in standalone mode) or all other MPUs (in IRF mode).

Related commands: v5to7 commit and v5to7 rollback (Comware V7 fundamentals configuration guide).

Examples

# In standalone mode, migrate from Comware V5 to Comware V7.

<sysname> v5to7 upgrade boot boot.bin system system.bin configuration-file test.cfg

This command will upgrade the system from Comware V5 to Comware V7 and automatically reboot the system. Continue? [Y/N]:y

Step 1: Copying software image and configuration file to CF cards…

Slots: 1.

Slot 1: ………………………………OK.

Step 2: Backing up files from Flash to CF cards…

Slots: 0, 1.

Slot 0: ………………………………OK.

Slot 1: ………………………………OK.

Step 3: Setting startup software image files and configuration file…

Slots: 0, 1.

Slot 0: OK.

Slot 1: OK.

Step 4: The system is rebooting…

# In IRF mode, migrate from Comware V5 to Comware V7.

<sysname> v5to7 upgrade boot boot.bin system system.bin configuration-file test.cfg

This command will upgrade the system from Comware V5 to Comware V7 and automatically reboot the system. Continue? [Y/N]:y

Step 1: Copying software image and configuration file to CF cards…

Slots: 1/1, 2/0, 2/1, 3/0, 3/1, 4/0, 4/1.

Chassis 1 slot 1: ………………………………OK.

Chassis 2 slot 0: ………………………………OK.

Chassis 2 slot 1: ………………………………OK.

Chassis 3 slot 0: ………………………………OK.

Chassis 3 slot 1: ………………………………OK.

Chassis 4 slot 0: ………………………………OK.

Chassis 4 slot 1: ………………………………OK.

Step 2: Backing up files from Flash to CF cards…

Slots: 1/0, 1/1, 2/0, 2/1, 3/0, 3/1, 4/0, 4/1.

Chassis 1 slot 0: ………………………………OK.

Chassis 1 slot 1: ………………………………OK.

Chassis 2 slot 0: ………………………………OK.

Chassis 2 slot 1: ………………………………OK.

Chassis 3 slot 0: ………………………………OK.

Chassis 3 slot 1: ………………………………OK.

Chassis 4 slot 0: ………………………………OK.

Chassis 4 slot 1: ………………………………OK.

Step 3: Setting startup software image files and configuration file…

Slots: 1/0, 1/1, 2/0, 2/1, 3/0, 3/1, 4/0, 4/1.

Chassis 1 slot 0: OK.

Chassis 1 slot 1: OK.

Chassis 2 slot 0: OK.

Chassis 2 slot 1: OK.

Chassis 3 slot 0: OK.

Chassis 3 slot 1: OK.

Chassis 4 slot 0: OK.

Chassis 4 slot 1: OK.

Step 4: The system is rebooting…

01-Fundamentals Command Reference

boot-loader update slot

bootrom update

oam-bootrom update

patch active

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program

Global Learning

Partner Sales Resources

Service Business

News & Events

Contact Us