Re: [c-nsp] ASR9000 Input MIB CRC

2019-03-23 Thread Saku Ytti
You may be able to capture the broken frames on the ASR9k, which should help you narrow down where the problem happens. https://gist.github.com/ytti/436fe3b602a963acf21e On Sat, 23 Mar 2019 at 20:26, Curtis Piehler wrote: > > The rate at which these CRCs come in so quick that it is difficult to

Re: [c-nsp] ASR9000 Input MIB CRC

2019-03-23 Thread Curtis Piehler
The rate at which these CRCs come in so quick that it is difficult to clear both the router and switch counters at the same time to get an exact match. However, bear in mind the human delay is 1-2 seconds between hitting "enter" to clear the counters on the devices, yes they do appear to match on

Re: [c-nsp] ASR9000 Input MIB CRC

2019-03-23 Thread 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 >

[c-nsp] ASR9000 Input MIB CRC

2019-03-23 Thread Curtis Piehler
I have tried researching this but have not found any substance on this type of error. I have an ASR9000 with a Layer3 Bundle-Eth connected to a VPC Nexus5596. Both sides run LACP active/active. The ports are connected via 10G XFP 10G-SR and 10G SFP+ 10G-SR (OM3 Fiber) One of the Bundle members

Re: [c-nsp] 9396 SNMP

2019-03-23 Thread Mike Hammett
I'm guessing not? Am I barking up the right tree regarding the source of my issues? - Mike Hammett Intelligent Computing Solutions Midwest Internet Exchange The Brothers WISP - Original Message - From: "Mike Hammett" To: cisco-nsp@puck.nether.net Sent: Sunday, March