HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

Telnet listener on Decserver

 
SOLVED
Go to solution
labadie_1
Honored Contributor

Telnet listener on Decserver

Alpha Vms 6.2-1H3, DS90M.

I have some TNAxxx: ports created on a Decserver 90M.

When the Alpha crashes and reboots, the port can't be created
telnet/create host 2002 177
%TELNET-E-NOCRSES, Failed to create session
-SYSTEM-F-REJECT, connect to network object rejected

I have to reboot the DS90M in order to re-create the TNA, but not on all DS90M. I have not been able to spot a difference in configuration between the DS90M.

Any idea ?

DS90M> sh telnet listener 2002
Listener TCP-port: 2002 Listener Type: RAW TCP
Identification: Indicateur telnet
Ports: 2
Connections: Enabled
IP Address: 10.44.32.61

Local>
19 REPLIES
Karl Rohwedder
Honored Contributor

Re: Telnet listener on Decserver

Are all servers on the same software revision?

regards Kalle
labadie_1
Honored Contributor

Re: Telnet listener on Decserver

the versions are puzzling, as the DS90M which needs reboot has BL29-52, like another one which works fine (no need to reboot the DS90M in order to create the TNA device).

Another DS90M which works has BL10C-40.

:-(
Wim Van den Wyngaert
Honored Contributor

Re: Telnet listener on Decserver

I don't find it directly in the help but is it possible that keepalive must be enabled for TCP ? Or is the (show server) setting applied ? As long as listenner has a connection, it will not accept new ones.

Wim (without much knowledge of tcp on decservers)

BTW : great wine, only 1 bottle left
Wim
Karl Rohwedder
Honored Contributor

Re: Telnet listener on Decserver

I meant the SW version, or servers are running e.g.:

Network Access SW 2.3A, BL47-60

A sample telnet port on the VAX looks like:
Remote: vuw03t.wob.vw.vwg:2006
TNA9314: BG296: Outgoing Local: vuw30:49169
Remote: vuw02t.wob.vw.vwg:2007
TELNET> sho dev 9314/fu
Device TNA7224:
Access port name: (none)
Characteristics: (none)
Connection attempts: 0 (tries)
Connection interval: 0 (seconds)
Connection timeout: 0 (seconds)
Data high limit: 512 (bytes at VCI port)
Data low limit: 256 (bytes at VCI port)
Idle interval: 0 (seconds)
Idle timeout: 0 (seconds)
Network device name: (not connected)
Protocol: undefined (raw)
Local address: (not available)
port:
Remote address: (not available)
port:
Service type: None
labadie_1
Honored Contributor

Re: Telnet listener on Decserver

telnet > sh dev xxx/fu
is not available with ucx 4.2 Eco 4 :-(

the sw version is 2.2 for the DS90M working and the other not working, and 2.0 for another DS90M working.

Wim Van den Wyngaert
Honored Contributor

Re: Telnet listener on Decserver

on the decserver the default keepalive is 8 * 120 sec, so 16 minutes.
> show internet
should show the settings.

Wim
Wim
labadie_1
Honored Contributor

Re: Telnet listener on Decserver

120 (keepalive timer), 8 (retry) on the 2 DS90M with SW 2.2, on the third one, sh internet does not show any parameter

show internet
State: Enabled
Internet Address: 10.64.32.61
Subnet Mask: 255.255.0.0

Local>
Wim Van den Wyngaert
Honored Contributor

Re: Telnet listener on Decserver

And did you already wait let say 20 minutes after the crash of the alpha before rebooting the decserver ? How long ?

Wim
Wim
labadie_1
Honored Contributor

Re: Telnet listener on Decserver

I usually wait less than 10 minutes, when I can log in, I recreate the TNA devices.

I do not understand when I need to re-create the TNA devices only on one DS90M, not on the two others.
Walter Miller_1
Valued Contributor
Solution

Re: Telnet listener on Decserver

If you have not already done so, check the port configurations on the servers and look for differences.

Local> show port 2

Also next time you get the error check the status of the port to see if there is still a connection showing on the port.

Local> show port 2 status

Look for Current Service, Current Node and Current Port.

Instead of rebooting the DS90M you might try logging out the port.

Local> set priv
Password>
Local> log port 2

Hope this helps.
Kelly Cox
Frequent Advisor

Re: Telnet listener on Decserver

I agree with Walter Miller.
Just logout the port in question.

I have this happen at least once weekly at client sites where I have no control over the terminal servers. I just logout the port and recreate the telnet session from the VMS side.

I would need to find some old notes from long ago, but a DEC support person told me it was related to terminal server port not dropping the session when it lost communication. I don't remember how to change a 90M, but I would compare port settings on the ones that work and the ones that don't.
Wim Van den Wyngaert
Honored Contributor

Re: Telnet listener on Decserver

Release notes 2.3A in 1998 (found on cd)

It is possible, in some circumstances, for the Telnet connection to the remote console to be broken, without disconnecting the remote console session itself. In this situation, the remote console will be continually "in use", and unavailable until the access server is rebooted.

But that doesn't explain why 1 has the problem and 1 isn't. There is also mentioned a bug when memory is nearly full.

Wim
Wim
labadie_1
Honored Contributor

Re: Telnet listener on Decserver

Local> sh port X
on both DS90M shows exactly the same characteristics, but
Local> sh port X status
shows one difference
the DS90M which reconnects smoothly has
input signals: RXD
while the "disturbing" DS90M has
input signals: DSR RXD

DSR means (I think) Data Set Ready, or something similar

thanks to all who replied, I am going to modify the setup (remove the DSR) and, will try to just logout (if this happens before :-)

Volker Halle
Honored Contributor

Re: Telnet listener on Decserver

Gerard,

DSR is an Input Signal - normally indicating that the pin in the RS232 cable has a signal applied by whatever is at the other end of the cable. Same with RXD, which is received data signal.

I don't think you can TURN OFF DSR from the DS90M side.

The fact that 'DSR' is set, may just indicate, that the TELNET connection had not been completely torn down, so a LOGOUT PORT may be needed and may turn off DSR.

Volker.
labadie_1
Honored Contributor

Re: Telnet listener on Decserver

Ok Volker

So this means that it is not this difference that explains the different behavior :-(
labadie_1
Honored Contributor

Re: Telnet listener on Decserver

In order to have a procedure that connects to a decserver, set priv, log port 2, as my vms node has 6.2-1h3, what should I do ?

telnet client accepting non interactive commands needs Vms 7.1
http://h18000.www1.hp.com/support/asktima/appl_tools/009E60A3-96F8B0E0-1C0186.html

tsm ?

any other way ?

Thanks
Walter Miller_1
Valued Contributor

Re: Telnet listener on Decserver

One other place to look for differences.

Local> show port 2 telnet client

Check for input flow control and output flow control.
Volker Halle
Honored Contributor

Re: Telnet listener on Decserver

Gerard,

use TSM V6.1, it's on the Freeware V6.0 CD.

Volker.
labadie_1
Honored Contributor

Re: Telnet listener on Decserver

Walter

sh port 2 telnet client gives exactly the same output :-(

Volker

I will install Tsm

thanks