Software types include the BootWare image and startup software images. They are required for the device to start and run and provide support, management, and other services.

This image contains a basic segment and an extended segment. The basic segment is the minimum code that bootstraps the system. The extended segment enables hardware initialization and provides system management menus. When the device cannot start up correctly, you can use the menus to load software and the startup configuration file or manage files.

NOTE:

Typically, you do not need to upgrade the BootWare, and use the built-in BootWare of the router.

Startup software images

Startup software image subcategories

Startup software images include the following image subcategories:

· Boot image—A .bin file that contains the Linux operating system kernel. It provides process management, memory management, file system management, and the emergency shell.

· System image—A .bin file that contains the Comware kernel and standard features, including device management, interface management, configuration management, and routing.

· Feature image—A .bin file that contains advanced or customized software features.

· Patch image—A .bin file that is released for fixing bugs without rebooting the device. A patch image does not add or remove features.

The boot image and system image are required for the device to operate and cannot be uninstalled. A feature or patch image can be uninstalled.

Software release forms

Software images are released in one of the following forms:

· Separate .bin files. You must verify compatibility between software images.

· All startup software images except patch images are released as a whole in one .ipe package file. The images in an .ipe package file are compatible. The system decompresses the file automatically, loads the .bin images and sets them as startup software images.

Main and backup startup software images

To upgrade software, you must specify the upgrade files as the startup software images for the device to load at next startup. You can specify two lists of software images: one main and one backup. The device first loads the main startup software images. If the main startup software images are not available, the device loads the backup startup software images.

Software upgrade types

Software upgrade types include BootWare upgrade, startup software upgrade, and feature and patch installation.

Upgrade restrictions and guidelines

This document covers software upgrade procedures only for physical devices.

Unless otherwise noted, this document uses a standalone device to describe the upgrade procedures.

Hardware-related restrictions and guidelines

Before the upgrade, make sure the device is operating correctly, and make sure the LEDs of the power supply, fans, cards, and subcards are normal.

During the upgrade, do not power off the device, and do not restart or remove swappable modules.

If you store the startup software images in a hot swappable storage medium, do not remove the hot swappable storage medium during the startup process.

Read the release notes to verify the software and hardware compatibility and hardware restrictions for the device, cards, and subcards.

Software-related restrictions and guidelines

The command output varies by device model.

Before the upgrade:

· Use the release notes (software feature changes) to identify the differences between the new and old commands. Some functions might become unavailable due to command changes.

· Use the release notes to verify that the current software version can be upgraded to the target version.

· Back up the current software images, configuration files, and login passwords to prevent data loss if the storage medium is damaged.

· Make sure the device has sufficient storage space for the upgrade software images.

· Make sure the CPU usage of the device or a card is not high.

During the upgrade:

· Enable logging of the terminal to collect information.

· An upgrade requiring a device reboot will cause service interruption for the duration of the reboot.

· Before an upgrade operation is completed, no other upgrade operations can be performed. Upgrade operations include the install, issu, and boot-loader commands.

After the upgrade:

· The upgrade of the BootWare might cause the software version to fail to be downgraded.

· After the upgrade, do not delete the running software images.

Upgrade workflow

Figure 1 shows the upgrade workflow.

Figure 1 Upgrade workflow

Table 1 describes each step of the upgrade workflow.

Table 1 Upgrade method

Upgrade step	Remarks
Prepare for the upgrade	Describes the preparatory tasks to be performed before the upgrade (see "Preparing for the upgrade").
Is installing patches or features enough?	Checks whether installing patches or features can meet requirements. To fix bugs without upgrading the software version, install a patch. To add a new feature, install a feature.
Install patches or features	Describes the steps to install a patch or feature (see "Installing patches and features").
Does BootWare need to be upgraded?	Contact H3C Support to confirm whether the BootWare needs to be upgraded. If two software versions span many versions, the BootWare might need to be upgraded.
Upgrade BootWare	Describes the steps to upgrade the BootWare (see "Upgrading the BootWare").
Upgrade startup software	Describes the steps to upgrade the software version (see "Upgrading the startup software").
Check whether the upgrade is successful	Describes the checks to be performed after upgrade. If the upgrade fails, perform a version rollback. For more information, see "Verifying the upgrade."
Roll back the software version	Describes the steps to roll back the software version ("Rolling back the running software images").

Preparing for the upgrade

This chapter contains the following sections:

· Preparing tools

· Selecting an upgrade method

· Setting up an upgrade environment

· Logging in to the

· Obtaining the upgrade file

· Verifying the running software version

· Verifying the device operating status

· Backing up important files

· Checking the storage space

Preparing tools

Prepare the following tools:

· A terminal, such as a PC or laptop.

· Network cable and console cable.

· FTP server program or TFTP server program.

· Terminal emulation program.

NOTE:

The FTP server program or TFTP server program is not shipped with the router. Purpose it by yourself.

Selecting an upgrade method

Select an appropriate upgrade method as shown in Table 2 according to your situation.

Table 2 Upgrade method

Upgrade method	Software types	Remarks
Upgrading from the CLI by using the boot loader method	· Boot image · System image · IPE package · BootWare image	This method is disruptive. You must reboot the entire router to complete the upgrade.
Upgrading by using install commands	· Patch image · Feature image	This method does not require the reboot of the router and has a small impact on services.
Performing an ISSU from the CLI	· Boot image · System image · IPE package	This method is supported on an IRF fabric. This method has a small impact on services.
Upgrading from the BootWare menu	· IPE package · BootWare image	Use this method when the device cannot start up correctly. To use this method, you must log in to the router through the console port.

Setting up an upgrade environment

Set up an upgrade environment as follows:

1. Use the console cable to connect the serial port on the PC and the console port on the router.

2. Use the network cable to connect the network port on the PC and the management Ethernet port on the router.

NOTE:

If the router does not have a management Ethernet port, connect the network port on the PC and an Ethernet interface on the router.

Figure 2 Setting up an upgrade environment

Logging in to the router

To upgrade software from the BootWare menu, you can log in to the router through only the console port.

To upgrade software at the CLI, you can log in to the router through either the console port or the management Ethernet port. If the device does not have a management Ethernet port, you can log in to the router through a VLAN interface or Layer 3 Ethernet interface. The procedure for configuring a VLAN interface or Layer 3 Ethernet interface for login is similar to that for configuring the management Ethernet port.

Before you log in to the device through the console port, disable login authentication on the console port as a best practice.

Logging in to the router through the console port

1. Run a terminal emulation program on the PC and configure the following parameters:

¡ Bits per second—9600.

¡ Data bits—8.

¡ Stop bits—1.

¡ Parity—None.

¡ Flow control—None.

2. Power on the router. The following information is displayed. After you press Enter, the command prompt appears (such as <Sysname>).

****************************************************************************

* Without the owner's prior written consent, *

* no decompiling or reverse-engineering shall be allowed. *

****************************************************************************

Line aux0 is available.

Press ENTER to get started.

<Sysname>%Mar 30 09:52:58:243 2022 H3C SHELL/5/SHELL_LOGIN:TTY logged in from aux0.

Logging in to the router through the management Ethernet port

1. Log in to the router through the console port, enter system view, and enable the Telnet service.

<Sysname> system-view

[Sysname] telnet server enable

2. Assign an IP address to the management Ethernet port. The IP address must be in the same network segment as the IP address of the PC.

[Sysname] interface M-GigabitEthernet 0/0/0

[Sysname-M-GigabitEthernet0/0/0] ip address 192.168.0.105 24

[Sysname-M-GigabitEthernet0/0/0] quit

3. Configure common attributes for the VTY line.

[Sysname] line vty 0 63

[Sysname-line-vty0-63] authentication-mode none

[Sysname-line-vty0-63] user-role network-admin

[Sysname-line-vty0-63] idle-timeout 0 0

[Sysname-line-vty0-63] quit

4. Open the terminal emulation program on the PC, and log in to the router through Telnet.

****************************************************************************

* Without the owner's prior written consent, *

* no decompiling or reverse-engineering shall be allowed. *

****************************************************************************

Obtaining the upgrade file

CAUTION:

Make sure the obtained upgrade file is compatible with the device model. An incompatible software version can lead to a failure in the software upgrade.

You can obtain the upgrade file by using the following methods:

· Log in to the H3C website at https://www.h3c.com/en and navigate to Support > Resource Center > Software Download > Routers. Then, find the target router model and download its software image file.

· Contact H3C Support to obtain the upgrade file.

Verifying the running software version

# View the running software version on the router and use the release notes to verify that the running software version can be upgraded to the target software version.

The command output might vary by router model. This section uses a CR16000-F router as an example.

<Sysname> display version

H3C Comware Software, Version 7.1.075, Release 8260P22

H3C CR16010H-F uptime is 0 weeks, 0 days, 0 hours, 59 minutes

Last reboot reason : USER reboot

Boot image: cfa0:/CR16000-CMW710-BOOT-R8260P22.bin

Boot image version: 7.1.075, Release 8260P22

Compiled Dec 17 2021 11:00:00

System image: cfa0:/CR16000-CMW710-SYSTEM-R8260P22.bin

System image version: 7.1.075, Release 8260P22

Compiled Dec 17 2021 11:00:00

Feature image(s) list:

cfa0:/CR16000-CMW710-DEVKIT-R8260P22.bin, version: 7.1.075

Compiled Dec 17 2021 11:00:00

...

Verifying the device operating status

Verifying the device status

# Verify that the system is stable. The system is stable if the System State field displays Stable.

If the system is unstable, contact H3C Support to confirm whether the upgrade can be performed.

The command output might vary by router model. This section uses a CR16000-F router as an example.

<Sysname> display system stable state

System state : Stable

Redundancy state : No redundancy

Slot CPU Role State

0 0 Active Stable

6 0 Other Stable

6 1 Other Stable

13 0 Other Stable

Verifying the card or subcard status

# Verify that the status of a card or subcard is normal. The card or subcard is normal if the Brd Status field displays Normal.

If the status of a card or subcard is abnormal, contact H3C Support to confirm whether the card or subcard needs to be replaced, and record the status of the card or subcard.

The command output might vary by router model. This section uses a CR16000-F router as an example.

<Sysname> display device

Slot No. Brd Type Brd Status Software Version

0 CSR05SRP1P3 Master CR16000-CMW710-R8260P22

1 NONE Absent NONE

2 NONE Absent NONE

3 NONE Absent NONE

4 CSPEX-1504X Normal CR16000-CMW710-R8260P22

5 NONE Absent NONE

6 CSPEX-1504X Normal CR16000-CMW710-R8260P22

7 NONE Absent NONE

8 NONE Absent NONE

9 NONE Absent NONE

10 NONE Absent NONE

11 NONE Absent NONE

12 NONE Absent NONE

13 CSFC-08E1 Normal CR16000-CMW710-R8260P22

14 NONE Absent NONE

Verifying the CPU usage

# Verify that the CPU usage is lower than 80%.

The command output might vary by router model. This section uses a CR16000-F router as an example.

<Sysname> display cpu-usage

Slot 1 CPU 0 CPU usage:

1% in last 5 seconds

1% in last 1 minute

1% in last 5 minutes

Verifying the alarm information

# Use the display alarm command to verify that no alarms are generated for the router, cards, and subcards.

If an alarm of the Error level exists, contact H3C Support to confirm whether the upgrade can be performed.

NOTE:

The display alarm command is supported only some router models. On router models that do not support the display alarm command, you can use the display logbuffer command to view the alarm information in buffered logs.

Backing up important files

Back up the current software images, configuration files, and login passwords.

This section uses backing up configuration files in the CF card as an example.

# Save the running configuration to the CF card.

<Sysname> save

The current configuration will be written to the device. Are you sure? [Y/N]:y

Please input the file name(*.cfg)[cfa0:/startup.cfg]

(To leave the existing filename unchanged, press the enter key):cfa0:/startup.cfg

Validating file. Please wait.........................

The current configuration is saved to the active main board successfully.

Configuration is saved to device successfully.

# Back up all files (including configuration files and log files) to the PC through FTP.

NOTE:

The operation of uploading files by using FTP is similar to that of uploading files by using TFTP. This section uses FTP as an example. For the detailed uploading operation, see "Downloading the upgrade file."

<Sysname>ftp 192.168.33.77

Trying 192.168.33.77 ...

Press CTRL+K to abort

Connected to 192.168.33.77.

220 3Com 3CDaemon FTP Server Version 2.0

User(192.168.33.77:(none)):Username1

331 User name ok, need password

Password:

230 User logged in

ftp> binary

200 Type is Image (Binary)

ftp> put startup.cfg

227 Entering Passive Mode (192,168,77,3,8,222)

150 "D:\FTP\ startup.cfg " file ready to receive in BIN mode

226 Transfer finished successfully.

FTP: 6360 byte(s) sent in 0.170 second(s), 37.00Kbyte(s)/sec.

Checking the storage space

Check the free storage space of the storage medium to which the upgrade file will be saved to verify that the router has sufficient storage for the upgrade file.

If the free storage space is not sufficient on the router, delete unused files.

If an .ipe file is used, make sure the free storage space is greater than the sum of the size of the .ipe file and the size of the .bin files decompressed. If the free storage space is insufficient, you can download only the required .bin files (including the boot image and system image).

