Hitachi

JP1 Version 12 JP1/Performance Management User's Guide


6.9.2 Notes on the relationship between alarm damping and the issuing of alarm events

Note

The cases in this example assume that a multi-instance record is used to create an alarm. A multi-instance record is a record consisting of multiple instances collected at the same time. For example, assume a multi-instance record that checks the status of disk A and disk B. During alarm evaluation, the status of the disks is evaluated for alarms, and if either (or both) of the disks meets an alarm condition, an alarm is issued for each disk.

Organization of this subsection

(1) When the alarm damping is n/n (n=n)

The relationship between alarm damping and the issuing of alarm events depends on the combination of the Always notify and Evaluate all data settings in the Advanced settings area of the New Alarm > Main information or Edit > Main Information window. The following table lists the section in this manual that describes relationship for each combination of settings.

Evaluate all data

Always notify

Cleared

Selected

Cleared

6.9.2(1)(a)

6.9.2(1)(b)

Selected

6.9.2(1)(c)

6.9.2(1)(d)

In the cases described below, the check box names are referred to as follows:

(a) When the alarm damping is n/n (n=n) (Always is cleared and All is cleared)

If Always and All are both cleared, the following occurs:

  • An alarm is issued when a threshold is exceeded n times in n evaluations.

  • The alarm is reported only when the status of the alarm changes from the previously reported status.

  • Among the instances that were collected at the time of reporting the alarm, the alarm status of the instance that indicates the highest severity is reported.

This functionality is illustrated by the following examples:

[Figure]

(b) When the alarm damping is n/n (n=n) (Always is selected and All is cleared)

If Always is selected and All is cleared, the following occurs:

  • An alarm is issued when a threshold is exceeded n times in n evaluations. You can use this to control the frequency of the alarm.

  • The instance that indicates the highest severity at the time of reporting the alarm is reported.

This functionality is illustrated by the following examples:

[Figure]

(c) When the alarm damping is n/n (n=n) (Always is cleared and All is selected)

If Always is cleared and All is selected, the following occurs:

  • An alarm is issued when a threshold is exceeded n times in n evaluations.

  • The alarm is reported only when the status of the alarm changes from the previously reported status.

  • If the status is Warning or Abnormal, the alarm statuses of all the instances that meet the status condition at the time of reporting the alarm are reported.

This functionality is illustrated by the following examples:

[Figure]

(d) When the alarm damping is n/n (n=n) (Always is selected and All is selected)

If Always and All are both selected, the following occurs:

  • An alarm is issued when a threshold is exceeded n times in n evaluations. You can use this to control the frequency of the alarm.

  • All of the instances that meet the Warning or Abnormal condition at the time of reporting the alarm are reported.

This functionality is illustrated by the following examples:

[Figure]

(2) When the alarm damping is n/m (n<m)

The relationship between alarm damping and the issuing of alarm events depends on the combination of the Always notify and Evaluate all data settings in the Advanced settings area of the New Alarm > Main Information or Edit > Main Information window. The following table lists the section in this manual that describes relationship for each combination of settings.

Evaluate all data

Always notify

Cleared

Selected

Cleared

6.9.2(2)(a)

6.9.2(2)(b)

Selected

6.9.2(2)(c)

6.9.2(2)(d)

In the cases described below, the check box names are referred to as follows:

(a) When the alarm damping is n/m (n<m) (Always is cleared and All is cleared)

If Always and All are both cleared, the following occurs:

  • You can specify whether the alarm status changes when a threshold is exceeded n times in m evaluations.

  • The alarm is reported only when the status of the alarm changes from the previously reported status.

  • Among the instances that were collected at the time of reporting the alarm, the alarm status of the instance that indicates the highest severity is reported.

This functionality is illustrated by the following examples:

[Figure]

(b) When the alarm damping is n/m (n<m) (Always is selected and All is cleared)

If Always is selected and All is cleared, the following occurs:

  • You can specify whether an alarm is reported when a threshold is exceeded n times in m evaluations. You can use this to control the frequency of the alarm.

  • The instance that indicates the highest severity at the time of reporting the alarm is reported.

This functionality is illustrated by the following examples:

[Figure]

(c) When the alarm damping is n/m (n<m) (Always is cleared and All is selected)

If Always is cleared and All is selected, the following occurs:

  • You can specify whether the alarm status changes when a threshold is exceeded n times in m evaluations.

  • The alarm is reported only when the status of the alarm changes from the previously reported status.

  • If the status is Warning or Abnormal, the alarm statuses of all the instances that meet the status condition at the time of reporting the alarm are reported.

This functionality is illustrated by the following examples:

[Figure]

(d) When the alarm damping is n/m (n<m) (Always is selected and All is selected)

If Always and All are both selected, the following occurs:

  • You can specify whether an alarm is reported when a threshold is exceeded n times in m evaluations. You can use this to control the frequency of the alarm.

  • All of the instances that meet the Warning or Abnormal condition at the time of reporting the alarm are reported.

This functionality is illustrated by the following examples:

[Figure]