MONITORING
If an Agent function is not working, first check that the QuerySet Handler and Event Interceptor server add-in tasks are running by using the Show Tasks command on the IBM® Lotus® Domino® console. You can do this remotely if you are authorized. If neither task is running, then the SNMP Agent will report that the server is down.
Check MIB Values using the SNMP Management Station
Query the MIB remotely to determine which components are up and running. There are three components in the SNMP architecture for MIB variables:
Test the:
If this fails, you can (ICMP) ping the server to determine if TCP/IP is responding. If TCP/IP is running, check the community name used by the server’s Master SNMP Agent. If you cannot verify the community name, try the "public" community name.
Refer to your SNMP management software documentation for specific instructions.
QuerySet sends a "heartbeat" to the Domino SNMP Agent every few seconds. If the Domino SNMP Agent is not running, you will receive the following message for each failed heartbeat at the Domino server console:
Lotus Domino SNMP Agent is not available.
The message stops if you start the agent or tell the QuerySet Handler to quit running.
Caution Every 30 seconds, the Domino SNMP Agent tests whether the QuerySet Handler is responding. If this test fails you will receive a Warning trap "Domino Server pulse has failed." This is usually a temporary problem because the server is overloaded. If the condition lasts 5 cycles, however, you will get a Critical trap "Domino Server is not responding." This means that the server may have crashed or hung. In either case, while it is occurring you will not be able to query the Domino MIB. When the pulse returns, you will receive a canceling trap message that the server pulse is restored.