Have you considered the operational view versus design view of subnetting yet?
Imagine you’ve gone to the beach with a team of friends and each person has been charged with building a sand castle or an object from sand, perhaps you may say, what has this got to do with Introduction to Subnetting from the Perspective of Design and Operation, well it does indeed have everything to do with it. The beach has an endless heap of sand readily available to your use and the weather is fantastic. You go on a nice trip to work on sand projects with the aim to create a competition amongst some friends.
Now each member of the team has been given a container to fill up with sand for their object but you have been delegated as the person responsible for giving the right amount to each individual for their selected objects based on the sizes chosen.
John has chosen to create a full size motorcycle, Jenny has chosen to create a mouse, Rebecca has chosen to create her pet dog, Kwabena has chosen to create a joystick and then the twins have decided to become the Wright brothers, you guessed it, they are creating an aircraft. Knowing the estimated sizes of their objects, you have provided each one a container to work within and have started to heap the sand for each of them.
Before undertaking a task as per the above scenario, what do you personally think should be his approach so no one is deficient of sand enough to cater for their sand objects?
Let us consider the following key points;
- Analyse Needs
- Choose Size Requirements (Sand)
- Plan how to apportion the Sand.
A big question to ask is this, will you give Jenny the same amount of sand as the Twins who wants to create a full sized aircraft? The answer is obvious, No! Someone may argue that this is a competition and so it does not matter, give them all the same portion and let them get on with it. This is not the best mindset as this will only incur waste.
So the best thing to do is measure a quantity equivalent or just slightly over the size of the object they are about to create so there is enough room for the creation of the object and any unforseeable adjustments they might need.
Translate our beach creation to the world of subnetting from the perspective of design and operation.
Consider the following diagram – Figure 1.0
Subnet Design: Class B 172.16.0.0 | First 3 Octets are Equal. | Figure 1.0 is our Sample Subnet Plan Document
In the design above, the entire network design depicts 5 separate networks broken down into three LANs and one each for the WAN links. Each subnet has the same value in the first 3 octets. For example, for the LAN on the left, the number shows 172.16.1._ meaning all addresses that begin with 172.16.1. Since this is a class B network and not all the subnets have been used, there is a great deal of room for improvement.
The skill of subnetting in designing is crucial for the network engineer. Do note that most times the role you take would have had some engineers beforehand who would have designed the network and planned the subnets before you arrived there. The concept is still very essential for you as will need to interpret what someone before you has already chosen. To completely grasp IP addressing and subnetting, you need to have a mindset from the perspective of design and operation. In our earlier example of Figure 1.0, I mentioned that the Subnet Design states that the first three octets of all the subnets were equal. A question you may ask is why was this convention chosen? Could there not have been any alternatives? Would the alternatives be better for the network today. As you can see, subnetting require a great deal of planned design rather than to operation. Let’s consider the following flow;
Figure 1.1
Analyse Needs
- Number of Subnets
- Number of Hosts per Subnet
- Size of Subnet
Design Subnets
- Choose Network
- Choose 1 Mask
- List all Subnets
Plan Implementation
- Subnets and their Locations
- Static IP
- DHCP Ranges
Let us break these down so we can have a deeper understanding of what needs doing.
Analyse Subnetting and Addressing Needs
- Which hosts should be grouped together into a subnet?
- How many sunbets does this network require?
- How many host IP addresses does each subnet require?
- Will we use a single subnet size for simplicity, or not?
Figure 1.2
Rules to consider for devices in each subnet
Every device that connects to an IP internetwork needs to have an IP address in order to do so. These devices include printers,IP phones, servers, mobile phones, tablets and end devices used by users. Major network devices like routers, switches, and firewalls must also have IP’s in order to internetwork.
Figure 1.3 – Identifying the Subnets
IP addresses must be assigned according to some fundamental rules and for for good reasons. To make routing work efficiently, IP addressing rules group addresses into groups called subnets. The rules are as follows:
Addresses in the same subnet are not separated by a router – look at figure 2.1
Addresses in different subnets are separated by at least one router – look at figure 2.2
Notice that PC A and B are in one subnet and PC C is in another subnet. For PC A to speak with PC C, at least one router (R1) would be required.
Determine the Number of Subnets
You would be given a document detailing the entire detail of your organisation’s internetwork. Once you have been given this document start applying the rules.
Consider the following:
Network Diagrams
VLAN configuration details
WAN technology used( MPLS, Frame-Relay, VPLS, Metronet, etc) Based on this information, use the above rules and plan one subnet for every;
- VLAN
- Point-to-point Serial link
- Ethernet emulation WAN link (EoMPLS)
- Frame Relay PVC.
In the above diagram, there is a clear indication of expected hosts per subnet and so it makes out design and implemention of a subnet scheme a little less daunting. I will be going through a simple method in performing subnetting in another article. Look out for more and You might also enjoy reading my article on Inter-VLAN Routing.
Good Resource for Further Study:
Get more advanced in-depth knowledge in Routing and Switching from the world’s most renown author in Networking.