Using the Event Monitoring Service (November 1999)

92 AppendixB
Troubleshooting
Testing Monitor Requests
Testing Monitor Requests
To test that events are being sent, use the INITIAL option available with
conditional notification when creating a monitoring request. This option
sends notification on startup. Examine it to make sure your request is
properly configured and showing up in the correct system management
tool.
An alternative is to use the “At each interval” notification to test that
events are being sent in the correct system management tool. Once you
establish that events are being sent properly, you can modify the request.
Testing Cluster Monitor Requests
Use the cmviewcl -v command to display detailed information about
the current status of the cluster and packages on the cluster. The EMS
cluster monitor should return the same values as this command.
Testing Network Monitor Requests
If you want totest whether events are sent in case ofnetwork failure, use
the /usr/bin/ifconfig LANname down command to bring a card down,
and examine the event to make sure it shows up in the correct system
management tool.
Testing System Resource Monitor Requests
Use the uptime command to verify the number of users and the system
load. The EMS system resource monitor should return the same values
that this command does.
Making Sure Monitors are Running
Monitor daemons automatically start when you create a monitoring
request. Because monitoring is designed to work in a high-availability
environment, monitors are written to automatically restart if anything
causes them to fail.
A daemon called p_client restarts all appropriate monitors using the
monitor restart interval defined in /etc/opt/resmon/config.
Therefore, a monitor cannot be permanently stopped or started by a