Software upgrade enables you to add new features and fix bugs. This chapter describes types of software and procedures to upgrade software from the CLI without using ISSU. For a comparison of all software upgrade methods, see "Upgrade methods."

When you upgrade software, you do not need to upgrade MPUs and interface cards separately. The software images are integrated for MPUs and interface cards. The interface cards upgrade automatically when you upgrade MPUs.

In an IRF 3 system, the parent devices and PEXs use separate software images. You must specify software images for the parent devices and PEXs separately. For more information about IRF 3, see Virtual Technologies Configuration Guide.

Unless otherwise stated, the term "IRF system" refers to both IRF fabrics and IRF 3 systems. The term "IRF fabric" refers to both a standalone IRF fabric and the parent fabric in an IRF 3 system.

NOTE:

In an IRF 3 system, the master device on the parent fabric is also the master of the entire system.

Software types

The following software types are available:

· BootWare image—A .bin file that 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. You can use these menus to load software and the startup configuration file or manage files when the device cannot start up correctly. For easy software compatibility management, the BootWare image is contained in the Boot image file. The BootWare image is upgraded automatically when the Boot image is upgraded.

· Comware image—Includes the following image subcategories:

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

¡ System image—A .bin file that contains the minimum feature modules required for device operation and some basic features, including device management, interface management, configuration management, and routing. To have advanced features, you must purchase feature images.

¡ Feature image—A .bin file that contains advanced software features. Users purchase feature images as needed.

¡ Patch image—A .bin file irregularly released for fixing bugs without rebooting the device. A patch image does not add new features or functions.

Comware images that have been loaded are called current Comware images. Comware images specified to load at the next startup are called startup Comware images.

BootWare image, boot image, and system image are required for the system to operate. These images might be released separately or as a whole in one .ipe package file. If an .ipe file is used, the system decompresses the file automatically, loads the .bin images, and sets them as startup software images.

NOTE:

BootWare might be called Boot ROM on PEXs. Unless otherwise stated, the term "BootWare" refers to both BootWare and Boot ROM in this document.

Software file naming conventions

Software image file names use the chassis-comware version-image type-release format, for example, S7500E-CMW710-SYSTEM-R7178.bin and S7500E-CMW710-BOOT-R7178.bin.

Comware image redundancy and loading procedure

You can specify one main and one backup list of Comware software images.

The system always attempts to start up with the main images. If any main images do not exist or are invalid, the system tries the backup images. Figure 1 shows the entire Comware image loading procedure.

In this procedure, both the main and backup image lists have feature and patch images. If an image list does not have feature or patch images, the system starts up with the main boot and system images after they pass verification.

If both the main and backup boot images do not exist or are invalid, access the BootWare menu during the system startup to upgrade software.

Figure 1 Comware image loading procedure

System startup process

Upon power-on, the BootWare image runs to initialize hardware, and then the startup software images run to start up the entire system, as shown in Figure 2.

Figure 2 System startup process

PEX startup process

PEX startup process differs depending on the availability of storage media on PEXs.

· If a PEX has a storage medium, it can start up from the local medium or from the medium on the parent device.

· If a PEX does not have a storage medium, it must start up from the storage medium on the master device.

The following switches can be PEXs in an IRF 3 system:

· S5120-28SC-HI.

· S5120-52SC-HI.

· S5130-EI.

· S5130-HI.

· S6300.

The S5130-EI, S5130-HI, and S6300 switches have storage media, but the S5120-28SC-HI and S5120-52SC-HI switches do not.

NOTE:

The PEX startup images on the PEX's local medium are called local startup images. The PEX startup images on the parent devices are called remote startup images.

Startup process for S6300 and S5130-EI PEXs

1. Upon power-on, the PEX runs the BootWare image to initialize hardware and display hardware parameters.

2. The PEX attempts to load software images from its local storage medium (see Figure 4):

a. The PEX searches the local storage medium for startup images:

- If all the images exist and are valid, the PEX moves to step b.

- If any images do not exist or are invalid, the PEX goes to step 3.

