|I'm using DECnet, but it is Phase V on Alphas, which has a different setup and command interface, so I can't only be vague in the commands to diagnose.|
First the basic Ethernet connection verification:
Of course one can connect the VAX directly to a hub via BNC. Are You sure the BNC connection is used ? There should be a switch and/or indicator showing AUI or BNC is selected.
Does the hub or switch indicate "link up" and activity?
If the hardware connection looks o.k., VMS DECnet software:
First enable the operator console on Your VMS terminal (-window), or better on a separate terminal window:
to see any system messages.
Check if DECnet is started and active on VMS:
NCP SHOW EXECUTOR is it in state ON ?
NCP SHOW KNOWN CIRCUIT is one ON ?
I assume the circuit name is ESA-0 (substitute for the correct one ...).
NCP SHOW COUNTERS KNOWN CIRCUITS
(or SHOW KNOWN CIRCUITS COUNTERS , don't know which is correct, use HELP SHOW from the NCP prompt).
Do counters show activity or only error counts ?
Is the address setup on both sides (Linux and VMS) agreeing ?
Since You (most probably) have no DECnet router in between, are all nodes in the same area ? The area is the first part of the address a.n .
If the Linux nodes are in 1.x then the VMS system must have an address 1.x as well.
Is the (non-)reachability symmetric ? What is the result of SET HOST linuxnode ?
Another point is to look at the Ethernet counters:
MCR LANCP SHOW DEVICE/COUNTERS
That's all I have to offer for the moment.
If there is no solution, maybe asking the question on the HP ITRC VMS forum (see link in my sig below) brings in somebody with a similar VAX and VMS version.
Joseph Huber, http://www.huber-joseph.de