Using EMS HA Monitors

Chapter 2 53
Monitoring Disk Resources
Creating Disk Monitoring Requests
Resources to Monitor for Mirrored Disks
This section is valid for mirrored disks created with MirrorDisk/UX. Mirroring is
required to be PVG-strict if you are using the disk monitor. Mirrored configurations
that are not PVG-strict will not give you a correct pv_summary.
To adequately monitor mirrored disks, create requests for the following resources
for all volume groups on a node:
Figure 2-5 represents two nodes with 2-way mirrored configuration with 10 disks on
2 busses. Both copies are in a single volume group. Assume you want to be notified
when any physical device fails, and when you only have one copy of data, or when
there is an MC/ServiceGuard failover. To configure this last request, you must
duplicate your MC/ServiceGuard package dependency. See Chapter 1 “Configuring
MC/ServiceGuard Package Dependencies”.
Figure 2-5 Mirrored Disks Example
/vg/vgName/pv_summary This gives you summary status of all physical volumes in a volume
group. A high availability system must be configured PVG strict. If
not, pv_summary cannot accurately determine disk availability.
vg/vgName/pv_pvlink/status/* This gives you the status of each physical disk and links.
vg/vgName/lv_summary This gives you the status of data availability for logical volumes.
vg/vgName/lv/copies/* This gives you the total number of copies of data currently available.
/dev/dsk/c0t7d0
/dev/dsk/c1t7d0
/dev/dsk/c0t8d0
/dev/dsk/c1t8d0
node1
node2
/dev/vg01
/dev/dsk/c1t11d0
/dev/dsk/c1t10d0
/dev/dsk/c1t9d0
/dev/dsk/c0t11d0
/dev/dsk/c0t10d0
/dev/dsk/c0t9d0