Because this is running over a serial cable, how do you have the serial handshaking setup? It may be expecting a hard drop on DTR (boy, this is going back in time). Try setting it to software handshaking. Maybe try playing with the [telnet] section in protocols.cfg. At worst, you could write an expect script to do the test - at least then you get to see what the terminal server responds to.
HTHs, Phil
From: Xymon <xymon-bounces at xymon.com> on behalf of KING, KEVIN <KK1051 at att.com> Sent: Tuesday, 29 November 2016 3:30 AM To: Root, Paul T; xymon at xymon.com Subject: Re: [Xymon] telnet test leaving port hung.,
Paul, thanks for responding. No it is not a script, it is the internal telnet test in Xymon. I do not use the telnet test much as not many thing use that now. But I only see this hang issue going to the cisco. I have tried to catch it, I was thinking as you that telnet is not disconnecting nicely.
-Kevin
From: Root, Paul T [mailto:Paul.Root at CenturyLink.com] Sent: Monday, November 28, 2016 11:50 AM To: KING, KEVIN <KK1051 at att.com>; xymon at xymon.com Subject: RE: telnet test leaving port hung.
Sounds to me like the xymon server is disconnecting from the Cisco, and the Cisco is missing it.
Is this an expect script doing the test? Perhaps you aren't disconnecting gracefully?
From: Xymon [mailto:xymon-bounces at xymon.com] On Behalf Of KING, KEVIN Sent: Monday, November 28, 2016 10:26 AM To: xymon at xymon.com<mailto:xymon at xymon.com> Subject: [Xymon] telnet test leaving port hung.
Xymon folks,
I am running Xymon 4.3.10 and I am seeing an issue with the telnet test going to a Cisco term server (router with async cards to serial device). Randomly the term server will hang and show a refuse connection. We the term server is checked the hung session came from the Xymon server. When I check the Xymon server netstat I do not show a connection to the term server. I get the term server port cleared and we are ok again. Anyone see this behavior?
-Kevin
This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.