Logical Disk Overview (PI_LDSK)

Notes

• If the connection to the monitored host fails, the information cannot be collected.

• If you collect this record in a Windows environment, note the following:

  • This record collects performance information for hard disk drives and fixed disk drives. Performance information for other devices (such as network disks) cannot be monitored.

  • If a disk volume corresponding to the ID (ID) field is not accessible due to the security settings, no record for that disk volume is created. To create a record for such a disk volume, change the security settings so that the user account specified for User in the monitoring target settings can be used to access the disk volume.

  • If no drive letter or drive path is assigned to the disk volume, 0 is set in the Size (SIZE) field.

  • If multiple drive letters or drive paths are assigned to the same disk volume, 0 might be set in the Size (SIZE) field.

  • If you change the drive letter or drive path of a disk volume, restart the WMI service of the monitoring target you changed. If you try to collect records without restarting it, you might not be able to collect the records from that disk volume. Even if the record is collected, the Size (SIZE) field might contain a value of 0 and the ID (ID) field might contain the logical disk volume name before the change was made.

• If the OS of the monitored host is UNIX, and if Filesystem or Mounted on includes a space when you execute the df command on the monitored host, the Logical Disk Overview (PI_LDSK) record will not be correctly displayed.

• If the monitored host uses an optical drive, the Free Mbytes % field for the applicable instance is sometimes set to 0% when media is inserted into the drive. To remove the Free Mbytes % field from the alarm settings, specify ID <> applicable-disk in the alarm condition expression.

• Information is not collected if TargetType is set to icmp in the monitoring target settings.