BGP (Border Gateway Protocol) routers usually receive multiple paths to the same destination. Like how our IGPs (RIP, EIGRP, OSPF) work, we need to select the best path to each destination.
IGPs select the path with the lowest metric. For example:
- RIP selects the path with the lowest hop count.
- OSPF selects the path with the lowest cost.
- EIGRP selects the path with the highest bandwidth and lowest delay (unless you change the K values).
BGP however, selects the best path based on a list of attributes. On the Internet, it’s more important that you have granular control over how you forward your traffic and to which autonomous systems instead of just going for the shortest path based on a metric.
Let’s look at a quick example. Below I have the output of the BGP table of a looking glass server:
oute-views.optus.net.au>show ip bgp BGP table version is 781755060, local router ID is 184.108.40.206 Status codes: s suppressed, d damped, h history, * valid, > best, i - internal, r RIB-failure, S Stale, m multipath, b backup-path, x best-external Origin codes: i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight Path * 220.127.116.11/24 18.104.22.168 0 7474 4826 13335 i * 22.214.171.124 1 0 7474 4826 13335 i * 126.96.36.199 1 0 7474 4826 13335 i * 188.8.131.52 10 0 7474 4826 13335 i *> 184.108.40.206 0 7474 4826 13335 i
This BGP router has 5 paths for network 220.127.116.11/24. Look at the > symbol at the bottom left. The > symbol means that BGP has selected this path as the best path. This path will be installed in the routing table.
Out of all those 5 paths, why did BGP select this path as the best path?
This path was selected based on the following attributes:
|4||AS path length|
|7||eBGP path over iBGP path|
|8||Shortest IGP path to BGP next hop|
|11||Neighbor IP address|
Let me give you a quick overview of each attribute. We will cover these in other lessons in detail.
Prefer the path with the highest weight. This is a value that is local to the router and it’s Cisco proprietary. The default value is 0 for all routes that are not originated by the local router. You can learn how it works in the BGP weight attribute lesson.
The local preference is used within an autonomous system and exchanged between iBGP routers. We prefer the path with the highest local preference. The default value is 100. To learn more, take a look at the BGP local preference attribute lesson.
Prefer the path that the local router originated. In the BGP table, you will see next hop 0.0.0.0. You can get a path in the BGP table through the BGP network command, aggregation, or redistribution. A BGP router will prefer routes that it installed into BGP itself over a route that another router installed in BGP.
AS path length
Prefer the path with the shortest AS path length. For example, AS path 1 2 3 is preferred over AS path 1 2 3 4 5. You can learn more about AS path length here.
Prefer the lowest origin code. There are three origin codes:
IGP is lower than EGP and EGP is lower than INCOMPLETE. You can learn how it works in the origin code lesson.
Prefer the path with the lowest MED. The MED is exchanged between autonomous systems. For a detailed explanation, take a look at the MED lesson.
eBGP path over iBGP path
Prefer eBGP (external BGP) over iBGP (internal BGP) paths.
Shortest IGP path to BGP next hop
Prefer the path within the autonomous system with the lowest IGP metric to the BGP next hop.
Prefer the path that we received first, in other words, the oldest path.
Prefer the path with the lowest BGP neighbor router ID. The router ID is based on the highest IP address. If you have a loopback interface, then the IP address on the loopback will be used. The router ID can also be manually configured.
Neighbor IP address
Prefer the path with the lowest neighbor IP address. If you have two eBGP routers and two links in between then the router ID will be the same. In this case, the neighbor IP address is the tiebreaker.
When BGP has multiple paths to a destination they are stored in the BGP table. All paths are in the BGP table but only one gets installed in the routing table.
Which path do we select? We start at the top of the list with BGP attributes and work our way to the bottom:
- We start with weight because it’s at the top of the BGP attributes list. We now have two options:
- If one path has a better weight then we select this path as the best path.
- If the weight is equal, we move down to the next attribute.
- The next attribute is local preference. Once again, we have two options:
- If one path has a better local preference then we select this path as the best path.
- If the local preference is equal, we move down to the next attribute.
- We work our way down this attribute list until we have a tiebreaker to select the best path. If all paths have the same BGP attributes, then we end up with the neighbor IP address.
I hope this lesson has been useful to understand how BGP selects the best path.