Each time the switch is powered on, it runs the BootWare image to initialize hardware, and display hardware information. Then, the switch runs the system software image (called "boot file" or "application file" in software code). The system software image provides drivers and adaption for hardware, and implements service features. The BootWare image and system software image are required for the startup and running of a switch.

Figure 1 System startup process

FIPS compliance

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

Software upgrade task list

The system software image file (with the file extension .bin) comprises the BootWare image and MBUS daughter card software, which are automatically upgraded when the system software image is upgraded. You can also upgrade the BootWare image and MBUS daughter card software separately.

To upgrade software from the CLI, perform the following tasks as appropriate:

Task	Remarks
Upgrading BootWare	Optional.
Upgrading the system software	Optional.
Installing hotfixes	Optional.
Upgrading MBUS daughter card software	Optional.
Upgrading CPLDs	Optional.
Upgrading or repairing the power software on an interface card	Optional.
Upgrading the clock monitor software	Optional.

Upgrading BootWare

The BootWare image is automatically upgraded when you upgrade the system software image. You can also perform the tasks in this section to upgrade the BootWare image separately.

To upgrade the BootWare image on an MPU, save the upgrade file in the root directory of a storage medium on the MPU.

To upgrade the BootWare image for an interface card or a base card:

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

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

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

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

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

After upgrading the BootWare, you must restart the switch to validate the upgrade.

To upgrade the BootWare on a card:

Task	Command	Remarks
Upgrade the BootWare on a card (in standalone mode).	bootrom update file file-url slot slot-number-list	Available in user view.
Upgrade the BootWare on a card (in IRF mode).	bootrom update file file-url chassis chassis-number slot slot-number-list	Available in user view.

To upgrade the BootWare of the OAM modules on an MPU:

Task	Command	Remarks
Upgrade the BootWare of the OAM module on an MPU (in standalone mode).	oam-bootrom update file file-url slot slot-number	Available in user view.
Upgrade the BootWare of the OAM module on an MPU (in IRF mode).	oam-bootrom update file file-url chassis chassis-number slot slot-number	Available in user view.

Upgrading the system software

To upgrade the system software (in standalone mode):

1. Use FTP, TFTP, or any other method to save the upgrade system software image file to the root directory of the active MPU's storage medium (Flash or CF card).

2. Copy the image file to the root directory of the standby MPU's storage medium (Flash or CF card).

3. Specify the file as the main startup system software image file on both MPUs. For more information, see "Specifying a startup system software image."

4. Reboot the switch to complete the upgrade.

To upgrade the system software (in IRF mode):

1. Use FTP, TFTP, or any other method to save the upgrade system software image to the root directory of the global active MPU's storage medium (Flash or CF card).

2. Copy the image file to the root directory of the storage medium (Flash or CF card) on each MPU in the IRF fabric.

3. Specify the system software image as the main startup system software image on all the MPUs. For more information, see "Specifying a startup system software image."

4. Reboot the switch to complete the upgrade.

Specifying a startup system software image

You can specify one main startup system software image and one backup startup system software image on each MPU. The main system software image is always preferred over the backup system image at startup.

The startup system software image files must be saved in the root directory of the Flash or CF card. If a partitioned CF card is used, the image files must be saved in the root directory of the first partition.

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

To upgrade system software image:

Task	Command	Remarks
Specify a startup system software image (in standalone mode).	boot-loader file file-url slot slot-number { main \| backup }	Available in user view.
Specify a startup system software image (in IRF mode).	boot-loader file file-url chassis chassis-number slot slot-number { main \| backup }	Available in user view.

Synchronizing the main startup system software image from the active MPU to the standby MPU in standalone mode

This section does not apply to the IRF mode.

Use the display device command to examine the state of the standby MPU.

If its state is Fault, upgrade the standby MPU from the BootWare menu or remove the standby MPU and upgrade it.

