How to set Decnet MAX LINKS on 8.3 on integrity server?

[Paul Goslin Rae McCarth]

OpenVMS 8.3 on Integrity...
A user requested we increase the Decnet Max Links to 256... having problems getting it set/assigned:

Could you please increase the number of DECnet maximum links on archer? It is currently at 0 and we need 256 like it is on tbird. This can be seen with the command:
$ mcr ncp show executor characteristics
and can be set with the command
$ MCR NCP SET EXECUTOR MAXIMUM LINKS 256
or you may have to use NCL instead of NCP but in that case I don't know the command.
-----------------------
I'm grasping @ straws trying to help him...

[Phillip Thayer]

Try using the following:

MCR NCP SET EXECUTOR MAXIMUM LINKS 256
MCR NCP DEFINE EXECUTOR MAXIMUM LINKS 256

Decnet uses two databases, Volatile and Permanent. The SET command will change the Volatile database and DEFINE will set the permanent database.

Phil

[Dean McGorrill]

for decnet +
$ MCR NCL SET NODE 0 NSP MAXIMUM TRANSPORT CONNECTIONS 256
$ MCR NCL SET NODE 0 OSI TRANSPORT MAXIMUM TRANSPORT CONNECTIONS 256

[Hoff]

Here's a one-page intro to NCP

http://64.223.189.234/node/271

[Volker Halle]

Paul/Rae,

having your user report DECnet maximum links being 0 is most likely the result of using NCP SHOW EXEC CHAR on a DECnet-OSI/DECnet-Plus node. This command does not report a maximum links value.

Identification = DECnet-OSI for OpenVMS
Management version = V4.0.0
Incoming timer = 0
Outgoing timer = 0
NSP version = V4.1.0
Maximum links = 0
...

For DECnet-Plus, you need to check the equivalent values with:

MC NCL> SHOW NSP MAXIMUM TRANSPORT CONNECTIONS
MC NCL> SHOW OSI TRANSPORT MAXIMUM TRANSPORT CONNECTIONS

You might want to find out about the real problem behing this question...

Volker.

[Colin Butcher · Accepted solution]

Hi,

If you're running DECnet-Plus (Phase V) then the easy way is to re-run NET$CONFIGURE in ADVANCED mode (@sys$startup:net$configure advanced) and change the NSP and OSI transport configurations by increasing the maximum number of connections from 200 (the default) to a bigger number. You might as well make it 1000 or 2000 - there's little or no penalty for that on a large memory machine like the Integrity boxes.

All the DECnet-Plus configuration is help in the NCL script files in SYS$STARTUP: You can edit these manually and re-execute them if you wish, or you can simply type the individual command at the NCL prompt, however the scripts need to be changed so that it happens next time the network is started. That's why it's a good idea to use NET$CONFIGURE unless you are thoroughly familiar with what you're changing.


If you're running DECnet Phase IV then NCP DEFINE EXECUTOR MAXIMUM LINKS for the permanent database and SET EXECUTOR ... for the volatile database.


If you want some background to DECnet-Plus then this might help: http://www.downloads.xdelta.co.uk/vmstjv5%20feb2005/decnet%20article%20vms%20tj%20v5%20feb2005.pdf, as might some of the other stuff at http://www.hpug.xdelta.co.uk

Cheers, Colin (http://www.xdelta.co.uk).

[Paul Goslin Rae McCarth]

Thanks for all the suggestions !!

We're apparently running Decnet +

I re-ran the net$config in advanced mode and increased both the NCP and OSI to 1000 as recomended, then I rebooted and all seems well...

[Paul Goslin Rae McCarth]

Closing thread...