Logging and tracing, EMS Logging | HP HA s Software instruction

NOTE

Troubleshooting

Logging and tracing

Logging and tracing

Use logging for most troubleshooting activities. By default the monitors log to api.log and client.log. Logging to /var/adm/syslog/syslog.log is on by default for the disk monitor and off by default for the remaining monitors. Tracing should only be used when instructed to do so by HP support personnel.

EMS Logging

As mentioned in the previous section, log ﬁles in /etc/opt/resmon/log / contain information logged by the monitors.

Look at the client.log if you seem to be having a problem with the SAM interfaces to EMS or MC/ServiceGuard. With the default level of logging, only audit and error messages are logged. An example of an audit message is:

User event occurred at Thu	Jul 31 16:13:31 1997
Process ID: 10404 (client)	Log Level:Audit

+/vg/vg00/lv/copies/* (8 instances) If (<1), OpC (m/n), 18000s, Thu Jul 31 16:13:31 1997

The “+” means that request has been added. A “-” indicates a removal. A “-” followed by a “+” indicates a modiﬁcation. Events sent to targets are marked with “.”. Errors are marked with Log Level: Error or Warning.

Look at the api.log if you seem to be having a problem with a speciﬁc monitor. Check for warnings or errors.

Logging to /var/adm/syslog/syslog.log is enabled with the -loption by default for the disk monitor only. Although it is not recommended, you can turn off logging modify the diskmond.dict ﬁle in /etc/opt/resmon/dictionary and remove -lfrom the monitor:

MONITOR: /etc/opt/resmon/lbin/diskmond

Logging to /var/adm/syslog/syslog.log is disabled by default for the other monitors. To enable logging, modify the mibmond.dict ﬁle in /etc/opt/resmon/dictionary and add -lfrom the monitor:

MONITOR: /etc/opt/resmon/lbin/diskmond -l

Logging will occur at every polling interval. This can create a very large syslog file, so you may only want to use logging when you are troubleshooting.

76

Chapter 6

Image 76

HP HA s Software manual Logging and tracing, EMS Logging

Contents

Using EMS HA Monitors B5735-90001 August Legal Notices Contents Monitoring Cluster Resources Monitoring Network Interfaces Monitoring System Resources TroubleshootingGlossary Contents Printing Date Part Number Edition Printing HistoryB5735-90001 Page Preface PublicationsPage Installing and Using EMS Event Monitoring Services High Availability Monitors What are EMS HA Monitors? Chapter Role of EMS HA Monitors in a High Availability Environment Installing and Removing EMS HA Monitors Installing EMS HA Monitors Removing EMS HA Monitors Using EMS HA Monitors Event Monitoring Service Resource Class HierarchyStatus AvailMB Pvpvlink Event Monitoring Service Screen Selecting a Resource to Monitor Screen Using Wildcards Creating a Monitoring Request Monitoring Request Parameters How Do I Tell EMS When to Send Events? What is a Polling Interval? Which Protocols Can I Use to Send Events? What is a Notiﬁcation Comment? Modifying Monitoring Requests Copying Monitoring RequestsRemoving Monitoring Requests Conﬁguring MC/ServiceGuard Package Dependencies Service EMS Package Conﬁguration Screen Package Resource Dependencies Screen Resource Parameters Screen Using EMS HA Monitors Monitoring Disk Resources Monitoring Disk Resources Disk Monitor Reference Disk Monitor Resource Class Hierarchy Physical Volume Summary Interpreting Physical Volume Summary Disk Monitor Reference Physical Volume and Physical Volume Link Status Interpreting Physical Volume and Physical Volume Link Status Logical Volume Summary Interpreting Logical Volume Summary Logical Volume Status Interpreting Logical Volume StatusLogical volume is inactive Logical volume is DOWN, a complete copy of the data is not Logical Volume Number of Copies Interpreting Logical Volume Copies Rules for Using the EMS Disk Monitor with MC/ServiceGuard Rules for Using the EMS Disk Monitor with MC/ServiceGuard Rules for RAID Arrays Pvsummary Calculations Case Conclusion State Creating Volume Groups on Disk Arrays Using PV Links Adding PVGs to Existing Volume Groups # mkdir /dev/vgdatabase Creating Logical Volumes Rules for Mirrored Individual Disks Creating Disk Monitoring Requests Disk Monitoring Request Suggestions Parameters When Disks Fail Resources to Monitor for RAID Arrays RAID Array Example Pvgup Return Resources to Monitor for Mirrored Disks Mirrored Disks Example Monitoring Parameters Resource Notify Condition Option Resources to Monitor for Lock Disks Example for Interpreting the pvsummary for Mirrored DisksNumber Pvsummary Valid Meaning Value Devices Resource Monitoring Parameters Notify Condition Option Resources to Monitor for Root Volumes Monitoring Cluster Resources Cluster Monitor Resource Class Hierarchy Cluster Monitor ReferenceCluster Cluster Status Interpreting Custer Status Node Status Interpreting Node Status Package Status Interpreting Package Status Creating Cluster Monitoring Requests Monitoring Network Interfaces Network Monitor Resource Class Hierarchy Network Monitor ReferenceInterpreting LAN Interface Status Chapter Net/interfaces/lan/status/LANname When value is Conﬁguring Network Monitoring Requests30 sec Hour Monitoring System Resources System Monitor Reference System Resource Monitor Class Hierarchy Interpreting Number of Users Number of UsersResource Name Value Range Interpretation Interpreting Job Queues Job QueuesResource Name Value Interpretation Range Filesystem Available Space Filesystem Available SpaceResource Name Creating System Resource Monitoring Requests 6Troubleshooting EMS Directories and Files Etc/opt/resmon/log Logging and tracing EMS Logging EMS Tracing Network Performance Issues System Performance IssuesPerformance Considerations Testing Monitor Requests Testing Disk Monitor RequestsTesting Cluster Monitor Requests Testing Network Monitor Requests Making Sure Monitors are Running Glossary Notiﬁcation See alert Glossary Glossary Index Index Index