Subject: | |
From: | |
Reply To: | J. Patrick Lindley |
Date: | Fri, 21 Jul 2000 14:10:55 -0600 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
This is a multi-part message in MIME format.
--------------E9C87302460C9F00FCB95CB5
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Other than the obvious construction differences, are there any
communications differences between these two types of DTCs? We are
using Cisco routers to bridge the HP3000 DTC traffic. We can get the
DTC48s to connect to the HP3000 and take a download over an ISDN backup
circuit connection, but can't seem to get the DTC72 to do the same over
a similarly configured ISDN backup circuit. Each of the DTCs are at
different physical locations in our network.
However, both of these DTCs work fine over our T1 main circuits to these
branch locations using the same routers that are being used to control
the ISDN backup circuits.
When the DTC72 is connected to the ISDN circuit through the Cisco
router, the router displays "badly formed Ethernet packet" (or similar
verbage). This message continuously scrolls through the logs until the
DTC72 is turned off or disconnected from the router.
I believe the protocol used by the DTCs is something called "AFCP"? Is
that right? Does it matter? Is there any information about Cisco
products vs. HP DTCs that I should be aware of? Is the DTC72 using a
routed protocol instead of brided protocol? What about the DTC48?
Help!
--------------E9C87302460C9F00FCB95CB5
Content-Type: text/x-vcard; charset=us-ascii;
name="patrick.lindley.vcf"
Content-Transfer-Encoding: 7bit
Content-Description: Card for J. Patrick Lindley
Content-Disposition: attachment;
filename="patrick.lindley.vcf"
begin:vcard
n:Lindley;J. Patrick
tel;pager:916-971-2252
tel;fax:916-339-2170
tel;work:916-971-2253
x-mozilla-html:TRUE
url:http://www.safecu.org
org:SAFE Credit Union;Information Technology
adr:;;3720 Madison Avenue;North Highlands;CA;95660;USA
version:2.1
email;internet:[log in to unmask]
title:Data Center Manager
fn:J. Patrick Lindley
end:vcard
--------------E9C87302460C9F00FCB95CB5--
|
|
|