Dennis hopes:
> I am looking for sites that have successfully implemented HP's solution
> for routing AFCP packets across WAN's using DTCs at both ends configured
> to encapsulate and redirect the packets across the WAN.

> Hopefully somebody will have implemented this years ago and be able to
> provide some long term history/problems that we can learn from and
> avoid.

Since I believe it requires an OpenView DTC Manager workstation on *each*
end of the connection (which always has to be up in case the DTC power
fails, is difficult or impossible to order the software for, and officially
required a very specific (obsolete and unobtainable) hardware config the
last time I checked), plus an extra DTC on the 3000 side to act as a
protocol converter (so that the 3000 itself doesn't have to know what's
going on) and only supports a limited set of DTC devices as the protocol
converter, and only supports a limited set of DTCs at the remote end, I
think the answer is that (almost) nobody has implemented this :-)

> Configuring/changing CISCO router settings is not an option in this
> case.

You're positive about this? :-)

For terminals you really ought to use PC's with telnet or VT, and for
printers you should be able to use network printing, so my recommendation
would be to avoid RAFCP (and live longer).

If you absolutely had to have serial devices out there, I'd look at one of
the various generic "telnet server" or "terminal server" boxes that exist
and talk RS-xxx serial on one side and telnet on the other.  If you
absolutely have to be able to open a serial port on the 3000 and get to a
serial device at the remote location, I'd look at using back-to-back
"terminal server" boxes before heading down the RAFCP route.

I'd think Telamon would be good people to ask about this stuff.

G.