Using High Availability Monitors (June 2003)

Troubleshooting HA Monitors
Steps to Obtain EMS Data to Reproduce an EMS Problem
Appendix B92
Steps to Obtain EMS Data to Reproduce an
EMS Problem
If you are about to reproduce an EMS problem, you should obtain a full
set of EMS data that allows to get all logfiles and configuration
information. Here is an example for a diskmond problem.
1. Enable debugging for EMS by issuing the command
# touch /etc/opt/resmon/debug
2. Enable diskmond logging and debugging.
# vi /etc/opt/resmon/dictionary/diskmond.dict
Change the following line:
MONITOR: /etc/opt/resmon/lbin/diskmond
to
MONITOR: /etc/opt/resmon/lbin/diskmond -l -d
NOTE Do not save the backup copy of the diskmond.dict file in the
/etc/opt/resmon/dictionary directory or in any subdirectory. If
you want to make a backup copy of the diskmond.dict file,saveitto
/tmp or any similiar path.
3. Create the file /etc/opt/resmon/unlimited_log. If you do not
create this file, the log files will be overwritten once they reach 500
KB in size.
# touch /etc/opt/resmon/unlimited_log
The EMS log files in /etc/opt/resmon/unlimited_log are limited
to 500 KB in size and are then moved to <logfile>.old. The
previous *.old file is lost. The limit of 500 KB per log file can be
removed by creating the file /etc/opt/resmon/unlimited_log.
WARNING Be careful while creating this file. Growing EMS log files can
easily fill up your root file system.