5-18
Figure 5-8
Network diagram for software maintenance through the CLI
PC
TFTP Server
AC
TFTP Client
Console
Ethernet
Configure the IP addresses for both sides, which must be on the same subnet. For example, set the IP
address of the TFTP server to 192.168.0.1, and that of the access controller’s management interface to
192.168.0.2. Then use
ping
to verify the network connectivity.
Backing up and restoring application and configuration files
After setting up the environment, perform the following operations on the PC:
View the files in the current file system with the
dir
command.
<H3C>dir
Directory of cfa0:/
0 -rw- 10295948 Sep 11 2053 02:17:14 main.bin
1 -rw- 33 Aug 20 2008 09:58:44 system.xml
2 -rw- 802 Aug 20 2008 09:58:44 startup.cfg
3 -rw- 76960 Aug 15 2008 15:58:02 vmetest.vme
253950 KB total (243028 KB free)
File system type of cfa0: FAT32
<H3C>
For example, to back up the file
startup.cfg
on the access controller and save it as
config.bak
on the
TFTP server, use the following command:
<H3C>tftp 192.168.0.1 put startup.cfg config.bak
File will be transferred in binary mode
Sending file to remote TFTP server. Please wait... \
TFTP: 802 bytes sent in 10 second(s).
File uploaded successfully.
To download
config.cfg
from the TFTP server to the access controller, use the following command:
<H3C>tftp 192.168.0.1 get config.bak startup.cfg
File will be transferred in binary mode
Downloading file from remote TFTP server, please wait...
TFTP: 842 bytes received in 1 second(s)
File downloaded successfully.
