Software upgrade commands 1

boot-loader file· 1

boot-loader update· 3

bootrom update· 4

display boot-loader 5

fan update· 7

logic update· 8

mbus update· 9

pmu update· 10

power-logic update· 11

version auto-update enable· 12

version check ignore· 13

v5to7 commit 14

v5to7 rollback· 16

 

boot-loader file

Use boot-loader file to specify startup software image files.

Syntax

In standalone mode:

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

boot-loader file ipe-filename slot slot-number { backup | main }

In IRF mode:

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

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

Views

User view

Predefined user roles

network-admin

Parameters

boot boot-package: Specifies a .bin boot image file, a case-insensitive string of 1 to 63 characters. The file name specified for the boot-package argument takes the storage-media:/base-filename.bin format, for example, flash:/startup-boot.bin.

system system-package: Specifies a .bin system image file, a case-insensitive string of 1 to 63 characters. The file name specified for the system-package argument takes the storage-media:/base-filename.bin format, for example, flash:/startup-system.bin.

feature feature-package: Specifies a space-separated list of up to 30 .bin feature package files. Each feature package file name must be a case-insensitive string of 1 to 63 characters and takes the storage-media:/base-filename.bin format, for example, flash:/startup-a.bin.

ipe-filename: Specifies an .ipe Comware image file name, a case-insensitive of 1 to 63 characters. The file name must take the storage-media:/base-filename.ipe format, for example, flash:/startup.ipe.

slot slot-number: Specifies the slot number of the MPU for which the startup images are specified. (In standalone mode.)

chassis chassis-number slot slot-number: Specifies the MPU for which the startup images are specified in the IRF fabric. The chassis-number argument represents the IRF member ID of the device that holds the card, and the slot-number argument represents the slot number of the card. (In IRF mode.)

backup: Specifies the files as backup startup files. Backup startup images are used only when main images are not available.

main: Specifies the files as main startup files. The device always first attempts to start up with main startup files.

Usage guidelines

In standalone mode:

Use this command to upgrade the startup software images on both MPUs. To upgrade only the standby MPU, you can also use the boot-loader update command.

Before using this command, you must save the startup software image file to the root directory of Flash memory or CF card on the active MPU. If the CF card has been partitioned, save the file to the root directory of the first partition. If the standby MPU is specified in this command, the system examines the root directory of the standby MPU's storage media for any file with the same name as the file on the active MPU. If no such a file exists, the system copies the specified file from the active MPU to the standby MPU and sets it as a startup image file. If a file with the same name exists, you must choose whether to overwrite the file already on the standby MPU.

In IRF mode:

Use this command to upgrade the startup software images on all MPUs. To upgrade only standby MPUs, you can also use the boot-loader update command.

Before using this command, you must save the startup software image file to the root directory of Flash memory or CF card on the active MPU. If the CF card has been partitioned, save the file to the root directory of the first partition. If a standby MPU is specified in this command, the system performs the same procedure as in standalone mode.

This command overwrites the entire startup software image list. To add new startup feature images, specify all feature package files, including feature package files in the old startup software image list. If not, the new startup software image list contains only the feature package files that are specified in the command.

Examples

# In standalone mode, specify flash:/all.ipe as the backup startup image file for the MPU in slot 0.

<Sysname> boot-loader file flash:/all.ipe slot 0 backup

Images in IPE:

  boot.bin

  system.bin

ssh.bin

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

Add images to target slot.

  flash:/boot.bin already exists on slot 0.

  flash:/system.bin already exists on slot 0.

  flash:/ssh.bin already exists on slot 0.

Overwrite it? [Y/N]:y

The specified file list will be used as the backup startup software images at the next reboot on slot 0.

# In standalone mode, specify startup-boot.bin and startup-system.bin as the backup startup image files for the MPU in slot 1.

<Sysnam>boot-loader file boot flash:/ startup-boot.bin system flash:/ startup-system.bin slot 1 backup

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

The specified file list will be used as the backup startup software images at the next reboot on slot 1.

# In IRF mode, specify flash:/all.ipe as the backup startup image file for the MPU in slot 0 on IRF member device 1.

<Sysname> boot-loader file flash:/all.ipe chassis 1 slot 0 backup

Images in IPE:

  boot.bin

  system.bin

  ssh.bin

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

Add images to target slot.

  flash:/boot.bin already exists on chassis 1 slot 0.

  flash:/system.bin already exists on chassis 1 slot 0.

  flash:/ssh.bin already exists on chassis 1 slot 0.

