Hi!
 
  I'm posting this on behalf of CSY marketing... here we go:
 
 
 
There has recently been discussion re: HP DTCs functionality in routed
networks.
 
Here is an overview of both routable management and routable datapaths using
DTCs, as well as a list of some of the materials available for further
reference
 
For further information, you can contact me instead of Eero Laurila.
Eero is taking on new responsibilities within HP but was kind enough to post
this information.  I am currently the product manager and can be reached
at the following address:
 
[log in to unmask]
 
 
Routable datapath to HP3000: Routable AFCP
------------------------------------------
 
The protocol used for communication between HP 3000 systems and DTCs is called
AFCP (Avesta Flow Control Protocol).  This is HP proprietary protocol, and was
not able to be passed on by routers.
 
Enhancements to both the DTC code and the MPE code allow routable AFCP
datapath.
This allows a terminal user connected to a DTC on one LAN to talk to an HP 3000
located on a remote LAN across a routed network.
 
The way it works is that AFCP packets are encapsulated in UDP/IP (User
Datagram/
Internet Protocol) packets that the router can pass through the network using
a DNS server to map the addresses.  The packets are then deencapsulated for the
local user or local HP 3000 server.
 
The configuration must include a DTC on the local LAN with the user desktop
devices, as well as a DTC on the local LAN with the HP 3000 server.  The
DTC on the HP 3000 LAN is called a "front-end" DTC, because it offloads
some of the encapsulation/deencapsulation and address searching from the
HP 3000.  The HP 3000 MPE code does some of the remaining work so you
need the right version of MPE/iX code.
 
A DNS (domain name server) must reside somewhere on the routed network.
HP supports DNS on the HP 9000 HP-UX systems.  Note that a Telnet Access
card (TAC) is NOT required.
 
DTCs that can be used on the LAN with desktop devices include DTC16MX, DTC16RX,
DTC 72MX, DTC16 and DTC48 (with memory extension date code > 3110).  DTCs that
can be used as front-ends, on the same LAN as the HP 3000, include DTC 16MX,
DTC 16RX and DTC 72MX.  The front-end DTC does NOT need to be dedicated; that
is
it can be used for local traffic as well as encapsulation/deencapsulation of
the IP packets.  The only constraint is performance and throughput of the DTC
itself.
 
Part numbers of currently orderable products:
 
              DTC 16MX     J2063A     PC/OpenView based management
              DTC 72MX     J2072A      "           "
              DTC 16RX     J2064A     HP 9000 S/700/800 based management
 
 
For software, the DTC code must be 14.2 or later.  The MPE/iX code
must be version 5.0, C.50.00 or later.
 
Routable DTC Management
------------------------
 
The DTC 16RX supports the HP 3000 and HP 9000 systems and can be MANAGED
remotely over a routed network.  Note that some other DTCs can be managed
remotely using 2 PCs, one on each LAN, but this requires 2 PCs as well as
greater LAN traffic.
 
The DTC 16RX is managed by software called DTC 16RX Manager (P/N J2496A).
This software runs on HP-UX systems, including HP 9000 series 700 or 800
systems with HP-UX version 9.X or 10.X.
 
Reference Sources
-----------------
 
Technical Documentation:
 
Technical Datasheet on DTC 16RX and DTC 16RX Manager
Customer Support News (11/95 and 4/96)
MPE/iX 5.0 documentation
 
 
General Product Documentation:
 
HP Advisor article (2/95)
HP 3000 900 Series Computer Systems Ordering Guide
HP 3000 900 Series Computer Systems Configuration Guide
 
------------------- Posted by Eero Laurila for Dianne DISABATINO.