HECnet

hecnet@lists.dfupdate.se

5 participants
15579 discussions

by paulkoning＠comcast.net

Gentlepeople, I committed rev 560, which may be of interest to a number of you. It's basically a change of internal machinery, no functional changes. The main ones are: 1. Restructured the point to point (DDCMP and Multinet) implementations. Error recovery is much cleaner now and should be faster. Retry for persistent problems has holdoff on it that starts out pretty fast and slows down to (typically) one retry per two minutes. 2. Ethernet in PCAP mode now uses the PCAP filter mechanism to request only the frames we want. This means the Python code no longer spends a bunch of CPU time tossing away non-DECnet frames. If your machine runs other traffic in significant quantities, as mine does, this can be quite useful. 3. Improve the performance of packet logging. This code has been running on PYTHON for several days now without problems (except for one bug that has been fixed). You're invited to give it a try; as always, problem reports or other comments are welcome. paul

4 years, 11 months

Booting VMS 5.5.2 cluster satellite node [SIMH 4.0] over slow link

by xdelta＠meta.ua

Hi, guys! I'm trying to boot latest SIMH (4.0-current) as LAVC satellite node over link with latency about 100ms. Boot node is VAX/VMS 5.5.2 with latest PEDRIVER ECO. Result: MOP part of boot sequence is work without a hitch, but SCS part is failing miserably. The most frequent result: SIMH console filled with 10 x " %VAXcluster-W-NOCONN, No connection to disk server " messages, halting with "%VAXcluster-F-CTRLERR, boot driver virtual circuit to SCSSYSTEM 0000 Failed" Sometime it goes little further: ... %VAXcluster-W-RETRY, Attempting to reconnect to a disk server %VAXcluster-W-NOCONN, No connection to disk server %VAXcluster-W-RETRY, Attempting to reconnect to a disk server %VAXcluster-W-NOCONN, No connection to disk server VULCAN %VAXcluster-W-RETRY, Attempting to reconnect to a disk server %VAXcluster-W-NOCONN, No connection to disk server %VAXcluster-W-RETRY, Attempting to reconnect to a disk server %VAXcluster-I-CONN, Connected to disk server VULCAN %VAXcluster-W-NOCONN, No connection to disk server VULCAN %VAXcluster-W-RETRY, Attempting to reconnect to a disk server ... And halting after minute or so of filling console with those messages. Whenever I setup throttling in SIMH to 2500K ops/s, the node boots successfully, joins cluster successfully and work flawlessly, but slow. Boot process takes about half hour. After boot, changing throttle value to 3500K ops/s still works. Increasing throttle value further broke system, with the same messages about disk server. Throttled SIMH performance is about 5VUPS. The only information about maximum channel latency restrictions found in "Guidelines for OpenVMS Cluster Configurations" manual is that: "When an FDDI is used for OpenVMS Cluster communications, the ring latency when the FDDI ring is idle should not exceed 400 ms." So I suppose that 100ms latency link should be good enough for booting satellite nodes over it. My understanding of situation is that combination of PEDRIVER/[PEBTDRIVER within NISCS_LOAD] with fast hardware and slow links is a primary reason of such behavior. Please correct me if I'm wrong. Do anyone have experience with booting VMS clusters over slow links? OS version recommendations? Probably some VMS tunable variables are exists for making PEDRIVER happy on fast hardware? Having PEDRIVER listings can shed lights for such PEDRIVER's buggy behavior. Link details: Two Cisco 1861 routers connected with Internet via ADSL on one side and 3G HSDPA on other side. TCP/IP between sites is routed over IPSec site-to-site VPN. Ping between sites is about 100ms. Over that VPN built DECnet family (eth.type = 0x6000..0x600F) bridge with L2TPv3 VPN. -- BR, Vladimir Machulsky

4 years, 11 months

Question for PyDECnet users

by paulkoning＠comcast.net

