Groups | Search | Server Info | Login | Register
Groups > alt.sys.pdp10 > #9823
| From | jayjwa <jayjwa@atr2.ath.cx.invalid> |
|---|---|
| Newsgroups | alt.sys.pdp10 |
| Subject | Re: TOPS-10 networking in modern time |
| Date | 2025-12-29 12:05 -0500 |
| Organization | Atr2 RG 2025 |
| Message-ID | <87h5t96wx3.fsf@atr2.ath.cx> (permalink) |
| References | (3 earlier) <mdd5xa7v1w3.fsf@panix5.panix.com> <87ike6mljt.fsf@atr2.ath.cx> <10iqucr$504s$1@dont-email.me> <87ecoembvh.fsf@atr2.ath.cx> <10itjtr$tdk1$1@dont-email.me> |
"G." <nan6328@iperbole.invalid> writes:
> I searched the sources for LATNSC and found it in the LATSER module
> (SER = Service). It seems that LATNSC is a stopcode generated when the
> host stops a circuit for some reason (NSC = Node Stopped Circuit). The
> reason is that "2" code which apparently means that the host received
> an invalid RUN message.
> If I'm doing it right, the address of the other side is
> AA-00-04-00-00-10-40, i.e. DECnet node 1.16... Could it be? What kind
> of node it is?
1.16 is for VXT, the virtual Xterminal you get if you boot a
microvax2000 off an Infoserver. Odd thing is, I've not had it running
since I started with TOPS-10 so TOPS-10 has never seen it. It does have
it listed as 'known nodes'.
Here's the view from TOPS-20:
@info decnet
Local DECNET node: AMATSU. Nodes reachable: 7.
Accessible DECNET nodes are: AMATSU ATR2 KIRIN KUSHAL LUNAST NERGIG
TEOSTR
@enable
$opr
OPR>enter ncp
NCP>tell nergig show exec char
NCP>
11:47:36 NCP
Request # 3 Accepted
NCP>
11:47:40 NCP
Request # 3; Show Executor Node Characteristics Completed
Executor Node = 1.15 (NERGIG)
Identification = DECnet-10 Version 4.0 11:48 [13/70]
Management Version = 4.0.0
Loop Count = 1
Loop Length = 127
Loop With = Mixed
Incoming Timer = 30
Outgoing Timer = 60
NSP Version = 4.0.0
Maximum Links = 65535
Delay Factor = 48
Delay Weight = 10
Inactivity Timer = 120
Retransmit Factor = 10
Routing Version = 2.0.0
Type = Nonrouting IV
Routing Timer = 600
Broadcast Routing Timer = 40
Maximum Address = 1023
Maximum Circuits = 20
Maximum Cost = 100
Maximum Hops = 16
Maximum Visits = 20
Maximum Broadcast Nonrouters = 64
Maximum Broadcast Routers = 32
Maximum Buffers = 80
Buffer Size = 576
Segment Buffer Size = 576
NCP>loop node 1.2
NCP>
11:47:59 NCP
Request # 4 Accepted
NCP>
11:47:59 NCP
Request # 4; Loop Node Completed
NCP>loop node 1.16
NCP>
NCP>
11:48:03 NCP
Request # 5 Accepted
NCP>
11:48:03 NCP
Request # 5; Loop Node Failed, Mirror connect failed
NCP>
11:48:28 -- DECnet link message --
Communication failure to the following nodes:
VXT
NCP>
So you can see it's not even on the network now. I'm beginning to think
there's something deeper going on here. DECnet is dog slow - as in a
10-20 second delay between key presses when you login over it. mail11
works but that's about all. No loop, no FAL. Last night I learned
there's a NETGEN and found the manual for it. Maybe that might hold some
answers.
Here's the view from TOPS-10 that shows everyone:
NCP>show known nodes
NCP>
8:44:20 NCP
Request # 30; Show Known Nodes Summary Completed
Node State Active Delay Circuit Next node
links
1.1 (ATR2) 1 1 ETH-0
1.2 (NAMIEL) 1 1 ETH-0
1.10 (DTSR) ETH-0
1.11 (KIRIN) ETH-0
1.12 (KUSHAL) ETH-0
1.13 (TEOSTR) 1 1 ETH-0
1.14 (LUNAST) ETH-0
1.15 (NERGIG) On 0
Identification = DECnet-10 Version 4.0
1.16 (VXT) ETH-0
1.17 (EWS) ETH-0
1.18 (EWS2) ETH-0
1.19 (AMATSU) 0 1 ETH-0
1.20 (ZORAH) ETH-0
NCP>
--
PGP Key ID: 781C A3E2 C6ED 70A6 B356 7AF5 B510 542E D460 5CAE
"The Internet should always be the Wild West!"
Back to alt.sys.pdp10 | Previous | Next — Previous in thread | Next in thread | Find similar
TOPS-10 networking in modern time jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-12-14 20:55 -0500
Re: TOPS-10 networking in modern time Rich Alderson <news@alderson.users.panix.com> - 2025-12-14 21:23 -0500
Re: TOPS-10 networking in modern time Al Kossow <aek@bitsavers.org> - 2025-12-14 18:34 -0800
Re: TOPS-10 networking in modern time drb@ihatespam.msu.edu (Dennis Boone) - 2025-12-15 03:04 +0000
Re: TOPS-10 networking in modern time jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-12-15 14:34 -0500
Re: TOPS-10 networking in modern time Rich Alderson <news@alderson.users.panix.com> - 2025-12-15 17:03 -0500
Re: TOPS-10 networking in modern time jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-12-16 11:35 -0500
Re: TOPS-10 networking in modern time Rich Alderson <news@alderson.users.panix.com> - 2025-12-16 22:12 -0500
Re: TOPS-10 networking in modern time Johnny Billquist <bqt@softjar.se> - 2025-12-17 10:31 +0100
Re: TOPS-10 networking in modern time jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-12-17 11:06 -0500
Re: TOPS-10 networking in modern time jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-12-17 10:56 -0500
Re: TOPS-10 networking in modern time Johnny Billquist <bqt@softjar.se> - 2025-12-20 13:27 +0100
Re: TOPS-10 networking in modern time Lars Brinkhoff <lars.spam@nocrew.org> - 2025-12-20 13:23 +0000
Re: TOPS-10 networking in modern time jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-12-20 11:59 -0500
Re: TOPS-10 networking in modern time Johnny Billquist <bqt@softjar.se> - 2025-12-25 11:35 +0100
Re: TOPS-10 networking in modern time "G." <nan6328@iperbole.invalid> - 2025-12-29 17:59 +0100
Re: TOPS-10 networking in modern time "G." <nan6328@iperbole.invalid> - 2025-12-28 10:47 +0100
Re: TOPS-10 networking in modern time jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-12-28 18:21 -0500
Re: TOPS-10 networking in modern time "G." <nan6328@iperbole.invalid> - 2025-12-29 11:07 +0100
Re: TOPS-10 networking in modern time Johnny Billquist <bqt@softjar.se> - 2025-12-29 13:20 +0100
Re: TOPS-10 networking in modern time jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-12-29 12:22 -0500
Re: TOPS-10 networking in modern time "G." <nan6328@iperbole.invalid> - 2025-12-29 20:43 +0100
Re: TOPS-10 networking in modern time jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-12-30 11:57 -0500
Re: TOPS-10 networking in modern time Johnny Billquist <bqt@softjar.se> - 2025-12-31 15:21 +0100
Re: TOPS-10 networking in modern time jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-12-31 12:33 -0500
Re: TOPS-10 networking in modern time Johnny Billquist <bqt@softjar.se> - 2025-12-31 15:20 +0100
Re: TOPS-10 networking in modern time "G." <nan6328@iperbole.invalid> - 2025-12-29 17:59 +0100
Re: TOPS-10 networking in modern time jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-12-29 12:05 -0500
Re: TOPS-10 networking in modern time "G." <nan6328@iperbole.invalid> - 2025-12-29 19:58 +0100
Re: TOPS-10 networking in modern time jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-12-30 12:15 -0500
Re: TOPS-10 networking in modern time "G." <nan6328@iperbole.invalid> - 2025-12-31 02:21 +0100
Re: TOPS-10 networking in modern time jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-12-31 12:17 -0500
Re: TOPS-10 networking in modern time "G." <nan6328@iperbole.invalid> - 2026-01-01 18:32 +0100
Re: TOPS-10 networking in modern time jayjwa <jayjwa@atr2.ath.cx.invalid> - 2026-01-02 13:27 -0500
Re: TOPS-10 networking in modern time "G." <nan6328@iperbole.invalid> - 2026-01-05 13:37 +0100
Re: TOPS-10 networking in modern time jayjwa <jayjwa@atr2.ath.cx.invalid> - 2026-01-05 12:52 -0500
Re: TOPS-10 networking in modern time "G." <nan6328@iperbole.invalid> - 2026-01-06 01:37 +0100
Re: TOPS-10 networking in modern time jayjwa <jayjwa@atr2.ath.cx.invalid> - 2026-01-06 12:18 -0500
csiph-web