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

Introduction

Typical Network Configurations

Chapter 1

Routable AFCP Connections

Routable AFCP is a method of encapsulating AFCP packets into a UDP/IP packet to

permit devices connected to a DTC to communicate to an HP e3000 computer across a

routed IP network. The encapsulation is done in the DTC. A remote dtc (RDTC)

encapsulates the AFCP packets into an UDP/IP packet and sends these packets to the

front-end dtc (FEDTC). The FEDTC deencapsulates these packets and sends AFCP

packets transparently to the HP e3000. In the opposite direction, the HP e3000 sends

AFCP packets to the FEDTC. The FEDTC encapsulates these packets into UDP/IP

packets and sends them to the RDTC. The RDTC deencapsulates them and forwards

them to the addressed DTC port.

Figure 1-6 shows the hardware and topology needed to implement a Routable AFCP

DTC configuration. Note that on each LAN segment where a DTC resides, there must be

a DTC management platform present to manage the DTC. The platform can be the

OpenView DTC Manager or the HP e3000 host that has the latest DTS versions

installed. Although terminal and printer connections become routable in this

enviornment, the DTC management protocols are not.

Figure 1-6 Routable AFCP Hardware Topology

Remote DTCs can be: DTC 72MX, 16MX, 16RX, 16, 48 with memory extensions. The

DTC 16iX, 16TN and 48 without memory extension do not support Routable AFCP. The

Front End DTC must be a DTC 72MX, DTC 16MX, DTC 16RX or Telnet Express Box.

The Remote or Front end DTCs do not need to be dedicated to Routable AFCP. They can

be used to establish other supported connections at the same time.

IP Network

DTC

Manager

Platform

HP e3000

Series 900

DTC

Manager

Platform

DNS Server

Router

RDTC

FEDTC