Gentlepeople, Currently the details of what PyDECnet circuits connect to are not displayed. So you can see that a Multinet circuit is up and the other end is node 42.73, but you don't see the IP addresses or the like. When things are working that's fine; when they are broken it might be helpful to see what something is trying to talk to. On the other hand, hiding IP addresses is arguably a security feature. So I have this question: 1. Should the addressing info (basically, what's in the --device config argument) be shown in the PyDECnet web interface? 2. Should the addressing info be visible via NCP / NML? The difference is that #1 can be limited to be local only, if you use an internal address for the web service. That's what I do for my nodes except for the mapper, though perhaps there isn't a strong argument why it should be so restrictive. #2, on the other hand, is visible to all HECnet users assuming you haven't disabled NML in your config settings. I'd be interested in comments. Am I too concerned about hiding information, or is it sensible to be cautious? paul

4 years, 11 months

RSTS/E patches

by paulkoning＠comcast.net

I previously created a Github repository for various DEC things, including updated DECnet/E utilities. I thought that the RSTS patches I had posted in the past were there also, but that wasn't the case. I've added a "patches" subdirectory, which contains the patches I have collected. I just added a new one, which fixes a bug encountered when running SIMH set to be an 11/94. In that case (and possibly some other similar variations) RSTS tries to figure out the line frequency and gets it wrong because SIMH executes much faster. https://github.com/pkoning2/decstuff is the repository. paul

4 years, 11 months

RSTS/E patches

by paulkoning＠comcast.net

The patches I posted are mostly for both. The kdj11e.cmd patch is for a problem seen on SIMH that probably can't happen on real hardware. The nsp1.pat file Tony mentioned is certainly more likely on SIMH but I suspect could happen on real hardware also. In any case, none of them will create problems on real hardware. paul > On Sep 15, 2020, at 9:20 AM, W2HX via cctalk <cctalk at classiccmp.org> wrote: > > Are these patches discussed below only for patching SIMH to fix problems with it? Or are these fixes that are for actual PDP hardware implementations of RSTS? > > -----Original Message----- > From: cctalk <cctalk-bounces at classiccmp.org> On Behalf Of Tony Nicholson via cctalk > Sent: Monday, September 14, 2020 6:10 PM > To: hecnet at update.uu.se > Cc: cctalk at classiccmp.org > Subject: Re: [HECnet] RSTS/E patches > > On Tue, Sep 15, 2020 at 7:28 AM Paul Koning <paulkoning at comcast.net> wrote: > >> I previously created a Github repository for various DEC things, >> including updated DECnet/E utilities. I thought that the RSTS patches >> I had posted in the past were there also, but that wasn't the case. >> >> I've added a "patches" subdirectory, which contains the patches I have >> collected. I just added a new one, which fixes a bug encountered when >> running SIMH set to be an 11/94. In that case (and possibly some >> other similar variations) RSTS tries to figure out the line frequency >> and gets it wrong because SIMH executes much faster. >> >> https://github.com/pkoning2/decstuff is the repository. >> >> paul >> >> > Thanks for this Paul. > > There's also your NSP1.PAT patch to improve data flow using RSTS/E V10.1 under SIMH (posted to the SIMH mailing list in May 2016). > > You'll find it and the NSP1.TXT describing it in my repository at > > https://github.com/agn453/RSTS-E > > in the "decnete" subdirectory. > > I've recently joined HECnet and will be making some of my updates available soon. > > Tony > > -- > Tony Nicholson <tony.nicholson at computer.org>

4 years, 11 months

Some RSTS/E files on HECnet node DINGO::

by tony.nicholson＠computer.org

I've just thrown together the RSTS/E updates mentioned in my previous message into the DECnet default account on HECnet node DINGO:: (35.619) The file DINGO::FILES.TXT contains the following details (and will be added to as I make available more files). === FILES.TXT == These are the files available from HECnet node DINGO:: (a SIMH PDP-11/70 emulation running RSTS/E V10.1 on a Raspberry Pi 3B) in the Default DECnet account (no password required). There's also a GitHub repository at https://github.com/agn453/RSTS-E where you can get further RSTS/E related information (with a link to Paul Koning's repository too). Name .Typ Size Prot Access Date Time Clu RTS DINGO:: Patch for improved Ethernet throughput using DECnet/E V4.1 on RSTS/E V10.1 NSP1 .PAT 2 < 62> 03-May-16 03-May-16 08:38 AM 64 ...RSX NSP1 .TXT 9 < 62> 19-Sep-16 19-Sep-16 02:29 PM 64 ...RSX Year 2003 update for FIT (File Interchange Transfer program) FIT .TSK 92C < 62> 03-Jul-20 03-Jul-20 02:09 PM 64 RSX FIT .DIF 5 < 62> 02-Jul-20 02-Jul-20 07:49 AM 64 ...RSX FITBLD.COM 2 < 62> 03-Jul-20 03-Jul-20 08:09 AM 64 DCL This file FILES .TXT 2 < 60> 15-Sep-20 15-Sep-20 09:31 AM 64 RT11 A directory of Kermit-11 T3.63 files (with updates to 3-Oct-2006) available from DINGO::KERMIT: KERMIT.TXT 35 < 60> 15-Sep-20 15-Sep-20 09:32 AM 64 RT11 Please report any problems to me via e-mail to either tony.nicholson at computer.org or (HECnet) FAUNA::TONY -- Tony Nicholson <tony.nicholson at computer.org>

4 years, 12 months

integrity and alpha hardware

by system＠TMESIS.COM

Peter Lothberg <roll at stupi.com> writes: >Yes, it says DEC on some on Compac on some. The DS20 diagnostics and >microcode update CD works on it. What does it say in the SRM? -- VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG I speak to machines with the voice of humanity.

5 years

Introducing some Australian fauna to HECnet

by tony.nicholson＠computer.org

G'day fellow HECnet enthusiasts! In the past week I decided to jump in and join up my little home network of Digital animals to HECnet. With the assistance of Johnny Billquist, David Moylan (Wiz) and the brilliant piece of PyDECnet routing code by Paul Koning running on a Raspberry Pi - I'm now up and online! You'll see my machines pop up as 35.6xx nodes; and, as soon as I organise things, I'll put some files up for perusal in the default DECnet accounts - (they're empty now though). I'm located at Newcastle, NSW in Australia and nudging over 45 years contact with systems from PDP-11's through VAXen and on to Alpha... along with various Cisco, Sun, CDC3500, ICL1904A, HP2100, HP1000 systems plus microcomputers from the 8080, SC/MP, Z80 era up to now. Johnny says I have "quite a list" of machines.. so I'll give a partial list here (node names in brackets) - RSTS/E V10.1 running on Raspberry Pis under SIMH PDP11 (DINGO and GALAH) - the latter is a PiDP11 mini 11/70 front panel. RSX11M-Plus V4.6 running on the same Raspberry Pi as DINGO under SIMH PDP11 (RUSTY) OpenVMS VAX V7.3 on a Vaxstation-3100 M48 (POSSUM) - which is showing its age with a power-supply fault since yesterday! An original DEC-2000 AXP model 300 (TAIPAN) just freshly upgraded to VSI OpenVMS V8.4-2L1 A VAX-11/780 SIMH emulation running OpenVMS V5.5-2 on Raspberry Pi (EMU) Intermittently I also fire up emulations running Ultrix-32 VAX V4.6 (NUMBAT), TRU-64 V5.1B (QUOLL), "ancient" VAX/VMS from V1.5 to V4.7 (BROLGA), TOPS10 V7.04 (PANDA) - and P/OS V3.2 one day when I get a round 'tuit (DUGONG) with Xhomer Pro-380 emulation and async DECnet. Finally a couple that are nearly always online - An Alpha ES40 emulation (KOALA) under AlphaVM-Free running VSI OpenVMS V8.4-2L1 on an Intel Core i7 Windows-10 box, and VAXserver-3900 SIMH with OpenVMS VAX V7.3 under Windows-10/Cygwin-32 (VOGON). You can reach me at FAUNA::TONY if you want to try e-mail the old fashioned way from VAX-MAIL or Mail-11. Tony -- Tony Nicholson <tony.nicholson at computer.org>

5 years

integrity and alpha hardware

by djm＠wiz.net.au

Greetings all, Now that VSI has their Hobbyist program all under way, we can get licensing for Integrity and Alpha hardware. (the future is obviously x86 which is progressing well and I'm looking very forward to. The hobbyist program will cover x86 once it has been released) I was thinking of trying to find an older Integrity or Alpha server to run OpenVMS but I'm struggling to find any real comparative performance comparison between the different models. Most of the old forum posts on HP link to dead articles. Alpha hardware still seems to be very high priced, but I'm starting to see some Integrity equipment coming down in price. How does something like an Integrity rx1620 stack up? Would there be any sense in purchasing a single CPU version of this server? If anyone has a list or can provide information on the different Integrity and Alpha platforms available that would be great. I totally understand that performance comparison is an "it depends" question, but I'm just after some reality checks here, ie: a specific Integrity server might have "twice" the average performance of a different Alpha box and it might be cheaper, thus better bang per buck. Can anyone help me out here? The box will just be for hobbyist purposes. I'll probably setup a mail gateway and perhaps usenet and some other things to play with. If it's relevant (for suggestions of anyone selling refurbed hardware), I'm located in Australia. Thanks in advance, Cheers, Wiz!!

5 years

Configuring py-decnet --> patches

by R.Voorhorst＠swabhawat.com

L.S. You a true altruistic wonder these days to have around :) A king, sitting on his coffers chockfull of goodies, waiting to dispense them lavishly among the lesser endowed fellow users .... Usually with kings it is the other way around as can be seen so often today. Are the other set host varieties on MIM also endowed with workable patches? We'll play copycat then, ... until better times will arrive. Thanks ever so much, Reindert -----Original Message----- From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Johnny Billquist Sent: Wednesday, 26 August, 2020 22:02 To: hecnet at Update.UU.SE Subject: Re: [HECnet] Configuring py-decnet. Aw, shit! (Excuse my language.) I had more or less forgotten. Yes, as distributed, it has a bug. I have fixed it, but of course, noone else have that. For now, the simple solution, pick MIM::DU:[5,54]RRS.TSK, and you'll be good. Sigh! I really hope the whole DEC/Mentec/HP ownership mess can be sorted one day. I have about 100 fixes or improvements to RSX sitting... Johnny On 2020-08-26 21:57, R. Voorhorst wrote: > L.S. > > > Is there something different with patch levels or otherwise? > > After successful login on Rsts 10.1: > > $ logout > SAVED ALL DISK FILES ON SY: 6784 BLOCKS IN USE JOB 7 USER 1,2 LOGGED > OFF KB24: AT 26-AUG-20 21:53 > 6 OTHER USERS STILL LOGGED IN UNDER THIS ACCOUNT SYSTEM RSTS V10.1-L > RSTS/E V10.1 RUN TIME WAS .2 SECONDS ELAPSED TIME WAS 1 MINUTE GOOD > EVENING > > > > > > > SWBU01::RRS -- Remote disconnect > > SWBU01::RRS -- Control returned to node SWBU01:: > MOV #20,R0 > EM:065126 > XDT> > > > Best regards, > > Reindert > > -----Original Message----- > From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On > Behalf Of Johnny Billquist > Sent: Wednesday, 26 August, 2020 15:09 > To: hecnet at Update.UU.SE > Cc: Thord Nilson <thordn at gmail.com> > Subject: Re: [HECnet] Configuring py-decnet. > > And to complement the picture a little more. On RSX, you need a program called RRS, which is provided among the "unsupported utilities" in the DECnet distribution. > > .rrs elvira > MIM::RRS -- Connection established to node ELVIRA:: > > RSTS V10.1-L 26-Aug-20 14:41 > User: 99,99 > PASSWORD: > > LAST INTERACTIVE LOGIN ON 26-AUG-20, 02:36 AT KB21: > > > $ > > > Johnny > > On 2020-08-26 02:19, Thomas DeBellis wrote: >> Yeah, that's what I found out, too. >> >> On Tops-20, the CTERM client is called CTERM-SERVER (don't ask) >> whereas the NRT client is called SETHOST. SETHOST is /quite/ old and >> I had been hacking it for efficiency and fixing a few bugs. >> >> It now has an alternate debugging entry to try to force Tops-20 NRT >> (which will also work on Tops-10) and ignore the remote node type >> until it can't proceed any further. Here are the results from my own >> tests; they indicate that a CTERM (server) object does not exist on ELVIRA. >> I'm not sure, but I had thought that CTERM had not been done on RSTS/E. >> >> !cterm-sERVER.EXE.2 elvira >> >> [Attempting a connection, >> _CTERM Connect failed - Destination process does not exist_ !g >> ds:sethost !ree Escape character(^Y): >> Host name: ELVIRA:: >> [Connecting to remote host: ELVIRA] >> _?RSTS/E type systems do not support Tops-20 NRT communications._ >> >> >> On 8/25/20 8:09 PM, Paul Koning wrote: >>> John, >>> >>> Some systems, like VMS, will use CTERM by default, and there isn't a CTERM listener on RSTS. So you have to tell it to use the "old protocol", whatever that involves on your OS. >>> >>> paul >>> >>>> On Aug 25, 2020, at 7:24 PM,jy at xtra.co.nz wrote: >>>> >>>> Hi Thord, >>>> >>>> Congratulations, I can see you're up at: >>>> >>>> http://akdesign.dyndns.org:8080/map/data >>>> >>>> I just tried a set host elvira and set hsot 59.53 but I'm getting "network object unknown at remote node". >>>> >>>> Cheers, John >>>> >>>> >>>> >>>>> On 26 August 2020 at 11:14 Thord Nilson<thordn at gmail.com> wrote: >>>>> >>>>> Hi all! >>>>> Update! >>>>> Basic connections are now working, so for a limited time you can: >>>>> set host elvira:: >>>>> login as 99,99 psw: testing >>>>> Nothing much to see though. >>>>> Thanks to all for your help! >>>>> >>>>> /Thord. > -- 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

5 years

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

HECnet