Conference azur::mcc

A little more info,

These commands fail:
GETEVENT MCC 0 ALARMS RULE * ANY EVENT,in domain .xxx
GETEVENT MCC 0 ALARMS RULE * OSI RULE CLEAR,in domain .xxx

These commands are ok:
GETEVENT MCC 0 ALARMS RULE * OSI RULE FIRED,in domain .xxx
GETEVENT MCC 0 ALARMS RULE * OSI RULE EXCEPTION,in domain .xxx

But as indicated in base note I am really looking for OSI RULE CLEAR
functions.

brad/

Brad .. I just tried what I think you wanted to do.  Here is the output.
Is that what you are seeing too ?  In any case .. I am running the pre-SSB
kit and Alarms is not working correctly .. 8(

/keith

	NANOVX-S> man/ent
	DECmcc (X1.2.21)

	MCC> getevent mcc 0 alarms rule *
	  Type ? for a list of valid event IDs
	Event: ?
	    Rule Created
	    Rule Deleted
	    Rule Enabled
	    Rule Disabled
	    OSI Rule Fired
	    OSI Rule Exception
	    OSI Rule Disabled
	    OSI Rule Clear
	    Any Events
	Event: OSI Rule Clear
	
	MCC 0 ALARMS RULE *
	AT  3-JUN-1992 12:23:11 NOTIFICATION EVENTS
	
	An unrecognized argument, code = 37 was included in the request
	             Unrecognized Argument Code = 37

>	An unrecognized argument, code = 37 was included in the request
>	             Unrecognized Argument Code = 37

That's the one. I ditto your :(. Will it be worked on (fixed) for SSB???
I could really use this one for a pseudo change_of function. I guess I should
explain a bit.

Currently V1.2 does not support change_of wildcards and therefore I don't use
it because of general rule wildcarding support. With the new wildcarding of

expression=(node4 * circ * substate <> none)

I've got zero maintenance (a huge win I won't give up). But what I've done
is taken the fired rules and write them into status logs which is dependent
on the timestamp. To make a long story short I use the entries in these log 
files to control certain actions for long outages. For example, I only send 
mail the first time I see a circuit go down if the outage is contiguous. This 
gives me a pseudo change_of fuction when a circuit transitions from UP to DOWN.

Using the OSI RULE CLEARED would give me the other half of change_of function.
That is, the transition from DOWN to UP would be easily detected if all works
the way I think it would and it finishes the picture. Hopefully someone will
have the time to fix this.

kind regards,
brad... 

  Brad,

  The error you are getting (code=37 ...) was found and fixed in the 'other'
  Alarms interface (Domain/Rule).  It just wasn't found/fixed in the 
  MCC/Alarms/Rule interface 8(

  I was going to suggest that you use the other interface; that is:

	getevent domain <d> rule <r> osi rule clear

  But I just found that that interface doesn't even describe osi rule clear !
  So I guess that idea is dead.  I'll QAR both of these problems (if they 
  haven't been already).

  No workaround that I can think of.  You'll have to wait another few days
  (a week?) for the SSB kit.

  /keith

>  No workaround that I can think of.  You'll have to wait another few days
>  (a week?) for the SSB kit.

No problem waiting considering the fix is in this version.

thanks,
brad...

Okay, let me clarify a few things. There is no "OSI RULE CLEAR" event
in the v1.2 alarms module.  The implementation instead returns 
a "OSI RULE FIRED" event with a severity of cleared. The clear
events in the .MS files are vestiges of the v1.1 implementation.

As to why this has changed, well that person no longer works for
the company, so the complete reasoning will not be known. There
were limitations in the initial field test kit of the alarms 
module such that it couldn't handle supplying a notification id
to tie together two different events, so they were instead made into
a single evnt with two different severities and the coorelation left
for the notiication services modules.

As to what we are going to do, we have removed the clear events from
the .MS files so that they will no longer confuse users, but the user
of the osi rule fired with a severity of clear will remain for this
release.

I hope that this clarifies things for you.

jill