What My Internship Taught Me About Enterprise Networks

Why I Took the Internship

When I started my BS IT degree at University of Gujrat, I quickly realized that textbook networking wasn't enough. I could recite the OSI model layers and explain TCP/IP, but I had never actually configured a router or troubleshooted a real network issue. That's why when the opportunity came to intern at IT-Simplera Institute as a Network Administration Intern, I took it immediately.

The internship ran from June 24 to August 30, 2026 — 10 weeks of hands-on network design, configuration, and troubleshooting. Here's what I learned.

Week 1-2: The Basics Are Not Basic

My first task was simple: configure a basic network in Cisco Packet Tracer with three PCs and a router, then verify connectivity with ping. Sounds easy, right?

It took me two days.

The problem wasn't the commands — it was understanding why things weren't working. IP addresses were in different subnets. The default gateway was misconfigured. One PC had a static IP while the others used DHCP. Each issue taught me that networking is 20% configuration and 80% understanding the fundamentals.

The first time all three PCs pinged each other successfully, I literally wrote it down in my notebook. That moment made me realize: networking is about patience and attention to detail.

Week 3-5: GNS3 Changes Everything

After getting comfortable with Packet Tracer, we moved to GNS3. This was a completely different experience. GNS3 uses real IOS images, which means the commands and behavior are identical to physical Cisco equipment.

Key things I learned in GNS3:

• How to connect virtual routers to real network interfaces
• Configuring OSPF single-area and understanding link-state routing
• Setting up VLANs and trunk ports between switches
• Using VPCS (Virtual PC Simulator) for end-device testing
• Troubleshooting with show ip route, show ip interface brief, and debug ip ospf adj

The biggest lesson from GNS3: there's a massive difference between knowing a command and understanding what it does.

Week 6-8: Enterprise Network Design

This was the core of the internship. We had to design and implement a multi-site enterprise network with:

• Multiple VLANs for different departments
• OSPF routing between areas
• STP (Spanning Tree Protocol) for redundancy
• ACLs for basic security filtering
• DHCP for automatic IP assignment

I spent an entire week just on STP. The concept of root bridge election, port states, and convergence was confusing at first. But once I physically drew out the topology and traced the BPDU flow, it clicked.

What STP taught me about learning:

Don't just memorize the theory. Draw the topology. Trace the packets. Break things on purpose. That's how you actually understand networking.

Week 9-10: Documentation and Reporting

Every week, I had to write progress reports. At first, I hated this part. But looking back, it was one of the most valuable exercises. Writing about what I configured, what went wrong, and how I fixed it forced me to truly understand the material.

I also learned that in a real IT job, documentation is not optional. If you can't explain what you did to someone else, you don't really understand it.

What I'd Tell Other Students

If you're studying IT or networking and haven't done any hands-on lab work yet, start now. You don't need expensive equipment. Download Cisco Packet Tracer (it's free for students). Build a network. Break it. Fix it. Document everything.

The internship taught me that the gap between "I know networking theory" and "I can design and troubleshoot a network" is enormous. Bridging that gap is what makes you employable.

My GitHub has all my lab projects — from basic ping tests to enterprise topologies. Every project includes screenshots, configuration files, and what I learned. That's the portfolio that got me interviews.