11.7.5 Packet Tracer - Subnetting Scenario

When you open the 11.7.5 packet tracer - subnetting scenario, the first thing that hits you is a tidy topology waiting to be sliced into subnets. You stare at a handful of routers, a couple of switches, and a mess of unassigned IP addresses, and you wonder where to even begin. It’s the kind of moment that makes you question whether you really understand subnetting or if you’re just memorizing formulas. The good news? Here's the thing — this scenario was built to force you into the messy middle of network design, where theory meets a blinking cursor and a handful of green cables. By the time you finish, you’ll have walked through a complete subnetting exercise, made real‑world decisions about address planning, and learned a few tricks that most tutorials leave out.

What Is 11.7.5 Packet Tracer Subnetting Scenario

The Lab Setup

The environment is deliberately simple: three routers, two switches, and a set of end‑device PCs. Each router represents a different branch office, and the switches act as distribution points. No VLANs, no advanced routing protocols—just basic IPv4 addressing and static routes. The goal is to allocate subnets that satisfy a list of requirements, such as providing enough host addresses for each department while keeping the number of subnets manageable Surprisingly effective..

Key Concepts You’ll Use

You’ll be juggling CIDR notation, calculating subnet masks, and deciding where to place the gateway address. You’ll also be using Packet Tracer’s addressing table, the simulation mode, and the built‑in ping utility to verify your work. All of these tools are there to help you see the impact of each decision in real time, rather than relying on mental math alone.

Why This Scenario Matters in Real Networks

Bridging Theory and Practice

Most textbooks walk you through subnetting with static examples that never change. The 11.7.5 packet tracer - subnetting scenario flips the script by adding constraints: a limited address pool, a requirement to keep certain subnets contiguous, and a need to minimize the number of routing entries. Those constraints mimic what you’ll face when designing a corporate LAN or a campus network, where every IP address is precious and every routing decision has consequences Not complicated — just consistent..

What Happens When You Get It Wrong

If you miscalculate a mask, you might end up with overlapping subnets, which can cause traffic to be routed to the wrong destination or, worse, be dropped entirely. A common symptom is a PC that can ping the router but cannot reach any other subnet. Spotting that symptom early is a skill that translates directly to troubleshooting real networks, where a single mis‑placed bit can bring an entire department offline.

How to Build the Subnet in Packet Tracer

Step 1: Plan Your Address Space

Before you click a single

Step 1: Plan Your Address Space

Begin by selecting a single classful block that can be carved into the required pieces. In this lab the instructor has reserved the 10.0.0.0/8 range, which gives you 16 million possible hosts. Because the scenario limits you to three sites and two distribution switches, you’ll need only a handful of subnets, but you must still respect the “no‑overlap” rule and keep the number of routing entries low.

First, decide how many hosts each department will need. A typical breakdown might look like this:

The total number of subnets is therefore four, which comfortably fits within a /22 mask (256 addresses per subnet). Using a /22 gives you 256 addresses per subnet, enough room for growth while keeping the count of subnets manageable And it works..

Step 2: Derive the Subnet Mask

A /22 network has a binary mask of 11111111.11111111.11111111.11000000, which translates to 255.255.255.192 in decimal. This mask yields:

• Network address: the first address of each block (e.g., 10.0.0.0, 10.0.0.128, 10.0.0.192, 10.0.0.256‑but the last exceeds the /8 boundary, so we stay within 10.0.0.0‑10.0.0.255).
• Broadcast address: the last address of each block (e.g., 10.0.0.191).
• Usable hosts: 191 – 2 = 189 per subnet, more than enough for any of the departments listed.

If you need tighter control, you could carve the /8 into four /22s and then further subdivide each /22 into smaller /26 or /27 blocks, but that would increase the routing table size—something the scenario explicitly asks you to avoid.

Step 3: Map Subnets to Physical Locations

Now translate the mathematical blocks into the physical topology:

Step 4: Assign IP Addresses to End‑Devices

With the subnets locked in, the next logical phase is to populate each device with a usable address that respects the hierarchy you just created.

