9.7 moncheck (checks definitions)

Format

moncheck

Users who can execute the command

Superuser and general user

Description

This command checks definitions. The moncheck command checks the following items:

• Whether the definitions in the definition files are consistent with the specification rules and conventions

• Whether the following resources are available:

  • Resources specified in operands in the environment definition file

  • LAN status settings files

  • LAN monitor definition files for the LAN interfaces specified in the switchbyfail operand in the server environment definition

  If these resources are not available, not available is displayed.

  The following table shows the resources that the moncheck command checks for availability and the meaning of not available.

  Table 9‒3: Resources that the moncheck command checks for availability and the meaning of not available

  Resource whose availability is checked		Meaning of not available
  HA Monitor environment settings (sysdef)	lan operand	The specified host name is not defined in /etc/hosts.
  	usrcommand operand	No file corresponds to the specified path, or the file owner does not have execution permissions.
  	multicast_lan operand	The host name of the specified host group is not defined in /etc/hosts. Alternatively, the specified IP address is not a class-D address.
  Server environment definition (servers)	disk operand	The specified volume group does not exist. At least one of the disk devices that make up the specified volume group is incorrectly included in a control group of HA Booster.
  	fs_name operand	The specified path is not a path to a file system.
  	fs_mount_dir operand	No directory corresponds to the specified path.
  	hab_gid operand	HA Booster cannot be used.
  	ptrlcmd_ex operand sby_ptrlcmd_ex operand patrolcommand	No file corresponds to the specified path, or the file owner does not have execution permissions.
  	scsi_device operand	No SCSI device name is specified. If the specified device name belongs to a symbolic link, no symbolic link name is specified. If the specified device name belongs to an HDLM logical device, no HDLM logical device name is specified. This includes when HDLM has not been installed and when HDLM services are stopped.
  	dmmp_device operand	No DMMP logical device name is specified. DMMP has not been installed. The DMMP services are stopped.
  Monitor-mode program environment definition (programs)	restartcommand operand	No file corresponds to the specified path, or the file owner does not have execution permissions.
  LAN status settings file		The server-alias-name.up or server-alias-name.down file does not exist in /opt/hitachi/HAmon/etc. Alternatively, the file owner does not have execution permissions.
  LAN monitor definition files for the LAN interfaces specified in the switchbyfail operand in the server environment definition		There is no LAN monitor definition file under /opt/hitachi/HAmon/etc/ that corresponds to the LAN interface specified for the switchbyfail operand. Alternatively, the file owner does not have read permissions.
  Monitoring definition file for the system disk (if use is specified for the disk_ptrl operand in the HA Monitor environment settings)		The /opt/hitachi/HAmon/etc/system_patrol.disk file does not exist. Alternatively, the file owner does not have read permissions. The monitoring definition file for the system disk does not satisfy any of the following conditions: • The monitoring-target files exist. • The monitoring targets are files. • The absolute path of each monitoring-target file has a valid length. • The number of monitoring-target files is valid. • All monitoring-target files are unique.
  Monitoring definition file for the disk for business use (if use is specified for the disk_ptrl operand in the server environment definition)		The server-alias-name.disk file does not exist in /opt/hitachi/HAmon/etc/. Alternatively, the file owner does not have read permissions. The monitoring definition file for the disk for business use does not satisfy any of the following conditions: • The absolute path of each monitoring-target file has a valid length. • The number of monitoring-target files is valid. • All monitoring-target files are unique.

• If the function that detects OS panics in other systems is used, the environment in which the function can operate is prepared.

• When the HA Monitor Extension functions are set up, whether the monsetup -ex command is executed.

• When SCSI reservation for shared disk is used, whether the following operands are consistent with each other:

  • fence_reset and fence_scsi operands in the HA Monitor environment settings

  • fence_scsi operand in the HA Monitor environment settings and the scsi_device or dmmp_device operand in the server environment definition

Options

None

Return codes