Conference csc32::consolemanager

Geert,

Interesting, We will need to investigate.

Cheers,
Phil

Geert,

  Can you disable the "Inactivity Logout" Characteristic on the port
  and let us know if that cures your problem.

Cheers,
Phil

    
    Hi,
    
    I tried, but it's the same problem.
    
    Rgds,
    
    Geert

    
    
    Any more ideas ?

    I just looked at my terminal server and I can see that the 'Inactivity
    Timer' is set to 30 and you have yours set at 1. You might try changing
    this.
    
    Dave

    
    Hi Dave,
    
    I have changed the 'Inactivity Timer' to 30, but I still can't connect.
    The connect window is created :
    	POLYCENTER Console Manager
   	Connect/Monitor Interface V1.1-000
    	Connected to remote console (TESTTCPIP)
    	Type CTRL/E to exit or CTRL/G to escape to monitor
    
    But when I type return nothing happens.
     
    In the Multi-Line Window I see :
    	User SYSTEM connected TESTTCPIP
    CTRL/E to exit works fine.
    I don't have the other messages(errors) anymore mentioned in 270.0 .
    
    TESTTCPIP is in fact a terminal connected to the DECserver.
    Can that be the reason. Although when I do 'telnet dss300 2006'
    (Console manager is shutdown first of course) I get :
    	$ telnet dss300 2006
    	Trying...16.201.0.51
    	Connected to DSS300.
    	Escape character is '^]'.
        I can type something ....
    
    Any more ideas.
    
    Rgds,
    
    Geert
    	
           

Geert,

when you did:


$ telnet dss300 2006
    	Trying...16.201.0.51
    	Connected to DSS300.
    	Escape character is '^]'.
        I can type something ....
    

       if you leave your seesion logged in for some timeWITHOUT typing anything
does it then disconnect??

It seems strange that Phil and I were able to reproduce your problem here and
fix it by removing the "Inactivity Logout" parameter from the port attributes.

Since that test I have not been able to reprodcue your problem again.

Please send your current setting for:

1) Port setup on Terminal server	Local> Show port x

2) Server Setup on Terminal server	Local> show server

And the system entry in your database.

If this still gives no joy can I get access to your system and terminal server
to get a closer look.

Cheers Simon...

P.S. If you prefer reply by mail to elbrig::sdj

    >I no longer get the error messages in 270.0
    
    Then that says you are getting the connection. To prove this you will
    need two sessions/decterms. From one session do the following:
    
    $ TELNET server-name   ! By default you will access the "console" of
                           ! the DECServer
    #                      ! type in the login password for the server
    Local> SET PRIV
    Password:              !type in the servers priviledged password
    
    Local> SHOW PORT ALL
    
    You will get a brief listing of each port and it's conect status. At
    this time we have not attempted a telnet to the other port so we
    shouldn't have a connection.
    
    Now, go over to the other session and do
    
    TELNET server-name listener-number
    
    Now go back over to the other session where we have connected to the
    server console and repeat the SHOW PORT ALL command and see if the
    connect status has changed to connected. Do it a few times to make sure
    that the connection doesn't drop.
    
    >    TESTTCPIP is in fact a terminal connected to the DECserver.
    >    Can that be the reason. Although when I do 'telnet dss300 2006'
    
    
    Are you saying that you have a dumb terminal connected to server port
    and that is functioning as the service node? If so then theres no
    wonder that you aren't getting an echo back from your CONNECT sessions.
    Dumb terminals do not echo characters back to the source they were
    sent from. What you would have to do is walk over to the terminal and
    type something to see if it shows up in your CONNECT session.
    
    Regards,
       Dan 
        (Console manager is shutdown first of course) I get :
            $ telnet dss300 2006
            Trying...16.201.0.51
            Connected to DSS300.
            Escape character is '^]'.
            I can type something ....
    

    
    Hi Dan,
    
    Yes, it's a dumb terminal. I wanted to test the tcpip/telnet part of
    PCM.
    I will test what you proposed in two weeks. I'm this week and next week
    not in the office.
    
    Thanks & rgds,
    
    Geert

OSF 2.0

I am trying to help a customer connect to a port on a 3com terminal
server, and do not know what the proper setup on the "port" should be.

The consoled is not starting on the host.
............The consoled log file contains:


Unable to connect to event port
Failed to connect to Local listener /var/opt/console/tmp/CONSOLE_EVT_ENS on node

No such file or directory
Console Manager shutting down at user request
Write error on Local socket /var/opt/console/tmp/CONSOLE_CTRL
Broken pipe

...........And the port shows the following:


[2]B4iplatC# sh !0 dp
---------------------------Port Dependent Parameters---------------------------
AUToDisconnect = Disabled BAud = 9600               BSPad = None
BUffersize = 512          CRPad = None              DataBits = 8
DeVice = (Host,Glass,DeFault)                       DUplex = Full
FFPad = None              LFPad = None              LinePRotocol = ASynchronous
PARIty = None             PermanentVC = ""          PvcProtocol = ANY
StopBits = 1              TabPad = None
UseDCDout = (AlwaysAssert,NoToggle)                 UseDTRin = Ignore
----------------------Session and VT Dependent Parameters----------------------
BReakAction = IGnore      DataForward = None        DIsconnAction = None
ECHOData = OFF            FlowCtrlFrom = Xon_Xoff   FlowCtrlTo = Xon_Xoff
FlushVC = OFF             HostEchoData = ON         IdleTimer = 1
LFInsertion = None        LongBReakAction = IGnore  MOde = Transparent
XOFF = ^S                 XON = ^Q
[3]B4iplatC#

.......................................................

????????????????????????????

    
    I can't give any 3com specific commands to you but
    here is basic things ypu have to do.
    
    You have to map telnet listener number to the terminal server
    port where system is connected.
    	
    Before you start PCM make sure you can connect with command
    
    # telnet server_name listernumber
    
    for example
    
    # telnet 3comsrevr 3016
    
    -Olli