[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

4190.0. "REGISTER sometimes fails with "No such entity"" by KAOFS::BOIVIN (Moi, j'viens du nord!) Thu Dec 03 1992 13:59

Good day,

I'm registering Phase IV nodes using MCC V1.2.3 and having an intermittent
problem. The "trend" I'm seeing is that the error occurs when registering
either a *very* remote node (ie. slow links) or a slow local node4. I kept
checking the object under DNS to see what was happening...

If I retry the register command, MCC says it's already registered...

For example:

***** before register command ******
DNS> sho obj .vao.vaor01
 Attribute (Single) ___ DNA$NodeSynonym
 Attribute (Set) ______ DNA$Towers
 Attribute (Set) ______ DNS$ACS
 Attribute (Single) ___ DNS$Class
 Attribute (Single) ___ DNS$ClassVersion
 Attribute (Single) ___ DNS$UID
 Attribute (Single) ___ DNS$UTS
*************************************

MCC> register node4 .VAO.VAOR01 syn VAOR01

Node4 DEC:.VAO.VAOR01
AT  3-DEC-1992 13:47:55

No such entity: Node4 DEC:.VAO.VAOR01
                         Unknown Entity = Node4 DEC:.VAO.VAOR01


*********after 1st register command***************
DNS> sho obj .vao.vaor01
 Attribute (Set) ______ %X4D43435F11000C000000000000000000000000000000000000
 Attribute (Set) ______ %X4D43435F12000C000B00000000000000000000000000000000
 Attribute (Single) ___ DNA$NodeSynonym
 Attribute (Set) ______ DNA$Towers
 Attribute (Set) ______ DNS$ACS
 Attribute (Single) ___ DNS$Class
 Attribute (Single) ___ DNS$ClassVersion
 Attribute (Single) ___ DNS$UID
 Attribute (Single) ___ DNS$UTS
 Attribute (Set) ______ MCC_Class
 Attribute (Single) ___ MCC_UID
 Attribute (Set) ______ MCC_Version
*************************************************

MCC> register node4 .VAO.VAOR01 syn VAOR01

Node4 DEC:.VAO.VAOR01
AT  3-DEC-1992 13:51:28

The entity is already registered with MCC.
MCC>


************ after 2nd register command ***********

DNS> sho obj .vao.vaor01
 Attribute (Set) ______ %X4D43435F02000C000B0000000000000000000000000000000000FE
 Attribute (Set) ______ %X4D43435F11000C000000000000000000000000000000000000
 Attribute (Set) ______ %X4D43435F12000C000B00000000000000000000000000000000
 Attribute (Single) ___ DNA$NodeSynonym
 Attribute (Set) ______ DNA$Towers
 Attribute (Set) ______ DNS$ACS
 Attribute (Single) ___ DNS$Class
 Attribute (Single) ___ DNS$ClassVersion
 Attribute (Single) ___ DNS$UID
 Attribute (Single) ___ DNS$UTS
 Attribute (Set) ______ MCC_Class
 Attribute (Single) ___ MCC_UID
 Attribute (Set) ______ MCC_Version

*********************************************

Anybody have any clues what to look for?

Thanks,

Ed

PS. We are using the corporate DEC namespace. Anybody else out there seeing
this problem?
T.RTitleUserPersonal
Name
DateLines