Reset Search



Downloading a file over TFTP is significantly slow

« Go Back


TitleDownloading a file over TFTP is significantly slow
When a switch downloads a file from a TFTP server, especially in a remote location, downloading is significantly slow. 
  • EXOS All
In EXOS, the TFTP client is using the data block size of 1,400 bytes by default. (The block-size refers to data octets and does not include TFTP header.)
With the default block-size, a TFTP server sends a 1,400 byte packet to a client and waits until it gets an acknowledgement from the client before it starts sending a next one.  
Due to the acknowledgement required for each packet from the client, the delay between the server and the client significantly contributes to the overall download speed. 

Supposing that the round trip time is 100 ms, the server can at most send ten 1,400 byte packets within a second which are 14K bytes in total, no matter how high bandwidth a link supports.
At this rate of the server sending packets to the client, it would take the client a significant time to download a file over TFTP. 

In the case a TFTP server resides in a remote location incurring a considerable network delay,
use "block option" to increase the block size to the maximum of 65,000 bytes so that more data are transferred at a time. 

# download image <tftp server ip address> <filename> block-size <24–65000 bytes>
# tftp get|put <tftp server ip address> block-size <24–65000 bytes> <local filename> <remote filename>
* block-size option is available on ExtremeXOS 15.7 or onwards. 
Additional notes



Was this article helpful?



Please tell us how we can make this article more useful.

Characters Remaining: 255