Quite a while ago, I asked the following (dumb) question:
>I have a couple of Dec Alphas running osf1 v2.0. Someone wants
>to "connect" to them via the local terminal server ( a decserver
>500, I think. It's a LAT thing, anyway.) How does one do this?
>I suppose I need decnet numbers, right? Do I need some layered
>product?
I was told
>It's in the System Management FM
Actually, for 1.3, I could only find reference in the index
to the "Release Notes." And this was more related to after
the fact diagnostic matters. For 3.0 manuals, there
actually was a reference in the System Admin manual index to
a page that discussed setting the kernel for LAT. However,
the real meat was in the Network Admin and problem solving
manual. For 1.3, this apparently useful information seems to be lacking
in the corresponding manual. So the 3.0 manuals appear to
be a definite improvement. Altho, it would be nice to
have things cross-referenced. I didn't read all the manauls,
just skimmed them. So I could have missed things.
>is the osf1 system and the LAT terminal server on the
>same extended, bridged ethernet (no routers?)
If so, stop and pause. If there is a router between the osf1
systems and the terminal servers which does not bridge the LAT
protocol, then the LAT protocol will not get from the terminal
server to osf1.
>possibly need to install LAT subset
E.g., setld -l /cdrom/ALPHA/BASE OSFLAT200
>add the "options LAT"
Anyway. You need the following (if not already there) in the kernel
configuration file:
options LAT
(options DLB ??? not sure what this is. someone suggested it,
tho.)
>remake kernel via doconfig
E.g., shutdown, boot genvmunix (>>>b -fl i [and answer with genvmunix,]
and run bcheckrc, and doconfig.
>generate a new system-specific configuration file
I don't quite see the need for this one (but then I haven't
actually done any of this yet and hopefully never will.)
>run /usr/sbin/latsetup
Then run /usr/sbin/latsetup. This apparently creates the
necessary special files (e.g., /dev/lat,) modifies the /etc/inittab
file (gettys,) etc.
Apparently, you can do some/all of this via setup (choose LAT setup) as well.
Moreover, you don't need decnet numbers per see unless you intend to download
to the LAT terminal servers (MOP subset.)
Relevant man pages are latcp and latsetup.
Actually, it doesn't seem quite so obvious as some of my respondents
seemed to think. I, for one, haven't had a lot of experience
with Dec equipment and, especially, their network protocols.
(I.e., you can never tell what sort of gyrations etc. you
might have to do.)
Anyway, it turns out that, in my case, the terminal server
and the osf1 machines are seperated by a router. I waved my hands
and said it probably couldn't be done, regardless. I'm anxious
to kill off user dependency on LATish and DECNETish things.
Sorry it took so long for me to summarize this information
(classic overworked and underpaid I'm sure you're all too
familiar with.)
My very sincere thanks to all those who responded as well.
Received on Mon Jan 23 1995 - 17:53:54 NZDT