TFTP Performance Test

TFTP, or Trivial File Transfer Protocol, is a simple high-level protocol for transferring data servers use to boot diskless workstations, X-terminals, and routers by using User Data Protocol (UDP).

TFTP plays a crucial role in the Citrix Provisioning Services boot process, where a target device logs into a Citrix PVS server and boots into a vDisk. The typical process is as follows:

  • When a target device boots from the network, DHCP sends a request to the Provisioning Server for an IP address and Scope Option settings. The Provisioning Server returns the information as requested. Additionally, DHCP also sends the TFTP server name and boot file name - ARDBP32.BIN - to the target device.
  • Using TFTP (that listens on UDP port 69), a request for the bootstrap file (ARDBP32.BIN) is sent from the target device to the Provisioning Server. The Provisioning Server downloads the boot file on the target device.
  • The target device boots the assigned vDisk image.

If the UDP port 69 is unavailable, then the target device will not be able to connect to the TFTP server; as a result, it will be unable to boot the vDisk image. Similarly, if the target device experiences any delays when downloading the bootstrap file from the Provisioning server, it is bound to adversely impact the booting process. This is why, it is important to periodically check whether/not the TFTP port is accessible from the target device and also measure how quickly the target device is able to get/download the bootstrap file from the Provisioning server. This is where the TFTP Performance Test helps!

At configured intervals, this test emulates a target device connecting to the TFTP port and downloading the bootstrap file (ARDBP32.BIN) from the Provisioning server. In the process, the test reports the following:

  • Is the TFTP server (on UDP port 69) accessible over the network?
  • How much time does it take to download/get the bootstrap file?

This way, the test promptly alerts administrators to the unavailability and poor responsiveness of TFTP, and thus helps them troubleshoot a target device not booting into a vDisk.

Target of the test : A TFTP server

Agent deploying the test : An internal agent

Outputs of the test : One set of results for the TFTP server being monitored.

Configurable parameters for the test
Parameter Description

Test Period

How often should the test be executed


The host for which the test is to be configured


The port number at which the specified host listens


Provide the full path to each of the IN folders in a comma-separated list. in folders are folders to which a job is submitted.

Detailed Diagnosis

To make diagnosis more efficient and accurate, the eG system embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option against Detailed Diagnosis. To disable the capability, click on the Off option.

The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

  • The eG manager license should allow the detailed diagnosis capability
  • Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0. 
Measurements made by the test
Measurement Description Measurement Unit Interpretation


Indicates whether/not the TFTP server is accessible over the network


If the value of this measure is 100%, it indicates that the TFTP server is available. The value 0 on the other hand indicates that the server is unavailable. Typically, if the UDP port 69 is unavailable or not accessible over the network, then this measure will report the value 0.

Response time

Indicates the time taken to download the bootstrap file (ARDBP32.BIN) from the Provisioning server to a configured location on the external agent host.


Ideally, the value of this measure should be low. An increase in the value can occur because there are too many simultaneous requests or because of a network bottleneck.