Translate this Page

 

To monitor event in HP-UX server, first we must install and running Event Monitoring Services(EMS). After that we can use monconfig (a utility that allows a superuser to manage hardware event monitor requests for EMS).

In this working note, I will show you the example steps through creating a monitor request and sending any alerts that are greater than or equal to (>=) “Major Warnings” to an EMAIL address

ffahserver:/>cd /etc/opt/resmon/lbin
ffahserver:/etc/opt/resmon/lbin>ll
total 7872
lrwxr-xr-x   1 bin        bin              7 Mar 17  2004 clustermond -> mibmond
-r-xr--r--   1 bin        bin         280464 Jul 14  2005 emsagent
lrwxr-xr-x   1 bin        bin              7 Mar 17  2004 fsmond -> mibmond
-r-xr--r--   1 bin        bin          36864 Sep  1  2004 krmond
lrwxr-xr-x   1 bin        bin              7 Mar 17  2004 lanmond -> mibmond
-r-xr-xr-x   1 bin        bin        3055616 Jun 27  2003 mibmond
-r-xr--r--   1 bin        bin          49152 Jun 21  2005 moncheck
-r-xr--r--   1 bin        bin          94208 Aug 23  2005 monconfig
-r--r--r--   1 bin        bin          12806 Feb 28  2005 monconfig.help
-r-xr-xr-x   1 bin        bin          86016 Jul 14  2005 p_client
lrwxr-xr-x   1 bin        bin              7 Mar 17  2004 pkgmond -> mibmond
-r-xr-xr-x   1 bin        bin         167936 Jul 14  2005 registrar
-r-xr-xr-x   1 bin        bin          40960 Aug 23  2005 send_test_event
-r-xr-xr-x   1 bin        bin          32768 Aug 23  2005 set_fixed
-r-xr--r--   1 bin        bin            232 Feb 28  2005 startcfg_client
-r-xr--r--   1 bin        bin          69632 Jun 21  2005 startmon_client
lrwxr-xr-x   1 bin        bin              7 Mar 17  2004 svcmond -> mibmond
-r--r--r--   1 bin        bin           3019 Mar 29  2001 test.cov
-r-xr--r--   1 bin        bin          57344 Jun 21  2005 toggle_switch

 ffahserver:/etc/opt/resmon/lbin>./monconfig

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

 EVENT MONITORING IS CURRENTLY ENABLED.
 EMS Version : A.04.20
 STM Version : A.49.10

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

Note: Monitoring requests let you specify the events for monitors
 to report and the notification methods to use.

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) /StorageAreaNetwork/events/SAN_Monitor
 2) /storage/events/disk_arrays/AutoRAID
 3) /storage/events/disks/default
 4) /adapters/events/FC_adapter
 5) /adapters/events/TL_adapter
 6) /system/events/chassis
 7) /system/events/core_hw
 8) /connectivity/events/hubs/FC_hub
 9) /connectivity/events/multiplexors/FC_SCSI_mux
 10) /connectivity/events/switches/FC_switch
 11) /adapters/events/iscsi_adapter
 12) /system/events/memory
 13) /adapters/events/ql_adapter
 14) /adapters/events/raid_adapter
 15) /storage/events/enclosures/ses_enclosure
 16) /storage/events/tapes/SCSI_tape
 17) /system/events/ups
 18) /storage/events/disk_arrays/FC60
 19) /system/events/ipmi_fpl
 20) /storage/events/disk_arrays/FW_SCSI
 21) /storage/events/disk_arrays/High_Availability
 22) /system/events/ia64_corehw
 23) /system/events/cpu/lpmc
 24) /storage/events/disk_arrays/MSA1000
 25) /adapters/events/scsi123_em
 26) /system/events/system_status
 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] 3

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] dba@levicorp.co.id

User Comment:
 (C)lear   (A)dd
 Enter selection {or (Q)uit,(H)elp} [c] a

 Enter comment: [] SERVER_ERROR Call DBA

Client Configuration File:
 (C)lear
 Use Clear to use the default file.
 Enter selection {or (Q)uit,(H)elp} [c] c

New entry:
 Send events generated by all monitors
 with severity >= MAJOR WARNING to EMAIL dba@levicorp.co.id
 with comment:
SERVER_ERROR Call DBA

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

 Changes will take effect when the diagmond(1M) daemon discovers that
 monitoring requests have been modified.  Use the 'c' command to wait for
 changes to take effect.

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

Note: Monitoring requests let you specify the events for monitors
 to report and the notification methods to use.

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

============================================================================
=======================      Enable Monitoring      ========================
============================================================================

 This may take a while...

Waiting for changes in monitoring requests or in hardware configuration
to take effect...

 EVENT MONITORING IS CURRENTLY ENABLED.

 Leave a Reply

(required)

(required)

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

   
© 2012 LevICORP's webnote Suffusion theme by Sayontan Sinha