Another listmember has given me the required incantations.
It was looking good for the IGS for a while. To my surprise, it turned
out to
have DECnet capable software. Unfortunately, it was too good to last.
This
machine is now looking a bit sick. It keeps rebooting and not getting
past
the first two lines of the startup banner.
The 1600 does not have DECnet capable software.
Regards,
Peter Coghlan.
Hi Peter.. when is this the IGS's that have a 16Mhz m68020 in them? I
think I've got one or two (Although I've not dug that deep in over a
decade).
Al.
On 2012-04-30 22:44, Dave McGuire wrote:
On 04/30/2012 03:54 PM, Johnny Billquist wrote:
Here is my current node list. AXPEE is up 24/7. Last night I
finished unloaded a truck full of stuff from my old house, including
lots of VAXen, so there will likely be some more coming up soon.
Node Name System
------------------------------------------------------------------
61.1 GW Cisco 7206VXR, IOS 12.3
61.2 AXPEE DS10L, 466MHz, 1GB, 120GB, VMS 8.3
61.3 EBOLA VAX 4000/700A, 128MB, 4GB, VMS 7.3
61.4 MECCA PDP-11/53, RSTS/E v10.1
61.5 FANG PDP-11/70, RSTS/E v10.1
61.50 RA Linux
Gothca.
By the way, I know "GW" is a pretty generic name; you can leave that
out if you'd like. It's just my router here.
One convention that I've seen/used in the past have been to call the area router for areas in DECnet names like "AnnRTR", where nn is the area number. So, in your case, that would be A61RTR. It's an idea anyway. But I'll leave it to you to decide what to call the machine. I just keep the records...
Another file you might want to look at, if you prefer, would be
MIM::US:[DECNET]NODENAMES.DAT. The format should be obvious if you check
either that, or FIX.CMD
By the way, I hope you know that VMS can copy the nodename database
directly from another machine without you having to hack files on your
own, if that is the reason why you asked for a file...
(from your reference below, I just did that)
:-)
What I'll need to hack the files for, though, are Linux, RSTS/E (most
likely), and the Cisco. I'll just do it with an awk script, that'll be
quick and easy.
Right. Although, you might be able to more or less use the file as is for RSTS/E...
And unless you actually need to do stuff on the Cisco, you don't really have to have a complete nodename database in there...
Assuming you are running Phase IV, just do:
"MCR NCP COPY KNOWN NODES FROM MIM TO BOTH"
and you are set.
Oh nice, I didn't know about that trick. Thanks!
You are welcome. :-)
Now, under RSX, you do this in a very different way. And don't even ask me about RSTS/E, since I don't know for that one. ;-)
(Nor do I know a TOPS-20 equivalent, but I would like to...)
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
On 04/30/2012 03:54 PM, Johnny Billquist wrote:
Here is my current node list. AXPEE is up 24/7. Last night I
finished unloaded a truck full of stuff from my old house, including
lots of VAXen, so there will likely be some more coming up soon.
Node Name System
------------------------------------------------------------------
61.1 GW Cisco 7206VXR, IOS 12.3
61.2 AXPEE DS10L, 466MHz, 1GB, 120GB, VMS 8.3
61.3 EBOLA VAX 4000/700A, 128MB, 4GB, VMS 7.3
61.4 MECCA PDP-11/53, RSTS/E v10.1
61.5 FANG PDP-11/70, RSTS/E v10.1
61.50 RA Linux
Gothca.
By the way, I know "GW" is a pretty generic name; you can leave that
out if you'd like. It's just my router here.
Another file you might want to look at, if you prefer, would be
MIM::US:[DECNET]NODENAMES.DAT. The format should be obvious if you check
either that, or FIX.CMD
By the way, I hope you know that VMS can copy the nodename database
directly from another machine without you having to hack files on your
own, if that is the reason why you asked for a file...
(from your reference below, I just did that)
What I'll need to hack the files for, though, are Linux, RSTS/E (most
likely), and the Cisco. I'll just do it with an awk script, that'll be
quick and easy.
Assuming you are running Phase IV, just do:
"MCR NCP COPY KNOWN NODES FROM MIM TO BOTH"
and you are set.
Oh nice, I didn't know about that trick. Thanks!
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On 04/30/2012 03:41 PM, Peter Coghlan wrote:
They're trivially easy to crack if you have console access. Drop me a
note if you want to work on those and have trouble finding the
appropriate info.
Thanks Dave.
Another listmember has given me the required incantations.
Excellent.
It was looking good for the IGS for a while. To my surprise, it turned out to
have DECnet capable software. Unfortunately, it was too good to last. This
machine is now looking a bit sick. It keeps rebooting and not getting past
the first two lines of the startup banner.
Hmm, that's not good. If memory serves, in an IGS, IOS resides in a
bank of EPROMs and the memory is in the form of 30-pin SIMMs. I'd try
re-seating those and see how far you get.
The 1600 does not have DECnet capable software.
Perhaps Brian can help out here.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On 04/30/2012 09:09 PM, Peter Lothberg wrote:
What is your IP address? Mine are on the HECnet mailinglinst.
My 7206VXR's external-facing interface is 50.73.179.1.
Hum.. That is on a network that refuced to peer with me:
MM>!traceroute 50.73.179.1
traceroute to 50.73.179.1 (50.73.179.1), 64 hops max, 52 byte packets
1 R29A-GW.Stupi.SE (192.108.198.254) 0.260 ms 0.245 ms 0.287 ms
2 R29BFR-GE-2-0-6-GW.Stupi.NET (192.108.195.150) 0.435 ms !H * 0.303 ms !H
Wow, that's odd. I have no idea why that'd be happening.
But it will work from the box in Reston..
interface Tunnel4001
no ip address
ip broadcast-address 0.0.0.0
decnet cost 10
tunnel source 199.0.131.2
tunnel destination 50.73.179.1
Excellent, thank you! I have routes for area 59 via Reston.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On 04/30/2012 03:39 PM, Johnny Billquist wrote:
Might already have that (more or less).
MIM::US:[DECNET]FIX.CMD have all the nodes except MIM herself. One per
line, in a format that is usable for NCP (or CFE in RSX).
Ok. Slight chicken/egg problem, though...what's the node address
of MIM?
*The* most important machine on HECnet... And it's not already in your
database... Tsk... :-)
Mmm-hmm. ;)
1.13
Got it. Thanks!
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On 2012-04-30 21:46, Johnny Billquist wrote:
On 2012-04-30 21:38, Dave McGuire wrote:
Here is my current node list. AXPEE is up 24/7. Last night I
finished unloaded a truck full of stuff from my old house, including
lots of VAXen, so there will likely be some more coming up soon.
Node Name System
------------------------------------------------------------------
61.1 GW Cisco 7206VXR, IOS 12.3
61.2 AXPEE DS10L, 466MHz, 1GB, 120GB, VMS 8.3
61.3 EBOLA VAX 4000/700A, 128MB, 4GB, VMS 7.3
61.4 MECCA PDP-11/53, RSTS/E v10.1
61.5 FANG PDP-11/70, RSTS/E v10.1
61.50 RA Linux
Gothca.
Another file you might want to look at, if you prefer, would be
MIM::US:[DECNET]NODENAMES.DAT. The format should be obvious if you check
either that, or FIX.CMD
By the way, I hope you know that VMS can copy the nodename database directly from another machine without you having to hack files on your own, if that is the reason why you asked for a file...
Assuming you are running Phase IV, just do:
"MCR NCP COPY KNOWN NODES FROM MIM TO BOTH"
and you are set.
replace MIM with 1.13, if you don't have MIM in your database already.
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
On 2012-04-30 21:38, Dave McGuire wrote:
Here is my current node list. AXPEE is up 24/7. Last night I
finished unloaded a truck full of stuff from my old house, including
lots of VAXen, so there will likely be some more coming up soon.
Node Name System
------------------------------------------------------------------
61.1 GW Cisco 7206VXR, IOS 12.3
61.2 AXPEE DS10L, 466MHz, 1GB, 120GB, VMS 8.3
61.3 EBOLA VAX 4000/700A, 128MB, 4GB, VMS 7.3
61.4 MECCA PDP-11/53, RSTS/E v10.1
61.5 FANG PDP-11/70, RSTS/E v10.1
61.50 RA Linux
Gothca.
Another file you might want to look at, if you prefer, would be MIM::US:[DECNET]NODENAMES.DAT. The format should be obvious if you check either that, or FIX.CMD
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
They're trivially easy to crack if you have console access. Drop me a
note if you want to work on those and have trouble finding the
appropriate info.
Thanks Dave.
Another listmember has given me the required incantations.
It was looking good for the IGS for a while. To my surprise, it turned out to
have DECnet capable software. Unfortunately, it was too good to last. This
machine is now looking a bit sick. It keeps rebooting and not getting past
the first two lines of the startup banner.
The 1600 does not have DECnet capable software.
Regards,
Peter Coghlan.
On 2012-04-30 21:34, Dave McGuire wrote:
On 04/30/2012 03:29 PM, Johnny Billquist wrote:
I even have automated populating the DECnet permanent nodename database
on MIM from the Datatrieve database. So when I get updates, I just
insert them into Datatrieve, and then kick off the updating process.
Excellent.
Hmm ok. Do you know if the RSX distribution of DTR-11 run under
RSTS/E's RSX RTS? I don't have an operational RSX-11 system here. (yet)
I very much doubt it would work. DTR is playing some pretty low level
tricks, including having multiple tasks and interprocess communication
under RSX.
Yuck.
:-)
And unfortunately I don't have any leads to DTR-11 for RSTS/E. I assume
it did exist?
I'm not certain; I've never worked with it. I'm willing to bet that
it did, though.
Just did a check in the wayback machine, and apparently at least Mentec did not sell it. Anyone know if it did exist?
Oh ok, thank you. I'd love to have it just as a text file that I can
massage into my various machines here. One line per entry would be best
for me. Is that doable on your end without any trouble?
Might already have that (more or less).
MIM::US:[DECNET]FIX.CMD have all the nodes except MIM herself. One per
line, in a format that is usable for NCP (or CFE in RSX).
Ok. Slight chicken/egg problem, though...what's the node address of MIM?
*The* most important machine on HECnet... And it's not already in your database... Tsk... :-)
1.13
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
