Conference azur::mcc

I do not believe that the leading "." in the namespace name is legal.
If you namespace is called "LAB", then your domain would be
"LAB:.domain", not ".LAB:.domain"

Also, the NS name should not appear in the Prefix data file.
That file should be:

	DOMAIN | .domain.
	NODE4 | .dna_node.
	SNMP | .snmp.

The use of the name space name, while allowed in certain places, does not
always work as expected, and hence, the requirement that MCC either use the
"local" name space (e.g. the local MIR) or the DEFAULT DNS name space.

This has been true since V1.0, I think.

I reguards to the ".LAB:" prefix, the autotopology tools did exactly what
you asked it to do.  If you had specified the prefix as "^$#%^%&#", it
would have used that, too.

The real question is the last point you raised:

> . I also tried without having created them in DNS before then :
>   I have first to add in the register.com file: create domain LAB:.domain.
>   but when trying to create the subdomain LAB:.domain.TOPOLOGY then
>   the .com file complains about some missing information in the 
>   namespace server.

What, exactly, is the message?  Its hard to guess what the problem might be
from the phrase "the .com file complains about some missing information"

Hi Erik,
Hi Dave,

Thanks for your quick answers. I have tested your suggestions and here are 
my results.

Dave, you will also find more information on the registration.com
file problem.

> I do not believe that the leading "." in the namespace name is legal.
> If you namespace is called "LAB", then your domain would be
> "LAB:.domain", not ".LAB:.domain"

If you specify the domain this way in mcc_autoconfig_prefix.dat 
DOMAIN | LAB:.domain.
NODE4 | LAB:.dna_node.
SNMP | LAB:.snmp.

DECmcc Phase IV Autoconfiguration returns at namespace checking :

   Error : the DECmcc autoconfiguration prefix file has not been set up
           properly.
   The following prefixes are invalid :
   LAB:.domain.
   LAB:.dna_node.
   LAB:.snmp.
   All prefixes must end with a ".".
   etc...
(please note the accuracy of the last message!)
The same message is specified in the documentation and in the file itself 
2 line above the prefixes with both "begin and end":
Autoconfiguration and autotoplogy use manual/ page 2-3, namely:

"# NOTE: Prefixes must begin and end with a period." 


> What, exactly, is the message?  Its hard to guess what the problem might be
> from the phrase "the .com file complains about some missing information"

After the modification of the 
sys$sysroot:[000000.sysmgr.dna4.topology]mcc_topology_registration.com
file, ( if you already add:"  create domain LAB:.domain. " which works ok)
I have the following message when runnning the second command line
( which is: "  create domain LAB:.domain.TOPOLOGY. ")

   The requested operation cannot be completed
       MCC unhandled service reply =
          Unable to register name, required name space directory
          does not exist.


> The use of the name space name, while allowed in certain places, does not
> always work as expected, and hence, the requirement that MCC either use the
> "local" name space (e.g. the local MIR) or the DEFAULT DNS name space.


We are using DNS as our "DEFAULT" DNS name space.
What do you mean by DEFAULT DNS. We have installed DNS V1.1.
MCC_DNS_SELECTION = "DNS" as logical
and don't want to use a local MIR namespace as the tool we are testing will
help migrating the EASYNET to phase V, and so should use DNS, with replicas,..

Thanks helping us,
We are stuck at that point with the autotopology feature and our DNS 
environment.

Any idea will be helpful
Bruno

>> "local" name space (e.g. the local MIR) or the DEFAULT DNS name space.
>
>What do you mean by DEFAULT DNS. We have installed DNS V1.1.

This refers to the namespace used by DECdns on the system if no
namespace is specified.  This default is specified at the time that
DECdns is installed on the system.  You use it by simply leaving out
the namespace name in your specification.

Example:

Assuming that DECdns is set up to use the corporate namespace, then

	DEC:.lkg.mynode

is the same as

	.lkg.mynode

Hi Bruno,

Knowing how the tool works my guess is that there may be an extra blank line
at the end in mcc_autoconfig_prefix.dat file. For us to help you we need
following information from you. 
1. An exact copy of your mcc_autoconfig_prefix.dat file.
2. Screen dump of the error messages reported by the entity.

You may also want to try the following mcc_autoconfig_prefix.dat 
file.

DOMAIN	| .MCC.DOMAIN.
NODE4	| .DNA_Node.
SNMP	| .SNMP.

Regards,

