2811 eating all IO memmory

[Tsasbrink]

Hi,

We have an 2811 which uses crypto and nat.

This router consumes all of its IO memory over time and starts generating alloc failures.

IF we compare the memory usage of the io memory to a healty router with a comparable config it had several 65Kb memory blocks assigned to Normal.

it is running 12.4 3g.

Anyone an idea ?

TIA,

Tom

[a.alekseev]

You have a memory leak.

You need upgrade your IOS.

[Tsasbrink]

It sure looks like it, but my question is how do I confirm that it is an known bug or not.

I will not be able te know if newer ios code will fix it or not if i can not indentify the bug.

[a.alekseev]

Do some research with Cisco BUG Tool.

http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl

See release notes for IOS which you have

Open a service request with a CiscoTAC.

[a.alekseev]

looks like it's yours

CSCsb60583 Bug Details

NetGX : Memory Leak in IOmem - Normal buffer

Symptom:

When running a 2800 at a high CPU utilization, I/O Memory will begin to

decrease until all memory is exhausted. At that point the router begins

reporting "Pool Manager" tracebacks.

Conditions:

This symptom is observed on a Cisco 2811 or Cisco 2821 that

uses the onboard Virtual Private Network (VPN) crypto engine.

The symptom is prominantly observed when crypto is configured

over serial interfaces.

Workaround:

There is no workaround. The router must be reloaded to recover.

[Tsasbrink]

The problem seems to be solved by upgrading to 12.4 19b software.

The profile however does not meet our situation entirely because we are not running on high cpu load. in normal behaviour the highest peeks with shoe proc cpu his are registered te be 5%.

[adns]

We tested with 12.4.19b and still saw the memory leak. Cisco support desk recommends upgrading from our old 12.4.10 to 19b but it looks like 19b doesn't pan out. Has anyone looked at 12.4.21 to resolve this memory leak?

[Tsasbrink]

We have not used this version as i believe it was not available at the time we were investigating this.

But anyway the bug behaviour does not seem to be predictable as we still have allmost similar configured routers which do not have the problems with 12.4.3g.

Anyway the 12.4.19b does not seem to give us any trouble.

555555555555555555555555555555555555555555555555555555555555555555555555

222222222222222222222222222222222222222222222222222222222222222222222222

100

90

80

70

60

50 ########################################################################

40 ########################################################################

30 ########################################################################

20 ########################################################################

10 ########################################################################

0....5....1....1....2....2....3....3....4....4....5....5....6....6....7..

0 5 0 5 0 5 0 5 0 5 0 5 0

Free memory per hour (last 72 hours)

* = maximum # = average