The configuration examples were created and verified in a lab environment, and all the devices were started with the factory default configuration. When you are working on a live network, make sure you understand the potential impact of every command on your network.

The following information is provided based on the assumption that you have basic knowledge of software upgrade, FTP, and TFTP.

Upgrading software from the CLI

Example: Using the device as a TFTP client to upgrade software

Network configuration

As shown in Figure 1, use TFTP to download a software upgrade file from a TFTP server to upgrade the device.

Figure 1 Network diagram

Restrictions and guidelines

When you upgrade software, follow these restrictions and guidelines:

· Make sure the device has sufficient storage space for the upgrade file. If the device does not have sufficient storage space, delete unused files by using the delete /unreserved file-url command.

· Save the running configuration before the upgrade for the configuration to survive a reboot.

· If the device has two MPUs, you must upgrade both MPUs for the device to operate correctly.

Procedures

1. Configure the TFTP server:

# Assign the IP address 192.168.100.14/24 to the TFTP server. (Details not shown.)

# Start the TFTP server and specify a working directory. (Details not shown.)

2. Upgrade the device:

# Assign an IP address to Ten-GigabitEthernet 3/1/0. Make sure the device can reach the TFTP server.

<Device> system-view

[Device] interface Ten-GigabitEthernet3/1/0

[Device-Ten-GigabitEthernet3/1/0] ip address 192.168.100.66 255.255.255.0

[Device-Ten-GigabitEthernet3/1/0] quit

[Device] quit

# Verify that the device can ping the TFTP server.

<Device> ping 192.168.100.14

Ping 192.168.100.14 (192.168.100.14): 56 data bytes, press CTRL_C to break

56 bytes from 192.168.100.14: icmp_seq=0 ttl=64 time=10.701 ms

56 bytes from 192.168.100.14: icmp_seq=1 ttl=64 time=2.678 ms

56 bytes from 192.168.100.14: icmp_seq=2 ttl=64 time=2.282 ms

56 bytes from 192.168.100.14: icmp_seq=3 ttl=64 time=1.617 ms

56 bytes from 192.168.100.14: icmp_seq=4 ttl=64 time=1.701 ms

--- Ping statistics for 192.168.100.14 ---

5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss

round-trip min/avg/max/std-dev = 1.617/3.796/10.701/3.474 ms

# Save the running configuration.

<Device> 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 exists, overwrite? [Y/N]:y

Validating file. Please wait...

Saved the current configuration to mainboard device successfully.

# Identify MPUs on the device.

<Device> display device

…

The output shows that the device has two MPUs: one active MPU in slot 0 and one standby MPU in slot 1. You must upgrade both MPUs.

# Use TFTP to download the upgrade file from the TFTP server to the root directory of the storage medium on the active MPU.

<Device> tftp 192.168.100.14 get new.ipe

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

Dload Upload Total Spent Left Speed

100 70.7M 100 70.7M 0 0 1193k 0 0:00:50 0:00:50 --:--:-- 1127k

# Specify the upgrade file as the main startup image file for both MPUs.

<Device> boot-loader file boot cfa0:/new.ipe slot 0 main

Verifying the IPE file and the images............Done.

Images in IPE:

BOOT-test.bin

SYSTEM-test.bin

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

Add images to target slot.

File cfa0:/BOOT-test.bin already exists on slot 0.

File cfa0:/SYSTEM-test.bin exists on slot 0.

Overwrite the existing files? [Y/N]:Y

Decompressing file boot.bin to cfa0:/BOOT-test.bin........................Done.

Decompressing file system.bin to cfa0:/SYSTEM-test.bin........................Done.

The images that have passed all examinations will be used as the main startup software images at the next reboot on slot 0.

<Device> boot-loader file boot cfa0:/BOOT-test.bin system cfa0:/SYSTEM-test.bin slot 1 main

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

Copying file cfa0:/BOOT-test.bin to slot1#cfa0:/BOOT-test.bin...........................

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

Copying file cfa0:/SYSTEM-test.bin to slot1#cfa0:/SYSTEM-test.bin.....................

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

The images that have passed all examinations will be used as the main startup so

ftware images at the next reboot on slot 1.

# Specify the current startup image file as the backup startup image file for both MPUs. This setting ensures that the device can start up if the upgrade file is corrupt or not correct.

<Device> boot-loader file boot cfa0:/BOOT-old.bin system cfa0:/SYSTEM-old.bin slot 0 backup

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

Verifying the file cfa0:/BOOT-old.bin on slot 0............Done.

Verifying the file cfa0:/SYSTEM-old.bin on slot 0.....................................

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

The images that have passed all examinations will be used as the backup startup software images at the next reboot on slot 0.

<Device> boot-loader file boot cfa0:/BOOT-old.bin system cfa0:/SYSTEM-old.bin slot 1 backup

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

Copying file cfa0:/BOOT-old.bin to slot1#cfa0:/BOOT-old.bin............................

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

Copying file cfa0:/SYSTEM-old.bin to slot1#cfa0:/SYSTEM-old.bin.........................

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

The images that have passed all examinations will be used as the backup startup software images at the next reboot on slot 1.

# Reboot the device.

<Device> reboot

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

.......DONE!

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

Verifying the configuration

1. Verify that the software has been upgraded.

<Device> display version