If the storage medium can only store software images in one version, you can first delete the software images in the old version, and then directly download the .bin files in the new version (including the boot and system images).

Checking the storage space at the CLI

Identifying the storage medium

# Use the display boot-loader command to identify the storage medium. The following command output shows that the storage medium is the CF card.

The command output might vary by router model. This section uses a CR16000-F router as an example.

<Sysname> display boot-loader

Software images on slot 0:

Current software images:

cfa0:/CR16000-CMW710-BOOT-R8260P22.bin

cfa0:/CR16000-CMW710-SYSTEM-R8260P22.bin

Main startup software images:

cfa0:/CR16000-CMW710-BOOT-R8260P22.bin

cfa0:/CR16000-CMW710-SYSTEM-R8260P22.bin

Backup startup software images:

cfa0:/CR16000-CMW710-BOOT-R7751P01.bin

cfa0:/CR16000-CMW710-SYSTEM-R7751P01.bin

Verifying the free storage space

# Use the dir command to view the free storage space.

The command output might vary by router model. This section uses a CR16000-F router as an example.

NOTE:

If the dir command does not display the file information on the storage medium of startup software images by default, first use the cd command to access the storage medium of the startup software images.

<Sysname> cd cfa0:/

<Sysname> dir

Directory of cfa0:

0 -rw- 40403968 Aug 24 2021 13:03:11 CR16000-CMW710-BOOT-R8260P22.bin

1 -rw- 40434688 Sep 27 2021 12:43:18 CR16000-CMW710-BOOT-R7751P01.bin

...

6 -rw- 361966592 Aug 24 2021 13:11:46 CR16000-CMW710-SYSTEM-R8260P22.bin

7 -rw- 354719744 Sep 27 2021 12:50:55 CR16000-CMW710-SYSTEM-R7751P01.bin

2044256 KB total (1773684 KB free)

Deleting unused files

· Use the delete /unreserved command to delete an unused file permanently.

<Sysname> delete /unreserved boot.bin

The file cannot be restored. Delete cfa0:/boot.bin? [Y/N]:y

Deleting the file permanently will take a long time. Please wait...

Deleting file cfa0:/boot.bin...Done.

· Use the delete command to delete an unused file.

# Delete an unused file.

<Sysname> delete boot.bin

Delete cfa0:/boot.bin? [Y/N]:y

Deleting file cfa0:/boot.bin...Done.

# Clear the recycle bin.

<Sysname> reset recycle-bin

Clear cfa0:/boot.bin? [Y/N]:y

Clearing file cfa0:/boot.bin... Done

NOTE:

To delete a file permanently, use the delete /unreserved command. If you use the delete command, the file is moved to the recycle bin and still occupies the storage space. To release the storage space, you must execute the reset recycle-bin command in the file's original directory.

Checking the storage space from the BootWare menu

Identifying the storage medium from the BootWare menu

NOTE:

The BootWare menu varies by router model and BootWare version. This section uses a CR16000-F router as an example.

· Identify the storage medium from the EXTENDED-BOOTWARE menu.

a. Access the EXTENDED-BOOTWARE menu.

==========================<EXTENDED-BOOTWARE MENU>==========================

|<1> Boot System |

|<2> Enter Serial SubMenu |

|<3> Enter Ethernet SubMenu |

|<4> File Control |

|<5> Restore to Factory Default Configuration |

|<6> Skip Current System Configuration |

|<7> BootWare Operation Menu |

|<8> Skip Authentication for Console Login |

|<9> Storage Device Operation |

|<0> Reboot |

============================================================================

Ctrl+Z: Access EXTENDED ASSISTANT MENU

Ctrl+C: Display Copyright

Ctrl+F: Format File System

Enter your choice(0-9):

b. Enter 4 to access the file control submenu.

===============================<File CONTROL>===============================

|Note:the operating device is cfa0 |

|<1> Display All File(s) |

|<2> Set Image File type |

|<3> Set Bin File type |

|<4> Delete File |

|<5> Copy File |

|<0> Exit To Main Menu |

============================================================================

Enter your choice(0-5):

c. Enter 1 to display all files.

Display all file(s) in cfa0:

'M' = MAIN 'B' = BACKUP 'N/A' = NOT ASSIGNED

============================================================================

|1 33086464 Nov/15/2021 17:21:50 M cfa0:/CR16000-CMW710-BOOT-R8260P|

|22.bin |

|2 278083584 Nov/15/2021 17:15:07 M cfa0:/CR16000-CMW710-SYSTEM-R826|

|0P22.bin |

|3 6952 Nov/15/2021 18:36:51 N/A cfa0:/info/info_5_3.bin |

============================================================================

===============================<File CONTROL>===============================

|Note:the operating device is cfa0 |

|<1> Display All File(s) |

|<2> Set Image File type |

|<3> Set Bin File type |

|<4> Delete File |

|<5> Copy File |

|<0> Exit To Main Menu |

============================================================================

Enter your choice(0-5):

d. Enter 0 to exit the file control submenu.

The image file of the M type shows that the storage medium is the CF card. If no image file is the M type, change the storage device to be operated.

· Change the storage device to be operated.

e. Access the EXTENDED-BOOTWARE menu.

==========================<EXTENDED-BOOTWARE MENU>==========================

|<1> Boot System |

|<2> Enter Serial SubMenu |

|<3> Enter Ethernet SubMenu |

|<4> File Control |

|<5> Restore to Factory Default Configuration |

|<6> Skip Current System Configuration |

|<7> BootWare Operation Menu |

|<8> Skip Authentication for Console Login |

|<9> Storage Device Operation |

|<0> Reboot |

============================================================================

Ctrl+Z: Access EXTENDED ASSISTANT MENU

Ctrl+F: Format File System

Ctrl+C: Display Copyright

Enter your choice(0-9):

f. Enter 9 to access the storage device submenu.

==============================<DEVICE CONTROL>==============================

|<1> Display All Available Nonvolatile Storage Device(s) |

|<2> Set The Operating Device |

|<3> Set The Default Boot Device |

|<0> Exit To Main Menu |

============================================================================

Enter your choice(0-3):

g. Enter 2 to set the operated storage medium.

Please set the operating device:

============================================================================

|Note:the operating device is cfa0 |

|NO. Device Name File System Total Size Available Space |

|1 flash JFFS2 262144KB 224937KB |

|2 cfa0 FAT 2044256KB 1173684KB |

|0 Exit |

============================================================================

Enter your choice(0-2):

h. Enter 2 to set the operated storage medium to CF card.

==============================<DEVICE CONTROL>==============================

|<1> Display All Available Nonvolatile Storage Device(s) |

|<2> Set The Operating Device |

|<3> Set The Default Boot Device |

|<0> Exit To Main Menu |

============================================================================

Enter your choice(0-3):

i. Enter 3 to set the default storage medium.

Please set the default device:

============================================================================

|Note:the default device is cfa0 |

|NO. Device Name File System Total Size Available Space |

|1 flash JFFS2 262144KB 224937KB |

|2 cfa0 FAT 2044256KB 1173684KB |

|0 Exit |

============================================================================

Enter your choice(0-2):

j. Enter 2 to set the default storage medium to CF card.

==============================<DEVICE CONTROL>==============================

|<1> Display All Available Nonvolatile Storage Device(s) |

|<2> Set The Operating Device |

|<3> Set The Default Boot Device |

|<0> Exit To Main Menu |

============================================================================

Enter your choice(0-3):

k. Enter 0 to exit the storage device submenu.

Verifying the free storage space

NOTE:

The BootWare menu varies by router model and BootWare version. This section uses a CR16000-F router as an example.

# Access the EXTENDED-BOOTWARE menu.

==========================<EXTENDED-BOOTWARE MENU>==========================

|<1> Boot System |

|<2> Enter Serial SubMenu |

|<3> Enter Ethernet SubMenu |

|<4> File Control |

|<5> Restore to Factory Default Configuration |

|<6> Skip Current System Configuration |

|<7> BootWare Operation Menu |

|<8> Skip Authentication for Console Login |

|<9> Storage Device Operation |

|<0> Reboot |

============================================================================

Ctrl+Z: Access EXTENDED ASSISTANT MENU

Ctrl+F: Format File System

Ctrl+C: Display Copyright

Enter your choice(0-9):

# Enter 9 to access the storage device submenu.

==============================<DEVICE CONTROL>==============================

|<1> Display All Available Nonvolatile Storage Device(s) |

|<2> Set The Operating Device |

|<3> Set The Default Boot Device |

|<0> Exit To Main Menu |

============================================================================

Enter your choice(0-3):

# Enter 1 to view the free storage space.

Display all available nonvolatile storage device(s):

============================================================================

|NO. Device Name File System Total Size Available Space |

|1 flash JFFS2 262144KB 224937KB |

|2 cfa0 FAT 2044256KB 1173684KB |

============================================================================

Deleting unused files

NOTE:

The BootWare menu varies by router model and BootWare version. This section uses a CR16000-F router as an example.

# Access the EXTENDED-BOOTWARE menu.

==========================<EXTENDED-BOOTWARE MENU>==========================

|<1> Boot System |

|<2> Enter Serial SubMenu |

|<3> Enter Ethernet SubMenu |

|<4> File Control |

|<5> Restore to Factory Default Configuration |

|<6> Skip Current System Configuration |

|<7> BootWare Operation Menu |

|<8> Skip Authentication for Console Login |

|<9> Storage Device Operation |

|<0> Reboot |

============================================================================

Ctrl+Z: Access EXTENDED ASSISTANT MENU

Ctrl+F: Format File System

Ctrl+C: Display Copyright

Enter your choice(0-9):

# Enter 4 to access the File Control submenu.

===============================<File CONTROL>===============================

|Note:the operating device is cfa0 |

|<1> Display All File(s) |

|<2> Set Image File type |

|<3> Set Bin File type |

|<4> Delete File |

|<5> Copy File |

|<0> Exit To Main Menu |

============================================================================

Enter your choice(0-5):

# Enter 4, and enter the number of the file to delete.

Deleting the file in cfa0:

'M' = MAIN 'B' = BACKUP 'N/A' = NOT ASSIGNED

============================================================================

|NO. Size(B) Time Type Name |

|1 361966592 Aug/24/2021 13:04:32 N/A cfa0:/CR16000-CMW710-SYSTEM-R826|

|0P22.bin |

|2 24333312 Aug/24/2021 13:04:03 N/A cfa0:/CR16000-CMW710-PACKET-CAPT|

|URE-R8260P22.bin |

|0 Exit |

============================================================================

Enter file No.:2

The file you selected is

cfa0:/CR16000-CMW710-PACKET-CAPTURE-R8260P22.bin,Delete it? [Y/N]Y

Deleting....................................................Done.

Upgrading the BootWare

You can upgrade the BootWare at the CLI or from the BootWare menu.

· Upgrading the BootWare at the CLI on a single-MPU device (distributed devices in standalone mode)

· Upgrading the BootWare at the CLI on a dual-MPU device (distributed devices in standalone mode)

· Upgrading the BootWare at the CLI (distributed devices in IRF mode)

· Upgrading the BootWare at the CLI (centralized devices)

· Upgrading the BootWare from the BootWare menu

Upgrading the BootWare at the CLI on a single-MPU device (distributed devices in standalone mode)

Upgrade workflow

Figure 3 Upgrade workflow

Upgrade procedure

Commands might slightly vary by router model. This section uses a CR16000-F router as an example.

Preparing for the upgrade

See "Preparing for the upgrade."

Downloading the upgrade file

Download the upgrade file from an PC to the router. For more information, see "Downloading the upgrade file."

Decompressing the .ipe file

If the upgrade file for upgrading the BootWare is in an .ipe file, decompress the .ipe file and save the decompressed files in the root directory of the storage medium on the router.

<Sysname>install add cfa0:/newest.ipe cfa0:

Verifying image file...Done.

This operation will take several minutes, please wait...........................

....................................................Done.

A boot image and a system image are generated in in the root directory of the storage medium after decompression.

Upgrading the BootWare

# Upgrade the BootWare on the MPU in slot 0.

<Sysname> bootrom update file cfa0:/CR16000-CMW710-BOOT-R8260P22.bin slot 0

This command will update bootrom file on the specified board(s),

Continue? [Y/N]:y

Now updating the Boot ROM, please wait........... ...........Done

# Upgrade the BootWare on the service module in slot 3. The upgrade step for other service modules is the same.

<Sysname> bootrom update file cfa0:/CR16000-CMW710-BOOT-R8260P22.bin slot 3

This command will update bootrom file on the specified board(s),

Continue? [Y/N]:y

Now updating the Boot ROM, please wait........... ...........Done

# Upgrade the BootWare on the switching fabric module in slot 6. The upgrade step for other switching fabric modules is the same.

<Sysname> bootrom update file cfa0:/CR16000-CMW710-BOOT-R8260P22.bin slot 6

This command will update bootrom file on the specified board(s),

Continue? [Y/N]:y

Now updating the Boot ROM, please wait........... ...........Done

Rebooting the router

# Reboot the router to complete the BootWare upgrade.

<Sysname> reboot

Start to check configuration with next startup configuration file, please wait.

........DONE!

This command will reboot the device. Continue? [Y/N]:y

Now rebooting, please wait...

