Adding PVGs to Existing Volume Groups | HP HA s Software specs

Monitoring Disk Resources

Rules for Using the EMS Disk Monitor with MC/ServiceGuard

links are not conﬁgured in separate PVGs, the disk monitor sees all links to the array as one physical volume, so if one link fails, pv_summary will register DOWN, and your package will fail over, even if the other link is still up and data is available.

The following sections describe how to make sure your PV links are in physical volume groups.

Adding PVGs to Existing Volume Groups

If you have already created volume groups, you can create PVGs and put PV links into them:

1. Create a ﬁle called /etc/lvmpvg with permissions 600. See the lvmpvg man

page and HP-UX System Administration Tasks

2. Create an entry for each volume group and assign a different PVG name to each PV link. The PVG names can be any arbitrary name of your choosing, but must be unique on the system For example, an array containing 2 volume groups, vgdance and vgsing, each containing a single LUN and each with 2 PV links (see Figure 2-4 on page 51) should have the following /etc/lvmpvg ﬁle:

VG /dev/vgdance PVG busA /dev/dsk/c1t0d0 /dev/dsk/c1t2d0 PVG busB /dev/dsk/c2t1d0 /dev/dsk/c2t3d0

VG /dev/vgsing PVG busA /dev/dsk/c1t0d1 /dev/dsk/c1t2d1 PVG busB

	/dev/dsk/c2t1d1
	/dev/dsk/c2t3d1
	3. Carefully copy the /etc/lvmpvg to each system connected to the disk array.

NOTE	Make sure you edit lvmpvg to contain the correct link names in
	/dev/dsk/device for that system.

Creating Volume Groups on Disk Arrays Using PV

Links

If you will be monitoring volume groups that use mass storage on disk arrays, you should use redundant I/O channels from each node, connecting them to separate controllers on the array. Then you can deﬁne alternate links to the LUNs or logical disks you have deﬁned on the array. Alternate links (known as PV links) to the same disk should be assigned to different physical volume groups. In SAM, choose the

Chapter 2

43

Image 43

HP HA s Software manual Creating Volume Groups on Disk Arrays Using PV Links, Adding PVGs to Existing Volume Groups

Contents

B5735-90001 August Using EMS HA Monitors Legal Notices Contents Monitoring Network Interfaces Monitoring Cluster Resources Monitoring System Resources TroubleshootingGlossary Contents Printing Date Part Number Edition Printing HistoryB5735-90001 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? Modifying Monitoring Requests Copying Monitoring RequestsRemoving 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 Monitor Resource Class Hierarchy Cluster Monitor ReferenceCluster Interpreting Custer Status Cluster Status Interpreting Node Status Node Status Interpreting Package Status Package Status Creating Cluster Monitoring Requests Monitoring Network Interfaces Network Monitor Resource Class Hierarchy Network Monitor ReferenceInterpreting LAN Interface Status 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 Interpreting Number of Users Number of UsersResource Name Value Range Interpretation Interpreting Job Queues Job QueuesResource Name Value Interpretation Range Filesystem Available Space Filesystem Available SpaceResource Name Creating System Resource Monitoring Requests 6Troubleshooting EMS Directories and Files Etc/opt/resmon/log EMS Logging Logging and tracing EMS Tracing Network Performance Issues System Performance IssuesPerformance Considerations 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