|
Hello Al,
Sorry for the delay in responding to your note.
>When we tried to run the IP auto discovery feature on the ULTRIX system,
>no problem....it created a new domain and placed all of the entities it
>found, using the IP icon.
>But when we tried the same thing using the same options in the edited
>procedure, it created a seperate domain for each entity found and then
>used the domain icon for each entity in the map domain.
I'm not sure I understand what you are saying. Do you mean that
the behavior on VMS did not match that on ULTRIX?
Could you please post the files <domain>.cf* for each of
the two discovery sessions you mentioned?
You should find the files <domain>.cf, .cfA, .cfB and .cfC
for each discovery session in <top-directory>/IP/<domain> on
ULTRIX or [<top-directory>.IP.<domain>] on VMS, where
<top-directory> is the top level directory you specified for
that run, and <domain> is the name of the domain you specified.
Looking at these files will help us determine if the behavior
you are observing is correct.
>If you already have an existing domain, or subdomain, and use its name
>when doing the auto discovery, why does it not place the new entities in
>this domain.
>Example...my top level domain is USA, below which I have domain DWO, below
>which I have domains DECnet and TCP_IP. When asked for a domain, I gave it
>TCP_IP. But it created domain mcc.domain.16-68-192-0-hosts as well as
>domain .mcc.domain.{ip_node_name}.
>In both cases we're using the local MIR. But in the case of DNS, why are
>we forced to create additional directories?
>If this is to work with a customers established name space, why would they
>want to create directories just for DECmcc registration?
Have you read the release notes? If not, please do. Chapter
5 discusses Autoconfiguration and offers information about
how to control registration of entities discovered by
Autoconfiguration using namespace prefixes.
By editing the prefixes in MCC_AUTOCONFIG_PREFIX.DAT you control
how entities discovered by Autoconfiguration are registered.
In order to register entities at the top level in your
namespace, when using a MIR, specify the prefix "LOCAL_NS:.".
(This will not work for DNS.) To register them in some other
directory, specify that directory as a prefix, being careful
that the prefix ends with a ".".
Remember also, that you can make any domain a member of
any other domain yourself, after Autoconfiguration has run.
About domains created by Autoconfiguration. It may be necessary
for Autoconfiguration to create domains other than the top
level domain you specify. These subdomains are made members
of the top level domain. I believe this is the behavior
you are seeing. The domains 16-68-192-0-hosts and {ip_node_name}
are probably members of your top level domain.
I hope this helps a bit. Please let me know if you have any
more questions. I look forward to seeing your .cf files.
Regards,
Ulla Figwer
|