State Probe Configuration

State probes monitor the state of a remote service by actively transmitting network packets to a specified remote host. To configure a state probe:

• Create the probe by specifying a probe name and type
• Optionally configure a description to be associated with this probe
• Optionally configure a domain, host or IPv6 address DNS query type to send with this state probe
• Optionally configure an IP address or domain name to verify the DNS query response
• Optionally modify the number of consecutive failed faildetect probes that will determine when the service is declared down
• Optionally modify the interval between faildetect probes
• Optionally modify the number of successful pass detection probes that will determine when a service marked as down will be declared up
• Optionally modify the interval between pass detection probes
• Optionally specify the ACV or DNS Layer 5 protocol to use with this state probe
• Optionally modify the length of time the Tracked Object Manager will wait for a response from the monitored service before declaring that a probe request failed
• For a TCP probe, optionally modify the open interval that sets how long the Tracked Object Manager should wait for the completion of the TCP 3-way handshake
• When configuring ACV on a TCP or UDP probe:
  • Set the request string that will initiate the ACV session on the server
  • Set the reply string that will validate the server response to the request string
  • If required by the protocol being monitored, configure a close string to close the session
• Enable the probe by placing it inservice

The three state probe protocols supported by the Tracked Object Manager are ICMP, UDP, and TCP. Probe parameters are configured in probe configuration mode. You enter probe configuration mode by creating the probe in global configuration mode, specifying the name of the probe and the probe protocol. If the specified probe already exists, Tracked Object Manager enters configuration command mode for the named probe.

The state probe protocol used determines the fail detection method(s) that are available for monitoring the remote service. The fail detection methods supported for monitoring a remote service are:

• Ping
• Port Service Verification
• Application Content Verification (ACV)

Probes that do not yet exist can be assigned to monitor a service, but fail detection will not occur until the probe is created.