Network Service Monitors

Before You Begin

Before configuring the DNS monitor, determine the IP address for the host that you want to monitor. For internal hosts, you can use the ipconfig command from the command line.

The ipconfig command returns information similar to the following:

Connection-specific DNS Suffix . . : uptimesoftware.com
IP Address . . . . . . . . . . . . : 10.1.1.42
Subnet Mask . . . . . . . . . . . .: 255.255.255.0
Default Gateway . . . . . . . . . .: 10.1.1.1

For external hosts, you can use the nslookup command from the command line as follows:

nslookup <host name>

The nslookup command returns information about the host, similar to the following:

Server: filter.uptimesoftware.com
Address: 10.1.1.100

Name: uptimesoftware.com
Addresses: 217.160.226.70, 10.1.1.95, 
192.168.23.1, 192.168.190.1

Configuring DNS Monitors

To configure DNS monitors do the following:

1. In the DNS monitor template, complete the monitor information fields.
   To learn about monitor information fields, see Monitor Identification.
2. Complete the following fields:
   
   • Hostname to Lookup
     The host name that the monitor will check. The host name can be a Web site address, a server name, or a cluster name.
     For example, for a Web site enter www.uptimesoftware.com in this field.
   • Port
     The number of the port on which the DNS server is listening. The default is 53 .
   • IP Address
     The IP address for which you want to check. If this address is not returned, the status of the service monitor becomes Critical.
   • Response Time
     Enter the Warning and Critical Response Time thresholds for the amount of time required to complete a service check. For more information, see Configuring Warning and Critical Thresholds.
3. Click the Save for Graphing checkbox to save the data for a metric to the DataStore, which can be used to generate a report or graph.
4. Complete the following settings:
   
   • Timing Settings (see Adding Monitor Timing Settings Information for more information)
   • Alert Settings (see Monitor Alert Settings for more information)
   • Monitoring Period settings (see Monitor Timing Settings for more information)
   • Alert Profile settings (see Alert Profiles for more information)
   • Action Profile settings (see Action Profiles for more information)
5. Click Finish.

Configuring FTP Monitors

To configure FTP monitors, do the following:

1. In the FTP monitor template, complete the monitor information fields.
   To learn how to configure monitor information fields, see Monitor Identification.
2. Complete the following fields:
   
   • Port
     The number of the port number on which the FTP server is listening. The default is 21 .
   • Server Response
     Enter the Warning and Critical time thresholds required to receive a ready response from the FTP server. A server ready response can look like the following:
     220 filter FTP server (Version wu-2.6.2(1) Mon Dec 3 15:29:55 EST 2005) ready
   • For more information, see Configuring Warning and Critical Thresholds.
   • Response Time
     Enter the Warning and Critical Response Time thresholds for the length of time that the service check takes to complete. For more information, see Configuring Warning and Critical Thresholds.
3. Click the Save for Graphing checkbox to save the data for a metric to the DataStore, which can be used to generate a report or graph.
4. Complete the following settings:
   
   • Timing Settings (see Adding Monitor Timing Settings Information for more information)
   • Alert Settings (see Monitor Alert Settings for more information)
   • Monitoring Period settings (see Monitor Timing Settings for more information)
   • Alert Profile settings (see Alert Profiles for more information)
   • Action Profile settings (see Action Profiles for more information)
5. Click Finish .

Configuring HTTP (Web Services) Monitors

To configure HTTP (Web Services) monitors, do the following:

