[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference help::decnet-osi_for_vms

Title:DECnet/OSI for OpenVMS
Moderator:TUXEDO::FONSECA
Created:Thu Feb 21 1991
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:3990
Total number of notes:19027

3886.0. "DECnet-Plus only recognised limited nodes" by ZGOMIF::HWLEE () Sat Feb 22 1997 06:49

    
    
    Hi,

I am currently setting up a new node, a Alphaserver 2100.
FIS with OpenVMS v7.1; DECnet-Plus for OpenVMS 7.1.

I have configure it to be a single node cluster with a cluster alias.
Upon bootup:
   DECdtm complains that the logicals:  SYS$NODE and SYS$NODE_FULLNAME
   is not define.

   It does not recognised nodes that it recognised before the reboot.
   
   running decnet_loc_register says it can load a maximum of 960 nodes.

   running CDI$TRACE shows it looking up it owns name 99.9% of the time.

Anyone has any idea what I may done wrong with my configuration?

I also suspect I may need some ECO/patches to be installed but al the 
entries in this note are talking about OSI 6.2 'n 6.3 etc... nothing about 
DECnet-Plus 7.1.   Any help/suggestion???  

Thanks very much.
...lee...
T.RTitleUserPersonal
Name		DateLines
3886.1Does rename fix it?ipng::CARSONPete Carson, Networks for OpenVMS EngineeringMon Feb 24 1997 16:1612
1. Make sure the name of the node is what you think it is.


	mcr ncl sho name

>>   running decnet_loc_register says it can load a maximum of 960 nodes.

	Is this used anymore?  (Anyone know?  I don't think so.  I believe
	it's only there for upgrade.)  I think what you 
	should do is use decent_register.  Can you see the
	node specified in 1.?
3886.2ZGOMIF::HWLEEMon Feb 24 1997 20:4016
Hi,

Upon reboot, mcr ncl show name shows a blank name.

I have to do net$configure using option (2) taking all the default answer to
define the name.

After that, thing are better until the next reboot.

Regarding the nodename not reachable, now I issue the following command..

  $mc ncl flush session control naming cache entry "nodename"

Now, the nodename is reachable.
3886.3DAVIDF::FOXDavid B. Fox -- DTN 285-2091Tue Feb 25 1997 09:379
Re: .1

Hi Pete!

As far as I know, the only reason why DECNET_LOC_REGISTER still ships is because
it can clear the DNS Clerk Cache.  When you execute it you are warned that that
is the only supported function.

	David
3886.4Maybe FIS problem?BACHUS::VANLOOCKPatrick DTN 856-8648Fri Feb 28 1997 08:1815
    Hi,                                             
    
    I've faced a similar problem: in 'my' case: this system came factory
    installed with V7.1 and configured for using DNS (as clerk only) in
    already existing namespace.
    Phenomenon was that after every second reboot,sys$node was not set correctly. 
    Running net$configure and taking all proposed defaults cured, next reboot ok 
    but 2nd reboot: again same problem.  
    
    Re-installing VMS 7.1 + DECnet-plus 7.1 from CD cured!
    
    Maybe there is a problem with FIS??
    
    Patrick
3886.5Is the latest V7.1 NET$STARTUP.COM on FIS? BULEAN::TAYLORMon Mar 03 1997 21:537
    Is there be any difference in the NET$CONFIGURE.COM
    or the NET$STARTUP.COM between the 2 versions?
    
    Thanks,
    
    Pat