Another important part of this is most of the recent routers
support route-refresh:
Router>sh ip bgp nei 198.32.162.100
BGP neighbor is 198.32.162.100, remote AS 6447, external link
Index 1, Offset 0, Mask 0x2
feed-me peer-group member
Community attribute sent to this neighbor
BGP version 4, remote router ID 198.32.162.100
BGP state = Established, table version = 219413, up for 1d04h
Last read 00:00:39, last send 00:00:03
Hold time 180, keepalive interval 60 seconds
Neighbor NLRI negotiation:
Configured for unicast and multicast routes
Peer negotiated unicast and multicast routes
Exchanging unicast and multicast routes
Sends NEXT_HOP attribute for MBGP NLRIs
Uses NEXT_HOP attribute for MBGP NLRIs
Received route refresh capability(new) from peer
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
This makes it possible to do soft-reconfig stlye stuff but
without having to enable soft-reconfig on your router.
That greatly helps conserve memory.
- Jared
On Thu, May 31, 2001 at 12:42:25PM -0400, George Robbins wrote:
> It's an interesting question. IOS *has* to store more information
> when soft-reconfig is enabled, the question is how selective it
> is, and if/when it gives it back. I think to really resolve the
> issue you might have to try removing and replacing BGP sessions
> or trying it one way, rebooting, and trying it the other way.
>
> Either that or hope of of the Cisco whizzes wants to take about
> data structures...
>
> George
>
> > From gert@greenie.muc.de Thu May 31 12:29:51 2001
> > Date: Thu, 31 May 2001 18:30:17 +0200
> > From: Gert Doering <gert@greenie.muc.de>
> > To: George Robbins <grr@shandakor.tharsis.com>, jared@puck.nether.net,
> > kf@reign.sk
> > Cc: cisco-nsp@puck.nether.net
> > Subject: Re: Full BGP and memory
> > References: <200105311601.MAA17037@shandakor.tharsis.com>
> > In-Reply-To: <200105311601.MAA17037@shandakor.tharsis.com>; from George Robbins on Thu, May 31, 2001 at 12:01:37PM -0400
> > X-mgetty-docs: http://alpha.greenie.net/mgetty/
> >
> > Hi,
> >
> > On Thu, May 31, 2001 at 12:01:37PM -0400, George Robbins wrote:
> > > Avoid "expensive" BGP options like "soft reconfig", "bgp multipath" or
> > > "dampening" which can increase the size of bgp tables. Don't run an
> > > IGP unless you need one. 8-)
> >
> > One question on "soft reconfig". I'm one of the people that have problems
> > with their 7206 and 128 Mb RAM - on both "full" BGP peers (one internal,
> > one external) "soft reconfig" has been switched off, but didn't bring
> > any memory benefits (!).
> >
> > I have a number of "small" peers, that *do* use "soft reconfig".
> >
> > Is it possible that once you switch on "soft reconfig" for any peer
> > it will eat up memory for *all* BGP entries? (This is just wild
> > speculation, but this is the only way I could explain why turning off
> > the "soft in" on the full eBGP peer didn't change anything).
> >
> > gert
> > --
> > USENET is *not* the non-clickable part of WWW!
> > //www.muc.de/~gert/
> > Gert Doering - Munich, Germany gert@greenie.muc.de
> > fax: +49-89-35655025 gert.doering@physik.tu-muenchen.de
> >
-- Jared Mauch | pgp key available via finger from jared@puck.nether.net clue++; | http://puck.nether.net/~jared/ My statements are only mine.
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:39 EDT