2.9.1 Packet Tracer - Basic Switch And End Device Configuration

Ever tried to get two devices to talk in Packet Tracer and ended up pulling your hair out? Here's the thing — you’re not alone. So most of us have stared at a blinking green light, wondering why the ping refuses to cooperate, only to realize we skipped a single line of CLI input. That little moment of frustration is exactly why the 2.Still, 9. 1 packet tracer - basic switch and end device configuration lab shows up on so many certification study lists. It’s not just a checkbox exercise; it’s the foundation for everything that follows — from routing protocols to network security. Let’s walk through it together, step by step, in a way that feels more like a conversation than a textbook recital Simple, but easy to overlook..

What Is Packet Tracer and Why It Matters

Packet Tracer is Cisco’s free, visual network simulation tool. The 2.9.So it lets you drag switches, routers, PCs, and a handful of other goodies onto a virtual canvas, then wire them together and give them life with a few commands. 1 packet tracer - basic switch and end device configuration scenario is one of the first places you’ll see a switch actually do something beyond just being a shiny box on the screen.

Why does this lab matter? Because once you can get a PC to ping a server through a switch, you’ve unlocked the ability to design real‑world LANs. In real terms, you’ll understand how MAC tables work, how IP addresses are assigned, and why a mis‑typed command can bring an entire segment to a halt. In short, mastering this tiny slice of configuration gives you the confidence to tackle bigger, more complex topologies later on Simple as that..

Setting Up Your Environment

Before you even think about typing a command, you need a basic topology. Imagine a single Cisco 2960 switch sitting in the middle, with two end devices — let’s call them PC‑A and PC‑B — connected to two of its ports. Worth adding: that’s all you need for the 2. 9.1 packet tracer - basic switch and end device configuration exercise.

1. Drag a Switch onto the workspace.
2. Add two PC devices and connect each to a different switch port using the cable tool.
3. Power up the switch (click the On button) and each PC (right‑click → On).

That’s it. You now have a tiny network ready for configuration Worth keeping that in mind..

Accessing the Switch CLI

The command line interface (CLI) is where the magic happens. By default, the switch’s console port is the easiest way to get in.

• Click the Switch to open its desktop.
• Double‑click the Terminal icon.
• A small window pops up; you’ll see a blinking cursor waiting for input.

From here, you can start typing the commands that will shape the switch’s behavior. No need for fancy menus — just pure, text‑based control Most people skip this — try not to..

Configuring the Switch Basics

Setting a Hostname and Password

A clean, identifiable switch makes troubleshooting later a breeze Easy to understand, harder to ignore..

enable
configure terminal
hostname MyFirstSwitch
line vty 0 4
 password secret123
 login

These few lines give your switch a name and protect it with a password. It’s a small habit that pays off when you’re juggling dozens of devices That alone is useful..

Securing the Management Interface

If you plan to manage the switch remotely, you’ll want to lock down the management VLAN. 9.For the 2.1 packet tracer - basic switch and end device configuration lab, we’ll keep it simple: assign an IP address to the VLAN 1 interface and enable SSH (or Telnet, if you’re feeling nostalgic).

interface vlan 1
 ip address 192.168.1.2 255.255.255.0
 no shutdown
exit
ip default-gateway 192.168.1.1

Now the switch can be reached from any device on the same subnet, which is essential for remote troubleshooting Simple, but easy to overlook..

Configuring End Devices

Assigning IP Addresses

Your PCs need IP addresses, subnet masks, and default gateways to talk to each other. In this lab, we’ll manually assign them to avoid relying on DHCP — a common source of confusion for beginners Surprisingly effective..

• PC‑A: IP = 192.168.1.10, Subnet Mask = 255.255.255.0, Default Gateway = 192.168.1.1
• PC‑B: IP = 192.168.1.11, Subnet Mask =

Subnet Mask = 255.255.255.0, Default Gateway = 192.168.1.1.

Connectivity Test

With all configurations in place, it’s time to verify communication. Open a command prompt on PC-A and ping PC-B (ping 192.168.1.11). The output should show 100% success, confirming layer 2 connectivity. Repeat the test from PC-B to PC-A to ensure bidirectional communication It's one of those things that adds up..

Troubleshooting Common Issues

If the ping fails, check these potential culprits:

1. Cable Connections: Ensure cables are securely attached to the correct ports.
2. Interface Status: Verify switch ports are enabled (show interfaces status).
3. IP Configuration: Confirm both PCs have valid IPs in the same subnet.
4. Default Gateway: Ensure the gateway IP (192.168.1.1) matches the switch’s VLAN 1 address.

