Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

[LAT connect failure on BASEstar history]

BG Jeong
Advisor

[LAT connect failure on BASEstar history]

One of our customers has a BASEstar application. When I do a "show history" whitch display BASEstar event log.
Some event repeatedly occured like below messages.

Event 21.25.1 occurred at 10-MAR-2005 19:52:59.66
Error occurred on VAX port LTA781:.
LAT connect failure.
device timeout

Event 10.86.13 occurred at 10-MAR-2005 19:52:59.66
DCM request unsuccessful: DS_CONNECT_DEVICE detected an error from NI_CONNECT
Device's network communication is offline.

Event 10.86.79 occurred at 10-MAR-2005 19:52:59.66
Illegal or unexpected abort requested for device: S2_PLC current state: 2

Event 10.86.84 occurred at 10-MAR-2005 19:52:59.66
DCM request unsuccessful: DS_RECONDEV_AST detected an error from DVB_STATUS
Device's network communication is offline.

Event 21.25.1 occurred at 10-MAR-2005 19:52:59.66
Error translating message text.

I searched web, but I'm not found anything.

Does anyone see that the problem could be other?
Is there anything that I can check?

please inform about that event error?
Tru64 from Korea
5 REPLIES
Karl Rohwedder
Honored Contributor

Re: [LAT connect failure on BASEstar history]

Aside from BASEstar I would check device LTA781:

$ MC LATCP
LATCP> SHOW PORT LTA781

gives you the name and port of the target terminalserver. Check if server is up and running. May be your network folks just cut off the LAT protocol?

regards Kalle
Jan van den Ende
Honored Contributor

Re: [LAT connect failure on BASEstar history]

Yes,

I share Kalle's fear! I have seen that done before. Please check with Network Management.

One other thing that HAS happened to us was the need to reboot the terminal server after about 200 days.
Most clear symptom: if you look at the LTA device (see Kalle), then the Status was "Connecting". In normal operation this status should last no longer than a few miliseconds.

(those were NOT |D|I|G|T|A|L| servers)

Proost.

Have one on me.

jpe
Don't rust yours pelled jacker to fine doll missed aches.
Anton van Ruitenbeek
Trusted Contributor

Re: [LAT connect failure on BASEstar history]

Another problem using LAT.

We use to have Digital network products and all the protocols didn't have any problem over the network.
Then we went to IBM sort of material. LAT hangs every appr. 250 days, but was to work with. Not good, but yeh they want to go to one sort of network equipment.
Now we changed to Cisco (all the expensive stuff), and now we have whitout any reason sometimes no LAT. The network department say 'Hey, we dont see anything, everything works'. Yes right, they only look at IP.
So, we bought this network for IP _AND_ LAT but Cisco drops sometimes LAT.
We think when the Cisco gets to many traffic, it drops anything besides IP.
Maybe it has to do something with SpanningTree fo Cisco.

AvR
NL: Meten is weten, maar je moet weten hoe te meten! - UK: Measuremets is knowledge, but you need to know how to measure !
BG Jeong
Advisor

Re: [LAT connect failure on BASEstar history]

Thanks your kindness.

Actually, that errors happened on a specific port. these happended on random port.

I will reset some decserver.....hope to resolve problem.


Tru64 from Korea
Ian Miller.
Honored Contributor

Re: [LAT connect failure on BASEstar history]

certain old versions of the DECserver software had memory leaks and therefore needed to be reboted occationally.
____________________
Purely Personal Opinion