Lotus Domino Administrator 8.5 Help - Creating Messaging probes

MONITORING

Creating Messaging probes
Note When the Messaging -- Mail Flow Statistic Check probe is running, if the MAIL.BOX file contains an excessive number of mail messages, the performance of the mail router is impacted. A "slack percentage" is created. The slack percentage is the number of messages by which the router can fall behind in processing before a fatal event is generated.

1. From the IBM® Lotus® Domino® Administrator, click the Files tab.

2. Open the Monitoring Configuration database (EVENTS4.NSF).

3. Choose DDM Configuration.

4. Choose any DDM probe view, and then click New DDM Probe.

5. Choose Messaging.

6. Complete these fields and then click Save and Close. The actual fields and tabs that are available to be completed depends on the probe that you choose.

Field Action

Probe Subtype Choose one:

SMTP TCP Port Health
Message Retrieval TCP Port Health
Router Process State
SMTP Process State
Message Retrieval Process State
NRPC Routing Status
Transfer Queue Check
Mail Flow Statistic Check
Mail Reflector
Mail DSN

Probe Description Type a short description of the probe.

Severity Choose the severity level of the events that will be generated by the probe.
Note This field does not apply to the Mail Flow Statistic Check probe subtype.

Which server(s) should run this probe? Choose one:

All servers in the domain -- Runs the probe on all servers in the domain.
Special target servers -- Specify the type of servers to run the probe, such as POP3 servers or the administration server for the Domino Directory.
Only the following servers -- Specify the servers on which the Messaging probe will run.

Database(s) to attempt to open? Specify the names of the databases that the probe tries to open.

Timeout for open attempt Enter the amount of time, in milliseconds, that the probe has to open the selected databases. If the probe fails to open the databases in this amount of time, an event is generated.

7. Complete these fields on the Schedule tab:

Field Action

How often should this probe run? Choose one:

Run multiple times per day -- The probe runs more than once each day. Causes the "Defined schedule" field to display.
Daily -- The probe runs once each day. Use the "On which days should this probe run" field to specify the days on which the probe is run.
Weekly -- The probe runs once each week. Use the "On which day of the week should this probe run?" field to specify the day on which the probe is run.
Monthly -- The probe runs once each month. Use the "On which day of the month should this probe run" field to specify when the probe should run.

Defined schedule Specify the number of minutes or seconds between each run of the probe.

Should this probe run twenty-four hours per day, seven days per week? Choose one:

Yes -- The probe runs continuously.
No -- The probe runs according to a schedule that you specify. Complete the "On which days should this probe run" field.

On which days should this probe run? Choose the days on which to run the probe.

On which day of the week should this probe run? Choose the day of the week on which to run the probe.

On which day of the month should this probe run? Enter the day of the month on which to run the probe. For example, enter 15 to run the probe on the 15th day of the month.

During which hours of the day should this probe run? Specify the start time in the From field, and the end time in the To field.

At what time should this probe run? Choose the time that you want the probe to run.

How should missed probes be handled? Choose one:

Ignore missed probe -- The missed probe is not run or rescheduled.
Run missed probe at startup -- The next time that the server starts, the missed probe runs.
Run missed probe at next time range -- The missed probe reschedules itself once. For example, if a probe scheduled to run every Tuesday at 5:00 AM fails to run, the probe reschedules itself to run on Wednesday at 5:00 AM. After that, the probe returns to its regular schedule.

Related topics

DDM probes

Messaging probes

Glossary

Feedback on Help or Product Usability?

Help on Help

All Help Contents

Glossary

Field	Action
Probe Subtype	Choose one: SMTP TCP Port Health Message Retrieval TCP Port Health Router Process State SMTP Process State Message Retrieval Process State NRPC Routing Status Transfer Queue Check Mail Flow Statistic Check Mail Reflector Mail DSN
Probe Description	Type a short description of the probe.
Severity	Choose the severity level of the events that will be generated by the probe. Note This field does not apply to the Mail Flow Statistic Check probe subtype.
Which server(s) should run this probe?	Choose one: All servers in the domain -- Runs the probe on all servers in the domain. Special target servers -- Specify the type of servers to run the probe, such as POP3 servers or the administration server for the Domino Directory. Only the following servers -- Specify the servers on which the Messaging probe will run.
Database(s) to attempt to open?	Specify the names of the databases that the probe tries to open.
Timeout for open attempt	Enter the amount of time, in milliseconds, that the probe has to open the selected databases. If the probe fails to open the databases in this amount of time, an event is generated.

Field	Action
How often should this probe run?	Choose one: Run multiple times per day -- The probe runs more than once each day. Causes the "Defined schedule" field to display. Daily -- The probe runs once each day. Use the "On which days should this probe run" field to specify the days on which the probe is run. Weekly -- The probe runs once each week. Use the "On which day of the week should this probe run?" field to specify the day on which the probe is run. Monthly -- The probe runs once each month. Use the "On which day of the month should this probe run" field to specify when the probe should run.
Defined schedule	Specify the number of minutes or seconds between each run of the probe.
Should this probe run twenty-four hours per day, seven days per week?	Choose one: Yes -- The probe runs continuously. No -- The probe runs according to a schedule that you specify. Complete the "On which days should this probe run" field.
On which days should this probe run?	Choose the days on which to run the probe.
On which day of the week should this probe run?	Choose the day of the week on which to run the probe.
On which day of the month should this probe run?	Enter the day of the month on which to run the probe. For example, enter 15 to run the probe on the 15th day of the month.
During which hours of the day should this probe run?	Specify the start time in the From field, and the end time in the To field.
At what time should this probe run?	Choose the time that you want the probe to run.
How should missed probes be handled?	Choose one: Ignore missed probe -- The missed probe is not run or rescheduled. Run missed probe at startup -- The next time that the server starts, the missed probe runs. Run missed probe at next time range -- The missed probe reschedules itself once. For example, if a probe scheduled to run every Tuesday at 5:00 AM fails to run, the probe reschedules itself to run on Wednesday at 5:00 AM. After that, the probe returns to its regular schedule.