Options for Managing a DTC Remotely

connection. It was envisioned that this product would reside in the computer
room, next to the CPU with a simple 10 Mbit connection running between the
system and the DTC. A simple, lightweight, proprietary protocol was developed
that would enable the user to make networked connections between the DTC
and a serial device. These protocols, the Avesta Flow Control Protocol (AFCP)
and the Avesta Device Control Protocol (ADCP) had the advantage of being
designed for and with the DTC in mind, so they were highly efficient and
produced excellent throughput. However, these protocols were designed for
simple networking architectures and did not include any mechanism for routing.
The following diagram outlines a simple DTC network, as envisioned by
the original design team:
In this network diagram, the HP 3000 is attached to a network with 2 DTCs that is
connected with various serial devices, including terminal, printers and serial
modems. This is what was typically available after the 1.1 release of the MPE/iX
operating system. However, due to customer feedback and industry trends, it
became apparent that this functionality was not going to be sufficient and so
starting at MPE/iX release 2.0 and beyond, additional functionality was added,
including X.25 system-to-system and PAD support, Telnet Access Card support
and multi-system switching support. In order to accomplish this, the
OVDTCMGR management platform was developed. With this added
functionality support, the possible network diagram evolved into the following
example: