emscli(1M)emscli(1M)NAMEemscli - Event Monitoring Service Command Line Interface
SYNOPSIS
condition value] notification_option] interval unit_of_polling] notifi‐
cation_mechanism] "comment"]
Req_ID condition value] notification_option] interval unit_of_polling]
notification_mechanism] "comment"]
Req_ID1[resource_class]
Req_ID1[filename]
Req_ID1[resource_class]
resource_class]
DESCRIPTION
is a command line utility that is used to configure and manage persis‐
tent monitoring requests for Event Monitoring Service (EMS) monitors,
such as, HA Monitors, Hardware Monitors and Kernel Monitors. The util‐
ity can be used to perform the following activities.
· Add Monitoring Requests
· Modify Existing Monitoring Requests
· Delete Monitoring Requests
· Generate Script for Currently Configured Requests
· List Monitoring Requests
· View Status of Monitoring Requests
· List Resource Instances Available for Monitoring
· Help to view the usage of various options of
Options
supports the following options and arguments:
Add a new monitoring request and specify the resource instance
for which
a request needs to be created. also allows a
user to specify a wildcard resource instance. For
example, The following parameters can be used
with the option.
Note: If parameters are not provided, all default
parameters will be used while adding a monitoring
request. If a duplicate request already exists,
does not register the new request.
Specify when the notification has to be sent.
Notify when a value exists, and specify a
comparison value.
This is the default option. You
define the conditions under which
you wish to be notified for a par‐
ticular resource. Choose an operator
(=, not equal, >, >=, <, <=) and one
of the possible values returned by
the monitor. The content of the
value field varies depending upon
the resource monitored.
Notify when a value changes.
This sends notification every time a
resource value changes. Typically
this is used for resources whose
values change infrequently. Change
here means any change. For example,
you could receive notification every
time the number of mirrored copies
of data changes, whether it is from
2 to 1 or from 1 to 2.
Notify at each interval.
This sends notification at each
polling interval. It is commonly
used for reminders or for gathering
data for system analysis. Use this
for only a small number of resources
at a time, and with long polling
intervals of several minutes or
hours; there is a risk of affecting
system performance.
Specify the notification options.
This determines what type of event will
trigger a notification when the threshold
is crossed. This option takes any or all
of the following notification options:
Initial notification.
Use this option to establish a base‐
line when monitoring resources such as
available filesystem space or system
load. It can also be used to test
whether newly requested events are
being sent.
Repeat notification.
Use this option for urgent alerts. The
Repeat option sends an alert at each
polling interval as long as the notify
condition is met. Use this option with
caution because there is a risk of
high CPU use or filling log files and
alert windows.
Return notification.
Use this option to track when emer‐
gency situations return to normal.
Specify a polling interval. The polling interval
specifies how often the resource monitor checks
the
resource value. The polling interval is the
maximum amount of elapsed time before a
monitor knows about a change in status for
a particular resource. The default value is
300.
Specify a unit of polling interval.
This option takes one of the following four
units of polling.
Seconds. This is the default option.
Minutes
Hours
Day
Specify a conditional statement.
condition takes one of the following
options:
Equal to.
Not equal to. This is the default
option.
Less than.
Less than or equal to.
Greater than.
Greater than or equal to.
value is the threshold value. The default
threshold value is 0.
Select the mechanism to be used for notification.
This option takes one of the following
8 notification mechanisms:
Simple Network Management Protocol.
This option can be used with any
application that accepts SNMP
traps, such as, OpenView NNM or
ITO. The application must be set‐
up to recognize the SNMP traps
generated. This is the default
option. The severity levels for
SNMP trap notifications are:
Critical Severity
Major Severity
Minor Severity is the default
option.
Warning
Normal Severity
OpenView Messaging Protocol.
This option sends messages to ITO
applications via the opcmsg dae‐
mon. For this option to display,
IT Operation Managed Node software
must be installed on the resource
server. The severity levels for
OPC messages are:
Critical Severity
Major Severity
Minor Severity
Warning
Normal Severity
User Datagram Protocol.
This option sends UDP encoded
events to the target host name and
port indicated for that request.
Thus, the message can be directed
to a user-written socket program.
Hostname for UDP notification.
Port Number for UDP notification.
Transmission Control Protocol.
This option sends TCP encoded
events to the target host name and
port indicated for that request.
Thus, the message can be directed
to a user-written socket program.
Hostname for TCP notification.
Port Number for TCP notification.
This option sends event notification to
a file you specify.
Note: For a textlog file, the path
for the filename is not mandatory.
If a path is not specified, it
defaults to
This sends event notification to the
system log.
The default file defines the loca‐
tion for the file.
This option sends event notification to
the email address indicated for that
request.
This option sends event notification to
the system console.
This option sends event notification to
the Event Viewer tool available in the
HP System Management Homepage (HP SMH).
To launch Event Viewer, enter
http://<hostname>:2301 on the Web
browser and go to Logs -> Evweb ->
Event Viewer. You can also run the
evweb command to view these notifica‐
tions. For more information, refer the
evweb(9) manpage.
The notification comment is useful for sending
task reminders to the
recipients of an event. Enter the com‐
ment within quotes.
Deletes configured EMS monitoring requests by specifying the
request IDs.
Each monitoring request is identified by a unique
request ID (Req_ID).
Note: Request ID is the "Monitor Request ID in DECI‐
MAL" field of the output and not the "PID.Request#".
Deletes EMS requests configuration under a speci‐
fied resource class.
EMS groups resources into classes in a
hierarchy similar to that of a filesystem
structure. Resource Classes specify a
monitorable resource by its full hierar‐
chical name. Resources are organized into
tree structures, starting with the most
general class, branching into more spe‐
cific subclasses, and ending in individual
resource instances.
Executes force delete. EMS asks for confirmation
before deleting the request.
Note:
More than one option is allowed so that
requests associated with multiple resource
classes can be deleted.
Generates script for all configured requests specified by
request IDs.
Each monitoring request is identified by a unique
request ID ( Req_ID).
Note: Request is the "Monitor Request ID in DECIMAL"
field of the output and not the "PID.Request#". Also
specify a user-defined filename for the script.
Note: If filename is not specified, it saves the
script to by default.
Invokes help for viewing the usage of various options of the
utility.
Lists EMS configured persistent monitoring requests with only
selected
columns.
Lists monitoring requests with all columns.
The output may be cluttered.
Modifies persistent monitoring requests.
Each monitoring request is identified by a unique
request ID (Req_ID).
If parameters are not provided, all default parameters
will be used while modifying a monitoring request.
When parameters for a request are modified, the Req_ID
changes. If a duplicate request already exists, emscli
does not register the new request.
Request is the "Monitor Request ID in DECIMAL" field
of the output and not the "PID.Request#". The options
described in the option are also applicable to option.
Note: When is used without all the options, then the
values that were set while registering the request get
retained. For example, if a request was registered
with the default parameters, executing will not alter
the other parameters.
Lists resource instances available for monitoring.
Prints resource instances configured under a specified
resource class.
EMS groups resources into classes in a hierar‐
chy similar to that of a filesystem structure.
Resource Classes specifies a monitorable
resource by its full hierarchical name.
Resources are organized into tree structures,
starting with the most general class, branching
into more specific subclasses, and ending in
individual resource instances.
Note: The option lists all available resources if a
resource class is not provided.
Prints status of all currently monitored requests. Each monitor‐
ing request
is identified by a unique request ID (Req_ID).
Note: Request ID is the "Monitor Request ID in DECIMAL"
field of the output and not the "PID.Request#".
Prints resource instances configured under a specified
resource class.
EMS groups resources into classes in a hierar‐
chy similar to that of a filesystem structure.
Resource Classes specifies a monitorable
resource by its full hierarchical name.
Resources are organized into tree structures,
starting with the most general class, branching
into more specific subclasses, and ending in
individual resource instances.
Return Value
returns 0 on success and 1 on failure.
EXAMPLES
Add a monitoring request in with default parameters:
Modify request parameters (notification mechanism - snmp, severity
level - maj) for request ID, 1709703209:
Delete the monitoring request having the request ID, 1709703212:
Generate script for the request ID 1460207635 in the file:
View monitoring request parameters for Request ID, 1709703185:
List resources instances available for monitoring in the /samples
resource instance:
DEPENDENCIES
Event Monitoring Service (EMS) must be installed. You must be a supe‐
ruser.
AUTHOR
was developed by HP.
FILES
Refer to EMS Directories and Files section in the ems(5) manpage.
SEE ALSOresls(1), ems(5).
emscli(1M)
