We have a machine that I just did a fresh start upgrade on, and we
can't get the LAT devices to connect.  I have checked everything I can think
of but our Instrument Interfacing department says that instruments going to
terminal servers on LAT cannot connect.
        One thing I do notice is that the file command shows ttys
differently on 4.0f.  Example:
        (5.1a)
        OSF1 osflab_at_GCH:/sbin/init.d # file /dev/tty4a
        /dev/tty4a:     character special (5/133)
        (4.0f)
        OSF1 gabby_at_SIS:/ # file /dev/tty2b
        /dev/tty2b:     character special (5/133) LAT #0 terminal #133
        The ttys (we were using BSD-style so I want to keep that) have been
created and getty runs on only 9 of them.  Here are some other things I have
looked at:
        OSF1 osflab_at_GCH:/sbin/init.d # /sbin/sysconfig -s | grep dlb
        dlb: loaded and configured
        OSF1 osflab_at_GCH:/sbin/init.d #  /sbin/sysconfig -q lat
        lat:
        The (lat:) was the same response I got in 4.0f.
        OSF1 osflab_at_GCH:/sbin/init.d # setld -i|grep LAT
        OSFLAT520            installed              Local Area Transport
(LAT) (General
        I can see a device pointing to a terminal and port after configuring
it with latcp -A
        OSF1 osflab_at_GCH:/sbin/init.d # latcp -dPp tty4a
 
        Local Port Name = tty4a     <application>
 
                Specified Remote Node Name = DSV703
                Specified Remote Port Name = PORT_12
        If I go into the lat setup, it shows that lat is running.
        Users can come in on LAT terminals where getty is running.
        OSF1 osflab_at_GCH:/sbin/init.d # who
        ...
        UNAME        tty02       Dec  9 15:20
        ...and I was just told that a user could send an outbound print job
to tty01, but that is strange because it has a getty running on it and it's
supposed to be connected to a modem!  Maybe he was mistaken about the port
number.
        /dev/tty01:     character special (35/1) ACE_SLU #0 terminal #1
modem_control on
        I've checked everything I can think of.   Everything is OK for
inbound terminal connections, but nothing can connect to a server port.
        I haven't had this problem with any of the 20 or so sites that I've
upgraded, but I can't say for sure that they weren't all on TCP.  This may
well be the first site with LAT that I've done.
        Any ideas?  Anything else to check?
Thanks
-denise
"Customer service may be the only way that a company can distinguish
itself from its competition these days."  -H. Frank Gibbard
Denise McCracken, Systems Software Specialist
Misys Health Care, Tucson, AZ
Certified Tru64 v5 Systems Administrator
Comptia Network+ Certified Professional
Received on Tue Dec 09 2003 - 23:13:28 NZDT