Overwrite it? [Y/N]:y

The specified file list will be used as the backup startup software images at the next reboot on chassis 1 slot 0.

Related commands

display boot-loader

boot-loader update

In standalone mode:

Use boot-loader update to synchronize startup images from the active MPU to the standby MPU.

In IRF mode:

Use boot-loader update to synchronize startup images from the global active MPU to a standby MPU.

Syntax

In standalone mode:

boot-loader update slot slot-number

In IRF mode:

boot-loader update chassis chassis-number slot slot-number

Views

User view

Predefined user roles

network-admin

Parameters

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

chassis chassis-number slot slot-number: Specifies a standby MPU of the global active MPU. The chassis-number argument represents the IRF member ID of the device that holds the standby MPU. The slot-number argument represents the slot number of the standby MPU. (In IRF mode.)

Usage guidelines

You can use this command to fast synchronize startup images after adding new MPUs.

The startup images synchronized to the standby MPU are set as main startup images, regardless of whether the source startup images are main or backup.

In the following description, the term "active MPU" collectively refers to the active MPU in standalone mode and the global active MPU in IRF mode.

If the active MPU has started up with main startup images, its main startup images are synchronized to the standby MPU, regardless of whether any change has been made to this set of startup images.

If the active MPU has started up with backup startup images, its backup startup images are synchronized to the standby MPU, regardless of whether any change has been made to this set of startup images.

Startup image synchronization fails if any software image being synchronized is not available or has been corrupted.

If a patch installation or software upgrade has been performed in ISSU approach, use the install commit command to update the set of main startup images on the active MPU before software synchronization for startup image consistency between the active MPU and the standby MPU.

Examples

# In standalone mode, synchronize startup images from the active MPU to the standby MPU in slot 1.

<Sysname> boot-loader update slot 1

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

Updating. Please wait...

Copying main startup software images to slot 1. Please wait...

Done.

Setting copied images as main startup software images for slot 1...

Done.

Successfully updated the startup software images of slot 1.

# In IRF mode, synchronize startup images from the global active MPU to the MPU in slot 1 on IRF member device 1.

<Sysname> boot-loader update chassis 1 slot 1

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

Updating. Please wait...

Copying main startup software images to chassis 1 slot 1. Please wait...

Done.

Setting copied images as main startup software images for chassis 1 slot 1...

Done.

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

Related commands

·           display boot-loader

·           install commit

bootrom update

Use bootrom update to load the BootWare image in a storage medium (Flash memory or CF card) to the Normal area of BootWare.

Syntax

In standalone mode:

bootrom update file filename slot slot-number-list

In IRF mode:

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

Views

User view

Predefined user roles

network-admin

Parameters

file filename: Specifies the file that contains the BootWare image in a storage medium, Flash memory or CF card. The filename argument represents the file name, a string of 1 to 63 characters.

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. (In standalone mode.)

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

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 on the specified IRF member device. For example, slot 0 to 1 2. (In IRF mode.)

Usage guidelines

If a software upgrade requires upgrading the BootWare image, you can use this command to preload the new BootWare image to the BootWare before upgrading Comware images. This command helps shorten the subsequent upgrade time, reducing the risk of upgrade failure caused by unexpected electricity failure.

To complete the upgrade, reboot the device.

To save space, you can delete the BootWare image in the storage medium after completing the BootWare image upgrade.

Examples

# Use the file a.btw to upgrade the BootWare image.

<Sysname> bootrom update file a.btw slot 0

   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

display boot-loader

Use display boot-loader to display current software images and startup software images.

Syntax

In standalone mode:

display boot-loader [ slot slot-number ]

In IRF mode:

display boot-loader [ chassis chassis-number [ slot slot-number ] ]

Views

Any view

Predefined user roles

network-admin

network-operator

Parameters

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

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, and the slot-number argument represents the slot number of the MPU on the device. If no IRF member device is specified, this command displays the software images on each MPU in the IRF fabric. If an IRF member device is specified, but no MPU is specified, this command displays the software images on each MPU on the specified member device. (In IRF mode.)

Examples

# In standalone mode, display current software images and startup software images.

<Sysname> display boot-loader

Software images on slot 0:

Current software images:

  flash:/boot-r7122.bin

  flash:/system-r7122.bin

Main startup software images:

  flash:/boot-r7122.bin

  flash:/system-r7122.bin

  flash:/ssh-r7122.bin

