[HECnet] Asymmetric connectivity in a cluster
Johnny Billquist
bqt at softjar.se
Mon Apr 23 10:30:40 PDT 2018
On 23.04.18 19:13, Johnny Billquist wrote:
> On 23.04.18 02:14, dwe-6006 at philtest.org wrote:
>> I agree with you, on the other hand they should be consistently the
>> wrong thing in consistently the same way L
>
> Who said they are acting differently?
> The thing is, RODNEL *knows* who ADV1 is, but ADV1 does not know RODNEL,
> and you cannot define RODNEL on ADV1 using NCP. You are using DECnet+...
Sorry, that should have been ADV2, and not ADV1.
Your "SHOW KNOWN NODES" on the two nodes tells is clearly, as do the
error messages when you try to SET NODE ... on ADV2.
The Cluster system also have a different way of knowing of members,
which is why you can somewhat see and know about RODNEL anyway, but you
need to properly have the nodes known in DECnet as well, and NCP is not
the way in DECnet+.
Johnny
>
> Johnny
>
>>
>> --Dave
>>
>> *From:*Johnny Billquist [mailto:bqt at softjar.se]
>> *Sent:* Sunday, April 22, 2018 7:11 PM
>> *To:* hecnet at Update.UU.SE; dwe-6006 at philtest.org
>> *Subject:* Re: [HECnet] Asymmetric connectivity in a cluster
>>
>> I haven't really looked at what this might be, but one reflection is
>> that ncp is not really the right tool of you're running decnet+.
>>
>> Johnny
>>
>> dwe-6006 at philtest.org <mailto:dwe-6006 at philtest.org> skrev: (23 april
>> 2018 01:01:28 CEST)
>>
>> I’m not sure that asymmetric is the correct description but I can’t
>> think of a better term. I am using SIMH and I have a two node
>> cluster (with a quorum disk) the two nodes have a common system disk.
>>
>> The two nodes are RODNEL (1.1) booting from SYS0 and ADV2 (1.3)
>> booting from SYS2. Both are running DECnet Plus both are running
>> Multinet for the IP stack. At one time there was also a node (never
>> actually a member of the cluster called HCBVAX (1.2) it booted from
>> SYS1 but it no longer exists.
>>
>> The nodes are connected over an Ethernet and the MAC addresses are
>> the ones that I would expect AA-00-04-00-01-04 (1.1) and
>> AA-00-04-00-03-04 (1.3) HCBVAX was AA-00-04-00-02-04 (1.2)
>>
>> I can login to RODNEL and “set host adv2” with no problem, I can
>> login to ADV2 and “set host rondel” with no problem. On each of the
>> nodes I can “show cluster” and I see what I expect to see with no
>> errors. While logged in to RODNEL the command “moni cluster” works
>> fine. While logged in to ADV2 the wheels seem to fall off the bus –
>> “show cluster” is fine but “moni cluster” isn’t Any help would be
>> appreciated. This is the information that I have gathered so far (I
>> am not happy with the forwarding address in the error message from
>> “moni proc” on ADV2 which seems to arise from RODNEL
>>
>> --Dave
>>
>> View of Cluster from system ID 1027 node: ADV2 22-APR-2018
>> 22:24:50
>>
>> +-----------------------------+
>>
>> ¦ SYSTEMS ¦ MEMBERS ¦
>>
>> +-------------------+---------¦
>>
>> ¦ NODE ¦ SOFTWARE ¦ STATUS ¦
>>
>> +--------+----------+---------¦
>>
>> ¦ ADV2 ¦ VMS V7.3 ¦ MEMBER ¦
>>
>> ¦ RODNEL ¦ VMS V7.3 ¦ MEMBER ¦
>>
>> +-----------------------------+
>>
>> ^Z
>>
>> $
>>
>> $ moni cluster
>>
>> %MONITOR-I-ESTABCON, establishing connection to remote node(s)...
>>
>> %%%%%%%%%%% OPCOM 22-APR-2018 22:24:56.75 %%%%%%%%%%%
>>
>> Message from user SYSTEM on RODNEL
>>
>> Event: Address Unreachable PDU Discard from: Node LOCAL:.RODNEL
>> Routing,
>>
>> at: 2018-04-22-23:24:56.740-04:00Iinf
>>
>> Discard Reason=Destination Addrs Unknown,
>>
>> Source Address=49::00-01:AA-00-04-00-03-04:21,
>>
>> Forwarding Address=49::00-01:AA-00-04-00-02-04:21
>>
>> eventUid FC95D640-467B-11E8-99E1-AA0004000104
>>
>> entityUid 5683CC80-467B-11E8-8004-AA0004000104
>>
>> streamUid 5A113900-467B-11E8-8004-AA0004000104
>>
>> Still on ADV2 - NCP is odd as well:
>>
>> $ mcr ncp
>>
>> NCP>sho exec char
>>
>> Node Volatile Characteristics as of 22-APR-2018 22:31:17
>>
>> Executor node = 1.3 (ADV2)
>>
>> Identification = DECnet-OSI for OpenVMS
>>
>> Management version = V4.0.0
>>
>> Incoming timer = 0
>>
>> Outgoing timer = 0
>>
>> NSP version = V4.1.0
>>
>> Maximum links = 0
>>
>> Delay factor = 0
>>
>> Delay weight = 0
>>
>> Inactivity timer = 0
>>
>> Retransmit factor = 0
>>
>> Routing version = V2.0.0
>>
>> Type = nonrouting IV
>>
>> Routing timer = 0
>>
>> Subaddresses = 0
>>
>> Broadcast routing timer = 0
>>
>> Maximum address = 0
>>
>> Maximum circuits = 0
>>
>> Maximum cost = 0
>>
>> Maximum hops = 0
>>
>> Maximum visits = 0
>>
>> Maximum area = 0
>>
>> Max broadcast nonrouters = 0
>>
>> Max broadcast routers = 0
>>
>> Maximum path splits = 0
>>
>> Area maximum cost = 0
>>
>> Area maximum hops = 0
>>
>> Maximum buffers = 0
>>
>> Segment buffer size = 0
>>
>> Buffer size = 0
>>
>> Pipeline quota = 0
>>
>> Alias maximum links = 0
>>
>> Path split policy = Normal
>>
>> Maximum Declared Objects = 0
>>
>> NCP>show know nodes
>>
>> Known Node Volatile Summary as of 22-APR-2018 22:31:29
>>
>> Executor node = 1.3 (ADV2)
>>
>> State = on
>>
>> Identification = DECnet-OSI for OpenVMS
>>
>> NCP>def node rodnel
>>
>> Node address (1.1-63.1023): 1.1
>>
>> Node name (1-6 characters): rodnel
>>
>> NCP>set node rodnel all
>>
>> %NCP-W-UNRCMP, Unrecognized component
>>
>> NCP>set node rodnel
>>
>> Node address (1.1-63.1023): 1.1
>>
>> Node name (1-6 characters): rodnel
>>
>> %NCP-W-UNRCMP, Unrecognized component , Node
>>
>> NCP>exit
>>
>> Whereas RODNEL seems happier:
>>
>> NCP>sho exec char
>>
>> Node Volatile Characteristics as of 22-APR-2018 20:15:29
>>
>> Executor node = 1.1 (RODNEL)
>>
>> Identification = DECnet-OSI for OpenVMS
>>
>> Management version = V4.0.0
>>
>> Incoming timer = 0
>>
>> Outgoing timer = 0
>>
>> NSP version = V4.1.0
>>
>> Maximum links = 0
>>
>> Delay factor = 0
>>
>> Delay weight = 0
>>
>> Inactivity timer = 0
>>
>> Retransmit factor = 0
>>
>> Routing version = V2.0.0
>>
>> Type = nonrouting IV
>>
>> Routing timer = 0
>>
>> Subaddresses = 0
>>
>> Broadcast routing timer = 0
>>
>> Maximum address = 0
>>
>> Maximum circuits = 0
>>
>> Maximum cost = 0
>>
>> Maximum hops = 0
>>
>> Maximum visits = 0
>>
>> Maximum area = 0
>>
>> Max broadcast nonrouters = 0
>>
>> Max broadcast routers = 0
>>
>> Maximum path splits = 0
>>
>> Area maximum cost = 0
>>
>> Area maximum hops = 0
>>
>> Maximum buffers = 0
>>
>> Segment buffer size = 0
>>
>> Buffer size = 0
>>
>> Pipeline quota = 0
>>
>> Alias maximum links = 0
>>
>> Path split policy = Normal
>>
>> Maximum Declared Objects = 0
>>
>> NCP>sho kno node
>>
>> Known Node Volatile Summary as of 22-APR-2018 20:15:37
>>
>> Executor node = 1.1 (RODNEL)
>>
>> State = on
>>
>> Identification = DECnet-OSI for OpenVMS
>>
>> Node State Active Delay Circuit Next node
>>
>> Links
>>
>> 1.3 (ADV2) 1.1
>> (RODNEL)
>>
>> NCP>sho node adv2 char
>>
>> Node Volatile Characteristics as of 22-APR-2018 20:16:02
>>
>> Remote node = 1.3 (ADV2)
>>
>> Service password = 0000000000000000
>>
>>
>> --
>> Skickat från min Android-enhet med K-9 Mail. Ursäkta min fåordighet.
>>
>
>
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
More information about the Hecnet-list
mailing list