DDC Controller Status Test

This test periodically verifies whether configured ports on the DDC are available or not, and if so how quickly it responds to connection requests. In addition, the test also reports whether the DDC being monitored is the ‘master’ of a farm.

Target of the test : A Citrix Delivery Controller v3/4

Agent deploying the test : An internal agent

Outputs of the test : One set of results for every targetport configured.

Configurable parameters for the test
Parameter Description

Test Period

How often should the test be executed.


The IP address of the host for which this test is to be configured.


Refers to the port at which the specified host listens to.


Specify either a comma-separated list of port numbers that are to be tested (eg., 80,7077,1521), or a comma-separated list of port name:port number pairs that are to be tested (eg., smtp:25,mssql:1433). In the latter case, the port name will be displayed in the monitor interface. Alternatively, this parameter can take a comma-separated list of port name:IP address:port number pairs that are to be tested, so as to enable the test to try and connect to Tcp ports on multiple IP addresses.


Specify the duration beyond which the test will time out, if no response is received from the DDC. The default value is 60 seconds.


If the value chosen is Yes, then the server under consideration is a passive server in a cluster. No alerts will be generated if the server is not running. Measures will be reported as "Not applicable" by the agent if the server is not up.

Measurements made by the test
Measurement Description Measurement Unit Interpretation

Is this server the farm master?

Indicates whether this DDC is the farm master.


While the value 1 indicates that this server is the farm master, the value 0 indicates that it is not.

DDC availability

Indicates whether a TCP connection to the DDC is currently available or not.


If the DDC is available, then this measure will report the value 100. The value 0 for this measure, indicates that the DDC is not available.

An availability problem can be caused by different factors – e.g., the server process may not be up, a network problem may exist, or there could be a configuration problem with the DNS server.

Response time

Indicates the time taken by the DDC to respond to a request.


An increase in response time can be caused by several factors such as a server bottleneck, a configuration problem with the DNS server, a network problem, etc.