Backup startup software images:

  flash:/boot-r7122.bin

  flash:/system-r7122.bin

# In IRF mode, displays current software images and startup software images.

<Sysname> display boot-loader

Software images on chassis 0 slot 1:

Current software images:

  flash:/boot-r7122.bin

  flash:/system-r7122.bin

Main startup software images:

  flash:/boot-r7122.bin

  flash:/system-r7122.bin

  flash:/ssh-r7122.bin

Backup startup software images:

  flash:/boot-r7122.bin

  flash:/system-r7122.bin

Table 1 Command output

Field	Description
Software images on slot slot-number	In standalone mode, displays the boot images and system images on the MPU in a specific slot.
Software images on chassis chassis-id slot slot-number	In IRF mode, displays the boot images and system images on a specific MPU. The chassis ID represents the IRF member ID, and the slot-number represents the MPU's slot number.
Current software images	Boot image and system image that have been loaded.
Main startup software images	Main boot image and system image to be loaded at the next startup.
Backup startup software images	Backup boot image and system image to be loaded at the next startup.

 

Related commands

boot-loader file

fan update

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

Syntax

In standalone mode:

fan update [ file filename ] tray { top | bottom }

In IRF mode:

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

Views

User view

Predefined user roles

network-admin

Parameters

file filename: Specifies the upgrade fan monitor file. The filename 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 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. The S12504 switch has only one fan tray, and it does not support the bottom keyword.

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

Usage guidelines

On the S12508 or S12518 switch, this command is available only for fan trays that use software version 103 and CPLD 002 (or above). For an S12504 switch, this command is available only for fan trays that use software version 202 (or above). To display this information, use the display fan verbose command.

In IRF mode, save the upgrade file on the active MPU that is in the same chassis as the fan tray you are upgrading.

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

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

·           Perform an active and standby switchover.

·           Execute the power-supply off command.

·           Power off the device.

·           Reboot or swap the active MPU.

On the S12508 or S12518 switch, after the fan update command is executed for one fan tray, you must remove and reinstall the fan tray before upgrading the other fan tray.

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

Examples

# Use the fan monitor software in the current software image to upgrade the fan monitor software of the top fan tray.

<Sysname> fan update tray top

The fan and power manage does not work during update period. Continue? [Y/N]:y

Begin to update fan, progress

OK!

Update the fan tray successfully, please reset by hand.

logic update

Use logic update to upgrade a CPLD on an interface card or MPU through the MBUS daughter card.

Syntax

In standalone mode:

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

In IRF mode:

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

Views

User view

Predefined user roles

network-admin

Parameters

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

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

logicid logicid: Specifies one of the following logic types:

·           0—Specifies the card (interface card or MPU) CPLD.

·           1—Specifies the 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 device. The chassis-number argument represents the ID of the IRF member device, and the slot-number argument represents the slot number of the card. To display the member IDs and slot numbers of IRF member devices, use the display device command. (In IRF mode.)

Usage guidelines

To upgrade the CPU CPLD on an interface card in an IRF fabric, you must save the upgrade file on the active MPU that is in the same chassis as the interface card.

Before upgrading the CPLD for an interface card, set the interface card in offline state by executing the board-offline command. For more information about the configurations, see "Managing the device."

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 or reboot the device.

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

If you are upgrading the OAM module CPLD on an MPU, you must reboot the MPU to run the new CPLD. If you are upgrading a card CPLD or CPU CPLD, the card automatically reboots.

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

Examples

# Upgrade the OAM module CPLD on the MPU in slot 0.

<Sysname> logic update slot 0 logicid 1

This command will last several minutes, please be patient, and it will reboot th

e board, continue? [Y/N]:y

Begin to update cpld, progress

OK!

CPLD is updated. Please reboot the specified slot to make it effective.

mbus update

Use mbus update to upgrade the MBUS daughter card software on a card.

Syntax

In standalone mode:

mbus update [ file filename ] slot slot-number

In IRF mode:

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

Views

User view

Predefined user roles

network-admin

Parameters

file filename: Specifies the MBUS daughter card software upgrade file. The filename 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 software image.

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

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

Usage guidelines

In an IRF fabric, save the upgrade file on the active MPU in the same chassis as the MBUS daughter card.

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 or reboot the device.

·           Reboot or swap the active MPU or the card that hosts the MBUS daughter card.

Examples

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

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

This command will reboot the specified mbus card, continue? [Y/N]:y

Begin to update mbus, progress

