Conference azur::mcc

    All I can say is that when I did this, it took me two weeks to recover!
    
    Good Luck!

From:	MCDOUG::MCPHERSON "Doug McPherson | LKG2-2/N1 | DTN: 226-5145  28-Sep-1990 2349" 28-SEP-1990 23:53:10.47
To:	@TOOK::JSG_STAFF.DIS
CC:	MCPHERSON
Subj:	How to fix DNS server when you change DECnet information on a node...

Save this information. This is almost as important to know as 'how to break
into your own system when you forget the passwords...'

/doug

Instructions for changing DECnet node and address information:

    1. Before changing the DECnet address, add the access rights to the server
       for the new node name.

	$ MCR DNS$CONTROL
	DNS> ADD ACCESS <new_nodename>::DNS$SERVER CLEARINGHOUSE - 
	_DNS> <clearinghouse_name>/RIGHTS = (READ,WRITE,DELETE,TEST,CONTROL)

	DNS> ADD ACCESS <new_nodename>::DNS$SERVER  OBJECT -
	_DNS> <clearinghouse_name>/RIGHTS = (READ,WRITE,DELETE,TEST,CONTROL)
	DNS> EXIT
	$

    2. Execute SYS$MANAGER:NETCONFIG.COM to change the node name and address

	$ @SYS$MANAGER:NETCONFIG.COM

		(answer the prompts)

    3. Reboot the system

    4. Create the new default namespace file 	

	$ SOL :== $DNS$SOLICIT
	$ SOL NS_DUMP
	$

    5. Get rid of any DNS$DEFAULT_FILE.DATs in SYS$SPECIFIC:

	$
	$ DELETE SYS$SPECIFIC:[SYSEXE]DNS$DEFAULT_FILE.DAT;*
	$

    6. Point the client to the namespace 	

	$
	$ COPY SYS$SHARE:DNS$NS_DEF_FILE.DAT SYS$SYSTEM:DNS$DEFAULT_FILE.DAT
	$

    7. Reload the ns cach with the new nameserver address
        $ 
	$ SOL LOAD
	$

    8. Update the root directory

	$
	$ MCR DNS$CONTROL
	DNS> UPDATE DIR .
	DNS> EXIT
	$

    9. All done.


    Note: If you get an error on the "UPDATE DIR ." command, then repeat the
    last two steps. 

    It depends on the configuration of your namespace.
    
    1 If you are not a server and only a client then changing your address
      (in DECnet Phase IV) is easy.
    
    2 If you are a server and you have exactly only one clearinghouse in the
      namespace and it is on your local node, then it is easy.
    
    3 If you are a server and you are part of a larger namespace and have
      one or more clearinghouses then it is not real easy.
    
    4 If you are going to change addresses (Phase IV to Phase IV) and not
      change your node name, this is the easiest.
    
    5 Changing the node name adds some complications.
    
    If you have the simple case, 2 above, just changing addresses, and you
    have the only clearinghouse of your namespace local, then here is
    what you need to do:

    1. Before changing the DECnet address, add the access rights to the server
       for the new node name.

        $ MCR DNS$CONTROL
        DNS> ADD ACCESS <new_nodename>::DNS$SERVER CLEARINGHOUSE -
        _DNS> <clearinghouse_name>/RIGHTS = (READ,WRITE,DELETE,TEST,CONTROL)

        DNS> ADD ACCESS <new_nodename>::DNS$SERVER  OBJECT -
        _DNS> <clearinghouse_name>/RIGHTS = (READ,WRITE,DELETE,TEST,CONTROL)
        DNS> EXIT
        $

    2 Change the address of the system:

    - check your MODPARAMS.DAT file to see if the SCSNODE and SCSSYSTEMID
      are set. If so, change the SCSSYSTEMID to reflect the new address
      SYSSYSTEMID = (area # * 1024) + node #
    
    - shut down DECnet
    
    - Change the Exec address
      NCP PURGE NODE new-address ALL
      NCP DEFINE EXEC ADDRESS new-address
    
      Note, you could use SYS$MANAGER:NETCONFIG.COM to do the above, but
      it will create new files for defining network objects and may
      cause problems if you are running a VAXcluster.

    - SYSGEN
      SET SCSSYSTEMID new-id  (if changed in MODPARAMS)
      WRITE CURRENT
      EXIT
    
    - EDIT your system startup files to keep DNS from attempting to start
      Also edit out the startup of anything that depends on DNS
    
    - REBOOT
    
    - After the system comes up you should have a normal system at the new
      address but without the DNS Server
    
    3 Update the default namespace files

    - MCR DNS$SOLICIT NS_DUMP

    - Now look up the physical address of your system

      NCP SHOW EXEC STATUS
      Note the Physical Address

      or
      TYPE SYS$LIBRARY:DNS$NS_DEF_FILE.DAT  (the file created by DNS$SOLICIT)
      and note the clearinghouse address
    
    - EDIT SYS$SYSROOT:[SYSEXE]DNS$DEFAULT_FILE.DAT
      and change the clearinghouse address for the clearinghouse on
      your system to be the new physical address.
    
      note: I use this technique so I can preserve any other namespaces
            that may be defined in my SYS$SYSROOT:[SYSEXE]DNS$DEFAULT_FILE.DAT
            file. If you have been using DFS to mount remote disks it is
            likely that you have at least one other namespace defined. On
            my system I have DEC: in addition to my private namespace.

    - START DNS
    
    That should do it.
    
    If anyone sees something I missed, please jump in and correct me!!!
    
    s/rob
    

Thanks for the info. I will try it out. 

Cheers,
Louis

I guess I should have mentioned this in .0. What happens if we setup DECmcc on 
a workstation, and then copy the setup ( image backup of disks ) to another 
system, and try to use the new system. I notice that the hardware address is
kept in one of the DNS attributes -

DNS> show nameserver

Namespace name _____________________ sprnet_ns
Name Server state __________________ On
UID ________________________________ aa-00-04-00-01-ec-60-8e-f8-45-12-4f-94-00

The UID is made up partly of the DECnet address, and partly of the Ethernet 
address. 

What we are doing is setting up DECmcc workstations for customers from
our office. To make life easy, we want to have one standard DECmcc system setup, 
which we then copy to the new hardware as it arrives, and simply change the 
DECnet address/name to what the customer requires. This would be easiier than 
having to do the entire install from scratch.

Cheers,
Louis

    I would not reccomend this. VMS doesn't support this either. Also,
    keep in mind that licenses must be correct and you cannot clear out
    the old ones in any easy way.
    
    If you must do this sort of thing, I suggest you do NOT create the
    namespace in advance. There is no supported way of copying a nameserver
    and changing it's namespace name or clearinghouse names. I do not
    think you want system at lots of sites with all the same namespace
    name.
    
    I suggest you create a command procedure that after the instalation of
    DNS at the customer site so you can have all the addresses and DECnet
    node names correct, it will go out and create all the needed
    directories and apply access control as needed.
    
    Remember, (and yes this isn't good news) if you clone systems built
    on the EASYnet and install them at customer sites, you may have trouble
    getting support for problems that come up since this is something that
    has been frowned apon officially for a decade.
    
    If you are going to plan on installing DECmcc systems at customer sites
    and each is to have it's own local namespace then I suggest planning
    around the use of V1.2 of DECmcc which has the ability to use a
    namespace that is local and not based on DECdns. This makes it much
    easier to build evaluation systems, demo systems and to prebuild
    systems.
    
    s/rob

I am about to change a customer's MCC (v1.1)/private namespace node's address, 
from 1.54 to 10.54 (lets say). I was very pleased to see an entry such as this
until I read replies .2 and .3, both discuss changing address but both give the
first step as:-

        $ MCR DNS$CONTROL
        DNS> ADD ACCESS <new_nodename>::DNS$SERVER CLEARINGHOUSE -
        _DNS> <clearinghouse_name>/RIGHTS = (READ,WRITE,DELETE,TEST,CONTROL)

        DNS> ADD ACCESS <new_nodename>::DNS$SERVER  OBJECT -
        _DNS> <clearinghouse_name>/RIGHTS = (READ,WRITE,DELETE,TEST,CONTROL)
        DNS> EXIT
        $

My confusion starts here, if I'm only changing the address and not the node name
where does the <new_nodename> come in?

Am I missing something here?

Thanks,

Tony.

    Check your existing namespace to see if you have control in the listed
    areas. If so, you are set, if not, you may not after the changes.
    
    I agree that it shuold not be needed but folk from DNS engineering
    made that suggestion to me so I included it.
    
    s/rob