🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.dcom.sys.cisco
Article #447

Could it be a cisco problem?

#447
From: Curt Mosso (CGM) (805)961-4044
Date: Tue, 03 Jul 1990 22:11
27 lines
1762 bytes
We have a serial connection which looks like:
 
      cisco       local              remote
    AGS with     DATATEL            DATATEL
       V.35 ----- V.35 ------56k---- V.35 ----- SUN
    interface    CSU/DSU            CSU/DSU
 
Briefly, the remote CSU/DSU will drop CTS although the CSU/DSU is switch set
to leave CTS always on. We have BERT tested the line, swapped CSU/DSU's, and
pretty much done all the testing you would expect. What we can't swap is the
cisco box. Has anyone seen an occurrence where a cisco gateway would cause a
CSU/DSU to drop CTS and leave it that way until the CSU/DSU has been reset?
 
You might ask why am I questioning the cisco gateway? We have seen the same
symptom once before. We have a two hop circuit. The first hop is on rf modems
on campus the second hop is on DATATEL CSU/DSU's off campus. We got a problem
report that a the remote CSU/DSU was dropping CTS. We could find no problems
on the CSU/DSU line, but when we found and fixed a problem on the rf modem
line, the CSU/DSU ceased to drop CTS. (If you have some idea why fixing the rf
line fixed the CSU/DSU I'd like to hear it.)
 
The cisco ASG is running GS Software Version 8.0(9). Show controller MCI
yields: MCI 1, controller type 2.1 microcode version 1.0.
 
Please respond to me at: com1curt@ucsbvm.bitnet When, if, we get a solution
I'll respond to the mailing list. Thank you. Curt
 
Technical Details
Message-ID: <23074@boulder.Colorado.EDU>
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!stan!boulder!daemon

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!stan!boulder!daemon
From: COM1CURT@UCSBVM.BITNET (Curt Mosso (CGM) (805)961-4044)
Newsgroups: comp.dcom.sys.cisco
Subject: Could it be a cisco problem?
Message-ID: <23074@boulder.Colorado.EDU>
Date: 3 Jul 90 22:11:24 GMT
Sender: daemon@boulder.Colorado.EDU
Lines: 27