[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

3381.0. "Data Collector and Iconic Map notification" by KAOFS::BOIVIN (Moi, j'viens du nord!) Fri Jul 17 1992 16:03

Good day,

I'm running MCC BMS V1.2 on VMS V5.5-1 (Motif V1.1). Here's my domain
hierarchy:

			Mohawk
			/    
		       /      
		     VAO       
		    /	\
		   /	 \
		CLUSTER	  Node4 nodes and MHO_DC data collector
		  /
		 /
		Node4 nodes and Reference entities (HSC000 and HSC001)

So, I created a notify request (using IMPM) in the form of:

	Notify Domain VAO entity list = (Collector *), Event = (Any event)

When I use MCC_EVC_SEND (from SYS$EXAMPLES) to notify an entity in the CLUSTER
domain, the VAO domain icon changes color (and the notification show up in the
notification window), BUT the sub-domains (CLUSTER) and the entity specified
(HSC000) do *not* change color... What am I missing? I thought that the
notification request would propagate to sub-domains (they are all dynamic).

$ MCC_EVC_SEND my_node MHO_DC "REFERENCE .ref.HSC000" "DCM reporting" -
	"HSC problem" CRITICAL

I can get the icon to change color by adding another data collector and notify
request in the CLUSTER domain, but then I get two notifications (one from VAO
and another from CLUSTER).

Any ideas/hints how to make this work? All I want is one notification and the
icon to change color...

Thanks,

Ed
T.RTitleUserPersonal
Name		DateLines
3381.1collector and target entity need to be in same domainTOOK::S_KOHoot mon!Tue Jul 21 1992 15:5424
    
    hi Ed,
    
>> When I use MCC_EVC_SEND (from SYS$EXAMPLES) to notify an entity in the CLUSTER
>> domain, the VAO domain icon changes color (and the notification show up in the
>> notification window), BUT the sub-domains (CLUSTER) and the entity specified
>> (HSC000) do *not* change color... What am I missing? I thought that the
>> notification request would propagate to sub-domains (they are all dynamic).
    
    To get the target entity of a collection event to change color, it must
    be in the same domain as the collector receiving the event.
    
>> I can get the icon to change color by adding another data collector and notify
>> request in the CLUSTER domain, but then I get two notifications (one from VAO
>> and another from CLUSTER).
    
    If the same collector is a member of multiple domains, each domain will report
    notification of events that the collector receives.
    
    You can avoid this by creating unique collectors for each domain.
    
    Hope this helps.
    
    -s
3381.2Lots of collectors OK?KAOFS::BOIVINMoi, j'viens du nord!Wed Jul 22 1992 14:3221
Re: .1

Yikes! So to use the Data Collector to highlight my icons, I'll have to
create a unique collector for every domain... Scary when you think about
it:

� Autoconfiguration creates a domain for every VMS cluster
� I ran it for our area (57.* Canada) and got hundreds of domains

I wanted to use the Data Collector to "collect" all of the critical 
events generated by other "monitoring" products like DCM, VCS, etc. and
update the iconic map accordingly.

Am I going to run into resource problems by creating hundreds of 
collectors? Is this a reasonable thing to do, or I am trying to make
the Data Collector do what it wasn't designed for?

Thanks for any ideas/hints,

Ed
3381.3only 1 processRACER::daveAttending The School of Comparative IrrevelevanceThu Jul 23 1992 09:234
Remember that a data collector is, basically, a data structure.  There is
still only one process that is actually getting the events.  We are using
the data collector (along with reference icons) to drive the new demo
that is being developed for V1.2 ("The Canned Demo").
3381.418 collectors works wellCTHQ3::WOODCOCKThu Jul 23 1992 09:415
For the record, we also have built a monitor using collectors/reference 
entities to help us manage the tymnet based WATN network. The domain structure
has only 18 collectors but all is working very well so far.

brad...