[Info-vax] VMS startup - building LLA devices

[Carl Friedberg]

At a former client, we were using LAN failover. We had a series of
minor problems, and decided LAN failover configuration caused more
problems than it solved. We had one failure in the years we were using
that configuration, and it did work. However, it was too complicated;
which outweighed potential benefits. At a convenient time, we removed
the LAN failover, and had just one connection from the Itanic servers
to the network switch (we were using two independent network switches,
but they were in fact Cisco linked, so there was a single point of
failure. I don't believe the single EWA0 config ever caused a problem,
and it was much simpler. This was in a 3 node Itanium cluster.

Carl Friedberg

On Tue, Mar 21, 2023 at 1:40 PM fossey...--- via Info-vax
<info-vax at rbnsn.com> wrote:
>
> Hi Marc Van Dyck,
>
> It is LANACP that is run to create the LLx device along with VLx device early in boot
> LANACP is both a server process started up by VMS$DEVICE_STARTUP.COM and
> and image loaded during early boot to perform the network device creation and build.
>
> I've had a conversation with Dick Stockdale about this a while ago.
>
> The reason the LAN$DEVICE_DATABASE.SEQ had to be created in because when LANACP first runs early in boot there is no ability to process RMS indexed files.
>
> Interestingly on X86 in system disk they have split the LANACP image into LANACP.exe and LANACP_BFS.exe and it is the latter along with the .SEQ file that reside on the Memory Disk with LANACP.exe and the.DAT file on the main system disk.
>
> Cheers, Laurence
> _______________________________________________
> Info-vax mailing list
> Info-vax at rbnsn.com
> http://rbnsn.com/mailman/listinfo/info-vax_rbnsn.com



-- 
www.comets.com