If its state is Slave, execute the boot-loader update command. The system automatically upgrades the system software on the standby MPU to be the same as the active MPU, and reboots the standby MPU with the new system software image.

Before upgrading system software for the standby MPU, verify that the standby MPU has sufficient storage space for the new system software image. If the sum of the free space and the space occupied by the old system software image is greater than the size of the new system software image, the switch automatically deletes the old system software image before the upgrade.

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

To upgrade system software on the standby MPU:

Task	Command	Remarks
Synchronize the main startup system software image from the active MPU to the standby MPU (in standalone mode).	boot-loader update slot slot-number	Available in user view.

Installing hotfixes

Hotfixes (called "patches" in this document) repair software defects without requiring a system reboot.

Basic concepts

Patch, patch file and patch package file

A patch fixes certain software defects.

A patch file contains one or more patches. A patch package file contains patch files for multiple features. It enables you to use one command to bulk-fix bugs for multiple features.

Incremental patch

Incremental patches add enhancements to the system.

Patches that have been released are all incremental patches.

Common patch and temporary patch

Common patches are formally released to users.

Temporary patches are interim solutions that are provided to fix critical bugs. They are not formally released.

A common patch always includes the functions of its previous temporary patches. The system deletes all the temporary patches before loading the common patch.

Patch states

A patch is in IDLE, DEACTIVE, ACTIVE, or RUNNING state, depending on the patch manipulation command.

Patch manipulation commands include patch load (load), patch active (run temporarily), patch run (confirm running), patch deactive (stop running), patch delete (delete), patch install (install), and undo patch install (uninstall).

For example, if you execute the patch active command, patches in DEACTIVE state change to the ACTIVE state.

Figure 2 shows the patch manipulation commands and how they affect the patch state.

IMPORTANT:

Patch state information is saved in the patchstate file on the Flash. To make sure the switch can correctly find the patches, do not edit, delete, move the file, or change the file name.

Figure 2 Impact of patch manipulation commands on patch state

IDLE state

Patches that have not been loaded are in IDLE state. You cannot install or run these patches. As shown in Figure 3, the patch memory area can load up to eight patches.

The patch memory area supports up to 200 patches.

Figure 3 Patches that are not loaded to the patch memory area

DEACTIVE state

Patches in DEACTIVE state have been loaded to the patch memory area but have not yet run in the system. Suppose the patch file you are loading has seven patches. After the seven patches successfully pass the version check and CRC check, they are loaded to the patch memory area and are in DEACTIVE state. In the patch memory area, patch states are as shown in Figure 4.

Figure 4 Patch states in the patch memory area after a patch file is loaded

ACTIVE state

Patches in ACTIVE state run temporarily in the system and become DEACTIVE at a reboot. For the seven patches in Figure 4, if you activate the first five patches, their states change from DEACTIVE to ACTIVE. The patch states in the system are as shown in Figure 5.

The patches that are in ACTIVE state are in DEACTIVE state after at a reboot.

Figure 5 Patches are activated

RUNNING state

After you confirm ACTIVE patches, their states change to RUNNING and persist after a reboot. In contrast to ACTIVE patches, RUNNING patches continue to take effect after a reboot. For example, if you confirm the first three patches in Figure 5, their states change from ACTIVE to RUNNING, and the RUNNING state persists after a reboot. The patch states of the system are as shown in Figure 6.

The patches that are in RUNNING state are still in RUNNING state after system reboot.

Figure 6 Patches in RUNNING state

Hotfix configuration task list

Task	Remarks
Install patches: · Installing and running a patch in one step · Installing a patch step by step	Use either method. Step-by-step patch installation allows you to control the patch status.
Uninstalling a patch step by step	Optional.

Task

Remarks

Install patches:

· Installing and running a patch in one step

· Installing a patch step by step

Use either method.

Step-by-step patch installation allows you to control the patch status.

Uninstalling a patch step by step

Optional.

Installation prerequisites

