diskmond man page on HP-UX

Man page or keyword search:  
man Server   10987 pages
apropos Keyword Search (all sections)
Output format
HP-UX logo
[printable version]

diskmond(1m)							  diskmond(1m)

NAME
       diskmond - EMS Disk Resource Monitor daemon

SYNOPSIS
DESCRIPTION
       The  daemon monitors the status of physical devices and logical volumes
       configured in the Logical Volume Manager (LVM).	It is an  Event	 Moni‐
       toring Services (EMS) monitor.

       includes	   a   resource	  dictionary   file   (/etc/opt/resmon/dictio‐
       nary/diskmond.dict) which is used by EMS to identify resources for mon‐
       itoring.

   Options
       diskmond recognizes the following command-line options:

	      Write  a	syslog	message	 any time a monitored resource changes
	      value.  If
			     this option is  not  specified,  and  the	syslog
			     notification  type was not selected for the moni‐
			     tored resource in the GUI, no syslog messages are
			     logged    for   value   changes.	 The   default
			     diskmond.dict does not specify this option.

	      Turn on daemon debugging	and  tracing  messages.	  This	allows
	      detailed
			     information     to	    be	   logged    to	   the
			     /var/opt/resmon/log/diskmond.log file.   WARNING:
			     This  file	 grows	without	 bound.	 Only use this
			     option if you really need a trace.	 Debugging and
			     tracing is off by default.

RESOURCES
       The EMS Disk Resource Monitor monitors the following resources:

   Logical Volume Copies
       /vg/<vgName>/lv/copies/<volumeName>

       This  resource  is  an  integer representing the current number of data
       copies in a logical volume.  It is only valid for mirrored  disks  con‐
       figured	with MirrorDisk/UX.  The number of copies includes the primary
       copy of data plus all mirrors.  This resource can be used to  determine
       if one or more of the copies of data is unavailable.

       Possible values are:

       No complete copies of the data are available.  If a volume group
	      or logical volume is inactive, there will be 0 copies available.

       One complete copy of the data is available.  If the data is
	      unmirrored,  then	 all  physical extents are up.	If the data is
	      2-way mirrored, at least one of the logical extents has a	 miss‐
	      ing or stale physical extent.  If the data is 3-way mirrored, at
	      least one of the logical extents has  a  missing/stale  physical
	      extent.

       Two complete copies of the data are available.  If the
	      data  is	2-way  mirrored, all copies of the data are available.
	      If the data is 3-way mirrored,  at  least	 one  of  the  logical
	      extents has a missing/stale physical extent.

       All copies of the data are available. This is only possible with
	      three-way mirroring.

   Logical Volume Status
       (/vg/<vgName>/lv/status/<volumeName>)

       This  resource represents the status of a logical volume as reported by
       LVM.  LVM status is based on the last I/O activity.  The following enu‐
       merated states can be reported:

       Active and at least one copy of all data is available

       This logical volume is currently inactive

       Active and at least one portion of data is completely unavailable

   Logical Volume Summary
       (/vg/<vgName>/lv_summary)

       This  resource  provides	 a  summary status of the logical volumes in a
       particular volume group.	 Possible values are:

       All logical volumes are UP

       This volume group is inactive

       This volume group is inactive, but the last time it was active, it  was
       DOWN.

       At least one logical volume is not UP

       The INACTIVE_DOWN state will be exited in two cases:
		      o	 querying  the logical volumes results in an UP state,
	      or
		      o /etc/lvmtab changes

   Physical Volume and PVLink Status
       (/vg/<vgName>/pv_pvlink/status/<cXXtXXdXX>)

       This resource shows the status of the  physical	volume	or  PVLink  as
       reported	 by  a	SCSI inquiry to the device.  Each resource name corre‐
       sponds to a device file in /dev/dsk.  Possible states are as follows:

       This device was successfully contacted

       Either the device or the bus returned a busy signal when the monitor
	      tried to contact the device; 3 attempts are made before  marking
	      a device BUSY

       SCSI inquiry is unsuccessful; device is inaccessible.

   Physical Volume and PVLinks Summary
       (/vg/<vgName>/pvsummary)

       This  resource  provides	 a  summary status of the physical volumes and
       pvlinks in a particular volume group.  Possible values are:

       All physical volumes and pvlinks are UP.

       Some physical volumes and pvlinks are not UP, but at least
	      one PVG has all physical volumes and pvlinks UP.

       Some physical volumes and pvlinks are down, and they are in
	      different PVGs,  therefore  the  disk  monitor  cannot  conclude
	      whether all data is available.

       Enough physical volumes and pvlinks are not UP so that there is not
	      one complete copy of all data (based on PVGs).

AUTHOR
       was developed by HP.

FILES
       Executable.

       The resource dictionary for
			   describes  the  location (/vg) of disk resources in
			   the	resource  hierarchy  and  references  as   the
			   resource monitor.
       Log file for the entire Resource Monitor Framework, including
			   Any errors are logged here.
       System log file.	 Some errors are logged here as well as in
			   Also,  if  the  option is specified, resource state
			   changes detected by are logged here.
       Configuration file currently used to contain one or more VG names to be
			   excluded  from  consideration  for  monitoring   by
			   diskmond.   This file is If this file is not found,
			   the default	behavior  is  to  include  all	volume
			   groups found in /etc/lvmtab.	 Please see the sample
			   configuration      file	 /etc/opt/resmon/moni‐
			   tors/diskmond.config.sample for more information.

DEPENDENCIES
       must  be	 run  by the registrar process of the Event Monitoring Service
       (EMS).

SEE ALSO
       resls(1), ems(5).

								  diskmond(1m)
[top]

List of man pages available for HP-UX

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net