DECNET

[Tim Pride]

Just installed VMS7.3-2 on a new disk, TCPIP works fine BUT DECnet only works for tcpip supported services, eg FTP, Telnet but when I use SET HOST newnode : I get "%SYSTEM-F-UNREACHABLE remote node is not currently reachable" also same msg if I try from another node to newnode. Have tried sys$manager:net$configure advanced many times, have read and tried many tips from forums. Attached is a print of collected data. I need help not just "use config"

[Duncan Morris]

Hi Tim,

welcome to the ITRC OpenVMS forum.

The first item I spotted in your attachment was this line from the session control counters of the failing node.

Access Control Violations = 5

If this is a new node in the domain, does it possibly need to have access enabled to/from the domain?

I have only used LOCAL and DECDNS in the past, and I know that setting up access control for DECDns could be quite painful.

Can you try a simple SET HOST nnnnn, where nnnnn is the SCSSYSTEMID of the target node?
This would avoid name to address translation.

Duncan

[Volker Halle]

Tim,

DECnet-Plus provides different transports and different directory services for name to address translations.

You seem to not have configured the LOCAL directory service. This prevent DECnet from translating the local host name and also the remote host name GD2089.

If you want to use NSP transport or DECnet Phase IV addresses, you should also define the LOCAL namespace.

On the other hand, you seem to not have defined OSI transport (including DECnet-over-IP), which also needs TCPIP PWIPDRIVER to be started. This will prevent you from using DECnet-over-IP.

To skip name to address translation problems, specify the remote node DECnet (or IP) addresses with SET HOST (not SCSSYSTEMID, but the DECnet NSP address e.g. 15.990). Or use the IP address to test whether DECnet-over-IP works (SET HOST 193.247.236.208).

I noted that you seem to be using different node names in DECnet and TCPIP, this is not very helpful for troubleshooting.

Volker.

[Tim Pride]

Hi Volker and Duncan,

I have to work with Aplpha's on a remote network, must use set h nodeName.
I really apprecite your replies.
Our Network, with many MS nodes, is controlled by an MS/Network expert and thus the many names!! The node GD2099 is IMS0205 is IMSF205, that is how they like it!
This is a new node, TCPIP seems to work with FTP, Telnet etc..
Set host does not work with TCP address or node name.
In the net$configure the Qu. Decnet over TCPIP the answer was Yes.
Have seen that the Show Net/Full decnet for an established node has far more info and have tried in vain to get them similar!
I shall try config with [LOCAL,DOMAIN] once more!

[Tim Pride]

Here is the result of another go at the Config with LOCAL,DOMAIN, plus main points of config answers!

[Colin Butcher]

Hello Tim,

This might help you with some of the background: http://h71000.www7.hp.com/openvms/journal/v5/index.html#decnet

A diagram of your configuration would be most helpful. Reading your notes it seems that your main interest is using DECnet over IP to reach a node outside the local LAN, not using DECnet native within the local LAN.

DECnet over IP needs both the PWIP driver enabled and the DOMAIN name service added to the list of name resolvers when you do the naming part of NET$CONFIGURE. I usually specify 127.0.0.1 (localhost) as the DOMAIN name service provider - that way the local node's BIND resolver can use a local hosts file and will also then chase down the list of DNS servers. For machines with static IP addresses (like the Alphas) this lets you remove a layer of complexity.

Something else to check is the number of NICs in the machines and which physical path you're actually using. Remember that DECnet Phase IV compatible addressing is per node, while IP addressing is per interface. Another thing to check is that all the software licences are valid and active.

If you still end up in difficulties it may be worth having someone else come to help you and teach you how to set up and debug this kind of configuration.

Good luck!
Cheers, Colin.

[Tim Pride]

Hi Guys,
Thanks for your help, I reconfgured with LOCAL plus a bit of guess work, followed by running sys$system:decnet_reister.exe and it works the new node is reachable by my local nodes and the new node reaches the local nodes.
I assume that I must register the node names of the remote network before I can set host to them ?? Or is there an automatic way of doing it??
Network is three node alphas and routed out to a larger network with many nodes, but my access is restricted!

[Volker Halle]

Tim,

if you want/need to use the DECnet node names for communication, you need to register them in DECNET_REGISTER first. If you have other nodes in your network running DECnet-Plus with a fully populated DECnet registry, you can export node name definitions on that node and import them on your local node.

Volker.

[Tim Pride]

I reconfigure as LOCAL not as DOMAIN,
and registered the nodes.