How are you trying to connect? Do you have an up-to-date node list on LULU?
SET HOST LEGATO
or
SET HOST 2.1
Zane
On Mon, 6 Apr 2009, Marc Chametzky wrote:
LULU, on the other hand, can only connect to DUSTY. It can't connect to
LEGATO.
Hmm. What makes you think this? I ask because LEGATO can connect to LULU
(I just tried it a minute ago), so it is working at least one way.
That is strange... I saw your connection attempt, but my attempts to contact LEGATO don't work as well:
$ set host legato
%SYSTEM-F-UNREACHABLE, remote node is not currently reachable
When I look in NCP, I see something that doesn't look right.
NCP>show node legato
Node Volatile Summary as of 6-APR-2009 12:06:19
Node State Active Delay Circuit Next node
Links
2.1 (LEGATO) SVA-0 0
I would expect that the next node should be 2.210 (DUSTY), but it doesn't know how to get there.
--Marc
Marc Chametzky wrote
DUSTY is "TYPE ROUTING IV" and has two circuits, TCP-0-0 to LEGATO and
QNA-0 for the local network. DUSTY has connectivity to both LEGATO (and
the rest of HECnet) and also to LULU.
This is the way it should be.
I tried setting
DUSTY up as an area router, thinking that making it a level 2 router
would permit LULU's packets to go through DUSTY, but that didn't seem to
work either.
An area router isn't necessary since all your nodes (and LEGATO too) are
in the same area.
LULU, on the other hand, can only connect to DUSTY. It can't connect to
LEGATO.
Hmm. What makes you think this? I ask because LEGATO can connect to LULU
(I just tried it a minute ago), so it is working at least one way.
Bob
I have my new system, LULU, up and it's connected via Ethernet on the same network segment as DUSTY. LULU is a non-routing end node.
DUSTY is "TYPE ROUTING IV" and has two circuits, TCP-0-0 to LEGATO and QNA-0 for the local network. DUSTY has connectivity to both LEGATO (and the rest of HECnet) and also to LULU.
LULU, on the other hand, can only connect to DUSTY. It can't connect to LEGATO.
I thought that DUSTY, being a routing node, would route packets between its two circuits, but that appears not to be the case. I tried setting DUSTY up as an area router, thinking that making it a level 2 router would permit LULU's packets to go through DUSTY, but that didn't seem to work either.
What should I do in order to get DUSTY to route the packets from LULU to the rest of HECnet?
--Marc
Guys, just in case any of you fancy a play, I've installed MP/M II V2.1 on a SIMH Altair Z80 emulator.
It's accessible through CHIMPY by logging in as ALTAIR. There are a number of floppy drives (write locked) and a hard drive (writeable) as follows:
A: System Disk
B: Multiplan
C: VEDIT
D: WordStar
E: Games
I: Writeable hard drive.
Let me know how it's working!.
Sampsa
Marc Chametzky wrote:
http://www.sparetimegizmos.com/Downloads/DCN%20Node%20List.pdf
DUSTY and CALHAN appear to have the wrong addresses ...
I'd also like to add 2.212 as LULU, a Personal Alpha running OpenVMS ...
Ok, I've updated these things on the list.
Bob
Marc Chametzky wrote:
http://www.sparetimegizmos.com/Downloads/DCN%20Node%20List.pdf
Looking at this list, last updated in August 2008, I notice that my systems, DUSTY and CALHAN appear to have the wrong addresses. They are 2.210 and 2.211, respectively. The NCP database on LEGATO has them correct.
I'd also like to add 2.212 as LULU, a Personal Alpha running OpenVMS V8.3. I haven't yet decided where I'm going to run LULU, either in my VMware Fusion system on occasion, or as part of my "trailing-zone" environment in ESXi.
I've added LULU on MIM now.
I thought I'd take this chance to make two comments.
1. Nodenames in DECnet phase IV are actually local to each machine, so there is no strict requirement that we all have the same view on the name to address mappings. That said, it sure helps if we do, so I try to keep MIM up to date, and others can copy the nodename database from there (in VMS, you just do a "NCP COPY KNOWN NODES FROM MIM TO BOTH", if someone wants to know how you do in RSX, write me a mail. :-) )
2. In addition to the nodename database, I also keep a plaintext file with both nodenames people use, and nodenames people have asked to be reserved. You can find that at MIM::US:[DECNET]NODENAMES.ALL
In the same directory I also have a DECNET.TXT file, which have a list of all areas allocated, and by whom.
(And the file from sparetimesgizmos is not my creation or responsibility, so I can't make any changes in that.)
Johnny
--
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
Marc Chametzky wrote:
http://www.sparetimegizmos.com/Downloads/DCN%20Node%20List.pdf
Looking at this list, last updated in August 2008, I notice that my systems, DUSTY and CALHAN appear to have the wrong addresses. They are 2.210 and 2.211, respectively. The NCP database on LEGATO has them correct.
I'd also like to add 2.212 as LULU, a Personal Alpha running OpenVMS V8.3. I haven't yet decided where I'm going to run LULU, either in my VMware Fusion system on occasion, or as part of my "trailing-zone" environment in ESXi.
Ok. I've added LULU at my "master" database on MIM.
As for that list, I'm not the one compiling it, so I can't make any changes, or comments on it.
Johnny
--
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
http://www.sparetimegizmos.com/Downloads/DCN%20Node%20List.pdf
Looking at this list, last updated in August 2008, I notice that my systems, DUSTY and CALHAN appear to have the wrong addresses. They are 2.210 and 2.211, respectively. The NCP database on LEGATO has them correct.
I'd also like to add 2.212 as LULU, a Personal Alpha running OpenVMS V8.3. I haven't yet decided where I'm going to run LULU, either in my VMware Fusion system on occasion, or as part of my "trailing-zone" environment in ESXi.
--Marc
