Physical Disk Overview (PI_PDSK)

Notes

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

• Note the following points when collecting this record in a Windows environment:

  • If a security setting prevents access to the disk volume that corresponds to the ID (ID) field, no record is created for this disk volume. To create a record of the disk volume, set the security setting in the monitoring target setup to allow the user account specified in User to access the disk volume.

  • 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 a record is collected, the ID (ID) field might display the disk volume name before the change was made.

• If the OS of the monitored host is AIX, only the following users can collect this record information:

  • root user

  • User who belongs to both adm and system groups

• If the OS of the monitored host is AIX, and if you change the device name by using a command such as rendev, performance data is collected for a different instance than the one that was present before the change.

• If the OS of the monitored host is the Workload Partition (WPAR) environment of AIX V6.1 or later, the information for this record cannot be collected.

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

• If the monitored host is running Solaris, and the disk configuration is changed while JP1/PFM - RM for Platform is collecting performance information, PI_PDSK records are not collected.

  Note:

  Changing the disk configuration means that the following command was executed, resulting in a message such as <<device added: xxxx>> being output.

  Command: iostat -x 5 2