TCP Port Status Test

This test indicates the health of TCP connections to the ESX server by periodically verifying the availability and responsiveness of configured ESX server ports.

Target of the test : An ESX server host

Agent deploying the test : An internal/remote agent

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

Configurable parameters for the test:
Parameter	Description
Test Period	How often should the test be executed
Host	The host for which the test is to be configured
Port	The port at which the specified HOST listens. By default, this is NULL.
Target Ports	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. For example, mysql:192.168.0.102:1433,egwebsite:209.15.165.127:80
Timeout	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.

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
Availability:	Whether the TCP connection is available	Percent	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.	Secs	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.