STEINBERGER@KL.SRI.COM (Richard Steinberger) (04/20/87)
I would like to have a uVAX be in two DECNETs. One of them knows the machine as node 1.20. The other needs to know it as 11.153. Is this possible? The node that will know it as 11.153 will be connected through ASYNC DECNET and the other DECNET uses ethernet and a DEQNA board. Thanks for any suggestions. -Ric Steinberger steinberger@kl.sri.com -------
LEICHTER-JERRY@YALE.ARPA (04/21/87)
I would like to have a uVAX be in two DECNETs. One of them knows the machine as node 1.20. The other needs to know it as 11.153. Is this possible? The node that will know it as 11.153 will be connected through ASYNC DECNET and the other DECNET uses ethernet and a DEQNA board. There's certainly no straightforward way to do this, and I doubt it can be done at all. DECnet node number is a pretty fundamental attribute of DECnet; there has to be one node per number, and one number per node, on any given network. There's one exception to this: The cluster alias can provide an additional, distinct node number for a node. If you ran your node as a one-node Local Area VAXCluster - having paid the requisite license fee, of course! - you could then give it two numbers. Off hand, I don't know if you could get away with assigning numbers in different areas. Of course, this STILL might not solve your problem, since your node would then be known by BOTH numbers to BOTH nets. Which, in fact, only makes it clear that there are fundamental issues involved here anyway: If your node is a router, the two nets will instantly merge when it comes up. There are of isolating nets from each other (using lines set to undocumented protocols - this was discussed on this list a couple of days back). The intermediate "filter" node is still known by the same number to both nets, however. -- Jerry -------