[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference csc32::consolemanager

Title:POLYCENTER Console Manager
Notice:Kits, Scans, Docs on CSC32:: as PCM$KITS:,PCM$DOCS:, PCM$SCANS:
Moderator:CSC32::BUTTERWORTH
Created:Thu Aug 06 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1541
Total number of notes:6564

668.0. "SYSTEM-F-CONNECFAIL message in the controller log from telnet" by CX3PST::ANASAZ::J_BECKER (There's no substitute for a good boot) Wed Apr 05 1995 02:06

Customer has telnet connections to a xyplex server.

The connections are made at startup but intermitantly fail
with 

read error on telnet console for system XXXXXX
read error on tcp socket port number XXXXX
SYSTEM-F-CONNECFAIL connect to  network object timeout or fail

Is this telnet, pcm, or both?

Any ideas?

john becker
T.RTitleUserPersonal
Name		DateLines
668.1OPG::PHILIPAnd through the square window...Wed Apr 05 1995 10:3212
John,

  What happens if you Telnet to the server and port manually ($ TELNET server port)?
  Do you get the same error?

  Strictly speaking, we dont officially support the xyplex, although we do
  know that it works, however, the ones we have used in the past dont support
  the GETSTATUS TELNET option so you wont get connection checks on a periodic
  basis.

Cheers,
Phil
668.2Dcl works, what will GETSTATUS do for usCX3PST::ANASAZ::J_BECKERThere's no substitute for a good bootWed Apr 05 1995 20:0125
>
>  What happens if you Telnet to the server and port manually ($ TELNET server 
>port)?
>  Do you get the same error?

The connection to the telnet port from dcl works.  As I stated in .0, this
problem is intermittant.  The connection seems to die every 2-20 minutes. The
Dcl connection never fails.

>
>  Strictly speaking, we dont officially support the xyplex, although we do
>  know that it works, however, the ones we have used in the past dont support
>  the GETSTATUS TELNET option so you wont get connection checks on a periodic
>  basis.
> 

I was aware of this and we approached XYPLEX about this.  They have updated the
servers to a firmware rev they say supports this.  I was wondering what 
symptoms are exhibited when the functino is missing.  Would we make a
connection and then lose it as we are seeing?  Is that what "wont get
connection checks on a periodic basis" means?

thanks for your help phil

john becker
668.3OPG::SIMONSimon Jackson @reo 830 X3879Thu Apr 06 1995 10:3534
John,

>I was aware of this and we approached XYPLEX about this.  They have updated the
>servers to a firmware rev they say supports this.  I was wondering what 
>symptoms are exhibited when the functino is missing.  Would we make a
>connection and then lose it as we are seeing?  Is that what "wont get
>connection checks on a periodic basis" means?

What should be seen on a server which does not support the GETSTATUS is:

On the attempt to open the line we do the Option negotiation for GETSTATUS.

If the other end i.e. the terminal server responds with NO we generate a PCM
event that the server does not support GETSTATUS. We then set a flag in the 
host streucture for the system so we do not then do the periodic line check
for that particular system.

The periodic line check means that we have a recurring timer which when it goes
off it looks to see if there are any open console lines which have had no
traffic since the last check. If so we look to see if the line id really OK or
whether it has broken. If broken we attempt to reopen it. On TELNET lines we
use the GETSTATUS option to "poll" the other end.

A good way to test is to set up a filter for ENS which detects the event for ALL
systems and see if it gets triggered. 

Cheers Simon....