- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: osidiag: Timed out awaiting activity from rem...
Operating System - HP-UX
1823202
Members
3758
Online
109648
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
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
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
тАО06-30-2004 10:53 PM
тАО06-30-2004 10:53 PM
osidiag: Timed out awaiting activity from remote
Hi,
When we run the "TRANSPORT" test in x25, the above error is got.
It also says:
"The remote's state may not be synchronized with the local State.
Verify you were running compatible tests on both sides. The remote site may have received an error prior to connection establishment, check the errors and addresses used on remote side. To extend the timeout value, go to the Utilities menu and select "Wait Time" "
Any pointers to the resolution ??
Thanks & Regards,
Ramesh.K.R.
When we run the "TRANSPORT" test in x25, the above error is got.
It also says:
"The remote's state may not be synchronized with the local State.
Verify you were running compatible tests on both sides. The remote site may have received an error prior to connection establishment, check the errors and addresses used on remote side. To extend the timeout value, go to the Utilities menu and select "Wait Time" "
Any pointers to the resolution ??
Thanks & Regards,
Ramesh.K.R.
hai
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-04-2004 04:44 PM
тАО07-04-2004 04:44 PM
Re: osidiag: Timed out awaiting activity from remote
Hello Experts,
No repplys from anyone ????
Regards,
Ramesh.K.R.
No repplys from anyone ????
Regards,
Ramesh.K.R.
hai
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-06-2004 10:04 AM
тАО07-06-2004 10:04 AM
Re: osidiag: Timed out awaiting activity from remote
Ramesh,
I don't claim to be an X25 expert.
And there is little detail here.
But try this.
Go to the system you are connecting to and run the following:
netstat -an |grep -i fin
If you have a finwait2 state on the X25 port it could be causing your problem.
I have seen this on other transports.
By default finwait on HPUX is set to never time out. As these "Should never occur"
On later versions of the OS this value can be get/set with:
"ndd -get /dev/tcp tcp_fin_wait_2_timeout"
if this value is 0 it is never timeout.
"ndd -set /dev/tcp tcp_fin_wait_2_timeout 3600"
A rather quick timout for finwait2 but I have gone as low as 1200 when very impatient to see results.
If the finwait2 remains after timout interval the only solution I have seen is reboot. But occasionally a client may again corrupt the port even after the boot.
Add finwait_timout setting to /etc/rc.config.d/nddconf prior to boot to have it take effect on bootup.
Hope that helps.
Joy
I don't claim to be an X25 expert.
And there is little detail here.
But try this.
Go to the system you are connecting to and run the following:
netstat -an |grep -i fin
If you have a finwait2 state on the X25 port it could be causing your problem.
I have seen this on other transports.
By default finwait on HPUX is set to never time out. As these "Should never occur"
On later versions of the OS this value can be get/set with:
"ndd -get /dev/tcp tcp_fin_wait_2_timeout"
if this value is 0 it is never timeout.
"ndd -set /dev/tcp tcp_fin_wait_2_timeout 3600"
A rather quick timout for finwait2 but I have gone as low as 1200 when very impatient to see results.
If the finwait2 remains after timout interval the only solution I have seen is reboot. But occasionally a client may again corrupt the port even after the boot.
Add finwait_timout setting to /etc/rc.config.d/nddconf prior to boot to have it take effect on bootup.
Hope that helps.
Joy
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP