| RE: .0
> For alarm rule format 3, sub-entity wildcarding is NOT valid.
> Example:
> EXPRESSION = (change_of(node4 aeo467 circuit * substate, none, *), AT
> every 01:00:00)
> doesn't work.
>
> For alarm rule format 4, sub-entity wildcarding is valid.
> Example:
> EXPRESSION = (occurs (node4 aeo467 line * counters zeroed))
> does work.
>
>
> Is it correct ?
Yes this is correct
> Is it true for all global entity classes ?
Provided that the MM knows how to handle Child Wildcards, then these
rules should work every time.
> When an alarm fmt2/fmt4 fires, how does it notify the user of the actual
> sub-entity instance which fires ?
The Information record returned from Alarms contains the 'Output Entity';
the entity which the MM returned to Alarms. This contains the actual
entity processed by Alarms.
If you use the Notify command:
Notify Domain <domain-name>
You will will see the Evidence record when the Rule fires. This output
is actually some advanced development of Global Wildcards:
------------------------
Event Type = QualityofServiceAlarm
Event Time = 21-FEB-1992 07:27:37.42
Probable Cause = DegradedSignal
Additional Info = { (
significance = True,
information = "Rule fired: Sample ETHRFX_NS:.neenee User Bytes
Sent = 2231166 21-FEB-1992 07:27:37.41" ),
(
significance = True,
information = "(sample * user byte sent > 50)" ) }
Managed Object = Sample ETHRFX_NS:.neenee
Perceived Severity = Indeterminate
-------------------------
The expression is: (sample * user bytes sent > 50)
The managed object is: Sample ETHRFX_NS:.neenee
Hope this helps.
/keith
|