Configuring Systems for Terminals, Printers, and Other Serial Devices (32022-90057)

RAFCP Theory of Operation
Appendix D
213
D RAFCP Theory of Operation
Routable AFCP is an encapsulation of AFCP packets under UDP/IP to provide the
support of Terminals and Printers with the DTC and HP e3000 series 900 over a routed
IP network. The encapsulation is done in the DTC. A remote dtc (RDTC) encapsulates
the AFCP packets under UDP/IP and sends these packets to the front-end dtc (FEDTC).
The FEDTC deencapsulates these packets and sends AFCP packets transparently to the
HP e3000. For data sent in the opposite direction, the HP e3000 sends AFCP packets to
the FEDTC. The FEDTC encapsulates these packets under UDP/IP and sends them to
the RDTC. The RDTC deencapsulates them and forwards them to the addressed DTC
port.
RAFCP allows terminals and printers to be used within routed networks. With the
exception of the DTC 16RX, the DTCs can not be managed over a routable network.
Remote Local Switch (RLS) on OpenView DTC Manager allows the central management
of remote OpenView DTC Managers over IP networks.
Routable AFCP is supported on the following hardware and with the listed limitations:
• Remote DTCs can be DTC 72MX, DTC 16MX, DTC 16RX, DTC 16 and DTC48 with
memory extensions. The DTC 16iX, 16TN and DTC48 w/o memory extension do not
support Routable AFCP.
• Front End DTCs can be DTC 72MX, DTC 16MX, DTC 16RX and Telnet Express Box.
These DTCs do not need to be dedicated to Routable AFCP. They can be used as
regular DTCs at the same time.
• Each FEDTC and RDTC are managed by it’s own DTC Management platforms. The
Management platform can be the DTC 16RX Manager (DTC 16RX only), the
Windows 95 Openview DTC Manager or by the HP e3000 using Host-Based
Management.
• RAFCP requires MPE 5.0 Push release and OpenView DTC Manager 14.2 or DTC
16RX Manager 14.2 or newer.
• When the DTC is managed by the HP e3000 you must have the MPE/iX release 7.0
or 7.5 and must have installed the same patch set as described in Table B.1 or Table
B.2 in Appendix B “Migrating from a Previous Release” to enable the FEDTC to
allow RAFCP. See the section “Migrating your Configuration to Host-Based
Management” in Appendix B.
• The FEDTC function has no table which limits the max number of connections it can
handle. The level of traffic is limited by the DTC’s processing power (e.g. by the
number of packets it can transfer and by the other traffic it may be handling (local
terminals, HP e3000 Telnet Access, or X.25)). More than 300 active connections have
been opened through a FEDTC.