[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

3680.0. "rules notify without domain" by CTHQ::WOODCOCK () Wed Sep 02 1992 22:56

Hi there,

I've seen this problem a few times now and at the current customer site it
is very consistent. I have an OCCURS rule looking at adjacency UP/DOWN events
that I have written but with NO domain qualifier. I only want the alarm
to update logs and leave map color updating up to a seperate NOTIFY request
on the event itself. The problem seen is that these rules show up on the map
even though there was no domain defined on the rule. So I get 2 notifications
for every event which I don't want. When looking at the details of the 
notification the domain field looks like

Domain:      Domain

It seems to only happen to non-registered adjacencies (a first guess). Is
this a bug or my expectations. Any workarounds???

thanks,
brad...
T.RTitleUserPersonal
Name
DateLines
3680.1I'll bet (hope) it only happens in domains with the MCC entity registeredMCC1::DITMARSPeteFri Sep 04 1992 13:2526
Hi Brad,

The "default" notify request from IMPM listens for "any notification event"
from any registered entities in the domain(s) you open.

If the MCC entity is in any of the domains, one of its subentities, the 
MCC ALARMS RULE entity, is registered as generating notification events, and 
therefore the notification request is going to issue the equivalent of a 

GETEVENT MCC 0 ALARMS RULE * ANY NOTIFICATION EVENT

And therefore, any rules defined in the "null" domain are going to be heard.
In fact, they'll be reported once for each domain in the "tree" of domains
you're listening to that has the MCC entity as a member.

I'd recommend you define a real live domain that will never be used from
the IMPM and put all your DOMAIN RULES that you don't want to turn a map
colors into that domain.

Note that the behavior you've run into can be used to play some tricks, e.g. poll
once get notifications in several domains.  It gets clumsy fast, but it's
a fun trick to know.

regards,

Pete
3680.2Same thing to me ???? MLNCSC::BARILAROFri Sep 04 1992 13:5237
Hi Brad,

	I'm not sure to have understand completly your topic, my 
	english isn't the best one, I think happen something 
	similar to me.

	My situation:
	I had a LAN router that send me event like "adjacency down/up",
	I inserted a notify request for each of my domains + a targeting
	to have the correct icon that change colors (not the router, the
	node that down/up). When I receive an event, I receive a notification
	for each of the Notification Request I wrote (one for each domains,
	5 in my site, so 5 notifications), also if the event is generate
	from a node that exist in one of my domains the Targeting works
	correctly, BUT if it's generate from a unknown node (ie. a not
	registered PC) I receive always the 5 notifications, no icon 
	change color (because the Targeting doesn't found the unknow
	PC icon). 

	As you see it isn't your exact situation, But I see that you write:

>	The problem seen is that these rules show up on the map
>	even though there was no domain defined on the rule. So I get 2 notifications
>	for every event which I don't want.

	If for "these rules show up on the map" you mean Notification Map,
	or if you haven't reTarget the alarm it's the Sink node that change
	color, and for "I get 2 notification for every event which I 
	don't want" you mean that you receive the alarm AND the notification
	it's more similar. 

	Let me know if I intrerpretate correctly your topic, and if you
	want more details.

					Hoping to be understandable,
						Ciao Luciano	
3680.3dummy domain=workaroundCTHQ3::WOODCOCKSun Sep 06 1992 15:2018
Hi all,

Yes the notification was only in the Notify Box so that is consistent
with want you had saw also.

Pete, I'm ahead of you. I'm home from the customer sight just reading this
note now. I set up a dummy domain and put the alarms in it. Others should
be forewarned though. I wrote a rule (without domain) to monitor internal
RULE events for a specific domain. Because this rule magically seems to
show up in domains even though there is no domain involved guess what
happened?? This first time a rule fired in that domain the MCC 0 rule
fired. Which also saw itself fire, and fired. Which also saw itself fire, and
fired. It's a loop. How fast can you count batch jobs PENDING incrementing??
Fortunately I got to the job before it got to the system...if ya know what I
mean :-).

best regards and thanks,
brad...