- Table of Contents
-
- H3C S5500-SI Series Ethernet Switches Operation Manual-Release 1205-(V1.03)
- 00-1Cover
- 00-2Overview
- 01-Login Operation
- 02-Basic System Configuration and Maintenance Operation
- 03-File System Management Operation
- 04-VLAN Operation
- 05-QinQ-BPDU TUNNEL Operation
- 06-Port Correlation Configuration Operation
- 07-MAC Address Table Management Operation
- 08-MSTP Operation
- 09-IP Address and Performance Operation
- 10-IPv6 Configuration Operation
- 11-Routing Overview Operation
- 12-IPV4 Routing Operation
- 13-IPv6 Routing Operation
- 14-802.1x-HABP-MAC Authentication Operation
- 15-AAA-RADIUS-HWTACACS Operation
- 16-Multicast Protocol Operation
- 17-ARP Operation
- 18-DHCP Operation
- 19-ACL Operation
- 20-QoS Operation
- 21-Port Mirroring Operation
- 22-Cluster Operation
- 23-SNMP-RMON Operation
- 24-NTP Operation
- 25-DNS Operation
- 26-Information Center Operation
- 27-NQA Operation
- 28-SSH Terminal Service Operation
- 29-UDP Helper Operation
- 30-SSL-HTTPS Operation
- 31-PKI Operation
- 32-PoE-PoE Profile Operation
- 33-Appendix
- Related Documents
-
Title | Size | Download |
---|---|---|
03-File System Management Operation | 405 KB |
Chapter 1 File System Configuration
1.1.4 Storage Device Operations
1.1.5 File System Prompt Mode Setting
1.1.6 File System Operations Example
1.2 Configuration File Management
1.2.2 Saving Current Configuration
1.2.3 Erasing the Startup Configuration File
1.2.4 Specifying a Configuration File for Next Startup
1.2.5 Backup/Restore the Configuration File for Next Startup
1.3 Displaying and Maintaining Device Configuration
2.2 Configuring the FTP Client
2.2.1 Establishing an FTP Connection
2.2.2 Configuring the FTP Client
2.2.3 FTP Client Configuration Example
2.3 Configuring the FTP Server
2.3.1 Configuring FTP server operating parameters
2.3.2 Configuring Parameters for FTP Users
2.3.3 FTP Server Configuration Example
2.4 Displaying and maintaining FTP
3.2 Configuring the TFTP Client
3.3 TFTP Client Configuration Example
Chapter 1 File System Configuration
& Note:
Throughout this document, a filename can be entered as either of the following:
l A fully qualified filename with the path included to indicate a file under a specific path. The filename can be 1 to 135 characters in length.
l A short filename with the path excluded to indicate a file in the current path. The filename can be 1 to 91 characters in length.
When configuring the file system, go to these sections for information you are interested in:
l File System Management
l Configuration File Management
1.1 File System Management
This section covers these topics:
l Overview
l Directory Operations
l File Operations
l Storage Device Operations
l File System Prompt Mode Setting
l File System Operations Example
1.1.1 Overview
A major function of the file system is to manage storage devices. It allows you to perform operations such as directory create and delete, and file copy and display. If an operation, delete or overwrite for example, may cause problems such as data loss or corruption, the file system will ask you to confirm the operation by default.
Depending on the managed object, file system operations fall into directory operations, file operations, storage device operations, and file system prompt mode setting.
1.1.2 Directory Operations
Directory operations include create, delete, display the current directory, display files or subdirectories in a specific directory as shown in the following table:
To do… |
Use the command… |
Remarks |
Create a directory |
mkdir directory |
Optional Available in user view |
Remove a directory |
rmdir directory |
Optional Available in user view |
Display the current directory |
pwd |
Optional Available in user view |
Display files or directories |
dir [ /all ] [ file-url ] |
Optional Available in user view |
Change the current path |
cd directory |
Optional Available in user view |
1.1.3 File Operations
File operations include delete (removing files into the recycle bin), restore the deleted, permanently delete (deleting files from the recycle bin), display, rename, copy, and move as shown in the following table:
To do… |
Use the command… |
Remarks |
Remove a file to the recycle bin or delete it permanently |
delete [ /unreserved ] file-url |
Optional Available in user view |
Restore a file from the recycle bin |
undelete file-url |
Optional Available in user view |
Empty the recycle bin |
reset recycle-bin [ file-url ] [ /force ] |
Optional Available in user view |
Display the contents of a file |
more file-url |
Optional Available in user view Currently, the file is displayed only in the format of text. |
Rename a file |
rename fileurl-source fileurl-dest |
Optional Available in user view |
Copy a file |
copy fileurl-source fileurl-dest |
Optional Available in user view |
Move a file |
move fileurl-source fileurl-dest |
Optional Available in user view |
Display files or directories |
dir [ /all ] [ file-url ] |
Optional Available in user view |
Enter system view |
system-view |
–– |
Execute the batch file |
execute filename |
Optional Available in system view |
Caution:
l Empty the recycle bin timely with the reset recycle-bin command to save memory space.
l As the delete /unreserved file-url command deletes a file permanently and the action cannot be undone, use it with caution.
l The execute command cannot ensure the execution of each command. For example, if a certain command is not correctly configured, the system will omit this command and go to the next one. Therefore, each configuration command in a batch file must be a standard configuration command, meaning the valid configuration information which can be displayed with the display current-configuration command after this command is configured successfully; otherwise, this command may not be executed correctly.
1.1.4 Storage Device Operations
Storage device operations include disk fix and format as shown in the following table:
To do… |
Use the command… |
Remarks |
Restore the space of a storage device |
fixdisk device |
Optional Available in user view |
Format a storage device |
format device |
Optional Available in user view |
You may use the two commands when some space of a storage device becomes inaccessible due to abnormal operations for example.
Caution:
When you format a storage device, all the files stored on it are erased and cannot be restored. In particular, if you format the Flash, the bootup and configuration file will be missing.
1.1.5 File System Prompt Mode Setting
The file system provides the following two prompt modes:
l Alert, where the system warns you about operations that may bring undesirable consequence such as file corruption or data loss.
l Quiet: where the system does not do that in any cases. To prevent undesirable consequence resulted from misoperations, the alert mode is preferred.
To do… |
Use the command… |
Remarks |
Enter system view |
system-view |
–– |
Set the operation prompt mode of the file system |
file prompt { alert | quiet } |
Optional The default is alert. |
1.1.6 File System Operations Example
# Display the files under the root directory.
<Sysname> dir
Directory of flash:/
0 drw- - Feb 16 2006 11:45:36 logfile
1 -rw- 1218 Feb 16 2006 11:46:19 config.cfg
2 drw- - Feb 16 2006 15:20:27 test
3 -rw- 184108 Feb 16 2006 15:30:20 aaa.bin
15240 KB total (2521 KB free)
# Create a new folder called mytest under the test directory.
<Sysname> cd test
<Sysname> mkdir mytest
%Created dir flash:/test/mytest.
# Display the files under the test directory.
<Sysname> dir
Directory of flash:/test/
0 drw- - Feb 16 2006 15:28:14 mytest
15240 KB total (2519 KB free)
# Return to the upper directory.
<Sysname> cd ..
1.2 Configuration File Management
This section covers these topics:
l Overview
l Saving Running Configuration
l Erasing the Startup Configuration File
l Specifying a Configuration File for Next Startup
l Naming Configuration Files and Selecting One for Startup
l Displaying and Maintaining Device Configuration
1.2.1 Overview
I. Types of configuration
The configuration of a device falls into two types:
l Saved configuration, a configuration file used for initialization. If this file does not exist, the default parameters are used.
l Current configuration, which refers to the user’s configuration during the operation of a device. This configuration is stored in the flash. It is removed when rebooting.
II. Format of configuration file
Configuration files are saved as text files for ease of reading. They:
l Save configuration in the form of commands.
l Save only non-default configuration settings.
l List commands in sections by view in this view order: system, interface, routing protocol, and so on. Sections are separated with one or multiple blank lines or comment lines that start with a pound sign (#).
l End with a return.
The operating interface provided by the configuration file management function is user-friendly. With it, you can easily manage your configuration files.
III. Main/backup attribute of the configuration file
A main configuration file and a backup configuration file can exist simultaneously if the device supports main/backup configuration file attribute. As such, when the main configuration file is missing or damaged, the backup file can be used instead. This increases the safety and reliability of the file system compared with the device that only support one configuration file. You can configure a file to have both main and backup attribute, but only one file of either main or backup attribute is allowed on a device.
The following three situations are concerned with the main/backup attributes:
l When saving the current configuration, you can specify the file to be a main or backup or normal configuration file.
l When removing a configuration file from a device, you can specify to remove the main or backup configuration file. Or, if it is a file having both main and backup attribute, you can specify to erase the main or backup attribute of the file.
l When setting the configuration file for next startup, you can specify the main/backup attribute of the file.
IV. Startup with the configuration file
The following steps are taken during startup:
1) If the main configuration file exists, the device initializes with this configuration.
2) If the main configuration file does not exist but the backup configuration file exists, the device initializes with the backup configuration.
3) If neither the main nor the backup configuration file exist, the device will:
l Initialize with the default configuration file if it exist;
l Or initialize with empty configuration if the default configuration file does not exist.
1.2.2 Saving Current Configuration
You can modify the configuration on your device at the command line interface (CLI). To use the modified configuration for your subsequent startups, you must save it (using the save command) as a configuration file.
I. Two modes in saving the configuration
l Fast saving mode. This is the mode when you use the save command without the safely keyword. The mode saves the file quicker but is likely to lose the configuration file if the device reboots or the power fails during the process.
l Safe mode. This is the mode when you use the save command with the safely keyword. The mode saves the file slower but can retain the configuration file in the flash even if the device reboots or the power fails during the process.
II. Three attributes of the configuration file
l Main attribute. When you use the save [ [ safely ] [ main ] ] command to save the current configuration, the configuration file you get has main attribute. If this configuration file already exists and has backup attribute, the file will have both main and backup attributes after execution of this command. If the filename you entered is different from that existing in the system, this command will erase its main attribute to allow only one main attribute configuration file in the device.
l Backup attribute. When you use the save [ safely ] backup command to save the current configuration, the configuration file you get has backup attribute. If this configuration file already exists and has main attribute, the file will have both main and backup attributes after execution of this command. If the filename you entered is different from that existing in the system, this command will erase its backup attribute to allow only one backup attribute configuration file in the device.
l Normal attribute. When you use the save file-name command to save the current configuration, the configuration file you get has normal attribute if it is not an existing file. Otherwise, the attribute is dependent on the original attribute of the file.
Follow the step below to save current configuration:
To do… |
Use the command… |
Remarks |
Save current configuration |
save [ file-name | [ safely ] [ main | backup ] ] |
Required Available in any view |
& Note:
l Fast saving is suitable for environments where power supply is stable. The safe mode, however, is preferred where stable power supplies are unavailable or remote maintenance is involved.
l The extension of the configuration file must be .cfg.
1.2.3 Erasing the Startup Configuration File
After erasing the configuration file, your device will boot up with the default configuration next time it is powered on.
You may need to erase the configuration file for one of these reasons:
l After you upgrade software, the old configuration file does not match the new software.
l The startup configuration file is corrupted or not the one you needed.
The following two situations exist:
l While the reset saved-configuration main command erases the configuration file with main attribute, it only erases the main attribute of a configuration file having both main and backup attribute.
l While the reset saved-configuration backup command erases the configuration file with backup attribute, it only erases the backup attribute of a configuration file having both main and backup attribute.
Follow the step below to erase the configuration file:
To do… |
Use the command… |
Remarks |
Erase the startup configuration file from the storage device |
reset saved-configuration [ main | backup ] |
Required Available in user view |
Caution:
This command will permanently delete the configuration file from the device.
1.2.4 Specifying a Configuration File for Next Startup
You can assign main or backup attribute to the startup configuration file.
I. Assign main attribute to the startup configuration file
l If you save the current configuration to the main configuration file, the system will automatically set the file as the main startup configuration file.
l You can also use the startup saved-configuration cfgfile main command to set the file as main startup configuration file.
II. Assign backup attribute to the startup configuration file
l If you save the current configuration to the backup configuration file, the system will automatically set the file as the backup startup configuration file.
l You can also use the startup saved-configuration cfgfile backup command to set the file as backup startup configuration file.
Follow the step below to specify a configuration file for next startup:
To do… |
Use the command… |
Remarks |
Specify a configuration file for next startup |
startup saved-configuration cfgfile [ main| backup ] |
Required Available in user view |
& Note:
The configuration file must have an extension of .cfg and must be saved at the root directory of the device.
1.2.5 Backup/Restore the Configuration File for Next Startup
I. Backup/restore function overview
The backup/restore function allows you to backup or restore a configuration file for next startup through operations at the CLI. TFTP is used for intercommunication between the device and the server. The backup function enables you to backup the main startup configuration file to the TFTP server, while the restore function enables you to download the main startup configuration file from the TFTP server for startup.
& Note:
The effect of the backup/restore operation applies to the main startup configuration file.
II. Backup the configuration file for next startup
To do… |
Use the command… |
Remarks |
Backup the configuration file for next startup |
backup startup-configuration to dest-addr [ dest-filename ] |
Required Available in user view |
& Note:
Before backup, you should:
l Ensure that the route between the device and the server is reachable; the server is enabled with TFTP service, the client has permission to read and write.
l Use the display startup command (in user view) to verify if you have set the startup configuration file, and use the dir command to verify if this file exist. If the file is set as NULL or does not exist, the backup will be unsuccessful.
III. Restore the startup configuration file
To do… |
Use the command… |
Remarks |
Restore the startup configuration file |
restore startup-configuration from src-addr src-filename |
Required Available in user view |
& Note:
l Before restoring, you should ensure that the route between the device and the server is reachable; the server is enabled with TFTP service, the client has permission to read and write.
l After the command is successful executed, you can use the display startup command (in user view) to verify if the filename of the startup configuration file is the same with the filename argument, and use the dir command to verify if the restored file exist.
1.3 Displaying and Maintaining Device Configuration
To do… |
Use the command… |
Remarks |
Display the configuration file saved in the storage device |
display saved-configuration [ by-linenum ] |
Available in any view |
Display the configuration file used for this and next startup |
display startup |
|
Display the validated configuration in current view |
display this [ by-linenum ] |
|
Display current configuration |
display current-configuration [ configuration [ configuration-type ] | interface [ interface-type ] [ interface-number ] ] [ by-linenum ] [ | { begin | include | exclude } text ] |
& Note:
l Configuration files are displayed in the same format in which they are saved.
l For detailed description of the display this and display current-configuration command, refer to Basic System Configuration and Maintenance Command Module.
Chapter 2 FTP Configuration
When configuring FTP, go to these sections you are interested in:
l Overview
l Configuring the FTP Client
l Configuring the FTP Server
l Displaying and maintaining FTP
2.1 Overview
The file transfer protocol (FTP) is an application layer protocol for sharing files between hosts over a TCP/IP network.
FTP adopts the server/client model. Your device can function either as client or as server (as shown in Figure 2-1). They work in the following way:
l When the device serves as the FTP client, a PC user first telnets or through an emulation program connects to the device, then s/he executes the ftp commands to establish the connection to the remote FTP server, and gain access to the files on the server.
l When the device serves as the FTP server, it must be configured with an IP address so that a user running FTP client program can access it.
Figure 2-1 Network diagram for FTP
2.2 Configuring the FTP Client
2.2.1 Establishing an FTP Connection
To access an FTP server, the FTP client must connect with it. Two ways are available for the connection: using the ftp command to establish the connection directly; using the open command in FTP client view.
Multiple reachable routes may exist to accessing the FTP server. You can specify one by configuring the source address of the packets of the FTP client to meet the requirement of the security policy of the FTP client. You can configure the source address by ftp -a command. The source address specified with the ftp command is valid only for the current FTP connection.
Follow these steps to establish an FTP connection (In IPv4 networking)
To do... |
Use the command |
Remarks |
Log onto the remote FTP server directly in user view |
ftp [ ftp-server [ port ] [ -a source-ip ] ] |
Use either command. |
Log onto the remote FTP server indirectly in FTP client view |
ftp |
|
open ftp-server [ port ] [ -a source-ip ] |
Follow these steps to establish an FTP connection (In IPv6 networking):
To do... |
Use the command |
Remarks |
Log onto the remote FTP server directly in user view |
ftp ipv6 [ ftp-ipv6-server [ port ] [ -a source-ipv6 ] [ -i interface-type interface-number ] ] |
Use either command |
Log onto the remote FTP server indirectly in FTP client view |
ftp ipv6 |
|
open ipv6 ftp-ipv6-server [ port ] [ -a source-ipv6 ] [ -i interface-type interface-number ] |
2.2.2 Configuring the FTP Client
Follow these steps to configure FTP client:
To do… |
Use the command… |
Remarks |
Display help information of FTP-related commands supported by the remote FTP server |
remotehelp [ protocol-command ] |
Optional |
Enable information display in a detailed manner |
verbose |
Optional Enabled by default |
Log into the FTP server again using another username |
user username [ password ] |
Optional |
Set the file transfer mode to ASCII |
ascii |
Optional ASCII by default |
Set the file transfer mode to binary |
binary |
Optional ASCII by default |
Change the working path on the remote FTP server |
cd pathname |
Optional |
Exit the current directory and enter the upper level directory |
cdup |
Optional |
Display files/directories information on the FTP server |
dir [remotefile [ localfile ] ] |
Optional |
Check files/directories on the FTP server |
ls [ remotefile [ localfile ] ] |
Optional |
Download a file from the FTP server |
get remotefile [ localfile ] |
Optional |
Upload a file to the FTP server |
put localfile [ remotefile ] |
Optional |
View the working directory of the remote FTP server |
pwd |
Optional |
Find the working path of the FTP client |
lcd |
Optional |
Create a directory on the FTP server |
mkdir directory |
Optional |
Set the data transfer mode to passive |
passive |
Optional Passive by default |
Delete specified file on the FTP server |
delete remotefile |
Optional |
Delete specified directory on the FTP server |
rmdir directory |
Optional |
Disconnect with the FTP server without exiting the FTP client view |
disconnect |
Optional Equal to the close command |
Disconnect with the FTP server without exiting the FTP client view |
close |
Optional Equal to the disconnect command |
Disconnect with the FTP server and exit to user view |
bye |
Optional |
Terminate the connection with the remote FTP server, and exit to user view |
quit |
Optional Available in FTP client view, equal to the bye command |
& Note:
l FTP uses two modes for file transfer: ASCII mode and binary mode.
l The Is command can only display the file/directory name, while the dir command can display more information, such as the size and date of creation of files or directories.
2.2.3 FTP Client Configuration Example
I. Network requirements
Use your device as an FTP client to download an image file for upgrading purpose from the FTP server with the IP address 10.1.1.1/16.
On the FTP server, an FTP user account has been created for the FTP client, with the username being abc and the password being pwd.
II. Network diagram
Figure 2-2 Network diagram for FTPing an image file from an FTP Server
III. Configuration procedure
# Check files on your device. Remove those redundant to ensure adequate space for the image 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
15240 KB total (2511 KB free)
<Sysname> delete /unreserved flash:/backup.cfg
# Download the image 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 WFTPD 2.0FTP service (by Texas Imperial Software) ready for new user .
User(10.1.1.1:(none)):abc
331 Give me your password, please
Password:
230 Logged in successfully
331 Password required for abc.
Password:
230 User logged in.
[ftp] binary
200 Type set to I.
[ftp] get aaa.appbin bbb.appbin
227 Entering Passive Mode (10.,1.,1.,1,4,17).
125 BINARY mode data connection already open, transfer starting for aaa.app.bin.
.....226 Transfer complete.
FTP: 5805100 byte(s) received in 19.898 second(s) 291.74 byte(s)/sec.
[ftp] bye
221 Server closing.
# Specify the main image file for next startup with the boot-loader command
<Sysname> boot-loader file bbb.bin main
<Sysname> reboot
The image file updates to the device at the reboot.
Caution:
Image files for next startup must be saved under the root directory. For the details of this command, refer to Basic System Configuration and Maintenance Command Module .
2.3 Configuring the FTP Server
2.3.1 Configuring FTP server operating parameters
Follow these steps to configure the FTP server:
To do… |
Use the command… |
Remarks |
Enter system view |
system-view |
–– |
Enable the FTP server |
ftp server enable |
Required Disabled by default. |
Configure the idle-timeout timer |
ftp timeout minutes |
Optional The default is 30 minutes. |
Set the file update mode in FTP |
ftp update { fast | normal } |
Optional Normal update is used by default. |
Caution:
Make sure that the FTP server and the FTP client are reachable to each other. The routing configuration is beyond the scope of this section.
2.3.2 Configuring Parameters for FTP Users
To allow an FTP user to access certain directories on the FTP server, you need to create an account for the user, authorizing access to the directories and associating the username and password with the account.
Follow these steps to make configuration for an FTP user:
To do… |
Use the command… |
Remarks |
Enter system view |
system-view |
–– |
Enter or create a local user view |
local-user user-name |
Required No local user exists by default, and the system does not support FTP anonymous user access. |
Assign a password to the user |
password { simple | cipher } password |
Required |
Assign the FTP service to the user and specify the FTP user’s access to a directory |
service-type ftp [ ftp-directory directory] |
Optional Not assigned by default; if no directory is assigned, users can access the root directory of the device after gain FTP access. |
& Note:
AAA-related parameters need to be configured on the FTP server if the FTP server adopts the authentication, authorization and accounting (AAA) security policy for FTP clients. For description on the local-user, password, and service-type commands and AAA-related configurations, refer to the AAA-RADIUS-HWTACACS module.
2.3.3 FTP Server Configuration Example
I. Network requirements
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 is the FTP client.
II. Network diagram
Figure 2-3 Smooth upgrading using the FTP server
III. Configuration procedure
1) Configure the device ( FTP server )
# Create a local user account on the device, and set the username to abc and the password to pwd.
<Sysname> system-view
[Sysname] local-user abc
[Sysname-luser-abc] password simple pwd
# Specify FTP as the serive type available for user abc, and configure the directory authorized for user abc to access.
[Sysname-luser-abc] service-type ftp ftp-directory flash:/
[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 image 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
15240 KB total (2511 KB free)
<Sysname> delete /unreserved flash:/back.cfg
2) Configure the PC ( FTP client )
# Upload the image file to the FTP server.
c:\> ftp 1.1.1.1
ftp> put aaa.bin bbb.bin
& Note:
l When upgrading the configuration file with FTP, put the new file on under the root directory.
l After you finish upgrading the Boot ROM program through FTP, you must perform the bootrom upgrade command to refresh the system configuration.
# Specify the main image file for next startup with the boot-loader command
<Sysname> boot-loader file bbb.bin main
<Sysname> reboot
The image file updates to the device at the reboot.
Caution:
Image files for next startup must be saved under the root directory. For the details of this command, refer to Basic System Configuration and Maintenance Command Module
2.4 Displaying and maintaining FTP
To do… |
Use the command… |
Remarks |
Display the configuration of the FTP server |
display ftp-server |
Available in any view |
Display information about logged-in FTP users |
display ftp-user |
Chapter 3 TFTP Configuration
When configuring TFTP, go to these sections you are interested in:
l Overview
l Configuring the TFTP Client
l Displaying and Maintaining the TFTP Client
l TFTP Client Configuration Example
3.1 Overview
The trivial file transfer protocol (TFTP) provides functions similar to those provided by FTP, but it is not as complex as FTP in interactive access interface and authentication. Therefore, it is more suitable where complex interaction is not needed between client and server.
TFTP uses the UDP service for data delivery. In TFTP, file transfer is initiated by the client.
In a normal file downloading process, the client sends a read request to the TFTP server, receives data from the server, and then sends the acknowledgement to the server.
In a normal file uploading process, the client sends a write request to the TFTP server, sends data to the server, and receives the acknowledgement from the server.
TFTP transfers files in two modes: binary for programming files and ASCII for text files.
& Note:
Only the TFTP client service is available with your switch at present.
3.2 Configuring the TFTP Client
When a device acts as a TFTP client, you can upload files on the device to a TFTP server and download files from the TFTP server to the local device. You can use either of the following ways to download files:
l Normal download: The device writes the obtained files to the storage device directly. In this way, the original system file will be overwritten and if file download fails (for example, due to network disconnection), the device cannot start up normally because the original system file has been deleted.
l Secure download: The device saves the obtained files to its memory and does not write them to the storage device until all user files are obtained. In this way, if file download fails (for example, due to network disconnection), the device can still start up because the original system file is not overwritten. This mode is more secure but consumes more memory.
You are recommended to use the latter mode or use a filename not existing in the current directory as the target filename when downloading startup file or configuration file.
Multiple reachable routes may exist to accessing the TFTP server. You can specify one by configuring the source address of the packets of the TFTP client to meet the requirement of the security policy of the TFTP client. You can configure the source address by the tftp command. The source address specified with the tftp command is valid only for the current TFTP connection.
Follow these steps to configure the TFTP client:
To do… |
Use the command… |
Remarks |
Enter system view |
system-view |
–– |
Associate the configured access control list (ACL) to the TFTP application |
tftp-server [ ipv6 ] acl acl-number |
Optional |
Return to user view |
quit |
— |
Download a file in IPv4 network |
tftp tftp-server get source-file [ dest-file | -a source-ip ]* |
Optional |
Secure download a file in IPv4 network |
tftp tftp-server sget source-file [ dest-file | -a source-ip ]* |
Optional |
Upload a file in IPv4 network |
tftp tftp-server put source-file [ dest-file | -a source-ip ]* |
Optional |
Download or upload a file in IPv6 network |
tftp ipv6 tftp-ipv6-server [ -i interface-type interface-number ] { get | put } source-file [ destination-file ] |
Optional |
3.3 TFTP Client Configuration Example
I. Network requirements
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, making that the port connected to PC belongs to the same VLAN.
l TFTP an image file from PC for upgrading and a configuration file to PC for backup.
II. Network diagram
Figure 3-1 Smooth upgrading using the TFTP client function
III. Configuration procedure
1) Configure the PC (TFTP server). The detailed configuration procedure is omitted.
l Enable the TFTP server function on the PC
l Configure the working directory of the TFTP server
2) Configure the device (TFTP client)
Caution:
If the free memory space of the device is not big enough, you should delete the existing programs before download new ones.
# Enter system view.
<Sysname> system-view
# Assign VLAN interface 1 an IP address 1.1.1.1/16, making sure that the port connected to PC belongs to the same VLAN.
[Sysname] interface vlan-interface 1
[Sysname-Vlan-interface1] ip address 1.1.1.1 255.255.0.0
[Sysname-Vlan-interface1] return
# Download an application image file aaa.bin from the TFTP server. (Before that, make sure that adequate memory is available.)
<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.cfg configback.cfg
# Specify the main image file for next startup with the boot-loader command.
<Sysname> boot-loader file bbb.bin main
<Sysname> reboot
Caution:
Image files for next startup must be saved under the root directory. For the details of this command, refer to Basic System Configuration and Maintenance Command Module.