Anil

    
    Thanks Erik and Dave for your responses to this note.
    
    Hello Philippe,
    
    Dave is correct in .2.  The namespace should not be specified
    in MCC_AUTOCONFIG_PREFIX.DAT.  Thus, you may want to edit the
    file to read:
    
	DOMAIN | .domain.
	NODE4  | .dna_node.
	SNMP   | .snmp.

    if .domain., .dna_node., and .snmp. are in fact the directories
    in DNS which you would like Autoconfiguration to use when registering
    entities.

    We will make note of your findings and try to improve the error
    messages which Autoconfiguration prints regarding the format
    of the prefixes in MCC_AUTOCONFIG_PREFIX.DAT.
    
    If DNS is set up properly before Autoconfiguration is run, it
    should never be necessary to edit the registration command file.
    The problems you noted in .3 are due to the fact that before running
    Autoconfiguration you need to create directories in DNS which match the
    prefixes you specify in MCC_AUTOCONFIG_PREFIX.DAT. If these directories
    are not present, registration will fail.
    
    Please refer to Chapter 2 of the DECmcc Autoconfiguration and
    Autotopology Use manual for important information about
    namespace planning.  Specifically, page 2-2 ("DECdns Namespace
    Planning and the Autoconfiguration Prefix File") and pages 2-6
    and 2-7 ("Setting Up DECdns Namespace Directories for
    Autoconfiguration") should provide you the information you need.
                                
    Regards,
    
    Ulla Figwer
                   

Hi Folks,

Regarding the extra blank line at the end in mcc_autoconfig_prefix.dat we
dont have any.

we are using a file (version ;2)
MCC_AUTOCONFIG_PREFIX.DAT;2 	8-APR-1992 14:16:29.81 

the end of the file is :
#
#=============================================================================
#
DOMAIN | .domain. 
NODE4  | .dna_node.
SNMP   | .ip.
<EOF>
this was the original version delivered in the SSB kit.

My namespace is called LAB: in DNS and I have already a .MCC. and .DNA_Node. dir.
but no SNMP directories,

let's put the problem like that:

If i don't want to use or disturb the DNS current configuration, what should 
I do first inside DNS and then in the MCC_AUTOCONFIG_PREFIX.DAT ?

my namespace is called LAB:
I have already a MCC and .DNA_Node. and no SNMP directories, but don't want 
to use them.

May I create 3 directories in DNS LAB:
e.g.:
TESTMCC
TESTDNA
TESTSNMP

Should I also create LAB:.TMCC.DOMAIN. in DNS
before running:
the MCC_AUTOCONFIG_PREFIX.DAT from autotopology with :



DOMAIN	| .TESTMCC.DOMAIN.
NODE4	| .TESTDNA.
SNMP	| .TESTSNMP.

Regards,

I would like to suggest to the kind user, that he create the directories
using the MCC_COMMON:MCC_DNS_SETUP.COM command file, provided exactly for that
use.

This nifty little command procedure has been there since v1.1, at least,
and was created to help with setting up the DNS name space.  The feature is
that it should help you get all the ACL's and ACE's correctly, as well as
setting up the simple directory structure.  Please try it out and let us know
results.

Thanks.

    
    Hello,
    
    If you do not want to use the existing directories in DNS, then
    you do need to create new ones.  If you want to use the
    MCC_ACONFIG_PREFIX.DAT file you suggested:
    
	DOMAIN	| .TESTMCC.DOMAIN.
	NODE4	| .TESTDNA.
	SNMP	| .TESTSNMP.
    
    Then you need to create directories ".TESTMCC", ".TESTMCC.DOMAIN",
    ".TESTDNA" and ".TESTSNMP" in DNS before running Autoconfiguration.
    As Dave pointed out in .8, you can use the command procedure
    MCC_COMMON:MCC_DNS_SETUP.COM to create these directories, as
    suggested in the "Autoconfiguration and Autotopology Use" document.
    
    (The answer to your question "Should I also create LAB:.TESTMCC.DOMAIN.
    in DNS before running Autoconfiguration..." is yes.)

    Please be aware of the implications of having entities already
    registered in DNS before running Autoconfiguration.  As I mentioned
    before, the "Autoconfiguration and Autotopology Use" document contains
    important information about Namespace Planning for Autoconfiguration
    and about Domain and Map File Mismatches.  If you read this
    information and have any questions, please feel free to contact
    me.  I can be reached at TOOK::FIGWER or at DTN 226-7858.

    Regards,
    
    Ulla