CSCsj26883 - CISCO Bug - Recommendation Required

Answered Question
May 5th, 2008
User Badges:
  • Gold, 750 points or more

Hello Experts,


Refer to CISCO Bug: CSCsj26883


/sh int/ on MLP Bundle interface shows 100% input errors


Symptom: on a multilink bundle interface, the output from "show interface" will show an input error count which includes essentially 100% of the traffic being received. Other drop counters, usually the "bad frame" counter, are also incremented to match.


For example:


# show interface Multilink1

Multilink1 is up, line protocol is up

Hardware is multilink group interface

Internet address is 10.20.0.1/30

MTU 1500 bytes, BW 3072 Kbit, DLY 100000 usec,

reliability 181/255, txload 1/255, rxload 1/255

Encapsulation PPP, LCP Open, multilink Open

...

5 minute input rate 0 bits/sec, 0 packets/sec

5 minute output rate 0 bits/sec, 0 packets/sec

6080 packets input, 1027997 bytes, 0 no buffer

Received 0 broadcasts, 0 runts, 0 giants, 0 throttles

6077 input errors, 0 CRC, 6077 frame, 0 overrun, 0 ignored, 0 abort

^^^^ ^^^^


Impact: Very Low. This is an accounting error; the counters are being accidentally incremented each time Multilink begins to receive a new datagram. This does not affect actual traffic flow or operation of the bundle, it is only the statistics that are in error.


Workaround: none.


My Router Reliability Status:

==============================

Router#sh int Mu 1 | in reliability

reliability 140/255, txload 23/255, rxload 86/255


My Question:

============

What is meant by an "accounting error" that has been described in the BUG details.


Can someone please provide some Recommendation on this BUG. What is the next course of Action should i take forward ?


show Log for your Reference:

============================

The Input Errors are continuously increasing but the CISCO Bug says it doesnot affect the actual traffic flow or operation of Bundle.


How do i get it confirmed that my actual traffic is not getting impacted ? Is there any possible way to verify the same.


Router#sh int Mu 1 | i input errors

350220064 input errors, 0 CRC, 350219309 frame, 0 overrun, 2 ignored, 0 abort

Router#sh int Mu 1 | i input errors

350220460 input errors, 0 CRC, 350219705 frame, 0 overrun, 2 ignored, 0 abort

Router#sh int Mu 1 | i input errors

350220783 input errors, 0 CRC, 350220028 frame, 0 overrun, 2 ignored, 0 abort

Router#sh int Mu 1 | i input errors

350221116 input errors, 0 CRC, 350220361 frame, 0 overrun, 2 ignored, 0 abort

Router#sh int Mu 1 | i input errors

350221292 input errors, 0 CRC, 350220537 frame, 0 overrun, 2 ignored, 0 abort



Thanks in Advance


Best Regards,


Guru Prasad R

Correct Answer by mounir.mohamed about 8 years 10 months ago

Hi Guru,


Since no packet loss you are saved, and this can be tested by any way, extended PING, FTP, TFTP ...etc


The BUG report that the counters increased without any effect on the actual traffic, so its negative or fake counters and should be ignored.


Please rate helpful posts.


Best Regards,

Mounir Mohamed

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4 (1 ratings)
Loading.
Correct Answer
mounir.mohamed Mon, 05/05/2008 - 06:43
User Badges:
  • Gold, 750 points or more

Hi Guru,


Since no packet loss you are saved, and this can be tested by any way, extended PING, FTP, TFTP ...etc


The BUG report that the counters increased without any effect on the actual traffic, so its negative or fake counters and should be ignored.


Please rate helpful posts.


Best Regards,

Mounir Mohamed

guruprasadr Tue, 05/06/2008 - 00:40
User Badges:
  • Gold, 750 points or more

HI Mounir,


Thanks for the POST and the added recommendtions.


Dear All,


Refer this BUG & act accordingly if you face any such Issue in your Network.


Best Regards,


Guru Prasad R

Actions

This Discussion