Manuals / HP / Computer Equipment / Software

HP HA s Software manual EMS Tracing

Models: HA s Software

1 87

Download 87 pages 29.75 Kb

Page 77

Troubleshooting

Logging and tracing

Entries in /var/adm/syslog/syslog.log are marked with the monitor daemon name, e.g. diskmond or fsmond, followed by the resource name and logging data. Additions, deletions, notiﬁcations, and changes in resource states are logged. Errors explaining why a resource is not available for monitoring, or why the monitor cannot access a resource are also logged in /var/adm/syslog/syslog.log.

Look at the registrar.log if you are having trouble ﬁnding resources that you suspect exist on your system. This log contains any errors that were encountered when trying to read the dictionary. If a dictionary was corrupted in any way, the registrar would not be able to read it, and EMS would not be able to ﬁnd the resources associated with that dictionary.

EMS Tracing

Tracing is used when debugging monitor code.

Use the -doption to turn on tracing for EMS monitors. Tracing should only be used at the request of your HP support personnel when trying to determine if there may be a problem with the EMS HA monitors. To turn on tracing, modify the .dict ﬁle in /etc/opt/resmon/dictionary and add -dto the monitor you would like to trace:

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

Kill the monitor process. The monitor will automatically restart with tracing enabled. To speed up monitor restart, use the resls command with the top level of the resource class as an argument, for example, resls /vg.

Tracing is logged to /etc/opt/resmon/log/diskmond.log for the disk monitor and /etc/opt/resmon/log/mibmond.log for all other monitors

Chapter 6

77

Image 77

HP HA s Software manual EMS Tracing

Contents

B5735-90001 August Using EMS HA MonitorsLegal Notices Contents Monitoring Network Interfaces Monitoring Cluster ResourcesGlossary TroubleshootingMonitoring System Resources Contents B5735-90001 Printing HistoryPrinting Date Part Number Edition Page Publications PrefacePage Installing and Using EMS What are EMS HA Monitors? Event Monitoring Services High Availability MonitorsChapter Role of EMS HA Monitors in a High Availability Environment Installing EMS HA Monitors Installing and Removing EMS HA MonitorsRemoving EMS HA Monitors Event Monitoring Service Resource Class Hierarchy Using EMS HA MonitorsStatus AvailMB PvpvlinkEvent Monitoring Service Screen Screen Selecting a Resource to MonitorUsing Wildcards Monitoring Request Parameters Creating a Monitoring RequestHow Do I Tell EMS When to Send Events? Which Protocols Can I Use to Send Events? What is a Polling Interval?What is a Notiﬁcation Comment? Removing Monitoring Requests Copying Monitoring RequestsModifying Monitoring Requests Service EMS Conﬁguring MC/ServiceGuard Package DependenciesPackage Conﬁguration Screen Package Resource Dependencies Screen Resource Parameters Screen Using EMS HA Monitors Monitoring Disk Resources Monitoring Disk Resources Disk Monitor Resource Class Hierarchy Disk Monitor ReferenceInterpreting Physical Volume Summary Physical Volume SummaryDisk Monitor Reference Interpreting Physical Volume and Physical Volume Link Status Physical Volume and Physical Volume Link StatusInterpreting Logical Volume Summary Logical Volume SummaryInterpreting Logical Volume Status Logical Volume StatusLogical volume is inactive Logical volume is DOWN, a complete copy of the data is notInterpreting Logical Volume Copies Logical Volume Number of CopiesRules for Using the EMS Disk Monitor with MC/ServiceGuard Rules for Using the EMS Disk Monitor with MC/ServiceGuard Pvsummary Calculations Case Conclusion State Rules for RAID ArraysAdding PVGs to Existing Volume Groups Creating Volume Groups on Disk Arrays Using PV Links# mkdir /dev/vgdatabase Creating Logical Volumes Rules for Mirrored Individual Disks Creating Disk Monitoring Requests Disk Monitoring Request Suggestions Parameters When Disks Fail RAID Array Example Resources to Monitor for RAID ArraysPvgup Return Mirrored Disks Example Resources to Monitor for Mirrored DisksMonitoring Parameters Resource Notify Condition Option Example for Interpreting the pvsummary for Mirrored Disks Resources to Monitor for Lock DisksNumber Pvsummary Valid Meaning Value Devices Resource Monitoring Parameters Notify Condition OptionResources to Monitor for Root Volumes Monitoring Cluster Resources Cluster Cluster Monitor ReferenceCluster Monitor Resource Class Hierarchy Interpreting Custer Status Cluster StatusInterpreting Node Status Node StatusInterpreting Package Status Package StatusCreating Cluster Monitoring Requests Monitoring Network Interfaces Interpreting LAN Interface Status Network Monitor ReferenceNetwork Monitor Resource Class Hierarchy Chapter Conﬁguring Network Monitoring Requests Net/interfaces/lan/status/LANname When value is30 sec HourMonitoring System Resources System Resource Monitor Class Hierarchy System Monitor ReferenceResource Name Value Range Interpretation Number of UsersInterpreting Number of Users Resource Name Value Interpretation Range Job QueuesInterpreting Job Queues Resource Name Filesystem Available SpaceFilesystem Available Space Creating System Resource Monitoring Requests 6Troubleshooting EMS Directories and Files Etc/opt/resmon/log EMS Logging Logging and tracingEMS Tracing Performance Considerations System Performance IssuesNetwork Performance Issues Testing Disk Monitor Requests Testing Monitor RequestsTesting Cluster Monitor Requests Testing Network Monitor RequestsMaking Sure Monitors are Running Glossary Notiﬁcation See alert Glossary Glossary Index Index Index