- Table of Contents
-
- H3C Low-End and Mid-Range Ethernet Switches Configuration Examples(V1.01)
- 00-1Cover
- 01-Login Configuration Guide
- 02-VLAN Configuration Guide
- 03-GVRP Configuration Guide
- 04-Voice VLAN Configuration Guide
- 05-IP Addressing and Performance Configuration Guide
- 06-QinQ Configuration Guide
- 07-BPDU Tunnel Configuration Guide
- 08-VLAN Mapping Configuration Guide
- 09-MAC Address Table Management Configuration Guide
- 10-Link Aggregation Configuration Guide
- 11-IP Source Guard Configuration Guide
- 12-DLDP Configuration Guide
- 13-MSTP Configuration Guide
- 14-IPv4 Routing Configuration Guide
- 15-IPv6 Configuration Guide
- 16-IPv6 Routing Configuration Guide
- 17-IPv4 Multicast Configuration Guide
- 18-IPv6 Multicast Configuration Examples
- 19-802.1x Configuration Guide
- 20-AAA Configuration Guide
- 21-MAC Authentication Configuration Guide
- 22-Portal Configuration Guide
- 23-ARP Configuration Guide
- 24-DHCP Configuration Guide
- 25-ACL Configuration Guide
- 26-QoS Configuration Guide
- 27-Port Mirroring Configuration Guide
- 28-Cluster Management Configuration Guide
- 29-SNMP-RMON Configuration Guide
- 30-NTP Configuration Guide
- 31-FTP-TFTP Configuration Guide
- 32-UDP Helper Configuration Guide
- 33-Information Center Configuration Guide
- 34-DNS Configuration Guide
- 35-File System Management Configuration Guide
- 36-Remote Upgrade Configuration Guide
- 37-NQA Configuration Guide
- 38-VRRP Configuration Guide
- 39-SSH Configuration Guide
- 40-Port Security Configuration Guide
- 41-Port Isolation Configuration Guide
- 42-LLDP Configuration Guide
- 43-MCE Configuration Guide
- 44-PoE Configuration Guide
- 45-OAM Configuration Guide
- 46-Connectivity Fault Detection Configuration Guide
- 47-RRPP Configuration Guide
- 48-sFlow Configuration Guide
- 49-SSL-HTTPS Configuration Guide
- 50-PKI Configuration Guide
- 51-Track Configuration Guide
- 52-EPON-OLT Configuration Guide
- 53-Smart Link Configuration Guide
- 54-MPLS Configuration Guide
- Related Documents
-
Title | Size | Download |
---|---|---|
31-FTP-TFTP Configuration Guide | 108.45 KB |
Table of Contents
1 FTP-TFTP Configuration Guide
Networking and Configuration Requirements
Networking and Configuration Requirements
Networking and Configuration Requirements
All the configurations in this chapter are performed in the case that a reachable route exists between FTP/TFTP server and client. For the related configurations of IP addresses and routing protocols, refer to the related sections in this manual.
Configuring FTP Client
Network Diagram
Figure 1-1 Network diagram for configuring FTP client
Networking and Configuration Requirements
As shown in Figure 1-1:
l Use your device as an FTP client to download a startup file from the FTP server.
l The IP address of the FTP server is 10.1.1.1/16.
l On the FTP server, an FTP user has been created for the FTP client, with the username being abc and the password being pwd.
Applicable Product Matrix
Product series |
Software version |
Hardware version |
S3610 Series Ethernet Switches |
Release 5301 Release 5303 |
All versions |
S5510 Series Ethernet Switches |
Release 5301 Release 5303 |
All versions |
S5500-SI Series Ethernet Switches |
Release 1207 |
All versions except S5500-20TP-SI |
Release 1301 |
S5500-20TP-SI |
|
S5500-EI Series Ethernet Switches |
Release 2102 |
All versions |
S7500E Series Ethernet Switches |
Release 6100 Release 6300 |
All versions |
Configuration Procedure
# Check files on your device. Remove those redundant to ensure adequate space for the startup file to be downloaded.
<Sysname> dir
Directory of flash:/
0 drw- - Dec 07 2005 10:00:57 filename
1 drw- - Jan 02 2006 14:27:51 logfile
2 -rw- 1216 Jan 02 2006 14:28:59 config.cfg
3 -rw- 1216 Jan 02 2006 16:27:26 backup.cfg
31496 KB total (12133 KB free)
<Sysname> delete /unreserved flash:/backup.cfg
# Log in to the FTP server and download the startup file from the server.
<Sysname> ftp 10.1.1.1
Trying 10.1.1.1 ...
Press CTRL+K to abort
Connected to 10.1.1.1.
220 FTP service ready.
User(10.1.1.1:(none)):abc
331 Password required for abc.
Password:
230 User logged in.
[ftp] binary
200 Type set to I.
[ftp] get aaa.bin bbb.bin
227 Entering Passive Mode (10.1.1.1,4,1).
125 BINARY mode data connection already open, transfer starting for aaa.bin.
.....226 Transfer complete.
FTP: 5805100 byte(s) received in 19.898 second(s) 291.74 byte(s)/sec.
[ftp] bye
# You can use the boot-loader command to specify the downloaded file as the main startup file for next startup. Then restart the device and the startup file of the device is updated.
<Sysname> boot-loader file bbb.bin main
<Sysname> reboot
l Startup files for next startup must be saved under the root directory of the device. You can copy or move a file to change the path of it to the root directory. For the description of the corresponding command, refer to the File System Management Configuration Guide.
l About the S7500E switch,the startup file must use .bin as its extension name
l When you specify a main startup file on an S7500E switch, you need to provide the slot number in the boot-loader command. For example, boot-loader file bbb.app slot 1 main.
Complete Configuration
The commands in this configuration guide are one-time commands and will not be saved in the configuration file; therefore complete configuration is not involved.
Configuration Guidelines
Follow these guidelines when configuring FTP client:
l FTP transmits files in two modes: binary mode for program file transmission and ASCII mode for text file transmission.
l You cannot specify the main/backup startup files for the next startup on the S3610&S5510 series switches.
Configuring FTP Server
Network Diagram
Figure 1-2 Network diagram for configuring FTP server
Networking and Configuration Requirements
As shown in 0:
l Use your device as an FTP server. Create a user account for an FTP user on it, setting the username to abc and the password to pwd.
l The IP address of the Ethernet interface is 1.1.1.1/16.
l The PC serves as the FTP client.
Applicable Product Matrix
Product series |
Software version |
Hardware version |
S3610 Series Ethernet Switches |
Release 5301 Release 5303 |
All versions |
S5510 Series Ethernet Switches |
Release 5301 Release 5303 |
All versions |
S5500-SI Series Ethernet Switches |
Release 1207 |
All versions except S5500-20TP-SI |
Release 1301 |
S5500-20TP-SI |
|
S5500-EI Series Ethernet Switches |
Release 2102 |
All versions |
S7500E Series Ethernet Switches |
Release 6100 Release 6300 |
All versions |
Configuration Procedure
l Configuration on Device (FTP Server)
# Create an FTP user abc, setting its password to pwd.
<Sysname> system-view
[Sysname] local-user abc
[Sysname-luser-abc] password simple pwd
# Specify abc to use FTP, and authorize its access to a certain directory.
[Sysname-luser-abc] service-type ftp
[Sysname-luser-abc] work-directory flash:/
# Configure the user privilege level of abc as 3, making it able to upload files to the directory.
[Sysname-luser-abc] level 3
[Sysname-luser-abc] quit
# Enable FTP server.
[Sysname] ftp server enable
[Sysname] quit
# Check files on your device. Remove those redundant to ensure adequate space for the startup file to be uploaded.
<Sysname> dir
Directory of flash:/
0 drw- - Dec 07 2005 10:00:57 filename
1 drw- - Jan 02 2006 14:27:51 logfile
2 -rw- 1216 Jan 02 2006 14:28:59 config.cfg
3 -rw- 1216 Jan 02 2006 16:27:26 back.cfg
4 drw- - Jan 02 2006 15:20:21 ftp
31496 KB total (12133 KB free)
<Sysname> delete /unreserved flash:/back.cfg
l Configuration on the PC (FTP Client)
# Log in to the FTP server, upload the startup file to the FTP server and save it under the root directory of the FTP server.
c:\> ftp 1.1.1.1
Connected to 1.1.1.1.
220 FTP service ready.
User(1.1.1.1:(none)):abc
331 Password required for abc.
Password:
230 User logged in.
ftp> put aaa.bin bbb.bin
200 Port command okay.
150 Opening BINARY mode data connection for bbb.bin.
226 Transfer complete.
ftp: 2737556 byte(s) sent in 7.02 Second(s) 390.24Kbyte(s)/sec.
ftp>
# You can use the boot-loader command to specify the uploaded file as the main startup file for next startup. Then restart the device and the startup file of the device is updated.
<Sysname> boot-loader file bbb.bin
<Sysname> reboot
l The startup files for next startup specified by the boot-loader command must be saved under the root directory of the device. You can copy or move a file to change the path of it to the root directory. For description of the corresponding command, refer to the File System Management Configuration Guide.
l About the S7500E switch,the startup file must use .bin as its extension name
l When you specify a main startup file on an S7500E switch, you need to provide the slot number in the boot-loader command. For example, boot-loader file bbb.app slot 1 main.
l The operation procedure for upgrading the configuration file with FTP is the same as that for uploading files. Note that you need to put the new file under the root directory when upgrading the configuration file with FTP.
l After you finish upgrading the Boot ROM program through FTP, you need to execute the bootrom update command to refresh the system configuration.
Complete Configuration
#
ftp server enable
#
local-user abc
password simple pwd
work-directory flash:/
level 3
service-type ftp
#
Configuration Guidelines
Follow these guidelines when configuring FTP client:
When the device serves as the FTP server, if the client is to perform the write operations (upload, delete, create, and delete for example) on the device’s file system, the FTP login users must be level 3 users; if the client is to perform other operations, for example, read operation, the device has no restriction on the user level of the FTP login users, that is, any level from 0 to 3 is allowed.
Configuring TFTP Client
Network Diagram
Figure 1-3 Network diagram for configuring TFTP client
Networking and Configuration Requirements
As shown in 0:
l Use a PC as the TFTP server and your device as the TFTP client.
l PC uses IP address 1.2.1.1./16 and a TFTP working directory has been defined for the client.
l On your device, VLAN-interface 1 is assigned an IP address 1.1.1.1/16. Make sure that the port connected to PC belongs to VLAN 1.
l TFTP a startup file from PC for upgrading and a configuration file config.cfg to PC for backup.
Applicable Product Matrix
Product series |
Software version |
Hardware version |
S3610 Series Ethernet Switches |
Release 5301 Release 5303 |
All versions |
S5510 Series Ethernet Switches |
Release 5301 Release 5303 |
All versions |
S5500-SI Series Ethernet Switches |
Release 1207 |
All versions except S5500-20TP-SI |
Release 1301 |
S5500-20TP-SI |
|
S5500-EI Series Ethernet Switches |
Release 2102 |
All versions |
S7500E Series Ethernet Switches |
Release 6100 Release 6300 |
All versions |
Configuration Procedure
l Configure PC (TFTP Server). On the PC, enable TFTP server and configure a TFTP working directory. The configuration procedure is omitted.
l Configure the switch (TFTP Client)
If the free memory space of the device is not big enough, you should delete the existing programs before downloading new ones.
# Download an application file aaa.bin from the TFTP server.
<Sysname> tftp 1.2.1.1 get aaa.bin bbb.bin
# Upload a configuration file config.cfg to the TFTP server.
<Sysname> tftp 1.2.1.1 put config.bin configback.bin
# You can use the boot-loader command to specify the uploaded file as the main startup file for next startup. Then restart the device and the startup file of the device is updated.
<Sysname> boot-loader file bbb.bin main
<Sysname> reboot
l Startup files for next startup must be saved under the root directory. You can copy or move a file to change the path of it to the root directory. For description of the corresponding command, refer to the File System Management Configuration Guide.
l About the S7500E switch,the startup file must use .bin as its extension name
l When you specify a main startup file on an S7500E switch, you need to provide the number argument in the boot-loader command. For example, boot-loader file bbb.app slot 1 main.
Complete Configuration
The commands in this configuration guide are one-time commands and will not be saved in the configuration file; therefore complete configuration is not involved.
Configuration Guidelines
None