CCIE Me!

Cisco's BGP Case Studies

http://www.cisco.com/en/US/tech/tk365/technologies_tech_note09186a00800c95bb.shtml

Comparing MPLS, IPSec, and SSL VPN Architectures

The Layer 3 IP VPN architecture that an enterprise chooses for its corporate WAN has wide-ranging effects on the business, including scalability, connectivity options, and the ability to deploy voice, video, and multicast applications. Enterprises can select from Layer 3 IP VPN architectures based on Multiprotocol Label Switching (MPLS), IP Security (IPSec), and Secure Sockets Layer (SSL).

THE OPTIMAL IP VPN ARCHITECTURE FOR AN ENTERPRISE CORPORATE WAN DEPENDS ON ITS BUSINESS REQUIREMENTS

http://www.cisco.com/en/US/solutions/collateral/ns340/ns414/ns465/net_implementation_white_paper0900aecd801b1b0f.html

Cisco BGP Route Selection

1. Discard routes where the next-hop is inaccessible (thus, needs IGP route to next-hop address)
2. Prefer the path with the largest weight (Cisco proprietary, local, per-router)
3. If the weights are the same, prefer the route with the largest local preference (local-pref is distributed via iBGP, so is «AS-local»).
4. If the routes have the same local preference, prefer the route that was locally originated (by this router).
5. If the local preference is the same, prefer the route with the shortest AS_path (unless bgp bestpath as-path ignore is configured)
6. If the AS_path length is the same, prefer the route with the lowest origin type (IGP < EGP < Incomplete).
7. If the origin type is the same, prefer the route with the lowest MED (multi-exit discriminator). Cisco knobs: bgp always-compare-med, bgp bestpath med-confed, bgp deterministic-med.
8. If the routes have the same MED, prefer in the following manner: External (eBGP) is better than Confederation External which is better than Internal (iBGP).
9. If all the preceding comparisons are identical, prefer the route that can be reached via the closest IGP neighbor, i.e. take the shortest internal path inside the AS to reach the destination (follow the shortest path to the BGP NEXT_HOP). This results in what is commonly referred to as hot potato routing, because you give the «problem» (packet carriage) as quickly as possible to the next guy.
10. If both paths are external, prefer the oldest route, unless bgp bestpath compare-routerid has been configured.
11. If the internal path is the same, the BGP router ID will be a tie braker. Prefer the route coming from the BGP router with the lowest router ID. The router ID is usually the highest IP address on the router or the loopback (virtual) address. The router ID could be implementation specific.
12. If the router ID is the same, prefer the path with the minimum cluster ID length (only relevant for route reflector configs)
13. Prefer the path coming from the lowest neighbor address.

http://www.cisco.com/en/US/tech/tk365/technologies_tech_note09186a0080094431.shtml