Rlogin connections

[sid_22]

Hi

We have HP-UX 11i after 60 rlogin connections we cant open other connecions
How can I do to allow more than 60 rlogin connections at the same time.

According to my investigation in this foru, it must be the kernet parameter maxfiles but I don’t In which file it is and what is the impact of its modification

Thanks

[Alex Lavrov.]

It's "npty" kernel parameter.

do:
kmtune | grep npty
It's probably 60. To change it:

kmtune -s npty=100
mk_kernel
shutdown -ry now

REQUIRES BOOT!

Alex.

[Giri Sekar.]

Hi:

Looks like you have change your nstrpty.
kmtune -q nstrpty (check existing value)
run sam-configurable Parameters-nstrpty..set it to 300 (or any desired value)
reboot.
After reboot..
insf -d pts -s 512 (Build the pts files)

Thanks

Giri.

[Giri Sekar.]

Hi:

The last step build it to 512 if you set the nstrpty to that value.

Thanks

Giri.

[Alex Lavrov.]

"nstrpty" must not be extremely bigger than "npty". Currently, your "npty" is probably 60, so if you intent to increase "nstrpty" to 200-300, you should consider increase "ntpy" too.



http://docs.hp.com/en/939/KCParms/KCparam.NstrPty.html


Alex.

[Steven E. Protter]

The default number of telnet/rlogin pty sessions allowed on an HP-UX system defaults to 60.

You need to build a new kernel with a number of sessions that allows you enough rlogin sessions with a comfortable margin for error.

Alex document is a perfect explanation.

kmtune -s nstrpty 200
kmtune -s npty 200

Or use sam.

Then compile a new kernel, put it into production and boot the box.

Then the problem will go away until you have 200 simultaneous rlogins.

Note that rlogin is not a secure way to handle logins, continue secure shell.

SEP

[Steven E. Protter]

In my opinion I and others posted the wrong kernel variables to fix, though they may also need to be revised.

nstrpty 60 - 60
nstrtel 60 - 60


Those two need to be bumped up to allow more than 60 simultaneous telnet connections that use pty pseudo terminals.

They need to be pushed up higher than the anticipated number of simultanous users.

SEP

[sid_22]

Thank you all for your answers.

If I understood well I must modify the nstrpty and npty parameters as follow :

kmtune -s nstrpty 200
kmtune -s npty 200

(For 200 connections for example)

Then I must recompiler the kernel.
Can somebody show me a simple method to recompile the kernel (excuse my ignorance)

Thank you

[Alex Lavrov.]

kmtune -s npty=200
kmtune -s nstrpty=200
kmtune -s nstretl=200
mk_kernel


Then reboot and it should be fine.

Alex.

[Alex Lavrov.]

Oops, sorry, forgot someting:

After you do "mk_kernel" do:
kmupdate

mk_kernel will build a new kernel and kmupdate will schedule the replacement of the old kernel with a new one on the next boot.

Alex.

[Raj D.]

Hi Sid ,

Dont forget to keep a copy of the working kernel , incase of any problem, [ being a safer side.]

# cd /stand/vmunix
# cp vmunix vmunix.ok
# cp system system.ok

Cheers,
Raj.

[sid_22]

Hi

We had make the following :

>kmtune -s npty=200
>kmtune -s nstrpty=200
>kmtune -s nstretl=200
>mk_kernel
>kmupdate
And we restart the server

We have the new parameters (please, see the attached file) but we still limited by a maximum of 60 rlogin connections.

Can someone help please

Thanks

[Fabio Ettore]

Hi,

sorry, why don't recompile the kernel by SAM?

- launch
sam ---> Kernel Configuration ---> Configurable Parameters --->

search for nstrpty

select from menu Actions ---> Modify Configurable Parameter

and change the value to 200.

Then follows Ok and reboot.

After boot up launch by root

insf -d pts -s 200

Does it solve your problem?

Best regards,
Fabio

[Muthukumar_5]

Is your new kernel parameter changed for,

# kmtune | grep nst with 200 for nstrpty and nstrtel

It is better to do with sam.

hth.

[Bill Hassell]

The problem is that npty and nstrpty (and also nstrtel) set limits in the kernel but each connection requires a device file pair and if you don't run insf to create these device files, then you'll not get more than your original 60. That's why using sam is the recommended method--sam will create the device files automatically before building the new kernel.

I would set all 3 parameters (npty, nstrtel and nstrpty) to 200 using sam and you'll have all you device files and new limits. Otherwise, run insf to install the device files:

insf -e -s 200 -n 200