[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

Title:DECmcc user notes file. Does not replace IPMT.
Notice:Use IPMT for problems. Newsletter location in note 6187
Moderator:TAEC::BEROUD
Created:Mon Aug 21 1989
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6497
Total number of notes:27359

3668.0. "TARGETTING ACROSS DOMAINS" by KAOA00::63492::SLEE () Tue Sep 01 1992 21:45

Correct me if I'm wrong, but, it seems you cannot target a notification
from one entity in a domain to different entity in another domain.

Why is this so? Will it ever be made possible?

I have domains setup to represent DEC facilities. I also have domains (within
the same map) setup to represent aggregate circuits between the facilities.

The domains representing the aggregate circuits contain all the individual 
circuit entities.

I have alarms setup in some of the facility domains for detecting circuit
down/up conditions on node4 routers since these routers reside in their
respective facility domains.

Now one of the circuit entities in a given circuit domain represents the 
circuit connected to one of these node4 routers.

eg.	domain C_ABC		domain CALGARY
	
	contains circuit	contains node4 entity CGOR01,
	entity CCT_xyz		and rule CGOR01_SYN1_DWN
	

What I was hoping to achieve was to have the alarm CGOR01_SYN1_DWN fire,
and with a notify request for circuit CCT_xyz in domain C_ABC and a targetting
assignment in domain C_ABC pointing to CCT_xyz, generate the icon notification
on circuit entity CCT_xyz in domain C_ABC.

Hope I made myself clear.

/Steve
T.RTitleUserPersonal
Name
DateLines
3668.1notify requests, domains, etc.MCC1::DITMARSPeteWed Sep 02 1992 13:4560
>Correct me if I'm wrong, but, it seems you cannot target a notification
>from one entity in a domain to different entity in another domain.
>
>Why is this so? Will it ever be made possible?

You're mostly correct.

Targeting does not include a "target domain" argument, so by simply using
targeting you can't change the domain of a notification.  I can't answer
as to why this is so.  I do know that this is not planned for V1.3.
But this isn't what you were trying to do anyway.

Notify requests for specific entities can reach across domains, e.g. you can
receive a notification in domain A for an event generated by an entity in domain B.
This only works if you use a specific global entity instance in the
notify request, since global entity wildcards are enumerated within the context
of the domain that notification is requested on.

This is almost what you tried, except you were listening to the wrong entity.

Notify requests listen to entities that generate events.  In your case, the
alarm event is being generated by your domain rule entity, not by the circuit 
entity, so you should be able to do what you want by specifying the domain rule in
the notify request's "entity list" argument.  BUT, there's a bug in
the notification FM (and it's QAR'd) where notifications for DOMAIN RULES are
always reported against the domain that the rule exists in, and not in the
domain that the notification was requested for.  I do not know if this bug
is being addressed for V1.3.  I will ask.

There are several work arounds that come to mind:

	1) write your alarms action procedure to use the data collector
	   to send an event into your circuit domain for the appropriate
	   circuit entity.

	2) restructure your domains and/or rules to get the behavior you want
	   e.g. put the node4s and rules into your circuit domains instead of 
	   (or in addition to) the facility domains 

	3) put the relevant node4 entities into your circuit domains as well 
	   (in an out-of-the-way place, if you don't want to see them on the map)
	   and use notify requests and events from the node4 circuits instead of
	   alarm rules to detect circuit state transitions.
	   i.e. have a notify request like the following:
	            notify domain C_ABC -
			entity list = (node4 * circuit *), - 
			event = (circuit up, circuit down, -
				 circuit down circuit fault, -
				 Circuit Down Operator Initiated)
		and use targets to assign severities to each event, e.g.
		    assign target domain C_ABC -
			event source = (node4 * circuit *), -
			event name = "circuit up", -
			target severity = clear
		    assign target domain C_ABC -
			event source = (node4 * circuit *), -
			event name = "circuit down circuit fault", -
			target severity = critical

Good luck.
3668.2p.s.MCC1::DITMARSPeteWed Sep 02 1992 13:4913
in work around 3 in the previous reply, you can instead list the
node4's explicitly by name in your notify request and not put them
in the domain at all, 

	            notify domain C_ABC -
			entity list = (node4 one circuit *, node4 two circuit *, -
				       node4 three circuit *, node4 four circuit *), - 
			event = (circuit up, circuit down, -
				 circuit down circuit fault, -
				 Circuit Down Operator Initiated)

I think it'd be easier to use the wildcard and put the node4's in the 
domain... but it's an option.