Skip to content
FALCON CORETECHNOLOGIES

// Troubleshooting

Find the fault. Prove the fix.

Guessing wastes hours. A structured, layer-by-layer method finds most network faults in minutes — and leaves evidence that the fix worked.
PC1 — PowerShell
PS> Test-NetConnection 10.20.0.15 -Port 443ComputerName     : 10.20.0.15RemotePort       : 443PingSucceeded    : TrueTcpTestSucceeded : False # Layer 3 works, layer 4 fails → check ACL / firewall / service

// Method

Six steps, every time

  1. 01

    Define the problem

    Who is affected, what exactly fails, since when, and what changed.
  2. 02

    Gather facts

    Reproduce it. Collect interface status, logs, routes and captures before touching anything.
  3. 03

    Isolate by layer

    Work up (or down) the OSI model and split the path in half until the fault is boxed in.
  4. 04

    Fix one thing

    Make a single, reversible change, so you know which change worked.
  5. 05

    Verify

    Re-run the same test that failed. Confirm users are working again.
  6. 06

    Document

    Record cause, fix and evidence. Tomorrow's outage is easier because of it.

// Layer by layer

What to check at each layer

LayerNameTypical checks
L1PhysicalLink lights, cabling, optics/SFP type, interface errors (CRC, input errors), duplex and speed.
L2Data linkVLAN membership, trunk allowed VLANs, STP state, MAC address table, LLDP/CDP neighbours.
L3NetworkIP address and mask, default gateway, routing table, ARP, ACLs, routing protocol adjacencies.
L4TransportPort reachability, firewall/NAT rules, TCP handshake, resets and retransmissions.
L5–7Session → ApplicationDNS resolution, DHCP leases, TLS/certificates, authentication, application logs.

// Quick reference

Commands worth knowing by heart

Read-only commands: safe to run on production devices while you gather facts.

Cisco IOS / IOS XE

show ip interface brief
Interface IPs and up/down status
show interfaces status
Switchport speed, duplex, VLAN, state
show vlan brief
VLANs and their access ports
show spanning-tree
STP roles and port states
show ip route
Routing table
show cdp neighbors / show lldp neighbors
Directly connected devices
show logging
Recent device log messages

Juniper Junos

show interfaces terse
Interface addresses and link state
show route
Routing table
show ethernet-switching table
Learned MAC addresses
show lldp neighbors
Directly connected devices
show log messages
System log
show system alarms
Active system alarms

Windows

ipconfig /all
Addresses, gateway, DNS servers, DHCP lease
Test-NetConnection host -Port 443
Ping plus TCP port test (PowerShell)
tracert host
Hop-by-hop path
nslookup name
DNS lookup against the configured server
route print
Local routing table
netstat -ano
Connections and listening ports with process IDs

Wireshark display filters

ip.addr == 10.0.0.5
Traffic to or from one host
tcp.port == 443
One TCP port
tcp.flags.reset == 1
Connections being reset
tcp.analysis.retransmission
Retransmitted segments
dns
DNS queries and responses
dhcp
DHCP exchange (DORA)

Practise on broken labs

The best way to get fast at troubleshooting is to fix things that are broken on purpose.