[c-nsp] OSM memory allocating process question

[Emanuel Popa]

On 3/31/06, Rodney Dunn <rodunn at cisco.com> wrote:
> Oh...just because you disable it globally I bet we are still
> downloading the data structures to the LC.
>
> You might would have to delete the policies all together.
> I don't know and I don't have one to test right now.

I have deleted all policies and removed them from the interfaces, but
the "CWTLC STAT INFO" process is still in the top with the same amount
of memory occupied:

CWTLC-Slot3#sh memory allocating-process totals | i CWTLC STAT INFO
0x603F4EC8   20447344       2  CWTLC STAT INFO

> And if dCEF is off the LC then the updates for the QOS
> stuff probably will not happen either since I'm pretty sure
> it uses the same messaging infrastructure.

I have issued a "clear cef linecard 4" and after that dCEF is back and
is running. But the memory issue is still there and dCEF will probably
go down eventually:

CWTLC-Slot3#sh memory allocating-process totals
                Head    Total(b)     Used(b)     Free(b)   Lowest(b)  Largest(b)
Processor   6183D880    92022656    91691216      331440      283432      304192
      I/O   20000000    16777216     4138720    12638496    12638496    12625400

Good night,
Emanuel