Using High Availability Monitors (June 2003)

Monitoring Disk Resources
HA Disk Monitor Reference
Chapter 2 31
• PVGs (physical volume groups) exist in a volume group, but not all
physical volumes are assigned to a PVG. The /var/adm/syslog/
syslog.log 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 /var/adm/syslog/syslog.log 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 is both 2-way and 3-way mirroring in the same volume
group.
— The mirrored disks contain a different number of physical disks
that equate to the same amount of disk space. For example, one
4GB drive in one PVG mirrored with 2-2G drives in the
redundant PVG.
Checks for the validity of pv_summary are logged with the name of the
local node and the identifier diskmond to both
/var/adm/syslog/syslog.log and /etc/opt/resmon/log/api.log.
Physical Volume and Physical Volume Link Status
Requests to monitor physical volumes and physical volume links give
you status of the individual physical volumes and PV links in a volume
group. In the case of most RAID arrays, this means the HA Disk Monitor
can talk to a physical link LUN (logical unit number) in the array. In the
case of stand-alone disks, it means the HA Disk Monitor can talk to the
disk itself.
The pv_pvlink status is used to calculate pv_summary. Although it is
somewhat redundant to use both, you might want to have more specific
status sent by pv_summary, and only have status sent on pv_pvlinks if a
device is DOWN.