VLSM: Critiquing Allocation & Calculating Savings

1. The Core Problem: Wasted Address Space

The fundamental goal of an efficient IP plan is to allocate just enough addresses for a given network segment's current and future needs, without being wasteful. Using subnets that are too large is a common mistake, especially in legacy designs.

A classic example is using a large subnet for a simple point-to-point link between two routers.

This problem arises from using a Fixed-Length Subnet Mask (FLSM), where every subnet in a network is the same size. The solution is Variable-Length Subnet Masking (VLSM), which allows you to use different subnet mask sizes for different segments within the same parent network. This lets you "right-size" each subnet.

Let's read a formal definition to solidify this concept.

2. Case Study: Critiquing an Inefficient Plan

Now let's apply this concept to the "Cisco Jedi" case study you analyzed previously. The article provides a perfect "before and after" scenario for critiquing efficiency.

Let's break down the critique and calculate the potential savings.

The Inefficient Plan:

• Allocation: Each retail store is given two separate /24 subnets (one for data, one for voice).
• Total Addresses Allocated per Store: A /24 subnet has 256 total addresses (254 usable). So, 2 * 256 = 512 addresses are allocated to each store.

The Efficient VLSM Plan:

• Allocation: Each store is given a single /24 subnet, which is then subdivided using VLSM into four /26 subnets for different functions (POS, Wireless, VoIP, Corporate).
• Total Addresses Allocated per Store: A single /24 means only 256 total addresses are allocated.
• Breakdown: Each /26 subnet provides 64 addresses (62 usable), which is a much more reasonable size for these specific functions in a small retail store.

Calculating the Savings:

By switching from the inefficient plan to the efficient VLSM plan, the company saves:

512 addresses (inefficient) - 256 addresses (efficient) = 256 addresses saved PER STORE

Now, let's scale that across the entire retail network of 400 stores:

256 addresses/store * 400 stores = 102,400 addresses

This is a massive saving. The inefficient plan would have wasted over 100,000 IP addresses, potentially forcing the company to re-architect its entire IP scheme as it expands. This calculation demonstrates the profound impact of efficient VLSM design.

3. The Mechanics of Efficient VLSM Allocation

To design or critique effectively, you must understand the correct procedure for VLSM allocation. A key principle is to allocate subnets from largest to smallest. This prevents smaller subnets from getting "stranded" in address space that could have been used for a larger block, a problem known as fragmentation.

This video provides an excellent visual demonstration of this process.

4. A Critical Flaw: Detecting Overlapping Subnets

An address plan can seem efficient on the surface, but if its subnets overlap, it is fundamentally broken. Overlapping subnets mean that two different parts of your network are assigned the same range of IP addresses, which leads to routing failures and unpredictable connectivity issues. A critical part of any design critique is verifying that no overlaps exist.

There is a systematic process for finding these overlaps.

Practice: Find the Overlap

Let's apply this process. Imagine you are given a network design document with the following subnets. Is this design valid?

• 172.16.126.151/22
• 172.16.122.57/27
• 172.16.122.33/30
• 172.16.122.1/30
• 172.16.128.151/20

Follow the three-step process you just read about. Calculate the network and broadcast address for each, sort them, and check for overlaps.

5. Quantifying Efficiency: Address Utilization

The final step in our critique is to put a number on efficiency. We can do this by calculating the address utilization percentage. This metric tells you what percentage of the allocated addresses are actually being used (or are planned for use).

The formula is straightforward:

A good design aims for reasonable utilization while still leaving room for growth. Very low utilization (like < 20%) is a red flag for a wasteful allocation.

Let's apply this to our "Cisco Jedi" retail store example. Assume a store requires a total of 100 host addresses across all its functions.

• Inefficient Plan Utilization:

  • Required Hosts: 100
  • Allocated Usable Hosts: 508 (from two /24 subnets: 254 + 254)
  • Utilization = (100 / 508) * 100 ≈ 19.7%

• Efficient Plan Utilization:

  • Required Hosts: 100
  • Allocated Usable Hosts: 248 (from four /26 subnets: 4 * 62)
  • Utilization = (100 / 248) * 100 ≈ 40.3%

The calculation confirms our critique: the VLSM plan is more than twice as efficient in its address utilization for the same requirement. Professional IP Address Management (IPAM) documents, like the one shown in the "Addressing Plan Template" image, often track these metrics, including columns for immediate and projected future needs to ensure the allocated space is sufficient over time.

Conclusion

In this lesson, you graduated from simply identifying a network's design to critically evaluating its efficiency. You've learned that a good addressing plan is not just about connectivity; it's about the responsible and scalable management of a finite resource.

Key Takeaways:

• Critiquing efficiency involves comparing the number of required hosts against the number of allocated addresses in a subnet.
• VLSM is the primary technique for "right-sizing" subnets to match requirements and minimize IP address waste.
• The "largest-to-smallest" allocation method is a best practice that prevents address space fragmentation.
• An efficient design must be free of overlapping subnets. You learned a systematic process to detect these critical flaws.
• Address Utilization % is a key metric used to quantify the efficiency of an allocation plan.

Preview of the Next Lesson:

You have now analyzed a design's structure and critiqued its efficiency. The next layer of analysis involves security. In our next lesson, you will learn to identify security gaps or inefficiencies in a sample architecture's VLAN and ACL implementation. We will look for common vulnerabilities and design weaknesses that could expose the network to threats.