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

[Peter Weaver]

>...
> 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.
>...
> (I also have NET$PROXY defined the same on both nodes, and the Security
> server has that file opened).
>...

I don't have the time right now to look up the details so this is off the
top of my head (which means it might be wrong), but I think NETPROXY.DAT and
NET$PROXY.DAT are not supposed to be shared in a cluster. So I would get rid
of the logicals and put each file in SYS$SYSROOT:[SYSEXE]. Also it seems to
me that when you ADD or MODIFY a proxy the command updates NET$PROXY.DAT and
NETPROXY.DAT since they are the permanent files and also modifies the
volatile database on the node where the command was issued. In other words,
if you change or create a proxy on one node and you are sharing the
permanent database the volatile database is only updated on one node until
the other node restarts DECNet.

As I said, it has been a long time since I had to trouble shoot DECNet
issues and I do not have time to check the docs right now, so I could be
wrong, but you may want to first check the cluster configuration manual and
see if the proxy files should be shared.

Peter Weaver
www.weaverconsulting.ca
Winner of the OpenVMS.org Readers' Choice Award for System
Management/Performance
http://www.linkedin.com/in/peterweaver