[Lvlug] Jabbers, Jabbers but where?
Thu, 6 Jun 2002 08:52:47 -0400 (EDT)
On Thu, 6 Jun 2002, dann wrote:
> Okay, I cannot get a solid answer on this problem.
> switch. I noted there were a number of FCS (Frame Check Sequence) errors
> statistics. The port connected to the catalyst reported CRC (Cycle
> Redundancy Check) errors and Jabbers.
> Over the past few weeks I have learned that these errors could be a result
> of faulty hardware or cables. I have replaced the cable and tried three
> different ports on the 3300 and 2 different ports on the catalyst.
> The other day I found another cisco diagnostic utility that indicated
> during these periods that the catalyst port was reporting jabbers also.
> My question has been this. Should I be looking to the 3300 or the
> Catalyst as the device jabbering? Or is it possible that there is a third
> device out there (either on our network or somewhere on the IU's) with a
> jabbering NIC. If there is a device with a jabbering NIC, should I not
> see this jabbering on the port the device is connected in to?
> Anyone with some advice?
OK, I have seen similar problems like this on my T1.. Are you running a T
or Frame? Either way, the problem probably is *not* your internal
network, although I bet you have a metric butt-load of unnecessary traffic
on there from running multiple protocalls like TCP/IP, IPX/SPX, Netbios,
etc, etc.. I would have your carrier run a diagnostic on your
landline.. I'd bet your getting ghosting from your lec or
substation. I'd bet that once a week here I have to call out carrier
(comcast) and have them fix our voice T's because of misc trunks in a
static "system busy" that doesn't release. I still can't get them to get
a grip on the data T problems (they are quite uncooperative).
I am just glad to be switching carriers soon..
In the Beginning there was nothing, which exploded - Yeah right...