b. The system verifies the compatibility of the PEX startup software images with the running software images of the global active MPU:

- If all the images are compatible, the PEX starts up with the images in the local medium.

- If any incompatibility exists, the PEX goes to step 3.

3. The PEX attempts to load software images from the global active MPU (see Figure 5):

a. The PEX searches the default storage medium on the global active MPU for PEX startup images:

- If all the images exist and are valid, the PEX moves to step b.

- If any images do not exist or are invalid, the startup process fails. You must specify new PEX startup images from the CLI or from the PEX's BootWare menus.

b. The PEX verifies the compatibility of the PEX startup software images with the running software images on the global active MPU:

- If the images are compatible, the PEX loads the PEX software images from the global active MPU.

- If any incompatibility exists, the startup process fails. You must specify new PEX startup images from the CLI or from the PEX's BootWare menus.

Figure 3 Generic startup process for S6300 PEXs

Figure 4 S6300 PEX startup from the local medium

Figure 5 S6300/S5120-HI PEX startup from the parent device's storage medium

Startup process for S5120-HI PEXs

1. Upon power-on, the PEX runs the BootWare image to initialize hardware and display hardware parameters.

2. The PEX attempts to load software images from the master device (see Figure 6):

a. The PEX searches the default storage medium on the global active MPU for the startup images:

- If all the images exist and are valid, the PEX goes to step b.

- If any images do not exist or are invalid, the startup process fails. You must specify new PEX startup images from the CLI.

b. The PEX verifies the compatibility of the PEX startup software images with the running software images on the global active MPU (see Figure 5):

- If the images are compatible, the PEX loads the PEX software images from the global active MPU.

- If any incompatibility exists, the startup process fails. You must specify new PEX startup images from the CLI or from the PEX's BootWare menus.

Figure 6 Startup process for S5120-HI PEXs

Upgrade methods

Upgrading method	Software types	Remarks
Upgrading from the CLI without using ISSU	· BootWare image · Comware images (excluding patches)	This method is disruptive. You must reboot the entire device to complete the upgrade.
Performing an ISSU	Comware images	The ISSU method enables a software upgrade without service interruption. Use this method for an IRF fabric. For more information about ISSU, see "Performing ISSU."
Upgrading from the BootWare menu	· BootWare image · Comware software images	Use this method when the device cannot start up correctly. To use this method, first connect to the console port and power cycle the switch or PEX. Then press Ctrl+B at prompt to access the BootWare menu. For more information about upgrading software from the BootWare menu, see the release notes for the software version. IMPORTANT: Upgrade an IRF system from the CLI rather than the BootWare menu, if possible. The BootWare menu method increases the service downtime, because it requires that you upgrade the member devices one by one.

This chapter only covers upgrading software from the CLI without using ISSU.

Upgrade restrictions and guidelines

The switch starts up from the default storage medium. The default storage medium can be the built-in flash memory or a USB disk. To change the default storage medium setting, access the BootWare menu. For more information, see the release notes for the switch.

H3C recommends that you store the startup images in the flash memory and specify the flash memory as the default storage medium.

If the switch is starting up from a USB disk, do not remove the USB disk during startup.

Preparing for the upgrade

1. Use the display version command to verify the current BootWare image version and startup software version.

2. Use the release notes for the upgrade software version to evaluate the upgrade impact on your network and verify the following items:

¡ Software and hardware compatibility.

¡ Version and size of the upgrade software.

¡ Compatibility of the upgrade software version with the current BootWare image and startup software image version.

¡ Licensing requirements for the upgrade software images. If licenses are required, register and activate licenses for each license-based software image. For more information about licensing, see "Managing licenses."

3. Use the dir command to verify that all MPUs have sufficient storage space in the default storage medium for the upgrade images. If the storage space is not sufficient, delete unused files by using the delete command. For more information, see "Managing the file system."

4. Use FTP or TFTP to transfer the upgrade image file to the root directory of the default storage medium on the active MPU (in standalone mode) or the global active MPU (in IRF mode).

