Conference azur::mcc

RE: .0

>I have an alarm rule with an expression and a wildcard, something like:
>	PABX * PTT Cost > 10
>
>When you have the following values:
>	PABX 1 PTT Cost = 5
>	PABX 2 PTT Cost = 11
>	PABX 3 PTT Cost = 2
>	PABX 4 PTT Cost = 0
>

  Henk van Steeg.

  (Q) Which version of DECmcc are you using ?

  It appears that you have specified a Global Wildcard in your Rule
  Expression:  (PABX * PTT Cost > 10)

  Alarms Global Wildcards support was added to baselevel x1.2.18 ... if
  you are not using this baselevel, I do not know how you could have gotten
  this Rule to work at all.

  (Q) Could you show me the exact command you used to create the Rule ?

  (Q) Could you explain what you mean by:

>     When I started the alarm rule I got the following:
>	  PABX 2 -> MINOR alarm       ----> Good
>	  PABX 3 -> CLEAR alarm       ----> Not good, but why ??

  Thanks,

  Keith

Hi Keith,  

Thanks for your response.

>(Q) Which version of DECmcc are you using ?

I am using DECmcc T1.2.15

>  (Q) Could you show me the exact command you used to create the Rule ?

I created the rule with the IMPM:
     Comparison rule:
	Severity = Minor
	Description = Phoned to much
	Polling Interval = 00:02:00
	Entity = pabx .tc_uto pabx_accounting extension *
	Attribute Name = PTT Metering Cost
	Relational Operator = GT
	Comparison Value = 1.00

> (Q) Could you explain what you mean by:
>
>>     When I started the alarm rule I got the following:
>>	  PABX 2 -> MINOR alarm       ----> Good
>>	  PABX 3 -> CLEAR alarm       ----> Not good, but why ??

This was an (simple) example of what I got.
- The attribute value of PABX 2 was to high so there must be a minor alarm
- The attribute value of PABX 3 was not to high and had never been to high, 
	why I get that clear alarm ? ? ?


I think this is a bug in the Alarms FM, 
because first it looks at PABX 1 and the value is not to high, 
then it looks at PABX 2 and the value is to high so an alarm, 
then it looks at PABX 3 and the value is NOT to high now it gives a clear 
alarm because the last value was an alarm.


Regards		Henk.

RE: .2

  Henk,

  You are using a child wildcard !! (not a global wildcard as I had thought).

> Entity = pabx .tc_uto pabx_accounting extension *

  Alarms keeps track of rule transitions, that is .. how did the rule fire
  this time vs. how it fired last time.

> - The attribute value of PABX 2 was to high so there must be a minor alarm
> - The attribute value of PABX 3 was not to high and had never been to high, 

  This logic used only a signle `bit'.  Because PABX 2 fired true, followed
  by PABX 3 fireing False, the transitions was from True to False, thus
  you got a Clear Event ... the fact that the entities were different was
  not taken into account  8(

  Since adding support for global wildcards, the rule transition logic is
  now based on an Entity and the Rule Transition.  So, the problem you are
  seeing has been fixed in baselevel x1.2.18, and thus will be fixed in the
  Field Test Update (about to happen any time now).

  Hope I explained this - let me know if I haven't.

  /keith

Hi

Keith, thank you very much for your clear explanation

Regards		Henk.