Introduction to BGP

This lesson will be interesting! BGP (Border Gateway Protocol) is the routing protocol that glues the Internet together. I’m going to explain in which situations we need BGP and how it works.

Before you continue reading I should tell you to “forget” everything you know about routing protocols like RIP, OSPF and EIGRP so far…Those three routing protocols have one thing in common: they are all IGPs (Interior Gateway Protocols). We only use them within our autonomous system but they are not scalable to use for a network as large as the Internet.

RIP, OSPF and EIGRP are all different but they have one thing in common…they want to find the shortest path to the destination. When we look at the Internet we don’t care as much as to find the shortest path, being able to manipulate traffic paths is far more important. There is only one routing protocol we currently use on the Internet which is BGP.

Why do we need BGP?

Let’s start by looking at some scenarios so you can understand why and when we need BGP:

ISP Customer Internet

Nowadays almost everything is connected to the Internet. In the picture above we have a customer network connected to an ISP (Internet Service Provider). Our ISP is making sure we have Internet access. Our ISP has given us a single public IP address we can use to access the Internet. To make sure everyone on our LAN at the customer side can access the Internet we are using NAT/PAT (Network / Port address translation) to translate our internal private IP addresses to this single public IP address. This scenario is excellent when you only have clients that need Internet access. On our customer LAN we only need a default route pointing to the ISP router and we are done. For this scenario we don’t need BGP…

ISP Customers Servers Internet

Maybe the customer has a couple of servers that need to be reachable from the Internet…perhaps a mail- or webserver. We could use port forwarding and forward the correct ports to these servers so we still only need a single IP address. Another option would be to get more public IP addresses from our ISP and use these to configure the different servers. For this scenario we still don’t need BGP…

ISP Customer Servers Internet Redundancy

What if I want a bit more redundancy? Having a single point of failure isn’t a good idea. We could add another router at the customer side and connect it to the ISP. You can use the primary link for all traffic and have another link as the backup. We still don’t require BGP in this situation, it can be solved with default routing:

  • Advertise a default route in your IGP on the primary customer router with a low metric.
  • Advertise a default route in your IGP on the secondary customer router with a high metric.

This will make sure that your IGP sends all traffic using the primary link. Once the link fails your IGP will make sure all traffic is sent down the backup link. Let me ask you something to think about…can we do any load balancing across those two links? It’ll be difficult right?

Your IGP will send all traffic down the primary link and nothing down the backup link unless there is a failure. You could advertise a default route with the same metric but you’d still have something like a 50/50% load share. What if I wanted to send 80% of the outgoing traffic on the primary link and 20% down the backup link? That’s not going to happen here but with BGP it’s possible.

Customer two ISPs BGP

This scenario is a bit more interesting. Instead of being connected to a single ISP we now have two different ISPs. For redundancy reasons it’s important to have two different ISPs, in case one fails you will always have a backup ISP to use. What about our Customer network? We still have two servers that need to be reachable from the Internet.

In my previous examples we got public IP addresses from our ISP. Now I’m connected to two different ISPs so what public IP addresses should I use? From ISP1 or ISP2? If we use public IP addresses from ISP1 (or ISP2) then these servers will be unreachable once the ISP has connectivity issues.

