I had something like this happen once on a fiber circuit where one patch cord in the path was multi mode when it should have been single mode.
On Thu, Nov 3, 2011 at 8:36 AM, Jared Valentine <[email protected]> wrote: > If the optic doesn't work, then clean the patch cable, then try swapping for > a new patch cable, then try a different port on the TI24X. > > Jared Valentine > [email protected] > > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Matt Kassawara > Sent: Thursday, November 03, 2011 7:28 AM > To: Drew Weaver > Cc: [email protected] > Subject: Re: [f-nsp] TurboIron CRC/Input errors > > I'd try swapping the optic. > > On Tue, Nov 1, 2011 at 3:11 PM, Drew Weaver <[email protected]> wrote: >> Howdy, >> >> >> >> While troubleshooting another problem I noticed that the crc/input error >> counter on one of our Turboiron 24s increments a few every couple of >> seconds: >> >> >> >> The amount of crc/input errors doesn't seem to scale up with the amount of >> traffic on the interface and the total number if tiny compared to the > number >> of packets: >> >> >> >> Received 156698568 broadcasts, 108451187 multicasts, 3166991325637 > unicasts >> >> 131804 input errors, 131801 CRC, 0 frame, 0 ignored >> >> 0 runts, 3 giants >> >> >> >> Does anyone know if there is any definitive way of knowing what is causing >> this? >> >> thanks, >> >> Drew >> >> >> >> _______________________________________________ >> foundry-nsp mailing list >> [email protected] >> http://puck.nether.net/mailman/listinfo/foundry-nsp >> > _______________________________________________ > foundry-nsp mailing list > [email protected] > http://puck.nether.net/mailman/listinfo/foundry-nsp > > _______________________________________________ > foundry-nsp mailing list > [email protected] > http://puck.nether.net/mailman/listinfo/foundry-nsp > _______________________________________________ foundry-nsp mailing list [email protected] http://puck.nether.net/mailman/listinfo/foundry-nsp
