[c-nsp] ASR9000 Input MIB CRC

[Saku Ytti]

Hey Curtis,

> One of the Bundle members appears to be accruing active Input MIB CRC which
> then reflects on standard Input CRC errors.  These accruing errors do not
> seem to be service impacting as there is 500M-1G of traffic on the physical
>     Input error CRC             = 2635490
>     Input MIB CRC               = 2635490
> The Nexus 5k side just indicates accruing "Output Errors" under the
> interface with no further details.  The actual counter error output of the
> interface sees nothing.

Do the counts match? ASR9k CRC input and Nexus 5k output errors?

I believe 5596 supports cut-through switching so CRC is detected after
frame has been sent. So possibly:

A => 5596 => ASR9k

A>5596 transit is breaking your frames or broken memory in 5596 and
ASR9k is dropping them on ingress due to FCS/CRC check.

And I'd be surprised if it is not service affecting, what ever frames
those are, they are not delivered. Voice with modern codecs is very
insensitive to quality, tolerates massive packet losses and jitter.
Couple CRC errors here and there wouldn't matter at all.

-- 
  ++ytti