For more information about FTP and TFTP, see "Configuring FTP" and "Configuring TFTP."

Upgrade task list

Tasks at a glance	Remarks
(Optional.) Preloading the BootWare image to BootWare	If a BootWare upgrade is required, you can perform this task to shorten the subsequent upgrade time. This task helps avoid upgrade problems caused by unexpected electricity failure. If you skip this task, the device upgrades the BootWare automatically when it upgrades the startup software images. The BootWare image preloaded into the BootWare take effect only after you reboot the device. You can perform this task to upgrade the BootWare image for the device or a PEX.
(Required.) Specifying startup images and completing the upgrade	Perform this task to upgrade a standalone device, an IRF fabric, or the parent fabric in an IRF 3 system. Start with the parent fabric when you upgrade the parent fabric and PEXs in an IRF 3 system.
(Optional.) Upgrading PEXs	Perform this task to upgrade the PEXs in an IRF 3 system.
(Optional.) Restoring or downgrading the BootWare image without using ISSU	N/A
(Optional.) Enabling software synchronization from the active MPU to the standby MPU at startup	By default, software synchronization is enabled. This feature enables automatic software synchronization when the device operates in standalone mode. With software synchronization, you do not need to manually upgrade the standby MPU. To synchronize software from the global active MPU to other MPUs on an IRF fabric, use the irf auto-update enable command.

Preloading the BootWare image to BootWare

BootWare is called bootrom in CLI.

To preload the BootWare image to BootWare:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. (Optional.) Enable BootWare image validity check.	bootrom-update security-check enable	By default, this feature is enabled. This feature examines the image for wrong file type, file corruption, and hardware incompatibility. H3C recommends enabling it to ensure a successful upgrade.
3. Return to user view.	quit	N/A
4. Load the upgrade BootWare image to the Normal area of BootWare.	· In standalone mode: bootrom update file file-url slot slot-number-list [ subslot subslot-number-list ] · In IRF mode: bootrom update file file-url chassis chassis-number slot slot-number-list [ subslot subslot-number-list ]	Specify the downloaded software image file for the file-url argument. The new BootWare image takes effect at a reboot. The subslot subslot-number-list option is reserved for future support. LSQ OAP modules do not support this command. To upgrade an LSQ OAP module, contact H3C Support. For information about LSQ OAP modules, see OAA Configuration Guide.

Specifying startup images and completing the upgrade

Standalone mode

Perform this task in user view.

To specify startup images and complete the upgrade in standalone mode:

Step	Command	Remarks
1. Specify main or backup startup images for the active MPU.	· Use an .ipe file for upgrade: boot-loader file ipe-filename { all \| slot slot-number } { backup \| main } · Use .bin files for upgrade: boot-loader file boot boot-package system system-package [ feature feature-package&<1-30> ] { all \| slot slot-number } { backup \| main }	N/A
2. Specify main or backup startup images for the standby MPU.	· Use an .ipe file for upgrade: boot-loader file ipe-filename { all \| slot slot-number } { backup \| main } · Use .bin files for upgrade: boot-loader file boot boot-package system system-package [ feature feature-package&<1-30> ] { all \| slot slot-number } { backup \| main } · Use the image list with which the active MPU started up: boot-loader update { all \| slot slot-number } · Use the software synchronization feature: See "Enabling software synchronization from the active MPU to the standby MPU at startup."	If an ISSU upgrade has been performed, use the install commit command to update the main startup images on the active MPU before you execute the boot-loader update command. This operation ensures startup image consistency between the active MPU and the standby MPU. The boot-loader update command uses the main or backup startup image list for synchronization, instead of the current software images list. · The main images list is used if the active MPU started up with the main startup images. · The backup image list is used if the active MPU started up with the main startup images. Startup image synchronization fails if any software images being synchronized are corrupted or not available.
3. (Optional.) Verify the software image settings.	display boot-loader [ slot slot-number ]	N/A
4. Save the running configuration.	save	This step ensures that any configuration you have made can survive a reboot.
5. Reboot the device.	reboot	At startup, the MPUs read the preloaded BootWare image to RAM, and load the startup images.

