In this Cisco CCNA tutorial, you’re going to learn about CIDR, which is classless inter-domain routing. Scroll down for the video and text tutorial.
CIDR Classless Inter-Domain Routing Video Tutorial
I love the way the resources are laid out for us and I can already tell I’m going to learn a lot. Very excited to be studying for my CCNA with Neil.
A problem with the original implementation of the classful addresses was that when the internet authorities give out addresses, they always give out complete:
- Class A with a /8 subnet mask
- Class B with a /16 subnet mask
- Class C with a /24 subnet mask
This gave a problem that if a company had more than 254 hosts, let’s say 500 hosts, is too big for a class C. So, they would be given a class B and they would get allocated addresses for 65,534 hosts.
That's way too much and this led to huge amounts of the global address space being wasted. As a solution, classless inter-domain routing or CIDR was introduced in 1993.
CIDR removed the fixed /8, /16, and /24 requirements for the different address classes and allowed them to be split in smaller networks called subnetting.
For example, the internet authorities could allocate the address, 18.104.22.168 /20. The first octet, 175, is a class B address which would normally be /16. Rather than allocating the entire /16, the internet authorities could now assign /20 which means the other networks in the 175 range would be available to give to other companies.
Rather than giving a huge range, we split the classes into smaller networks that could be given to different organizations. Companies can now be allocated in an address range that matches what they need, therefore, there would be fewer addresses getting wasted.
CIDR and Route Summarization
Route summarization is another benefit of CIDR. In the example below, we've got ISP A and they have allocated the address blocks that you see on the left. One company got 22.214.171.124 /24, another one got 126.96.36.199 /24, one got 188.8.131.52 /24, all the way up to 184.108.40.206 /24. ISP A has given out 255 address blocks.
We've also got ISP B and they've given out 220.127.116.11 /24, 18.104.22.168 /24, and so on, all the way up to 22.214.171.124 /24. ISP A and ISP B get connected.
If we didn't have CIDR and route summarization, ISP A would advertise all of its 256 address blocks to ISP B and vice versa. But when we've got CIDR and route summarization, the two ISPs can advertise just an aggregate block.
Rather than advertising all 256 /24s, ISP A advertises 126.96.36.199 /16 which is a superset of all those 256 smaller networks. ISP B then learns one route to all the networks behind ISP A, rather than learning 256 routes. ISP B will similarly advertise one route of 188.8.131.52 /16 to ISP A.
Route Summarization Benefits
The benefits we get from route summarization is that ISP A doesn't know about all 256 networks behind ISP B. It only gets a single summary route that covers all of them.
One route compared to 256 routes, is a lot less information, more efficient, and it takes up less memory in the router. If an individual link goes down in ISP B, it doesn't have any impact on ISP A because that one summary route doesn't change.
It's going to be different in ISP B though. Whenever one of their routes goes down, the other routers are going to have to recalculate that.
The benefit we get from this is we're compartmentalizing the different parts of our network. If we've got an issue in ISP A of the network, it's not going to impact ISP B. It makes things a lot more stable and reliable. It also makes things more logical, which is better for us humans because it makes it easier to troubleshoot related problems.
Understanding CIDR Subnet Mask Notation: https://docs.netgate.com/pfsense/en/latest/book/network/understanding-cidr-subnet-mask-notation.html
Classless Inter-domain Routing (CIDR): The Internet Address Assignment and Aggregation Plan: https://tools.ietf.org/html/rfc4632
IP Addressing and Subnetting for New Users: https://www.cisco.com/c/en/us/support/docs/ip/routing-information-protocol-rip/13788-3.html
Text by Libby Teofilo, Technical Writer at www.flackbox.com
With a mission to spread network awareness through writing, Libby consistently immerses herself into the unrelenting process of knowledge acquisition and dissemination. If not engrossed in technology, you might see her with a book in one hand and a coffee in the other.