¡ SR8800-X:

H3C Comware Software, Version 7.1.075, Release R8380

H3C SR8804-X uptime is 0 weeks, 0 days, 2 hours, 56 minutes

Last reboot reason : Cold reboot

Boot image: cfa0:/BOOT-test.bin

Boot image version: 7.1.075, Release R8380

Compiled Jul 22 2019 18:38:45

System image: cfa0:/SYSTEM-test.bin

System image version: 7.1.075, Release R8380

Compiled May 08 2019 16:00:00

---- More ----

¡ SR8800-X-S:

H3C Comware Software, Version 7.1.075, Release R8385P09

H3C SR8803-X-S uptime is 0 weeks, 0 days, 2 hours, 56 minutes

Last reboot reason : Cold reboot

Boot image: cfa0:/BOOT-test.bin

Boot image version: 7.1.075, Release R8385P09

Compiled Jul 22 2019 18:38:45

System image: cfa0:/SYSTEM-test.bin

System image version: 7.1.075, Release R8385P09

Compiled May 08 2019 16:00:00

---- More ----

2. Verify that the software images on the MPUs are the same:

# Display the current software images and startup software images on the active MPU.

<Device> display boot-loader slot 0

Software images on slot 0:

Current software images:

cfa0:/BOOT-test.bin

cfa0:/SYSTEM-test.bin

Main startup software images:

cfa0:/BOOT-test.bin

cfa0:/SYSTEM-test.bin

Backup startup software images:

cfa0:/BOOT-old.bin

cfa0:/SYSTEM-old.bin

# Display the current software images and startup software images on the standby MPU.

<Device> display boot-loader slot 1

Software images on slot 1:

Current software images:

cfa0:/BOOT-test.bin

cfa0:/SYSTEM-test.bin

Main startup software images:

cfa0:/BOOT-test.bin

cfa0:/SYSTEM-test.bin

Backup startup software images:

cfa0:/BOOT-old.bin

cfa0:/SYSTEM-old.bin

Configuration files

interface Ten-GigabitEthernet3/1/0

port link-mode route

ip address 192.168.100.66 255.255.255.0

Example: Using the device as an FTP client to upgrade software

Network configuration

As shown in Figure 2, use FTP to download a software upgrade file from an FTP server to upgrade the device.

Figure 2 Network diagram

Restrictions and guidelines

When you upgrade software, follow these restrictions and guidelines:

· Make sure the device has sufficient storage space for the upgrade file. If the device does not have sufficient storage space, delete unused files by using the delete /unreserved file-url command.

· Save the running configuration before the upgrade for the configuration to survive a reboot.

· If the device has two MPUs, you must upgrade both MPUs for the device to operate correctly.

· The FTP username, password, and file name settings must be the same between the FTP server and the device.

Procedures

1. Configure the FTP server:

# Assign the IP address 192.168.100.14/24 to the FTP server. (Details not shown.)

# Start the FTP server and specify a working directory. (Details not shown.)

# Add a local user account. (Details not shown.)

# Set the username to 123456 and the password to 123456 for the user account. (Details not shown.)

2. Upgrade the device:

# Assign an IP address to Ten-GigabitEthernet 3/1/0. Make sure the device can reach the FTP server.

<Device> system-view

[Device] interface ten-gigabitethernet3/1/0

[Device-Ten-GigabitEthernet3/1/0] ip address 192.168.100.66 255.255.255.0

[Device-Ten-GigabitEthernet3/1/0] quit

[Device] quit

# Verify that the device can ping the FTP server.

<Device> ping 192.168.100.14

Ping 192.168.100.14 (192.168.100.14): 56 data bytes, press CTRL_C to break

56 bytes from 192.168.100.14: icmp_seq=0 ttl=64 time=10.701 ms

56 bytes from 192.168.100.14: icmp_seq=1 ttl=64 time=2.678 ms

56 bytes from 192.168.100.14: icmp_seq=2 ttl=64 time=2.282 ms

56 bytes from 192.168.100.14: icmp_seq=3 ttl=64 time=1.617 ms

56 bytes from 192.168.100.14: icmp_seq=4 ttl=64 time=1.701 ms

--- Ping statistics for 192.168.100.14 ---

5 packet(s) transmitted, 5 packet(s) received, 0.0% packet loss

round-trip min/avg/max/std-dev = 1.617/3.796/10.701/3.474 ms

# Save the running configuration.

<Device> 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 exists, overwrite? [Y/N]:y

Validating file. Please wait...

Saved the current configuration to mainboard device successfully.

# Use the username 123456 and the password 123456 to log in to the FTP server.

<Device> ftp 192.168.100.14

User (192.168.100.14:(none)): 123456

331 User name ok, need password

Password:

230 User logged in

Remote system type is UNIX.

Using binary mode to transfer files.

# Use FTP to download the upgrade file from the FTP server to the root directory of the storage medium on the active MPU.

ftp> get new.ipe

227 Entering passive mode (192,168,100,14,8,86)

125 Using existing data connection

226 Closing data connection; File transfer successful.

70445056 bytes received in 53.6 seconds (1.25 Mbyte/s)

ftp> quit

# Identify MPUs on the device.

<Device> display device

...

The output shows that the switch has two MPUs: one active MPU in slot 0 and one standby MPU in slot 1.