IRF mode

Perform this task in user view.

To specify startup images and complete the upgrade in IRF mode:

Step	Command	Remarks
1. Specify main or backup startup images for the global active MPU.	· Use an .ipe file for upgrade: boot-loader file ipe-filename { all \| chassis chassis-number slot slot-number } { backup \| main } · Use .bin files for upgrade: boot-loader file boot boot-package system system-package [ feature feature-package&<1-30> ] { all \| chassis chassis-number slot slot-number } { backup \| main }	N/A
2. Specify main startup images for each standby MPU in the IRF fabric.	· Use an .ipe file for upgrade: boot-loader file ipe-filename { all \| chassis chassis-number slot slot-number } { backup \| main } · Use .bin files for upgrade: boot-loader file boot boot-package system system-package [ feature feature-package&<1-30> ] { all \| chassis chassis-number slot slot-number } { backup \| main } · Use the image list with which the global active MPU started up: boot-loader update { all \| chassis chassis-number slot slot-number }	Skip this step if you have only one single-MPU device. If an ISSU upgrade has been performed, use the install commit command to update the main startup images on the active MPU before you execute the boot-loader update command. This operation ensures startup image consistency between the active MPU and the standby MPU. The boot-loader update command uses the main or backup startup image list for synchronization, instead of the current software images list. · The main images list is used if the global active MPU started up with the main startup images. · The backup image list is used if the global active MPU started up with the main startup images. Startup image synchronization fails if any software images being synchronized are corrupted or not available.
3. (Optional.) Verify that the startup software images are correct.	display boot-loader [ chassis chassis-number [ slot slot-number ] ]	N/A
4. Save the running configuration.	save	This step ensures that any configuration you have made can survive a reboot.
5. Reboot the IRF fabric.	reboot	At startup, the MPUs read the preloaded BootWare image to RAM, and load the startup images.

Restoring or downgrading the BootWare image without using ISSU

This feature is available only for upgrading the parent device. To restore or upgrade the BootWare image of a PEX device, you must use its BootWare menus.

To restore or downgrade the BootWare image for a card, make sure you have used the bootrom backup command to back up the image to the Backup area of BootWare.

Before performing a downgrade, also verify software compatibility.

Perform the following task in user view to restore or downgrade the BootWare image:

Step	Command	Remarks
1. Replace the BootWare image in the Normal area of BootWare.	In standalone mode: · Use the BootWare image in the Backup area of BootWare for a replacement: bootrom restore slot slot-number-list [ subslot subslot-number-list ] · Use the BootWare image in a storage medium for a replacement: bootrom update file file-url slot slot-number-list [ subslot subslot-number-list ] In IRF mode: · Use the BootWare image in the Backup area of BootWare for a replacement: bootrom restore chassis chassis-number slot slot-number-list [ subslot subslot-number-list ] · Use the BootWare image in a storage medium for a replacement: bootrom update file file-url chassis chassis-number slot slot-number-list [ subslot subslot-number-list ]	In an IRF 3 system, you can restore BootWare images for both cards and PEXs.
2. Reboot the device or the entire IRF fabric.	reboot	At startup, the system runs the new BootWare image to complete the restoration or downgrade.

Step

Command

Remarks

1. Replace the BootWare image in the Normal area of BootWare.

In standalone mode:

· Use the BootWare image in the Backup area of BootWare for a replacement:
bootrom restore slot slot-number-list [ subslot subslot-number-list ]

· Use the BootWare image in a storage medium for a replacement:
bootrom update file file-url slot slot-number-list [ subslot subslot-number-list ]

In IRF mode:

· Use the BootWare image in the Backup area of BootWare for a replacement:
bootrom restore chassis chassis-number slot slot-number-list [ subslot subslot-number-list ]

· Use the BootWare image in a storage medium for a replacement:
bootrom update file file-url chassis chassis-number slot slot-number-list [ subslot subslot-number-list ]

