Blog posts

BGP (Border Gateway Protocol) is the protocol of the Internet. BGP is designed to handle hundreds of thousands of routes unlike our IGP counterparts. Currently there are roughly 635 000 IPv4 routes on the internet. Could you imagine an IGP like OSPF running on an Internet router containing 635k routes? It would die if a link flapped. This is why BGP was created. Actually, there was an Internet routing protocol called EGP (Exterior Gateway Protocol) which was BGP's predecessor however it was replaced by BGP a long time ago. 

OSPFv3 is the updated version of OSPFv2 that has support for IPv6 addressing as well as IPv4. OSPFv3 is defined in RFC 5340. OSPFv3 differs to OSPFv2 in the following ways:

Okay, so now let's talk about how to configure OSPF. Configuring OSPF is just like configuring any other dynamic routing protocol. You first need to enable OSPF by configuring the OSPF process ID by using the global configuration command router ospf <process-id>. Once you have configured the OSPF Process ID, it is best practice to manually configure the OSPF Router ID using the router ospf configuration subcommand router-id <id>.

An OSPF area is a logical grouping of routers into a specific OSPF area (Area 0, the backbone area by default). Using a single area OSPF design has it's benefits in that it can simplify your network, however there are some drawbacks to using a single area when your OSPF network gets too large. 

In this part of the OSPF article, I will talk about OSPF Area types and also the specific LSA messages and where/how they're used. 

OSPF uses the concept of Areas to logically group routers together inside an AS. There are 5 different area types on Cisco OSPF routers.

1. Backbone Area (This is always Area 0)
2. Non-Backbone Area (Any other are other than 0)
3. Stub Area 
4. Totally Stubby Area
5. Not-So-Stubby-Area (NSSA)

OSPF (Open Shortest Path First) is the IETFs replacement IGP for RIP and is a link state routing protocol. Link state routing protocols advertise all of the information about all links to all link state routers inside the AS. OSPF is a link state protocol thst uses Dijkstra's SPF algorithm to find the shortest path to a network. 

Now that I've discussed the ins and outs of how EIGRP works, let's talk about the configuration of EIGRP.

Cisco routers support two methods of configuring EIGRP. There is the traditional method that supports IPv4 only, and the named EIGRP method that supports both IPv4 and IPv6 route using address families. Both the traditional and Named EIGRP configurations are backwards compatible with each other so you can configure each router in your topology in either method without any issues. 

RIP is probably one of the oldest routing protocols and if i'm honest, it should stand for Rest In Peace instead of Routing Information Protocol. In saying that, at one stage it was a great little lightweight protocol. RIP is a distance vector routing protocol that uses hop count as a metric. Each router in the path to a network is considered a hop. 

EIGRP is considered a hybrid distance vector protocol. While EIGRP does keep track of hop count as a metric, it doesn't so much use it as a metric like RIP does. Instead EIGRP uses path attributes to determine the best route. Don't worry too much about these path attributes as I will go through them later.

Let's start with how EIGRP sends routing information. EIGRP uses the multicast address 224.0.0.9 to send its messages using the EIGRP protocol number 88. There are 5 types of EIGRP messages that a router will send.

This article brings us to the Layer 3 part of the Network world and routing in general. In order for a packet to be sent from its source to its destination, our network devices, either a Router or a MLS, need to know how to get there. And to do that, Routers need to know which next-hop device the packet should be forwarded to and in which direction (Interface) that next-hop device is. There are several ways for routers to learn this information.