Operating System - HP-UX
1823064 Members
3155 Online
109645 Solutions
New Discussion юеВ

osidiag: Timed out awaiting activity from remote

 
Ramesh.K.R.
Regular Advisor

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.

hai
2 REPLIES 2
Ramesh.K.R.
Regular Advisor

Re: osidiag: Timed out awaiting activity from remote

Hello Experts,

No repplys from anyone ????

Regards,
Ramesh.K.R.
hai
Joy Orton
Occasional Advisor

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