Service Response Monitor › Test Management › Create Tests › TCP Connect Tests

TCP Connect Tests

The TCP Connect test monitors the amount of time required to connect to a port on a server through TCP. It can help you determine whether the TCP service is running and network connectivity exists.

Options and Arguments

TCP Connect tests require the following specific options and arguments:

• Destination. The hostname of the system to which you want to connect.

  Note: IPv6 addresses can be used, but they must be embedded in brackets, for example [0aff::230:6eff:fe4b:51db]:8080. Here 0aff::230:6eff:fe4b:51db represents the IPv6 address and 8080 represents the port number.

• Port. The port on which the TCP service is running.

Specify these options and arguments when you create or modify tests.

Example

Use this example to create a test that monitors the amount of time required to connect to port 2049 on the system nfsserver.yourdomain every 60 seconds. The test waits up to 5 seconds for a successful response and calculates response time and availability statistics over the last 600 seconds (10 minutes).

To create a new test in a policy

1. Click + (New) on the Test Monitors toolbar.

   The New test pane appears.

2. From the Test Type list, select TCP Connect.
3. In the Description field, specify nfsserver.yourdomain_tcp.
4. In the Test Name field, specify TCP Connection Test.
5. In the Test Interval field, specify 60.
6. In the Test Timeout field, specify 5.
7. In the Samples Per Interval field, specify 1.
8. In the Statistics Window field, specify 600.
9. In the Destination field, enter nfsserver.yourdomain.com.
10. In the Port field, specify 2049.
11. Accept defaults for all other fields.
12. Click Save Test.

When you commit your changes, SRM adds an entry similar to the following to the svcrsp.cf file:

{ 
index=90 
type=tcpconnect 
desc="nfsserver.yourdomain_tcp" 
args=" " 
dest="nfsserver.yourdomain:2049" 
interval=60 
samples=1 
timeout=5 
window=600 
tos=0 
limit=0 
status=active 
name="TCP Connection Test"
class=""
context=""
flags="1"
loglevel=1
}

For information about errors you may encounter when running TCP Connect tests, see Generic Error Codes.