Allows you to use TFTP from the current command line interface session to copy the file from a TFTP server and copy it to a local host, including the switch, internal memory card, compact flash card, or USB 2.0 storage device.
host-name | Specifies the name of the remote host. |
ip-address | Specifies the IP address of the TFTP server. |
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 Switch Engine 32.3 Feature License Requirements document. |
block_size | Specifies the data block size, excluding TFTP header. Data block size ranges from 24-65000 bytes. |
local_file | Specifies the name of the file (configuration file, policy file) on the local host. |
force-overwrite | Specifies the switch to automatically overwrite an existing file. |
If you do not specify a virtual router, VR-Mgmt, and then VR-Default (if needed), is used. If you transfer a file with a name that already exists on the system, the switch prompts you to overwrite the existing file.
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.
NetASCII and mail file type formats are not supported.
By default, the switch prompts you to overwrite an existing file. For example, if you have a file named test.cfg on the switch and download a file named test.cfg from a TFTP server, the switch displays a message similar to the following:
test.cfg already exists, do you want to overwrite it? (y/n)
Enter y to download the file and overwrite the existing file. Enter n to cancel this action.
If you successfully download the file, the switch displays a message similar to the following:
Downloading test.cfg to switch... done!
If you cancel this action, the switch displays a message similar to the following:
Tftp download aborted.
If you specify the force-overwrite parameter, the switch automatically overwrites an existing file. For example, if you have a file named test.cfg on the switch and download a file named test.cfg from a TFTP server, the switch automatically overrides the existing file. If you successfully download the file, the switch displays a message similar to the following:
Downloading test.cfg to switch... done!
This command was introduced to simplify using TFTP to transfer configuration, policy, and if configured, core dump files from the switch to the TFTP server. You can continue to use the original tftp command introduced in ExtremeXOS 10.1.
See the tftp command.
The following command retrieves and transfers the file test.pol from a TFTP server with an IP address of 10.1.2.3 and renames the file august23.pol when transferred to a removable storage device:
tftp get 10.1.2.3 vr “VR-Mgmt” test.pol /usr/local/ext august23.pol
The following command retrieves the configuration file named meg-upload.cfg from a TFTP server with an IP address of 10.10.10.10:
tftp get 10.10.10.10 vr “VR-Mgmt” meg_upload.cfg
This command was first available in ExtremeXOS 11.4.
Support for USB 2.0 storage devices was added in ExtremeXOS 12.5.3.
Pathname support for local files was added in ExtremeXOS 15.5.1.
Block size support was added in ExtremeXOS 15.7.1.
This command is available on ExtremeSwitching 5320, 5420, 5520, and 5720 series switches.