Is inbound as-path filtering an efficient way of
preventing routes from entering your bgp table? How
come the filtered routes still show up in the bgp
table and not in the routing table? What is hit on the
CPU?
Is inbound as-path filtering an efficient way of
preventing routes from entering your bgp table? How
come the filtered routes still show up in the bgp
table and not in the routing table? What is hit on the
CPU?
AFAIK, it shouldn't show up on bgp table if you are filtering inbound to you.
Do a sh ip bgp a.b.c.d/affectedaddr please.
Remember that Cisco's bgp implementation is scan-based, so it takes a bit of
time for policy changes to kick in. Try doing 'clear ip bgp w.x.y.z in' in an
attempt to speed it up.
-J
Do you have 'soft-reconfiguration inbound' on ?
If so it will hit the BGP table but will be marked as received-only.
This allows for re-scanning of the table in order to effect filter and
other changes without a hard reset of the session.