Upgrading the BootWare at the CLI on a dual-MPU device (distributed devices in standalone mode)

Upgrade workflow

Figure 4 Upgrade workflow

Upgrade procedure

Commands might slightly vary by router model. This section uses a CR16000-F router as an example.

Preparing for the upgrade

See "Preparing for the upgrade."

Downloading the upgrade file

Download the upgrade file from an PC to the router. For more information, see "Downloading the upgrade file."

Decompressing the .ipe file

If the upgrade file for upgrading the BootWare is in an .ipe file, decompress the .ipe file and save the decompressed files in the root directory of the storage medium on the router.

<Sysname>install add cfa0:/newest.ipe cfa0:

Verifying image file...Done.

This operation will take several minutes, please wait...........................

....................................................Done.

A boot image and a system image are generated in in the root directory of the storage medium after decompression.

Upgrading the BootWare

# Upgrade the BootWare on the active MPU in slot 0 and standby MPU in slot 1.

<Sysname> bootrom update file cfa0:/CR16000-CMW710-BOOT-R8260P22.bin slot 0

This command will update bootrom file on the specified board(s),

Continue? [Y/N]:y

Now updating the Boot ROM, please wait........... ...........Done

<Sysname> bootrom update file cfa0:/CR16000-CMW710-BOOT-R8260P22.bin slot 1

This command will update bootrom file on the specified board(s),

Continue? [Y/N]:y

Now updating the Boot ROM, please wait........... ...........Done

# Upgrade the BootWare on the service module in slot 3. The upgrade step for other service modules is the same.

<Sysname> bootrom update file cfa0:/CR16000-CMW710-BOOT-R8260P22.bin slot 3

This command will update bootrom file on the specified board(s),

Continue? [Y/N]:y

Now updating the Boot ROM, please wait........... ...........Done

# Upgrade the BootWare on the switching fabric module in slot 6. The upgrade step for other switching fabric modules is the same.

<Sysname> bootrom update file cfa0:/CR16000-CMW710-BOOT-R8260P22.bin slot 6

This command will update bootrom file on the specified board(s),

Continue? [Y/N]:y

Now updating the Boot ROM, please wait........... ...........Done

Rebooting the router

# Reboot the router to complete the BootWare upgrade.

<Sysname> reboot

Start to check configuration with next startup configuration file, please wait.

........DONE!

This command will reboot the device. Continue? [Y/N]:y

Now rebooting, please wait...

Upgrading the BootWare at the CLI (distributed devices in IRF mode)

NOTE:

· In this section, the IRF fabric has two member devices, and each member device has two MPUs.

· The upgrade procedure for single-MPU devices is the same as that for dual-MPU devices.

Upgrade workflow

Figure 5 Upgrade workflow

Upgrade procedure

Commands might slightly vary by router model. This section uses a CR16000-F router as an example.

Preparing for the upgrade

See "Preparing for the upgrade."

Downloading the upgrade file

Download the upgrade file from an PC to the router. For more information, see "Downloading the upgrade file."

Decompressing the .ipe file

If the upgrade file for upgrading the BootWare is in an .ipe file, decompress the .ipe file and save the decompressed files in the root directory of the storage medium on the router.

<Sysname>install add cfa0:/newest.ipe cfa0:

Verifying image file...Done.

This operation will take several minutes, please wait...........................

....................................................Done.

A boot image and a system image are generated in in the root directory of the storage medium after decompression.

Upgrading the BootWare

# Upgrade the BootWare on the all MPUs in the IRF fabric.

<Sysname> bootrom update file cfa0:/CR16000-CMW710-BOOT-R8260P22.bin chassis 1 slot 0

This command will update bootrom file on the specified board(s),

Continue? [Y/N]:y

Now updating the Boot ROM, please wait........... ...........Done

<Sysname> bootrom update file cfa0:/CR16000-CMW710-BOOT-R8260P22.bin chassis 1 slot 1

This command will update bootrom file on the specified board(s),

Continue? [Y/N]:y

Now updating the Boot ROM, please wait........... ...........Done

<Sysname> bootrom update file cfa0:/CR16000-CMW710-BOOT-R8260P22.bin chassis 2 slot 0

This command will update bootrom file on the specified board(s),

Continue? [Y/N]:y

Now updating the Boot ROM, please wait........... ...........Done

<Sysname> bootrom update file cfa0:/CR16000-CMW710-BOOT-R8260P22.bin chassis 2 slot 1

This command will update bootrom file on the specified board(s),

Continue? [Y/N]:y

Now updating the Boot ROM, please wait........... ...........Done

# Upgrade the BootWare on the service module in slot 3 of chassis 1. The upgrade step for other service modules is the same.

<Sysname> bootrom update file cfa0:/CR16000-CMW710-BOOT-R8260P22.bin chassis 1 slot 3

This command will update bootrom file on the specified board(s),

Continue? [Y/N]:y

Now updating the Boot ROM, please wait........... ...........Done

# Upgrade the BootWare on the switching fabric module in slot 6 of chassis 1. The upgrade step for other switching fabric modules is the same.

<Sysname> bootrom update file cfa0:/CR16000-CMW710-BOOT-R8260P22.bin chassis 1 slot 6

This command will update bootrom file on the specified board(s),

Continue? [Y/N]:y

Now updating the Boot ROM, please wait........... ...........Done

Rebooting the router

# Reboot the router to complete the BootWare upgrade.

<Sysname> reboot

Start to check configuration with next startup configuration file, please wait.

........DONE!

This command will reboot the device. Continue? [Y/N]:y

Now rebooting, please wait...

Upgrading the BootWare at the CLI (centralized devices)

Upgrade workflow

Figure 6 Upgrade workflow

Upgrade procedure

Commands might slightly vary by router model. This section uses an MSR 2600 router as an example.

Preparing for the upgrade

See "Preparing for the upgrade."

Downloading the upgrade file

Download the upgrade file from an PC to the router. For more information, see "Downloading the upgrade file."

Decompressing the .ipe file

If the upgrade file for upgrading the BootWare is in an .ipe file, decompress the .ipe file and save the decompressed files in the root directory of the storage medium on the router.

<Sysname>install add flash:/newest.ipe flash:

Verifying image file...Done.

This operation will take several minutes, please wait...........................

....................................................Done.

A boot image and a system image are generated in in the root directory of the storage medium after decompression.

Upgrading the BootWare

# Upgrade the BootWare on the router.

<Sysname> bootrom update file flash:/msr26-CMW710-BOOT-R0821P18.bin 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.

Rebooting the router

# Reboot the router to complete the BootWare upgrade.

<Sysname> reboot

Start to check configuration with next startup configuration file, please wait.

........DONE!

This command will reboot the device. Continue? [Y/N]:y

Now rebooting, please wait...

Upgrading the BootWare from the BootWare menu

Upgrade workflow

Figure 7 Upgrade workflow

Upgrade procedure

Preparing for the upgrade

See "Preparing for the upgrade."

Downloading and upgrading the BootWare from the BootWare menu

NOTE:

· The BootWare menu varies by router model and BootWare version. This section uses a CR16000-F router as an example.

· The operation of downloading an image file through FTP is similar to that through TFTP. This section uses FTP as an example.

1. Run the FTP server program on a PC (its IP address is 192.168.0.23), set the working directory, FTP username, and password. Store the upgrade file on the working directory of the FTP server.

2. Run the terminal emulation program on the PC, and power on the router. Press Ctrl+B at prompt to access the EXTENDED-BOOTWARE menu.

==========================<EXTENDED-BOOTWARE MENU>==========================

|<1> Boot System |

|<2> Enter Serial SubMenu |

|<3> Enter Ethernet SubMenu |

|<4> File Control |

|<5> Restore to Factory Default Configuration |

|<6> Skip Current System Configuration |

|<7> BootWare Operation Menu |

|<8> Skip Authentication for Console Login |

|<9> Storage Device Operation |

|<0> Reboot |

============================================================================

Ctrl+Z: Access EXTENDED ASSISTANT MENU

Ctrl+F: Format File System

Ctrl+C: Display Copyright

Enter your choice(0-9):

3. (Optional.) Set the default storage medium.

IMPORTANT:

If the storage medium storing the BootWare image file is not the default storage medium, set it as the default storage medium.

# Enter 9 to access the storage device submenu.

==============================<DEVICE CONTROL>==============================

|<1> Display All Available Nonvolatile Storage Device(s) |

|<2> Set The Operating Device |

|<3> Set The Default Boot Device |

|<0> Exit To Main Menu |

============================================================================

Enter your choice(0-3):

# Enter 2 to set the storage medium for storing the BootWare image file.

Please set the operating device:

============================================================================

|Note:the operating device is cfa0 |

|NO. Device Name File System Total Size Available Space |

|1 flash JFFS2 262144KB 224937KB |

|2 cfa0 FAT 2044256KB 1173684KB |

|0 Exit |

============================================================================

Enter your choice(0-2):

# Enter 2 to configure the CF card as the storage medium for storing the BootWare image file.

==============================<DEVICE CONTROL>==============================

|<1> Display All Available Nonvolatile Storage Device(s) |

|<2> Set The Operating Device |

|<3> Set The Default Boot Device |

|<0> Exit To Main Menu |

============================================================================

Enter your choice(0-3):

# Enter 3 to set the default storage medium.

Please set the default device:

============================================================================

|Note:the default device is cfa0 |

|NO. Device Name File System Total Size Available Space |

|1 flash JFFS2 262144KB 224937KB |

|2 cfa0 FAT 2044256KB 1173684KB |

|0 Exit |

============================================================================

Enter your choice(0-2):

# Enter 2 to configure the CF card as the default storage medium.

==============================<DEVICE CONTROL>==============================

|<1> Display All Available Nonvolatile Storage Device(s) |

|<2> Set The Operating Device |

|<3> Set The Default Boot Device |

|<0> Exit To Main Menu |

============================================================================

Enter your choice(0-3):

# Enter 0 to exit the storage device submenu.

4. Download and upgrade the BootWare.

==========================<EXTENDED-BOOTWARE MENU>==========================

|<1> Boot System |

|<2> Enter Serial SubMenu |

|<3> Enter Ethernet SubMenu |

|<4> File Control |

|<5> Restore to Factory Default Configuration |

|<6> Skip Current System Configuration |

|<7> BootWare Operation Menu |

|<8> Skip Authentication for Console Login |

|<9> Storage Device Operation |

|<0> Reboot |

============================================================================

Ctrl+Z: Access EXTENDED ASSISTANT MENU

Ctrl+F: Format File System

Ctrl+C: Display Copyright

Enter your choice(0-9):

# Enter 7 to access the BootWare Operation submenu.

=========================<BootWare Operation Menu>==========================

|Note:the operating device is cfa0 |

|<1> Backup Full BootWare |

|<2> Restore Full BootWare |

|<3> Update BootWare By Serial |

|<4> Update BootWare By Ethernet |

|<0> Exit To Main Menu |

============================================================================

Enter your choice(0-4):

# Enter 4 to access the Ethernet submenu.

===================<BOOTWARE OPERATION ETHERNET SUB-MENU>===================

|<1> Update Full BootWare |

|<2> Update Extended BootWare |

|<3> Update Basic BootWare |

|<4> Modify Ethernet Parameter |

|<0> Exit To Main Menu |

============================================================================

Enter your choice(0-4):

# Enter 4 to configure the network settings.

NOTE:

To use the existing setting for a field, press Enter without modifying the setting.

==========================<ETHERNET PARAMETER SET>==========================

|Note: '.' = Clear field. |

| '-' = Go to previous field. |

| Ctrl+D = Quit. |

============================================================================

Protocol (FTP or TFTP) :ftp

Load File Name :test.btw

:mpu.btw

Target File Name :test.btw

:mpu.btw

Server IP Address :192.168.0.23

Local IP Address :192.168.0.105

Subnet Mask :255.255.255.0

Gateway IP Address :0.0.0.0

FTP User Name :xxx

FTP User Password :***

Table 3 Network parameter fields and shortcut keys

Field	Description
'.' = Clear field	Press a dot (.) and then press Enter to clear the setting for a field.
'-' = Go to previous field	Press a hyphen (-) and then press Enter to return to the previous field.
Ctrl+D = Quit	Press Ctrl+D to exit the ETHERNET PARAMETER SET menu.
Protocol (FTP or TFTP)	Set the file transfer protocol to FTP or TFTP.
Load File Name	Set the name of the file to be downloaded.
Target File Name	Set a file name for saving the file on the router. The target file name must have the same extension as the source file. By default, the target file name is the same as the source file name.
Server IP Address	Set the IP address of the FTP or TFTP server.
Local IP Address	Set the IP address of the Ethernet interface that connects to the TFTP server.
Subnet Mask	Set the IP address mask.
Gateway IP Address	Set a gateway IP address if the router is on a different network than the server.

After you finish setting the FTP parameters, the system returns to the BOOTWARE OPERATION ETHERNET submenu.

===================<BOOTWARE OPERATION ETHERNET SUB-MENU>===================

|<1> Update Full BootWare |

|<2> Update Extended BootWare |

|<3> Update Basic BootWare |

|<4> Modify Ethernet Parameter |

|<0> Exit To Main Menu |

============================================================================

Enter your choice(0-4):

