[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

1336.0. "RS/6000 console to DECserver 90M setup problem" by KETJE::63767::HERTA (For something fulfilled this hour, loved, or endured) Mon Jul 08 1996 05:10

I've connected the serial port 1 (console port) of an RS/6000 to a DECserver 90M
to set it up for remote management via POLYCENTER Console Manager.  

When I telnet to the telnet listener port it shows:

    # telnet qit974 2001
    Trying 205.248.24.2...
    Connected to qit974.
    Escape character is '^]'.

then waits indefinitely.

When I look at the terminal server port counters, "output characters" increase 
whenever I type a character, but "input characters" remains at 0.

I don't have any documentation on the RS/6000, so help is greatly appreciated.

Herta


==== terminal server configuration (SW)
Local> sho port 1

Port  1:                               Server: QIT974

Character Size:            8           Input Speed:               9600
Flow Control:            XON           Output Speed:              9600
Parity:                 None           Signal Control:        Disabled
Stop Bits:           Dynamic

Access:               Remote           Local Switch:              None
Backwards Switch:       None           Name:                    TSTSYS
Break:              Disabled           Session Limit:                4
Forwards Switch:        None           Type:                      Ansi
Default Protocol:     Telnet           Default Menu:              None

Preferred Service: None

Authorized Groups:   0
(Current)  Groups:   0

Enabled Characteristics:
Input Flow Control,  Lock,  Loss Notification,  Message Codes,
Output Flow Control,  Verification

Local> sh telnet list 2001

Listener TCP-port:  2001
Identification:     tstsys console
Ports:              1
Connections:        Enabled

Local> sh port 1 co

Port  1: (Remote)                      Server: QIT974

Seconds Since Zeroed:     515472       Local Accesses:              0
Framing Errors:                0       Remote Accesses:             8
Parity Errors:                 0       Input Characters:            0
Overrun Errors:                0       Output Characters:         158


Local> sh port 1 sta

Port  1: (Remote)                      Server: QIT974

Access:        Remote                  Current Service:       160.1.180.21
Status:     Connected                  Current Node:          160.1.180.21
Sessions:           1                  Current Port:                  1347

Input XOFFed:      No                  Output Signals: DTR
Output XOFFed:     No                  Input Signals:  RXD

==== HW configuration
RS/6000 serial 1 - H8575A (straight through) - BN24H (crossed-over 6-way MMP to 8-way MP) - DECserver 90M
T.RTitleUserPersonal
Name
DateLines
1336.1CSC32::BUTTERWORTHGun Control is a steady hand.Tue Jul 09 1996 16:1911
>==== HW configuration
>RS/6000 serial 1 - H8575A (straight through) - BN24H (crossed-over 6-way MMP to 8-way MP) - DECserver 90M
    
    It could be a cabling problem. I would suggest that you test the whole
    cabling config by plugging the H8575A into a suitable terminal
    and then verify that what you type in the TELNET session appears 
    on the terminal and vice-versa.
    
    Regs,
       Dan
    
1336.2any practical experience anyoneKETJE::63767::HERTAFor something fulfilled this hour, loved, or enduredWed Jul 10 1996 06:066
    Well, as the RS/6000s are in Italy and I'm based in Belgium, I was
    hoping for a more convenient answer...
    
    
    Anyone have any practical experience?
    Herta
1336.3CSC32::BUTTERWORTHGun Control is a steady hand.Wed Jul 10 1996 13:3922
    Herta,
      
       I checked all of your part numbers with the DECConnect applications
    guide and it all looks good to me hence my answer. There is no magic
    here. This same problem could occur with any device. I have some other
    ideas but they are very obvious things to check. I did not mention them
    previously as I would hope these had been checked:
    
    1. The H8575-A. Is the console port in question really a 25 pin port
       or is it a 9-pin port? If it's a 9 pin port the customer may be
       using an H8575-B. If they are then the RS6000 is probably wired like
       a 9-pin PC port and the H8575-B is not. The customer would want to
       use an H8571-J instead.
    
       If the H8575-A is then I'm back to the original answer: we need to
    verify that the cabling config works. 
    
    2. Are we using the correct port?????!!
    
    
    Regards,
       Dan
1336.4one possible solutionKETJE::63767::HERTAFor something fulfilled this hour, loved, or enduredWed Jul 17 1996 05:4328
Based on information in the VAXcluster Console System conference (NOTED::VCS -
Tpoic 1662), we asked one of our telecom guys to construct a cable with
an RS-232-like 25-pin connector on one side and an RJ45 connector on the other.
The wiring is as follows:

    RJ45                   "RS-232"
    Signal     Pin         Pin Signal
    =================================
    DSR        8           20  DTR
    ---------------------------------
    DTR        7            8  DCD
                            6  DSR
                            5  CTS
                            4  RTS
    ---------------------------------
    Tx Data    6            3  Rx
    ---------------------------------
    Tx Ground  3            7  SG
    Rx Ground  1
    ---------------------------------
    Rx Data    2            2  Tx
    =================================

Works like a charm.

Thanks for your suggestions,

Herta