On-the-Job Attachment Preparation Packet Tracer Phase 3 of 3

Packet Tracer Phase 3: Industry IT Mindset & Attachment Scenario Solvers

Thinking like an enterprise network engineer: Structured troubleshooting playbooks, SOPs, and workplace issue resolution.

💼 The Industry IT Engineering Mindset

When users complain that "the network is down", experienced IT engineers do not guess or randomly click around. They follow a systematic **Bottom-Up OSI Layer Diagnostic SOP** (Layer 1 Physical $\rightarrow$ Layer 2 Data Link $\rightarrow$ Layer 3 Network $\rightarrow$ Layer 7 Application) to pinpoint the exact root cause in minutes.

1. The 4-Tier Enterprise Network Architecture Breakdown

1. Core Layer (Core Switches / Routers)

High-speed 10Gbps/40Gbps backbone layer. Responsible for fast packet switching between building distributions and WAN ISP firewalls without packet filtering bottleneck.

2. Distribution Layer (Layer 3 Switches)

Combines access switch connections, enforces inter-VLAN routing, ACL security policies, and QoS traffic prioritization.

3. Access Layer (PoE Managed Switches)

Connects end-user PCs, IP desktop phones, WAPs, and CCTV security cameras. Enforces VLAN access port assignments and Port Security.

4. Perimeter Edge (Firewall & Fiber Box)

Inspects incoming stateful traffic, runs IDS/IPS penetration defenses, and terminates primary/secondary ISP WAN links.

2. Attachment Troubleshooting SOP Playbooks

Field Ticket 01

User PC Receives APIPA Address (169.254.x.x) - No Network Access

Scenario: A workstation in the Finance office cannot open internal portal pages. Running ipconfig /all shows an IP address of 169.254.42.88.

Engineering Diagnosis: APIPA (Automatic Private IP Addressing) indicates that Layer 1 and 2 links are physically connected, but the PC failed to receive a response from the DHCP server (DORA sequence failed).

Step-by-Step CLI SOP Resolution


Step 1: Verify switch access port status and VLAN membership:
        Switch# show interface FastEthernet 0/8
        Switch# show vlan brief
        ! If port is in wrong VLAN, reassign:
        Switch(config-if)# switchport access vlan 10

Step 2: Check if DHCP pool on router is exhausted:
        Router# show ip dhcp binding
        Router# show ip dhcp pool ADMIN_POOL

Step 3: If DHCP server is on a different subnet, verify IP Helper Address on router interface:
        Router(config-subif)# interface GigabitEthernet 0/0/0.10
        Router(config-subif)# ip helper-address 10.1.1.254  ! IP of central DHCP server

Field Ticket 02

Network Sluggishness Caused by Unmanaged Switch Loop (STP Storm)

Scenario: An employee brought a cheap unmanaged 4-port desktop switch from home and plugged both ends into office wall jacks, causing a broadcast loop storm that froze the enterprise switch.

Engineering Diagnosis: Unmanaged switches do not process Spanning Tree BPDUs. Plugging both ends into wall jacks creates a loop that floods the switch CPU with infinite broadcast frames.

Step-by-Step CLI SOP Resolution


Step 1: Identify high-bandwidth loop port using switch port stats:
        Switch# show interfaces status
        Switch# show spanning-tree summary

Step 2: Enable BPDU Guard on all access ports so ports automatically shut down if a rogue switch is attached:
        Switch(config)# interface range FastEthernet 0/1 - 24
        Switch(config-if-range)# spanning-tree portfast
        Switch(config-if-range)# spanning-tree bpduguard enable

Field Ticket 03

Primary Fiber WAN Internet Cut - Executing Emergency ISP Failover

Scenario: Construction outside campus cut the primary Liquid Fiber optic line. All internet browsing drops across all departments.

Engineering Diagnosis: Inspect the core fiber transceiver converter box in the network cabinet. Link/RX LED is dark. Firewall static route must switch to secondary TelOne ISP link.

Step-by-Step CLI SOP Resolution


Step 1: Check WAN interface status on perimeter firewall/router:
        Firewall# show ip interface brief
        ! Interface GigabitEthernet 0/0/1 (Primary Fiber) is down/down.

Step 2: Verify active routing table:
        Firewall# show ip route
        ! Confirm floating static route automatically switched default route to Secondary WAN:
        ! S* 0.0.0.0/0 [10/0] via 198.51.100.1 (TelOne Secondary Gateway)

Step 3: Test ping connectivity to public DNS:
        Firewall# ping 8.8.8.8
        ! Open high-priority ticket with primary fiber provider while monitoring backup link bandwidth.