Conference azur::mcc

    
    hi Barbara,
    
    ANY EVENTS in the EVENT argument of NOTIFY means "all" the event
    partitions that an entity supports.  AT this time there are two event
    partitions:  configuration and notification.  For example, ANY EVENTS 
    means ANY NOTIF EVENT and ANY CONFIG EVENT for DOMAIN RULES; for an
    entity that only supports the CONFIG partition such as NODE4, ANY EVENTS 
    means ANY CONFIG EVENT.
    
    Regarding your question about the two different methods for creating
    rules - they are basically the same.  Some of the attribute names are
    different, and rules created using the MCC 0 ALARM RULE syntax without
    the IN DOMAIN specified are not retrievable from the DOMAIN RULE
    syntax.
    
    Hope this makes sense.  
    
    -s

	Hello,

	and thank you for your reply.


	But now I have another problem:

	what does you mean "notification event" and "configuration event"?


	I've read tha manual and it says, as I've  understand:

	- Notification events - The primary events are alarms. Alarms are
	  generated whenever an alarm rule fires, clears, or produces an
	  errors....
	  (So I can suppose that I can notify an alarms fires on any entity).

	- Configuration events. These events are reported automatically by 
	  an entity or a management module
	  (An example is decnet event)

	When you says that a NODE4 supports only CONFIG partition I'm
	not completely sure.
	In fact a node4 can send event message (decnet event as like
	circuit up) and I can write a alarm rule on statistics and on the
	other partitions.

	Can you tell me an example of notification event / configuration
	events and any events ? 


	Thank you again for your help,

					from a doubtful	Barbara

    Hi Barbara,
    
    I think this is how the theory goes ... in practice, a configuration
    event is what happens at the entity - things that happen on the netowrk
    that need to be responded to - for example, circuit down, circuit up
    from a phase IV or phase V node.
    
    Notification events are 2nd order events - "value added" - generated in
    MCC for MCC often in response to configuration events.  For example,
    when a DOMAIN RULE OCCURS rule fires, it generates a NOTIFICATION
    event.
    
    An example ...
    
    	NODE4 * CIRCUIT * ADJ NODE * generates CONFIGURATION events
    	 - Adjacency up
    	 - Adjacency Down
    	 - Circuit Down Circuit Fault
    	 - ... etc.
    
    	DOMAIN d1 RULE anode-watch EXP=
    		(OCCURS(NODE4 * CIRC * ADJ NODE * ANY CONFIG EVENT))
    	
    	is an OCCURS rule that listens for CONFIGURATION EVENTS.
    
    	when this rule fires, it will generate a NOTIFICATION event.
    
    Hope this makes some sense!
    
    -s

    
    p.s.
    
    ANY EVENTS...
    
    If i have DOMAIN d1 that has NODE4 entities in it, and DOMAIN RULES
    defined and make the request :
    	
    	mcc> NOTIFY DOMAIN d1 EVENT=(ANY EVENTS)
    
    In this example ANY EVENTS implies ANY CONFIGURATION EVENTS and 
    ANY NOTIFICATION EVENTS because the domain contains entities that 
    generate both types of events.
    
    DOMAIN RULES generate both CONFIGURATION EVENTS and NOTIFICATION
    EVENTS.  A rule generates CONFIG events when it is created, deleted,
    enabled or disabled - these events are about the DOMAIN RULE entity
    itself.  When a RULE fires, it generates a NOTIFICATION event.
    
    A DOMAIN RULE can also look for notification events:
    
    	DOMAIN d1 RULE rule-watch exp=(
    		(OCCURS( domain d1 rule * ANY NOTIF EVENT))
    
    This rule will fire whenever a rule in domain d1 fires.  This rule
    doesn't have alot of meaning, but it is used for illustration.
    
    The request NOTIFY DOMAIN d1 without any ARGUMENTS will return only 
    NOTIFICATION events - this is the default.

	Hi,


	and many thank for your info!!!


	Now I'll do some proofs....


					Barbara