Repeat the same pattern for the other VLANs: Engineering uses 10.0.Still, 192/27, and the Guest Wi‑Fi pool lives in 10. 0.224/27. 0.Because of that, 128/26 (or /27 if you decide to split it further), HR occupies 10. 0.Still, 0. That said, 0. Remember to leave a few addresses untouched for future expansion or for devices such as DHCP scopes, NTP servers, or management consoles.

Step 5: Configure Inter‑VLAN Routing on the Layer‑3 Switch

Because the topology includes two distribution switches that each host multiple VLANs, you’ll enable routing on the switch that connects the two routers (or on a dedicated multilayer switch if one is available). The steps are:

1. Create VLANs on both switches, matching the departmental VLAN IDs you used in the addressing plan.
2. Assign switch‑port VLAN membership to the appropriate access ports.
3. Configure a Switched Virtual Interface (SVI) for each VLAN, entering the corresponding network address and mask.
   • Example for Sales VLAN on Switch A: interface Vlan10 → ip address 10.0.0.1 255.255.255.192
4. Enable IP routing (ip routing global command).
5. Verify with a show ip route that the router‑connected networks appear in the routing table, and that the switch can forward packets between VLANs without involving the external routers.

If you are using separate routers for each site, you can instead configure sub‑interfaces on the router’s LAN port, each tagged with the appropriate VLAN ID, and assign them the same gateway addresses you used on the SVIs. This approach mirrors real‑world deployments where a single router terminates multiple VLANs from different switches.

Step 6: Test Connectivity and Troubleshoot Common Pitfalls

Once the addressing and routing are in place, run a series of verification commands to confirm that every segment can talk to every other segment:

• From a host: ping 10.0.0.1 (gateway) → should succeed.
• From a host in Sales to a host in Engineering: ping 10.0.0.130 → should succeed if the routing table shows a valid entry.
• On the switch: show ip interface brief → confirms that each SVI is up and has the correct address.
• On the router: show ip route → verifies that the connected networks are listed with the correct administrative distance.

If a ping fails, check the following in order:

1. Cable/VLAN mismatch – ensure the host’s access port is in the correct VLAN.
2. SVI status – a down SVI will block routing; bring it up with no shutdown.
3. Subnet overlap – double‑check that you didn’t accidentally reuse an address block.
4. Default gateway – a mis‑typed gateway will isolate the host from the rest of the network.

Document any errors you encounter; they become valuable reference points when you later troubleshoot a live corporate network where a single misplaced bit can take an entire department offline Small thing, real impact..

Step 7: Optimize and Document

The final polish involves two often‑overlooked tasks:

• Route summarization – If you later add more sites, you can collapse adjacent /22 blocks into a larger summary (e.g., 10.0.0.0/21) to keep the routing table compact.
• Documentation – Export the topology diagram, the addressing table, and the configuration snippets into a lab report. Include a “lessons learned” section that notes where you had to adjust masks or VLAN IDs to meet the instructor’s constraints.

Conclusion

By methodically planning the address space, deriving an appropriate mask, mapping subnets to physical locations, assigning host addresses,

Conclusion

By methodically planning the address space, deriving an appropriate mask, mapping subnets to physical locations, assigning host addresses, and then configuring the SVIs, router sub‑interfaces, and verifying connectivity, you have built a scalable, multi‑site LAN that mirrors real‑world enterprise designs. The process underscores the importance of a disciplined approach: start with a clear addressing plan, enforce consistency across VLANs, and validate each step with targeted show commands and ping tests.

When a ping fails, the systematic troubleshooting checklist—cable/VLAN verification, SVI status, subnet overlap, and default‑gateway accuracy—provides a rapid path back to stability. Likewise, route summarization and thorough documentation turn a lab exercise into a reusable blueprint for larger deployments, ensuring that future expansions can be integrated without introducing hidden conflicts Practical, not theoretical..

In practice, the ability to design, implement, and validate a multi‑VLAN, multi‑router environment is a cornerstone skill for any network engineer. Mastery of these fundamentals not only prepares you for certification labs but also equips you to handle the complexity of real corporate networks where a single mis‑configured VLAN can disrupt entire departments. Keep refining your design habits, automate your documentation, and you’ll be ready to tackle increasingly sophisticated network architectures Less friction, more output..