# Choose an option from options 1 to 3. For example, enter 1 to upgrade the entire BootWare image.

Loading...........Done!

447612 bytes downloaded!

Updating Basic BootWare? [Y/N]

# Enter Y to upgrade the basic BootWare segment.

Updating Basic BootWare.........Done!

Updating Extended BootWare? [Y/N]

# Enter Y to upgrade the extended BootWare segment.

Updating Extended BootWare.........Done!

===================<BOOTWARE OPERATION ETHERNET SUB-MENU>===================

|<1> Update Full BootWare |

|<2> Update Extended BootWare |

|<3> Update Basic BootWare |

|<4> Modify Ethernet Parameter |

|<0> Exit To Main Menu |

============================================================================

Enter your choice(0-4):

Rebooting the router

# Enter 0 to return to the BootWare Operation menu.

# Enter 0 in the BootWare Operation menu to return to the EXTENDED-BOOTWARE menu.

# Enter 0 in the EXTENDED-BOOTWARE menu to reboot the router.

NOTE:

For a modular router that has an active MPU and a standby MPU, you must access the BootWare menus of them through the console port to upgrade their BootWares. You also need to connect to the management Ethernet ports on both MPUs.

Upgrading the startup software

You can upgrade the startup software by using the following methods:

· Upgrading the startup software by using the boot loader method

· Upgrading the startup software from the BootWare menu

· Performing a compatible upgrade by using ISSU commands (distributed devices)

· Performing a compatible upgrade by using ISSU commands (centralized devices)

· Performing an incompatible upgrade by using ISSU commands (distributed devices)

· Performing an incompatible upgrade by using ISSU commands (centralized devices)

Upgrading the startup software by using the boot loader method

Upgrade workflow

Table 4 Upgrade workflow

Upgrade procedure

Preparing for the upgrade

See "Preparing for the upgrade."

Downloading the upgrade file

Download the upgrade file from an PC to the router. For more information, see "Downloading the upgrade file."

Upgrading the startup software

NOTE:

· You can specify an .ipe file or a boot image file and a system image file in the boot-loader file command. This section uses an .ipe file as an example.

· Available commands vary by router model. This section uses a CR16000-F router as an example.

· The upgrade procedure for single-MPU devices is the same as that for dual-MPU devices.

# Specify an .ipe file as the main startup software file.

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

Verifying the file flash:/all.ipe on slot 1..............Done.

H3C CR16010H-F images in IPE:

boot.bin

system.bin

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

# Specify an .ipe file as the backup startup software file.

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

Verifying the file flash:/all2.ipe on slot 1..............Done.

H3C CR16010H-F images in IPE:

boot.bin

system.bin

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

Rebooting the router

# Reboot the router to complete the upgrade.

<Sysname> reboot

Start to check configuration with next startup configuration file, please wait.

........DONE!

This command will reboot the device. Continue? [Y/N]:y

Now rebooting, please wait...

Upgrading the startup software from the BootWare menu

Upgrade workflow

Table 5 Upgrade workflow

Upgrade procedure

Preparing for the upgrade

See "Preparing for the upgrade."

Downloading the upgrade file

Download the upgrade file from an PC to the router. For more information, see "Downloading the upgrade file."

Rebooting the router

# Return to the EXTENDED-BOOTWARE menu, and enter 0 in the EXTENDED-BOOTWARE menu to reboot the router.

NOTE:

For a modular router that has an active MPU and a standby MPU, you must access the BootWare menus of them through the console port to upgrade their startup software. You also need to connect to the management Ethernet ports on both MPUs.

Performing a compatible upgrade by using ISSU commands (distributed devices)

NOTE:

· Before performing an ISSU, you must use the display version comp-matrix command to identify the recommended ISSU methods.

· In this section, the IRF fabric or cluster has two member devices, and each member device has two MPUs.

· The upgrade procedure for single-MPU devices is the same as that for dual-MPU devices.

· The command output varies by device model.

Upgrade workflow

Table 6 Upgrade workflow

Upgrade procedure

Preparing for the upgrade

See "Preparing for the upgrade."

Downloading the upgrade file

Download the upgrade file from an PC to the router. For more information, see "Downloading the upgrade file."

Identifying the recommended ISSU methods

# Display active software images.

<Sysname> display install active

Active packages on chassis 1 slot 0:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature-t0001015.bin

Active packages on chassis 1 slot 1:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature-t0001015.bin

Active packages on chassis 2 slot 0:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature-t0001015.bin

Active packages on chassis 2 slot 1:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature-t0001015.bin

# Identify the recommended ISSU methods.

<Sysname> display version comp-matrix file boot flash:/boot-t0001016.bin system flash:/system-t0001016.bin feature flash:/feature-t0001016.bin

Verifying the file flash:/boot-t0001016.bin on chassis 1 slot 0..................................Done.

Verifying the file flash:/system-t0001016.bin on chassis 1 slot 0..................................Done.

Verifying the file flash:/feature-t0001016.bin on chassis 1 slot 0..................................Done.

Identifying the upgrade methods....Done.

Chassis Slot Upgrade Way

1 0 Reboot

1 1 Reboot

2 0 Reboot

2 1 Reboot

The output shows that reboot upgrades are recommended.

Upgrading the startup software

# Upgrade the startup software on the subordinate member.

<Sysname> issu load file boot flash:/boot-t0001016.bin system flash:/system-t0001016.bin feature flash:/feature-t0001016.bin chassis 2

This operation will delete the rollback point information for the previous upgrade and maybe get unsaved configuration lost. Continue? [Y/N]:y

Copying file flash:/boot-t0001016.bin to chassis2#slot0#flash:/boot-t0001016.bin......Done.

Copying file flash:/system-t0001016.bin to chassis2#slot0#flash:/system-t0001016.bin........................Done.

Copying file flash:/feature-t0001016.bin to chassis2#slot0#flash:/feature-t0001016.bin......Done.

Verifying the file flash:/boot-t0001016.bin on chassis 2 slot 0...Done.

Verifying the file flash:/system-t0001016.bin on chassis 2 slot 0............Done.

Verifying the file flash:/feature-t0001016.bin on chassis 2 slot 0...Done.

Copying file flash:/boot-t0001016.bin to chassis2#slot1#flash:/boot-t0001016.bin......Done.

Copying file flash:/system-t0001016.bin to chassis2#slot1#flash:/system-t0001016.bin........................Done.

Copying file flash:/feature-t0001016.bin to chassis2#slot1#flash:/feature-t0001016.bin......Done.

Verifying the file flash:/boot-t0001016.bin on chassis 2 slot 1...Done.

Verifying the file flash:/system-t0001016.bin on chassis 2 slot 1............Done.

Verifying the file flash:/feature-t0001016.bin on chassis 2 slot 1...Done.

Identifying the upgrade methods….Done.

Upgrade summary according to following table:

flash:/boot-t0001016.bin

Running Version New Version

Test 0001015 Test 0001016

flash:/system-t0001016.bin

Running Version New Version

Test 0001015 Test 0001016

flash:/feature-t0001016.bin

Running Version New Version

Test 0001015 Test 0001016

Chassis Slot Upgrade Way

2 0 Reboot

2 1 Reboot

Upgrading software images to compatible versions. Continue? [Y/N]:y

This operation might take several minutes, please wait...Done.

# Verify that the ISSU is in a stable state.

<Sysname> display issu state

ISSU state: Loaded

Compatibility: Compatible

Work state: Normal

Upgrade method: Chassis by chassis

Upgraded chassis:

chassis 2

Current upgrading chassis: None

Previous version list:

boot: 7.1.070, Test 0001015

system: 7.1.070, Test 0001015

feature: 7.1.070, Test 0001015

Previous software images:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature-t0001015.bin

Upgrade version list:

boot: 7.1.070, Test 0001016

system: 7.1.070, Test 0001016

feature: 7.1.070, Test 0001016

Upgrade software images:

flash:/boot-t0001016.bin

flash:/system-t0001016.bin

flash:/feature-t0001016.bin

The Loaded state is a stable state, which indicates that the system is waiting for a master/subordinate switchover. Chassis 2 has completed the upgrade, and chassis 1 has not.

# Perform a master/subordinate switchover.

<Sysname> issu run switchover

Upgrade summary according to following table:

flash:/boot-t0001016.bin

Running Version New Version

Test 0001015 Test 0001016

flash:/system-t0001016.bin

Running Version New Version

Test 0001015 Test 0001016

flash:/feature-t0001016.bin

Running Version New Version

Test 0001015 Test 0001016

Chassis Slot Switchover Way

1 0 Master subordinate switchover

Upgrading software images to compatible versions. Continue? [Y/N]:y

This operation might take several minutes, please wait.........

# Verify that the ISSU is in a stable state.

<Sysname> display issu state

ISSU state: Switchover

Compatibility: Compatible

Work state: Normal

Upgrade method: Chassis by chassis

Upgraded chassis:

chassis 2

Current upgrading chassis: None

Previous version list:

boot: 7.1.070, Test 0001015

system: 7.1.070, Test 0001015

feature: 7.1.070, Test 0001015

Previous software images:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature-t0001015.bin

Upgrade version list:

boot: 7.1.070, Test 0001016

system: 7.1.070, Test 0001016

feature: 7.1.070, Test 0001016

Upgrade software images:

flash:/boot-t0001016.bin

flash:/system-t0001016.bin

flash:/feature-t0001016.bin

The Switchover state is a stable state, which indicates that the system has completed the master/subordinate switchover and is waiting for a commit operation to upgrade chassis 1.

# Upgrade the startup software on the original master.

<Sysname> issu commit chassis 1

Copying file flash:/boot-t0001016.bin to chassis1#slot1#flash:/boot-t0001016.bin......Done.

Copying file flash:/system-t0001016.bin to chassis1#slot1#flash:/system-t0001016.bin........................Done.

Copying file flash:/feature-t0001016.bin to chassis1#slot1#flash:/feature-t0001016.bin......Done.

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

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

Verifying the file flash:/feature-t0001016.bin on chassis 1 slot 1...Done.

Upgrade summary according to following table:

flash:/boot-t0001016.bin

Running Version New Version

Test 0001015 Test 0001016

flash:/system-t0001016.bin

Running Version New Version

Test 0001015 Test 0001016

flash:/feature-t0001016.bin

Running Version New Version

Test 0001015 Test 0001016

Chassis Slot Upgrade Way

1 0 Reboot

1 1 Reboot

Upgrading software images to compatible versions. Continue? [Y/N]:y

This operation might take several minutes, please wait...Done.

Verifying the upgrade

# Verify that the ISSU is finished.

<Sysname> display issu state

ISSU state: Init

Compatibility: Unknown

Upgrade method: Chassis by chassis

Upgraded chassis: None

Current upgrading chassis: None

Current version list:

boot: 7.1.070, Test 0001016

system: 7.1.070, Test 0001016

feature: 7.1.070, Test 0001016

Current software images:

flash:/boot-t0001016.bin

flash:/system-t0001016.bin

flash:/feature-t0001016.bin

The ISSU state field displays Init, which indicates that the ISSU is finished.

# Verify that both members are running the new software images.

<Sysname> display install active

Active packages on chassis 1 slot 0:

flash:/boot-t0001016.bin

flash:/system-t0001016.bin

flash:/feature-t0001016.bin

Active packages on chassis 1 slot 1:

flash:/boot-t0001016.bin

flash:/system-t0001016.bin

flash:/feature-t0001016.bin

Active packages on chassis 2 slot 0:

flash:/boot-t0001016.bin

flash:/system-t0001016.bin

flash:/feature-t0001016.bin

Active packages on chassis 2 slot 1:

flash:/boot-t0001016.bin

flash:/system-t0001016.bin

flash:/feature-t0001016.bin

Performing a compatible upgrade by using ISSU commands (centralized devices)

NOTE:

· Before performing an ISSU, you must use the display version comp-matrix command to identify the recommended ISSU methods.

· In this section, the IRF fabric has two member devices.

· The command output varies by device model.

Upgrade workflow

Table 7 Upgrade workflow

Upgrade procedure

Preparing for the upgrade

See "Preparing for the upgrade."

Downloading the upgrade file

Download the upgrade file from an PC to the router. For more information, "Downloading the upgrade file."

Identifying the recommended ISSU methods

# Display active software images.

<Sysname> display install active

Active packages on slot 1:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature-t0001015.bin

Active packages on slot 2:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature-t0001015.bin

# Identify the recommended ISSU methods.

<Sysname> display version comp-matrix file boot flash:/boot-t0001016.bin system flash:/system-t0001016.bin feature flash:/feature-t0001016.bin

Verifying the file flash:/boot-t0001016.bin on slot 1.......................Done.

Verifying the file flash:/system-t0001016.bin on slot 1................. .................Done.

Verifying the file flash:/feature-t0001016.bin on slot 1.................Done.

Identifying the upgrade methods....Done.

Slot Upgrade Way

1 Reboot

2 Reboot

The output shows that reboot upgrades are recommended.

Upgrading the startup software

# Upgrade the startup software on the subordinate member.

<Sysname> issu load file boot flash:/boot-t0001016.bin system flash:/system-t0001016.bin feature flash:/feature-t0001016.bin slot 2

