Network requirements, Hotfix configuration example – H3C Technologies H3C S7500E Series Switches User Manual
Page 161
10-17
# Download file soft-version2.app from the TFTP server to the master and slave.
...
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.
# Specify file new-config.cfg as the boot file to be used at the next boot of all member devices of the
IRF virtual device.
Please wait ...
Setting the master board ...
... Done!
Setting the slave board ...
Slot 2:
Set next configuration file successfully
# Specify file soft-version2.app as the boot file to be used at the next boot of all main boards.
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!
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!
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!
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. The software version is upgraded now.
To check if the upgrade is successful after the device reboots, use the display version command.
Hotfix Configuration Example
Network requirements
z
As shown in
, the software running on the device is of some problem and thus hotfixing
is needed.
z
The patch files patch_mpu.bin, patch_lpb.bin and patch_lpr.bin are saved on the TFTP server.
z
The IP address of the device is 1.1.1.1/24, and IP address of the TFTP Server is 2.2.2.2/24. The
device and TFTP Server can reach each other.