Monitoring Disk Resources
Creating Disk Monitoring Requests
Resources to Monitor for RAID Arrays
These considerations are relevant to all supported RAID configurations listed at the beginning of this chapter. To adequately monitor a RAID system, create requests to monitor at least the following resources for all volume groups on a node:
/vg/vgName/pv_summary | This gives you an overview of the status of the entire physical volume | |
|
| group and is recommended when using EMS in conjunction with |
|
| MC/ServiceGuard; see “Rules for Using the EMS Disk Monitor with |
|
| MC/ServiceGuard” on page 40. |
vg/vgName/pv_pvlink/status/* | This gives you the status of each PV link in the array and is redundant | |
|
| to pv_summary. It is recommended when using EMS outside of the |
|
| MC/ServiceGuard environment, or if you require specific status on |
|
| each physical device. |
vg/vgName/lv_summary | This gives you the status of data availability on the array. | |
| Figure | |
Figure | RAID Array Example | |
Bus A for vgdance: /dev/dsk/c1t0d0 /dev/dsk/c1t2d0
Bus A for vgdsing: /dev/dsk/c1t0d1 /dev/dsk/c1t2d1
t0
vgdance
|
|
|
|
|
|
|
| Bus B for vgdance: |
| ||
|
|
| node1 |
|
| /dev/dsk/c2t1d0 |
| ||||
|
|
|
|
|
|
|
| /dev/dsk/c2t3d0 |
| ||
|
|
|
|
|
|
|
| Bus B for vgsing: |
| ||
Bus A (c1) |
|
| Bus B (c2) |
| |||||||
|
| /dev/dsk/c2t1d1 |
| ||||||||
|
|
|
|
|
|
|
| /dev/dsk/c2t3d1 |
| ||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| t1 |
|
|
|
|
|
|
|
|
|
|
|
| t2 |
|
| t3 | |
|
|
|
|
|
|
|
|
|
|
|
|
lun 0 | lun 0 | lun 0 | lun 0 |
|
| ||
vgsing |
|
|
|
lun1 | lun1 | lun1 | lun1 |
Chapter 2 | 51 |