To ensure a successful hotfix operation and normal switch operation after the hotfix operation:

· Make sure each patch file you are installing matches the device model, card type, and software version.

· In standalone mode, save the patch files for the active MPU, base cards or interface cards to the root directory of the active MPU's storage media, and save the patch files for the standby MPU to the root directory of the standby MPU's storage media.

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

· Make sure the patch files for the active MPU and the standby MPU are the same.

· To use a patch package file, save the patch package file to the root directory of a storage medium on each MPU before patch installation.

· If a partitioned CF card is used, save the patch files or patch package files to the root directory of the first partition.

· Correctly name a patch file in the patch_PATCH-FLAG suffix.bin format. The PATCH-FLAG suffix is pre-defined and must be the same as the letters (digits are excluded) displayed for the Version field in the output from the display patch information command. The system searches the root directory of the storage media (Flash by default) for patch files based on the PATCH-FLAG. If a patch file is not correctly named, the system cannot identify the file.

Installing and running a patch in one step

To install and run patches in one step, execute the patch install command. This command changes the state of installed patches from IDLE to ACTIVE or RUNNING, depending on your choice.

When executing the patch install command, you must choose to run installed patches or disable running them after a reboot. If you choose to have installed patches continue to run after a reboot, the installed patches are set in RUNNING state and remain in this state after a reboot. If not, the installed patches are set in ACTIVE state and change to the DEACTIVE state at a reboot.

To install and run patches in one step:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Install and run patches in one step.	patch install { patch-location \| file filename }	In FIPS mode, the patch file or the patch package file must pass authenticity verification before the command is executed. In this command: · patch-location—Specifies the directory where the patch file is located. · file filename—Specifies a patch package file name.

Step

Command

Remarks

1. Enter system view.

system-view

N/A

2. Install and run patches in one step.

patch install { patch-location | file filename }

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

In this command:

· patch-location—Specifies the directory where the patch file is located.

· file filename—Specifies a patch package file name.

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

If you execute the patch install file filename command, the directory specified with the patch location command does not change.

To uninstall all ACTIVE and RUNNING patches in one step, use the undo patch install command. H3C recommends this command for uninstalling patches in an IRF fabric. For information about the step-by-step patch uninstall method, see "Uninstalling a patch step by step."

Installing a patch step by step

In contrast to the one-step patch installation method, step-by-step patch installation enables you to control patch status during the patch installation process.

Step-by-step patch installation task list

Task	Remarks
Configuring the patch file location	Optional. To install a patch package, skip this step.
Loading a patch file	N/A
Activating patches	N/A
Confirming ACTIVE patches	Optional.

Configuring the patch file location

For reliable patch loading, H3C recommends saving patch files to the root directory of the Flash. To use a storage medium other than Flash, you must specify the directory for saving patch files on the storage medium.

Make sure the specified patch file directory has been created on each MPU.

To configure the patch file location:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Configure the patch file location.	patch location patch-location	Optional. By default, the patch file location is flash:.

Step

Command

Remarks

1. Enter system view.

system-view

N/A

2. Configure the patch file location.

patch location patch-location

Optional.

By default, the patch file location is flash:.

NOTE:

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

Loading a patch file

Loading patch files is the basis of other hotfix operations.

The patch files for MPUs, interface cards, and OAM modules are patch_mr.bin, patch_lc.bin, and patch_oam.bin, respectively.

To prevent patch state loss, the patch files on MPUs must be the same for patch state backup.

The active MPU and standby MPU get their patch files from their respective storage media.

By default, the system loads a patch file from Flash.

IMPORTANT:

Set the file transfer mode to binary mode before using FTP or TFTP to upload or download patch files to or from the switch's Flash. Otherwise, patch files cannot be parsed correctly.

To load a patch file:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Load the patch file from the storage medium (Flash or CF card) to the patch memory area.	· In standalone mode: patch load slot slot-number · In IRF mode: patch load chassis chassis-number slot slot-number	In FIPS mode, the patch package file or the patch file must pass authenticity verification before it can be loaded.

