RE: sh ip bgp ne [routes|advertised-routes|received-routes] and

Hammer,

The reason for this is that a copy of the pre-processed routes (before filters etc) are kept as well as the route which are accepted into the table. A router receiving a full feed could quickly run out of memory this way. It's good briefly for testing and then remove after you have your filters in check.

-ryan

-----Original Message-----
From: nobody_at_groupstudy.com [mailto:nobody_at_groupstudy.com] On Behalf Of Hammer
Sent: Wednesday, June 03, 2009 10:28 AM
To: ccielab_at_groupstudy.com
Subject: sh ip bgp ne [routes|advertised-routes|received-routes] and soft reconfiguration

I'm a little confused on this. I can build peers and verify
advertised-routes and just "routes" which is routes learned from the
neighbor. As I understand, "routes" is what has been received from the
neighbor but might be filtered from the RIB for a variety of reasons. If I
try to look at "received-routes" I get a "% Inbound soft reconfiguration not
enabled on x.x.x.x"

OK. I've read up on the BGP soft reset "function" as well as the old
enhancements page from Cisco to figure this out. What I can't understand is
why I must have soft reconfiguration enabled on a peer in order to look up
what routes I am processing from him. Am I totally missing the boat on this?
If anyone can clarify the differences in these commands in case I am
misinterpreting them as well as how the soft reconfiguration influences them
I would greatly appreciate it. Googling reveals some but does not provide
full enlightenment...

-Hammer

Blogs and organic groups at http://www.ccie.net
Received on Wed Jun 03 2009 - 10:41:46 ART