6.20.2 Settings in the files required for disk monitoring

(1) Settings in the files required for monitoring the system disk

To monitor the system disk, you must perform the following operations:

• Specifying the settings in the monitoring definition file for the system disk

• Creating monitoring-target files

Specifying the settings in the monitoring definition file for the system disk

The monitoring definition file for the system disk is /opt/hitachi/HAmon/etc/system_patrol.disk. In this monitoring definition file, specify a file that exists on the system disk.

A sample file of the monitoring definition file is provided at /opt/hitachi/HAmon/lib/system_patrol.disk. Copy this file to /opt/hitachi/HAmon/etc/system_patrol.disk, and use a copied file.

The contents of the sample monitoring definition file are as follows:

/opt/hitachi/HAmon/spool/hamonitor_disk_patrol

In the sample file, /opt/hitachi/HAmon/spool/hamonitor_disk_patrol is specified as the monitoring-target file. If the /opt/hitachi/HAmon file system exists on the system disk and the system disk uses only one mount point, you can use the sample file without changing the file contents.

If the /opt/hitachi/HAmon file system is not placed on the system disk:

On the system disk, create a monitoring-target file in a desired file system, and specify the file in the monitoring definition file.

The following shows a specification example (in the case where /home exists on the system disk and the hamonitor_disk_patrol file is monitored).

/home/hamonitor_disk_patrol

If the system disk can use multiple mount points (such as /home, /var, and /opt):

Create a monitoring-target file in a desired file system for each mount point, and specify the files in the monitoring definition file.

The following shows a specification example (in the case where additional mount point /home can also be used and the /home/hamonitor_disk_patrol file is also monitored).

/opt/hitachi/HAmon/spool/hamonitor_disk_patrol
/home/hamonitor_disk_patrol

Do not create a monitoring-target file in virtual file systems such as /boot, /proc, and /sys.

Observe the following rules when specifying settings in the monitoring definition file:

• Specify the absolute paths of the monitoring-target files on separate lines (one path on one line).

• The path of each monitoring-target file can have a maximum of 247 bytes.

• The path of each monitoring-target file must not include tabs or spaces.

• Tabs or spaces before or after the path of a monitoring-target file are ignored.

• The number of monitoring-target file paths that can be specified is 1 to 128.

Creating monitoring-target files

The monitoring-target files specified in the monitoring definition file must be created. You do not need to create the /opt/hitachi/HAmon/spool/hamonitor_disk_patrol file, which is automatically created when HA Monitor is installed.

A sample monitoring-target file is provided at /opt/hitachi/HAmon/lib/hamonitor_disk_patrol. Create the necessary number of copies of the sample file with the names specified in the monitoring definition file. For example, assume that the monitoring definition file contains the following settings:

/opt/hitachi/HAmon/spool/hamonitor_disk_patrol
/home/hamonitor_disk_patrol

In this case, copy the file as follows:

cp /opt/hitachi/HAmon/lib/hamonitor_disk_patrol /home/hamonitor_disk_patrol

To Page Top

(2) Settings in the files required for monitoring disks for business use

To monitor disks for business use, you must perform the following operations:

• Specifying the settings in the monitoring definition file for the disk for business use

• Creating monitoring-target files

Specifying the settings in the monitoring definition file for the disk for business use

The monitoring definition file for the disk for business use must be created at a specific location with a name in the following format: /opt/hitachi/HAmon/etc/server-alias-name.disk. You must set this monitoring definition file on each server. In this monitoring definition file, specify the following files:

• Files at the mount points for the monitoring-target disks for business use

Observe the following rules when specifying settings in the monitoring definition file:

• Specify the absolute paths of the monitoring-target files on separate lines (one path on one line).

• The path of each monitoring-target file can have a maximum of 247 bytes.

• The path of each monitoring-target file must not include tabs or spaces.

• Tabs or spaces before or after the path of a monitoring-target file are ignored.

• The number of monitoring-target file paths that can be specified is 1 to 128.

Creating monitoring-target files

The monitoring-target files specified in the monitoring definition file must be created.

A sample monitoring-target file is provided at /opt/hitachi/HAmon/lib/hamonitor_disk_patrol. Create the necessary number of copies of the sample file with the names specified in the monitoring definition file. For example, assume that the monitoring definition file contains the following settings:

/data1/hamonitor_disk_patrol
/data2/hamonitor_disk_patrol

In this case, copy the file as follows:

cp /opt/hitachi/HAmon/lib/hamonitor_disk_patrol /data1/hamonitor_disk_patrol
cp /opt/hitachi/HAmon/lib/hamonitor_disk_patrol /data2/hamonitor_disk_patrol

To Page Top