The Question is:
We have two clustered alpha's, each at OpenVMS 6.2. NCP Show Known Nodes
returns the same list from either alpha. We can do a NCP Connect Node SERV1
from one of the alpha's but the other just returns a "%SYSTEM-F-TIMEOUT,
device timeout" error message.
It is possible to do a NCP Connect Via EWA-0 Physical Address and make the
connection. What is causing this behavior?
The Answer is :
Unknown. Please contact the Customer Support Center as details
of the local DECnet configuration, of the network controllers
involved, of the network cabling and termination, and of the
of the MOP/DAP target SERV1 host will be required. In particular,
the particular settings of the SERV1 host in the DECnet database
for both hosts would be of interest.
TCP/IP Services is completely unrelated to this.
DECnet itself is only related to this discussion for its MOP
capabilities (and for the storage of certain information in its
database), LANCP (OpenVMS V6.2 and later) or other similar tool
would serve equally as well as an alternative mechanism for
establishing the remote console connection.
For the list of files that are typically shared within an OpenVMS
Cluster, please see SYLOGICALS.TEMPLATE on OpenVMS V7.2 and later,
and see the list of files included in the OpenVMS FAQ section "How
can I split up an OpenVMS Cluster?"