3com S7906E Manuel De Montage

Page de 2621
 
2-4 
TFTP Client Configuration Example (Distributed Device) 
Network requirements 
As shown in 
, use a PC as the TFTP server and Device as the TFTP client. Their IP 
addresses are 1.2.1.1/16 and 1.1.1.1/16 respectively. An available route exists between Device 
and PC. 
Device downloads a startup file from PC for upgrading and uploads a configuration file named 
config.cfg to PC for backup. 
Figure 2-2 Smooth upgrading using the TFTP client function 
 
 
Configuration procedure 
1)  Configure PC (TFTP Server), the configuration procedure is omitted. 
On the PC, enable the TFTP server 
Configure a TFTP working directory 
2)  Configure Device (TFTP Client) 
 
 
If the available memory space of the device is not enough, use the fixdisk command to clear the 
memory or use the delete /unreserved file-url command to delete the files not in use and then perform 
the following operations. 
 
# Download application file newest.app from PC to the device. 
Download application file newest.app from PC to the root directory of the storage medium on the 
AMB. 
<Sysname> tftp 1.2.1.1 get newest.app 
Download application file newest.app from PC to the root directory of the storage medium on the 
SMB (in slot 1). 
<Sysname> tftp 1.2.1.1 get newest.app slot1#flash:/newest.app 
# Upload a configuration file config.cfg to the TFTP server. 
<Sysname> tftp 1.2.1.1 put config.cfg configback.cfg 
# Specify newest.app as the main startup file to be used at the next startup. 
Specify newest.app as the main startup file to be used at the next startup for the AMB. 
<Sysname> boot-loader file newest.app 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! 
Specify newest.app as the main startup file to be used at the next startup for the SMB (in slot 1). 
<Sysname> boot-loader file slot1#flash:/newest.app slot 1 main