Grab multiple captures of sh proc mem to identify the process "holding" and not releasing (i.e. leaking) memory. When memory is heavily depleted, grab a *show memory allocating-process totals* and feel free to unicast.
Any MALLOC failures? -Eninja On Sun, Aug 30, 2009 at 10:11 AM, Chris Phillips <[email protected]>wrote: > Every six weeks or so I am running out of memory on a 6509 w/ dual > SUP720-3BXL with mostly 6700-series line cards. > > I have 21 other nodes with this exact same configuration, some even running > SXI or SXI1 that do not have this issue, which first led me to believe that > the issue might be hardware related. > > During our last maintenance window to alleviate the memory issue, I forced > the standby SUP to become the active SUP. The memory issue persisted, > leading me back to thinking it is a software issue. > > I did not have this issue with SXH* on this same device, but SXH is *SO* > buggy, rolling back is not an option. This leads me to believe that it is > most likely a software issue. > > The router is heavily used with 250+ BGP sessions, OSPF, MPLS, v4/v6, etc, > but I don't think it should be consuming and not releasing 4 mbytes of > memory each day. > > Has anyone else seen this? Anyone know a workaround? > > I'm upgrading to SXI2 tomight in hopes that it resolves my issue. > > -- > Chris Phillips > > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
