where DECnet *might* get confused.
Well, this is easy enough to test experimentally. I've disabled the
redundant Multinet links on LEGATO, so in theory there should be no
redundancy now at least as far as LEGATO goes.
This means not only disabling the direct links from LEGATO to other bridge
nodes (e.g. GORVAX, SG1) but _also_ the links from LEGATO to other nodes
that in turn have Multinet links to bridge nodes (STUPI, FRUGAL, ROOSTA).
In theory I suppose the latter step is excessive since we can assume that a
two hop path would always cost more than a one hop path, but there's no
guarantee of that. So just to be safe this absolutely eliminates redundant
paths.
I think that leaves me with area 54, CIERE, as the only machine that
_only_ gets its connectivity thru LEGATO. That link I've left turned on.
Now LEGATO sees the path to everything except CEIRE as being thru the
bridge (QNA-1), which is what we'd expect.
OpenVMS Network status for local node 2.1 LEGATO on 5-JAN-2012
08:11:19.43
Area Cost Hops Next Hop to Area
1 4 1 QNA-1 -> 1.300
CTAKAH
2 0 0 (Local) -> 2.1
LEGATO
3 7 2 QNA-1 -> 19.41
SG1
4 4 1 QNA-1 -> 4.249
SLAVE
5 14 4 QNA-1 -> 19.41
SG1
6 4 1 QNA-1 -> 6.1
STAR69
8 7 2 QNA-1 -> 19.41
SG1
11 4 1 QNA-1 -> 11.2
MAISA
19 4 1 QNA-1 -> 19.41
SG1
20 14 2 QNA-1 -> 19.41
SG1
33 7 2 QNA-1 -> 19.41
SG1
42 4 1 QNA-1 -> 42.1
CANADA
52 10 3 QNA-1 -> 19.41
SG1
54 2 1 TCP-0-54 -> 54.59
CEIRE
59 7 2 QNA-1 -> 19.41
SG1
Try your file copies again and see if anything changes...
Bob