Instead of using public IP addresses from the ISP we will get our own public IP addresses.The IP address space is maintained by IANA (Internet Assigned Numbers Authority – http://www.iana.org/ ). IANA is assigning IP address space to a number of large Regional Internet Registries like RIPE or ARIN. Each of these assign IP address space to ISPs or large organizations.
When we receive our public IP address space then we will advertise this to our ISPs. Advertising is done with a routing protocol and that will be BGP.

If you are interested here’s an overview of the IPv4 space that has been allocated by IANA:

IANA IPv4 address space

Autonomous Systems

Besides getting public IP address space we also have to think about an AS (Autonomous System):

autonomous system numbers

An AS is a collection of networks under a single administrative domain. The Internet is nothing more but a bunch of autonomous systems that are connected to each other. Within an autonomous system we use an IGP like OSPF or EIGRP.

For routing between the different autonomous systems we use an EGP (external gateway protocol). The only EGP we use nowadays is BGP.

How do we get an autonomous system number? Just like public IP address space you’ll need to register one.

Autonomous system numbers are 16-bit which means we have 65535 numbers to choose from. Just like private and public IP addresses, we have a range of public and private AS numbers.

Range 1 – 64511 are globally unique AS numbers and range 64512 – 65535 are private autonomous system numbers.

If you are interested, see if you can find the AS number of your ISP:

UltraTools AS Information Lookup

BGP has two flavors:

  • External BGP: used between autonomous systems
  • Internal BGP: used within the autonomous system.

External BGP is to exchange routing information between the different autonomous systems. In this lesson I explain why we need internal BGP. I would recommend to read it after finishing this lesson and learning about external BGP first.

BGP Advertisements

You now have an idea of why we require BGP and what autonomous systems are. The Internet is a big place, as I am writing this there are more than 500.000 prefixes in a complete Internet routing table. If you are curious, you can find the size of the Internet routing table here:

CIDR Report

On the internet there are a number of looking glass servers. These are routers that have public view access and you can use them to look at the Internet routing table. If you want to see what it looks like check out:

Looking glass servers

Scroll down all the way to “Category 2 – IPv4 and IPv6 BGP Route Servers by region (TELNET access)”. You can telnet to these devices and use show ip route and show ip bgp to check the BGP or routing table.

When we run BGP, does this mean we have to learn more than 500.000 prefixes? It depends…let’s look at some examples:

BGP AS1 AS2 AS3 ISP Customer

Above in our picture our customer network has an autonomous system number (AS 1) and some IP address space (10.0.0.0 /8), let’s pretend that these are public IP addresses. We are connected to two different ISPs and you can see their AS number (AS2 and AS3) and IP address space (20.0.0.0/8 and 30.0.0.0/8). We can reach the rest of the internet through both ISPs.

We can use BGP to advertise our address space to the ISPs but what are the ISPS going to advertise to our customer through BGP? There are a number of options:

  • They advertise only a default route.
  • They advertise a default route and a partial routing table.
  • They advertise the full Internet routing table.

Let’s walk through these three options!

We're Sorry, Full Content Access is for Members Only...

If you like to keep on reading, Become a Member Now! Here is why:

  • Learn any CCNA, CCNP and CCIE R&S Topic. Explained As Simple As Possible.
  • Try for Just $1. The Best Dollar You've Ever Spent on Your Cisco Career!
  • Full Access to our 660 Lessons. More Lessons Added Every Week!
  • Content created by Rene Molenaar (CCIE #41726)

505 Sign Ups in the last 30 days

satisfaction-guaranteed
100% Satisfaction Guaranteed!
You may cancel your monthly membership at any time.
No Questions Asked!

Tags:


Forum Replies

  1. Hi Rene…

     

    What an awesome article… simple and nice explanation,…

  2. Hi Rene,

    This is all I have to say, THANK YOU! :clap::clap::clap:

    Complicated concepts, made very objective.

  3. Hello Laz,

    Thanks for clarification. Now i am getting your point.

    Please make me correct if i am wrong. Now i am taking AD and FD value from R2’s perspective.

    1. Advertised distance from R3 is 9 (Path R3->R4) directly
    2. Advertise distance from R1 is 25 (Path R1->R2->R3->R4->Destnation). Second path would not be selected as per split horizon rule which is (R1->R3->R4->Destination).

    Feasible distance

    1. FD from R3 is = 9+4+5=18

    2. FD from R1 is = 25+7= 32

    Thanks,
    Abhishek Saini

  4. Hi Ziad,

    In reality, when R3 receives an update from R1 or R2 about the destination behind R4, it won’t install them since these don’t pass the feasibility condition (AD of the feasible successor has to be lower than FD of successor).

    R3 will only advertise its successor route to other neighbors. In this topology, R4 is the successor route so normally R3 would advertise this route to R4. However, because of split horizon (don’t advertise a route to a neighbor if you learned that route from the neighbor)…this route is not advertised.

    It might be helpful to see a

    ... Continue reading in our forum

  5. The topology is being viewed from the standpoint of R3. We have the benefit here of seeing the full network topology, and you can trace if R3 used R1 or R2 as a feasible successor, to reach the destination, you’ll be going in a loop back to R3 (where you started).

127 more replies! Ask a question or join the discussion by visiting our Community Forum