MONITORING

Creating a TCP server event generator
Create a TCP server event generator to verify the availability of the services on Internet ports on one or more servers. A TCP server event generator uses the ISpy task to send a probe to test whether the server is responding on a port. The probe generates a statistic that indicates the amount of time, in milliseconds, it takes to verify that the server is responding on the specified port. If the probe fails, the statistic has the value -1. The format of a server probe statistic is:
If the Collector task is running, the Monitoring Results database (STATREP.NSF) stores the Internet port statistics.

By default, the ISpy task monitors all enabled Internet ports (TCP services) on the server on which it is running. When you create a TCP server event generator, you can have each server probe its own configured ports and all services that are running on those ports, or you can select which servers and services to probe. To verify the statistic name and the type of event generated upon failure, click the tab for each service.

To create a TCP server event generator

1. Make sure that the ISpy task is running on the server.

2. From the IBM® Lotus® Domino™ Administrator, click the Configuration tab, and then open the Monitoring Configuration view.

3. Open the Event Generators - TCP Server view, and click New TCP Server Event Generator.

4. On the Basics tab for the field "All Domino servers in the domain will probe themselves," do one:

5. Under Target Servers, choose one: 6. Under Probing servers (source), select the server from which the probes will be sent.

7. Click the Probe tab, and complete these fields:
FieldAction
Probe intervalEnter the number of minutes between probes. Default is 15.
Service time-out thresholdEnter the number of seconds the probing server (source) waits for a response before logging a failure. Default is 30.
8. If all servers are probing themselves, continue with Step 8. If you chose to specify services, choose one.

9. If all servers are probing themselves or if you selected the HTTP service to probe, click the HTTP tab and choose one 10. If all servers are probing themselves or if you selected the NNTP service to probe, click the NNTP tab and choose one: 11. Click the Other tab, complete these fields, and then click Save & Close:
FieldAction
On time-out, generate an event severitySelect the severity level.
Create a new notification profile for this eventClick this button to launch the Event Notification Wizard and create an event handler.

See also