On 12/06/2012 12:03 pm, Michael Loftis wrote:
It seemed to me that it holds onto the memory until at the very least that peer is reset/clear-ed, and might until a clear ip bgp * is issued. We recently had a 6506 (same SUP IIRC) go OOM tailspin too. The fault was mine, insufficient monitoring. Had to remove soft reconfig and move some peers off of it. (In my defense I wasnt the one who set any of this up so Ive been fixing what I can as I go)
Thanks you for your insight. As it turns out, I one peer still needed to be cleared after checking out bgp summary more closely. Once I cleared it memory usage dropped.
-- ~Randy _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
