- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: [LAT connect failure on BASEstar history]
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-27-2005 06:30 PM
тАО04-27-2005 06:30 PM
[LAT connect failure on BASEstar history]
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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-27-2005 06:48 PM
тАО04-27-2005 06:48 PM
Re: [LAT connect failure on BASEstar history]
$ 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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-27-2005 08:23 PM
тАО04-27-2005 08:23 PM
Re: [LAT connect failure on BASEstar history]
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-27-2005 09:12 PM
тАО04-27-2005 09:12 PM
Re: [LAT connect failure on BASEstar history]
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-27-2005 09:28 PM
тАО04-27-2005 09:28 PM
Re: [LAT connect failure on BASEstar history]
Actually, that errors happened on a specific port. these happended on random port.
I will reset some decserver.....hope to resolve problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-28-2005 12:36 AM
тАО04-28-2005 12:36 AM
Re: [LAT connect failure on BASEstar history]
Purely Personal Opinion