[c-nsp] Re: MLP Memory Leak Issues in 12.2.25S1??
Brian Feeny
signal at shreve.net
Tue Jan 18 15:45:15 EST 2005
I did open this as case 600867998 and put the configs in place.
Brian
On Jan 18, 2005, at 1:49 PM, Dennis Peng wrote:
> Possibly CSCsa49019, which is committed to 12.2S, but not yet
> integrated into a release. Would need to see the configuration first
> to make sure. "debug ppp multilink events" should generate some error
> too if you are running into this problem. Is the bundle up and
> running?
>
> Dennis
>
> Brian Feeny [signal at shreve.net] wrote:
>>
>> Rodney,
>>
>> Apologies. Below is some output that I could get. I cannot get the
>> interface configuration just yet, until the
>> router gets reloaded, and I have put in a request for that.
>>
>> Its very possible something bad is being done in the configuration,
>> this router I have not been able to take a
>> look at yet, I certainly didn't configure it in the first place.
>>
>>
>>
>> System image file is "disk1:c7200-a3jk91s-mz.122-25.S1.bin"
>>
>>
>>
>> 131 0 192 192 6864 0 0
>> Multilink PPP
>> 132 0 192 192 6864 0 0
>> Multilink PPP ou
>> 133 0 135940368 170195840 40791248 0 0
>> Multilink event
>>
>>
>>
>>
>> nwcorp#show proc mem 131
>> Process ID: 131
>> Process Name: Multilink PPP
>> Total Memory Held: 6864 bytes
>>
>> Processor memory Holding = 6864 bytes
>> pc = 0x60745E50, size = 6056, count = 1
>> pc = 0x607328F8, size = 616, count = 1
>> pc = 0x607349BC, size = 192, count = 1
>>
>> I/O memory Holding = 0 bytes
>>
>> PCI memory Holding = 0 bytes
>>
>> nwcorp#show proc mem 132
>> Process ID: 132
>> Process Name: Multilink PPP out
>> Total Memory Held: 6864 bytes
>>
>> Processor memory Holding = 6864 bytes
>> pc = 0x60745E50, size = 6056, count = 1
>> pc = 0x607328F8, size = 616, count = 1
>> pc = 0x607349BC, size = 192, count = 1
>>
>> I/O memory Holding = 0 bytes
>>
>> PCI memory Holding = 0 bytes
>>
>> nwcorp#show proc mem 133
>> Process ID: 133
>> Process Name: Multilink event
>> Total Memory Held: 40791248 bytes
>>
>> Processor memory Holding = 40791248 bytes
>> pc = 0x60B28FF8, size = 40782208, count = 408771
>> pc = 0x60745E50, size = 6056, count = 1
>> pc = 0x607328F8, size = 616, count = 1
>> pc = 0x60B26CD8, size = 416, count = 3
>> pc = 0x60B0F814, size = 408, count = 3
>> pc = 0x60B253D8, size = 392, count = 1
>> pc = 0x60AB8C14, size = 288, count = 3
>> pc = 0x607349BC, size = 192, count = 1
>> pc = 0x60AB8BDC, size = 176, count = 2
>> pc = 0x60AB8E90, size = 168, count = 2
>> pc = 0x60AB8E64, size = 168, count = 2
>> pc = 0x60AB8DDC, size = 160, count = 2
>>
>> I/O memory Holding = 0 bytes
>>
>> PCI memory Holding = 0 bytes
>>
>>
>>
>> On Jan 18, 2005, at 7:41 AM, Rodney Dunn wrote:
>>
>>> When you post a question about a possible bug
>>> please always include the full IOS name.
>>>
>>> That's because to decode the PC values we
>>> have to map it to a symbols file.
>>>
>>> Can you post the relevant interface configurations
>>> also?
>>>
>>> If you can get 'sh proc mem' to see what the
>>> process ID is for MLP bundle name then do a
>>> 'sh proc mem <PID>' for it.
>>>
>>> Rodney
>>>
>>> On Mon, Jan 17, 2005 at 10:21:28PM -0600, Brian Feeny wrote:
>>>> Is anyone aware of any problems in 12.2.25S1 that would cause a
>>>> memory
>>>> leak in MLP?
>>>>
>>>> We have a 7204 that is doing MLP on over 2 T1 lines, running
>>>> 12.2.25S1
>>>> for about 4 weeks. It is out of memory so the CLI is not allowing
>>>> me
>>>> to do alot of things (like "show run").
>>>>
>>>> I do see however:
>>>>
>>>> nwcorp#show mem allocating-process totals
>>>> Head Total(b) Used(b) Free(b)
>>>> Lowest(b)
>>>> Largest(b)
>>>> Processor 636CBC80 59982720 59793888 188832 0
>>>> 91024
>>>> I/O 7000000 16777216 1635216 15142000
>>>> 15022688
>>>> 15134176
>>>> PCI 4B000000 4194304 842144 3352160
>>>> 3352160
>>>> 3352128
>>>>
>>>>
>>>>
>>>>
>>>> Allocator PC Summary for: Processor
>>>>
>>>> PC Total Count Name
>>>> 0x60B28FF8 40782208 408771 MLP bundle name
>>>> 0x606F6E08 3840280 5 Init
>>>> 0x60352590 1937616 2 RMON packet pool
>>>> 0x60745E50 1302008 143 Interrupt Stack
>>>> 0x606A6C34 603696 747 *Packet Header*
>>>> 0x606D9414 560152 1 IDB List Element Chunks
>>>>
>>>>
>>>> I did check Bug Toolkit for anything that hit on MLP, but nothing in
>>>> there looks like it would cause what I am seeing. The router is
>>>> working, and I plan to reload it soon to do more diagnostics, but if
>>>> anyone knows of this issue, please let me know.
>>>>
>>>> Brian
>>>>
>>>>
>>>> Brian Feeny, CCIE #8036, CISSP
>>>> Network Engineer
>>>> ShreveNet Inc.
>>>>
>>>> _______________________________________________
>>>> cisco-nsp mailing list cisco-nsp at puck.nether.net
>>>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>>>> archive at http://puck.nether.net/pipermail/cisco-nsp/
>>>>
>> ---------------------------------------------
>> Brian Feeny, CCIE #8036, CISSP
>> Network Engineer
>> ShreveNet Inc.
>>
>> _______________________________________________
>> cisco-nsp mailing list cisco-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-nsp
>> archive at http://puck.nether.net/pipermail/cisco-nsp/
>>
------------------------------------------------------------------------
------
Brian Feeny, CCIE #8036, CISSP e: signal at shreve.net
Network Engineer p: 318.213.4709
ShreveNet Inc. f: 318.221.6612
More information about the cisco-nsp
mailing list