Day 6: IPv4 Deep Dive – Mastering VLSM & Troubleshooting

Welcome to Day 6 of your CCNA journey.

Yesterday, we learned the “Magic Number” to chop a network into equal-sized pieces (Subnetting). But in the real world, networks are rarely equal.

Imagine you have a Main Office with 50 users, a Branch Office with 10 users, and a WAN link connecting them that needs only 2 IPs. If you used yesterday’s method (FLSM – Fixed Length Subnet Masking) and gave everyone a /26 (64 IPs), you would waste massive amounts of addresses on the Branch and WAN links.

Enter VLSM (Variable Length Subnet Masking). VLSM allows us to “subnet the subnet.” We can assign a /26 to the main office, a /28 to the branch, and a /30 to the WAN link, fitting everything perfectly like a game of Tetris.

This guide covers CCNA Exam Topic 1.6 (VLSM) and Topic 1.10 (Identify IP parameters on Client OS). We will master the “Largest to Smallest” rule and then jump into the command line to fix broken PCs.

The Golden Rule of VLSM

There is only one rule you need to follow to solve any VLSM question on the exam:

ALWAYS subnet for the largest requirement FIRST.

If you try to assign the small networks first, you will fragment your address space and run out of room for the big networks.

The Scenario

You are given the network 192.168.1.0/24 (256 Total IPs). You need to create subnets for:

1. Sales Dept: 100 Hosts
2. IT Dept: 50 Hosts
3. WAN Link A: 2 Hosts

Step-by-Step VLSM Walkthrough

Let’s apply the rule. We start with the largest need: Sales (100 Hosts).

Step 1: The Sales Subnet (100 Hosts)

• Requirement: 100 IPs.
• Powers of 2: Which block size fits 100?
  • 64 is too small.
  • 128 is perfect (/25).
• Action: We take the first block of 128.
  • Network: 192.168.1.0
  • Mask: /25 (255.255.255.128)
  • Range: .0 to .127
  • Broadcast: .127

Status: We have used 0 - 127. The next available IP is .128.

Step 2: The IT Subnet (50 Hosts)

• Start Point: 192.168.1.128 (This is where we left off).
• Requirement: 50 IPs.
• Powers of 2: Which block size fits 50?
  • 32 is too small.
  • 64 is perfect (/26).
• Action: We take a block of 64 starting at .128.
  • Network: 192.168.1.128
  • Mask: /26 (255.255.255.192)
  • Range: .128 to .191 (128 + 64 = 192, so we stop at 191).
  • Broadcast: .191

Status: We have used 0 - 191. The next available IP is .192.

Step 3: The WAN Link (2 Hosts)

• Start Point: 192.168.1.192.
• Requirement: 2 IPs.
• Powers of 2:
  • 4 is the minimum block size (/30). (Remember: Network + Broadcast + 2 Hosts = 4).
• Action: We take a block of 4 starting at .192.
  • Network: 192.168.1.192
  • Mask: /30 (255.255.255.252)
  • Range: .192 to .195 (Usable: .193 and .194).
  • Broadcast: .195

Final Tally: We fit all three networks into a single /24, and we still have space left over (from .196 to .255) for future growth. That is the power of VLSM.

Identifying IP Parameters (Windows, Mac, Linux)

Topic 1.10 asks you to “Identify IP parameters on Client OS.” You need to know how to find the IP, Subnet Mask, Gateway, and DNS on a computer, and what it means if they are wrong.

Windows Command Line

• Command:ipconfig
  • Shows: IP Address, Subnet Mask, Default Gateway.
• Command:ipconfig /all
  • Shows: MAC Address (Physical Address), DHCP Server, DNS Server, Lease Time.
• Command:ping
  • Tests connectivity.
• Command:tracert
  • Traces the path (hops) to a destination. Note: Windows uses ICMP for this.

Linux / macOS Terminal

• Command:ifconfig (Legacy) or ip addr (Modern Linux)
  • Shows interface details. Look for inet (IPv4) and ether (MAC).
• Command:traceroute
  • Note the spelling difference from Windows (tracert vs traceroute). Linux often uses UDP ports for tracing by default.

Troubleshooting Common IP Issues

The exam will present you with a screenshot of ipconfig and a problem description. You must deduce the error.

Scenario A: The “Duplicate IP” Error

• Symptom: User gets a pop-up saying “IP Address Conflict.” Network connectivity is intermittent.
• Cause: Two devices have the same static IP.
• Fix: Change one device to DHCP or a unique Static IP.

Scenario B: “I can print, but I can’t browse the web.”

• Analysis:
  • The printer is local (LAN). The web is remote (WAN).
  • LAN works = IP and Mask are correct.
  • WAN fails = Default Gateway is wrong or down.
• Troubleshooting Steps:
  1. ping 127.0.0.1 (Check NIC driver).
  2. ping (Check connection to router).
  3. If Gateway ping works, but internet fails, check Route or NAT.

Scenario C: “I can ping 8.8.8.8, but I can’t load https://www.google.com/search?q=Google.com“

• Analysis:
  • IP connectivity works (Ping to IP succeeds).
  • Name resolution fails.
• Cause: DNS Server issue. The PC has the wrong DNS IP, or the DNS server is down.
• Fix: Check ipconfig /all to see the DNS server. Try changing it to a public DNS (e.g., 1.1.1.1).

Scenario D: The “169.254” Address

• Symptom: User has IP 169.254.x.x. No connectivity.
• Cause: APIPA. The computer requested an IP from DHCP, but no server replied.
• Fix: Check the cable connectivity to the DHCP server or restart the DHCP service.

Precision Matters

To pass Topic 1.6 (VLSM) and 1.10 (Troubleshooting), remember:

1. VLSM: Largest to Smallest. Always.
2. Windows: ipconfig, tracert.
3. Linux: ifconfig, traceroute.
4. Gateway: If you can’t leave the LAN, check the Gateway.
5. DNS: If you can ping numbers but not names, check DNS.

Author’s Note: This guide is strictly aligned with Cisco CCNA 200-301 Exam Topics 1.6 and 1.10. Don’t let VLSM scare you; it’s just efficient packing!