Cisco Cisco IOS Software Release 12.2(33)SRE Guia De Resolução De Problemas
show mem dead
Certain processes require more in−depth investigation, but they are not covered in this document.
Another potential cause of memory issues is encountered when you run out of memory due to the
processes and configuration on the device. One example of this is the Border Gateway Protocol
(BGP) router. In some instances, BGP holds a large amount of memory because of the number of
routes that it takes in. This is not caused by a Cisco IOS bug. This problem must be corrected by
altering the configuration in order to achieve optimal routing and reduce memory consumption.
processes and configuration on the device. One example of this is the Border Gateway Protocol
(BGP) router. In some instances, BGP holds a large amount of memory because of the number of
routes that it takes in. This is not caused by a Cisco IOS bug. This problem must be corrected by
altering the configuration in order to achieve optimal routing and reduce memory consumption.
If you are unsure, collect the outputs listed previously (exclude show mem dead totals and show mem
dead), and open a TAC case, because this problem will probably require further investigation.
dead), and open a TAC case, because this problem will probably require further investigation.
3.
I/O Pool
The I/O pool refers to the I/O buffers seen with the show buffers command. These buffers are used for
process−switched traffic, among other things, such as routing updates or broadcasts. I/O memory is broken
down into pools, which are shown in the show buffers command output. These pools are based on packet size,
which allows more efficient allocation of memory based on the needs.
process−switched traffic, among other things, such as routing updates or broadcasts. I/O memory is broken
down into pools, which are shown in the show buffers command output. These pools are based on packet size,
which allows more efficient allocation of memory based on the needs.
Causes and What to Collect
The first thing to check with I/O memory issues is a potential buffer leak caused by a Cisco IOS bug.
This often manifests itself as a particular pool that increases its amount of buffers without releasing
them back into the I/O pool once they are no longer needed. Here is an example of this:
This often manifests itself as a particular pool that increases its amount of buffers without releasing
them back into the I/O pool once they are no longer needed. Here is an example of this:
−−−−−−−−− show buffers −−−−−−−−
Buffer elements:
500 in free list (500 max allowed)
3220350364 hits, 0 misses, 0 created
Public buffer pools:
Small buffers, 104 bytes (total 6144, permanent 6144):
3867 in free list (2048 min, 8192 max allowed)
248913132 hits, 0 misses, 0 trims, 0 created
0 failures (0 no memory)
Medium buffers, 256 bytes (total 86401, permanent 3000, peak 86401 @ 05:18:11):
0 in free list (64 min, 3000 max allowed)
9697361 hits, 203293 misses, 2208 trims, 85609 created
167633 failures (651288 no memory)
Middle buffers, 600 bytes (total 512, permanent 512):
0 in free list (64 min, 1024 max allowed)
9284431 hits, 237750 misses, 0 trims, 0 created
224619 failures (680486 no memory)
Big buffers, 1536 bytes (total 1000, permanent 1000):
0 in free list (64 min, 1000 max allowed)
69471745 hits, 895218 misses, 0 trims, 0 created
842142 failures (1821074 no memory)
VeryBig buffers, 4520 bytes (total 10, permanent 10, peak 122 @ 1w3d):
0 in free list (0 min, 100 max allowed)
2120517 hits, 1632477 misses, 112 trims, 112 created
1632421 failures (3272987 no memory)
Large buffers, 9240 bytes (total 8, permanent 8, peak 18 @ 1w3d):
0 in free list (0 min, 10 max allowed)
9593 hits, 832217 misses, 44 trims, 44 created
832195 failures (1651309 no memory)
Huge buffers, 18024 bytes (total 2, permanent 2):
0 in free list (0 min, 4 max allowed)
1.