[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

1270.0. "Telnet config help...thanks!" by OTOU01::TYPHAIR (Steve Typhair - dtn633-3761) Wed Apr 17 1996 23:22

    Hi
    
    I've set up the following environment using PCM under OSF1 and using
    Telnet versus LAT.  
    
    ds90tl---------AXP-2100 
      |                                    PCM Mgr
      |                                        |
    ======================================================
    

    My customer wants to avoid using LAT due to preference for Telnet. 
    I've configure DNAS for the 90tl and it loads fine.  I appear to have
    PCM configured okay, but I am not able to get through to my AXP-2100. 
    Basically when I try to connect to the console picture it puts up the
    decterm window and I get a few lines of information ie. use of Ctl E
    and Ctl G...  When I hit the return key I go to the command prompt and
    never get through or feedback from the TS and/or system.
    
    Question:
    For Telnet what should I have configured on the 90tl...the following
    lists what I have now or should say have ended up with.
    - Internet address and subnet mask are fine
    - can ping out and connect to other systems from a port into the
    network
    - Flow ctl=xon/xoff
    - parity=none
    - stop bits=dynamic
    - access=remote
    - break=disabled
    - def protocol=telnet
    - signal ctl=disabled
    Characteristics:
    - autobaud, inactivity timer logout, input flow ctl, output flow ctl,
    signal check
    Telnet Listener:
    - tcp-port=23
    - id=telnet console
    - ports(1 through 8)
    - connection=enabled
    
    What is a valid Telnet configuration setup on the 90tl to work with the
    PCM environment?
    
    I then set my system under PCM up to be telnet based with the server
    name and telnet number to be 23.  When I view the terminal server under
    options I see the server.
    
    When I did a MAKEDEV pty, I ended up with ptyn0... and ptyq0...
    devices, where do I map these or is it taken care of?  Also, I don't
    see where aI connect to port 8 on the 90tl, it appears to just connect
    to the server and 23...do I need to assign a tcp-port to each server
    port...I believe this is correct?
    
    Cabling, I'm using what the customer has right now and it may be
    causing additional grief.
    
    	- 90tl|
    	     _|rj45 adapter to mmj-------------------mmj to 9pin|2100-AXP
    
    The rj45 is an H8584-AC, the cable is the bc16e, the adapter is the
    H8571-J....
    
    I've also tried with a BN24H cable which has an rj45 on one end and an
    mmj on the other.
    
    Both of the above work from the terminal into the 90tl...
    
    
    What are the pin layouts supposed to be?
    
    My appologies for the above format, but I'm trying to work-out in short
    order.
    
    cheers
    steve
    Where do I map the ptyn0...
T.RTitleUserPersonal
Name
DateLines
1270.1CSC32::BUTTERWORTHGun Control is a steady hand.Thu Apr 18 1996 20:3741
>    Question:
>    For Telnet what should I have configured on the 90tl...the following
>    lists what I have now or should say have ended up with.
>    - Internet address and subnet mask are fine
>    - can ping out and connect to other systems from a port into the
>    network
>    - Flow ctl=xon/xoff
>    - parity=none
>    - stop bits=dynamic
>    - access=remote
>    - break=disabled
>    - def protocol=telnet
>    - signal ctl=disabled
>    Characteristics:
>    - autobaud, inactivity timer logout, input flow ctl, output flow ctl,
>    signal check
    
    get rid of autobaud, signal check and inactivity logout.
    
>    Telnet Listener:
>    - tcp-port=23
>    - id=telnet console
>    - ports(1 through 8)
>    - connection=enabled
    
    Don't use port 23 as thats the server console port number. What I do is 
    take each port and assign it a unique listener number. The numbers
    start at 2001 so the logical thing to do is assign listener 2001 to
    server port 1, 2002 to server port 2 etc.
        
    >    to the server and 23...do I need to assign a tcp-port to each server
    >port...I believe this is correct?
    
    answered in the above. Once you've assigned each port it's listener
    number modify the database record for the managed system to use the
    correct listener number and server name  for the server port it's
    console is physically connected to.
    
    Regs,
      Dan
    
1270.2Second connection won't happen?OTOU01::TYPHAIRSteve Typhair - dtn633-3761Tue May 07 1996 00:3715
    Thanks for the input, 23 I use for the console port and I have been
    using 2001...up for the other connections I need using telnet listener. 
    For some reason when I move to a second connection off of say port 7, 
    and have added it to PCM accordingly.  I then try to connect to it and
    I only have one active console device to connect to out of the two I
    have now added.  I've tried several combinations with the customer and
    the same results...ie. switched cables between systems etc.
    
    Any suggestions?
    
    Also, its key I have the 'telnet reset' function, I haven't seen it
    documented for the 90tl...does it support this feautre?
    
    Cheers
    Steve
1270.3CSC32::BUTTERWORTHGun Control is a steady hand.Wed May 08 1996 14:4114
    >    Thanks for the input, 23 I use for the console port and I have been
    >    using 2001...up for the other connections I need using telnet
    >listener. For some reason when I move to a second connection off of say 
    >port7, and have added it to PCM accordingly.  I then try to connect to it
    >and I only have one active console device to connect to out of the two
    >I have now added.  I've tried several combinations with the customer
    >and the same results...ie. switched cables between systems etc.
    
    >    Any suggestions?
    
    This sounds like a classic case of insufficient license units.
    
    Regs,
      Dan
1270.4Might be...will know todayNETRIX::"[email protected]"Thu May 09 1996 10:558
Hi Dan

After spending some time on the phone with the customer its my guess as well. 
I get a chance to verify one way or another today.

Cheers and Thanks
Steve
[Posted by WWW Notes gateway]