HP HA s Software manual Filesystem Available Space, Resource Name

Page 71

Monitoring System Resources

System Monitor Reference

 

Filesystem Available Space

 

The filesystem monitor checks the number of megabytes available for use in each

 

file system on the node. File systems must be mounted and active to be monitored.

 

File systems mounted over the network, such as NFS file systems, are not

 

monitored.

 

The MIB variables fileSystemBavail, and fileSystemBsize from the

 

hp-unix MIB are used to calculate the number of available Kb in the file systems.

 

The number is then divided by 1024 to get the number of available Mb.

Table 5-3

Filesystem Available Space

 

 

 

 

 

Resource Name

 

 

 

 

 

Most common names are:

 

 

/system/filesystem/availMb/stand

 

 

/system/filesystem/availMb/root

 

 

/system/filesystem/availMb/home

 

 

/system/filesystem/availMb/opt

 

 

/system/filesystem/availMb/tmp_users

 

 

/system/filesystem/availMb/usr

 

 

/system/filesystem/availMb/var

 

 

 

 

You may have more file systems, or different names, depending on how you

 

configured file systems on your system. You can monitor when a file system starts

 

filling up so you can clean up old files or add disk space and reconfigure your file

 

systems.

 

 

 

NOTE

Because the “/” character is not valid in a resource name, it is replaced by the “_”

 

character. So the file system /tmp/users would appear as the resource name

 

/system/filesystem/availMb/tmp_users. For the same reason the root file system (/)

 

is replaced by the name “root”.

 

The minimum polling interval is 30 seconds. We recommend a longer interval; short

 

 

polling intervals may adversely affect system performance.

 

When configuring requests from the SAM interface, a wildcard (*) is available to

 

monitor all file systems on a system.

Chapter 5

71

Image 71
Contents B5735-90001 August Using EMS HA MonitorsLegal Notices Contents Monitoring Network Interfaces Monitoring Cluster ResourcesGlossary 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 MonitorsChapter Role of EMS HA Monitors in a High Availability Environment Installing EMS HA Monitors Installing and Removing EMS HA MonitorsRemoving EMS HA Monitors Pvpvlink Using EMS HA MonitorsEvent Monitoring Service Resource Class Hierarchy Status AvailMBEvent Monitoring Service Screen Screen Selecting a Resource to MonitorUsing Wildcards Monitoring Request Parameters Creating a Monitoring RequestHow Do I Tell EMS When to Send Events? Which Protocols Can I Use to Send Events? What is a Polling Interval?What is a Notification Comment? Removing Monitoring Requests Copying Monitoring RequestsModifying Monitoring Requests Service EMS Configuring MC/ServiceGuard Package DependenciesPackage Configuration 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 ReferenceInterpreting Physical Volume Summary Physical Volume SummaryDisk Monitor Reference Interpreting Physical Volume and Physical Volume Link Status Physical Volume and Physical Volume Link StatusInterpreting Logical Volume Summary Logical Volume SummaryLogical volume is DOWN, a complete copy of the data is not Logical Volume StatusInterpreting Logical Volume Status Logical volume is inactiveInterpreting Logical Volume Copies Logical Volume Number of CopiesRules 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 ArraysAdding 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 ArraysPvgup Return Mirrored Disks Example Resources to Monitor for Mirrored DisksMonitoring 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 DevicesResources to Monitor for Root Volumes Monitoring Cluster Resources Cluster Cluster Monitor ReferenceCluster Monitor Resource Class Hierarchy Interpreting Custer Status Cluster StatusInterpreting Node Status Node StatusInterpreting Package Status Package StatusCreating 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 isConfiguring Network Monitoring Requests 30 secMonitoring System Resources System Resource Monitor Class Hierarchy System Monitor ReferenceResource 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 tracingEMS Tracing Performance Considerations System Performance IssuesNetwork Performance Issues Testing Network Monitor Requests Testing Monitor RequestsTesting Disk Monitor Requests Testing Cluster Monitor RequestsMaking Sure Monitors are Running Glossary Notification See alert Glossary Glossary Index Index Index