Path: utzoo!utgpu!watserv1!watmath!att!emory!swrinde!zaphod.mps.ohio-state.edu!uwm.edu!csd4.csd.uwm.edu!hardiman
From: hardiman@csd4.csd.uwm.edu (Paul V Hardiman)
Newsgroups: comp.protocols.ibm
Subject: IBM 3172
Message-ID: <8318@uwm.edu>
Date: 13 Dec 90 19:21:56 GMT
Sender: news@uwm.edu
Organization: University of Wisconsin - Milwaukee
Lines: 22
Originator: hardiman@csd4.csd.uwm.edu

The IBM 3172 comes in 2 models: the model 1 is based on a 386 processor
and supports token ring, Ethernet, token bus, and PC Network LAN connections,
in addition to up to 2 IBM block multiplexer channels; the model 2 is based
on a 486 processor and supports FDDI.

There is also a model 1 Remote CTC that supports up to 4 T1 links.

The basic function of the 3172 is to make the attached IBM CPU(s) function
as host nodes on the LAN(s) to which the 3172 is attached. IBM's TCP/IP
version 2 software, which runs on the attached CPU(s) provides a fairly
complete suite of TCP/IP functions (FTP, socket library, RIP, Domain Name
Service (requires DB2), SMTP, X Window interface, NFS, etc.).

Neither the 3172 nor IBM's mainframe software supports Lan Manager, Netbios,
IPX, or other protocols, although these protocols can operate over the LAN(s)
to which the 3172 is attached.

This is just an overview of the 3172, and doesn't begin to address the full
functionality of the product.

(Disclaimer: I don't work for IBM - I just happen to be doing some research
in this area.)