1. In the HTTP (Web Services) monitor template, complete the monitor information fields.
2. To learn about monitor information fields, see Monitor Identification.
3. Complete the following fields:
   
   • URI
     The URI of the Web page that you want to monitor. For example, 
     /login.php .
   • Text to Look For (Optional)
     Enter the text that you want the monitor to search for in the response from the server.
     This monitor parses the text from the server and, using the threshold values you enter, determines if the entire Web page returned by the server is within acceptable parameters.
     For example, if a Web page is returned then the monitor parses the entire page for the text that you input to match against. If you want to ensure that a particular page is returned, you could enter <TITLE>Expected Page</TITLE> , where Expected Page is the title of the Web page. The monitor generates an alert if this page is not matched.
   • Authentication
     The user ID and password, in the form userid:password . For example:
     jlamport:bluefrog5
   • Virtual Host
     The unique domain name that resolves to the IP address of the domain that you want to monitor. A virtual host has its own domain name, but has the same IP address as other domain names hosted by the Web server.
   • Server Response
     Enter a string to match against the response from the server. For example, HTTP/1.1 200 OK or HTTP 404 - File not found . Then, set the Warning and Critical comparison methods. For more information, see Configuring Warning and Critical Thresholds
   • Follow Redirect Actions
     Select an action that enables you to specify whether or not you want to be redirected to another Web address:
     
     • OK
       Return an OK status for any re-direction.
     • Follow
       Follow any re-direction.
     • Warning
       Return a Warning status for any re-direction.
     • Critical
       Return a Critical status for any re-direction.
   • POST String
     The URL-encoded POST string to be sent to the server. This string simulates what a Web browser sends to a Web server CGI script or binary. You can use the POST string to, for example, simulate logging into a Web application.
     For example, if you define the POST string as userid=bob&sku=123456 , the page to request would be /cgi-bin/sku_lookup . The text “ SKU count is ” is the expected response. If the SKU lookup is not successful or if the response from the application server is not fast enough, then up.time generates an alert.
   • Set-Cookie String
     The parameters that define the cookie. The cookie string uses the following format:
     domain:name:value:path
     If configuring multiple cookies for the monitor, separate each cookie string with a semicolon:
     
     •  domain is the subdomain the cookie is available to.
     •  name is a name with which you can later reference the cookie.
     •  value is a regular string to be stored as a cookie. The string should be encoded using URL-style %xx encoding, which converts all reserved and unsafe characters - such as tildes (~) and spaces - to their ASCII equivalents.
       For example, using %xx encoding, the URL http://www.mydomain.com/~jdoe/index.html becomes http://www.mydomain.com/%7ejdoe/index.htmlpath is the location on the server in which the cookie has been made available. For example, if the path is “ / ” the cookie is available to the entire domain, as opposed to a specific subdirectory name.
       d1:n1:v1:p1;d2:n2:v2:p2
       The name and value pair is the only required attribute of the Set-Cookie String field.
   • HTTP Header Settings
     The HTTP header settings for the response.
     The HTTP header settings define the syntax and semantics of all standard HTTP/1.1 header fields. For entity header fields, both sender and recipient refer to either the client or the server, depending on who sends and who receives the entity.
   • Response Time
     Enter the Warning and Critical Response Time thresholds. For more information, see Configuring Warning and Critical Thresholds
4. Click the Save for Graphing checkbox to save the data for a metric to the DataStore, which can be used to generate a report or graph.
5. Complete the following settings:
   
   • Timing Settings (see Adding Monitor Timing Settings Information for more information)
   • Alert Settings (see Monitor Alert Settings for more information)
   • Monitoring Period settings (see Monitor Timing Settings for more information)
   • Alert Profile settings (see Alert Profiles for more information)
   • Action Profile settings (see Action Profiles for more information)
6. Click Finish.

Configuring IMAP (Email Retrieval) Monitors

To configure IMAP (Email Retrieval) monitors, do the following:

1. In the IMAP (Email Retrieval) monitor template, complete the monitor information fields.
   To learn how to configure monitor information fields, see Monitor Identification.
