[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

733.0. "Domain creation problem" by UBOHUB::BRYAN () Mon Feb 18 1991 16:24

	Can someone shed some light on a problem I am experiencing.
    I have recently upgraded my EFT version on a 3500 to VMS Version
    5.4-1 and pre-MCS on a 3100. To do this I reinstalled TSAM, SNMP and FDA 
    management modules.

	On attempting to use the new system I have encountered a number 
    of problems. The first being on the world map a message stating 
    "One or more global entities is deregistered. Unable to display them."
    This map has three domains all of which are showing ? I also recieve
    this at a lower level in the domain hierachy where I am displaying 
    actual nodes. Here I found the IP nodes missing. I replaced these on 
    the map OK but I am still getting the message.

	The second problem was that a domain showing Phase IV nodes with
    lines interconnecting got populated as if the map did not exist even
    though it was displayed i.e. the lines did not match the systems. This
    could only be displayed after turning off notification since I was 
    informed that Notification could be corrupted.

	So I decided to delete the domain and try to recreate it. This is
    when I encountered a third problem in that I was unable to create 
    domains through the Iconic Map. I got through the registration details
    (username,directory) but then got an error "Unable to create member
    .domain.fred. It is not registered.". However through the FCL it is 
    registered and if I attempt the command again through the Iconic Map,
    I no longer get the registration form but still get the same message.

	Are any of these things linked at all ?

Thanks - Francis.
T.RTitleUserPersonal
Name
DateLines
733.1need more infoBARREL::LEMMONTue Feb 19 1991 01:2245
>	On attempting to use the new system I have encountered a number 
>    of problems. The first being on the world map a message stating 
>    "One or more global entities is deregistered. Unable to display them."
>    This map has three domains all of which are showing ? I also recieve
>    this at a lower level in the domain hierachy where I am displaying 
>    actual nodes. Here I found the IP nodes missing. I replaced these on 
>    the map OK but I am still getting the message.
    
    Check the logicals MCC_MAPS and MCC_ICONS.  The Iconic map looks in
    MCC_MAPS for the maps files and MCC_ICONS for the icons.  They are
    defined "sys$disk:[],mcc_common:" and "mcc_common:".  The ? being
    displayed inside the icon indicates that the icon files for the
    entity class was not found in MCC_ICONS.  
    
    If you want to see what the domain really contains, type
    
    	MCR DNS$CONTROL SHOW OBJECT domain ATTRIBUTE DNS$MEMBERS
    
    This will list all the domain members that the domain has.  (A future
    version of the Iconic Map will also list the unregistered domain
    members)
    
>	The second problem was that a domain showing Phase IV nodes with
>    lines interconnecting got populated as if the map did not exist even
>    though it was displayed i.e. the lines did not match the systems. This
>    could only be displayed after turning off notification since I was 
>    informed that Notification could be corrupted.
    
    What do you mean by got populated?  Did you initially add the nodes,
    draw the lines, save the map, and then re-open the domain, and then 
    find the nodes autoplaced instead of where you initially put them?
    
>	So I decided to delete the domain and try to recreate it. This is
>    when I encountered a third problem in that I was unable to create 
>    domains through the Iconic Map. I got through the registration details
>    (username,directory) but then got an error "Unable to create member
>    .domain.fred. It is not registered.". However through the FCL it is 
>    registered and if I attempt the command again through the Iconic Map,
>    I no longer get the registration form but still get the same message.>
    
    If I understand you right, a "directory domain .domain.fred" works,
    indicating that the domain is created/registered. But a "create domain 
    xxx member .domain.fred" fails.  Is that true?
    
    
733.2clarificationUBOHUB::BRYANTue Feb 19 1991 08:2123
    Sorry if my explanations were not clear, I will try to clarify them.

    The first problem is not related to the logicals you suggested. The 
    map and icons all display correctly. The question mark relates not to
    a display on the map but my own surprise as to why I should get an
    error message on entering the domain when all appears fine within it.
    I get the same error message on another domain which contains a mixture
    of entities yet they are all displayed correctly.

    Can you tell me what might cause this error message or how I might find
    out which global entities it thinks are deregistered ?

    The second problem you are correct in that a previously created map with
    lines and icons became a map of lines and autoplaced nodes. This I am not
    too concerned about since I have now deleted the domain.

    The last problem I have resolved by using a different directory in response
    to the Add Entity domain form. Both directories have RWE privs for the
    account, however the one used previously would not allow me to create
    domains through the iconic map but would allow me through the FCL.

Thanks - Francis.
733.3More infoUBOHUB::BRYANTue Feb 19 1991 09:1412
   As an update to the previous note. The third problem still exists on
   one particular domain. I try to create a new domain within this domain
   through the iconic map. However after completing the Add Entity form with
   Owner Id and Directory and pointing at the map I get a message box with
   "Unable to create member DGMT21_NS:.domain.tom. It is not registered.".
   If I do a SHOW DOMAIN .DOMAIN.TOM from the FCL the domain has been
   resistered.

   What steps does the iconic map go through when adding new entities ?
   Why should it work within one domain but not another ?

   Any help appreciated - Francis.
733.4 TOOK::F_MESSINGERTue Feb 19 1991 10:1311

Francis,

Were the domains you are having problems with created with an older
version of MCC?  If so, backward compatibility is not supported for 
any pre MCC 1.1 kits.  Hopefully we will be backward compatible with
subsequent releases.  If they were created with an older MCC, delete them
and recreate them.  (Not a very popular statement!)

Fred
733.5All V1.1 EFTUBOHUB::BRYANTue Feb 19 1991 13:205
    Fred,
    
    The domains were all created with the V1.1 EFT version.
    
    Francis.
733.6re:.2BARREL::LEMMONWed Feb 20 1991 00:1115
    The message is informational in nature.   The domain fm requires
    that a global entity be registered before it can be put in a domain.
    The messge you are seeing is telling you that the domain fm found 
    a member in the domain that has been deregistered.  The Iconic Map
    us unable to display members that are deregistered because only the
    fullname is returned.  The class information is missing.
    
    Try the following from the command line
    
    	MCC> SHOW DOMAIN domain MEMBER * ALL CHAR
    
    This is what the Iconic map does when you open a domain.  You should
    see the fullname of the member that is deregistered.   Either register
    the entity that this fullname represents or delete it from the domain.
    
733.7RE:.3BARREL::LEMMONWed Feb 20 1991 00:254
    see note 356.1 for information on how the add operation works.
    
    Try doing it via the command line (MCC> CREATE DOMAIN domain  MEMBER
    .DOMAIN.TOM). 
733.8resultsUBOHUB::BRYANTue Feb 26 1991 14:5665
Jim,        

RE: .6  This is the result of the command you suggested. All members in the
        domain are registered OK, all get displayed on the map OK, but I still
        get the message. 


MCC> SHOW DOMAIN .DOMAIN.WORLD MEMBER * ALL CHAR

Domain DGMT21_NS:.DOMAIN.WORLD Member DGMT21_NS:.DOMAIN.UNITED_STATES 
AT 26-FEB-1991 16:39:17 Characteristics

Examination of attributes shows
                            Member Type = Dynamic
                          Member Entity = Domain 
                                          DGMT21_NS:.DOMAIN.UNITED_STATES 

Domain DGMT21_NS:.DOMAIN.WORLD Member DGMT21_NS:.DOMAIN.WESTERN_EUROPE 
AT 26-FEB-1991 16:39:19 Characteristics

Examination of attributes shows
                            Member Type = Dynamic
                          Member Entity = Domain 
                                          DGMT21_NS:.DOMAIN.WESTERN_EUROPE 

Domain DGMT21_NS:.DOMAIN.WORLD Member DGMT21_NS:.DOMAIN.GIA 
AT 26-FEB-1991 16:39:19 Characteristics

Examination of attributes shows
                            Member Type = Dynamic
                          Member Entity = Domain DGMT21_NS:.DOMAIN.GIA 

MCC> SHOW DOMAIN .DOMAIN.WESTERN_EUROPE ALL CHAR

Domain DGMT21_NS:.DOMAIN.WESTERN_EUROPE 
AT 26-FEB-1991 16:40:44 Characteristics

Examination of attributes shows
                               Owner ID = "NETMAN"
                              Directory = $1$DUA1:[BRYAN]

MCC> SHOW DOMAIN .DOMAIN.GIA ALL CHAR

Domain DGMT21_NS:.DOMAIN.GIA 
AT 26-FEB-1991 16:40:57 Characteristics

Examination of attributes shows
                               Owner ID = "NETMAN"
                              Directory = $1$DUA1:[BRYAN]

MCC> SHOW DOMAIN .DOMAIN.UNITED_STATES ALL CHAR

Domain DGMT21_NS:.DOMAIN.UNITED_STATES 
AT 26-FEB-1991 16:41:10 Characteristics

Examination of attributes shows
                               Owner ID = "NETMAN"
                              Directory = $1$DUA1:[BRYAN]


RE: .7 the command works successfully from the command line but will
        not display on the map. It gives the not registered message
        as before.
    
    Francis.
733.9re: .8BARREL::LEMMONThu Feb 28 1991 14:526
Francis,
  I don't understand why this is happening and need to investigate
it further.  Lets work this off line.  Give me a call at DTN 226-5329 or 
send mail to BARREL::LEMMON.

/Jim
733.10try dns setup againWELCLU::MCCALLUMFri Mar 08 1991 14:479
    
    I had a similar problem on upgrading from EFT to BMS. I ran the
    MCC_DNS_SETUP again and it created a new DNS directory to do with DTSS.
    This has been added since EFT1.1
    
    After a reboot the global enetity message never appeared again.
    
    Dave
    
733.11Unable to create domain member; Can't do directory from IMPMCUJO::HILLDan Hill-Net.Mgt.-Customer ResidentWed Oct 16 1991 16:0146
    I have just experienced this same error.  If a resolution has been
    posted, please provide a pointer.
    
    SYMPTOMS:
    
        (NOTE:  .domain_2 and .domain_3 belong to .domain_1 and can be
    		seen via the IMPM and FCL.)
    
    I just completed several domain rebuilds to correct a typo error in the
    Owner ID field.  Everything went just fine.  
                                                           
    When I tried to ADD .domain_3 as a member of .domain_2 from
    IMPM, I got the infamous error message:
    	"Unable to create domain memeber .domain_3.  It is not registered."
    
    I "looked up" from .domain_2 to .domain_1, selected .domain_3 icon,
    tried to do a DIRECTORY operation on .domain_3 from IMPM and got the
    following:
    ----------------------------------------------------------------------
    Operation: Directory
    Entity: Domain .domain_2
    Domain: MY_NS:.domain_1
    
    16-OCT-1991 08:05:00
    
    The requested operation cannot be completed
    
    MCC Unhandled Service Reply     No such entity: Domain MY_NS:.domain_1 -
    								Member *
    				    Domain MY_NS:.domain_1 Member *
    ------------------------------------------------------------------------
    
    1.  All directory and show commands are successful from FCL on ALL
    	domains.
    2.  I can add other entities in .domain_2 with no problem.
    3.  The following FCL command fails with a very strange error:
    
        MCC> CREATE DOMAIN .domain_2 MEMBER .domain_3
          MY_NS:.domain_2 Member MY_NS:.bdg.BRIDGE1
          Unable to create member MY_NS:.domain_3.  It is not registered.
    
       ????? Why do I get a bridge which is a member of .domain_2 
             showing up in the error message when I try to add 
             .domain_3 as a member of .domain_2 ?????
    
    -Dan
733.12FYI re: .11 - I am running DECmcc V1.1CUJO::HILLDan Hill-Net.Mgt.-Customer ResidentWed Oct 16 1991 16:121
    
733.13Solution to "deregistered domain member" problem.CUJO::HILLDan Hill-Net.Mgt.-Customer ResidentFri Oct 18 1991 02:5552
    The following are solutions based on discussions with Jim Lemmon:
    
    When you have deleted and deregistered a domain that was a member of 
    one or more existing domains, strange things happen.
    
    To prevent the problem:
     1.  MCC> DELETE DOMAIN .parent_domain MEMBER .child_domain
    
         (You can use a "*" if .child_domain is a member of many domains. 
          If you are doing this from the Iconic Map PM, you must look into
          every parent domain which includes .child_domain as a member and
          delete it using the "double-lined delete icon" from the toolbox.
          If .child_domain is a member of 100 other domains, you're gonna 
          be deleting for a long, long time.)
    
     2.  MCC> DELETE DOMAIN .child_domain
    
    
    If you do step 2  before step 1 , or you don't do step 1  at all, you
    will see strange error messages and behavior as mentioned in earlier
    replies to note 733.  Here is the method to recover from your error.
    
     1.  Find the deregistered/deleted child domain which is causing you
         problems:
           MCC> SHOW DOMAIN .parent_domain MEMBER *
         and look for the following message 
           "Detected a deregistered Domain Member.  MY_NS:.prob_child_domain"
    
                  (By the way, I mentioned at the end of note 733.11
                   that I saw a bridge entity show up in the error
                   message following a CREATE command.  Turns out
                   that this bridge entity was just before the
                   "Detected a deregistered..." message.  This is
                   another helpful way of finding a problem entity.)
    
         This message can be hard to spot if you have many entities in your
         .parent_domain, so it may be helpful to create an output file and
         search for "Detected".
    
      2. Once identified, you must re-create/re-register .prob_child_domain
         so that you can properly delete it as a member of all other
         domains.
           MCC> CREATE DOMAIN .prob_child_domain
    
      3. Now you can delete .prob_child_domain from other domains and
         finally delete the .prob_child_domain altogether.
      
           MCC> DELETE DOMAIN * MEMBER .prob_child_domain
           MCC> DELETE DOMAIN .prob_child_domain
           
    
    -Dan