This operation will delete the rollback point information for the previous upgrade and maybe get unsaved configuration lost. Continue? [Y/N]:y

Copying file flash:/boot-t0001016.bin to slot2#flash:/boot-t0001016.bin......Done.

Copying file flash:/system-t0001016.bin to slot2#flash:/system-t0001016.bin........................Done.

Copying file flash:/feature-t0001016.bin to slot2#flash:/feature-t0001016.bin......Done.

Verifying the file flash:/boot-t0001016.bin on slot 2...Done.

Verifying the file flash:/system-t0001016.bin on slot 2............Done.

Verifying the file flash:/feature-t0001016.bin on slot 2...Done.

Identifying the upgrade methods….Done.

Upgrade summary according to following table:

flash:/boot-t0001016.bin

Running Version New Version

Test 0001015 Test 0001016

flash:/system-t0001016.bin

Running Version New Version

Test 0001015 Test 0001016

flash:/feature-t0001016.bin

Running Version New Version

Test 0001015 Test 0001016

Slot Upgrade Way

2 Reboot

Upgrading software images to compatible versions. Continue? [Y/N]:y

This operation might take several minutes, please wait...Done.

# Verify that the ISSU is in a stable state.

<Sysname> display issu state

ISSU state: Loaded

Compatibility: Compatible

Work state: Normal

Upgrade method: Card by card

Upgraded slot:

slot 2

Current upgrading slot: None

Previous version list:

boot: 7.1.070, Test 0001015

system: 7.1.070, Test 0001015

feature: 7.1.070, Test 0001015

Previous software images:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature-t0001015.bin

Upgrade version list:

boot: 7.1.070, Test 0001016

system: 7.1.070, Test 0001016

feature: 7.1.070, Test 0001016

Upgrade software images:

flash:/boot-t0001016.bin

flash:/system-t0001016.bin

flash:/feature-t0001016.bin

The Loaded state is a stable state, which indicates that the system is waiting for a master/subordinate switchover. Slot 2 has completed the upgrade, and slot 1 has not.

# Perform a master/subordinate switchover.

<Sysname> issu run switchover

Upgrade summary according to following table:

flash:/boot-t0001016.bin

Running Version New Version

Test 0001015 Test 0001016

flash:/system-t0001016.bin

Running Version New Version

Test 0001015 Test 0001016

flash:/feature-t0001016.bin

Running Version New Version

Test 0001015 Test 0001016

Slot Switchover Way

1 Master subordinate switchover

Upgrading software images to compatible versions. Continue? [Y/N]:y

This operation might take several minutes, please wait.........

# Verify that the ISSU is in a stable state.

<Sysname> display issu state

ISSU state: Switchover

Compatibility: Compatible

Work state: Normal

Upgrade method: Card by card

Upgraded slot:

slot 2

Current upgrading slot: None

Previous version list:

boot: 7.1.070, Test 0001015

system: 7.1.070, Test 0001015

feature: 7.1.070, Test 0001015

Previous software images:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature-t0001015.bin

Upgrade version list:

boot: 7.1.070, Test 0001016

system: 7.1.070, Test 0001016

feature: 7.1.070, Test 0001016

Upgrade software images:

flash:/boot-t0001016.bin

flash:/system-t0001016.bin

flash:/feature-t0001016.bin

The Switchover state is a stable state, which indicates that the system has completed the master/subordinate switchover and is waiting for a commit operation to upgrade slot 1.

# Upgrade the startup software on the original master.

<Sysname> issu commit slot 1

Upgrade summary according to following table:

flash:/boot-t0001016.bin

Running Version New Version

Test 0001015 Test 0001016

flash:/system-t0001016.bin

Running Version New Version

Test 0001015 Test 0001016

flash:/feature-t0001016.bin

Running Version New Version

Test 0001015 Test 0001016

Slot Upgrade Way

1 Reboot

Upgrading software images to compatible versions. Continue? [Y/N]:y

This operation might take several minutes, please wait...Done.

Verifying the upgrade

# Verify that the ISSU is finished.

<Sysname> display issu state

ISSU state: Init

Compatibility: Unknown

Work state: Normal

Upgrade method: Card by card

Upgraded slot: None

Current upgrading slot: None

Current version list:

boot: 7.1.070, Test 0001016

system: 7.1.070, Test 0001016

feature: 7.1.070, Test 0001016

Current software images:

flash:/boot-t0001016.bin

flash:/system-t0001016.bin

flash:/feature-t0001016.bin

The ISSU state field displays Init, which indicates that the ISSU is finished.

# Verify that both members are running the new software images.

<Sysname> display install active

Active packages on slot 1:

flash:/boot-t0001016.bin

flash:/system-t0001016.bin

flash:/feature-t0001016.bin

Active packages on slot 2:

flash:/boot-t0001016.bin

flash:/system-t0001016.bin

flash:/feature-t0001016.bin

Performing an incompatible upgrade by using ISSU commands (distributed devices)

NOTE:

· Before performing an ISSU, you must use the display version comp-matrix command to identify the recommended ISSU methods.

· In this section, the IRF fabric has two member devices, and each member device has two MPUs.

· The upgrade procedure for single-MPU devices is the same as that for dual-MPU devices.

· The command output varies by device model.

Upgrade workflow

Table 8 Upgrade workflow

Upgrade procedure

Preparing for the upgrade

See "Preparing for the upgrade."

Downloading the upgrade file

Download the upgrade file from an PC to the router. For more information, see "Downloading the upgrade file."

Identifying the recommended ISSU methods

# Display active software images.

<Sysname> display install active

Active packages on chassis 1 slot 0:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature-t0001015.bin

Active packages on chassis 1 slot 1:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature-t0001015.bin

Active packages on chassis 2 slot 0:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature-t0001015.bin

Active packages on chassis 2 slot 1:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature-t0001015.bin

# Identify the recommended ISSU methods.

<Sysname> display version comp-matrix file boot flash:/boot-t0001017.bin system flash:/system-t0001017.bin feature flash:/feature-t0001017.bin

Verifying the file flash:/boot-t0001017.bin on chassis 1 slot 0..................................Done.

Verifying the file flash:/system-t0001017.bin on chassis 1 slot 0..................................Done.

Verifying the file flash:/feature-t0001017.bin on chassis 1 slot 0..................................Done.

Identifying the upgrade methods....Done.

Incompatible upgrade

The output shows that an incompatible upgrade is recommended.

Upgrading the startup software

# Upgrade the startup software on the subordinate member.

<Sysname> issu load file boot flash:/boot-t0001017.bin system flash:/system-t0001017.bin feature flash:/feature-t0001017.bin chassis 2

This operation will delete the rollback point information for the previous upgrade and maybe get unsaved configuration lost. Continue? [Y/N]:y

Copying file flash:/boot-t0001017.bin to chassis2#slot0#flash:/boot-t0001017.bin......Done.

Copying file flash:/system-t0001017.bin to chassis2#slot0#flash:/system-t0001017.bin........................Done.

Copying file flash:/feature-t0001017.bin to chassis2#slot0#flash:/feature-t0001017.bin......Done.

Verifying the file flash:/boot-t0001017.bin on chassis 2 slot 0...Done.

Verifying the file flash:/system-t0001017.bin on chassis 2 slot 0............Done.

Verifying the file flash:/feature-t0001017.bin on chassis 2 slot 0...Done.

Copying file flash:/boot-t0001017.bin to chassis2#slot1#flash:/boot-t0001017.bin......Done.

Copying file flash:/system-t0001017.bin to chassis2#slot1#flash:/system-t0001017.bin........................Done.

Copying file flash:/feature-t0001017.bin to chassis2#slot1#flash:/feature-t0001017.bin......Done.

Verifying the file flash:/boot-t0001017.bin on chassis 2 slot 1...Done.

Verifying the file flash:/system-t0001017.bin on chassis 2 slot 1............Done.

Verifying the file flash:/feature-t0001017.bin on chassis 2 slot 1...Done.

Identifying the upgrade methods….Done.

Upgrade summary according to following table:

flash:/boot-t0001017.bin

Running Version New Version

Test 0001015 Test 0001017

flash:/system-t0001017.bin

Running Version New Version

Test 0001015 Test 0001017

flash:/feature-t0001017.bin

Running Version New Version

Test 0001015 Test 0001017

Chassis Slot Upgrade Way

2 0 Reboot

2 1 Reboot

Upgrading software images to incompatible versions. Continue? [Y/N]:y

This operation might take several minutes, please wait...Done.

# Verify that the ISSU is in a stable state.

<Sysname> display issu state

ISSU state: Loaded

Compatibility: Incompatible

Work state: Normal

Upgrade method: Chassis by chassis

Upgraded chassis:

chassis 2

Current upgrading chassis: None

Previous version list:

boot: 7.1.070, Test 0001015

system: 7.1.070, Test 0001015

feature: 7.1.070, Test 0001015

Previous software images:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature-t0001015.bin

Upgrade version list:

boot: 7.1.070, Test 0001017

system: 7.1.070, Test 0001017

feature: 7.1.070, Test 0001017

Upgrade software images:

flash:/boot-t0001017.bin

flash:/system-t0001017.bin

flash:/feature-t0001017.bin

The Loaded state is a stable state, which indicates that the system is waiting for a master/subordinate switchover. Chassis 2 has completed the upgrade, and chassis 1 has not.

# Perform a master/subordinate switchover.

<Sysname> issu run switchover

Copying file flash:/boot-t0001017.bin to chassis1#slot1#flash:/boot-t0001017.bin......Done.

Copying file flash:/system-t0001017.bin to chassis1#slot1#flash:/system-t0001017.bin........................Done.

Copying file flash:/feature-t0001017.bin to chassis1#slot1#flash:/feature-t0001017.bin......Done.

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

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

Verifying the file flash:/feature-t0001017.bin on chassis 1 slot 1...Done.

Upgrade summary according to following table:

flash:/boot-t0001017.bin

Running Version New Version

Test 0001015 Test 0001017

flash:/system-t0001017.bin

Running Version New Version

Test 0001015 Test 0001017

flash:/feature-t0001017.bin

Running Version New Version

Test 0001015 Test 0001017

Chassis Slot Upgrade Way

1 0 Reboot

1 1 Reboot

Upgrading software images to incompatible versions. Continue? [Y/N]:y

This operation might take several minutes, please wait.........

Verifying the upgrade

# Verify that the ISSU is finished.

<Sysname> display issu state

ISSU state: Init

Compatibility: Unknown

Work state: Normal

Upgrade method: Chassis by chassis

Upgraded chassis: None

Current upgrading chassis: None

Current version list:

boot: 7.1.070, Test 0001017

system: 7.1.070, Test 0001017

feature: 7.1.070, Test 0001017

Current software images:

flash:/boot-t0001017.bin

flash:/system-t0001017.bin

flash:/feature-t0001017.bin

The ISSU state field displays Init, which indicates that the ISSU is finished.

# Verify that both members are running the new software images.

<Sysname> display install active

Active packages on chassis 1 slot 0:

flash:/boot-t0001017.bin

flash:/system-t0001017.bin

flash:/feature-t0001017.bin

Active packages on chassis 1 slot 1:

flash:/boot-t0001017.bin

flash:/system-t0001017.bin

flash:/feature-t0001017.bin

Active packages on chassis 2 slot 0:

flash:/boot-t0001017.bin

flash:/system-t0001017.bin

flash:/feature-t0001017.bin

Active packages on chassis 2 slot 1:

flash:/boot-t0001017.bin

flash:/system-t0001017.bin

flash:/feature-t0001017.bin

Performing an incompatible upgrade by using ISSU commands (centralized devices)

NOTE:

· Before performing an ISSU, you must use the display version comp-matrix command to identify the recommended ISSU methods.

· In this section, the IRF fabric has two member devices.

· The command output varies by device model.

Upgrade workflow

Table 9 Upgrade workflow

Upgrade procedure

Preparing for the upgrade

See "Preparing for the upgrade."

Downloading the upgrade file

Download the upgrade file from an PC to the router. For more information, see "Downloading the upgrade file."

Identifying the recommended ISSU methods

# Display active software images.

<Sysname> display install active

Active packages on slot 1:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature-t0001015.bin

Active packages on slot 2:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature-t0001015.bin

# Identify the recommended ISSU methods.

<Sysname> display version comp-matrix file boot flash:/boot-t0001017.bin system flash:/system-t0001017.bin feature flash:/feature-t0001017.bin

Verifying the file flash:/boot-t0001017.bin on slot 1.......................Done.

Verifying the file flash:/system-t0001017.bin on slot 1................. .................Done.

Verifying the file flash:/feature-t0001017.bin on slot 1.................Done.

Identifying the upgrade methods....Done.

Incompatible upgrade.

The output shows that reboot upgrades are recommended.

Upgrading the startup software

# Upgrade the startup software on the subordinate member.

<Sysname> issu load file boot flash:/boot-t0001017.bin system flash:/system-t0001017.bin feature flash:/feature-t0001017.bin slot 2

This operation will delete the rollback point information for the previous upgrade and maybe get unsaved configuration lost. Continue? [Y/N]:y

Copying file flash:/boot-t0001017.bin to slot2#flash:/boot-t0001017.bin......Done.

