send_test_event(1m)send_test_event(1m)NAME
send_test_event- Test event tool
SYNOPSIS
monitor_name
DESCRIPTION
The command is used to cause a monitor to generate one or more test
events.
Only those monitors which support the functionality of sending test
events will respond to this command. Monitors that support this func‐
tionality should be revision B.01.00 or higher.
NOTE: The event will only be generated out of EMS if a monitoring
request is active for that monitor on that resource. Therefore, to use
this mechanism to test the communication path after installation, the
caller must ensure that initial configuration has completed and the
appropriate monitoring requests are registered. This can be done via
the monconfig (Check monitoring) command or via EMS Client API calls.
Options
send_test_event recognizes the following command-line options:
Use verbose mode. Displays messages indicating the steps per‐
formed to
cause the monitor to generate a test event.
Cause the monitor to send a test event on each resource name
associated with
the monitor. If this flag is not set, only the
first resource name found will be used to gener‐
ate a test event.
The name of the monitor that should generate one or more test
events. NOTE:
this name is the name of the binary and is not
fully qualified.
EXIT VALUES
The request was successful.
The monitor name was not recognized. There was no matching
*.sapcfg file
with that monitor name.
The request failed for some unexpected reason.
EXAMPLES
Have the disk monitor send a test event for each resource
/etc/opt/resmon/lbin/send_test_event -a disk_em
Have the tape monitor send only one test event for first resource
/etc/opt/resmon/lbin/send_test_event dm_stape
AUTHOR
was developed by HP.
FILES
DEPENDENCIES
will only work for those monitors which are version B.01.00 or
higher, meaning they support the functionality of sending a test
event. It will also only recognize those monitors which have a
*.sapcfg file.
SEE ALSOems(5), monconfig(1m)send_test_event(1m)