Step

Command

Remarks

1. Enter system view.

system-view

N/A

2. Load the patch file from the storage medium (Flash or CF card) to the patch memory area.

· In standalone mode:
patch load slot slot-number

· In IRF mode:
patch load chassis chassis-number slot slot-number

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

Activating patches

Activating a patch changes its state to ACTIVE. An ACTIVE patch runs in memory until a reboot occurs. To have a patch continue to run after a reboot, you must change its state to RUNNING.

To activate patches:

Step	Command
1. Enter system view.	system-view
2. Activate patches.	· In standalone mode: patch active patch-number slot slot-number · In IRF mode: patch active patch-number chassis chassis-number slot slot-number

Step

Command

1. Enter system view.

system-view

2. Activate patches.

· In standalone mode:
patch active patch-number slot slot-number

· In IRF mode:
patch active patch-number chassis chassis-number slot slot-number

Confirming ACTIVE patches

To have an ACTIVE patch continue to run after a reboot, perform the task in this section.

After you confirm an ACTIVE patch, its state changes to RUNNING and persists after a reboot.

To confirm ACTIVE patches:

Step	Command
1. Enter system view.	system-view
2. Confirm ACTIVE patches.	· In standalone mode: patch run patch-number [ slot slot-number ] · In IRF mode: patch run patch-number [ chassis chassis-number slot slot-number ]

Step

Command

1. Enter system view.

system-view

2. Confirm ACTIVE patches.

· In standalone mode:
patch run patch-number [ slot slot-number ]

· In IRF mode:
patch run patch-number [ chassis chassis-number slot slot-number ]

Uninstalling a patch step by step

To uninstall a patch by using the step-by-step method, you must first stop running the patch and then remove it from the patch memory area.

Stopping running patches

After you stop running a patch, the patch state becomes DEACTIVE, and the system runs the way it did before it was installed with the patch.

To stop running patches:

Step	Command
1. Enter system view.	system-view
2. Stop running patches.	· In standalone mode: patch deactive patch-number slot slot-number · In IRF mode: patch deactive patch-number chassis chassis-number slot slot-number

Step

Command

1. Enter system view.

system-view

2. Stop running patches.

· In standalone mode:
patch deactive patch-number slot slot-number

· In IRF mode:
patch deactive patch-number chassis chassis-number slot slot-number

Removing patches from the patch memory area

After being removed from the patch memory area, a patch is still retained in IDLE state in the storage media. The system runs in the way before it was installed with the patch.

In an IRF fabric, H3C recommends that you uninstall all patches by using the undo patch install command.

To remove patches:

Step	Command
1. Enter system view.	system-view
2. Remove patches from the patch memory area.	· In standalone mode: patch delete patch-number slot slot-number · In IRF mode: patch delete patch-number chassis chassis-number slot slot-number

Step

Command

1. Enter system view.

system-view

2. Remove patches from the patch memory area.

· In standalone mode:
patch delete patch-number slot slot-number

· In IRF mode:
patch delete patch-number chassis chassis-number slot slot-number

Upgrading MBUS daughter card software

Typically, the MBUS daughter card software is automatically upgraded when the system software image is upgraded. If the auto-upgrade fails, you can use the mbus update command to upgrade it.

To ensure a successful upgrade, follow these guidelines:

· In an IRF fabric, save the upgrade file on the active MPU in the same chassis as the MBUS daughter card. If you are upgrading the master switch, the file can also be saved on the standby MPU.

· Make sure no one performs any of the following operations during the upgrade:

¡ Perform an active/standby switchover.

¡ Power off or reboot the switch.

¡ Reboot or swap the active MPU.

To upgrade MBUS daughter card software, perform one of the following tasks in user view:

