Big Buffer Failures and no increases to "created" counter
We are currently attempting to tune the buffers on aa 7200 series router. We have an extraordinary amount of Big Buffer failures (200,000 + per hour at times) yet the "created" field has remained at 43 since time immemorial.
I am reasonably certain of where the Big Buffers hits are coming from (Multicast replications on ATM links if that helps in any way). I'm wondering if the lack of "Created" buffers is indicating something? Perhaps the hits are spiking and not giving the router time to create them? Bad Memory? (There is 0 Failures from no Memory, FYI)
Here is a sample "show buffer" output:
Public buffer pools:
Small buffers, 104 bytes (total 148, permanent 148):
129 in free list (44 min, 211 max allowed)
63967265 hits, 1549 misses, 2167 trims, 2167 created
Re: Big Buffer Failures and no increases to "created" counter
I got the same pb as you except that the "created" number that is mocking me is ZERO as the failures keep increasing (and 0 no memory)
I found this in Cisco doc :
"How Buffers Are Handled by the Router
The number of buffers "in free list" is the number of available buffers. When a buffer request comes in, a buffer from the "in free list" is allocated.
If there are no buffers available and fast switching is enabled, there is a buffer failure and the packet is dropped. When the buffer pool manager process detects a buffer failure, it "creates" a new buffer to avoid future failures.
The router does not create a new buffer if the number "in free list" equals the "max allowed" value. If there is not enough memory in the router to create a new buffer, this is recorded as "no memory." If the number "in free list" is greater than the "permanent" number, the router "trims" some excess buffers.
The number of "failures" and "no memory" are the only areas you need to worry about. Failures may occur, but these should stabilize after a while. The router creates or trims buffers as necessary to stabilize the number of failures. If the number of failures continues to increase, then buffer tuning might be necessary.
If you do not have enough memory to create new buffers, look for a buffer leak or a more general memory problem. Buffers are not created in the fast−switching path, so if the router tries to fast−switch a packet and there is no buffer available, the packet is dropped and a failure is reported. The next time the buffer pool manager is run, a new buffer is created."
I am not English native speaker so the last paragraph is still puzzling me. Is a buffer created in fast-switching mode?
I hope it will help you anyway...
And if you have a magic command (except reload) to reset buffers counters, it will be welcome
[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...