HP3000-L Archives

December 1995, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Steve Dirickson b894 WestWin <[log in to unmask]>
Reply To:
Steve Dirickson b894 WestWin <[log in to unmask]>
Date:
Thu, 21 Dec 1995 19:16:00 P
Content-Type:
text/plain
Parts/Attachments:
text/plain (25 lines)
<<This is the point I most wanted to respond to.  If you have the luxury
of subnets, you should keep the DTCs/DTSLINK LANIC card(s) on a separate
subnet (or on a port of an Ethernet switch).  This isolates your DTC to
host traffic from the primary LAN, and vice versa.  Since a router or
switch won't transfer low-level DTC traffic, no bandwidth concerns.>>
 
Although the "isolation" is somewhat limited; since the TAC works by
accepting TCP/IP packets from the "outside world" and re-packaging them
as AFCP packets for the host (and vice versa for the outbound traffic:
1)  The "outside world" has to have access to the TAC; this is routable.
2)  The DTCManager machine has to have access to the TAC; this is not
routable.
3)  The TAC has to have access to the host; this is also not routable.
 
So you end up with all your inbound TCP/IP traffic showing up on the same
wire as the AFCP traffic between the host, DTC, and DTCManager PC.
 
This raises a configuration issue: can a DTC with a TAC be the "far" end
of a routable-AFCP link? My understanding is that RMP is not routable,
which would suggest that the answer is "no", but my understand may be out
of phase with reality.
 
Steve Dirickson         WestWin Consulting
(360) 598-6111  [log in to unmask]

ATOM RSS1 RSS2