[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

5789.0. "Events associated to an eroneous domain ..." by KETJE::PACCO (Horum omnium fortissimi sunt Belgae) Thu Dec 16 1993 13:39

    I would like to save time of support people who enconters the following
    message:
    
    "One or more global entities is deregistered. Unable to display them."
    
    Although this simple error message does not seem to be very dangerous
    I lost several days to understand another problem.
    
    I got events from the field from entities belonging to different
    domains.  From entities of one specific domain I got the most strange
    behaviour. Events from these entities appeared on the iconic map (and
    also on the forms and command line) being associated to other domains
    to which these did belong to.
    
    So if we assume (node A, collector B, snmp C) belonging all to domain D
    the notifications of events associated to 
    	node A did highlight the domain X
    	collector B highlight domain Y
    	snmp C highlight domain Z
    There was no relation at all to which domain the event seemed to be
    associated to, depending of the target domain or entity class for
    instance.  However if node A did send once an event to domain X, all
    events of that entity and all subentities were always sent to domain X
    (instead of domain D as expected).
    
    It's only when my attention was directed to that informational message
    (which I clicked away already a few times as is happens to be in the
    field) and I had time to investigate that one that this was the
    solution of another pending problem.
    
    Finally when the entity full name which was supposed to be a member of
    domain D was removed (delete domain D member FULLNAME) the problem
    described above disappeared !
    
    It was thanks to the original error message that I solved the problem,
    but I still does not understand why when DECmcc encounters an
    apparently harmless problem, issuing only an informational message, he is
    confused that much as to cause serious problems somewhere where you do
    not expect them any more !
    
    	Kind regards,
    	Dominique.
T.RTitleUserPersonal
Name
DateLines