Copying file flash:/system-t0001017.bin to slot2#flash:/system-t0001017.bin........................Done.

Copying file flash:/feature-t0001017.bin to slot2#flash:/feature-t0001017.bin......Done.

Verifying the file flash:/boot-t0001017.bin on slot 2...Done.

Verifying the file flash:/system-t0001017.bin on slot 2............Done.

Verifying the file flash:/feature-t0001017.bin on slot 2...Done.

Identifying the upgrade methods….Done.

Upgrade summary according to following table:

flash:/boot-t0001017.bin

Running Version New Version

Test 0001015 Test 0001017

flash:/system-t0001017.bin

Running Version New Version

Test 0001015 Test 0001017

flash:/feature-t0001017.bin

Running Version New Version

Test 0001015 Test 0001017

Slot Upgrade Way

2 Reboot

Upgrading software images to incompatible versions. Continue? [Y/N]:y

This operation might take several minutes, please wait...Done.

# Verify that the ISSU is in a stable state.

<Sysname> display issu state

ISSU state: Loaded

Compatibility: Incompatible

Work state: Normal

Upgrade method: Card by card

Upgraded slot:

slot 2

Current upgrading slot: None

Previous version list:

boot: 7.1.070, Test 0001015

system: 7.1.070, Test 0001015

feature: 7.1.070, Test 0001015

Previous software images:

flash:/boot-t0001015.bin

flash:/system-t0001015.bin

flash:/feature-t0001015.bin

Upgrade version list:

boot: 7.1.070, Test 0001017

system: 7.1.070, Test 0001017

feature: 7.1.070, Test 0001017

Upgrade software images:

flash:/boot-t0001017.bin

flash:/system-t0001017.bin

flash:/feature-t0001017.bin

The Loaded state is a stable state, which indicates that the system is waiting for a master/subordinate switchover. Slot 2 has completed the upgrade, and slot 1 has not.

# Perform a master/subordinate switchover.

<Sysname> issu run switchover

Upgrade summary according to following table:

flash:/boot-t0001017.bin

Running Version New Version

Test 0001015 Test 0001017

flash:/system-t0001017.bin

Running Version New Version

Test 0001015 Test 0001017

flash:/feature-t0001017.bin

Running Version New Version

Test 0001015 Test 0001017

Slot Switchover Way

1 Master subordinate switchover

Verifying the upgrade

# Verify that the ISSU is finished.

<Sysname> display issu state

ISSU state: Init

Compatibility: Unknown

Work state: Normal

Upgrade method: Card by card

Upgraded slot: None

Current upgrading slot: None

Current version list:

boot: 7.1.070, Test 0001017

system: 7.1.070, Test 0001017

feature: 7.1.070, Test 0001017

Current software images:

flash:/boot-t0001017.bin

flash:/system-t0001017.bin

flash:/feature-t0001017.bin

The ISSU state field displays Init, which indicates that the ISSU is finished.

# Verify that both members are running the new software images.

<Sysname> display install active

Active packages on slot 1:

flash:/boot-t0001017.bin

flash:/system-t0001017.bin

flash:/feature-t0001017.bin

Active packages on slot 2:

flash:/boot-t0001017.bin

flash:/system-t0001017.bin

flash:/feature-t0001017.bin

Installing patches and features

This chapter describes how to install patches and features.

· Installing patches

· Installing features on a single-MPU device (distributed devices in standalone mode)

· Installing features on a dual-MPU device (distributed devices in standalone mode)

· Installing features (distributed devices in IRF mode/CR19000)

· Installing features (centralized devices)

Installing patches

Installation workflow

Figure 8 Installation workflow

Installation procedure

Preparing for the upgrade

See "Preparing for the upgrade."

Downloading the image file

Download the image file from an PC to the router. For more information, see "Downloading the upgrade file."

Installing a patch

NOTE:

The upgrade procedure for single-MPU devices is the same as that for dual-MPU devices.

# Install a patch.

<Sysname> install activate patch flash:/patch1.bin all

...

# Commit the software change.

<Sysname> install commit

...

NOTE:

· The install commit command enables the installed patch to take effect after the device or a card reboots.

· You need to re-install the patch after the software is upgraded and then rolled back to original version.

Uninstalling a patch

# Display active patch images.

<Sysname> display install active

...

# Uninstall a patch.

<Sysname> install deactivate patch flash:/patch1.bin all

...

# Commit the software change.

<Sysname> install commit

...

NOTE:

The install commit command enables the uninstalled patch to not take effect after the device or a card reboots.

Installing features on a single-MPU device (distributed devices in standalone mode)

Installation workflow

Figure 9 Installation workflow

Installation procedure

Preparing for the upgrade

See "Preparing for the upgrade."

Downloading the upgrade file

Download the upgrade file from an PC to the router. For more information, see "Downloading the upgrade file."

Decompressing the .ipe file

If the image file for installing a feature is in an .ipe file, decompress the .ipe file.

<Sysname> install add flash:/feature1.ipe flash:/

...

Installing a feature

# Install a feature image on the MPU.

<Sysname> install activate feature flash:/feature1.bin slot0

...

# Commit the software change.

<Sysname> install commit

...

NOTE:

· The install commit command enables the installed feature images to take effect after the device or a card reboots.

· You need to re-install the feature images after the software is upgraded and then rolled back to original version.

Uninstalling a feature image

# Uninstall the feature image on the MPU.

<Sysname> install deactivate feature flash:/feature1.bin slot0

...

# Commit the software change.

<Sysname> install commit

...

NOTE:

The install commit command enables the uninstalled feature images to not take effect after the device or a card reboots.

Installing features on a dual-MPU device (distributed devices in standalone mode)

Installation workflow

Figure 10 Installation workflow

Installation procedure

Preparing for the upgrade

See "Preparing for the upgrade."

Downloading the upgrade file

Download the upgrade file from an PC to the router. For more information, see "Downloading the upgrade file."

Decompressing the .ipe file

If the image file for installing a feature is in an .ipe file, decompress the .ipe file.

<Sysname> install add flash:/feature1.ipe flash:/

...

Installing a feature

# Install a feature image on the active MPU.

<Sysname> install activate feature flash:/feature1.bin slot0

...

# Install a feature image on the standby MPU.

<Sysname> install activate feature flash:/feature1.bin slot1

...

# Commit the software change.

<Sysname> install commit

...

NOTE:

· The install commit command enables the installed feature images to take effect after the device or a card reboots.

· You need to re-install the feature images after the software is upgraded and then rolled back to original version.

Uninstalling a feature image

# Uninstall the feature image on the standby MPU.

<Sysname> install deactivate feature flash:/feature1.bin slot1

...

# Uninstall the feature image on the active MPU.

<Sysname> install deactivate feature flash:/feature1.bin slot0

...

# Commit the software change.

<Sysname> install commit

...

NOTE:

· To uninstall a feature image, you must begin with the standby MPU.

· The install commit command enables the uninstalled feature images to not take effect after the device or a card reboots.

Installing features (distributed devices in IRF mode/CR19000)

NOTE:

· In this section, the IRF fabric or cluster has two member devices, and each member device has two MPUs.

· The upgrade procedure for single-MPU devices is the same as that for dual-MPU devices.

Installation workflow

Figure 11 Installation workflow

Installation procedure

Preparing for the upgrade

See "Preparing for the upgrade."

Downloading the upgrade file

Download the upgrade file from an PC to the router. For more information, see "Downloading the upgrade file."

Decompressing the .ipe file

If the image file for installing a feature is in an .ipe file, decompress the .ipe file.

<Sysname> install add flash:/feature1.ipe flash:/

...

Installing a feature

# Install a feature image on all MPUs in the IRF fabric or cluster.

<Sysname> install activate feature flash:/feature1.bin chassis 1 slot0

...

<Sysname> install activate feature flash:/feature1.bin chassis 1 slot1

...

<Sysname> install activate feature flash:/feature1.bin chassis 2 slot0

...

<Sysname> install activate feature flash:/feature1.bin chassis 2 slot1

...

# Commit the software change.

<Sysname> install commit

...

NOTE:

· The install commit command enables the installed feature images to take effect after the device or a card reboots.

· You need to re-install the feature images after the software is upgraded and then rolled back to original version.

Uninstalling a feature image

# Uninstall the feature image from all standby MPUs.

<Sysname> install deactivate feature flash:/feature1.bin chassis 1 slot1

...

<Sysname> install deactivate feature flash:/feature1.bin chassis 2 slot1

...

<Sysname> install deactivate feature flash:/feature1.bin chassis 2 slot0

...

# Uninstall the feature image from the active MPU.

<Sysname> install deactivate feature flash:/feature1.bin chassis 2 slot0

...

# Commit the software change.

<Sysname> install commit

...

NOTE:

· To uninstall a feature image, you must begin with the standby MPUs.

· The install commit command enables the uninstalled feature images to not take effect after the device or a card reboots.

Installing features (centralized devices)

Installation workflow

Figure 12 Installation workflow

Installation procedure

Preparing for the upgrade

See "Preparing for the upgrade."

Downloading the upgrade file

Download the upgrade file from an PC to the router. For more information, see "Downloading the upgrade file."

Decompressing the .ipe file

If the image file for installing a feature is in an .ipe file, decompress the .ipe file.

<Sysname> install add flash:/feature1.ipe flash:/

...

Installing a feature

# Install a feature image.

<Sysname> install activate feature flash:/feature1.bin slot1

...

# Commit the software change.

<Sysname> install commit

...

NOTE:

· The install commit command enables the installed feature images to take effect after the device reboots.

· You need to re-install the feature images after the software is upgraded and then rolled back to original version.

Uninstalling a feature image

# Uninstall a feature image.

<Sysname> install deactivate feature flash:/feature1.bin slot1

...

# Commit the software change.

<Sysname> install commit

...

NOTE:

The install commit command enables the uninstalled feature images to not take effect after the device reboots.

Verifying the upgrade

This chapter includes the following sections:

· Verifying that the router is running the new BootWare image

· Verifying that the router is running the new software images

· Verifying that a patch or feature image is installed successfully

· Verifying that the cards and subcards are in normal state (modular router)

· Verifying that the router is in stable state

· Verifying that the configuration has been recovered

· Verifying that the services are normal

Verifying that the router is running the new BootWare image

NOTE:

The verification is required only if the BootWare image has been upgraded.

Use one of the following methods:

· Reboot the router to check whether the router is running the new BootWare image.

If not, examine the upgrade steps and perform the upgrade steps again.

The command output might vary by router model. This section uses a CR16000-F router as an example.

...

****************************************************************************

* *

* BootWare, Version 1.51 *

* *

****************************************************************************

...

· Use the display version command to verify that the router is running the new BootWare image. If not, examine the upgrade steps and perform the upgrade steps again.

Verifying that the router is running the new software images

NOTE:

The verification is required only if the startup software has been upgraded.

# Use the display boot-loader command to check whether the router is running the new software images.

If not, examine the upgrade steps and perform the upgrade steps again.

The command output might vary by router model. This section uses a CR16000-F router as an example.

<Sysname>display boot-loader

Software images on slot 0:

Current software images:

cfa0:/CR16000-CMW710-BOOT-R8260P22.bin

cfa0:/CR16000-CMW710-SYSTEM-R8260P22.bin

Main startup software images:

cfa0:/CR16000-CMW710-BOOT-R8260P22.bin

cfa0:/CR16000-CMW710-SYSTEM-R8260P22.bin

Backup startup software images:

None

Verifying that a patch or feature image is installed successfully

NOTE:

The verification is required only if a patch or feature image has been installed.

# Use the display install active command to check whether a patch or feature image has been installed successfully.

If the command output does not have a patch or feature image, no patch or feature image has been installed or the patch or feature image installation fails.

The command output might vary by router model. This section uses a CR16000-F router as an example.

<Sysname>display install active

Active packages on slot 0:

cfa0:/CR16000-CMW710-BOOT-R8260P22.bin

cfa0:/CR16000-CMW710-SYSTEM-R8260P22.bin

cfa0:/CR16000-CMW710-SYSTEM-WEAK-R8260P22H01.bin

Active packages on slot 6:

cfa0:/CR16000-CMW710-BOOT-R8260P22.bin

cfa0:/CR16000-CMW710-SYSTEM-R8260P22.bin

cfa0:/CR16000-CMW710-SYSTEM-WEAK-R8260P22H01.bin

Active packages on slot 13:

cfa0:/CR16000-CMW710-BOOT-R8260P22.bin

cfa0:/CR16000-CMW710-SYSTEM-R8260P22.bin

cfa0:/CR16000-CMW710-SYSTEM-WEAK-R8260P22H01.bin

Verifying that the cards and subcards are in normal state (modular router)

# Use the display device command to check whether the cards and subcards are in normal state.

The Brd Status field indicates the card or subcard status.

The command output might vary by router model. This section uses a CR16000-F router as an example.

<Sysname>display device

Slot No. Brd Type Brd Status Software Version

0 CSR05SRP1P3 Master CR16000-CMW710-R8260P22

1 NONE Absent NONE

2 NONE Absent NONE

3 NONE Absent NONE

4 CSPEX-1504X Normal CR16000-CMW710-R8260P22

5 NONE Absent NONE

6 CSPEX-1504X Normal CR16000-CMW710-R8260P22

