TRAP generation rules

Provides a brief overview of trap generation rules. If Tivoli Netcool Performance Manager is configured to generate traps, trap generation input to a specific threshold occur when there is a change in the violation state.

• burst, period (and proactive) thresholds

  Non-Violation <-> Warning Violation <-> Critical Violation

• baseline thresholds

  Non-Violation <-> Violation

The traps generated reflect the nature of the state transition. For example, when the system goes from burst non-violation to burst Warning violation for a particular m/g/r-threshold; a provisoCMEWarningViolationBurstThr (see proviso.mib) is generated.

The example illustrated in Resource in two groups example shows resource R1 as a member of two groups. A threshold is deployed against the m/g/r combinations that result from that group membership. Therefore, it is possible for multiple traps to be generated (one for each m/g/r combination) when a single metric value is processed.