I have several OC-3 PoS links out to my service provider. I see input errors incrementing on some of the interfaces, but not all of them. The errors fall into the ignored category, but do not appear to be related to any queueing or buffering.
The unusual part is that they increment about every 10 seconds at a rate of 11 packets each time. I have confirmed that the config is the same on both circuits for the ISP and we can not find any reason that this would happen. The routes are the same for both - static from the ISP for the same block to both and default routes to both from my router. Does anyone have any idea of what this could be?
Here are two interfaces on my router which connect to two interfaces on the ISP router, same card for both. Notice that the ignored errors are on one but not the other.
Ignores are caused by a MEMD buffer shortage , O high speed interfaces thaey are caused by the traffic that is received on a high speed interface that has to wait to be transmitters on a low speed interface , The interfaces buffer pool can be tied up waiting for the transmit ring to free up some buffers.
One solution to this is to configure the same MTU size on all your interfaces , When all the interfaces has the same MTU size all the interfaces can share the same pool .
Another thing to keep in mind is the amount of ignores you are having in rlation to the amount of input trafiic is very low ,
That does not seem to be the case. The OC-3 links that i showed above are on the same router to the same ISP. The traffic coming on those two was once all on one of the circuits, and had just recently been balanced across the two circuits. So currently, the traffic on both of these are going to the same outgoing interfaces of the router - some FastE and GigE interfaces. BTW, this is a 7609 router. One sees the ignores, but the other does not. Also, the fact that they are come 11 packets at a time at 10 second intervals leads me to believe tha they are something else. Are there any other causes that woudl increment the ignores.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...