2. Complete the following fields:
   
   • Port
     The number of the port on which IMAP is listening.
     The default is 143 . If you are applying a monitor to a service group, ensure that all of the systems use the defined port. Otherwise, create a monitor for each IMAP instance that listens on a different port.
     For information on service groups, see Service Groups.

   • Server Response
     Select a comparison method, and then enter the Warning and Critical thresholds for the server response. For more information, see Configuring Warning and Critical Thresholds.
     The server response is the same for Windows, UNIX, and Linux. For example, an expected response is:

     +OK [CAPABILITY IMAP4REV1 LOGIN-REFERRALS STARTTLS AUTH=LOGIN] filter IMAP4rev1 2002.336 at Thu, 2 Jun 2005 10:55:02 -400 (EDT)

     If IMAP is not available, then the following is an expected response:

     BAD Null command

     
     By making string comparisons on the returned values to the monitor, you can check:

     • The version of IMAP that is running to support your network routing.
     • The system on which IMAP is or is not running.
   • Response Time
     Enter the Warning and Critical Response Time thresholds for the length of time a service check takes to complete. For more information, see Configuring Warning and Critical Thresholds.
3. Click the Save for Graphing checkbox to save the data for a metric to the DataStore, which can be used to generate a report or graph.
4. Complete the following settings:
   
   • Timing Settings (see Adding Monitor Timing Settings Information for more information)
   • Alert Settings (see Monitor Alert Settings for more information)
   • Monitoring Period settings (see Monitor Timing Settings for more information)
   • Alert Profile settings (see Alert Profiles for more information)
   • Action Profile settings (see Action Profiles for more information)
5. Click Finish.

Before You Begin

To configure the LDAP monitor, you should understand how an LDAP directory works, and know how LDAP is configured in your environment. You can use the following tools to determine the Base, Bind, and Attribute values of the LDAP directory for which you want to search:

• at the Windows command line, use ntdsutil.exe to retrieve information
• one of the many freely-available LDAP browsing and editing tools
• your own network documentation and determine whether or not the proper configurations have been maintained

Configuring LDAP Monitors

To configure LDAP monitors, do the following:

1. In the LDAP monitor template, complete the monitor information fields.
   To learn how to configure monitor information fields, see Monitor Identification.
2. Complete the following fields:
   
   • Port
     The number of the port number on which the LDAP server is listening. The default is 389 .
   • Password
     The password that is required to log in to the LDAP server.
   • Base
     The location in the LDAP directory from which you want the monitor to begin searching for information.
     
     Using this directory structure, you can check your LDAP structure for your European employees by selecting the following as your base:
     dc=ldap,dc=uptime,ou=employees,ou=Europe
   • Bind
     The Bind string, which associates user account properties and LDAP account attributes. This string gives you access to the Base location of your LDAP directory structure.
     The format of the Bind string must match the Base location of your LDAP directory structure. For example, if you are checking for information found below the European employees directory, you can 
     use the following Bind string:
     cn=ldapadmin,dc=ldap,dc=uptime,dc=com
     Depending on your network security model, you will need domain controller administration privileges to bind to the locations on which you want to match information.
   • Attribute
     The attribute or information for which you want to search in your LDAP directory.
     An LDAP entry consists of a set of attributes. Each attribute has a type - which describes the kind of information contained in the attribute - and one or more values, which contain the actual data. For example, the entry [email protected] has the Attribute value [email protected] . The Attribute type is e-mail .
   • Response Time
     Enter the Warning and Critical Response Time thresholds. For more information, see Configuring Warning and Critical Thresholds.
3. Click the Save for Graphing checkbox to save the data for a metric to the DataStore, which can be used to generate a report or graph.
4. Complete the following settings:
   
   • Timing Settings (see Adding Monitor Timing Settings Information for more information)
   • Alert Settings (see Monitor Alert Settings for more information)
   • Monitoring Period settings (see Monitor Timing Settings for more information)
   • Alert Profile settings (see Alert Profiles for more information)
   • Action Profile settings (see Action Profiles for more information)
5. Click Finish.

Configuring NFS Monitors

To configure NFS monitors, do the following:

