Disk Monitor Reference | HP HA s Software manual

Monitoring Disk Resources

Disk Monitor Reference

The pv_summary resource may not be available for a given volume group in the following cases:

•Devices are on an unsupported bus (such as HP-IB or HP-FL) or an unrecognized bus, in the case of a new bus technology. The /etc/syslog entry would say:

diskmond[5699]: pv_summary will be unavailable for /dev/vg00 because there are physical volumes in this volume group which are on an unrecognized bus. (DRM-502)

•PVGs (physical volume groups) exist in a volume group, but not all physical volumes are assigned to a PVG. The /etc/syslog entry would say:

diskmond[18323]: pv_summary will be unavailable for /dev/vgtest because the physical volume groups (PVGs) in this volume group do not have an equal number of PVs or there are PVs not in a PVG. (DRM-503)

•Unequal numbers of physical volumes exist in each PVG in the volume group. The /etc/syslog entry would say:

diskmond[18323]: pv_summary will be unavailable for /dev/vgtest because the physical volume groups (PVGs) in this volume group do not have an equal number of PVs or there are PVs not in a PVG. (DRM-503)

Two cases where this would occur are:.

•There are both 2-way and 3-way mirroring in the same volume group.

•Mirrored disks are a different number of physical disks with the same total disk mi4Gb drive in one PVG and 2 2G drives in the redundant PVG.

All checks for the validity of pv_summary are logged to both /etc/syslog and /etc/opt/resmon/log/api.log with the name of the local node and the identiﬁer diskmond.

Chapter 2

35

Image 35

HP HA s Software manual Disk Monitor Reference

Contents

B5735-90001 August Using EMS HA Monitors Legal Notices Contents Monitoring Network Interfaces Monitoring Cluster Resources Glossary 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 Monitors Chapter Role of EMS HA Monitors in a High Availability Environment Installing EMS HA Monitors Installing and Removing EMS HA Monitors Removing EMS HA Monitors Pvpvlink Using EMS HA MonitorsEvent Monitoring Service Resource Class Hierarchy Status AvailMB Event Monitoring Service Screen Screen Selecting a Resource to Monitor Using Wildcards Monitoring Request Parameters Creating a Monitoring Request How 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 Dependencies Package 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 Reference Interpreting Physical Volume Summary Physical Volume Summary Disk Monitor Reference Interpreting Physical Volume and Physical Volume Link Status Physical Volume and Physical Volume Link Status Interpreting Logical Volume Summary Logical Volume Summary Logical volume is DOWN, a complete copy of the data is not Logical Volume StatusInterpreting Logical Volume Status Logical volume is inactive Interpreting Logical Volume Copies Logical Volume Number of Copies Rules 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 Arrays Adding 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 Arrays Pvgup Return Mirrored Disks Example Resources to Monitor for Mirrored Disks Monitoring Parameters Resource Notify Condition Option Resource Monitoring Parameters Notify Condition Option Resources to Monitor for Lock DisksExample for Interpreting the pvsummary for Mirrored Disks Number Pvsummary Valid Meaning Value Devices Resources to Monitor for Root Volumes Monitoring Cluster Resources Cluster Cluster Monitor ReferenceCluster Monitor Resource Class Hierarchy Interpreting Custer Status Cluster Status Interpreting Node Status Node Status Interpreting Package Status Package Status Creating Cluster Monitoring Requests Monitoring Network Interfaces Interpreting LAN Interface Status Network Monitor ReferenceNetwork Monitor Resource Class Hierarchy Chapter Hour Net/interfaces/lan/status/LANname When value isConﬁguring Network Monitoring Requests 30 sec Monitoring System Resources System Resource Monitor Class Hierarchy System Monitor Reference Resource 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 tracing EMS Tracing Performance Considerations System Performance IssuesNetwork Performance Issues Testing Network Monitor Requests Testing Monitor RequestsTesting Disk Monitor Requests Testing Cluster Monitor Requests Making Sure Monitors are Running Glossary Notiﬁcation See alert Glossary Glossary Index Index Index