Collision detect check failure is a warning, not a send failure -- the message
is misleading There are several possible causes.
1. The transceiver predates SQE check, it doesn't implement the signal. If so,
turn off the message, you're fine.
2. The transceiver can do SQE but it's turned off. Turn it on.
3. The collision signal circuitry in the transceiver is broken. Or the
collision wires in the transceiver cable are. If so, on a half-duplex link
with several other stations on it all busy talking, you might see lost packets,
and the other stations would likely be reporting "late collision" errors. If
so, replace the cable or transceiver.
I'm not sure if a bad coax segment (not properly terminated or damaged cable)
can do this, or if it would only cause false collision signals which is a
different message.
BTW, in all these cases you're probably communicating just fine. For 1 and 2,
no one else would be reporting any errors. Also: if your collision counts are
non-zero it's not #3.
paul
> On Dec 19, 2024, at 9:41 AM, Peter Ekstrom via cctalk <cctalk@classiccmp.org>
> wrote:
>
> Hi all,
>
> This may be a dumb question but I am a bit stumped. I can't seem to find
> any helpful info in the manuals. I have a DEQNA installed in my 11/23+ and
> I have run a NETGEN using the QNA driver. When NETINS runs I start seeing
> messages like these on the console:
>
> Event type 5.14, Send failed
> Occurred 19-DEC-24 09:30:11 on node 10.1 (TYCHO)
> Line QNA-0
> Failure reason = Collision detect check failed
>
> So obviously the link isn't working, but I find nothing helpful about where
> to start looking regarding the failed collision detect check. The line is
> on:
>
> NCP>show line qna-0 status
>
> Line status as of 19-DEC-24 09:36:31
>
> Line State
>
> QNA-0 On
>
> I have an Ethernet transceiver (I have 2 and have tried both, they worked
> last time I used them) connected to the DEQNA harness, and a cable
> connecting it to an old 10Base-T hub. I know that hub works because I have
> a couple of other systems (OS/2 laptop and an AS/400) connected to it.
>
> So does anyone have any ideas of where I can start?
>
> Thanks in advance!
> Peter
