1.1 7 Lab Create Network Topologies: Exact Answer & Steps

Ever tried to sketch a network on a napkin, only to realize the lines don’t line up when you actually build it?
That moment of “my diagram looks clean but my lab is a mess” is why a solid topology‑building process matters. In the world of CCNA‑style labs, the “1.1‑7 Create Network Topologies” exercise is the classic first‑step that teaches you how to turn theory into a working packet‑tracer (or real‑equipment) layout Took long enough..

Below is the deep‑dive you’ve been looking for: what the 1.1‑7 lab really asks you to do, why it’s worth mastering, the step‑by‑step workflow, the pitfalls most beginners fall into, and a handful of practical tips that actually move you from “I can drag a router” to “I can design a scalable, error‑free network.”

What Is the 1.1 7 Lab?

The “1.1 7 Create Network Topologies” lab is the first hands‑on assignment in many Cisco Networking Academy courses. It isn’t just a random collection of devices; it’s a structured exercise that forces you to:

1. Select the right device types – routers, switches, PCs, and sometimes a server.
2. Place them in a logical arrangement – think star, bus, or hybrid.
3. Connect them with the appropriate cable type – straight‑through vs. crossover vs. fiber.
4. Assign IP addressing that matches the topology’s subnet plan.
5. Verify connectivity with ping, traceroute, or the simulation mode.

In plain English, the lab asks you to build a tiny network from scratch, then prove that every piece can talk to every other piece. It’s the “Hello, World!” of networking, except the “world” is a handful of devices you control.

The Typical Lab Setup

Most instructors give you a sheet that looks like this:

• Three routers (R1, R2, R3) forming a triangle.
• Two switches (SW1, SW2) each attached to a router.
• Four PCs (PC1‑PC4) spread across the switches.
• One server (optional) for DNS or DHCP.

The goal: get all PCs to ping each other and the server, using only the IP scheme you devise.

Why It Matters – The Real‑World Payoff

You might think, “It’s just a classroom drill; I’ll never see that exact layout on the job.Because of that, ” Wrong. Here’s why the 1.

• Foundation for subnetting – before you can slice a network, you need a clean topology to apply those slices.
• Cable‑type awareness – mixing straight‑through and crossover cables sounds trivial, but the wrong choice breaks connectivity instantly.
• Troubleshooting muscle – the moment you run a ping and get “Destination host unreachable,” you’re forced to diagnose: wrong IP, bad cable, missing route? That diagnostic loop is the same loop you’ll run in a data‑center.
• Documentation habit – the lab’s topology diagram doubles as a living document. Learning to keep it updated saves hours later when you hand off the design.

Bottom line: nail this lab and you’ve earned the basic toolkit that underpins every larger network you’ll ever design.

How to Do It – Step‑by‑Step Walkthrough

Below is the full workflow, broken into bite‑size chunks. Feel free to follow along in Cisco Packet Tracer, GNS3, or on real gear if you have it.

1. Plan Your IP Scheme

Before you drag a single cable, write down the subnets you’ll use. A common approach for a small lab:

Why /30 for router‑to‑router? Two usable addresses, plus network and broadcast – perfect for point‑to‑point links And that's really what it comes down to..

2. Place the Devices

• Drag three routers onto the workspace, arrange them in a triangle.
• Add two switches near R1 and R2.
• Drop four PCs – two on each switch.
• Optional server goes near SW2.

Keep the layout tidy; messy cables make troubleshooting harder later.

3. Choose the Right Cables

In Packet Tracer you’ll see the cable icon change color when you select the correct type. Real gear: older routers need a crossover for router‑to‑router; newer models have auto‑MDI/MDIX, but it’s good practice to know the difference Small thing, real impact..

4. Assign IP Addresses

Router Interfaces

1. Click R1 → CLI → enable → configure terminal.
2. interface gig0/0 → ip address 10.0.0.1 255.255.255.252 → no shutdown.
3. interface gig0/1 → ip address 10.0.1.1 255.255.255.0 → no shutdown.
4. Repeat for R2 and R3, swapping the appropriate subnet numbers.

