Conference azur::mcc

39.0. "DNS ENVIRNOMENT documentation update" by TOOK::NELSON () Wed Jan 17 1990 08:36

This note updates section 1.4 (DNS ENVIRONMENT) of the MCC IFT release 
notes. 


1.4  DNS ENVIRONMENT REQUIREMENTS FOR THE DECMCC SYSTEM

The following subsections detail how  a  DECmcc  site  manager  should
configure   the  Digital  Distributed  Name  Service  Namespace  (DNS)
Nameserver.



1.4.1  Digital Distributed Name Service Namespace

DECmcc uses the  Digital  Distributed  Name  Service  Namespace  (DNS)
Nameserver  as  a repository for entity instance information (specific
entity names).

Although DECmcc can use the default namespace set up by your corporate
namespace  administrator,  you  may want to create a private namespace
for DECmcc's use for the following reason.  For internal  field  test,
the  corporate  policy  for  naming Phase IV nodes in the namespace is
unclear.  Therefore, a "snapshot" of the policy taken at the  time  of
the  internal field test has been implemented.  There is a possibility
that during internal field test the corporate policy will  change  and
be  implemented  differently  than  the  policy implemented by DECmcc.
Therefore, the site manager should decide whether to  make  a  private
namespace or use the default corporate namespace.

The DECdns Client software comes with VMS V5.3.  However, you must start 
it up by placing the following command in your system startup file:

     @SYS$MANAGER:DNS$CLIENT_STARTUP.COM

The Client must be running for the DECmcc installation to succeed.


1.4.2  Creating A Private Namespace

Should you decide to create a private namespace, you must install  the
DNS  Nameserver.   Any system startup files that use DSS products must
be modified to put the DEC:  prefix  (or  your  corporate  prefix)  in
front  of  namespace  names.   For example, the following DFS start-up

SYSTEM CONSIDERATIONS                                         Page 1-6


command:

     MOUNT/CLUSTER .ENG.NAC.TOOK.USER43

must be changed to the following:

     MOUNT/CLUSTER DEC:.ENG.NAC.TOOK.USER43

If you create a private namespace, modify the system default namespace
to    be    the   private   namespace.    Do   this   by   using   the
DNS$CHANGE_DEF_FILE.COM file provided with the DNS Clerk, as follows:

     @SYS$MANAGER:DNS$CHANGE_DEF_FILE

     Enter server name> <node name>

You must respond with  the  name  of  the  node  running  the  private
namespace  server.   This  is  the node on which you installed the DNS
Nameserver.

After executing this command file, you must  execute  the  DNS  Client
start-up command procedure, as follows:

     @SYS$MANAGER:DNS$CLIENT_STARTUP.COM



1.4.3  Setting Up The Namespace

The following considerations apply whether you have set up a private 
namespace or are using your corporate namespace.

For DECmcc to function properly, the following DNS directories must be
created  within  the namespace, and the appropriate access control set
for them.  Whether or not you have created a private namespace, you must
ensure that these directories are present for your use.  You must use
the DNS$CONTROL utility present on the  system running the DNS
nameserver to create the directories, as follows: 


     $ RUN SYS$SYSTEM:DNS$CONTROL
     DNS> CREATE DIRECTORY .DNA$NODES
     DNS> CREATE DIRECTORY .DNA$BackTranslation
     DNS> CREATE DIRECTORY .DNABackTranslation.0001
     DNS> CREATE DIRECTORY .MCC$BRIDGE_BackTranslation


SYSTEM CONSIDERATIONS                                         Page 1-7


Use DNS$CONTROL to create the following directories:

      o  <root>.DNA$Nodes

      o  <root>.DNA$BackTranslation

      o  <root>.DNA$BackTranslation.<area> (where  area  is  a  string
         representing the 4 digit area number in hex)

      o  <root>.MCC$<class>_BackTranslation (where class is the  ASCII
         string for the registered name of the entity class)

These directories must be created directly under the namespace root.

In addition to the DNA$NODES and DNA$BackTranslation directories,  you
must  create one area-specific directory under the DNA$BackTranslation
directory for each area in the DECnet network.  You must  also  create
one  class-specific  BackTranslation  directory for each global entity
class to be managed by DECmcc, except Phase IV and Phase V node.

DECmcc does not create directories; it assumes  that  the  directories
have been created.