7 NONE Absent NONE

8 NONE Absent NONE

9 NONE Absent NONE

10 NONE Absent NONE

11 NONE Absent NONE

12 NONE Absent NONE

13 CSFC-08E1 Normal CR16000-CMW710-R8260P22

14 NONE Absent NONE

Verifying that the router is in stable state

# Use the display system stable state command to check whether the router is in stable state.

The router is stable if the System State field displays Stable.

The command output might vary by router model. This section uses a CR16000-F router as an example.

<Sysname> display system stable state

System state : Stable

Redundancy state : No redundancy

Slot CPU Role State

0 0 Active Stable

6 0 Other Stable

6 1 Other Stable

13 0 Other Stable

Verifying that the configuration has been recovered

# Use the display current-configuration command to view the current configuration.

# Use the display diff current-configuration startup-configuration command to check whether configurations are lost or modified.

Verifying that the services are normal

NOTE:

Before verifying the services, do not execute the save command.

# Collect entries (such as routing entries, FIB entries, and MAC address entries) and compare them with the entries before the upgrade to check whether entries are lost.

# Check whether the service traffic before and after the upgrade is the same.

# Check whether the servers such as NMS servers are working correctly.

Rolling back the running software images

This chapter includes the following sections:

· Application scenarios

· Restrictions and guidelines

· Rollback workflow

· Rollback procedure

· Verifying the rollback

Application scenarios

The following are application scenarios for version rollback:

· You need to roll back the running software version to the old version due to service requirements.

· You need to roll back the running software version to the old version if the device cannot work correctly after a software upgrade.

Restrictions and guidelines

Hardware-related restrictions and guidelines

Before the version rollback, make sure the device is operating correctly, and make sure the LEDs of the power supply, fans, cards, and subcards are normal.

During the version rollback, do not power off the device, and do not restart or remove swappable modules.

If you store the startup software images in a hot swappable storage medium, do not remove the hot swappable storage medium during the startup process.

Read the release notes to verify the software and hardware compatibility and hardware restrictions for the device, cards, and subcards.

Software-related restrictions and guidelines

Before the version rollback:

· Use the release notes to verify that the current software version can be rolled back to the target version.

· Back up the current software images, configuration files, and login passwords to prevent data loss if the storage medium is damaged.

· Make sure the device has sufficient storage space for the upgrade software images.

· Make sure the CPU usage of the device or a card is not high.

· Verify that the original configuration file before version upgrade is present on the device. If it does not exist, download the original configuration file to the device and specify it as the startup configuration file.

During the version rollback:

· As a best practice, enable logging of the terminal to collect information.

· A rollback requiring a device reboot will cause service interruption for the duration of the reboot.

· Before a rollback operation is completed, no other rollback operations can be performed. Rollback operations include the install, issu, and boot-loader commands.

After the version rollback:

· After the rollback, do not delete the running software images.

· The upgrade of the BootWare might cause the software version to fail to be downgraded.

Rollback workflow

The version rollback workflow is the same as the version upgrade workflow. For more information, see "Upgrade workflow."

Rollback procedure

The version rollback procedure is the same as the version upgrade procedure. For more information, see "Upgrading the startup software."

If the replacement image files are still saved on the storage medium, you do not need to download them again. You only need to specify them as the startup software images.

Verifying the rollback

Verifying the rollback is the same as verifying the upgrade. For more information, see "Verifying the upgrade."

Troubleshooting

This chapter describes the problems that might be encountered during a software upgrade and the troubleshooting steps.

Failed to log in to the router

Symptom

Failed to log in to the router through the management port or console port.

Possible reasons

· Parameters of the terminal emulation program are configured incorrectly.

· Physical ports are connected incorrectly.

· The Telnet service is not enabled on the router.

· The memory is insufficient on the router.

Troubleshooting workflow

Figure 13 Troubleshooting workflow

Solution

To resolve the issue:

1. Verify that the parameters of the terminal emulation program are configured correctly. For how to configure the parameters of the terminal emulation program, see "Preparing for the upgrade."

2. Verify that the physical cable connecting the PC to the management port or console port is good.

3. Use the display current-configuration to verify that the telnet server enable command and other related commands are executed on the router. For information about the configuration, see "Preparing for the upgrade."

4. If the issue persists, collect the following information and contact H3C Support:

¡ Execution results of the preceding commands.

¡ Configuration file, log messages, and warning messages.

Failed to download software images

Symptom

Transmission is interrupted during the downloading of software images.

Possible reasons

· The free storage space is insufficient.

· The link between the PC and the router fails, or the network is unstable.

· The FTP server or TFTP server program is abnormal.

· The storage medium is abnormal.

Troubleshooting workflow

Figure 14 Troubleshooting workflow

Solution

To resolve the issue:

1. Verify that the free storage space is sufficient. If the free storage space is insufficient, delete unused files. For more information, see "Preparing for the upgrade."

2. Use the ping command to verify the connection between the PC and the router. If the connection is abnormal, replace the link media.

3. Verify that the FTP/TFTP server program works correctly and the FTP/TFTP settings are correct.

4. Check whether the storage medium is normal by deleting, reading and copying files. If the storage medium is abnormal, you can format the storage medium.

5. If the issue persists, collect the following information and contact H3C Support:

¡ Execution results of the preceding commands.

¡ Configuration file, log messages, and warning messages.

Failed to restart the router after an upgrade

Symptom

The router fails to restart with the startup software images or cannot enter user view or system view after startup.

Possible reasons

· The power supply or fan tray fails.

· The startup software images are damaged. The startup software images might be damaged if the FTP transfer mode for downloading them is not binary mode.

· The storage medium to which the startup software images are downloaded is not the specified storage medium.

· The difference between the old version and the new version is large, so the BootWare cannot be automatically upgraded.

Troubleshooting workflow

Figure 15 Troubleshooting workflow

Solution

To resolve the issue:

1. Verify that the power supply is normal (the LED is solid green). If the power supply is abnormal, replace it.

2. Verify that the fan tray is normal (the LED is solid green) and that the air inlet and outlet vents are blocked. If the fan tray is abnormal, replace it or clean the air inlet and outlet vents.

3. Use the BootWare menu to check whether the storage medium to which the startup software images are downloaded is the specified storage medium. If not, see "Downloading the upgrade file" to set the storage medium to which the startup software images are downloaded is the specified storage medium.

4. Obtain the correct software version and upgrade the software from the BootWare menu again.

5. If the issue persists, collect the following information and contact H3C Support:

¡ Execution results of the preceding commands.

¡ Configuration file, log messages, and warning messages.

Failed to start a card or subcard after an upgrade

Symptom

The output from the display device command shows that a card or subcard is in Fault state.

Possible reasons

· The startup software version does not support the card or subcard.

· The startup software version on the card or subcard is different from the startup software version on the active MPU.

· The card or subcard is faulty.

Troubleshooting workflow

Figure 16 Troubleshooting workflow

Solution

To resolve the issue:

1. Use the release notes to check whether the current version supports the card or subcard. If the current version does not support the card or subcard, use another software version and perform the upgrade again.

2. Use the display device command to check whether the startup software version on the card or subcard is the same as the startup software version on the active MPU. If not, specify the same startup software version on the card or subcard.

3. If the issue persists, collect the following information and contact H3C Support:

¡ Execution results of the preceding commands.

¡ Configuration file, log messages, and warning messages.

Downloading the upgrade file

The router can function as the TFTP client, FTP client, or FTP server. For more information about FTP and TFTP, see the FTP and TFTP configuration in the fundamentals configuration guide.

Using FTP to download upgrade file

This section uses the router as an FTP client to download files from an FTP server.

Downloading software images at the CLI

NOTE:

The BootWare menu varies by router model and BootWare version. This section uses a CF16000-F router as an example.

1. Set up an upgrade environment as described in "Preparing for the upgrade."

2. Run the FTP server program on a PC (its IP address is 192.168.0.23), and set the working directory, FTP username, and password. Store the upgrade file on the working directory of the FTP server.

3. Make sure the PC and the router can reach each other.

4. Log in to the router, and access the root directory of the storage medium for the startup software images.

<Sysname> cd cfa0:/

NOTE:

If the storage medium to which the startup software images are downloaded is not the specified storage medium, access the root directory of the storage medium of startup software images before downloading the software images.

5. Download the upgrade file (newest.ipe in this example) to the storage medium on the router.

# Log in to the FTP server.

<Sysname> ftp 192.168.0.23

Connected to 192.168.0.23 (192.168.0.23).

220 WFTPD 2.0 service (by Texas Imperial Software) ready for new user

User (192.168.0.23:(none)):username

331 Give me your password, please

Password:

230 Logged in successfully

Remote system type is MSDOS.

ftp>

# Set the file transfer mode to binary.

ftp> binary

200 Type is Image (Binary)

# Download the upgrade file newest.ipe to the root directory of the storage medium.

ftp> get newest.ipe

227 Entering Passive Mode (192,168,0,23,7,100)

150 "C:\ newest.ipe " file ready to send (385 bytes) in in IMAGE / Binary mode

226 Transfer finished successfully.

74948608 bytes received in 35.974 seconds (896.00 kbyte/s)

ftp> bye

221 Windows FTP Server (WFTPD, by Texas Imperial Software) says goodbye

# Verify that the upgrade file has been in the root directory of the storage medium.

<Sysname> dir

# Use the MD5 algorithm to calculate the digest of the file, and compare it with the MD5 digest on the H3C website to verify file integrity.

<Sysname> md5sum newest.ipe

MD5 digest:

4f22b6190d151a167105df61c35f0917

Downloading software images from the BootWare menu

1. Set up an upgrade environment as described in "Preparing for the upgrade."

2. Run the FTP server program on a PC (its IP address is 192.168.0.23), and set the working directory, FTP username, and password. Store the upgrade file on the working directory of the FTP server.

3. Run the terminal emulation program on the PC, and power on the router. Press Ctrl+B at prompt to access the EXTENDED-BOOTWARE menu.

==========================<EXTENDED-BOOTWARE MENU>==========================

|<1> Boot System |

|<2> Enter Serial SubMenu |

|<3> Enter Ethernet SubMenu |

|<4> File Control |

|<5> Restore to Factory Default Configuration |

|<6> Skip Current System Configuration |

|<7> BootWare Operation Menu |

|<8> Skip Authentication for Console Login |

|<9> Storage Device Operation |

|<0> Reboot |

============================================================================

Ctrl+Z: Access EXTENDED ASSISTANT MENU

Ctrl+F: Format File System

Ctrl+C: Display Copyright

Enter your choice(0-9):

4. (Optional.) Set the default storage medium.

IMPORTANT:

If the storage medium storing the upgrade file is not the default storage medium, set it as the default storage medium.

# Enter 9 to access the storage device submenu.

==============================<DEVICE CONTROL>==============================

|<1> Display All Available Nonvolatile Storage Device(s) |

|<2> Set The Operating Device |

|<3> Set The Default Boot Device |

|<0> Exit To Main Menu |

============================================================================

Enter your choice(0-3):

# Enter 2 to set the storage medium for storing the upgrade file.

Please set the operating device:

============================================================================

|Note:the operating device is cfa0 |

|NO. Device Name File System Total Size Available Space |

|1 flash JFFS2 262144KB 224937KB |

|2 cfa0 FAT 2044256KB 1173684KB |

|0 Exit |

============================================================================

Enter your choice(0-2):

# Enter 2 to set the CF card as the storage medium for storing the upgrade file.

==============================<DEVICE CONTROL>==============================

|<1> Display All Available Nonvolatile Storage Device(s) |

|<2> Set The Operating Device |

|<3> Set The Default Boot Device |

|<0> Exit To Main Menu |

============================================================================

Enter your choice(0-3):

# Enter 3 to set the default storage medium.

Please set the default device:

============================================================================

|Note:the default device is cfa0 |

|NO. Device Name File System Total Size Available Space |

|1 flash JFFS2 262144KB 224937KB |

|2 cfa0 FAT 2044256KB 1173684KB |

|0 Exit |

============================================================================

Enter your choice(0-2):

# Enter 2 to set the CF card as the default storage medium.

==============================<DEVICE CONTROL>==============================

|<1> Display All Available Nonvolatile Storage Device(s) |

|<2> Set The Operating Device |

|<3> Set The Default Boot Device |

|<0> Exit To Main Menu |

============================================================================

Enter your choice(0-3):

# Enter 0 to exit the storage device submenu.

5. Download and upgrade the BootWare.

==========================<EXTENDED-BOOTWARE MENU>==========================

|<1> Boot System |

|<2> Enter Serial SubMenu |

|<3> Enter Ethernet SubMenu |

|<4> File Control |

|<5> Restore to Factory Default Configuration |

|<6> Skip Current System Configuration |

|<7> BootWare Operation Menu |

|<8> Skip Authentication for Console Login |

|<9> Storage Device Operation |

|<0> Reboot |

============================================================================

Ctrl+Z: Access EXTENDED ASSISTANT MENU

Ctrl+F: Format File System

Ctrl+C: Display Copyright

Enter your choice(0-9):

# Enter 3 to access the Ethernet submenu.

==========================<Enter Ethernet SubMenu>==========================

|Note:the operating device is cfa0 |

|<1> Download Image Program To SDRAM And Run |