PCs and Server

• PC1: 192.168.10.2 255.255.255.0 gateway 192.168.10.1 (the switch’s VLAN interface or the router’s address if you’re using router‑on‑a‑stick).
• PC2‑PC4: sequential IPs.
• Server: 192.168.20.2 255.255.255.0 gateway 192.168.20.1.

If you’re using a switch with a VLAN interface (SVI), assign the gateway there; otherwise, point the PCs to the nearest router’s sub‑interface.

5. Configure Routing

Because you have three routers, you need a routing protocol or static routes. For a lab, static routes keep things simple:

On R1:

ip route 10.Also, 0 255. 1.1
ip route 10.0 255.In real terms, 3. Now, 0. 2
ip route 10.Here's the thing — 0 255. Because of that, 6

On R3:

ip route 10. 1
ip route 10.0.Here's the thing — 0. 255.255.0 255.That said, 0. 3.Now, 255. 0.Which means 2. 0.So 2. Also, 0. Still, 255. 0.Day to day, 0 255. Now, 0. 252 10.Consider this: 0. 255.6

On R2:

ip route 10.255.On top of that, 252 10. 255.1.Here's the thing — 0. 0.Still, 255. In practice, 0. Here's the thing — 0. 255.Consider this: 0. Which means 0 255. 252 10.0.Think about it: 252 10. Here's the thing — 252 10. Here's the thing — 252 10. 255.Now, 255. 255.Consider this: 0. 0.

If you prefer a dynamic protocol, enable OSPF:

router ospf 1 network 10.0.0.0 0.0.0.255 area 0 network 10.0.1.0 0.0.0.255 area 0

### 6. Verify Connectivity

- From PC1, `ping 192.168.10.3`.  
- From PC1, `ping 192.168.20.2` (the server).  
- From R1, `traceroute 192.168.20.2` to see the path across routers.

If any ping fails, check:

1. **IP address typo** – a single digit off throws everything.  
2. **Cable mismatch** – wrong cable type shows “link down” in the interface status.  
3. **Missing route** – `show ip route` on each router reveals gaps.  

### 7. Save Your Work

Never finish a lab without saving the configuration:

copy running-config startup-config

In Packet Tracer, hit **File → Save** to keep the .pkt file for later review.

---

## Common Mistakes – What Most People Get Wrong

1. **Using /24 for point‑to‑point links** – you’ll quickly run out of IP space and create unnecessary broadcast traffic.  
2. **Skipping “no shutdown”** – a default shutdown on router interfaces leaves the link dead, and the symptom is a mystery ping timeout.  
3. **Mixing up gateway addresses** – pointing PCs to a switch’s MAC instead of the router’s IP leads to “Destination host unreachable.”  
4. **Forgetting to enable routing** – static routes are easy to miss; OSPF won’t start unless you issue `router ospf …`.  
5. **Relying on auto‑MDI/MDIX in a real lab** – many older switches still need a crossover cable, and the habit of checking the cable type saves you headaches later.

---

## Practical Tips – What Actually Works

- **Label everything** in the diagram and on the device itself (R1‑G0/0 = “to R2”). A quick glance tells you which cable belongs where.  
- **Use the “show ip interface brief”** command after each interface configuration. It instantly tells you IP, status, and protocol.  
- **Keep a “ping checklist”**: PC → Router → Router → Server. If the first hop fails, the problem is local; if the second fails, look at inter‑router links.  
- **Create a reusable IP spreadsheet**. Copy‑paste the subnet blocks, then just increment the host octet for each device.  
- **Turn on “simulation mode”** in Packet Tracer when you’re stuck. Watching the frame travel helps you see where it drops.  
- **Document the topology in a simple drawing tool** (draw.io, Lucidchart). Even a rough sketch beats a mental picture when you return weeks later.

---

