That's fine. It just means we fell back to malloc a block that could hold it.
On Mon, Feb 16, 2009 at 03:45:29PM -0600, Justin Shore wrote: > I don't know if it's related or not but one of my borders and another > nearly identical box much further into the network logged these with > 18 seconds of each other: > > Feb 16 10:23:38 10.64.0.1 968577: 968585: Feb 16 10:23:37 CST: > %BGP-6-BIGCHUNK: Big chunk pool request (522) for aspath. > Replenishing with malloc > > Both are running 12.4(15)Tn releases. > > Justin > > > > Rodney Dunn wrote: > >One of those what? > > > >All I want is: > > > >sh ver > >sh log > >sh ip bgp <nei> > > > >on a box that SENT the BGP notification on receipt of the update. > > > >Don't send it if the BGP session when down because the notification > >was received. > > > >rodney > > > >On Mon, Feb 16, 2009 at 09:00:02PM +0000, Marko Milivojevic wrote: > >>On Mon, Feb 16, 2009 at 20:32, Rodney Dunn <rod...@cisco.com> wrote: > >>>We are working on that. I'll let you know once I have more. > >>We've got one of these on our node running SRB3. It was trigerred on > >>only one session when being announced to a customer. > >_______________________________________________ > >cisco-nsp mailing list cisco-nsp@puck.nether.net > >https://puck.nether.net/mailman/listinfo/cisco-nsp > >archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/