hpux telnet session is getting hung after about 15 minutes Post: 302359600

Sponsored Content

Operating Systems HP-UX hpux telnet session is getting hung after about 15 minutes Post 302359600 by mhbd on Wednesday 7th of October 2009 03:38:40 AM

10-07-2009

Registered User

Hi, many thanks for your reply with suggestions. Case 1 is not applicable as value of TMOUT is 0, it also not found in .profile, .login etc. /etc/skel is empty.

Now about case 2, I am now going through nddconf file and shall discuss with our Network admin before making any change.

Hope it will solve our problem.

Quote:

Originally Posted by Gecko12332

Hey -
There could be a few things going on:
1) If you are using HP-UX outta the box 11.11 telnetd(aemon) via inetd, then check to make sure you don't have a $TMOUT variable is set upon login. The standard telnetd with HP-UX will look at this var. IE: echo $TMOUT If there is a value, you can set to =0 OR find out you .profile, .login, etc and change. Then you can update the 'skel' login files which should live in /etc/skel.
2) If 1) is not the case, then talk to your network admin, they might have certain rules invoked that even though you have an active TCP connection over telnet, if there isn't any generating traffic, the inline router, (if routing) TCP session timeout configured at switch level, or even an active state-full firewall that will drop connections after X time. You can also sorta trick 'schtuff' like this by setting a TCP keep-alive ACK via ndd in HP-UX. I say, "sorta" because depending on the level of experience your network admin has and the equipment, you can also set known keep-alive watchdogs that will do deep packet inspection and see that it's nothing but a keep-alive and still close the connection for security reasons; once again, depending on your environment.

To modify your HP-UX host to send keep-alives for telnet try this:
1) cp -p /etc/rc.config.d/nddconf /etc/rc.config.d/nddconf.prior_keep_alive
2) vi /etc/rc.config.d/nddconf

Look for "NDD_NAME" (minus quotes)
Uncomment (remove #) if needed and put:
NDD_NAME=[0]=tcp_keepalive_interval

THEN set the interval:
NDD_VALUE[0]=300000

This will send a keep-alive data packet every 5 minutes. Each minute is 60000, so set for how often you would like.

Save and exit and run: ndd -c which will change the parameter without rebooting.

Once again, could be some timeout on the host, or network idle timeout. Good luck!

mhbd

View Public Profile for mhbd

Find all posts by mhbd

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

telnet session timeout

hi, we can set something such that if the user has been idle for a while, it will auto disconnect. where to do so? thanks

2. Shell Programming and Scripting

Telnet session does not expire

Dear friends.. Our project has a module that runs on handheld devices. Through the handheld we telnet to solaris where the application actually runs. I noticed that after starting a session through the handheld, if i go out of range or if i remove and replace the battery in the handheld, the...

3. Shell Programming and Scripting

Telnet Session

{ sleep 2 echo "$user" sleep 2 echo "$password" sleep 2 echo " ls" sleep 10 echo "exit" }| telnet $server I have a machine x and i have executed the above script on machine 'x'. i entered the...

4. UNIX for Dummies Questions & Answers

Unix Telnet session

Hi Is there any way whilst in a telnet session you can view your client machine name that you are using to connect to the Unix box ? :eek:

5. UNIX for Dummies Questions & Answers

Telnet Session to AIX

Hello, I have AIX 5.3 at home connected to netgear router. Port Forwarding has been enabled on the router. Problem is that if I want to telnet, I have to try 2 or 3 times before I can get a logon prompt. It times out for first or second time (Connection to session <IP_Address> failed: Connection...

6. UNIX for Dummies Questions & Answers

Disconnecting a telnet session

How can I disconnect an existing telnet session? The host is a serial port server with multiple ports. The users login using the host's name and a port, i.e. telnet host01 1235. Thanks.

7. HP-UX

ssh session getting hung (smilar to hpux telnet session is getting hung after about 15 minutes)

Our network administrators implemented some sort of check to kill idle sessions and now burden is on us to run some sort of keep alive. Client based keep alive doesn't do a very good job. I have same issue with ssh. Does solution 2 provided above apply for ssh sessions also?

8. SCO

Telnet session disconnects abruptly

I have inherited and SCO OpenServer Release 6 server. The clients connect using telnet to get to a proprietary database application for Service tickets. The issue I am currently having is that the connection just stops abruptly and you can see "telnet session terminated" on the terminal emulation...

9. Shell Programming and Scripting

How to break out of hung or waiting telnet session in shell script?

I have to put together telnet instructions for 100s of hosts for verifying basic connectivity and get output in a neat format. Problem- If a telnet is hung with message "Trying .... <hostname" due to firewall or routing issue the commands waits for a very long time before it times out and my...

LEARN ABOUT DEBIAN

bup-margin

bup-margin(1)						      General Commands Manual						     bup-margin(1)

NAME

       bup-margin - figure out your deduplication safety margin

SYNOPSIS

       bup margin [options...]

DESCRIPTION

       bup margin  iterates  through  all  objects  in	your  bup repository, calculating the largest number of prefix bits shared between any two
       entries.  This number, n, identifies the longest subset of SHA-1 you could use and still encounter a collision between your object ids.

       For example, one system that was tested had a collection of 11 million objects (70 GB), and bup margin returned 45.  That  means  a  46-bit
       hash  would be sufficient to avoid all collisions among that set of objects; each object in that repository could be uniquely identified by
       its first 46 bits.

       The number of bits needed seems to increase by about 1 or 2 for every doubling of the number of objects.  Since SHA-1 hashes have 160 bits,
       that  leaves 115 bits of margin.  Of course, because SHA-1 hashes are essentially random, it's theoretically possible to use many more bits
       with far fewer objects.

       If you're paranoid about the possibility of SHA-1 collisions, you can monitor your repository by running bup margin occasionally to see	if
       you're getting dangerously close to 160 bits.

OPTIONS

       --predict
	      Guess  the offset into each index file where a particular object will appear, and report the maximum deviation of the correct answer
	      from the guess.  This is potentially useful for tuning an interpolation search algorithm.

       --ignore-midx
	      don't use .midx files, use only .idx files.  This is only really useful when used with --predict.

EXAMPLE

	      $ bup margin
	      Reading indexes: 100.00% (1612581/1612581), done.
	      40
	      40 matching prefix bits
	      1.94 bits per doubling
	      120 bits (61.86 doublings) remaining
	      4.19338e+18 times larger is possible

	      Everyone on earth could have 625878182 data sets
	      like yours, all in one repository, and we would
	      expect 1 object collision.

	      $ bup margin --predict
	      PackIdxList: using 1 index.
	      Reading indexes: 100.00% (1612581/1612581), done.
	      915 of 1612581 (0.057%)

SEE ALSO

       bup-midx(1), bup-save(1)

BUP

       Part of the bup(1) suite.

AUTHORS

       Avery Pennarun <apenwarr@gmail.com>.

Bup unknown-															     bup-margin(1)