H3C Technologies H3C S12500 Series Switches - Manual (Page 95)

83
TFTP client configuration example (standalone
mode)
Network requirements
As shown in Figure 32 , Device and PC are reachable to each other.
Use the PC as the TFTP server and Device as the TFTP client. Download a system software image file from
the PC to the Device for upgrade and upload a configuration file named config.cfg to the PC for backup
Figure 32 Network diagram
Configuration procedure
1. Configure the PC (TFTP server):
a. Enable the TFTP server. (Details not shown.)
b. Configure a TFTP working directory. (Details not shown.)
2. Configure the Device (TFTP client):
# Examine the storage medium of the device for insufficiency or impairment. If no sufficient free
space is available, use the fixdisk command to fix the storage medium or use the
delete/unreserved file-url command to delete unused files. (Details not shown.)
# Download application file newest.bin from the PC to the device:
{
Download application file newest.bin from the PC to the root directory of the storage medium
on the active MPU.
tftp 1.2.1.1 get newest.bin
{
Download application file newest.bin from PC to the root directory of the storage medium on
the standby MPU (in slot 1).
tftp 1.2.1.1 get newest.bin slot1#flash:/newest.bin
# Upload configuration file config.cfg to the TFTP server.
tftp 1.2.1.1 put config.cfg configback.cfg
# Specify newest.bin as the main system software image file for the next startup:
{
For the active MPU.
boot-loader file newest.bin 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 slot
0!
{
For the standby MPU (in slot 1).
boot-loader file slot1#flash:/newest.bin 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 slot
1!