Filter
Top Products
DES-3500 Layer 2 Fast Ethernet Switch CLI Reference Manual
58
upload
Purpose Used to upload the current switch settings or the switch history log
to a TFTP.
Syntax
upload [cfg_toTFTP | log_toTFTP] <ipaddr> <path_filename
64>
Description This command is used to upload either the Switch’s current settings
or the Switch’s history log to a TFTP server.
Parameters
cfg_toTFTP − Specifies that the Switch’s current settings will be
uploaded to the TFTP server.
log_toTFTP − Specifies that the switch history log will be uploaded
to the TFTP server.
<ipaddr> − The IP address of the TFTP server. The TFTP server
must be on the same IP subnet as the Switch.
<path_filename 64> − Specifies the location of the Switch
configuration file on the TFTP server. This file will be replaced by
the uploaded file from the Switch.
Restrictions The TFTP server must be on the same IP subnet as the Switch.
Only Administrator and Operator-level users can issue this
command.
Example usage:
To upload a configuration file:
DES-3526:admin#upload cfg_toTFTP 10.48.74.121
c:\cfg\log.txt
Command: upload cfg_toTFTP 10.48.74.121 c:\cfg\log.txt
Connecting to server................... Done.
Upload configuration...................Done.
DES-3526:admin#
enable autoconfig
Purpose Used to activate the autoconfiguration function for the Switch. This will load a
previously saved configuration file for current use.
Syntax
enable autoconfig
Description When autoconfig is enabled on the Switch, the DHCP reply will contain a
configuration file and path name. It will then request the file from the TFTP server
specified in the reply. When autoconfig is enabled, the ipif settings will
automatically become DHCP client.
Parameters None.
Restrictions When autoconfig is enabled, the Switch becomes a DHCP client automatically
(same as: config ipif System dhcp). The DHCP server must have the TFTP
server IP address and configuration file name, and be configured to deliver this
information in the data field of the DHCP reply packet. The TFTP server must be
running and have the requested configuration file in its base directory when the
request is received from the Switch. Consult the DHCP server and TFTP server
software instructions for information on loading a configuration file.
If the Switch is unable to complete the autoconfiguration process the previously
saved local configuration file present in Switch memory will be loaded.