Task	Command
Upgrade the MBUS daughter card software on a card (in standalone mode).	mbus update [ file file-url ] slot slot-id
Upgrade the MBUS daughter card software on a card (in IRF mode).	mbus update [ file file-url ] chassis chassis-number slot slot-number

Upgrading CPLDs

To ensure a successful CPLD upgrade, follow these guidelines:

· In IRF mode, the CPLD upgrade file for a subordinate switch must be saved on its active MPU, and the CPLD upgrade file for the master switch can be saved on its active or standby MPU.

· Make sure no one performs any of the following operations during the upgrade:

¡ Perform an active/standby switchover.

¡ Power off or reboot the switch.

¡ Reboot or swap the active MPU.

When the upgrade is complete, the card automatically reboots to validate the upgraded CPLD.

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

Upgrading a CPLD on an interface card or MPU

Step	Command	Remarks
1. Set the interface card in offline state.	a. Enter system view. system-view b. Isolate the interface card. In standalone mode: board-offline slot slot-number In IRF mode: board-offline chassis chassis-number slot slot-number c. Return to user view. quit	Skip this step if you are upgrading CPLDs for an MPU. In offline state, an interface card cannot forward traffic.
2. Upgrade a CPLD on the interface card or MPU in user view.	· In standalone mode: logic update bymbus [ file filename ] slot slot-number logicid logicid · In IRF mode: logic update bymbus [ file filename ] chassis chassis-number slot slot-number logicid logicid	The logicid argument specifies the CPLD type: · 0—Card (interface card or MPU) CPLD. · 1—OAM module CPLD on an MPU, or CPU CPLD on an interface card. · 2—NP module CPLD on a base card. (Only supported by LSR1LN2BNL1.)

Step

Command

Remarks

1. Set the interface card in offline state.

a. Enter system view.
system-view

b. Isolate the interface card.
In standalone mode:
board-offline slot slot-number
In IRF mode:
board-offline chassis chassis-number slot slot-number

c. Return to user view.
quit

Skip this step if you are upgrading CPLDs for an MPU.

In offline state, an interface card cannot forward traffic.

2. Upgrade a CPLD on the interface card or MPU in user view.

· In standalone mode:
logic update bymbus [ file filename ] slot slot-number logicid logicid

· In IRF mode:
logic update bymbus [ file filename ] chassis chassis-number slot slot-number logicid logicid

The logicid argument specifies the CPLD type:

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

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

· 2—NP module CPLD on a base card. (Only supported by LSR1LN2BNL1.)

Upgrading a CPU CPLD on a base card or a CPLD on a subcard

This task can be performed only in standalone mode.

Perform the following task in user view:

Task	Command	Remarks
Upgrade a CPU CPLD on a base card or a CPLD on a subcard.	logic update [ file filename ] slot slot-number [ subslot subslot-number ] logicid logicid	Values for logicid: · 1—CPU CPLD on a base card. · 4—Interface subcard CPLD.

Task

Command

Remarks

Upgrade a CPU CPLD on a base card or a CPLD on a subcard.

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

Values for logicid:

· 1—CPU CPLD on a base card.

· 4—Interface subcard CPLD.

For information about base cards and subcards, see H3C S9500E Switch Series Installation Guide.

Upgrading or repairing the power software on an interface card

Upgrade or repair the power software on an interface card if the card is not correctly powered.

To ensure a successful upgrade, follow these guidelines:

· In an IRF fabric, save the upgrade file on the active MPU in the same chassis as the card you are working with. If you are upgrading for the master device, you can save the file on its active MPU or standby MPU.

· Make sure no one performs any of the following operations during the upgrade:

¡ Perform an active/standby switchover.

¡ Power off the switch.

¡ Reboot or swap the active MPU or the card you are working with.

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

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

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

