we have our system running through a cisco router gateway. in the past we had a broken switch in the system causing a lot of CRC errors and collisions. Those errors are all logged in the router. i’m wondering if anyone can help me out with some cisco advice on how i could reset the logs for each of the interfaces in the gateway router so they can be set back to zero after we’ve fixed the equipment issues.
thanks, any help would be appreciated.
inverted wrote: we have our system running through a cisco router gateway. in the past we had a broken switch in the system causing a lot of CRC errors and collisions. Those errors are all logged in the router. i'm wondering if anyone can help me out with some cisco advice on how i could reset the logs for each of the interfaces in the gateway router so they can be set back to zero after we've fixed the equipment issues.
thanks, any help would be appreciated.
"clear counters" will flush all counters in the router. Or, if you only want to apply it to an individual interface, "clear counters interface fa0/0" or whatever is actually appropriate.
I would observe that in most all cases where I see CRCs, framing errors, collisions, etc., it's mostly caused by the ethernet cable(s) themselves, not necessarily the equipment. Food for thought.
I would observe that in most all cases where I see CRCs, framing errors, collisions, etc., it's mostly caused by the ethernet cable(s) themselves, not necessarily the equipment. Food for thought.
I would agree that this is usually the cause, however I experienced something like this not too long ago that actually ended up being configuration errors.
A T1 line connected to an integrated CSU/DSU in a Cisco 3662 was taking a small number of incrementing CRC, Framing, etc. errors. The errors did not cause a noticable problem. Looking into the configuration, the service-module configurations were not set properly, and some of the required configs for the module were not set at all.
For this particular line, encapsulation is PPP. Timing is achieved from the network (or "line: in Cisco language), framing was ESF, line coding was B8ZS, and being a full T1 it used all 24 channels at 64k each.
Now, this is how the module was supposed to be configured. When I looked at it, it had the encapsulation set properly, and it had the timing being done/generated internally. No other settings that I mentioned above had been configured. Once I made these changes, and flushed the interface counters, the errors on the Serial interface went away.