There is no such thing as area 0, so if something is reporting that, it would indicate something peculiar going on. paul On Sep 20, 2012, at 11:38 AM, Dan Williams wrote: Hi, On a working machine here (also simh). I have exactly the same settings on every line of your show char below. I did notice that on the first email, it was saying that SIMVAX was in area 0. I don't know if that is relevant. Can you do a set host to 1.13 ? If you can set host, does a copy known nodes from 1.13 make any difference. I maybe wrong but I think that if that is the only machine in the area you will get unreachable as there is nothing else to reach. Dan On 20 September 2012 14:47, Mark Wickens <mark at wickensonline.co.uk> wrote: Dan, Thanks for the help. Unfortunately it didn't make any difference. License Management Facility V1.2 License Database File: SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB;1 Created on: 16-SEP-2012 Created by user: SYSTEM Created by LMF Version: V1.2 ----------------------------------- DVNETRTG DEC $ show network Product: DECNET Node: SIMVAX Address(es): 4.248 Product: TCP/IP Node: simvax.hecnet.eu Address(es): 192.168.1.127 NCP>show known areas Known Area Volatile Summary as of 20-SEP-2012 14:46:17 Area State Circuit Next node to area 4 unreachable NCP>show exec characteristics Node Volatile Characteristics as of 20-SEP-2012 14:45:58 Executor node = 4.248 (SIMVAX) Identification = DECnet for OpenVMS VAX V7.3 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 Nonprivileged user id = DECNET Nonprivileged password = AUMIAWOSAJ Default access = incoming and outgoing Pipeline quota = 4032 Alias maximum links = 32 Path split policy = Normal Maximum Declared Objects = 31 On Thu, 20 Sep 2012, Dan Williams wrote: Hi, You need : ncp>def exec type routing iv ncp>set exec state off $@startnet Also have you got dvnetrtg license loaded ? That's what I normally forget. Thanks Dan On 20 Sep 2012, at 12:05, Mark Wickens <mark at wickensonline.co.uk> wrote: Bit of a puzzler here, but it'll probably turn out to be my configuration. When the SIMH VAX/VMS 7.3 instance SIMVAX is serving hecnet.eu I get the following area/node stats reported: Known Area Volatile Summary as of 20-SEP-2012 11:53:22 Area State Circuit Next node to area 4 reachable QNA-0 0 (SIMVAX) Known Node Volatile Summary as of 20-SEP-2012 11:53:37 Executor node = 4.248 (SIMVAX) State = on Identification = DECnet for OpenVMS VAX V7.3 Node State Active Delay Circuit Next node Links 1.1 (MAGICA) QNA-0 0 1.2 (ERNIE) QNA-0 0 1.3 (FNATTE) QNA-0 0 1.4 (GOBLIN) QNA-0 0 1.5 (ZEKE) QNA-0 0 1.6 (GNOME) QNA-0 0 1.7 (BJARNE) QNA-0 0 1.8 (KRILLE) QNA-0 0 ... So only my area known, and weird stats for nodes. Can anyone tell me what is up with my configuration? I'm running Johnny's bridge and if I bring up SLAVE, the AlphaServer 1000A, on the same area it reports all stats correctly. SIMVAX is currently unable to see MIM. I set it up as a non-routing node. When I tried setting it up via NETCONFIG as a routing node I get everything unreachable. Regards, Mark. -- http://www.wickensonline.co.uk http://declegacy.org.uk