tftp

tftp [ ip-address | host-name ] { -v vr_name } { -b block_size } [ -g | -p ] [ -l local-file { -r remote-file } | -r remote-file { -l local-file } ]

Description

Allows you to TFTP from the current command line interface session to a TFTP server.

Syntax Description

ip-address Specifies the IP address of the TFTP server.
host-name Specifies the name of the remote host.
vr_name Specifies the name of the virtual router.
Note: User-created VRs are supported only on the platforms listed for this feature in the Feature License Requirements document.
block_size Specifies the data block size, excluding TFTP header. Data block size ranges from 24-65000 bytes.
-g Gets the specified file from the TFTP server and copies it to the local host.
-p Puts the specified file from the local host and copies it to the TFTP server.
local-file Specifies the name of the file (configuration file, policy file) on the local host.
remote-file Specifies the name of the file on the remote host.

Default

If you do not specify a virtual router, VR-Mgmt is used.

If you do not specify the internal memory card or a removable storage device, the switch downloads or uploads the file from the switch local file system.

If you do not specify block size, the default value is 1400 bytes.

Usage Guidelines

NetASCII and mail file type formats are not supported.

TFTP Server Requirements

Extreme Networks recommends using a TFTP server that supports blocksize negotiation (as described in RFC 2348, TFTP Blocksize Option), to enable faster file downloads and larger file downloads. If the TFTP server does not support blocksize negotiation, the file size is limited to 32MB. Older TFTP servers that do not support blocksize negotiation have additional implementation limits that may decrease the maximum file size to only 16MB, which may be too small to install ExtremeXOS images.

If your TFTP server does not support blocksize negotiation, the switch displays a message similar to the following when you attempt a get (-g) or put (-p) operation:

Note: The blocksize option is not supported by the remote TFTP server.
Without this option, the maximum file transfer size is limted to 32MB.
Some older TFTP servers may be limited to 16MB file.

Using TFTP

Use TFTP to download a previously saved configuration file or policy file from the TFTP server to the switch. When you download a file, this command does not automatically apply it to the switch. You must specify that the downloaded file be applied to the switch. For example, if you download a configuration file, issue the use configuration command to apply the saved configuration on the next reboot. You must use the reboot command to activate the new configuration. If you download a policy file, use the refresh policy command to reprocess the text file and update the policy database.

You also use TFTP to upload a saved configuration file or policy file from the switch to the TFTP server.

If your download from the TFTP server to the switch is successful, the switch displays a message similar to the following:

Downloading megtest2.cfg to switch... done!

If your upload from the switch to the TFTP server is successful, the switch displays a message similar to the following:

Uploading megtest1.cfg to TFTPhost ... done!

Up to eight active TFTP sessions can run on the switch concurrently.

You must configure DNS in order to use the host_name option.

Host Name and Remote IP Address Character Restrictions

This section provides information about the characters supported by the switch for host names and remote IP addresses.

When specifying a host name or remote IP address, the switch permits only the following characters:

  • Alphabetical letters, upper case and lower case (A-Z, a-z)
  • Numerals (0-9)
  • Period ( . )
  • Dash ( - ) Permitted only for host names
  • Underscore ( _ ) Permitted only for host names
  • Colon ( : )

When naming or configuring an IP address for your network server, remember the requirements listed above.

Local and Remote Filename Character Restrictions

This section provides information about the characters supported by the switch for local and remote filenames.

When specifying a local or remote filename, the switch permits only the following characters:

  • Alphabetical letters, upper case and lower case (A-Z, a-z)
  • Numerals (0-9)
  • Period ( . )
  • Dash ( - )
  • Underscore ( _ )
  • Slash ( / ) permitted only for remote files

When naming a local or remote file, remember the requirements listed above.

Virtual Router Requirements

The vr_name option specifies the name of the virtual router. The valid virtual router names at system boot-up are VR-Mgmt, VR-Control, and VR-Default; however, you can only TFTP on VR-Mgmt and VR-Default. In ExtremeXOS 10.1, the valid virtual routers are VR-0, VR-1, and VR-2 respectively. For more information about virtual routers, see Virtual Routers.

Internal Memory and Core Dump Files

Core dump files have a .gz file extension. The filename format is: core.process-name.pid.gz where process-name indicates the name of the process that failed and pid is the numerical identifier of that process. If you have a modular switch and save core dump files to the external memory card, the filename also includes the affected MSM/MM: MSM-A or MSM-B.

If you configure and enable the switch to send core dump (debug) information to the internal memory card, specify the internal-memory option to transfer those files from the internal memory card to a TFTP server.

If you specify the memorycard option, you can use TFTP to copy and transfer files to and from removable storage devices (compact flash cards or USB 2.0 storage devices).

If the switch has not saved any debug files, you cannot transfer other files to or from the internal memory. For example if you attempt to transfer a configuration file from the switch to the internal memory, the switch displays a message similar to the following:

Update: Error: tftp transfer to /usr/local/tmp is not allowed.

For information about configuring and sending core dump information to the internal memory card, see the configure debug core-dumps and save debug tracefiles memorycard commands.

For more detailed information about core dump files, see Troubleshooting.

Other Useful Commands

On the Summit family switches and SummitStack, use the download bootrom command to upgrade the BootROM. This command utilizes TFTP to transfer the BootROM image file from your TFTP server to the switch. Only upgrade the BootROM when asked to do so by an Extreme Networks technical representative. For more information about this command, see download bootrom .

To upgrade the image, use the download image command. This command utilizes TFTP to transfer the software image file from your TFTP server to the switch. For more information about this command, see download image .

Example

The following command downloads the configuration file named XOS1.cfg from the TFTP server with an IP address of 10.123.45.67:

tftp 10.123.45.67 -v “VR-Default” -g -r XOS1.cfg

The following command uploads the configuration file named XOS2.cfg to the TFTP server with an IP address of 10.123.45.67:

tftp 10.123.45.67 -v “VR-Default” -p -r XOS2.cfg

The following command downloads a policy file to a removable storage device:

tftp 10.1.2.3 -g -l /usr/local/tmp/test.pol -r august23.pol

History

This command was first available in ExtremeXOS 10.1.

The memorycard option was added in ExtremeXOS 11.1.

The internal-memory option was added in ExtremeXOS 11.4.

Support for USB 2.0 storage devices was added in ExtremeXOS 12.5.3.

Pathname support added in ExtremeXOS 15.5.1.

Block size support was added in ExtremeXOS 15.7.1.

Platform Availability

This command is available on all platforms.