To upgrade the power software on an interface card:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Set the interface card in offline state.	· In standalone mode: board-offline slot slot-number · In IRF mode: board-offline chassis chassis-number slot slot-number	In offline state, a card cannot forward traffic.
3. Return to user view.	quit	N/A
4. Upgrade the power software on the isolated card.	· In standalone mode: power-logic update [ file file-url ] slot slot-id · In IRF mode: power-logic update [ file file-url ] chassis chassis-id slot slot-id	The command is not available for MPUs.

Upgrading the clock monitor software

All clock-related services are affected during the upgrade process.

To ensure a successful upgrade, follow these guidelines:

· The clock update command is only available for the LSR1SRP2D1 MPU.

· The upgrade file must be saved on the MPU where the clock monitor module is located.

· Make sure no one performs any of the following operations during the upgrade:

¡ Perform an active/standby switchover.

¡ Reset the current clock monitor module.

¡ Power off the switch.

¡ Reboot or swap the active MPU.

You must wait a while for the upgrade to complete.

To upgrade clock monitor software for an MPU, perform one of the following tasks in user view:

Task	Command
Upgrade the clock monitor software on an MPU (in standalone mode).	clock update [ file file-url ] slot slot-id
Upgrade the clock monitor software on an MPU (in IRF mode).	clock update [ file file-url ] chassis chassis-number slot slot-id

For information about the clock monitor module, see Network Management and Monitoring Configuration Guide.

Displaying and maintaining software image settings

Task	Command	Remarks
Display system software image information (in standalone mode).	display boot-loader [ slot slot-number ] [ \| { begin \| exclude \| include } regular-expression ]	Available in any view.
Display system software image information (in IRF mode).	display boot-loader [ chassis chassis-number [ slot slot-number ] ] [ \| { begin \| exclude \| include } regular-expression ]	Available in any view.
Display patch package information.	display patch [ \| { begin \| exclude \| include } regular-expression ]	Available in any view.
Display patch information.	display patch information [ \| { begin \| exclude \| include } regular-expression ]	Available in any view.

Software upgrade examples

By default, Ethernet interfaces, VLAN interfaces, and aggregate interfaces are down. To configure such an interface, use the undo shutdown command to bring it up first.

System software image upgrade example (in standalone mode)

Network requirements

As shown in Figure 7, the current software version is soft-version1. The newest applications soft-version2.bin is saved in the aaa directory of the FTP server. The device and the FTP server can reach each other, and the user and the device can reach each other.

Remotely upgrade the software version of Device to soft-version2.

Figure 7 Network diagram

Upgrade procedure

1. Configure the FTP server (configurations varies with servers):

# Enable the FTP server.

<FTP-Server> system-view

[FTP-Server] ftp server enable

# Set the FTP username to aaa and password to hello.

[FTP-Server] local-user aaa

[FTP-Server-luser-aaa] password cipher hello

# Assign the FTP user the right to access the aaa directory.

[FTP-Server-luser-aaa] service-type ftp

[FTP-Server-luser-aaa] authorization-attribute work-directory flash:/aaa

2. Configure the device:

# Examine the free space of the Flash on the device for memory insufficiency. If the free space is not sufficient for the new application programs, delete unused files from the Flash. (Details not shown.)

# Execute the save command to save the current configuration. (Details not shown.)

# Log in to the FTP server.

<Device> ftp 2.2.2.2

Trying 2.2.2.2 ...

Press CTRL+K to abort

Connected to 2.2.2.2.

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

User(2.2.2.2:(none)):aaa

331 Give me your password, please

Password:

230 Logged in successfully

[ftp]

# Download the soft-version2.bin program from FTP server to the active MPU.

[ftp] binary

[ftp] get soft-version2.bin

[ftp] bye

# Specify the main startup system software image on the active MPU.

<Device> boot-loader file soft-version2.bin slot 0 main

# Copy the image from the active MPU to the standby MPU.

<Device> copy soft-version2.bin slot1#flash:/soft-version2.bin

# Specify the image as the main startup system software image on the standby MPU.

<Device> boot-loader file slot1#flash:/soft-version2.bin slot 1 main

