[HECnet] Decnet on RSX-11
Kurt Hamm
kurt at hamm.me
Sat Jun 8 15:12:14 PDT 2019
Apparently, the PDP-11 is advertising successfully as a DECNet router. My
VAX node MOE seems to be using it instead of the VAX Router LARRY. Which
is a problem because I can't route through the PDP-11 to MIM.
Well, that is basic understanding. If I turn off PDP-11, the routing from
the VAX node only Moe works fine and it routes through LARRY.
I am looking to see if I can raise the route cost of the PDP-11 to make
LARRY win the routing contest every time. Othewise, I will re-run netgen
on the PDP-11 and say no to being a router (Level 1 and Level 2).
Kurt
Kurt
On Sat, Jun 8, 2019 at 4:26 PM Mark Matlock <mark at matlockfamily.com> wrote:
> Kurt,
> If you want two circuits like UNA-0 and IP-0-0 I think you have to be a
> routing node (but not an area router).
> Also, you should define all the nodes you want to talk to with NCP in one
> of the startup files or do it with CFE but I prefer startup so it’s simple
> to change.
> Best,
> Mark
>
> Sent from my iPhone
>
> On Jun 8, 2019, at 3:07 PM, Kurt Hamm <kurt at hamm.me> wrote:
>
> This walkthrough was great.
>
> I do have a question about this the section listed below:
>
> My answers:
> 01.00 CURLY
> 02.00 31.132
> 03:00 Do I really want a routing node?
> 04:00 Do I really want a routing node?
> .
> .
> 07.00 Remote node name [<RET>=Done] Larry
> 08:00 Remote Node Address: 31.130
>
> I thought the Remote Node address setting would just route decnet through
> Larry. I don't really want the pdp-11 (CURLY) doing any routing.
>
> Thanks!
>
> Kurt
>
>
> >; =====================================================================
> >; DEC - Section 1 - Define the target and remote nodes
> >; =====================================================================
> >;
> >* 01.00 What is the target node name [S R:0-6]: RSX11M
> >* 02.00 What is the target node address [S R:0.-8.]: 30.12
> >* 03.00 Target node ID [D=None] [S R:0.-32.]: PiDP-11/70 HECnet
> >* 04.00 Do you want to generate a routing node [D=N]? [Y/N]: Y
> >* 04.01 Do you want to generate a level 2 routing node [D=N]? [Y/N]: Y
> >* 05.00 Highest node number in this area [D R:12.-1023. D:12.]: 15.
> >* 05.01 Highest area number in network [D R:30.-63. D:30.]: 63.
> >;y
> >; Extended network support for network command terminals and products
> >; layered on DECnet, will be included.
> >; [S R:0-6]:
> >* 07.00 Remote node name [<RET>=Done]
>
> On Sat, Jun 8, 2019 at 8:14 AM Mark Matlock <mark at matlockfamily.com>
> wrote:
>
>> Kurt,
>> As Johnny says you should read chapter 10 of [IP]README.DOC and run a
>> NETGEN to add the IP HECnet device. I’ve attached a walk-through of a
>> NETGEN that can help guide you but you should understand the information in
>> chapter 10.
>>
>> You should have a unique DECnet node address for your system (from
>> Johnny) to use instead of the one I supplied in the walk-through.
>>
>> Later when bringing up IP-0-0 in the [IPNET]INS.CMD I think you need a
>> port # for attachment to MIM if that is where you are connecting to?
>>
>> Best,
>> Mark
>>
>>
>>
>>
>>
>> > On Jun 8, 2019, at 6:36 AM, Kurt Hamm <kurt at hamm.me> wrote:
>> >
>> > Thanks Johnny and thanks Mark. For some reason I thought that this was
>> already done since IP was working.
>> >
>> > This is just what I needed to know to finish this thing off. I really
>> appreciate the assistance.
>> >
>> > Kurt
>> >
>> > On Sat, Jun 8, 2019, 5:32 AM Johnny Billquist <bqt at softjar.se> wrote:
>> > Kurt, Mark is absolutely right.
>> >
>> > You do not have the IP line driver generated into DECnet.
>> >
>> > This is what I suspect quite a few mails back between us, and tried to
>> > point out.
>> >
>> > And do not try to just edit CEMAC.MAC to add those lines Mark mention.
>> > That will not work. You need to run through the DECnet generation
>> > process, and then the IPNET postprocessing step. It's all in the TCP/IP
>> > manual, if you read it.
>> >
>> > Johnny
>> >
>> > On 2019-06-08 05:58, Mark Matlock wrote:
>> > > Kurt,
>> > > I think you need to have the “IP" network device NETGENed into
>> DECnet.
>> > >
>> > > The fact that you first error occurs at the NCP SET PROC IP TOP
>> makes me think that DECnet does not have a driver for the IP device loaded.
>> When I made the “Frodo” distribution available, I did a new SYSGEN for an
>> 11/70 and also a NETGEN. In the NETGEN for the Unibus system a “UNA” was
>> the ethernet device and on a Qbus system (the actual Frodo 30.1) a QNA
>> device is used.
>> > >
>> > > It would be helpful if you typed out LB:[5,54]CETAB.MAC as it
>> could confirm if the IP device has been NETGENed in or not. In CETAB.MAC
>> the 3rd actual line of code should look like:
>> > >
>> > > PDV$DF <AUX,EVL,ECL,XPT,NCT,RTH,LAT,DLX>,<EPM>,<UNA,IP>
>> > >
>> > > Three lines below that should be:
>> > >
>> > > SLT$DF IP,IP,XPT,LF.TIM,0,0,,0.,0.,15.
>> > >
>> > > It’s been a while since I added the IP-0-0 LIN and Circuits to my
>> system, but I try to do that to one of my PiDP-11s and post the walk
>> through for it.
>> > >
>> > > Below I’ve put some information of the sequence of startup
>> command files that may help you understand the files involved.
>> > >
>> > > In the LB:[1,2]STARTUP.CMD of the Frodo distribution RSX and
>> DECnet are started as is normal for any RSX. It then chains to
>> LB:[1,2]INSPROG.CMD which brings up the DU1: disk that you either download
>> from RSX11M.COM or the Simh boot.ini will make a blank one.
>> > >
>> > > At the end of the INSPROG.CMD two questions are asked with
>> timeouts. The first will load LAT and the second loads Johnny’s TCP/IP. It
>> loads the TCP/IP by chaining to LB:[IP]IPINS.CMD which will load TCP/IP and
>> either DHCP an IP address or set a static IP address. At the end of that
>> file then LB:[IP]IPAPPL.CMD is executed which sets up FTP, TELNET, NTP and
>> other applications.
>> > >
>> > > Now, in the Frodo distribution IPAPPL.CMD, there is a line that
>> was either commented or deleted that chains to LB:[IPNET]INSHECNET.CMD
>> which is used to link the actual node Frodo (HECnet 30.1) to MIM
>> > >
>> > > Your [IPNET]INS.CMD looks identical to the INSHECNET.CMD on Frodo
>> including the host port # which may be something we need to change?
>> > >
>> > > Do you have a HECnet address from Johnny? Also, where are you
>> planning to connect to HECnet?
>> > >
>> > > There is a [IPNET]INS.NEW which is the template that Johnny provides
>> and it does not have a port specified on MIM. I don’t remember the exact
>> mechanics on MIM That accepts connections but that may be a function of
>> that port # Frodo connects to MIM on IP-0-10 but that is not specified on
>> Frodo but on MIM.
>> > >
>> > > Best,
>> > > Mark
>> > >
>> > >
>> > >
>> > >
>> > >
>> > >> On Jun 7, 2019, at 9:35 PM, Kurt Hamm <kurt at hamm.me> wrote:
>> > >>
>> > >> So, I added this command to the startup.cmd: @LB:[IPNET]INS.CMD.
>> > >>
>> > >> I didn't modify the file yet. I wanted to see what it would do
>> > >>
>> > >> The result after rebooting was this:
>> > >>> INS LB:[IPNET]MLTCOM/UIC=[1,54]/PRO=[RW,RW,,]
>> > >>> INS LB:[IPNET]MLTNET
>> > >>> INS LB:[IPNET]MLTCFG
>> > >>> NCP SET PROC IP TOP
>> > >> NCP -- Set failed, unrecognized component, Process
>> > >>> NCP SET LIN IP-0-* ALL
>> > >> NCP -- Set failed, invalid identification format, Line
>> > >>> MNC SHO VER
>> > >> Initialize common
>> > >> NT.IP not found. Exiting...
>> > >>> MNC SET CIR IP-0-0 TCA HOST MIM.UPDATE.UU.SE:7705 PORT 0
>> > >> Initialize common
>> > >> NT.IP not found. Exiting...
>> > >>> NCP SET CIR IP-0-0 STA ON
>> > >> NCP -- Set failed, invalid identification format, Circuit
>> > >>
>> > >> There are lots of errors, so I am not sure where to start.
>> > >>
>> > >> Any advice would be appreciated.
>> > >>
>> > >> Kurt
>> > >
>> >
>> >
>> > --
>> > 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
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sonic.net/pipermail/hecnet-list/attachments/20190608/d9be57c2/attachment.html>
More information about the Hecnet-list
mailing list