Datakit Interface Through TCP/IP

[Joe Yung]

Previously, I posted the following questions:

>I have a SPARC station 2 and a Datakit with a bunch of TTY modules.
>I am trying to have the SPARC connected to the Datakit so I can use
>my SPARC to access various TTY line off the Datakit.
>Does anybody know how ?
>
>I heard that AT&T Datakit has a connection to TCP/IP directly.
>We have a bunch of SPARCs on the Ethernet.  It will be a
>a versatile way to open up the Datakit available to all the SPARCs.
>Does anybody know anything about this connectivity.

I have got many helps from the net.
The following is my conclusion.

There are two possible configurations.
The first configuration is the following:

   --------------   Fiber Link     ---------
   |Sparc server| -----------------|Datakit|-------async terminals
   --------------                  ---------

A CPM/HS module is required on the Datakit end and a fiber interface
plus some software (DKHOST ?) is requried on the Sparc server.
Based on my experience on the 3B2-to-Datakit fiber link,
I believe this configuration will allow me to use all the fiber link features
including the datakit library.

However this configuration does not apply to the Sparcstations
because the fiber interface requires VME bus architecture which is
on the Sparcserver only.
The Sparcstations use SBUS architecture !

Another configuration is the following:

  --------------
  |Sparcstation|
  --------------
         |
         |   TCP/IP                          TCP/IP
  ==========================            ================
                           |   |   |    |
                          ------------------------
                          |Datakit Interface(NIK)|
                          ------------------------
                                | Fiber
                                | Link
                    Async    ---------  Async
     Serial Printer----------|Datakit|--------async terminals
                             ---------

The Datakit Interface(NIK) is a "telnet" service box which convert the TCP/IP
to URP protocol.
The user login from the async terminals as shown has to select
the "telnet" service on the datakit destination prompt.
This will take the connection to the NIK.
>From there, a host address will be entered to connect to the sparcstation.
This configuration is only limited to telnet service.
>From the Sparcstation end, type in telnet and open the NIK host connection.
The NIK host can connect to the async lines via the fiber link.

I think the sparcstation is not awared of the NIK as a gateway to the Datakit. 
Here are some features provided by NIK(Thanks to Bill Hill):

*Local Routing on NIK 
*Routing between LAN and remote LAN through Datakit (DK)
*Up to 4 LANs/NIK
*NIK fiber connected to DK
*Local Mngt of NIK or through StarKeeper NMS
*Capability to act as Terminal Server; a terminal or host directly
connected to DK can log onto any Ethernet LAN host connected to DK
via NIK
*Reverse terminal service; PC on LAN to Access DK hosts or Terms



Joe Yung
 -----------------------------------------------------------------
Joe Yung
yjy at stlucia.bellcore.com
(908)699-5344