[Info-vax] Changing Decnet node name and address????

Jairo Alves jairo.ptbr at gmail.com
Fri Apr 5 10:42:06 EDT 2019


Sorry to relive the thread, but I needed to just say thanks to 
Mr. Steve Sparrow, I was having problems with DECNET proxies
not working by name, while working by decnet number.

I did the mcr decnet_register to create the entry and then
mcr ncl flush session control naming cache entry "*" 
command to force it live and it started worked again.

Thanks!

Em sexta-feira, 5 de junho de 1998 04:00:00 UTC-3, Steve Sparrow  escreveu:
> TK wrote:
> > 
> > Has anyone tried to change the Node Name, Address for Decnet (NCP) and
> > the Cluster Node Name?  Is this fairly common?  Is it hard?  I've
> > tried looking in my NCP manual and cannot find it.  Nor is it in the
> > Cluster Manual.  Does anyone know where I can find info on this?
> > Thanks in advance.
> > 
> > tk
> 
> Where I work, we change nodenames and DECnet IV address quite often
> for satellite nodes. It's rather involved if you haven't done it.
> Changing this for a standalone node is easy.
> 
> Keep in mind the following rules:
>   The system parameter SCSNODE defines the nodename
>   The system parameter SCSSYSTEMID defines the address in a form of
>       area * 1024 + number
> 
>   The DECnet nodename is changed with the following commands:
>       define/user netnode_remote -
>          'f$parse("netnode_remote","sys$system:",".dat;")'
>       MCR NCP DEFINE NODE oldname NAME newname
> 
>   The DECnet address is is changed with the following commands:
>       define/user netnode_local -
>       	 sys$sysdevice:[sys55.sysexe]netnode_local.dat
>       MCR NCP DEFINE NODE newname ADDRESS oldarea.newnumber
> 
>   The SCSNODE and DECnet node NAME must match.
>   The SCSSYSTEMID and the DECnet (Area *1024 + Number) must match.
> 
> Also,
>   Imagine that there is a secret decoder ring that consists of your
>       SCSNODE name combined with the SCSSYSTEMID number.
>       If either part of this "key" is used separately, without 
>       the other, the remainder of the cluster will deny membership
>       to the new node. You might also be denied use of the new 
>       nodename and address that you attempt to use unless you 
>       shutdown the entire cluster and boot it back up.
> 
> If the node is a satellite, edit NETNODE_UPDATE.COM
>   define netnode_update -
> 	'f$parse("netnode_update","sys$system",".com;")'
>   edit/edt netnode_update:
>   *Substitute/NODE oldname/NODE newname/W
>   *Substitute/Address oldarea.oldnumber/Address oldarea.newnumber/W
>   *exit
>   Apply the change with:
>     @netnode_update:
>     mcr sysman set env/cluster
>     SYSMAN> do mcr ncp set NODE oldname NAME newname
>     SYSMAN> do mcr ncp set NODE newname ADDRESS oldarea.newnumber
>     SYSMAN> exit
>   Deassign netnode_update
> 
> Change the node's DECnet name and address.
>   define/user netnode_remote -
> 	'f$parse("netnode_remote","sys$system",".dat;")'
>   mcr ncp define NODE oldname NAME newname
>   define/user netnode_local  -
> 	'f$parse("netnode_local", "sys$system",".dat;")'
>   mcr ncp define EXEC ADDRESS oldarea.newnumber
> 
> Change the node's SCSNODE and SCSSYSTEMID:
>   Define root sys$sysdevice:[sys55.sysexe]
>   create editedt.ini
>   deck/dollar=END_INI
>   Substitute/SCSNODE=oldname/SCSNODE=newname/W
>   Substitute/SCSSYSTEMID=oldid/SCSSYSTEMID=newid/W
>   Exit
> END_INI
>   edit/edt/comm=editedt.ini root:modparams.dat
>   edit/edt/comm=editedt.ini root:setparams.dat
>   edit/edt/comm=editedt.ini root:params.dat
>   edit/edt/comm=editedt.ini root:agen$feedback.dat
> 
> Make the SCSNODE and SCSSYSTEMID effective:
>   If the node is up use @sys$update:autogen getdata setparams
>   If the node is not up, use the following:
>   VAX: Define/user params root:vaxvmssys.par
>   AXP: define/user params root:axpvmssys.par
>        mcr sysgen
>        SYSGEN> use params:
>        SYSGEN> set scsnode=newname
>        SYSGEN> set scssystemid=newid
>        SYSGEN> write params:
>        SYSGEN> exit
> 
> Change the cluster alias NAME:
>   define/user netnode_remote -
> 	'f$parse("netnode_remote","sys$system:",".dat;")
>   mcr ncp define NODE oldaliasname NAME newaliasname
>   mcr sysman set env/cluster
>   SYSMAN> do mcr ncp set NODE oldalias NAME newaliasname
>   SYSMAN> do define/sys/exec sys$cluster_node newaliasname::
> 
> Change the cluster alias ADDRESS:
>   loop: local = f$search("disk:[sys*.sysexe]netnode_local.dat")
>         if local .eqs. "" then exit
> 	define/user netnode_local &local
> 	mcr ncp define exec alias node oldarea.newarea
> 	goto loop
>   mcr sysman set env/cluster
>   SYSMAN> shutdown/reboot/cluster
> 
> 
> Should you change a nodename,address,aliasname,aliasaddress?
> Search all your files on the system looking for your oldname
> or the oldaliasname. These files will have to be changed.
> You'll find most of these in the startup files. Some of these
> will be in DECnotes files, DECplan database, PCMS*DFS nodenames...
> 
> If you have DECnet objects set the way you want them, don't
> ever run @sys$manager:netconfig.com anymore, it wipes the objects
> out.
> 
> 0ne more thing, enable the alias on the FAL decnet object
> MCR NCP DEFINE OBJECT FAL NUMBER 17 ALIAS OUTGOING ENABLED
> On the fast systems, MCR NCP SET OBJ FAL ALIAS INCOMING ENABLED
> 
> You can use four11.com to find my home number by searching
> my old defunct email address that I'm currently using.
> 
> Steve in Fort Worth




More information about the Info-vax mailing list