23 Apr
2018
23 Apr
'18
1:01 a.m.
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
23 Apr
23 Apr
1:11 a.m.
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 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.
2:14 a.m.
I agree with you, on the other hand they should be consistently the wrong thing in
consistently the same way :(
--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.
7:37 a.m.
It?s an SCS issue, not a DECnet issue. Unless you?ve configured one node to run cluster
communication over IP.
Hans
Verstuurd vanaf mijn iPhone
Op 23 apr. 2018 om 02:14 heeft <dwe-6006 at
philtest.org> <dwe-6006 at philtest.org> het volgende geschreven:
I agree with you, on the other hand they should be consistently the wrong thing in
consistently the same way L
--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 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.
7:13 p.m.
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+...
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
7:30 p.m.
On 23.04.18 19:13, Johnny Billquist wrote:
On 23.04.18 02:14, dwe-6006 at philtest.org wrote:
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
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+...
? Johnny
--
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
--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.
8:06 p.m.
On Monday, April 23, 2018 at 10:31 AM, Johnny Billquist wrote:
--
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
On 23.04.18 19:13, Johnny Billquist wrote:
Right. On a cluster system with multiple nodes booting from the same disk,
you can avoid this kind of confusion/problem if you correctly locate the
DECnet (NCP) databases in SYS$COMMON:[SYSEXE]NETNODE_REMOTE.DAT.
Your system might have this file in SYS$SPECIFIC:[SYSEXE]NETNODE_REMOTE.DAT.
These details are specifically relevant to DECnet Phase IV. Dave seems to be
running Phase V. The same consideration would be relevant there, but I'm not
familiar with the names those files may have in Phase V.
- Mark
On 23.04.18 02:14, dwe-6006 at philtest.org
wrote:
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+. 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
? 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.
1:18 a.m.
On Sun, 22 Apr 2018 19:01:28 -0400, <dwe-6006 at philtest.org> wrote:
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.
[...]
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
I do not remember all the gory details, and above all none of them when
spealing about DECnet/Plus, but basically (if I'm not wrong) MONI CLU starts
a process on other nodes in order to collect from them the data it needs.
It seems that for some reason that process on RODNEL does not exists, or
does not start, or does not answer. A quick Google search turns out that the
process should be VPM$SERVER (VPM = Virtual Performance Monitor)...
Hope this helps somehow, :)
G.
2:12 a.m.
Thank you, I'll look for that process on RODNEL and ADV2 to see the
differences.
--Dave
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf
Of G.
Sent: Sunday, April 22, 2018 7:18 PM
To: hecnet at Update.UU.SE
Cc: hecnet at Update.UU.SE
Subject: Re: [HECnet] Asymmetric connectivity in a cluster
On Sun, 22 Apr 2018 19:01:28 -0400, <dwe-6006 at philtest.org> wrote:
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.
[...]
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
I do not remember all the gory details, and above all none of them when
spealing about DECnet/Plus, but basically (if I'm not wrong) MONI CLU starts
a process on other nodes in order to collect from them the data it needs.
It seems that for some reason that process on RODNEL does not exists, or
does not start, or does not answer. A quick Google search turns out that the
process should be VPM$SERVER (VPM = Virtual Performance Monitor)...
Hope this helps somehow, :)
G.
10:45 a.m.
Dave,
I would be interested in seeing your simh configuration files for the two nodes in the
cluster. That along with which simulator is running with those configurations.
Thanks.
- Mark
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of
dwe-6006 at philtest.org
Sent: Sunday, April 22, 2018 4:01 PM
To: hecnet at update.uu.se
Subject: [HECnet] Asymmetric connectivity in a cluster
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
2202
days inactive
2203
days old
9 comments
5 participants
participants (5)
-
bqt＠softjar.se -
dwe-6006＠philtest.org -
gerry77＠mail.com -
hvlems＠zonnet.nl -
Mark＠infocomm.com