Operating System - OpenVMS
1830207 Members
1400 Online
109999 Solutions
New Discussion

Re: ucx socket elimination

 
Edgar Ulloa
Frequent Advisor

ucx socket elimination

Hi

I have conections a cluster via telnet.
if I lost my switch or hub(power outage) my users that connect via this switch, they lost the conection in all pc applications (internet, mail and emulator for connect vms kea!), but in to my system the user keep the same ip and comunication socket.

all users only are be able to connect twice (maxjobs=2), but after power outage the sesion not died. when the try connect again the system reject because the job is max limit.

Some one know if I need configure my ucx at moment I loss the network automacly the socket kill or telnet sesion kill completly..?

Thanks
5 REPLIES 5
Michael Yu_3
Valued Contributor

Re: ucx socket elimination

Hi Edgar,

You can use keepalive to get rid of the disconnected telnet sessions.

Try the following.

UCX> set service telnet/proto=tcp=probe=xx
UCX> set service telnet/proto=tcp=drop=n

(xx and n are set depending on how soon you would like to have your disconnected sessions terminated.)

This can be used to shorten the time for the disconnected sessions to disappear.

Which version of UCX or TCP/IP services are you running?

There are fixes on different versions for dangling telnet sessions. So make sure you have the latest ECO kit for the version of TCP/IP you use.

Thanks and regards.

Michael
Sebastian Bazley
Regular Advisor

Re: ucx socket elimination

Or perhaps you could enable virtual terminals, so the users could reconnect to the lost sessions.
Galen Tackett
Valued Contributor

Re: ucx socket elimination

Edgar,

The suggestions from Michael and Sebastian both look good to me, and we actually began using Michael's before seeing it posted here--found it in the manuals first.

We modified an in house application to use socket keepalive, for similar situations where a link goes down and we need the socket closed at the other end.

So this just might take care of your problem, too. But if Sebastian's suggestion works for you, you may prefer it. After a connection is dropped, user will be able to re-connect to the virtual terminal and continue working.
Edgar Ulloa
Frequent Advisor

Re: ucx socket elimination

I was monitoring all the network because I try to locate why reason my sessions are disconnected, Im not sure if the real problem is in my network or bad parameter in my ucx. example you are in session and your session is over in 20 minutes, but is random, no same user, no same segment of network. but the process is not died, is keep in to system.

Im looking for a parameter to check or any idea and know if the network have gaps or any parameter in my ucx.

no errors in operator.log no errors in to dec event I set my security audit only for alarm logout and not have a lot information.

Thanks for all your time
Michael Yu_3
Valued Contributor

Re: ucx socket elimination

Hi Edgar,

When you said your session is over 20 minutes, do you mean an idle session or a busy session?

You can try the following.

1. On one telnet session, start a continuous ping so that data is passing through the telnet session for display. See if this will be disconnected.

2. On another telnet session, just leave it idle and see if it is disconnected.

If only the idle session is disconnected and the process on OpenVMS is still there, then the disconnect was not done by UCX. It might be likely that there is a firewall between the UCX host and your telnet clients. If this is the case, the keepalive will also protect your idle telnet session being 'killed' by the firewall.

Thanks and regards.

Michael