Information

This site will undergo a brief period of maintenance on Friday, 18 December at 12:30 AM Central/12:00 PM IST. During a 30 minute window, site availability may be intermittent.

Filling out the Use These Conditions dialog box


(BMC.AMIOPS.SPE2210)

On this dialog box, specify the conditions that are used to report alarms with specific severity levels.


Use_These_Conditions_dialog.png

  1. Accept the default values or specify alternate values.
    The fields in the dialog box are described in the following table.
  2. Click Next to continue to the next step in the MAKEALARM wizard (Filling-out-the-Report-Alarms-dialog-box).

Field descriptions for the Use These Conditions dialog box

Field

Default value

Information to specify

Persistence

Define alarm definitions that require one or more conditions to be true for more than one sample

Persistence requires that an alarm condition be true for n of m samples. The Samples value specifies m in the expression n of m.

Samples=m

1

Number of time samples

The maximum sample size is 32.

Info=n

Warn=n

Minor=n

Major=n

Critical=n

1

Value for each severity level

The value of n must be greater than 0 and less than or equal to the m (Samples) value.

Conditions for severities are evaluated from highest to lowest. The evaluation stops when a condition is true. All the lower level severities are assumed to be true. If Warn is true, Info is true, and if Critical is true, Major, Minor, Warn, and Info are considered true.

If you want an alarm to be reported whenever a condition is true, you would specify sample size 1 and 1 for each severity persistence value.

Information
Example

Consider a Samples value = 5 with the following severity persistence values:

  • Info = 5
  • Warn = 4
  • Minor = 3
  • Major = 2
  • Critical = 1

Then, on successive evaluations the following severities are evaluated:

Warn, Warn, Warn, Minor, Major, Minor
On the fourth evaluation, a Warn alarm condition is reported, and on the sixth evaluation, a Minor alarm condition is reported.

Conditions/Thresholds

Specify the conditions that must be true for each severity of an alarm definition

Report if corresponding conditions are true for [ALL|ANY] elements

ALL

Specify the conditions that must be true for each severity of an alarm definition

  • ALL means that the condition for a severity is true if the corresponding severity conditions are true for ALL the elements.
  • ANY means that the condition for a severity is true if any one of the corresponding conditions is true.

If the alarm definition is based on one element, then ALL or ANY have the same meaning. If a condition for a severity is specified for one element and not another element. The empty specification is ignored regardless of the specification of ALL or ANY.

Element Severity Conditions

No default

The alarm definition can be based on one or more elements from the view. This section repeats for each element.

For each element, you can specify a different operator and value for each of the following levels of severity:

  • Info
  • Warn
  • Minor
  • Major
  • Critical

The initial conditions for each severity are determined from the view. The threshold conditions are taken from the view in order. The first threshold condition for the field becomes the critical condition, the second major and so on, down to Info.

In the example above the is elementName is CPUSUs/Sec(MVDCPRT). You can remove the condition for the element by typing D in the field next to the element name.

Use Dynamic Threshold

YES

Indicate whether the alarm definition should make use of dynamic thresholds, if any are defined for the specified elements.

  • YES means any dynamic thresholds that are defined for an element take precedence.
  • NO means that thresholds that are specified in the alarm definition take effect only when no dynamic threshold is active.

To use only dynamic thresholds for an alarm, accept the default of YES and do not specify any conditions for any of the element’s severity levels.

For information about dynamic thresholds, seeWorking with dynamic thresholds on the mainframe.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC AMI Ops User Interface 2.0