## FAQ

**Q1: Do I have to use static routes for this lab?**  
A: No. Static routes are the easiest for a three‑router triangle, but you can also enable OSPF or EIGRP if you want practice with dynamic routing.

**Q2: What if my router interfaces show “administratively down” after I assign an IP?**  
A: You likely forgot the `no shutdown` command. Run it under each interface configuration mode.

**Q3: Can I use a single switch instead of two?**  
A: Technically, yes. But the lab’s learning objective is to practice multiple broadcast domains and inter‑switch routing, so keep the two‑switch design.

**Q4: My PC can’t ping the server, but routers can ping each other. Where do I look?**  
A: Check the PC’s default gateway and the server’s subnet mask. A mismatched mask will keep the PC from reaching the router’s interface.

**Q5: Is it okay to use IPv6 for this lab?**  
A: The 1.1‑7 lab is traditionally IPv4‑focused, but you can add an IPv6 layer once the IPv4 part works. Just remember to enable IPv6 routing (`ipv6 unicast-routing`) on each router.

---

Building a network from scratch feels a bit like assembling IKEA furniture without instructions—until you learn the pattern. Practically speaking, the 1. 1‑7 “Create Network Topologies” lab is more than a checkbox; it’s the sandbox where you discover the cause‑and‑effect of every cable, IP, and route.  

So fire up Packet Tracer, sketch that triangle, double‑check those /30s, and watch the pings roll across. Once you’ve nailed this, you’ll find larger, messier topologies a lot less intimidating. Happy networking!

### 6️⃣ Verify End‑to‑End Connectivity

Now that the devices are configured, it’s time to prove that the network actually works. A systematic verification process prevents you from chasing phantom bugs later on.

| Step | Command (on device) | Expected Result | What to Do if It Fails |
|------|---------------------|----------------|------------------------|
| 1️⃣  | `ping ` (e., from R1 to R2) | Replies with **0% loss** | Check the interface status (`show ip interface brief`), confirm the correct subnet mask, and verify the static route on the opposite router. |
| 2️⃣  | `traceroute ` from a PC | Shows three hops: PC → R1 → R2 → R3 → Server | If the trace stops at a router, re‑examine that router’s routing table (`show ip route`). In real terms, verify the cable type (straight‑through vs. Even so, |
| 4️⃣  | `show cdp neighbors detail` (or LLDP) on each switch | Lists the two routers attached to each switch, with correct port numbers | No neighbor? Even so, missing routes usually mean a typo in the `ip route` command. g.Pay attention to the **administrative distance** (static = 1) – a higher‑distance route would be ignored. Which means if it’s in the wrong VLAN, correct it with `switchport access vlan 1`. |
| 6️⃣  | `ping ` from the server (or vice‑versa) | Successful replies in both directions | Double‑check the default‑gateway on the PC and the server’s mask. So naturally, crossover) and the physical port you used. Consider this: |
| 3️⃣  | `show ip route` on each router | All three static routes you entered appear, plus directly‑connected networks | If a route is missing, re‑enter the command. On the flip side, |
| 5️⃣  | `show vlan brief` on each switch | VLAN 1 is **active** and ports are **assigned to the correct VLAN** | If a port shows “administratively down,” issue `no shutdown`. A common mistake is giving the PC a /24 mask while the router interface is /30. 

**Tip:** Keep a small notebook (or a text file) with the exact ping commands you ran and the output you received. When you revisit the lab later—perhaps for a certification exam—those notes become a priceless cheat‑sheet.

---

### 7️⃣ Common Pitfalls & How to Dodge Them