1. In the NFS monitor template, complete the monitor information fields.
   To learn how to configure monitor information fields, see Monitor Identification.
2. Complete the following fields:
   
   • Mounts
     Select a comparison method, and then enter the Warning and Critical Mount thresholds for the number of mounts on which NFS is loaded. For more information, see Configuring Warning and Critical Thresholds.
   • Response Time
     Enter the Warning and Critical Response Time thresholds for the length of time a service check takes to complete. For more information, see Configuring Warning and Critical Thresholds.
3. Click the Save for Graphing checkbox to save the data for a metric to the DataStore, which can be used to generate a report or graph.
4. Complete the following settings:
   
   • Timing Settings (see Adding Monitor Timing Settings Information for more information)
   • Alert Settings (see Monitor Alert Settings for more information)
   • Monitoring Period settings (see Monitor Timing Settings for more information)
   • Alert Profile settings (see Alert Profiles for more information)
   • Action Profile settings (see Action Profiles for more information)
5. Click Finish.

Configuring NIS/YP Monitors

To configure NIS/YP monitors, do the following:

1. In the NIS/YP monitor template, complete the monitor information fields.
   To learn how to configure monitor information fields, see Monitor Identification.
2. Complete the following NIS/YP monitor settings:
   
   • YP/NIS Domain
     The domain of the NIS service. For example, uptimesoftware.com . NIS administration databases that contain name service information are called maps . A domain is a collection of systems that share a common set of NIS maps.
   • YP/NIS Table
     The name of the NIS/YP table that contains the values for which you want to search.

   • Key
     Enter a value you want to search for in the NIS table. For example, the key is jsmith in the following string returned from a NIS table:

     jsmith:LLZDusFe5Da3s:20080:100:Jim Smith:/export/home/jsmith:/bin/sh

   • Lookup
     The Lookup value associated with the value in the Key field. For example, the following is returned from the passwd table of a NIS database based on the key jsmith :

     jsmith:LLZDusFe5Da3s:20080:100:Jim Smith:/export/home/jsmith:/bin/sh

   • Response Time
     Enter the Warning and Critical Response Time thresholds for the length of time that a service check takes to complete. For more information, see Configuring Warning and Critical Thresholds.
3. Click the Save for Graphing checkbox to save the data for a metric to the DataStore, which can be used to generate a report or graph.
4. Complete the following settings:
   
   • Timing Settings (see Adding Monitor Timing Settings Information for more information)
   • Alert Settings (see Monitor Alert Settings for more information)
   • Monitoring Period settings (see Monitor Timing Settings for more information)
   • Alert Profile settings (see Alert Profiles for more information)
   • Action Profile settings (see Action Profiles for more information)
5. Click Finish.

Command Implementation 

Response Category

Response Codes

Configuring NNTP (Network News) Monitors

To configure NNTP (Network News) monitors, do the following:

1. In the NNTP (Network News) monitor template, complete the monitor information fields.
   To learn how to configure monitor information fields, see Monitor Identification.
2. Complete the following fields:
   
   • Port
     The number of the port on which the NNTP server is listening. The default is 119 .
   • Server Response
     The server response according to the value that you want to measure.
     For information on command implementation, see Command Implementation.
     For information on response categories, see Response Category.
     For information on general response, see Response Codes.
3. Response Time
   Enter the Warning and Critical Response Time thresholds. For more information, see Configuring Warning and Critical Thresholds.
4. Click the Save for Graphing checkbox to save the data for a metric to the DataStore, which can be used to generate a report or graph.
5. Complete the following settings:
   
   • Timing Settings (see Adding Monitor Timing Settings Information for more information)
   • Alert Settings (see Monitor Alert Settings for more information)
   • Monitoring Period settings (see Monitor Timing Settings for more information)
   • Alert Profile settings (see Alert Profiles for more information)
   • Action Profile settings (see Action Profiles for more information)
6. Click Finish.

Configuring Ping Monitors

To configure Ping monitors, do the following:

1. In the Ping monitor template, complete the monitor information fields.
   To learn about monitor information fields, see Monitor Identification.
2. Complete the following fields:
   
   • Number to send
     The number of packets to send to an IP address or domain name.
     This value determines the number of times the ping command attempts to contact a server.
   • Average Round Trip Time
     Enter the Warning and Critical thresholds for the average round trip time for the number of packets sent by the ping command. The round trip time is in milliseconds.
     This value is a good indicator of ping performance because a variety of factors - including different packet paths to and from the server - can affect the round trip time of a packet.
   • Percent Loss
     Enter the Warning and Critical thresholds for the number of packets that did not returned a reply. For example, if four packets were sent and only two are returned, the percent loss is 50%.
   • Response Time
     Enter the Warning and Critical Response thresholds for the length of time the service check takes to complete. For more information, see Configuring Warning and Critical Thresholds.
3. Click the Save for Graphing checkbox to save the data for a metric to the DataStore, which can be used to generate a report or graph.
4. Complete the following settings:
   
   • Timing Settings (see Adding Monitor Timing Settings Information for more information)
   • Alert Settings (see Monitor Alert Settings for more information)
   • Monitoring Period settings (see Monitor Timing Settings for more information)
   • Alert Profile settings (see Alert Profiles for more information)
   • Action Profile settings (see Action Profiles for more information)
5. Click Finish.

Configuring POP (Email Retrieval) Monitors

To configure POP (Email Retrieval) monitors, do the following:

1. In the POP (Email Retrieval) monitor template, complete the monitor information fields.
   To learn about monitor information fields, see Monitor Identification.
2. Complete the following fields:

• Expected Server Response
  Enter the response from the server, as a string, that determines whether or not a connection is made to the POP service. Then, set the Warning and Critical thresholds. For more information, see Configuring Warning and Critical Thresholds.
  The expected server response is the same for Windows, Solaris, and Linux. For example, if the POP service is available then the following is an expected response:

  +OK POP3 <server name> v2002.81 server ready

  
  If the POP service is not available, the following is an expected response:

  -ERR Null command

• Response Time
  Enter the Warning and Critical Response Time thresholds. For more information, see Configuring Warning and Critical Thresholds.
3. Click the Save for Graphing checkbox to save the data for a metric to the DataStore, which can be used to generate a report or graph.
4. Complete the following settings:
   
   • Timing Settings (see Adding Monitor Timing Settings Information for more information)
   • Alert Settings (see Monitor Alert Settings for more information)
   • Monitoring Period settings (see Monitor Timing Settings for more information)
   • Alert Profile settings (see Alert Profiles for more information)
   • Action Profile settings (see Action Profiles for more information)
5. Click Finish.

Configuring SSH (Secure Shell) Monitors

To configure SSH (Secure Shell) monitors, do the following:

1. In the SSH (Secure Shell) monitor template, complete the monitor information fields.
   To learn how to configure monitor information fields, see Monitor Identification.
2. Complete Secure Shell monitor settings by entering the appropriate Warning and Critical thresholds.
   For more information, see Configuring Warning and Critical Thresholds.
   
   • Port
     The number of the port on which SSH is listening. The default is 22 .

   • Major
     The major version number of SSH. This is the number immediately to the left of the decimal in the version number. In the following example, the major version number is 2:

     SSH_2.0_SUN_SSH1.0

   • Minor
     The minor version number of SSH. This is the number immediately to the right of the decimal in the version number. In the following example the major version number is 0:

     SSH_2.0_SUN_SSH1.0

   • SSH Server Version
     The version of the SSH server that you want to monitor. This is the string immediately following the major and minor version numbers of SSH. In the following example the SSH server version is

     SUN_SSH1.0 :
     SSH_2.0_SUN_SSH1.0

   •  Response Time
     Enter the Warning and Critical Response Time thresholds for the overall time required to perform a service check. For more information, Configuring Warning and Critical Thresholds.
