ebook img

BGP for Internet Service Providers - Apricot Inc PDF

111 Pages·2005·0.37 MB·English
Save to my drive
Quick download
Download
Most books are stored in the elastic cloud where traffic is expensive. For this reason, we have a limit on daily download.

Preview BGP for Internet Service Providers - Apricot Inc

Deploying BGP PPhhiilliipp SSmmiitthh <<ppffss@@cciissccoo..ccoomm>> AAPPRRIICCOOTT 22000055 KKyyoottoo,, JJaappaann APRICOT2005 ©2005, Cisco Systems, Inc. All rights reserved. 111 Presentation Slides • Slides are at: ftp://ftp-eng.cisco.com /pfs/seminars/APRICOT2005-Deploying-BGP.pdf And on the APRICOT2005 website • Feel free to ask questions any time APRICOT2005 ©2005, Cisco Systems, Inc. All rights reserved. 222 BGP for Internet Service Providers • Scaling BGP • Using Communities • Deploying BGP in an ISP network APRICOT2005 ©2005, Cisco Systems, Inc. All rights reserved. 333 BGP Scaling Techniques APRICOT2005 ©2005, Cisco Systems, Inc. All rights reserved. 4 BGP Scaling Techniques • How does a service provider: Scale the iBGP mesh beyond a few peers? Implement new policy without causing flaps and route churning? Keep the network stable, scalable, as well as simple? • Three Techniques: Route Refresh, Flap Damping, Route Reflector APRICOT2005 ©2005, Cisco Systems, Inc. All rights reserved. 555 Route Refresh APRICOT2005 ©2005, Cisco Systems, Inc. All rights reserved. 6 Route Refresh Problem: • Hard BGP peer reset required after every policy change because the router does not store prefixes that are rejected by policy • Hard BGP peer reset: Tears down BGP peering Consumes CPU Severely disrupts connectivity for all networks Solution: • Route Refresh APRICOT2005 ©2005, Cisco Systems, Inc. All rights reserved. 777 Route Refresh Capability • Facilitates non-disruptive policy changes • For most implementations, no configuration is needed Automatically negotiated at peer establishment • No additional memory is used • Requires peering routers to support “route refresh capability” – RFC2918 APRICOT2005 ©2005, Cisco Systems, Inc. All rights reserved. 888 Dynamic Reconfiguration • Use Route Refresh capability if supported find out from the BGP neighbour status display Non-disruptive, “Good For the Internet” • If not supported, see if implementation has a workaround • Only hard-reset a BGP peering as a last resort Consider the impact to be equivalent to a router reboot APRICOT2005 ©2005, Cisco Systems, Inc. All rights reserved. 999 Route Flap Damping Stabilising the Network APRICOT2005 ©2005, Cisco Systems, Inc. All rights reserved. 10

Description:
Border Router Communities set at the aggregation router where the prefix is injected into the ISP’s iBGP. border when adding a new customer
See more

The list of books you might like

Most books are stored in the elastic cloud where traffic is expensive. For this reason, we have a limit on daily download.