| Symptom | Likely Cause | Quick Fix |
|---------|--------------|-----------|
| **“%LINK‑DOWN‑IF‑DOWN”** when you try to assign an IP | Interface is still administratively down | Enter `no shutdown` under the interface. |
| **PC gets an IP address but cannot reach the router** | Wrong default‑gateway set on the PC | Re‑enter the correct gateway IP (the router interface the PC is physically attached to). Also, |
| **No route appears in `show ip route`** after you typed `ip route …` | Typo in the destination network or mask | Re‑type the command, double‑checking each octet. |
| **Ping works one way but not the other** | Asymmetric ACLs or missing return route | If you added any ACLs, ensure they permit both inbound and outbound traffic. |
| **Switch ports stay in “trunking” mode** even though you never configured a trunk | The switch auto‑negotiated a trunk because both ends are routers (which default to trunk mode on some models) | Force access mode with `switchport mode access`. Verify the opposite router’s static route. |
| **`show cdp neighbors` lists only one neighbor** | One of the cables is bad or the wrong type | Swap the cable, or replace it with a known‑good straight‑through cable. 

---

### 8️⃣ Extending the Lab (Optional “Next Steps”)

Once the basic triangle is stable, you can stretch the scenario to reinforce concepts you’ll need for the CCNA and beyond.

| Extension | What You Learn | How to Implement |
|-----------|----------------|------------------|
| **Add a VLAN‑10 for “Voice”** on both switches and tag the router‑to‑switch links with a trunk | VLAN tagging, inter‑VLAN routing, native VLAN considerations | Create VLAN 10, assign ports, configure `switchport mode trunk` on the router‑facing ports, then add a sub‑interface on each router (e.g., `interface g0/0.Which means 10 encapsulation dot1q 10 ip address 192. 168.10.Still, 1 255. 255.And 255. 0`). |
| **Replace static routes with OSPF** (area 0) | Dynamic routing, adjacency formation, LSAs | Enable OSPF: `router ospf 1`, `network 10.0.0.0 0.This leads to 0. 0.255 area 0`. Worth adding: verify with `show ip ospf neighbor`. Consider this: |
| **Introduce a firewall (ASA or simple ACL)** between R2 and R3 | Security policy enforcement, packet filtering | On R2’s interface toward R3, apply an ACL that blocks TCP port 23 (Telnet). Practically speaking, use `access-list 100 deny tcp any any eq 23` followed by `access-group 100 out`. |
| **Simulate a link failure** (disconnect R1‑R2 cable) and watch convergence | Redundancy, failover, troubleshooting | Disconnect the cable in Packet Tracer, then re‑connect. Observe the routing table changes and the “*” in the output of `show ip route`. In practice, |
| **Add IPv6 addressing** (global unicast) | Dual‑stack operation, IPv6 routing basics | Enable IPv6 on each interface (`ipv6 address 2001:DB8:1::1/64`) and turn on `ipv6 unicast-routing`. Verify with `ping ipv6 
`. 

These extensions are optional; they’re meant to keep the lab fresh after you’ve mastered the fundamentals.

---

## 📚 Bottom Line

The 1.1‑7 “Create Network Topologies” lab is a microcosm of real‑world networking. By **planning the address scheme**, **laying out the physical connections**, **configuring each device methodically**, and **validating step‑by‑step**, you turn a seemingly abstract diagram into a living, breathing network. The checklist, the ping‑order workflow, and the labeling habit you develop here will pay dividends every time you design a larger campus, a data‑center spine‑leaf, or even a cloud‑native virtual network.

Remember: a network is only as reliable as its documentation and the rigor of its verification. Even so, take a few minutes to label cables, capture screenshots of `show run` and `show ip route`, and store the IP spreadsheet in a version‑controlled folder. When the next lab—or a production rollout—calls for a quick sanity check, you’ll have the exact reference you need, and you’ll avoid the classic “it works on my machine” trap.

No fluff here — just what actually works.

So fire up Packet Tracer, follow the steps, and let those green “up” lights appear on every interface. 3.When the final ping from PC‑A to the server returns **Reply from 192.Day to day, 168. 2: bytes=100 time<1ms TTL=255**, you’ll know you’ve built more than a triangle of routers—you’ve built a solid foundation for every network you’ll ever design.

Not obvious, but once you see it — you'll see it everywhere.

