[Info-vax] Stumped by DECnet proxies in a cluster (NETPROXY)

[JF Mezei]

Decnet 4. VAX:7.3    ALPHA:8.3 in a cluster.

Renamed my venerable VAX node from "VELO" to "VELOVX" to allow my new
Xserve to get the "VELO" name.

That VAX system "image" has had the name "VELO" for 20 years so this was
a strange occasion.

I was stumped by my ALLIN1 documents no longer being accessible. This
lead me to decnet proxy problems.

On the VAX:

> $ show log netproxy/full
>    "NETPROXY" [exec] = "$DISK4:[VMS$COMMON.SYSEXE]NETPROXY.DAT" (LNM$SYSTEM_TABL
> E)
> $ show log $disk4/full
>    "$DISK4" [exec] = "$11$DQA0:" [concealed,terminal] (LNM$SYSTEM_TABLE)


On the Alpha:

> $ show log netproxy/full
>    "NETPROXY" [exec] = "$DISK4:[VMS$COMMON.SYSEXE]NETPROXY.DAT" (LNM$SYSTEM_TABL
> E)
> $ show log $disk4/full
>    "$DISK4" [exec] = "$11$DQA0:" [concealed,terminal] (LNM$SYSTEM_TABLE)

On both nodes, a "DIR/NOHEAD/FILEID NETPROXY" yields the same file, same
file ID.

Why is then that AUTHORIZE on VELOVX:: and CHAIN:: yields different
results to UAF> SHOW/PROXY *  ????????????

I can made additions/deletions on one node and they are not reflected on
the other node. Yet they shoudl all be acting on the same file.



OK, after restarting DECnet a couple of times and removing "alias
incoming", I can now do dir 0:: with success. However, that doesn't
explain why AUTHORIZE shows different databases when the logicals point
to the same one.

(I also have NET$PROXY defined the same on both nodes, and the Security
server has that file opened).