# Reboot the device to complete the upgrade.

<Device> reboot

3. Use the display version command to verify the upgrade.

System software image upgrade example (in IRF mode)

Network requirements

The IRF fabric in Figure 8 has two member devices: the master with the member ID 1 and the subordinate switch with the member ID 2. Each member has an active MPU in slot 0 and a standby MPU in slot 1. The current software version is soft-version1 for the IRF fabric. The latest application soft-version2.bin and the latest configuration file new-config.cfg are both saved on the TFTP server. The TFTP server and the IRF fabric can reach each other.

Upgrade the software version of the IRF fabric to soft-version2 and configuration file to new-config.

Figure 8 Network diagram

Upgrade procedure

1. Configure the TFTP server. (Details not shown.)

2. Configure the IRF member switches:

# Download new-config.cfg from the TFTP server to the active MPU of the master.

<IRF> tftp 2.2.2.2 get new-config.cfg

File will be transferred in binary mode

Downloading file from remote TFTP server, please wait.....

TFTP: 917 bytes received in 1 second(s)

File downloaded successfully.

<IRF> copy new-config.cfg chassis1#slot1#flash:/new-config.cfg

# Download new-config.cfg to the active MPU of the subordinate switch.

<IRF> copy new-config.cfg chassis2#slot0#flash:/new-config.cfg

<IRF> copy new-config.cfg chassis2#slot1#flash:/new-config.cfg

# Download soft-version2.bin from the TFTP server to the master and the subordinate switches.

<IRF> tftp 2.2.2.2 get soft-version2.bin

...

File will be transferred in binary mode

Downloading file from remote TFTP server, please wait............

TFTP: 10058752 bytes received in 141 second(s)

File downloaded successfully.

<IRF> copy soft-version2.bin chassis1#slot1#flash:/soft-version2.bin

<IRF> copy soft-version2.bin chassis2#slot0#flash:/soft-version2.bin

<IRF> copy soft-version2.bin chassis2#slot1#flash:/soft-version2.bin

# Specify new-config.cfg as the next-startup configuration file for all member devices of the IRF fabric.

<IRF> startup saved-configuration flash:/new-config.cfg

Please wait ...

Setting the master board ...

... Done!

Setting the slave board ...

Chassis 1 Slot 1:

Set next configuration file successfully.

Chassis 2 Slot 0:

Set next configuration file successfully.

Chassis 2 Slot 1:

Set next configuration file successfully.

# Specify soft-version2.bin as the main startup system software image for all MPUs.

<IRF> boot-loader file flash:/soft-version2.bin chassis 1 slot 0 main

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

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

<IRF> boot-loader file chassis1#slot1#flash:/soft-version2.bin chassis 1 slot 1 main

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

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

<IRF> boot-loader file chassis2#slot0#flash:/soft-version2.bin chassis 2 slot 0 main

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

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

<IRF> boot-loader file chassis2#slot1#flash:/soft-version2.bin chassis 2 slot 1 main

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

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

# Reboot the device to complete the upgrade.

<IRF> reboot

3. Use the display version command to verify the upgrade.

Scheduled upgrade configuration example

Network requirement

The device in Figure 9 is running the system software version soft-version1. Download the latest software file soft-version2.bin from the aaa directory of the FTP server for an software upgrade.

Figure 9 Network diagram

Configuration procedure

This example assumes that the device and the FTP server can reach each other, and the user and the device can reach each other.

1. Configure the FTP server (configurations varies with servers):

# Enable the FTP server.

<FTP-Server> system-view

[FTP-Server] ftp server enable

# Set the FTP username to aaa and password to hello.

[FTP-Server] local-user aaa

[FTP-Server-luser-aaa] password cipher hello

# Assign the FTP user the right to access the flash:/aaa directory.

[FTP-Server-luser-aaa] service-type ftp

[FTP-Server-luser-aaa] work-directory flash:/aaa

