TCP Port Status Test
This test tracks various statistics pertaining to TCP connections to and from a host, from an external perspective. This test is disabled by default for a Generic server.
This test is disabled by default. To enable the test, go to the enable / disable tests page using the menu sequence : Agents -> Tests -> Enable/Disable, pick the desired Component type, set Performance as the Test type, choose the test from the disabled tests list, and click on the < button to move the test to the ENABLED TESTS list. Finally, click the Update button.
Target of the test : Any host system
Agent deploying the test : An external agent
Outputs of the test : One set of results for every configured port name
For some other component-types, like the Oracle database server, this test is enabled by default.
Parameter | Description |
---|---|
Test Period |
How often should the test be executed. |
Host |
The host for which the test is to be configured. |
Port |
Enter the port to which the specified host listens |
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. |
Time out |
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. |
Is Passive |
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. |
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. |