This is basicly a point to point. The other end is a Verizon 100 meg ethenet connection to the Internet. They have it shaped to burst only to 50 meg. The 5 minute input average on the interface is no more than 10 meg. They do have a transciever inline taking the ethernet for fiber to copper.

I would verify with verizon on how the tranciever is setup whether it is set as auto or is it hardcode to 100/full , you may have a speed/duplex mismatch if traffic is that low . Must match on both sides .

There was a mismatch when they first installed the unit. I was getting tons of CRC errors until I changed the setting from Auto Negotiate to 100 full on the unit. I thought I had the problem fixed but then I started getting just the ignored and overrun errors. Both sides are set static to 100/full

Sounds like the router and/or port is just too busy to handle the traffic. With a 50M burst then probably not the raw load if this is the only busy port in the router. What router mode, what else is it doing? Are you running CEF? What is the CPU load on the router? Even an older 2621 can handle simple L3 forwarding at 50Mbps if the packets are not all 64 and the routes/route cache are not getting flushed all the time. Really need more info here I would think. Where is the traffic going? Are the output destinations allowing this traffic the exit quickly?

Oops I meant what router model. What line cards, etc...

The router is a 7204 / NPE400 ....CPU runs at about 8-10%. CEF and Fast switching is turned on. The outputs are 2 100 meg ethernets that are load balacing the traffic into a 3750 L3 switch that sits behind the router. So basicly traffic comes in from the internet on the 50 meg ethernet and traffic is then routed on to the two 100 meg ethernets that go to my network. The two output ethernets are running clean with no errors.