Use the show ip interface brief command on the switch to validate VLAN 1’s IP assignment But it adds up..

Conclusion

This exercise lays the foundation for networking fundamentals. By configuring a Cisco switch, assigning static IPs to end devices, and verifying connectivity, you’ve mastered the basics of LAN setup. While this topology is simple, it mirrors real-world scenarios where devices rely on switches for communication. As you progress, you’ll expand this knowledge to more complex topologies—adding routers, VLANs, and advanced security measures. For now, however, this small network proves that even the simplest configurations are the building blocks of solid, scalable networks. Keep experimenting, and soon you’ll be ready to tackle the next layer of networking complexity.

Securing Remote Access

While the switch is now reachable via IP, the default configuration allows unencrypted Telnet access — a security risk in any environment. Let’s harden remote management by enabling SSH version 2 and disabling Telnet.

First, configure a domain name and generate RSA keys (minimum 1024 bits, though 2048 is recommended):

ip domain-name lab.local
crypto key generate rsa modulus 2048

When prompted, accept the default key pair name. Next, create a local user with privilege level 15 (full administrative access) and a strong password:

username admin privilege 15 secret cisco123

Now configure the virtual terminal lines to accept only SSH, apply the local user database, and set a reasonable timeout:

line vty 0 4
 transport input ssh
 login local
 exec-timeout 5 0
 logging synchronous
exit

Finally, restrict SSH to version 2 explicitly and set a connection timeout:

ip ssh version 2
ip ssh time-out 60
ip ssh authentication-retries 3

Verify the configuration with show ip ssh and test from PC-A using an SSH client (e.And 2). 168.g., ssh -l admin 192.1.You should be prompted for the password and granted a CLI session Simple, but easy to overlook. Nothing fancy..

Verifying the MAC Address Table

A switch learns MAC addresses dynamically by inspecting source addresses in incoming frames. After the ping tests, check the MAC address table to confirm both PCs are learned:

show mac address-table dynamic

You should see entries for PC-A (192.In practice, 168. 1.Day to day, 10) and PC-B (192. 168.1.11) mapped to their respective switch ports (e.g., Fa0/1 and Fa0/2), with type DYNAMIC. This confirms the switch is correctly building its forwarding table — the core of Layer 2 switching No workaround needed..

This is the bit that actually matters in practice.

To observe the aging process, clear the table with clear mac address-table dynamic and re-ping. The entries will repopulate, demonstrating the self-learning mechanism.

Saving the Configuration

All changes so far reside in running memory. A power cycle would erase them. Commit the configuration to NVRAM:

write memory

Or the modern equivalent:

copy running-config startup-config

Confirm with show startup-config — you should see your VLAN 1 IP, SSH settings, username, and any port configurations persisted.

Final Verification Checklist

Before considering the lab complete, validate each requirement:

Conclusion

This lab has taken you from a bare-metal switch to a securely managed, fully functional Layer 2 segment. You’ve configured in-band management, hardened remote access with SSH, assigned static IP addressing to end devices, validated connectivity, inspected the MAC address table, and persisted the configuration — each step reinforcing a core networking principle Simple as that..

And yeah — that's actually more nuanced than it sounds.

While the topology is intentionally minimal, the skills are directly transferable: VLAN interfaces scale to distribution layers, SSH hardening applies to every network device, and MAC address dynamics underpin all Ethernet switching. As you advance, you’ll layer routing, VLAN segmentation, spanning-tree tuning, and automation onto this foundation.

For now, you’ve

mastered the essentials of configuring and validating a secure, operational Layer 2 network.

Conclusion
This lab has taken you from a bare-metal switch to a securely managed, fully functional Layer 2 segment. You’ve configured in-band management, hardened remote access with SSH, assigned static IP addressing to end devices, validated connectivity, inspected the MAC address table, and persisted the configuration—each step reinforcing a core networking principle. While the topology is intentionally minimal, the skills are directly transferable: VLAN interfaces scale to distribution layers, SSH hardening applies to every network device, and MAC address dynamics underpin all Ethernet switching. As you advance, you’ll layer routing, VLAN segmentation, spanning-tree tuning, and automation onto this foundation. For now, you’ve built the bedrock of network infrastructure, ensuring reliability, security, and scalability in every deployment Small thing, real impact..