OK!

Update High

pmu update

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

Syntax

In standalone mode:

pmu update [ file filename ] pmu-id

In IRF mode:

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

Views

User view

Predefined user roles

network-admin

Parameters

file filename: Specifies an upgrade file for the power monitoring module. The filename argument represents the upgrade file name, a string of 1 to 63 characters. If no file name is specified, this command uses the .bin file contained in the current software image. In IRF mode, the specified upgrade file must be saved on the active MPU that is in the same chassis as the power monitoring module.

chassis chassis-number: Specifies the IRF member device bearing the power monitoring module whose software is to be upgraded. The chassis-number argument represents the ID of the IRF member device, which can be displayed with the display device command. (In IRF mode.)

pum-id: specifies the power monitoring module ID. On the S12504 or S12508 switch, the value is 1. On the S12518 switch, the value is 1 and 2.

Usage guidelines

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.

Examples

# Upgrade the software of the power monitoring module on the device in standalone mode.

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

The fan and power manage does not work during update period. Continue? [Y/N]:y

Begin to update pmu, progress

OK!

# Upgrade the software of power monitoring module 1 on member device 1 in IRF mode.

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

The fan and power manage does not work during update period. Continue? [Y/N]:y

Begin to update pmu, progress

OK!

power-logic update

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

Syntax

In standalone mode:

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

In IRF mode:

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

Views

User view

Predefined user roles

network-admin

Parameters

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

slot slot-number: Specifies the slot number of the card whose power software is to be upgraded. (In standalone mode.)

chassis chassis-number slot slot-number: Specifies card on the IRF member device whose power software is to be upgraded. The chassis-number argument represents the ID of the IRF member device, and the slot-number argument specifies the slot number of the card. You can display this information with the display device command. (In IRF mode.)

Usage guidelines

The command is not available for MPUs.

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.

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

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

This command will reboot the specified slot, continue? [Y/N]:y

OK!

Update power logic successfully.

version auto-update enable

Use version auto-update enable to enable software synchronization from the active MPU to the standby MPU at startup.

Use undo version auto-update enable to disable the function.

Syntax

version auto-update enable

undo version auto-update enable

Default

If software inconsistency is detected at startup, the standby MPU loads the current software images of the active MPU.

Views

System view

Predefined user roles

network-admin

Usage guidelines

This command is available in standalone mode.

To make sure the standby MPU always runs the same software images as the active MPU, configure both the version auto-update enable command and the undo version check ignore command.

The startup software version check function examines the standby MPU's startup software images for version inconsistency with the active MPU's current software images at startup. If their software versions are different, the standby MPU copies the current software images of the active MPU, specifies them as main startup software images, and reboots with these images.

Examples

# Enable software auto-update for the standby MPU.

<Sysname> system-view

[Sysname] version auto-update enable

Related commands

version check ignore

version check ignore

Use version check ignore to disable startup software version check for the standby MPU at startup.

Use undo version check ignore to enable this function.

Syntax

version check ignore

undo version check ignore

Default

The startup software images on the standby MPU are checked for version inconsistency with the current software images on the active MPU.

Views

System view

Predefined user roles

network-admin

Usage guidelines

This command is available in standalone mode.

When the standby MPU starts up, this command disables the system to examine the standby MPU's startup software images for version inconsistency with the active MPU's current software images. The standby MPU can start up with a different software version than the active MPU.

Even though you can use this command for upgrading software, H3C recommends the ISSU approach to software upgrade. The startup software version check function might fail to work because the software versions of the MPUs are incompatible.

To avoid anomalies, do not disable startup software version check for the standby MPU unless for software upgrade.

To make sure the standby MPU always runs the same software images as the active MPU, configure both the version auto-update enable command and the undo version check ignore command.

Examples

# Enable startup software version check for the standby MPU.

<Sysname> system-view

[Sysname] undo version check ignore

Related commands

version auto-update enable

v5to7 commit

Use v5to7 commit to commit the Comware V5-to-V7 software migration action.

Syntax

v5to7 commit

Views

User view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

 

CAUTION: If this command is executed, you will be unable to use the v5to7 rollback command to migrate back to Comware V5.

 

The software version for Comware V5 is S12500-CMW520-XXXXX, and the software version for Comware V7 is S12500-CMW710-XXXXX. (The cross marks represent the software version number.)

To configure Comware V7 features, you must commit the migration. Before that, you can use only read commands (such as display commands) and cannot configure Comware V7 features.