|<2> Update Main Image File |

|<3> Update Backup Image File |

|<4> Download Files(*.*) |

|<5> Modify Ethernet Parameter |

|<0> Exit To Main Menu |

|<Ensure The Parameter Be Modified Before Downloading!> |

============================================================================

Enter your choice(0-5):

# Enter 5 to configure the network settings.

==========================<ETHERNET PARAMETER SET>==========================

|Note: '.' = Clear field. |

| '-' = Go to previous field. |

| Ctrl+D = Quit. |

============================================================================

Protocol (FTP or TFTP) :ftp

Load File Name :newest.ipe

Target File Name :newest.ipe

Server IP Address :192.168.0.23

Local IP Address :192.168.0.105

Subnet Mask :255.255.255.0

Gateway IP Address :0.0.0.0

FTP User Name :xxx

FTP User Password :***

Table 10 Network parameter fields and shortcut keys

Field	Description
'.' = Clear field	Press a dot (.) and then press Enter to clear the setting for a field.
'-' = Go to previous field	Press a hyphen (-) and then press Enter to return to the previous field.
Ctrl+D = Quit	Press Ctrl+D to exit the ETHERNET PARAMETER SET menu.
Protocol (FTP or TFTP)	Set the file transfer protocol to FTP or TFTP.
Load File Name	Set the name of the file to be downloaded.
Target File Name	Set a file name for saving the file on the router. The target file name must have the same extension as the source file. By default, the target file name is the same as the source file name.
Server IP Address	Set the IP address of the FTP or TFTP server.
Local IP Address	Set the IP address of the Ethernet interface that connects to the TFTP server.
Subnet Mask	Set the IP address mask.
Gateway IP Address	Set a gateway IP address if the router is on a different network than the server.

After you finish setting the FTP parameters, the system returns to the Ethernet submenu. Choose option 2 to 3. For example, enter 2 to upgrade the main startup software images.

Loading.....................................................................

............................................................................

.........................Done!

31911744 bytes downloaded!

Image file BOOT.bin is self-decompressing... Saving file cfa0:/ BOOT.bin ..............................................Done.

Image file SYSTEM.bin is self-decompressing...Saving file cfa0:/ SYSTEM.bin .................................. ..Done.

# Enter 0 in the Ethernet submenu to return to the EXTENDED-BOOTWARE menu.

# Enter 0 to reboot the router.

Using TFTP to download software images

This section uses the router as an FTP client to download files from an FTP server.

Downloading software images at the CLI

1. Set up an upgrade environment as described in "Preparing for the upgrade."

2. Run the TFTP server program on a PC (its IP address is 192.168.0.23), and set the working directory, TFTP username, and password. Store the upgrade file on the working directory of the TFTP server.

3. Make sure the PC and the router can reach each other.

4. Log in to the router, and access the root directory of the storage medium for the startup software images.

<Sysname> cd cfa0:/

NOTE:

5. Download the upgrade file (newest.ipe in this example) to the storage medium on the router.

<Sysname> tftp 192.168.0.23 get newest.ipe

Press CTRL+C to abort.

% Total % Received % Xferd Average Speed Time Time Time Current

Dload Upload Total Spent Left Speed

100 13.9M 100 13.9M 0 0 1206k 0 0:00:11 0:00:11 --:--:-- 1206k

Writing file...Done.

# Verify that the upgrade file has been in the root directory of the storage medium.

<Sysname> dir

# Use the MD5 algorithm to calculate the digest of the file, and compare it with the MD5 digest on the H3C website to verify file integrity.

<Sysname> md5sum newest.ipe

MD5 digest:

4f22b6190d151a167105df61c35f0917

Downloading software images from the BootWare menu

NOTE:

The BootWare menu varies by router model and BootWare version. This section uses a CF16000-F router as an example.

1. Set up an upgrade environment as described in "Preparing for the upgrade."

2. Run the TFTP server program on a PC (its IP address is 192.168.0.23), set the working directory, TFTP username, and password. Store the upgrade file on the working directory of the TFTP server.

3. Run the terminal emulation program on the PC, and power on the router. Press Ctrl+B at prompt to access the EXTENDED-BOOTWARE menu.

==========================<EXTENDED-BOOTWARE MENU>==========================

|<1> Boot System |

|<2> Enter Serial SubMenu |

|<3> Enter Ethernet SubMenu |

|<4> File Control |

|<5> Restore to Factory Default Configuration |

|<6> Skip Current System Configuration |

|<7> BootWare Operation Menu |

|<8> Skip Authentication for Console Login |

|<9> Storage Device Operation |

|<0> Reboot |

============================================================================

Ctrl+Z: Access EXTENDED ASSISTANT MENU

Ctrl+F: Format File System

Ctrl+C: Display Copyright

Enter your choice(0-9):

4. (Optional.) Set the default storage medium for downloading the upgrade file.

IMPORTANT:

If the storage medium storing the upgrade file is not the default storage medium, set it as the default storage medium.

# Enter 9 to access the storage device submenu.

==============================<DEVICE CONTROL>==============================

|<1> Display All Available Nonvolatile Storage Device(s) |

|<2> Set The Operating Device |

|<3> Set The Default Boot Device |

|<0> Exit To Main Menu |

============================================================================

Enter your choice(0-3):

# Enter 2 to set the storage medium for storing the upgrade file.

Please set the operating device:

============================================================================

|Note:the operating device is cfa0 |

|NO. Device Name File System Total Size Available Space |

|1 flash JFFS2 262144KB 224937KB |

|2 cfa0 FAT 2044256KB 1173684KB |

|0 Exit |

============================================================================

Enter your choice(0-2):

# Enter 2 to set the CF card as the storage medium for storing the upgrade file.

==============================<DEVICE CONTROL>==============================

|<1> Display All Available Nonvolatile Storage Device(s) |

|<2> Set The Operating Device |

|<3> Set The Default Boot Device |

|<0> Exit To Main Menu |

============================================================================

Enter your choice(0-3):

# Enter 3 to set the default storage medium.

Please set the default device:

============================================================================

|Note:the default device is cfa0 |

|NO. Device Name File System Total Size Available Space |

|1 flash JFFS2 262144KB 224937KB |

|2 cfa0 FAT 2044256KB 1173684KB |

|0 Exit |

============================================================================

Enter your choice(0-2):

# Enter 2 to set the CF card as the default storage medium.

==============================<DEVICE CONTROL>==============================

|<1> Display All Available Nonvolatile Storage Device(s) |

|<2> Set The Operating Device |

|<3> Set The Default Boot Device |

|<0> Exit To Main Menu |

============================================================================

Enter your choice(0-3):

# Enter 0 to exit the storage device submenu.

5. Download and upgrade the BootWare.

==========================<EXTENDED-BOOTWARE MENU>==========================

|<1> Boot System |

|<2> Enter Serial SubMenu |

|<3> Enter Ethernet SubMenu |

|<4> File Control |

|<5> Restore to Factory Default Configuration |

|<6> Skip Current System Configuration |

|<7> BootWare Operation Menu |

|<8> Skip Authentication for Console Login |

|<9> Storage Device Operation |

|<0> Reboot |

============================================================================

Ctrl+Z: Access EXTENDED ASSISTANT MENU

Ctrl+F: Format File System

Ctrl+C: Display Copyright

Enter your choice(0-9):

# Enter 3 to access the Ethernet submenu.

==========================<Enter Ethernet SubMenu>==========================

|Note:the operating device is cfa0 |

|<1> Download Image Program To SDRAM And Run |

|<2> Update Main Image File |

|<3> Update Backup Image File |

|<4> Download Files(*.*) |

|<5> Modify Ethernet Parameter |

|<0> Exit To Main Menu |

|<Ensure The Parameter Be Modified Before Downloading!> |

============================================================================

Enter your choice(0-5)::

# Enter 5 to configure the network settings.

==========================<ETHERNET PARAMETER SET>==========================

|Note: '.' = Clear field. |

| '-' = Go to previous field. |

| Ctrl+D = Quit. |

============================================================================

Protocol (FTP or TFTP) :tftp

Load File Name :test.bin

:newest.ipe

Target File Name :test.bin

:newest.ipe

Server IP Address :192.168.0.23

Local IP Address :192.168.0.105

Subnet Mask :255.255.255.0

Gateway IP Address :0.0.0.0

Table 11 Network parameter fields and shortcut keys

Field	Description
'.' = Clear field	Press a dot (.) and then press Enter to clear the setting for a field.
'-' = Go to previous field	Press a hyphen (-) and then press Enter to return to the previous field.
Ctrl+D = Quit	Press Ctrl+D to exit the ETHERNET PARAMETER SET menu.
Protocol (FTP or TFTP)	Set the file transfer protocol to FTP or TFTP.
Load File Name	Set the name of the file to be downloaded.
Target File Name	Set a file name for saving the file on the router. The target file name must have the same extension as the source file. By default, the target file name is the same as the source file name.
Server IP Address	Set the IP address of the FTP or TFTP server.
Local IP Address	Set the IP address of the Ethernet interface that connects to the TFTP server.
Subnet Mask	Set the IP address mask.
Gateway IP Address	Set a gateway IP address if the router is on a different network than the server.

After you finish setting the FTP parameters, the system returns to the Ethernet submenu. Choose option 2 to 3. For example, enter 2 to upgrade the main startup software images.

Loading.....................................................................

............................................................................

.........................Done!

31911744 bytes downloaded!

Image file BOOT.bin is self-decompressing... Saving file cfa0:/ BOOT.bin ..............................................Done.

Image file SYSTEM.bin is self-decompressing...Saving file cfa0:/ SYSTEM.bin .................................. ..Done.

# Enter 0 in the Ethernet submenu to return to the EXTENDED-BOOTWARE menu.

# Enter 0 to reboot the router.

Upgrade record form

Site name		Upgraded at
Router model		Router name
Version before upgrade		Version after upgrade
Upgrade team members	Team members from the site: Team members from H3C:
Upgrade result
Check items		Result	Unexpected situation handling
Before the upgrade	Check tools used to upgrade software.
	Identify the upgrade methods supported by the router.
	Check the upgrade environment.
	Check whether the router can be logged in.
	Prepare the required upgrade software images.
	View the current system software version.
	Check whether the router is running correctly.
	Check whether important data has been backed up.
	Check whether the storage medium has sufficient space to store the upgrade software images.
During the upgrade	Check the upgrade process.
	Check the TFTP or FTP server configuration.
	Check whether the software images have been downloaded successfully.
	Check the upgrade operation.
	(Optional.) Check the upgrade status of the standby MPU.
After the upgrade	Check the software version after the upgrade.
	Check the status of cards or subcards (modular router).
	Check whether the router is in stable state.
	Compare the memory usage and CPU usage before and after the upgrade to identify whether they are significantly different.
	Check whether the configuration has been restored.
	Check whether services are running correctly.

Acronyms

Abbreviation	Full spelling
FTP	File Transfer Protocol
TFTP	Trivial File Transfer Protocol

H3C Router Software Upgrade Guide-6W101

Startup software image subcategories

Main and backup startup software images

Before the upgrade:

During the upgrade:

After the upgrade:

Preparing for the upgrade

Logging in to the router

Checking the storage space

Identifying the storage medium

Verifying the free storage space

Deleting unused files

Identifying the storage medium from the BootWare menu

Verifying the free storage space

Deleting unused files

Upgrading the BootWare at the CLI on a single-MPU device (distributed devices in standalone mode)

Preparing for the upgrade

Downloading the upgrade file

Decompressing the .ipe file

Upgrading the BootWare

Rebooting the router

Preparing for the upgrade

Downloading the upgrade file

Decompressing the .ipe file

Upgrading the BootWare

Rebooting the router

Preparing for the upgrade

Downloading the upgrade file

Decompressing the .ipe file

Upgrading the BootWare

Rebooting the router

Preparing for the upgrade

Downloading the upgrade file

Decompressing the .ipe file

Upgrading the BootWare

Rebooting the router

Preparing for the upgrade

Downloading and upgrading the BootWare from the BootWare menu

Rebooting the router

Preparing for the upgrade

Downloading the upgrade file

Upgrading the startup software

Rebooting the router

Preparing for the upgrade

Downloading the upgrade file

Rebooting the router

Performing a compatible upgrade by using ISSU commands (distributed devices)

Preparing for the upgrade

Downloading the upgrade file

Identifying the recommended ISSU methods

Upgrading the startup software

Verifying the upgrade

Preparing for the upgrade

Downloading the upgrade file

Identifying the recommended ISSU methods

Upgrading the startup software

Verifying the upgrade

Performing an incompatible upgrade by using ISSU commands (distributed devices)

Preparing for the upgrade

Downloading the upgrade file

Identifying the recommended ISSU methods

Upgrading the startup software

Verifying the upgrade

Preparing for the upgrade

Downloading the upgrade file

Identifying the recommended ISSU methods

Upgrading the startup software

Verifying the upgrade

Preparing for the upgrade

Downloading the image file

Installing a patch

Uninstalling a patch

Installing features on a single-MPU device (distributed devices in standalone mode)

Preparing for the upgrade

Downloading the upgrade file

Decompressing the .ipe file

Installing a feature

Uninstalling a feature image

Preparing for the upgrade

Downloading the upgrade file