0% found this document useful (0 votes)
60 views22 pages

VLSM Subnetting Explained with Examples

VLSM subnetting allows for variable subnet sizes to best utilize IP address space. It is more complex than FLSM but can minimize wasted addresses. In this example network, VLSM is used to subnet the 192.168.1.0/24 network into variable sized subnets to support the development department with 74 hosts, production with 52 hosts, administration with 28 hosts, and 3 WAN links. Block sizes are assigned to each segment based on host requirements, and subnets of the appropriate size are selected through iterative subnetting to match each segment's needs.
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
60 views22 pages

VLSM Subnetting Explained with Examples

VLSM subnetting allows for variable subnet sizes to best utilize IP address space. It is more complex than FLSM but can minimize wasted addresses. In this example network, VLSM is used to subnet the 192.168.1.0/24 network into variable sized subnets to support the development department with 74 hosts, production with 52 hosts, administration with 28 hosts, and 3 WAN links. Block sizes are assigned to each segment based on host requirements, and subnets of the appropriate size are selected through iterative subnetting to match each segment's needs.
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd

CHAPTER Three

VLSM Subnetting-part-2
Cont’
• Which Subnetting should be used is depend on objectives and
type of addresses used in network.
FLSM provides easier Subnetting at the cost of IP addresses
while VLSM best utilizes IP addresses at the cost of simplicity.
For private IP addresses, FLSM is the best choice. For public IP
addresses, VLSM is the best option.

2
VLSM Sub-netting
• VLSM (Variable Length Subnet Masks) Sub-netting.
Subnets are variable in size.
Subnets have variable number of hosts.
Subnets use different subnet masks.
It is complex in configuration and administration.
It wastes minimum IP addresses.
It is also known as classless Subnetting.
It supports only classless routing protocols.

3
VLSM Example
• Do the VLSM Subnetting of following network.

4
Solution
• In this network: -
Development department has 74 computers.
Production department has 52 computers.
Administration department has 28 computers.
All departments are connected with each other via wan links.
Each wan link requires two IP addresses.
The given address space is [Link]/24.
• Before we perform VLSM Subnetting for this network, let’s
understand how VLSM Subnetting actually works.

5
Con’t
• Basic concepts of VLSM Subnetting
Select block size for each segment.
 Block size must be greater than or equal to the actual requirement.
 Actual requirement is the sum of host addresses, network address and broadcast address.
Based on block size arrange all segments in descending order.
Do FLSM Subnetting for the block size of the first segment.
Assign first subnet from subnetted subnets to the first segment.
If next segment has similar block size, assign next subnet to it.
If next segment has lower block size, do FLSM Subnetting again for the block size of this
segment.
From subnetted subnets exclude the occupied subnets. Occupied subnets are the subnets
which provide the addresses which are already assigned.
From available subnets, assign the first available subnet to this segment.
Repeat above steps till the last segment of the network.
• Let’s implement above steps in our example network.
6
Step by step VLSM Subnetting
• The first step of VLSM Subnetting is selecting the appropriate block
size for each segment.
• While selecting appropriate block size for a given segment, always select a
size which is adequate for host addresses plus two additional addresses;
network address and broadcast address.
• Regardless the information about these two addresses is provided or not in
question; always add these addresses in requirement while selecting the block
size for a segment.

• Actual requirement = Host requirement + Network address + broadcast


• Address Block Size >= Actual requirement

7
Cont’
• The following table shows the selection of block size in our example.

8
Cont’
• The next step of VLSM Sub-netting is arranging segments in descending order.
Based on block size, following table arranges all segments in descending order.

9
Con’t
• The next step of VLSM Subnetting is doing FLSM Subnetting and selecting appropriate subnets
for segments from the subnetted subnets.
• First largest segment (Block size 128)
 Our first segment needs a block size of 128. The FLSM Subnetting of /25 provides us two subnets with
the block size 128.
 FLSM Subnetting of [Link]/25

10
Con’t
• From Subnetted subnets assign first subnet to this segment.

11
Con’t
• Since our second segment (Production) needs different block size (64), instead of using second
subnet (Subnet2) for it, let’s do Subnetting again.
• Second largest segment (Block size 64)
• The Subnetting of /26 provide us 4 subnets with block size 64.
• Sub-netting of [Link]/26

12
Con’t
• From this Subnetting, we cannot use subnet 1 and subnet 2 as they are already occupied.
• Subnet 1 and Subnet 2 provide addresses from 0 to 127 which are already assigned in the development
department.
• We can use subnet 3 for this segment (production).

13
Con’t
• Third largest segment (block size 32)
• The Subnetting of /27 provides us 8 network and 32 hosts.
• Subnetting of [Link]/27

14
Con’t
• Exclude the already occupied subnets (Sub1 to Sub6) and assign the
first available subnet (Sub7) to this segment.

15
Con’t
• WAN Links (Block Size 4)
• Last three segments require the block size of 4. The Subnetting of /30 gives us 64 subnets of
block size 4.
• Subnets of /30 Subnetting:-
0, 4, 8, 12, 16, 20, 24, 28, 32, 36, 40, 44, 48, 52, 56, 60, 64, 68, 72, 76, 80, 84, 88, 92, 96, 100,
104, 108, 112, 116, 120, 124, 128, 132, 136, 140, 144, 148, 152, 156, 160, 164, 168, 172, 176,
180, 184, 188, 192, 196, 200, 204, 208, 212, 216, 220, 224, 228, 232, 236, 240, 244, 248, 252,
256
• Exclude already occupied subnets (0-56) and use first three available subnets 57,
58 and 59 for WAN links.

16
Con’t

17
Con’t
• Assign subnet 57 to the WAN link 1.

18
Con’t
• Assign subnet 58 to the WAN link 2.

19
Con’t
• Assign subnet 59 to the WAN link 3.

20
Con’t
• We have assigned IP addresses to all segments. The subnets 60, 61, 62,
63 and 64 are still available for further use.

21
Thank you!!
22

Common questions

Powered by AI

Excluding already assigned subnets during VLSM allocation is crucial to prevent IP address conflicts and ensure unique address allocation across the network. This is particularly important in complex networks where the risk of overlap is higher due to numerous varying segment requirements. By carefully tracking and excluding occupied subnets, network integrity is maintained, eliminating potential connectivity issues and ensuring efficient routing within the network .

Arranging segments by block size in descending order is crucial in VLSM subnetting to ensure that the largest networks receive suitable subnet sizes first, thus preventing wastage of IP addresses. By prioritizing the largest segment, the block size needed for all subsequent segments can be determined more efficiently, allowing for precise subnet allocation without over-provisioning. This process reduces the chance of exhausting larger subnet resources on smaller segments and maintains a pool of optimal-sized subnets for future segments, enhancing overall network address allocation .

In VLSM, FLSM is used for segment allocation by first determining the largest required block size for initial subnetting, then subsequently allocating from the subnets created using FLSM to match specific segment needs . Starting with FLSM for the largest segment ensures maximization of available address space where it is most needed, and subsequent segment allocations can be made more efficiently by recalculating and using smaller blocks appropriately. This strategy results in optimal IP address usage and reduces rate of address wastage .

VLSM supports classless routing protocols by allowing subnets with different sizes, which are defined by variable length subnet masks. Classless protocols, such as OSPF, BGP, or EIGRP, can manage these varying-sized subnets efficiently because they consider the subnet mask information during routing, providing more precise routing decisions. In contrast, classful protocols do not use subnet mask information, thus would be unable to handle the variable-size subnets that result from VLSM, making them incompatible for such networks .

In VLSM, the block size for each segment must equal or exceed the sum of the host requirement plus two additional addresses (network and broadcast addresses). This differs from FLSM calculations where a fixed block size is used regardless of the specific needs of individual segments, often leading to inefficient IP use. The implication is that VLSM's requirement-based block sizing allows for more precise allocation of IPs, reducing wastage and supporting more tailored network designs, whereas FLSM could result in significant address underutilization .

Network administrators might prefer VLSM for public IP addresses because it allows for flexible subnetting to minimize IP wastage and optimize address usage, which is critical when dealing with the limited public IP space . Conversely, FLSM might be chosen for private IP addresses because it offers simplicity in subnetting and management, which is often more critical in internally managed networks where IP address space is not as constrained, hence allowing for easier organization even if it means some IP wastage .

VLSM configuration presents challenges in terms of management due to its complexity in planning and execution, as it requires an accurate assessment of network needs and careful allocation of subnets to avoid waste and overlap. Additionally, VLSM requires only classless routing protocols, which can add further complexity as these protocols must support variable length subnet masks to ensure proper routing of IP packets across different subnets . This complexity in administration and the necessity to use specific routing protocols make VLSM challenging for network managers.

The primary advantage of using VLSM (Variable Length Subnet Masks) over FLSM (Fixed Length Subnet Masks) is its ability to more efficiently utilize IP addresses by allowing subnets of varying sizes, which minimizes wasted IP addresses . In network design, this advantage means that VLSM can be used to tailor the number of available IPs in each subnet to match specific requirements, leading to better address space utilization. While VLSM offers flexibility and efficiency, it also adds complexity to the configuration and administration, which must be managed carefully .

Key steps in implementing VLSM subnetting include: selecting appropriate block sizes for each segment, arranging segments in descending order based on block size, performing FLSM subnetting to create variable-sized subnets, assigning the subnets, and excluding occupied subnets from future assignments. Each step is significant because it ensures that the correct number of IPs are allocated to meet specific network requirements, prevents wastage of IP addresses by fitting subnets to the requirement exactly, and maintains a structured approach to address allocation, thus simplifying the complex process of VLSM subnetting .

Performing VLSM subnetting early in network design is critical to ensure that IP addresses are allocated in a manner that efficiently meets the network's immediate and future needs. Early planning allows for optimal address utilization and avoids bottlenecks caused by IP shortages. Delaying this process could lead to inefficient IP usage and increased operational complexity as the network grows, potentially resulting in address exhaustion, increased costs for reconfiguration, and operational disruptions .

You might also like