In an IRF 3 system, you can restore BootWare images for both cards and PEXs.

2. Reboot the device or the entire IRF fabric.

reboot

At startup, the system runs the new BootWare image to complete the restoration or downgrade.

Enabling software synchronization from the active MPU to the standby MPU at startup

This feature is available only when the device operates in standalone mode. To synchronize software from the global active MPU to other MPUs on an IRF fabric, use the irf auto-update enable command. For more information about software auto-update, see Virtual Technologies Configuration Guide.

When the standby MPU starts up, this feature examines its startup software images for version inconsistency with the current software images on the active MPU.

If the software versions are different, the standby MPU does the following:

1. Copies the current software images of the active MPU.

2. Specifies the images as startup software images.

3. Reboots with these images.

IMPORTANT:

To ensure a successful synchronization in a multiuser environment, prevent users from rebooting or swapping MPUs during the software synchronization process. You can configure the information center to output the synchronization status to configuration terminals (see Network Management and Monitoring Configuration Guide).

To enable software synchronization from the active MPU to the standby MPU at startup:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enable startup software version check for the standby MPU.	undo version check ignore	By default, startup software version check is enabled.
3. Enable software auto-update for the standby MPU.	version auto-update enable	By default, software version auto-update is enabled.

Upgrading PEXs

Preparing for the upgrade

1. Use the display version command to identify the current BootWare and Comware image versions on the PEX.

2. Use the release notes for the upgrade software version to evaluate the upgrade impact on your network and verify the following items:

¡ Software and hardware compatibility.

¡ Version and size of the upgrade software.

¡ Compatibility of the upgrade software with the current BootWare and Comware software images.

¡ Software compatibility between the PEXs and the parent devices.

3. Upgrade all parent devices before upgrading any PEXs if both parent devices and PEXs require an upgrade. For more information about upgrading parent devices, see "IRF mode."

4. Use the dir command to verify that all PEXs and MPUs have sufficient storage space for the upgrade images. If the storage space is not sufficient, delete unused files by using the delete command. For a PEX to start up from its local storage medium, you must make sure its local storage medium has sufficient space for the upgrade images. For more information, see "Managing the file system."

5. Use FTP or TFTP to transfer the upgrade image file to the root directory of the default storage medium on the global active MPU.

For more information about FTP and TFTP, see "Configuring FTP" and "Configuring TFTP."

Upgrade procedure

Perform this task in user view.

To upgrade PEXs:

Step	Command	Remarks
1. Specify main or backup startup images for the PEX to load from the local medium.	· Use an .ipe file for upgrade: boot-loader file ipe-filename chassis chassis-number slot slot-number { backup \| main } · Use .bin files for upgrade: boot-loader file boot boot-package system system-package [ feature feature-package&<1-30> ] chassis chassis-number slot slot-number { backup \| main }	This step is available only for S6300 and S5130-EI PEXs. The boot-loader file command copies the specified images from the global active MPU to the local medium of the PEX. Specify the PEX virtual chassis number for the chassis-number argument. Specify the PEX virtual slot number for the slot-number argument.
2. Specify PEX startup images for the PEX to load from the parent device.	· Use .bin files for upgrade: boot-loader pex pex-model file boot boot-package system system-package [ feature feature-package&<1-30> ] · Use an .ipe file for upgrade: boot-loader pex pex-model file ipe ipe-filename	The boot-loader pex command copies the specified PEX startup images automatically to all MPUs on the parent fabric. To prevent a PEX startup failure after an active/standby or master/subordinate switchover, H3C recommends that you execute this command each time you add a new member device or MPU to the parent fabric. · For S5120-HI PEXs, you must use this command to set their startup software images. · For S6300 and S5130-EI PEXs, you can use this command to set startup software images for backup. To guarantee that the PEX loads the correct software when a master/subordinate switchover occurs, make sure the PEX startup software images are the same across the MPUs in the IRF fabric.
3. Save the running configuration.	save	This step ensures that any configuration you have made can survive a reboot.
4. Reboot the PEX.	reboot chassis chassis-number slot slot-number	Specify the PEX virtual chassis number for the chassis-number argument. Specify the PEX virtual slot number for the slot-number argument. The PEX device reboots with the new startup images.

