[c-nsp] OSM memory allocating process question

[Rodney Dunn]

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.

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.

Rodney

On Fri, Mar 31, 2006 at 11:05:20AM -0500, Rodney Dunn wrote:
> Can you get a 'sh proc mem sort' and then get a 'sh proc mem <PID>
> for the few processes holding the top amounts of memory?
> 
> Rodney
> 
> On Fri, Mar 31, 2006 at 06:35:31PM +0300, Emanuel Popa wrote:
> > On 3/31/06, Rodney Dunn <rodunn at cisco.com> wrote:
> > > On Fri, Mar 31, 2006 at 01:26:27PM +0300, Emanuel Popa wrote:
> > > > [...]
> > > >
> > > > Allocator PC Summary for: Processor
> > > >
> > > >     PC          Total   Count  Name
> > > > 0x603F4EC8   20447344       2  CWTLC STAT INFO
> > > > 0x602D8740    6291568       2  SCP Find Master process
> > > > 0x602D8A74    3604592       2  SCP Find Master process
> > > > 0x603F4EB0    3145840       2  Init
> > > > 0x602A0A20    1500056       1  rp if_info
> > > > 0x604C18B8    1377432      21  Linecard CEF m
> > > > 0x604597E4    1179648   12288  Init
> > > > 0x603F2F2C    1080056       1  fr if_info
> > > > [...]
> > > >
> > > > Allocator PC Summary for: I/O
> > > >
> > > >     PC          Total   Count  Name
> > > > 0x600ECB70    2952320       5  COMM
> > > > 0x600E6A54    1055392     338  *Packet Data*
> > > >
> > > > [...]
> > > >
> > > > Of course, an upgrade is necessary and will be done eventually...
> > >
> > > Yeah..but I do find it a bit odd that a STAT INFO type process would
> > > be holding 20M. I think that is some information about QOS running
> > > on the card. What code are you running?
> > >
> > > I see some changes where they changed things in this area in 12.2(18)SXD
> > > but I can't tell how much it would have changed it because it appears
> > > to be configuration specific.
> > >
> > 
> > the code we are running is 12.2(18)SXF:
> > 
> > ROUTER#sh ver | i IOS
> > IOS (tm) s72033_rp Software (s72033_rp-ADVIPSERVICESK9_WAN-M), Version
> > 12.2(18)SXF, RELEASE SOFTWARE (fc1)
> > 
> > i tried disabling qos because we were only using it to change the DSCP
> > of the packets in order to identify them on the access layer:
> > 
> > ROUTER#sh mls qos
> >   QoS is disabled globally
> > 
> > but the STAT INFO process still takes 20MB of our precious memory.
> > here is the memory allocating process from another OSM in the same
> > chassis:
> > 
> > CWTLC-Slot1#sh memory allocating-process totals
> >                 Head    Total(b)     Used(b)     Free(b)   Lowest(b)  Largest(b)
> > Processor   6183D880    92022656    91908624      114032       67664       71384
> >       I/O   20000000    16777216     3926232    12850984    12639360    12561432
> > 
> > Allocator PC Summary for: Processor
> > 
> >     PC          Total   Count  Name
> > 0x604CD6A8   30718952     912  FIB 1 path chu
> > 0x603F4EC8   20447344       2  CWTLC STAT INFO
> > 0x604CD7D8   11679168     354  IP mtrie node
> > 0x602D8740    6291568       2  SCP Find Master process
> > 0x602D8A74    3604592       2  SCP Find Master process
> > 0x603F4EB0    3145840       2  Init
> > 0x602A0A20    1500056       1  rp if_info
> > 0x604C18B8    1377432      21  Linecard CEF m
> > 0x604597E4    1179648   12288  Init
> > 0x603F2F2C    1080056       1  fr if_info
> > [...]
> > 
> > Indeed, we are running as close to the edge as possible.
> > 
> > Do you think there is any chance to find out more details about this
> > process: "CWTLC STAT INFO". Is there anybody out there with a 7600, a
> > full routing table, an OSM linecard and 12.2(18)SX? I would be curious
> > to see how much memory does this process take on other
> > configurations...
> > 
> > Thx,
> > Emanuel Popa