EMS Manual

Burst Detection and Suppression
EMS Manual426909-005
7-3
BDS Parameters
see repetitive events, either disable BDS or alter the BDS parameters so they do not
suppress the expected repetitive events.
BDS users should first create burst filters that enable burst detection in one or more of
your EMS distributors. This prevents redundant events from reaching destination
processes and devices while still making the events available to the EMS log files
(events are discarded and eliminated from the system when BDS is applied to an EMS
collector).
When you are comfortable with the burst configuration parameter options and the
overall function of BDS, you might choose to move burst detection to your collectors
(especially alternate collectors) to prevent the logging of repetitive events altogether.
The BDS algorithm is an enhanced version of the BDS facility available in all EMS
distributors and collectors.
BDS Parameters
Six parameters control the behavior of BDS in EMS collectors and distributors: N, T1,
T2, T3, L, and S. You can implement BDS parameters when:
Starting an alternate collector, use the SUPPRESS keyword parameters in the
RUN EMSACOLL command.
Starting an alternate collector, use the FILTER keyword parameters in the RUN
EMSACOLL command to load a burst filter that contains the BDS parameters.
Configuring a running primary or alternate collector, use the SUPPRESS keyword
parameters of the EMSCCTRL program.
Configuring a running primary or alternate collector, use the FILTER keyword
parameters of the EMSACOLL command to load a burst filter that contains the
BDS parameters.
Starting a distributor, use the FILTER keyword parameters in the EMSDIST
program to load a burst filter that contains the BDS parameters.
Or create a program that uses the SPI interface to ADD or DELETE a burst filter.
For a detailed description of the methods used to configure and enable BDS in
collectors and distributors, see Implementing BDS on page 7-6.
Two or more EMS events are considered similar if they:
Originate from the same subsystem (that is, have the same SSID)
Possess the same event number
Possess the same token code for their first event subject