Access control to the namespace and its object is handled by the  site
manager  and  site  policy.   DECmcc assumes that it has access to the
namespace  objects.   The  site  manager  must   give   DECmcc   users
appropriate privileges as follows:

      o  All DECmcc users must have READ access to the DNS directories
         mentioned above.

      o  All DECmcc users who will be REGISTERing  objects  must  have
         WRITE  and  DELETE  access  to  the DNS directories mentioned
         above.

      o  All DECmcc users must have  READ,  WRITE,  DELETE,  and  TEST
         access to the objects maintained by DECmcc.


Reference the Nameserver  documentation  for  more  information  about
namespace management.



1.4.4  Naming Entities (objects) In The Namespace

For field test, all AM developers and site managers must name their
managed objects in such  a  way  that  all objects, except Phase IV and
Phase V node, are created directly under the namespace root directory.  
Phase  IV  node objects are placed under the <root>.DNA$Nodes directory.

HI,


I just started using mcc and this is my first note in here ---Sorry it's a blast.
I installed: mccut010 5-mar and took the release notes: 
  MCC$EXEC_UT1_0_0.RELEASE_NOTES  5-mar  and the read_me_first.txt 6-mar

It didn't have the info in this note!! (I had look at this conference before
 but didn't remember/see this note)
Therefore, I assumed (wrongly) that register was creating these directories:
   dna... etc.     ---wrong!  And it took me awhile to realize why "register" 
wasn't working!

I think its important that this DNS info be included in the release notes and
even mentioned in the MCC documentation.

Thanks for the sounding board,  ===Steve

    I'm also a new reader of this conference...  And I'm pretty much
    starting with this note...
    
    Question....
    
    Why do :
    
    	o All DECmcc users who will be registering objects must have
    	WRITE AND DELETE access to the DNS directories mentioned 
    	above.
    
    Seems to me that DECmcc (as an applications managing objects) only
    needs READ and WRITE access to directories and their objects...
    DELETE is really only useful if you accessing DNS objects and Dirs
    via DNS$CONTROL.  Won't DECmcc WRITE objects out of dirs to delete
    them?
    
    DELETE access is a scary topic to most DNS ADministrators in the
    world.. Too many folks with DELETE Access to things can cause 
    alot of headaches..
    
    jr

    
    One thing to note here, is the statement you picked up on stated
    that "users who will be registering objects" need these privs. We
    don't expect that to be everyone. Just like your DNS Administrators
    don't like alot of delete privs going around, I don't think your
    network managers will be any to happy if lots of people have privileges
    to be playing around with de/registrations.
    
    

The subdirectories names as documented in the DECmcc manuals, as well as the 
documentation in this note, is incorrect for use with DECnet/OSI Phase V.
The subdirectories for the areas (1-63 for Phase IV use) must be of the
DNS external name format 'HexPair' or a Ninary Simple Name, 
where the directory created is:

	DNA$BackTranslation.%X0001 NOT DNA$BackTranslation.0001.

If the latter form is used (as it will be because it is documented that way)
Phase V addresses will not be stored there and you will have a skew between
the directories used by DECnet Session control and those used by DECmcc.
Which I do not think is the goal here.

Also, if the documentation is correct, then the code is wrong.  

/Claudia Peters

I checked with Stve Jong -- he indicates that the documenation is in error
and that DNA$BackTranslation.%x0001 is the correct syntax and the documenation
will be corrected.   /cp

    DECnet/OSI Phase V will use the format DNA$Backtranslation.IDP.Loc-Area, 
    hence, assuming the default IDP or PhaseIVPrefix value %X49, the following 
    directories should exist:

    	.DNA$BackTranslation
    	.DNA$BackTranslation.%X49
	.DNA$BackTranslation.%X49.%X0001 	(for area 1)

    Agree?

    Georges.
    	 

DECmcc is well aware of the Phase V Backtranslation implementation.
We know we don't conform, but way back in September of last year this 
information was not available and we had to take a stab at something.
This has already been exhaustively discussed in note 86 and 88, as well 
as at the field test training.

The current EFT software works with the directories as documented.
DNA$BackTranslation.0001	NOT 	DNA$BackTranslation.%x0001
				---

We will be upgrading MCC to use the correct directory names with EFT 
update.  (Now that Session Control and friends are in agreement)

...kjn

Yes I agree -- brain damage took hold yesterday and I forgot the IDP sorry
about that.  /Claudia