nanog mailing list archives
Re: as path filtering -- cisco implementation
From: James <haesu () towardex com>
Date: Fri, 16 Jul 2004 14:47:16 -0400
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 -- James Jun TowardEX Technologies, Inc. Technical Lead Network Design, Consulting, IT Outsourcing james () towardex com Boston-based Colocation & Bandwidth Services cell: 1(978)-394-2867 web: http://www.towardex.com , noc: www.twdx.net
Current thread:
- as path filtering -- cisco implementation Philip Lavine (Jul 16)
- Re: as path filtering -- cisco implementation James (Jul 16)
- Re: as path filtering -- cisco implementation Steve Baxter (Jul 16)
- Re: as path filtering -- cisco implementation James (Jul 16)