Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

DECNET default directory problem

DECNET default directory problem

Hello all.

I have three single nodes in network. From one I can see decnet default directory from the others, but not from himself.

NI21:SYSTEM> dir smni21::
%DIRECT-E-OPENIN, error opening SMNI21::*.*;* as input
-RMS-E-FND, ACP file or directory lookup failed
-SYSTEM-F-NOSUCHNODE, remote node is unknown

I was trying to play with route table, but nothing help. Thanks for the ideas.
10 REPLIES

Re: DECNET default directory problem

With localhost and IP address it's working.

NI21:SYSTEM> dir localhost::

Directory LOCALHOST::SYS$SPECIFIC:[FAL$SERVER]

NET$SERVER.LOG;6 NET$SERVER.LOG;5 NET$SERVER.LOG;4 NET$SERVER.LOG;3
NET$SERVER.LOG;2 NET$SERVER.LOG;1

Total of 6 files.
NI21:SYSTEM> dir 172.23.18.2::

Directory 172.23.18.2::SYS$SPECIFIC:[FAL$SERVER]

NET$SERVER.LOG;6 NET$SERVER.LOG;5 NET$SERVER.LOG;4 NET$SERVER.LOG;3
NET$SERVER.LOG;2 NET$SERVER.LOG;1

Total of 6 files.
Shilpa K
Valued Contributor

Re: DECNET default directory problem

Hi Dolezel,

The command seems to work correctly if you include username and password:

$ dir piano"system password"::

Regards,
Shilpa

Re: DECNET default directory problem

Unfortunately it's not problem with "username password".
Jan van den Ende
Honored Contributor

Re: DECNET default directory problem

Vaclav,

In DECnet, node 0 (zero) is always "self".

So, what does
$ dir 0::
give you?

If that _IS_ working, (which I would expect), then your local name definition is not (fully) correct.

For setting this correct, we need to know if you are using DECnet IV or DECnet V.

hth

Proost.

Have one on me.

jpe
Don't rust yours pelled jacker to fine doll missed aches.

Re: DECNET default directory problem

Dir 0:: is working correctly and DECNET is OSI.
Volker Halle
Honored Contributor

Re: DECNET default directory problem

If you carefully read the OpenVMS error message, you would see, that the underlying error is: SYSTEM-F-NOSUCHNODE, remote node is unknown

So the nodename SMNI21 cannot be resolved by DECnet.

There are multiple ways for DECnet to resolve host names, one of them is the local DECnet registry. Add the node name and DECnet address using MC DECNET_REGISTER.

Volker.

Re: DECNET default directory problem

I was expecting this, unfortunately this node it's there.

NI21:SYSTEM> mc decnet_register show node "*"

Directory Service: Local name file

Node name: LOCAL:.HOME.ASTRO
Phase IV synonym: ASTRO
Node address: 37:2041291266:00-3A:AA-00-04-00-64-E8:21 (58.100)
Node address: 37:2041291266:00-3A:AA-00-04-00-64-E8:20 (58.100)

Node name: LOCAL:.HOME.BETTY
Phase IV synonym: BETTY
Node address: 37:2041291266:00-01:AA-00-04-00-BB-07:21 (1.955)
Node address: 37:2041291266:00-01:AA-00-04-00-BB-07:20 (1.955)

Node name: LOCAL:.HOME.SMNI21
Phase IV synonym: SMNI21
Node address: 37:2041291266:00-CD:00-00-00-00-00-21:21
Node address: 37:2041291266:00-CD:00-00-00-00-00-21:20

Node name: LOCAL:.HOME.VENUS
Phase IV synonym: VENUS
Node address: 37:2041291266:00-01:AA-00-04-00-58-06:21 (1.600)
Node address: 37:2041291266:00-01:AA-00-04-00-58-06:20 (1.600)

Number of nodes reported on: 4
H.Becker
Honored Contributor

Re: DECNET default directory problem

There is a (cut & pase?) difference in your output for node SMNI21 and the other three:

SMNI21 shows no node number, while BETTY shows 1.955.

Did you try a "dir LOCAL:.HOME.SMNI21::"?
Volker Halle
Honored Contributor

Re: DECNET default directory problem

The DECnet registry entry for node SMNI21 looks a little bit different than the other entries. Is the missing DECnet Phase IV node address intentional ?

The key informations is in the output of MC NCL SHOW SESSION CONTROL NAMING SEARCH PATH. What does it say ?

If DECnet-over-IP (using the IP address) works, what happens if you use the FQDN (full IP name including domain name). Can this name be resolved from IP ? Does DIR smni21.domain-name work ?

Volker.
Oswald Knoppers_1
Valued Contributor

Re: DECNET default directory problem

You can run '$ mc cdi$trace' in one session while doing the failing directory command in another.

This will show you what type of name resolving is done.

You could try clearing the cache with the command:

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

Oswald