| Author |
DECNET--> SET HOST one way only |
cmethot
Member
Posts: 23
Location: Calgary, Canada
Joined: 13.06.08 |
| Posted on April 30 2010 07:31 |
|
|
Anybody with experience with DecNet troubleshooting?
I tried to connect to my old uVAX via DECNET to other nodes..
But can only initiate DecNet from one node then only then, the other way around...
Here we have Nodes OLDBOB AND VAXTOM
I Can only SET HOST from OLDBOB if and only if I previosly SET HOST from VAXTOM.
NODE name
---------
OLDBOB = uVMS 4.5 (yep this old one again...)DecNet IV
VAXTOM = VMS 5.5 ( younger..in its 40'.....)DecNet IV
All NCP SET NODE and DEFINE NODE have been made RECIPROCALLY on both machine.
On
Trial 1:
On VAXTOM I do:
$ SET HOST OLDBOB
%SYSTEM-F-UNREACHABLE, remote node is not currently reachable
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This is my problem...
If I switch terminal , go on OLDBOB and do:
$ SET HOST VAXTOM
Logging on to VAXTOM.
Username: SYSTEM
Password:
Welcome to VAX/VMS version V5.5
Last interactive login on Wednesday, 14-APR-2010 06:34
Last non-interactive login on Tuesday, 13-APR-2010 15:23
$LO
NOW back on VAXTOM terminal
$ SET HOST OLDBOB
Logging on to OLDBOB. -Old but Bold!
Username: SYSTEM
Password:
Welcome to VAX/VMS version V4.5
Last interactive login on Wednesday, 14-APR-2010 07:04
Last non-interactive login on Tuesday, 13-APR-2010 15:25
$
The same thing happened if I tried to set host from any other nodes to OLDBOB
If I Initially connect (SET HOST) from OLDBOB to any nodes.. I can NOW connect back from them to OLDBOB.
But only for a periode of time.. After 5 10 20 minutes, I will not be able to connect to OLDBOB from remote...
It is like their is a oneway connect thinggy
What ever that my other nodes are Alpha, Vax, DecNet IV, DecNet-plus the same happened..
It seem that OLDVAX do not want INCOMING DecNet despite that the NCP show EXCUTOR STATUS say it can..
(OLDBO
NCP>SHOW KNOW NODES CHARAC
Known Node Volatile Characteristics as of 13-APR-2010 14:01:22
Executor node = 18.105 (OLDBO
Identification = DECnet-VAX V4.5, VMS V4.5
Management version = V4.0.0
Incoming timer = 45
Outgoing timer = 60
NSP version = V4.0.0
Maximum links = 32
Delay factor = 80
Delay weight = 5
Inactivity timer = 60
Retransmit factor = 10
Routing version = V2.0.0
Type = nonrouting IV
Routing timer = 600
Broadcast routing timer = 180
Maximum address = 255
Maximum circuits = 16
Maximum cost = 1022
Maximum hops = 30
Maximum visits = 63
Maximum area = 63
Max broadcast nonrouters = 64
Max broadcast routers = 32
Area maximum cost = 1022
Area maximum hops = 30
Maximum buffers = 100
Buffer size = 576
Nonprivileged user id = DECNET
Nonprivileged password = DECNET
Default access = incoming and outgoing
Pipeline quota = 3000
Default proxy access = incoming and outgoing
Alias maximum links = 32
Remote node = 1.1 (VAXTOM)
No information available
Remote node = 1.2 (APXBART)
No information available
Remote node = 18.100 (APOLLO)
No information available
VAXTOM infos...:
NCP>SHOW KNOW NODES CHARAC
Known Node Volatile Characteristics as of 21-APR-2010 07:50:27
Executor node = 1.1 (VAXTOM)
Identification = DECnet-VAX V5.5-2, VMS V5.5-2H4
Management version = V4.0.0
Incoming timer = 45
Outgoing timer = 60
Incoming Proxy = Enabled
Outgoing Proxy = Enabled
NSP version = V4.1.0
Maximum links = 32
Delay factor = 80
Delay weight = 5
Inactivity timer = 60
Retransmit factor = 10
Routing version = V2.0.0
Type = routing IV
Routing timer = 600
Broadcast routing timer = 180
Maximum address = 1023
Maximum circuits = 16
Maximum cost = 1022
Maximum hops = 30
Maximum visits = 63
Maximum area = 63
Max broadcast nonrouters = 64
Max broadcast routers = 32
Maximum path splits = 1
Area maximum cost = 1022
Area maximum hops = 30
Maximum buffers = 100
Buffer size = 576
Default access = incoming and outgoing
Pipeline quota = 16000
Alias maximum links = 32
Path split policy = Normal
Maximum Declared Objects = 31
Remote node = 1.2 (APXBART)
No information available
Remote node = 18.100 (APOLLO)
No information available
Remote node = 18.105 (OLDBO
No information available
Similar set up on other VAX..
Concern/behind my mind:
- Nonrouting on OLDBOB
- both system are set incoming/outgoing connection
- Problem seem to be in OLDBOB since I do seem to have issues between APXBART, APOLLO and VAXTOM |
|
|
| Author |
RE: NCP SHOW KNO CIRC and NODES ? |
VolkerHalle
Member
Posts: 104
Location: Germany
Joined: 02.04.10 |
| Posted on April 30 2010 20:13 |
|
|
Hi,
the fact, that you can successfully do a SET HOST OLDBOB from VAXTOM only AFTER you once did the SET HOST VAXTOM from OLDBOB can be explained: the end node cache (on-LAN cache) on VAXTOM is being filled by the DECnet connection from OLDBOB to VAXTOM with the LAN address of OLDBOB. So - for some time after that - VAXTOM knows how to directly send packets to OLDBOB via the LAN. The cache entries have a certain timeout, so that explains, why it doesn't work anymore after some time...
Please show the output of MC NCP SHOW KNOWN CIRC and MC NCP SHOW KNOWN NODES from VAXTOM and OLDBOB.
If you start a connection, an end-node either sends the initial packet to the designated router on the LAN - if there is one - or directly to the other end-node by constructing the MAC address from the DECnet-node number.
Volker.
Edited by VolkerHalle on April 30 2010 20:14 |
 |
| Author |
RE: DECNET--> SET HOST one way only |
cmethot
Member
Posts: 23
Location: Calgary, Canada
Joined: 13.06.08 |
| Posted on May 02 2010 19:56 |
|
|
|
ok i will collect this tomorrow and will post it.. |
|
|
| Author |
RE: DECNET one way! |
cmethot
Member
Posts: 23
Location: Calgary, Canada
Joined: 13.06.08 |
| Posted on May 03 2010 12:29 |
|
|
as requested:
O L D B O B :
-----------
OLDBOB_SYSMGR> MC NCP SHOW KNOWN CIRC
Known Circuit Volatile Summary as of 3-MAY-2010 15:37:57
Circuit State Loopback Adjacent
Name Node
QNA-0 on
OLDBOB_SYSMGR> MC NCP SHOW KNOWN NODES
Known Node Volatile Summary as of 3-MAY-2010 15:39:08
Executor node = 18.105 (OLDBO
State = on
Identification = DECnet-VAX V4.5, VMS V4.5
Node State Active Delay Circuit Next node
Links
1.1 (VAXTOM) QNA-0 0
1.2 (APXBART) QNA-0 0
18.100 (APOLLO) QNA-0 0
OLDBOB_SYSMGR>
NOW ON
V A X T O M :
-----------
VAXTOM> MC NCP SHOW KNOWN CIRC
Known Circuit Volatile Summary as of 3-MAY-2010 16:06:57
Circuit State Loopback Adjacent
Name Routing Node
ISA-0 on
SVA-0 off
VAXTOM> MC NCP SHOW KNOWN NODES
Known Node Volatile Summary as of 3-MAY-2010 16:07:53
Executor node = 1.1 (VAXTOM)
State = on
Identification = DECnet-VAX V5.5-2, VMS V5.5-2H4
Active links = 2
Node State Active Delay Circuit Next node
Links
1.2 (APXBART) reachable ISA-0 1.2 (APXBART)
18.100 (APOLLO) reachable ISA-0 18.100 (APOLLO)
18.105 (OLDBO unreachable
VAXTOM>
I just notice that OLDBOB do not give the status as REACHABLE/UNREACHBLE as VAXTOM does.
Claude |
|
|
| Author |
RE: DECnet routing config related |
VolkerHalle
Member
Posts: 104
Location: Germany
Joined: 02.04.10 |
| Posted on May 04 2010 18:37 |
|
|
Claude,
VAXTOM is a DECnet router, but NOT an area router, so it only keeps the routing information for nodes in it's own area (DECnet area 1).
OLDBOB is an endnode in area 18. As an endnode, it can directly connect to any DECnet node on it's LAN.
If you would configure node OLDBOB with a DECnet address in area 1 as well, you would not see this problem.
The fact that node APOLLO, also in area 18, is shown as reachable by VAXTOM, could be caused by a recent (or existing) DECnet link from APOLLO to VAXTOM. Try OLDBOB $ SET HOST VAXTOM and then issue a MC NCP SHOW KNO NODES on VAXTOM.
Volker. |
|
|
| Author |
RE: DECNET--> SET HOST one way only |
cmethot
Member
Posts: 23
Location: Calgary, Canada
Joined: 13.06.08 |
| Posted on May 05 2010 08:44 |
|
|
DECnet router, but NOT an area router
endnode..
If I want everybody "EQUAL" and inter-reachable..
Q1: Should I have everybody under the same Area?
Q2: and/or should I set VAXTOM (1.1) as an AREA router
I have a work station (DECSAN1)set as a peer to peer "SAN" with a area 10.x, so if i want it to be accessable from VAXTOM, having VAXTOM as a area router would allow it to be permanatly seen ?
Thanks
|
|
|
| Author |
RE: put all DECnet nodes into same area |
VolkerHalle
Member
Posts: 104
Location: Germany
Joined: 02.04.10 |
| Posted on May 05 2010 21:43 |
|
|
Claude,
if you configure DECnet nodes in different areas and want them to communicate reliably, you also need AREA routers for both areas, i.e. if you configure VAXTOM (1.1) as an area router for area 1, you also need to configure another node in area 18 as an area router for area 18. This - generally - does not make much sense on a LAN.
Consider to configure all your nodes into the same DECnet area. Then you will be able to communicate reliably between also those nodes.
Volker.
Edited by VolkerHalle on May 05 2010 21:44 |
|
|
