VDI-in-a-Box TCP Ports Test

This test periodically checks and reports the availability and responsiveness of configured TCP ports on the vdimanager appliance. If users complain of delays when accessing the vdimanager or denial of access to the vdimanager, you can use this test to determine the reason for the anomaly – is it because, critical TCP ports on the vdimanager are currently unavailable? or is it due to the poor responsiveness of these ports to connection requests?

Target of the test : A VDI-in-a-Box Manager

Agent deploying the test : An external agent

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

Configurable parameters for the test
Parameters Description

Test period

This indicates how often should the test be executed.


The host for which this test is to be configured.


The port at which the specified host listens to.

VDI in a Box Host

The IP address of the vdimanager that is being monitored.


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., VDI_manager:443,SSH:22). 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. For example, mysql:,egwebsite:


Here, specify the maximum duration (in seconds) for which the test will wait for a response from the server. The default Timeout period 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


Whether the TCP connection is 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

Time taken (in seconds) by the server 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.