[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

2666.0. "line color changes not happening" by ICS::WOODCOCK () Tue Mar 31 1992 15:28

Hi there,

I know a lot of work has been done for the next base level but thought this
might be a 'new' find with line color changes.

I have two levels of domains on the map. The top level contains all domains
and the next level contains node4 entities primarily. The same node4 'circuit'
child entity is drawn in BOTH levels. Typically in the past I had to be
viewing the lower level when the alarm happens to see line color change. This
I believe has been worked from previous QARs. Now by adding these line to the
top level I expected to see changes at the top. When viewing from the top, the
event comes in, the notify signals a problem in the lower domain but the line
never changes color in the top domain. Problem?? Any ideas??

thanks,
brad...

T.R	Title	User	Personal Name	Date	Lines
2666.1	make sure your notify knows about the new circuit	TOOK::CALLANDER	MCC = My Constant Companion	`Tue Apr 07 1992 15:38`	9
	to signal the change in both domains you must have the notify outstanding in each domain. Also note that the NOTIFY command does not monitor the domain for changes in the domain content. So if you added the circuit after the domain was brought up then you will have to terminate the notify and restart it. This is done the easiest from the notification applications window/notify request window. jill
2666.2	more info	ICS::WOODCOCK		`Wed Apr 08 1992 13:32`	17
	Hi Jill, Originally, we had all domains in the top level and the second level domains contained all the entities. At this point we did a NOTIFY on the TOP level for NODE4 * CIRCUIT SYN-* event=Circuit Down Circuit Fault This command propogates into all domains from the top level and changes color for all entities in the entire structure. We then added the lines as NODE4 CIRCUIT entities to the top level and issued the same NOTIFY request at the top level, but the top level never changes any of the lines to any other color. any ideas? brad...
2666.3	global entity must be in domain	ICS::WOODCOCK		`Tue Apr 21 1992 20:56`	14
	Hi there, Some further testing with the t1.2.7 kit has shed some light on this problem. It appears that the GLOBAL entity must be a member of the domain for color to change on the line (QAR #2796) if it is a child entity. This is another major stumbling block (and a MUST FIX) on the road to create a real time hands off network monitor for anybody with more than a few entities/circuits to monitor. any ideas out there?? best regards, brad...
2666.4	subentities on map aren't "in domain"	DADA::DITMARS	Pete	`Thu Apr 23 1992 15:37`	18
	Hiya, The problem is, when you ask the notification FM to notify you of a wildcarded list of global entities, the FM qualifies that wildcard within the context of the domain. In V1.2, only global entities can be members of a domain. How then, you ask, am I able to put subentities on maps? The IMPM has special support to do just that: put the subentity on/in the map file, but the entity itself isn't a member of the domain. That explains why you're not getting notification in the domain that doesn't have the global entity in it. One work-around is to put the global entity in the domain using FCL and live with the "mismatch" box that comes up whenever you open the domain. Another is to put the global entity into the domain and push it somewhere away from the main part of your map. A third is to specify notify commands with explicit global entity instances. The FM doesn't seem to mind if those aren't in a domain. Of course, in a large installation, this might not be feasable.