Since network technicians work with IP addressing, it is hugely important to understand subnetting. I remember back when I started to learn subnetting it was confusing and I wanted nothing to do with it. The thing that made me change my mind was after I understood it and how important it is. In the “Cisco world” they don’t cover useless topics, there is always a reason why they expect you to know this and it’s not just for the exams. Subnetting has always had its moments with people and in this blog I’ll do my best to show you what I have done to make subnetting an easier experience.
Eons ago I talked about “The Wonders of Binary” which talked about how to convert these ones and zeros into decimal value and is another stepping stone into understanding the subnet world. Let’s introduce the three classes of subnet masks that PCs can use:
Class A: 1-127 — Subnet Mask: 255.0.0.0
Class B: 128-191 Subnet Mask: 255.255.0.0
Class C: 192-223 Subnet Mask: 255.255.255.0
Do you get it? Let me explain what is going on, back when the internet was young and just started out we had three IP classes you could use. These classes would be handed out depending on the size of the organization. Usually universities would get a Class B address range, big companies like GE received a class A address. The problem with this is it’s a waste of addresses when would you ever have 65,534 (Class B) or 16,277,214 (Class A) computers on the same network? Nothing would work!
What could I do to break this down into separate networks? That’s where subnetting comes into play, if I had class B address range I could break it up into smaller networks, watch and be amazed.
Let’s say my class B range is 126.96.36.199 – 188.8.131.52 in this range I have one network so I could have 65,534 computers connected to this. We already said this is stupid setup because nothing would be able talk because this network would be over saturated, remember computers are chatty fellows even when you don’t use them.
But what I could do is break this address into smaller ranges, instead of one big network I could break it into a Class C address. See if you follow this:
184.108.40.206 – 220.127.116.11 –Subnet 255.255.255.0
18.104.22.168 – 22.214.171.124 – Subnet 255.255.255.0
126.96.36.199 – 188.8.131.52 – Subnet 255.255.255.0
184.108.40.206 – 220.127.116.11 – Subnet 255.255.255.0
18.104.22.168 – 22.214.171.124 –Subnet 255.255.255.0
So what did I just do? Just what I said I would do I broke up this network into smaller networks, so how many networks do I have now? Well instead of one big network I now have 256 smaller networks with each network able to handle 254 computers. Real world example is if this was a campus environment each building can have its own network. Building A can have the 126.96.36.199 network, building B can have the 188.8.131.52 network, etc.
This makes the network scalable and way easier to manage, and that’s the basics of how subnetting works, for now remember you can always take a bigger subnet and break it down into smaller ones. It is a little tricky to take small subnets and expand them but remember it can be done with something called VLSM and if you designed your network scheme correctly :). Also check out this subnetting workbook which will help you to continue to practice subnetting, there are easier ways to get the answers but you have to start at the beginning and really have an understanding of it, once you got it you’ll find the shortcuts :cool:.
I have used this exact one when I was studying subnetting, try it out and if you have questions feel free to post them. Also if you have other ideas of the next topic I should cover that deals with ICND1 or ICND2 let me know. As always I hope this information is helpful and since this is part 1 of subnetting check back often see if I posted part 2 which will deal with VLSM.
- Configure Router on a Stick (ciscoskills.net)
- Network Subnetting (computrnetworking.wordpress.com)
- Stretched Layer-2 Subnets – The Server Engineer Perspective (ioshints.info)