3. Click the Save for Graphing checkbox to save the data for a metric to the DataStore, which can be used to generate a report or graph.
4. Complete the following settings:
   
   • Timing Settings (see Adding Monitor Timing Settings Information for more information)
   • Alert Settings (see Monitor Alert Settings for more information)
   • Monitoring Period settings (see Monitor Timing Settings for more information)
   • Alert Profile settings (see Alert Profiles for more information)
   • Action Profile settings (see Action Profiles for more information)
5. Click Finish.

Configuring SMTP (Email Delivery) Monitors

To configure SMTP (Email Delivery) Monitors, do the following:

1. In the SMTP (Mail Delivery) monitor template, complete the monitor information fields.
   To learn how to configure monitor information fields, see Monitor Identification.
2. Complete the following fields:
   
   • Port
     The number of the port on which the SMTP server is listening. The default is 25 .

   • Expected Server Response
     Enter the Warning and Critical thresholds for the amount of time that is required to send and receive a ready response from the SMTP server.
     For example, the following response reveals the ready status of the SMTP server:

     For more information, see Configuring Warning and Critical Thresholds.

     220 mail.yourdomain.com ESMTP
     Sendmail 8.12.10+SUN/8.12.8; 
     Tue, 14 Dec 2005 13:25:15: -0400 <EDT>

   • Response Time
     Enter the Warning and Critical Response Time thresholds. For more information, see Configuring Warning and Critical Thresholds.
3. Click the Save for Graphing checkbox to save the data for a metric to the DataStore, which can be used to generate a report or graph.
4. Complete the following settings:
   
   • Timing Settings (see Adding Monitor Timing Settings Information for more information)
   • Alert Settings (see Monitor Alert Settings for more information)
   • Monitoring Period settings (see Monitor Timing Settings for more information)
   • Alert Profile settings (see Alert Profiles for more information)
   • Action Profile settings (see Action Profiles for more information)
5. Click Finish.

SNMP OID Data Types and Formats

The SNMP service monitor will work with the OID data types listed below. When configuring an SNMP Poller, you will be able to specify whether the service monitor will process different data value formats (e.g., an SnmpInt object’s returned value can be processed by the service monitor as a string or an integer). The following table also outlines correct data type and value format combinations.

Adding MIBs to up.time

up.time ships with a large set of MIBs that are available when configuring an SNMP Poller. The resulting OIDs are viewed in the MIB Browser, which is displayed when creating or editing an SNMP Poller service monitor.

If desired, you can add new MIBs to augment or replace OIDs in the default list. These MIBs should be copied to the <uptime>/mib directory. If you are considering adding your own MIBs to this directory, consider the following:

• when adding MIBs, ensure you are observing their dependencies
• after adding MIBs, restart the up.time Data Collector service (see Stopping and Restarting up.time Services); upon restarting, up.time will move the newly added MIBs to the DataStore for use by the MIB Browser
• added MIBs are processed alphabetically, so an identically named OID from a later MIB will take precedence; note that the default MIBs included with up.time will always be parsed before other MIBs

Note that there is a core set of MIBs that up.time ’s SNMP functionality requires. The nodes belonging to these MIBs will always take precedence over any others added to up.time :

• SNMPv2-SMI
• SNMPv2-TC
• SNMPv2-CONF
• SNMPv2-MIB
• RFC1213-MIB
• IF-MIB
• HOST-RESOURCES-MIB

Understanding Port Status Checks

The port status check triggers an alert when a port’s ifOperStatus state changes from an “ up ” to a “ down ” state from one check to the next. Note that the following port states are ignored:

• dormant
• lowerLayerDown
• notPresent
• unknown
• testing

The status check makes use of data retrieved by the assigned network device’s Platform Performance Gatherer service; it does not rely on an external service check, such as a ping monitor. As such, when configuring the port monitor, ensure its Performance Time Interval and Check Interval settings are complementary (e.g., the status check should occur less frequently than how often performance data is gathered).

If a status-checking port monitor is running for the first time, since there is no last known status for comparison, the monitor will treat the port’s status as “up”, and re-check at configured intervals for the next 60 minutes. After this period, the port monitor’s status will be reset to OK . This behavior exists to prevent false positives where an administrator has removed network cables during maintenance, but has not set the network device’s ifAdminStatus to “ down ” or “ testing ”.

This first-run behavior is also applicable to other scenarios:

• the network device to which the port monitor is attached has its state changed to MAINT , then back to OK
• the Core service is restarted, regardless of the network device’s status

Network Device Port Performance Metrics

The following metrics can be used to configure alert thresholds for a port monitor:

Configuring a Port Monitor

To configure a Port Monitor for a network device Element, do the following:

1. In the Port Monitor template, complete the monitor information fields.
   This includes selecting the network device Element or Element group to which this service monitor will be assigned. For more information on configuring monitor information fields, see Monitor Identification.
2. For the Performance Time Interval , enter a positive integer indicating the number of minutes' worth of performance data to average and compare against threshold definitions.
3. Select the ports on the network device Element(s) whose performance and status you want to monitor:
   
   • All Detected Ports
     up.time will monitor any port it detects on the assigned network device Element, or Element group
   • All Ports of Type
     Allows you to focus on a specific type of port for monitoring. The list is based on the ifType OID, whose values are IANA-assigned interface types.
   • Specific Ports
     Select a network device Element to Show ports from , then from the list select which ports that will be monitored.
4. In the Port Performance Check section’s Value field, select the port metric that will be used to define the alerting threshold.
5. Enter the thresholds that will trigger a warning- and critical-level alert.
6. In the Port Status Checking section, confirm whether this port monitor will also perform a Status Check .
7. In the Response Time section, enter Warning and Critical response time thresholds.
   For more information, see Configuring Warning and Critical Thresholds.
8. Click the Save for Graphing checkbox to save the data for a metric to the DataStore, which can be used to generate a report or graph.
9. Complete the following settings:
   
   • Timing Settings (see Adding Monitor Timing Settings Information for more information)
   • Alert Settings (see Monitor Alert Settings for more information)
   • Monitoring Period settings (see Monitor Timing Settings for more information)
   • Alert Profile settings (see Alert Profiles for more information)
   • Action Profile settings (see Action Profiles for more information)
10. Click Finish.

Configuring TCP Monitors

To configure TCP monitors, do the following:

1. In the TCP monitor template, complete the monitor information fields.
   To learn how to configure monitor information fields, see Monitor Identification.
2. Complete the following fields:
   

   • Port
     The number of the port on which the service or application that you want to monitor is listening.

     Note - To check whether or not an application is listening on a port, leave the remaining TCP service monitor settings blank.
   • String to Send
     The string that contains the command to which the service or application can respond.
   • Use SSL
     Select this option if your connection uses SSL (Secure Sockets Layer) for security.
   • String to Receive
     The string that is returned by the specified port and host. The string is the response to the command that was specified in the String to Send field.
   • Response Time
     Enter the Warning and Critical Response Time thresholds. For more information, see Configuring Warning and Critical Thresholds.
3. Click the Save for Graphing checkbox to save the data for a metric to the DataStore, which can be used to generate a report or graph.
4. Complete the following settings:
   
   • Timing Settings (see Adding Monitor Timing Settings Information for more information)
   • Alert Settings (see Monitor Alert Settings for more information)
   • Monitoring Period settings (see Monitor Timing Settings for more information)
   • Alert Profile settings (see Alert Profiles for more information)
   • Action Profile settings (see Action Profiles for more information)
5. Click Finish.