- HP OpenView Event Correlation Services engine manager
ecsmgr [-instance instance] [-stream sname] option
ecsmgr is the HP OpenView Event Correlation Services (ECS) correlation engine manager. ecsmgr can be used to alter the correlation engine's configuration when it is running.
Only the superuser can use the ecsmgr command.
Sections labelled "pmd" are only applicable when running the event correlation engine in a DM or NNM environment.
The following option is used to identify the target correlation engine:
-instanceinstance
The default for this option is -instance 1
pmd: The pmd-linked correlation engine is always instance 1.
The following option can be used to specify an event stream:
-stream sname
-policy, -enable, and -disableoptions to affect the snamestream. For backward compatibility, if the -stream option is omitted, the default stream is affected.
Except for the default stream (which is automatically created at engine startup), the stream must have been previously created with the create_stream option.
The following options specify the action to perform on the target correlation engine. Only one of these options may be specified on the command line:
-auto_save_config [on|off]
ecsmgr) to the default startup configuration file (Unix: $OV_CONF/ecs/instance/config, Windows NT: %OV_CONF%\ecs\instance\config). This effectively makes the engine's configuration persistent across invocations.
This command implicitly saves the engine's configuration (to the default startup file), as the setting of this option is always made persistent.
The engine is automatically restored to the default startup configuration on startup (regardless of the setting of this option). See also -save_config and -restore_config.
-circuit_load cname file [dsname] [fsname]
cname must uniquely identify the ECS circuit in the target engine.
file must specify the name of a compiled ECS circuit file. See the ecsdes reference page for information about creating circuit files.
dsnamemust specify the name of a data store previously loaded with -data_load.
fsnamemust specify the name of a fact store previously loaded with -fact_load. If no data store was named, a zero (0) must be used in its place so that fsname will be interpreted as the name of the fact store.
-circuit_reload cname
cname with the circuit file that it was originally loaded from. Any data or fact stores associated with the circuit are not modified.
A circuit cannot be reloaded if its input or output is enabled in any stream.
-circuit_unload cname
cname from the correlation engine.
A circuit cannot be unloaded if its input or output is enabled in any stream.
-create_stream sname [output|discard]
sname in the correlation engine with the specified policy. If a policy is not specified, the policy defaults to output.
See policyfor more information about stream policy.
-data_dump dsname file
dsname to file.
-data_load dsname file
file into the data store dsname. This command will fail if a data store named dsname already exists.
-data_unload dsname
dsnameunless the data store is currently being used by a circuit.
-data_update dsname file
dsnameusing the contents of file.
-disable cname [input | output]
cname. This option affects the default stream unless the -stream option is also specified.
The input or output of the circuit can be disabled separately using the optional keywords input or output. If neither are specified, then both the input and output are disabled together. See enable for more information.
When the output of a circuit into a stream is disabled, the events within the circuit are flushed into that stream (subject to stream policy), but the circuit itself and the other streams are unaffected.
This option takes effect immediately
-enable cname [input | output]
cname. This option affects the default stream unless the -stream option is also specified (see -policy for more information about how circuits affect events in a stream). The same loaded circuit can be enabled in more than one stream.
Events will never enter the circuit more than once, regardless of how many streams in which the circuit is enabled for event input. In other words, a circuit will still receive events until its input has been disabled in every stream.
This option takes effect immediately.
-fact_dump fsname file
fsname to file.
-fact_load fsname file
file into the fact store fsname. This command will fail if a fact store named fsnamealready exists.
-fact_unload fsname
fsname unless the fact store is currently being used by a circuit.
-fact_updatefsname file
fsname using the contents of file.
-h
ecsmgr usage message.
-info
Engine Status:
Stream Status:
Circuit Status:
-licinfo
-logbitmap
A standalone correlation engine writes log information to ecs.log* provided the engine log mask is set.
pmd: A correlation engine linked to the HP OpenView pmd writes log information to the postmaster log file provided both the engine log mask and the pmd logging and tracing mask for the correlation engine sub-stack are set.
The bits in the correlation engine log mask have the following meanings:
DISASTERS(0x1)
ERRORS(0x2)
WARNINGS(0x4)
INFORM(0x8)
The default setting of the correlation engine log mask is 0x7. To create a mask that is a combination of the bits that are listed above, you add the bits together which effectively ORs the bits. The result is then used as the argument to the -log option.
pmd: The default setting of the HP OpenView pmd logging and tracing mask for the correlation engine sub-stack is 0x00400007. See the pmdmgr(1M) reference page for information about postmaster tracing and logging and on setting the postmaster logging and tracing mask for sub-stacks.
See theecslogmsg(5) reference page for an explanation of the meaning of correlation engine log messages.
-log_events input [on|off]
ecsin.evt0. Annotation responses are also logged in this file.
-log_events stream [sname] [on|off]
The output events are logged to sname_sout.evt0, and the discarded events are logged to sname_sdis.evt0 (where sname is the stream name).
-log_events policy [sname] [on|off]
-policy). If the optional stream name is omitted, the default stream is assumed.
The output events are logged to sname_pout.evt0, and the discarded events are logged to sname_pdis.evt0 (where sname is the stream name).
-log_events circuit cname [on|off]
The output events are logged to cname_cout.evt0, and the discarded events are logged to cname_cdis.evt0 (where cname is the circuit name).
-max_log_size [engine|event] size
.evt1 extension. Any old .evt1 file is overwritten. New log entries continue to be written to the .evt0 file. Where engine is specified the engine log and trace files are affected. Where event is specified all event log files are affected. Upon startup the engine sets the parameter to a default of 512 kilobytes for both event and engine logging.
-merge_config [configfile]
configfile is not specified, the contents of that engine's default configuration file are used.
If -auto_save_config is on, the result of the merge is stored in the default configuration file.
-policy [output|discard]
-stream is specified. The default stream has an initial policy of output when the engine is started.
In particular, stream policy affects events which do not enter any circuit within the stream, or enter an output-disabled circuit within the stream, or are present within a circuit when it becomes disabled in the stream. With a discard policy these events are discarded by the stream, but with an output policy these events are output by the stream.
Furthermore, this affects events which are correlated by more than one circuit in the same stream. With an output policy, events are output from the stream unless they are discarded by any circuit. With a discard policy, events are discarded by the stream unless they are output by any circuit.
Caution: Most circuits must be designed with a particular policy in mind, and running them with the wrong policy may cause unexpected output behavior. See the HP OpenView ECS Designer's Guide for details.
-remove_stream sname
-reset
pmd: Caution: Owing to the way dynamically linked libraries are implemented in some operating systems, using the ecsmgr -reset command causes the pmd image in memory to grow. Avoid repeated use of this command in normal operations.
-restore_config [configfile]
configfile if specified or from the default startup configuration file (Unix: $OV_CONF/ecs/instance/config, Windows NT: %OV_CONF%\ecs\instance\config) otherwise. This command implicitly resets the engine (see reset) first.
-save_ config [configfile]
$OV_CONF/ecs/instance/config, Windows NT: %OV_CONF%\ecs\instance\config) otherwise.
The engine is automatically restored to the default startup configuration on startup. See also -restore_config and -auto_save_config.
-shutdown
ecsd), and only when no circuits are enabled. To ensure that the shutdown succeeds, reset the engine prior to shutting it down.
-snapshot file
file. The snapshot contains detailed information regarding the structure of all loaded circuits and the contents of any fact or data stores that are loaded.
-stats [verbose]
If the verboseoption is specified, additional circuit node statistics are displayed which can be helpful to a circuit designer.
-stream sname
-stream at the start of this page.
-trace bitmap
A standalone correlation engine writes trace information to ecs.trc* provided the engine trace mask is set.
pmd: An engine linked to the HP OpenView pmd writes trace information to the postmaster trace file provided both the engine trace mask and the pmdlogging and tracing mask for the correlation engine sub-stack are set.
Correlation engine trace output provides very detailed information about the loading and operation of ECS circuits. The bits in the engine trace mask have the following meanings:
The default setting of the correlation engine trace mask is 0x0. To create a mask that is a combination of the bits that are listed above, you add the bits together which effectively ORs the bits. The result is then used as the argument to the -trace option.
pmd: The default setting of the HP OpenView pmd logging and tracing mask for the correlation engine sub-stack is 0x00400007. See the pmdmgr(1M) reference page for information about postmaster tracing and logging and on setting the postmaster logging and tracing mask for sub-stacks.
-updatecname file
cnamewith the fact store or data store updates in file. The update file can contain updates for the fact store or the data store, or both.
ecsmgr returns one of the following values:
0 Success
1 Invalid ecsmgr option
2 Requested operation failed
3 Parsing of the ecsmgr command failed
4 API failure
5 Cannot execute ecsmgr - must be superuser
130 Interrupt received
Examples of howecsmgrcan be used:
To enable event correlation in the circuit named ecsmgr -enable circuitnamecircuitname:
To set the logging level to DISASTERS and ERRORS messages only:
ecsmgr -log 0x3
ecsmgr outputs a diagnostic message if a command fails. Further diagnostic information can be found in the correlation engine log and trace files.
The environment variables below represent universal pathnames that are established according to your shell and platform requirements. See the ovenvvars(1) reference page for information on universal pathnames for your platform and shell. For Windows NT platforms, substitute the environment variables in Windows NT format. For example, substitute $OV_LOG with %OV_LOG%.
$OV_CONF/ecs/instance/config
instancethat is restored by the engine on startup.
$OV_LOG/ecs/instance/ecsd.log*
instance.
pmd: Engine log output is written to the HP OpenView postmaster log file ($OV_LOG/pmd.log*)
$OV_LOG/ecs/instance/ecsd.trc*
instance.
pmd: Engine trace output is written to the HP OpenView postmaster trace file ($OV_LOG/pmd.trc*)
$OV_LOG/ecs/instance/ecsd.stderr
$OV_LOG/ecs/instance/ecsin.evt*
instance.
$OV_LOG/ecs/instance/sname_sout.evt*
sname in engine instance instance.
$OV_LOG/ecs/instance/sname_sdis.evt*
sname in engine instance instance.
$OV_LOG/ecs/instance/cname_cout.evt*
cname in engine instance instance.
$OV_LOG/ecs/instance/cname_cdis.evt*
cname in engine instance instance.
$OV_LOG/ecs/instance/sname_pout.evt*
sname in engine instance instance.
$OV_LOG/ecs/instance/sname_pdis.evt*
sname in engine instance instance.
ecsmgrwas developed by Hewlett-Packard.
ecsdes
ecsd
ecslogmsg(5), ovstart(1M),ovstop(1M),ovstatus(1M),pmdmgr(1M)