1 Dec
2020
1 Dec
'20
12:50 a.m.
Do VMS cluster group numbers need to be coordinated on HECnet? If so, is anybody taking
care of the coordination yet? I'm getting ready to set up a VAX cluster in my little
patch of area 2.
--
Mark J. Blair, NF6X <nf6x at nf6x.net>
https://www.nf6x.net/
1 Dec
1 Dec
1:40 a.m.
That's the 16 bit number used in the Local Area VAXcluster protocols, right? If so,
since it's a LAN-local protocol, it needs to be coordinated on a (bridged) LAN but not
across routers.
paul
On Nov 30, 2020, at 6:50 PM, Mark J. Blair <nf6x at
nf6x.net> wrote:
Do VMS cluster group numbers need to be coordinated on HECnet? If so, is anybody taking
care of the coordination yet? I'm getting ready to set up a VAX cluster in my little
patch of area 2.
--
Mark J. Blair, NF6X <nf6x at nf6x.net>
https://www.nf6x.net/
1:56 a.m.
On Nov 30, 2020, at 4:40 PM, Paul Koning
<paulkoning at comcast.net> wrote:
That's the 16 bit number used in the Local Area VAXcluster protocols, right? If so,
since it's a LAN-local protocol, it needs to be coordinated on a (bridged) LAN but not
across routers.
I'm not sure how it's used. The manual says it's a number from 1 to 4095 or
61440 to 65535 to uniquely identify each cluster system on a LAN, but it didn't
specifically state whether it's something that might pass through a DECnet router.
I'll arbitrarily pick 2622 (since the cluster alias node ID is going to be 2.622), and
hope for a low probability of conflict?
--
Mark J. Blair, NF6X <nf6x at nf6x.net>
https://www.nf6x.net/
2:35 a.m.
On Nov 30, 2020, at 7:56 PM, Mark J. Blair <nf6x at
nf6x.net> wrote:
That's just slightly muddled, but it basically confirms what I thought. That's
the LAVC protocol, which is the Ethernet version of the original CI-based cluster
protocols. It's a non-routable protocol, entirely unrelated to DECnet and invisible
to routers.
paul
On Nov 30, 2020, at 4:40 PM, Paul Koning
<paulkoning at comcast.net> wrote:
That's the 16 bit number used in the Local Area VAXcluster protocols, right? If so,
since it's a LAN-local protocol, it needs to be coordinated on a (bridged) LAN but not
across routers.
I'm not sure how it's used. The manual says it's a number from 1 to 4095 or
61440 to 65535 to uniquely identify each cluster system on a LAN, but it didn't
specifically state whether it's something that might pass through a DECnet router.
I'll arbitrarily pick 2622 (since the cluster alias node ID is going to be 2.622), and
hope for a low probability of conflict?
4:24 a.m.
On Nov 30, 2020, at 5:35 PM, Paul Koning
<paulkoning at comcast.net> wrote:
That's just slightly muddled, but it basically confirms what I thought. That's
the LAVC protocol, which is the Ethernet version of the original CI-based cluster
protocols. It's a non-routable protocol, entirely unrelated to DECnet and invisible
to routers.
Ok, thanks for the clarification.
--
Mark J. Blair, NF6X <nf6x at nf6x.net>
https://www.nf6x.net/
1248
days inactive
1249
days old
4 comments
2 participants
participants (2)
-
nf6x＠nf6x.net -
paulkoning＠comcast.net