[comp.protocols.tcp-ip] Fibronics TCP/IP/Ethernet for IBM mainframe

haas%gr@CS.UTAH.EDU (Walt Haas) (12/22/87)

Forgive me if I'm asking in the wrong place, but has anybody out there
had any real-world experience with a series of products from Fibronics
designed to connect an IBM mainframe to an Ethernet?  A local sales rep
just sent me some advertisements for a K310x product line that hooks
a block multiplexer channel to an Ethernet and a software package called
KNET TCP/MVS that implements guess which protocol on guess which os.

Thanks in advance--Walt Haas  ARPA: haas@cs.utah.edu  uucp: ...utah-cs!haas

jch@DEVVAX.TN.CORNELL.EDU (Jeffrey C Honig) (12/22/87)

>Forgive me if I'm asking in the wrong place, but has anybody out there
>had any real-world experience with a series of products from Fibronics
>designed to connect an IBM mainframe to an Ethernet? 

Try knet-l@tamvm1.bitnet, it is primarily about the VM product but may
have useful information.  To subscribe send mail to
listserv@tamvm1.bitnet with a single line of data:

	subscribe knet-l

Jeff

louie@TRANTOR.UMD.EDU ("Louis A. Mamakos") (12/23/87)

I've used both a Fibronics K200 and a K320, but on a UNIVAC/Sperry/UniSys 1100
mainframe system.  We bought the K200, and have a K320 on loan in a beta test
mode.  Personally, I prefer the K200.  It seems to have good performence, and
costs less than the K320.   However, the K320 is "smart" and programmable.  By
default, the K320 emulates a K200, but in the future can/could be upgraded to
do processing and offload the host.  We don't need that capability.

We wrote our own TCP/IP implementation for the 1100 series;  I have no 
experience with the KNET package.

louie

LDW@MVSA.USC.EDU (Leonard D Woren) (12/23/87)

Anyone looking into TCP/IP for MVS should also look at the ACS 9310
and Acces/MVS, from Advanced Computer Communications.  We're
installing one now.


/Leonard