Displaying and maintaining software image settings

Execute display commands in any view and execute reset commands in user view.

Task	Command
Display current software images and startup software images (in standalone mode).	display boot-loader [ slot slot-number ]
Display current software images and startup software images (in IRF mode).	display boot-loader [ chassis chassis-number [ slot slot-number ] ]
Display the PEX startup software images on the parent device.	display boot-loader pex [ pex-model ]
Clear the PEX startup software image list on the parent device.	reset boot-loader pex pex-model

Non-ISSU software upgrade example (for standalone mode)

Network requirements

As shown in Figure 7, the device has two MPUs: one active MPU in slot 0 and one standby MPU in slot 1.

Use the file startup-a2105.ipe to upgrade software images for the device.

Figure 7 Network diagram

Configuration procedure

# Configure IP addresses and routes. Make sure the device and the TFTP server can reach each other. (Details not shown.)

# Complete TFTP settings on both the device and the TFTP server. (Details not shown.)

# Display information about the current software images.

<Sysname> display version

# Use TFTP to download the image file startup-a2105.ipe from the TFTP server to the root directory of the flash on the active MPU.

<Sysname> tftp 2.2.2.2 get startup-a2105.ipe

# Specify startup-a2105.ipe as the main startup image file for both MPUs.

<Sysname> boot-loader file flash:/startup-a2105.ipe slot 0 main

<Sysname> boot-loader file flash:/startup-a2105.ipe slot 1 main

# Copy the .bin image files decompressed from startup-a2105.ipe and save them to the current directory as boot_backup.bin and system_backup.bin.

<Sysname> copy boot.bin boot_backup.bin

<Sysname> copy system.bin system_backup.bin

# Specify boot_backup.bin and system_backup.bin as the backup startup image files for both MPUs.

<Sysname> boot-loader file boot flash:/boot_backup.bin system flash:/system_backup.bin slot 0 backup

<Sysname> boot-loader file boot flash:/boot_backup.bin system flash:/system_backup.bin slot 1 backup

# Verify the startup image settings.

<Sysname> display boot-loader

# Reboot the device to complete the upgrade.

<Sysname> reboot

Verifying the configuration

# Verify that the device is running the correct software.

<Sysname> display version

Non-ISSU software upgrade example (for IRF mode)

Network requirements

As shown in Figure 8, use the file startup-a2105.ipe to upgrade software images for the IRF fabric.

Each IRF member device has two MPUs: one in slot 0 and one in slot 1. The global active MPU is in slot 0 on the master device.

Figure 8 Network diagram

Configuration procedure

# Configure IP addresses and routes. Make sure the device and the TFTP server can reach each other. (Details not shown.)

# Complete TFTP settings on both the device and the TFTP server. (Details not shown.)

# Display information about the current software images.

<Sysname> display version

# Use TFTP to download the image file startup-a2105.ipe from the TFTP server to the root directory of the flash on the global active MPU.

<Sysname> tftp 2.2.2.2 get startup-a2105.ipe

# Specify startup-a2105.ipe as the main startup image file for all MPUs.

<Sysname> boot-loader file flash:/startup-a2105.ipe chassis 1 slot 0 main

<Sysname> boot-loader file flash:/startup-a2105.ipe chassis 1 slot 1 main

<Sysname> boot-loader file flash:/startup-a2105.ipe chassis 2 slot 0 main

<Sysname> boot-loader file flash:/startup-a2105.ipe chassis 2 slot 1 main

# Copy the .bin image files decompressed from startup-a2105.ipe and save them to the current directory as boot_backup.bin and system_backup.bin.

<Sysname> copy boot.bin boot_backup.bin

<Sysname> copy system.bin system_backup.bin

# Specify boot_backup.bin and system_backup.bin as the backup startup image files for all MPUs.

