HP3000-L Archives

August 1998, Week 5

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Bill Bennett CSY <[log in to unmask]>
Reply To:
Bill Bennett CSY <[log in to unmask]>
Date:
Fri, 28 Aug 1998 22:12:15 GMT
Content-Type:
text/plain
Parts/Attachments:
text/plain (66 lines)
     During the MPE technical round table at HPWorld a question was asked
     regarding using a terminal server to access the remote consoles.  I
     volunteered to document such a configuration that is currently in use
     at the Cupertino Capacity Planning Center (CPC).

     First let's explain what a terminal server is.  It is a small
     specialized device that support RS232 and TCP/IP protocols.  It has a
     LAN connection and multiple RS232 (usually RJ45) connections.
     Depending on how the device is configured, RS232 devices (such as
     terminals and modems) can connect to the LAN.  Also from the LAN,
     RS232 devices can be accessed.

     The CPC uses a Chase Research (www.chaser.co.uk) IOLAN+ as their
     terminal server (other companies offer terminal servers but I have not
     seen them work).  This terminal server can be purchased with 4,8 or 16
     RS232 ports and is rack mountable.  The CPC uses the 16 port version.
     They configure 8 ports for computer console connections, 4 for
     terminal connections and 4 for modem connections.  With this
     configuration 8 different computer consoles can be accessed in any of
     3 different ways: 1) using telnet from a computer on the LAN to
     connect to the terminal server. 2) using the terminal (in essence this
     is like hardwired) 3) connecting from an external modem, this is
     similar to the terminal connection except the connection is through a
     modem.

     To connect using telnet the user enters the telnet command on his
     computer along with the name/IP address of the terminal server and
     some additional information identifying which port to connect to.  The
     user is now connected to the console of one of the computers serviced
     by that terminal server.  Control-A and Control-B both work and if the
     user is running from an HP type terminal (such as with Reflection) he
     can even run NMMGR.

     From the terminals the user gets the terminal server prompt and then
     enters the information to connect to a specific console.  There is
     also a mode that would allow the user to disconnect another user and
     then take over the console connection.

     The modem interface is the same as the terminal except the user must
     connect to the modem first.

     The terminal server supports security so any of the access types can
     be password protected.  The terminal and modem accessors can also be
     restricted to not allow access out through the LAN.

     At the CPC the main consoles are connected through the terminal
     servers.  Most monitoring of the consoles is done from multiple
     windows on a workstation.  The terminals are used in the computer room
     (usually by operations during hardware setup).  The Dial ups are used
     when accessing outside of the network.

     This setup should work fine for the remote consoles.  If you are
     running predictive support you should consult your response center
     engineer before setting up your remote consoles through a terminal
     server.


--
---------------------------------------------------------------------------
Bill Bennett                                            [log in to unmask]
Hewlett Packard Company
Commercial Systems Division                            phone (408) 447-7858
19447 Pruneridge Avenue, MS 47UA                       fax   (408) 447-4441
Cupertino, California 95014
---------------------------------------------------------------------------

ATOM RSS1 RSS2