Conference azur::mcc

6448.0. ""ID already in use" error when registering node" by CSC32::J_RYER (MCI Mission Critical Support Team) Tue May 14 1996 04:22

    Customer uses a local namespace, and had all DECnis nodenames
    registered as a sort form (LOCAL:.name).  In preparation for
    moving to the corporate namesapce, they renamed all the DECnis's
    to a .usa.loc.name  form (where loc is a three-letter location
    code).  They de-registered and re-registered the nodes in the
    LOCAL: namespace.  They were able to delete the nodes out of
    MCC, but when they try to re-register them back they're seeing
    the following:  
    
    
MCC> register node .usa.scm.scm120 syn scm120

Node LOCAL_NS:.usa.scm.scm120
AT 10-MAY-1996 17:25:28

ID already in use.
                                Address = {([DNA_CMIP-MICE,
                                             None],
                                            [DNA_SessionControlV3,
                                             DNA_CMIP-MICE],
                                            [DNA_NSP,
                                             None],
                                            [DNA_OSInetwork,
                                            
39:840:11-35-67-00-36:AA-00-04-00-F
D-DB:20])}
MCC>
    
    
    However, MCC doesn't seem to know about this node . . .
    
MCC> dir node .usa.scm.scm120

Node LOCAL_NS:.usa.scm.scm120
AT 10-MAY-1996 17:26:58

The entity Node LOCAL_NS:.usa.scm.scm120  is not registered
                  Not Registered Entity = Node LOCAL_NS:.usa.scm.scm120
MCC>
    
    Here is how it's in the LOCAL: namespace  . . .
    
MCC> sho node .scm120
Using default ALL IDENTIFIERS

Node LOCAL_NS:.scm120
AT 10-MAY-1996 17:27:18 Identifiers

Examination of attributes shows:
                                   Name = LOCAL:.usa.scm.scm120
                                Address = {([DNA_CMIP-MICE,
                                             None],
                                            [DNA_SessionControlV3,
                                             DNA_CMIP-MICE],
                                            [DNA_NSP,
                                             None],
                                            [DNA_OSInetwork,
                                            
39:840:11-35-67-00-36:AA-00-04-00-F
D-DB:20])}
MCC>

    
    Can anyone give any information as to what the "ID already in use"
    error means?  How do we get these nodes completely de-registered
    from MCC so that we can re-register them with the new full names?
    
    Thanks,
    Jane Ryer
    MCI Mission Critical Support Team

    Hi,
    
    What you may want to do is have the customer deregister the DECnis
    nodes again (from whatever domain they are registered in) and then try
    doing the following command in MCC>
    
    MCC> DIR DOMAIN name MEMBER *
    
    This will show you if the entity still shows up somehow.  If you see it
    there, then do a:
    
    MCC> DELETE DOMAIN name MEMBER member name
    
    At that point, try the registration again.  If they are using the local
    naming option for DECnet/OSI, and the local mir for DECmcc, these two
    databases do not talk to each other.  Another option if they are using
    the local mir of DECmcc and did all their registrations via a command
    procedure, is to replace the MCC_COMMON:MCC_DNS_ATT.DAT and
    MCC_DNS_ENT.DAT file (the local mir) with blank ones from the DECmcc
    kit and reregister all of the entities.
    
    You can check to see if MCC is using he local MIR or DNS by doing a 
    
    $ SHOW LOGICAL MCC_DNS_SELECTION and seeing if it translates to DNS or
    MIR.
    
    Walt McGaw
    Digital Network Services Unit
    CSC/CS