On the bright side, your reliability is still 255/255, which makes sense
since only 597 out of 530182 frames have an input error. The ratio of bad
frames to good frames is 0.001, which is OK.
The port has received 231,187,726 bytes or 1,849,501,808 bits. We have to
assume that each frame has just one bit error, which might not be true, but
there's no way to know otherwise. Making that assumption, and the
assumption that I can do arithmetic (which is a stretch), your error rate
is 597/1,849,501,808 which is about .0000003, or 3 out of 10^7.
According to "experts" fiber-optic cabling should have a bit error rate of
less than 1 in 10^11. Copper cabling should have a bit error rate of less
than 1 in 10^6. If you are using copper cabling, then you are within the
threshold.
Is it copper cabling? Could there be electrical noise causing the errors?
Is this server in a different location than the others? Did swapping the
NIC reduce the rate? Perhaps the NIC outputs bad frames every so often.
Please let us know what you find out. It will help us learn, though I think
the "bottom line" answer is that you shouldn't worry about this low level
of errors.
Thanks!
Priscilla
At 02:32 AM 5/16/01, Keith Woodworth wrote:
>On Wed, 16 May 2001, Circusnuts wrote:
>
>|+You say the ports are locked to 100/ Full on the 2924 ??? It sounds as if
>|+you have done the trouble shooting with the cables. Have you isolated
>which
>|+box this is coming from & then maybe moved to swap the NIC ??? How are
you
>|+reading the CRC errors ???
>
>Yup, pegged the ports manually to 100/full. I know which box this is
>coming from and as it came with dual nics I will be shutting down the one
>in use now and will bring up the other one and see if that helps.
>
>I do a sho int faste 0/22 and look at what comes up from there. This is
>a full sho int on that port:
>
>FastEthernet0/22 is up, line protocol is up
> Hardware is Fast Ethernet, address is 0004.27c2.2156 (bia
>0004.27c2.2156)
> MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
> reliability 255/255, txload 1/255, rxload 1/255
> Encapsulation ARPA, loopback not set
> Keepalive not set
> Full-duplex, 100Mb/s, 100BaseTX/FX
> ARP type: ARPA, ARP Timeout 04:00:00
> Last input never, output 00:00:00, output hang never
> Last clearing of "show interface" counters 04:46:18
> Queueing strategy: fifo
> Output queue 0/40, 0 drops; input queue 0/75, 0 drops
> 5 minute input rate 91000 bits/sec, 27 packets/sec
> 5 minute output rate 41000 bits/sec, 24 packets/sec
> 530182 packets input, 231187726 bytes
> Received 2 broadcasts, 0 runts, 0 giants, 0 throttles
> 597 input errors, 290 CRC, 307 frame, 0 overrun, 0 ignored
> 0 watchdog, 0 multicast
> 0 input packets with dribble condition detected
> 416336 packets output, 170466717 bytes, 0 underruns
> 0 output errors, 0 collisions, 0 interface resets
> 0 babbles, 0 late collision, 0 deferred
> 0 lost carrier, 0 no carrier
> 0 output buffer failures, 0 output buffers swapped out
>
>This is the only port to show any errors of the 6 ports in use. Ive
>swapped ports, reset counters and still the CRC errors creep up.
>
>But next is the NIC on the box and see where that gets me.
>
>Thanks,
>Keith
>FAQ, list archives, and subscription info:
>http://www.groupstudy.com/list/cisco.html
>Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
________________________
Priscilla Oppenheimer
http://www.priscilla.com
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=4768&t=4646
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
