12-30-2004 07:49 AM - edited 03-02-2019 08:50 PM
We have a branch location connecting to our corporate office through a leased T1 line. Their connection goes from their Foundry switch to a Cisco 2600 router, which then connects to a 2600 router at the corp office.
Last week the IT admin at this other location noticed a ton of input errors on his switch on the port connected to the router. We began to monitor the port and saw that the errors were increasing at a fairly quick rate. At this point there was an old Cisco 2500 that he had brought from his house in place of the current 2600 that the errors seemed to be coming from. I could also see errors on the itnerfaces of this router. I did some testing and the problem appeared to be coming from the router. I ordered a refurbished 2600 and installed it yesterday. Once it was installed we noticed that almost all of the errors disappeared, however there were now some FCS errors appearing on the switch's port to which the router was connected. At this point I have tried three different cables, three different ports on the switch, on two different blades, but the errors still continue. It is not a huge deal as they only seem to be increasing at a rate of about 2 per minute, but since it is the router that their entire connection to the internet is going over it still bugs me a little. Plus, I am worried that there could possibly be something wrong with this second router as well, and want to make sure that I have it replaced during its warranty period rather than finding out later.
Does anyone have any suggestions for me to try? thanks in advance.
12-30-2004 08:22 AM
Two a minute? Sounds as if the foundry switch could be interpreting our CDP as an error. Try disabling CDP on the router and see if that stops it.
12-30-2004 10:08 AM
That was it! Thank you so much.
12-30-2004 08:22 AM
Can you post the (sanitized) configs for the router and the switch?
Consistant FCS errors may indicate a blown VLAN config (I don't think the tag insertion will change the FCS / CRC since it should be removed before forwarding the frame to a non-tagged environment).
Are you running any other protocols besides IP? Every 30 seconds sounds like a protocol update is triggering the error.
Please post the configs.
Good Luck
Scott
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide