09-25-2003 05:04 AM - edited 03-02-2019 10:35 AM
The logging contiaines the following message:
"-Traceback= 1AC9D8 1AE004 165784 1B9FE8 1BA230 1CD998
Sep 19 21:19:08 UTC: %SYS-2-MALLOCFAIL: Memory allocation of 1680 bytes failed f
rom 0x165780, alignment 0
Pool: I/O Free: 1976 Cause: Memory fragmentation
Alternate Pool: None Free: 0 Cause: No Alternate pool"
sh buffers:
Small buffers, 104 bytes (total 50, permanent 50):
50 in free list (20 min, 150 max allowed)
3114474 hits, 0 misses, 0 trims, 0 created
0 failures (0 no memory)
Middle buffers, 600 bytes (total 25, permanent 25, peak 40 @ 2w2d):
23 in free list (10 min, 150 max allowed)
236462 hits, 7 misses, 21 trims, 21 created
0 failures (0 no memory)
Big buffers, 1524 bytes (total 139, permanent 128, peak 4364 @ 1w4d):
132 in free list (128 min, 512 max allowed)
6585163 hits, 408417 misses, 293396 trims, 293407 created
2613 failures (158 no memory)
VeryBig buffers, 4520 bytes (total 0, permanent 0, peak 26 @ 3d02h):
0 in free list (0 min, 0 max allowed)
41772 hits, 47739 misses, 95476 trims, 95476 created
1 failures (2 no memory)
Large buffers, 5024 bytes (total 0, permanent 0):
0 in free list (0 min, 0 max allowed)
0 hits, 1 misses, 0 trims, 0 created
1 failures (2 no memory)
Huge buffers, 18024 bytes (total 0, permanent 0):
0 in free list (0 min, 0 max allowed)
0 hits, 1 misses, 0 trims, 0 created
1 failures (2 no memory)
------------------ show process memory --------------
Total: 52695632, Used: 6390048, Free: 46305584
There are 7285732 Bytes of free I/O-Memory.
Software Version 12.1(14)EA1.
Is there a hardwarefailure possible?
Regards.
Volker
Solved! Go to Solution.
09-25-2003 06:17 AM
You can run out of memory for a number of reasons: high traffic to/through the cpu, sw bug, etc. You can check out the following link for possible assistance:
http://www.cisco.com/warp/public/63/mallocfail.shtml
This link will help you troubleshoot the problem and possibly match against a known issue. However, if you can't find a match, you will likely need to open a TAC case for this problem. If you submit a case be sure to include a 'show tech' taken from enable mode, your complete logging buffer 'sh log', and as much detail about any changes to the configuration or your network operating environment. Also, when did the problem start, how frequent has it been, etc. If you collect any data per the above tech tip include that as well.
09-25-2003 06:17 AM
You can run out of memory for a number of reasons: high traffic to/through the cpu, sw bug, etc. You can check out the following link for possible assistance:
http://www.cisco.com/warp/public/63/mallocfail.shtml
This link will help you troubleshoot the problem and possibly match against a known issue. However, if you can't find a match, you will likely need to open a TAC case for this problem. If you submit a case be sure to include a 'show tech' taken from enable mode, your complete logging buffer 'sh log', and as much detail about any changes to the configuration or your network operating environment. Also, when did the problem start, how frequent has it been, etc. If you collect any data per the above tech tip include that as well.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: