EMS Manual

Burst Detection and Suppression
EMS Manual—426909-005
7-7
Implementing BDS From a Distributor
Programs. If you use EMSACOLL SUPPRESS to enable BDS, you cannot use the
EMSACOLL FILTER option.

When the alternate collector is first started, use the FILTER keyword of the
EMSACOLL command to add a burst filter that contains the BDS directives. If you
use the EMSACOLL FILTER option to load a burst filter to enable BDS, you cannot
use the EMSACOLL SUPPRESS option.

After the alternate collector is running, use the SUPPRESS keyword of
EMSCCTRL to specify BDS directives.

If the EMSCCTRL SUPPRESS function has not been specified, use the
EMSCCTRL FILTER command to specify a burst filter that contains the BDS
directives. (This command enables PLF.)

While the alternate collector is running, invoke a program that uses the SPI
interface to modify the filter criteria (for example, a program that contains an ADD
command with the burst filter as its object).
Implementing BDS From a Distributor
You can configure and enable BDS in a distributor using one of these methods:

When the distributor is first started, use the FILTER keyword of the EMSDIST
program to load a burst filter into that distributor.

While the distributor is running, invoke a program that uses the SPI interface to
modify the filter criteria (for example, a program that contains an ADD command
with the burst filter as its object).
Implementing Specific-Event Suppression
Using TACL, specific-event suppression can be configured and enabled using a
number of methods. Specific-event suppression causes all occurrences of specific
event messages that are received by the collector or distributor to be suppressed.
Specific-event suppression can be configured and implemented only by means of a
filter table or a compiled filter that identifies the event type to be suppressed and that is
added to the collector or distributor process.
Caution. Use caution when using compiled filters or filter tables to totally suppress events that
are generated by subsystems specific to the NonStop server because many of these events
are monitored by HP and other applications. Total event suppression can result in state
information from a particular subsystems for the NonStop server being discarded and
becoming nonretrievable. Because events from subsystems subsystems specific to the
NonStop server are almost always sent to the primary collector ($0), you must use discretion in
using such filters in the primary collector when the suppressed event information might be of
value to the user.