monconfig 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]

monconfig(1m)							 monconfig(1m)

NAME
       - is a utility that allows a superuser to manage hardware event monitor
       requests for EMS.

SYNOPSYS
       /etc/opt/resmon/lbin/monconfig

DESCRIPTION
       The utility can be  used	 to  List,  Add,  Modify,  or  Delete  monitor
       requests.   The	utility	 will also allow the user to enable or disable
       monitor requests.  A superuser can run at any time to configure monitor
       requests.

   Options
       does not support any options.

   Application Usage
       This  tool  will	 be deprecated on new server models. Please use System
       Management Homepage (see hpsmh(1M)).

EXAMPLES
       The following example steps through  creating  a	 monitor  request  and
       sending	any alerts that are greater than or equal to (>=) "Major Warn‐
       ings" to an EMAIL address.

       ======================================================================
       ================	       Event Monitoring Service	      ================
       ================	     Monitoring Request Manager	      ================
       ======================================================================

	 EVENT MONITORING IS CURRENTLY ENABLED.

       ======================================================================
       ===========	Monitoring Request Manager Main Menu	   ===========
       ======================================================================

       Select:
	  (S)how monitoring requests configured via monconfig
	  (C)heck detailed monitoring status
	  (L)ist descriptions of available monitors
	  (A)dd a monitoring request
	  (D)elete a monitoring request
	  (M)odify an existing monitoring request
	  (E)nable Monitoring
	  (K)ill (disable) monitoring
	  (H)elp
	  (Q)uit
	  Enter selection: [s] a

       ======================================================================
       ==================      Add Monitoring Request	    ==================
       ======================================================================

       Start of edit configuration:

       A monitoring request consists of:
	 - A list of monitors to which it applies
	 -  A  severity	 range	(A  relational expression and a severity.  For
       example,
	   < "MAJOR WARNING" means events with severity "INFORMATION" and
	   "MINOR WARNING")
	 - A notification mechanism.  Please answer the following questions to
       specify a monitoring request.

       Monitors to which this configuration can apply:
	  1) /storage/events/disk_arrays/AutoRAID
	  2) /storage/events/disks/default
	  3) /adapters/events/FC_adapter
	  4) /connectivity/events/hubs/FC_hub
	  5) /connectivity/events/multiplexors/FC_SCSI_mux
	  6) /system/events/memory
	  7) /storage/events/enclosures/ses_enclosure
	  8) /storage/events/tapes/SCSI_tape
	  9) /storage/events/disk_arrays/FW_SCSI
	 10) /storage/events/disk_arrays/High_Availability
	  Enter monitor numbers separated by commas
	     {or (A)ll monitors, (Q)uit, (H)elp} [a] a

       Criteria Thresholds:
	  1) INFORMATION    2) MINOR WARNING	3) MAJOR WARNING
	  4) SERIOUS	    5) CRITICAL
	  Enter selection {or (Q)uit,(H)elp} [4] 3

       Criteria Operator:
	  1) <	    2) <=      3) >	 4) >=	    5) =      6) !=
	  Enter selection {or (Q)uit,(H)elp} [4] 4

       Notification Method:
	  1) UDP	2) TCP	      3) SNMP	    4) TEXTLOG
	  5) SYSLOG	6) EMAIL      7) CONSOLE
	  Enter selection {or (Q)uit,(H)elp} [6] 6

	  Enter email address: [root] some_user@hp.com

       New entry:
	     Send events generated by all monitors
	     with severity >= MAJOR WARNING to EMAIL some_user@hp.com

	  Are you sure you want to keep these changes?
	     {(Y)es,(N)o,(H)elp} [n] y

       When you press <Enter>, the new monitor request will be created and the
       user will be returned to	 the  Monitoring  Request  Manager  Main  Menu
       screen.

       ----------------------------------------------------------------------
       When you Add and/or Modify a monitor request, the  following  questions
       will appear:

       Criteria Thresholds
	    This selection will allow the user to select a triggering
	    level that will cause a monitor request to issue an alert.
	    Thresholds can be:

	    Critical - An event that will or has already caused data
		 loss, system down time, or other loss of service.
		 Immediate action is required to correct the problem.
		 System operation will be impacted and normal use of the
		 hardware should not continue until the problem is
		 corrected. If Service Guard is installed and this is a
		 critical component, it will perform a package
		 fail-over.
	    Serious - An event that may cause data loss, system down
		 time, or other loss of service if left uncorrected.
		 The problem should be repaired as soon as possible.
		 System operation and normal use of the hardware may
		 be impacted. If Service Guard is installed and this
		 is a critical component, it will perform a package
		 fail-over.
	    Major Warning - An event that could escalate to a more
		 serious condition if not corrected. The problem should
		 be repaired at a convenient time. System operation
		 should not be impacted and normal use of the hardware
		 can continue. If Service Guard is installed, it will
		 NOT perform a package fail-over.
	    Minor Warning - An event that will not likely escalate to a
		 more serious condition if let uncorrected. The problem
		 can be repaired at a convenient time. System operation
		 will not be interrupted and normal use of the hardware
		 can continue. If Service Guard is installed, it will
		 NOT perform a package fail-over.
	    Informational - An event that is expected as part of the
		 normal operation of the hardware. No action is
		 required. If Service Guard is installed, it will NOT
		 perform a package fail-over.

       Criteria Operators
	    This selection will allow the user to select a relationship
	    to a Criteria Threshold that will cause a monitor request
	    to issue an alert. For example, if "greater than" is selected
	    for Minor Warning, the monitor request will issue alerts when
	    it identifies any problems that are greater than (more serious)
	    than a Minor Warning. Operators can be:

	      <	 (less than)
	      <= (less than or equal to)
	      >	 (greater than)
	      >= (greater than or equal than)
	      =	 (equal)
	      !	 (not equal to)

       Notification Method
	    This selection will allow the user to select a location to
	    send an alert issued by a monitor request. Locations can be:

		UDP - User Datagram Protocol (a host name and port number
		      will be requested)
		TCP - Transmission Control Protocol (a host name and port
		      number will be requested)
		OPC - OpenView Messaging Protocol (this selection is only
		      offered when OpenView Messaging is installed on the
		      system)
	       SNMP - Simple Network Management Protocol
	    TEXTLOG - A text file (path will be requested)
	     SYSLOG - The system log
	      EMAIL - An electronic mailbox address (email address will
		      be requested)
	    CONSOLE - The system console

FILES
       /var/stm/data/tools/monitor/disabled_instances	-   file   that	 lists
       instances (devices) for which monitoring requests should NOT be created
       by monconfig

DEPENDENCIES
       Event  Monitoring  Services  (EMS)  must be installed and running.  You
       must be a superuser.

AUTHOR
       was developed by HP.

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

								 monconfig(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