Use text editor on the FTP server to edit batch file auto-update.txt. The following is the content of the batch file:

return

boot-loader file soft-version2.bin slot 0 main

boot-loader file slot1#flash:/soft-version2.bin slot 1 main

save

reboot

2. Configure the device:

# Execute the save command to save the current configuration. (Details not shown.)

# Log in to FTP Server. (The prompt might vary with servers.)

<Device> ftp 2.2.2.2

Trying 2.2.2.2 ...

Press CTRL+K to abort

Connected to 2.2.2.2.

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

User(2.2.2.2:(none)):aaa

331 Give me your password, please

Password:

230 Logged in successfully

[ftp]

# Download soft-version2.bin from the FTP server.

[ftp] binary

[ftp] get soft-version2.bin

[ftp] bye

# Change the extension of file auto-update.txt to .bat.

<Device> rename auto-update.txt auto-update.bat

To ensure correctness of the file, use the more command to view the content of the file.

<Device> more flash:/auto-update.txt

return

boot-loader file soft-version2.bin slot 0 main

boot-loader file slot1#flash:/soft-version2.bin slot 1 main

save

reboot

# Specify soft-version2.bin as the startup system software image for all MPUs. Execute the scheduled automatic execution function to enable the device to be automatically upgraded at 1 am June 21st, 2010. (Slot number of the active MPU is 0, and that of the standby MPU is 1.)

<Device> copy soft-version2.bin slot1#flash:/soft-version2.bin

<Device> schedule job at 01:00 2010/6/21 view system execute auto-update.bat

3. Use the display version command to verify the upgrade.

Hotfix configuration example

Network requirements

The software running on the device is of some problem. The patch file patch_mr.bin is saved in the aaa directory of the FTP server. The device and the FTP server can reach each other, and the user and the device can reach each other.

Use FTP to download the patch files and then hotfix the software on the device.

Figure 10 Network diagram

Configuration procedure

1. Configure the FTP server:

# Enable the FTP server.

<FTP-Server> system-view

[FTP-Server] ftp server enable

# Set the FTP username to aaa and password to hello.

[FTP-Server] local-user aaa

[FTP-Server-luser-aaa] password cipher hello

# Assign the FTP user the right to access the aaa directory.

[FTP-Server-luser-aaa] service-type ftp

[FTP-Server-luser-aaa] authorization-attribute work-directory flash:/aaa

2. Configure the device (FTP client):

# Examine the free space of the Flash on the device for memory insufficiency. If the free space is not sufficient for the patch file, delete unused files from the Flash. (Details not shown.)

# Use the save command to save the current system configuration. (Details not shown.)

# Log in to the FTP server.

<Device> ftp 2.2.2.2

Trying 2.2.2.2 ...

Press CTRL+K to abort

Connected to 2.2.2.2.

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

User(2.2.2.2:(none)):aaa

331 Give me your password, please

Password:

230 Logged in successfully

[ftp]

# Download the file patch_mr.bin from the FTP server.

[ftp] binary

[ftp] get patch_mr.bin

[ftp] bye

# Copy the patch file to the root directory of the standby MPU in slot 1.

<Device> copy patch_mr.bin slot1#flash:/

# Install patches.

<Device> system-view

[Device] patch install flash:

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

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

Installing patches........

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

01-Fundamentals Configuration Guide

Synchronizing the main startup system software image from the active MPU to the standby MPU in standalone mode

Patch, patch file and patch package file

Incremental patch

Common patch and temporary patch

IDLE state

DEACTIVE state

ACTIVE state

RUNNING state

Hotfix configuration task list

Displaying and maintaining software image settings

Software upgrade examples

System software image upgrade example (in standalone mode)

Network requirements

Network requirements

Upgrade procedure

Network requirement

Configuration procedure

Network requirements

Configuration procedure

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program

Global Learning

Partner Sales Resources

Service Business

News & Events

Contact Us