<Sysname> boot-loader file boot flash:/boot_backup.bin system flash:/system_backup.bin chassis 1 slot 0 backup

<Sysname> boot-loader file boot flash:/boot_backup.bin system flash:/system_backup.bin chassis 1 slot 1 backup

<Sysname> boot-loader file boot flash:/boot_backup.bin system flash:/system_backup.bin chassis 2 slot 0 backup

<Sysname> boot-loader file boot flash:/boot_backup.bin system flash:/system_backup.bin chassis 2 slot 1 backup

# Verify the startup image settings.

<Sysname> display boot-loader

# Reboot the IRF fabric to complete the upgrade.

<Sysname> reboot

Verifying the configuration

# Verify that the IRF fabric is running the correct software.

<Sysname> display version

Non-ISSU PEX upgrade example

Network requirements

As shown in Figure 9:

· Each IRF member device has two MPUs: one in slot 0 and one in slot 1. The global active MPU is in slot 0 on the master device.

· The IRF fabric has two PEXs: one S6300 switch in virtual slot 0 of virtual chassis 110 and one S5120HI switch in virtual slot 0 of virtual chassis 120. The S6300 switch has a storage medium, but the S5120HI switch does not.

Use the file startup-s6300.ipe to upgrade the S6300 switch and use the file startup-s5120hi.ipe to upgrade the S5120HI switch.

Figure 9 Network diagram

Configuration procedure

# Configure IP addresses and routes. Make sure the IRF fabric and the TFTP server can reach each other. (Details not shown.)

# Complete TFTP settings on the IRF fabric and the TFTP server. (Details not shown.)

# Display information about the current software images.

<Sysname> display version

# Use TFTP to download the image files startup-s6300.ipe and startup-s5120hi.ipe from the TFTP server to the root directory of the flash memory on the global active MPU.

<Sysname> tftp 2.2.2.2 get startup-s6300.ipe

<Sysname> tftp 2.2.2.2 get startup-s5120hi.ipe

# Specify startup-s6300.ipe as the main startup image file for the S6300 switch to load from its local medium.

<Sysname> boot-loader file flash:/startup-s6300.ipe chassis 110 slot 0 main

# Copy the .bin image files decompressed from startup-s6300.ipe and save them to the current directory as s6300-boot_backup.bin and s6300-system_backup.bin.

<Sysname> copy s6300-boot.bin s6300-boot_backup.bin

<Sysname> copy s6300-system.bin s6300-system_backup.bin

# Specify s6300-boot_backup.bin and s6300-system_backup.bin as the backup startup image files for the S6300 switch to load from its local medium.

<Sysname> boot-loader file boot flash:/s6300-boot_backup.bin system flash:/system_ s6300-backup.bin chassis 110 slot 0 backup

# Verify the startup image settings on the S6300 switch.

<Sysname> display boot-loader

# Specify startup-s6300.ipe as the PEX startup image file for the S6300 switch to load from the parent device.

<Sysname> boot-loader pex PEX-S6300 file ipe flash:/startup-s6300.ipe

# Specify startup-s5120hi.ipe as the PEX startup image file for the S5120HI switch to load from the parent device.

<Sysname> boot-loader pex PEX-S5120HI file ipe flash:/startup-s5120hi.ipe

# Verify the PEX startup image settings on the parent device for the S6300 and S5120HI switches.

<Sysname> display boot-loader pex

# Reboot the PEXs to complete the upgrade.

<Sysname> reboot chassis 110 slot 0

Verifying the configuration

# Verify that the PEXs are running the correct software.

<Sysname> display version

01-Fundamentals Configuration Guide

Startup process for S6300 and S5130-EI PEXs

Startup process for S5120-HI PEXs

Non-ISSU software upgrade example (for standalone mode)

Non-ISSU software upgrade example (for IRF mode)

Non-ISSU PEX upgrade example

Cloud & AI

InterConnect

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Resources

Partner Business Management

Company Information

News & Events

Contact Us