HECnet

hecnet@lists.dfupdate.se

15559 discussions

by mark＠wickensonline.co.uk

On 21/09/12 04:51, Kari Uusim ki wrote: On 21.9.2012 2:56, Mark Wickens wrote: Hi guys, Does anyone have the DEC RDB Version 6.1 developers kit. I have the December 1995 ConDist which *should* have it on, but for some inexplicable reason the .C saveset is missing from the CDROM (.A, .B, .D etc...) Regards, Mark . Which one do you need; VAX or Alpha? I'll check what I can find. Regards, Kari VAX please. Yes, I tried to install it - it fails loading saveset C. I have installed 5.1 without issue. Regards, Mark.

12 years, 8 months

DEC RDB 6.1 Kit

by hvlems＠zonnet.nl

Have you tried to install it? Hans ------Origineel bericht------ Van: Mark Wickens Afzender: owner-hecnet at Update.UU.SE Aan: hecnet at update.uu.se Beantwoorden: hecnet at Update.UU.SE Onderwerp: [HECnet] DEC RDB 6.1 Kit Verzonden: 21 september 2012 01:56 Hi guys, Does anyone have the DEC RDB Version 6.1 developers kit. I have the December 1995 ConDist which *should* have it on, but for some inexplicable reason the .C saveset is missing from the CDROM (.A, .B, .D etc...) Regards, Mark

12 years, 8 months

DEC RDB 6.1 Kit

by uusimaki＠exdecfinland.org

On 21.9.2012 2:56, Mark Wickens wrote: Hi guys, Does anyone have the DEC RDB Version 6.1 developers kit. I have the December 1995 ConDist which *should* have it on, but for some inexplicable reason the .C saveset is missing from the CDROM (.A, .B, .D etc...) Regards, Mark . Which one do you need; VAX or Alpha? I'll check what I can find. Regards, Kari

12 years, 8 months

DEC RDB 6.1 Kit

by mark＠wickensonline.co.uk

Hi guys, Does anyone have the DEC RDB Version 6.1 developers kit. I have the December 1995 ConDist which *should* have it on, but for some inexplicable reason the .C saveset is missing from the CDROM (.A, .B, .D etc...) Regards, Mark

12 years, 8 months

Some more old hardware available

by Paul_Koning＠Dell.com

It looks like this didn't go out the first time, perhaps because I sent it from the wrong place... --------- Since people are offering to send old hardware to a good home, I figure I should do likewise. I have some bits of old DEC hardware, free to a good home. a. two M9202 Unibus jumpers (the ones with a foot or three of Unibus cable between the boards). b. DEFPA-DA -- PCI FDDI NIC, dual attachment style (two fiber optic ports). paul

12 years, 8 months

decnet known area/nodes from SIMH instance

by mark＠wickensonline.co.uk

That got it! Thanks Rob. Mark. On Thu, 20 Sep 2012, Rob Jarratt wrote: Is it not that you have not set up your routing node as an *area* routing node. Try DEF EXEC TYPE AREA and restart DECnet. Regards Rob -----Original Message----- From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of hvlems at zonnet.nl Sent: 20 September 2012 19:16 To: hecnet at Update.UU.SE Subject: Re: [HECnet] decnet known area/nodes from SIMH instance Try $ show network/old That will tell you whether you've got a router or an endnode. Based on what you posted so far you have the former. Hans -----Original Message----- From: Mark Wickens Sender: owner-hecnet at Update.UU.SE Date: Thu, 20 Sep 2012 14:47:26 To: hecnet at Update.UU.SE<hecnet at update.uu.se> Reply-To: hecnet at Update.UU.SESubject: Re: [HECnet] decnet known area/nodes from SIMH instance 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 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

12 years, 8 months

decnet known area/nodes from SIMH instance

by robert.jarratt＠ntlworld.com

Is it not that you have not set up your routing node as an *area* routing node. Try DEF EXEC TYPE AREA and restart DECnet. Regards Rob -----Original Message----- From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of hvlems at zonnet.nl Sent: 20 September 2012 19:16 To: hecnet at Update.UU.SE Subject: Re: [HECnet] decnet known area/nodes from SIMH instance Try $ show network/old That will tell you whether you've got a router or an endnode. Based on what you posted so far you have the former. Hans -----Original Message----- From: Mark Wickens Sender: owner-hecnet at Update.UU.SE Date: Thu, 20 Sep 2012 14:47:26 To: hecnet at Update.UU.SE<hecnet at update.uu.se> Reply-To: hecnet at Update.UU.SESubject: Re: [HECnet] decnet known area/nodes from SIMH instance 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 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

12 years, 8 months

decnet known area/nodes from SIMH instance

by hvlems＠zonnet.nl

Try $ show network/old That will tell you whether you've got a router or an endnode. Based on what you posted so far you have the former. Hans -----Original Message----- From: Mark Wickens Sender: owner-hecnet at Update.UU.SE Date: Thu, 20 Sep 2012 14:47:26 To: hecnet at Update.UU.SE<hecnet at update.uu.se> Reply-To: hecnet at Update.UU.SESubject: Re: [HECnet] decnet known area/nodes from SIMH instance 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 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

12 years, 8 months

decnet known area/nodes from SIMH instance

by Paul_Koning＠Dell.com

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 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 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

12 years, 8 months

decnet known area/nodes from SIMH instance

by williams.dan＠gmail.com

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 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 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

12 years, 8 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

HECnet