**Happy packet‑crafting!** 🚀

## 🚀 Next‑Level Troubleshooting: A “What‑If” Playbook

| **Scenario** | **What to Look For** | **Command‑Line Checklist** |
|--------------|---------------------|----------------------------|
| **PC‑A can’t reach R2** | Verify interface status, IP mask, and default gateway on PC‑A; check R2’s `show ip interface brief`. | `ipconfig /all` on PC‑A, `show ip interface brief` on R2, `show ip route` on R2. |
| **R3 advertises a wrong subnet** | Inspect OSPF LSAs (`show ip ospf database router`), confirm the subnet is correctly configured on the interface. | `show ip ospf interface g0/1` to see the network type and cost. |
| **ACL blocks legitimate traffic** | Check ACL hit counts (`show access-lists 100`), ensure order of permit/deny statements. And | `show access-group interface g0/0 in` to confirm applied ACL. |
| **Link flaps cause routing loops** | Observe OSPF state changes (`show ip ospf neighbor`), look for `2` (down) states. | `debug ip ospf events` (use with caution). 

A systematic “what‑if” approach not only fixes problems faster but also deepens your understanding of how each layer reacts to misconfigurations.

## 📈 Scaling Out: Adding a Fifth Router

Once you’re comfortable with three routers, try inserting **R4** between R2 and R3 to simulate a larger campus. Repeat the same steps:

1. **Assign new subnets** (e.g., 10.0.0.64/26 for R4‑R2, 10.0.0.128/26 for R4‑R3).  
2. **Update OSPF**: `network 10.0.0.64 0.0.0.63 area 0` and `network 10.0.0.128 0.0.0.63 area 0`.  
3. **Re‑label cables**: R2‑R4 (red), R4‑R3 (green).  
4. **Validate**: `show ip route` on each router now contains the new subnet.  

This exercise demonstrates how OSPF scales linearly with the number of routers, and how the lab environment can mirror a real‑world campus backbone.

## 📦 Packaging the Lab for Future Reference

1. **Export the Packet Tracer file** and save it in a dedicated folder (e.g., `Lab-01-Topology-OSPF`).  
2. **Create a README** that lists all IP addresses, subnet masks, and OSPF process IDs.  
3. **Snapshot key states**: `show running-config`, `show ip route`, and `show ip ospf neighbor`.  
4. **Version‑control** the README and screenshots using Git or a cloud‑storage “revisions” feature.  

Having a clean, reproducible lab environment means you can revisit the topology months later, refresh your memory, or share it with classmates without re‑building from scratch.

## 🎓 What You’ve Mastered

- **Physical and logical design**: Translating a diagram into a working network.  
- **Device configuration**: From interface IPs to OSPF adjacency.  
- **Verification**: Using ping, traceroute, and routing tables to prove connectivity.  
- **Documentation**: Labeling, spreadsheets, and screenshots that make troubleshooting painless.  
- **Extension mindset**: Adding security, IPv6, and redundancy on top of a solid base.

These skills are the cornerstones of any network engineer’s toolkit. 3.168.When the final ping from PC‑A to the server returns **Reply from 192.So each time you approach a new lab or a production environment, remember the sequence: **Plan → Build → Configure → Verify → Document**. 2: bytes=100 time<1ms TTL=255**, you won’t just have a green “up” light—you’ll have a confidence‑boosting moment that your network is ready for the real world.

---

## 📌 Final Takeaway

The “Create Network Topologies” lab isn’t just an exercise; it’s a micro‑simulation of the challenges you’ll face on the job. By mastering the fundamentals—addressing, routing, and verification—you pave the way for more complex scenarios: multi‑area OSPF, BGP, MPLS, or SD‑WAN. Keep experimenting, keep documenting, and let each lab be a stepping stone toward becoming a network architect who can design, troubleshoot, and secure networks with confidence.

**Happy packet‑crafting, and may your routing tables always converge on time!** 🚀