I'm baffled as to what the problem is. Likewise, we are seeing a large number
of framing errors on this one PM, though I don't know if it's the PM or line
quality. According to the CSU, the quality on the line is dubious at times,
but the hits don't coincide with the periods of the PM silence.
It has me baffled as well. It -seems- to be a software problem from the
ability to reset the port, though the framing error count bothers me. This is
ComOS 3.3.2 (no c2, but as I understand it, that's mainly ISDN fixes, and we're
not doing that at the moment).
In a sick way I am glad to see I'm not the only one with this problem.
> This looks like a telco problem but after replacement of the V.35 modem
> and putting it on different wires it still continued:
>
> Tried Comos 3.1.4 and 3.3.2c2, same results. W1 functions for about a day
> reading occasional frame and abort errors then all of a sudden it stays
> on ESTABLISHED, idle time remains 0, but not a single bit can go thru;
> the other side is a cisco saying "line protocol down". A reset W1 solves
> it each time. Needless to say this is most annoying :-(
>
> Previous experience with "stuck" lines always required a physical reset of
> the V.35 modem and where always a telco problem but since this one kicks
> back in after a "soft" reset ... Could this be a hardware problem with
> the W1 port ?
>
> --Steven.