[Info-vax] DECserver/LAT across DECnet areas?

[Robert A. Brooks]

On 7/22/2023 7:07 PM, Scott Dorsey wrote:
> Andy Green  <agreen0868 at gmail.com> wrote:
>> Is there a way to get the DECserver 200 to recognize the VAX on 2.2 so I can log into it using the DECserver?  Is that supposed to happen automagically since the routers are there, or do I have to do something special?  Or is it not possible?
> 
> LAT is not decnet.  Vaxcluster isn't decnet either.  LAT is its own protocol,
> and it's one that doesn't route.  You might be able to write some sort of
> LAT bridge but I have never seen one in place before because really the L
> in LAT is for Local.

In the olden days, a terminal server needed a DECnet address in order to be MOP 
downline-loaded.

That is, when an unsolicited MOP request would come in, Phase IV DECnet would 
search its volatile database looking for a MAC address match with the incoming 
request.

If a match was found, and there was a file defined with which that node node 
could be loaded, then that node would attempt to fulfill the MOP request.

Later on, the advent of LANCP allowed MOP clients to be defined that had no 
relationship with DECnet.

I am less familiar with how Phase V sorts out MOP stuff; mercifully, I've never 
had to debug the Phase V MOP implementation.

Neither the DECnet nor LAT protocols have anything to do with how a terminal 
server is loaded via MOP.

-- 

                    --- Rob