This command formats the Flash memory on each MPU, copies the backup files from the CF card back to the Flash memory, and depending on your choice, deletes the backup directory on the CF card.

To execute this command successfully and avoid configuration loss:

·           Execute the command in the Admin MDC.

·           Make sure you have executed the v5to7 upgrade command.

·           Verify that all cards in the system are in a normal state.

·           Make sure the system is not committing the migration or migrating back to Comware V5.

·           Do not perform any of the following actions before executing the v5to7 commit command:

¡  Formatting or partitioning the Flash memories or CF cards.

¡  Editing or deleting any files saved in the backup directory named flash_backup. This backup directory is in cfa0:/ on each MPU.

Examples

# In standalone mode, commit the Comware V5-to-V7 software migration action.

<Sysname> v5to7 commit

This operation will format Flash memory and take a long time to complete. Continue? [Y/N]:y

Do you want to delete the backup files on CF cards after this operation? [Y/N]:y

Step 1: Formatting Flash…

Slots: 0, 1.

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

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

Step 2: Copying backup files back to Flash…

Slots: 0, 1.

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

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

Step 3: Deleting backup files on the CF card…

Slots: 0, 1.

Slot 0: OK.

Slot 1: OK.

# In IRF mode, commit the Comware V5-to-V7 software migration action.

<Sysname> v5to7 commit

This operation will format Flash memory and take a long time to complete. Continue? [Y/N]:y

Do you want to delete the backup files on CF cards after this operation? [Y/N]:y

Step 1: Formatting Flash…

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

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 4: ………………………………OK.

Chassis 4 slot 5: ………………………………OK.

Step 2: Copying backup files back to Flash…

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

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 4: ………………………………OK.

Chassis 4 slot 5: ………………………………OK.

Step 3: Deleting backup files on the CF card…

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

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 4: OK.

Chassis 4 slot 5: OK.

Table 2 Command output

Field	Description
Slots:	Displays all cards that take the step.
Slot n: OK.	In standalone mode, the card in slot n has completed the step successfully. If failed is displayed instead of OK, the card has failed the step.
Chassis x slot n: OK.	In IRF mode, the card in slot n of chassis x has completed the step successfully. If failed is displayed instead of OK, the card has failed the step.

 

Related commands

·           v5to7 rollback

·           v5to7 upgrade  (Comware V5 fundamentals configuration guide)

v5to7 rollback

Use v5to7 rollback to migrate from Comware V7 back to Comware V5.

Syntax

v5to7 rollback

Views

User view

Predefined user roles

network-admin

mdc-admin

Usage guidelines

This command automatically restores the Comware V5 configuration.

To execute this command successfully:

·           Execute the command in the Admin MDC.

·           Make sure you have executed the v5to7 upgrade command but not the v5to7 commit command.

·           Verify that all cards in the system are in a normal state.

·           Verify that the Comware V5 startup software image is available from cfa0:/ on each MPU.

·           Make sure the system is not committing the migration or migrating back to Comware V5.

·           Before or during the rollback process, do not perform the following tasks:

¡  Formatting or partitioning the Flash memories or CF cards.

¡  Editing or deleting any files saved in the backup directory named flash_backup.

Examples

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

<Sysname> v5to7 rollback

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

Do you want to delete the backup files on CF cards after this operation? [Y/N]:y

Step 1: Setting the startup system software image file…

Slots: 0, 1.

Slot 0: OK.

Slot 1: OK.

Step 2: Deleting backup files on the CF card…

Slots: 0, 1.

Slot 0: OK.

Slot 1: OK.

Step 3: The system is rebooting…

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

<Sysname> v5to7 rollback

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

Do you want to delete the backup files on CF cards after this operation? [Y/N]:y

Step 1: Setting the startup system software image file…

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

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 4: OK.

Chassis 4 slot 5: OK.

Step 2: Deleting backup files on the CF card…

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

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 4: OK.

Chassis 4 slot 5: OK.

Step 3: The system is rebooting…

Table 3 Command output

Field	Description
Slots:	Displays all cards that take the step.
Slot n: OK.	In standalone mode, the card in slot n has completed the step successfully. If failed is displayed instead of OK, the card has failed the step.
Chassis x slot n: OK.	In IRF mode, the card in slot n of chassis x has completed the step successfully. If failed is displayed instead of OK, the card has failed the step.

 

Related commands

·           v5to7 commit

·           v5to7 upgrade (Comware V5 fundamentals configuration guide)