There are many millions of routes on the internet. If these routes all had to be stored individually the internet would have come to a stop many years ago.
Route summarization is also knows as supernetting and was proposed in RFC 1338 which you can read online by clicking on the RFC or if you have printed this document by visiting www.faqs.org/rfcs/rfc1338.html. If you want to read a very comprehensive guide to route summarization then please grab a hold of Jeff Doyles excelling Cisco book Routing TCP/IP Volume 1 which is in its second edition now.
The system was devised to make routing of mail more accurate and efficient. The sorting office in Atlanta doesn't need to know which street in San Francisco the packet is destined for. Having to store that information would make the sorting process unworkable.
Route Summarization Pre-requisites
In order to use route summarization on your network you need to use a classless protocol such as RIPv2, EIGRP or OSPF. You also need to design your network in a hierarchical order which will require careful planning and design. This means that you can't randomly assign networks to various routers or LANs within your network.
See what I did there? I cleverly used the example of letters and will now apply it to IP routes. Well, in fact I think I have made my point so I won't labour the point. Let's move onto an example of a network and what the problem will look like on your network if you don't use route summarization.
Here is an example of how summarization would work with a range of IP addresses on a network.
The router has several networks attached. The first choice is to advertise all of these networks to the next hop router. The alternative is to summarize these eight networks down into one route and send that summary to the next hop router which will cut down on bandwidth, CPU and memory requirements.
You can only really work out a summary route by converting the IP address into binary (sorry). If you don't do this then you have no way of knowing if you are advertising the correct summary route which will lead to problems on your network.
Firstly, write out all of the network addresses in full and then the binary versions to the right of that.
I have italicised the bits in each address which match. You can see that the first 21 bits match on every address so your summarized route can reflect these 21 bits:
One other significant advantage of using route summarization is that if a local network on your router goes down, the summary network still be advertised out. This means that the rest of the network will not need to update its routing tables or worse still, have to deal with a flapping route.
Please write out the binary equivalents for the below addresses and then determine which bits match. I have written the first two octets for you to save time.
What summarized address would you advertise?
I make it 172.16.0.0 255.255.128.0 or /17
The below company has three routers connecting to their HQ router. They need to summarize the routes advertised from London 1, 2 and 3.
Let's start with London 1.
We have 21 common bits so London 1 can advertise 10.1.0.0 /21 to HQ router.
And for London 2.
London 2 also has 21 common bits so can advertise 10.1.8.0 /21 to the HQ router.
And onto London 3.
London 3 has 21 common bits also we can advertise 10.1.16.0 upstream to HQ router.
You will be expected to understand route summarization for the CCNA exam. If you can quickly work out the common bits then you should be able to answer the question quickly and accurately. If you want to read up to learn more about route summarization then please get yourself a copy of Jeff Doyles book Routing TCP/IP Vol 1 2nd Edition.
Here is the answer to Exercise 1: