Documenting, diagnosing, and fixing a segmented LAN
Good documentation makes troubleshooting faster. Systematic diagnosis turns a complex, multi-segment network problem into an identifiable cause. And knowing the correct solution for each type of issue restores connectivity without guessing. This topic covers all three steps — from recording IP addressing schemes to fixing DHCP failures and voltage drops.
What this topic covers
- › 3.6.A — Network documentation: topology diagrams, device naming, IP addressing, and ACL notes
- › 3.6.B — Identifying root causes of common segmented LAN issues
- › 3.6.C — Solutions for each category of issue, and verifying that functionality is restored
Troubleshoot before you configure
When a connectivity issue appears on a segmented network, the first step is always to try simple solutions before diving into configuration changes: restart the router, switch, or WAP; restart affected devices; reconnect to the network; and confirm the device is on the correct SSID with the right password. Only if these steps fail should diagnostic tools be used to investigate further.
Network documentation (3.6.A)
Complete and current documentation enables efficient network management and troubleshooting. Documentation must be updated whenever changes are made to the network.
What to document
- › Topology diagrams: Physical and logical layout with labeled devices and all wired/wireless connections
- › Device naming: Consistent, clear names and roles for every device — not just "Switch" or "Router"
- › IP addressing scheme: All subnets, ranges, and any statically assigned devices identified separately
- › Security notes: Segments with specific firewall rules or ACL requirements noted for easy reference
Why documentation matters
Without clear documentation, a technician troubleshooting a connectivity issue must probe the network to discover its topology, IP ranges, and security rules before even beginning to diagnose the actual problem. Good documentation eliminates this discovery phase, allowing the technician to immediately compare the current state against the intended state.
Always update documentation after any configuration change.
Identifying root causes (3.6.B)
After basic restart steps fail, use diagnostic tools to identify the root cause. Different symptoms point to different causes in a segmented LAN.
| Symptom / observation | Likely cause | How to identify |
|---|---|---|
| IP address shows 169.254.x.x | DHCP server unavailable or pool exhausted | Check IP config with ipconfig/ifconfig |
| Has an IP address but cannot reach other segments or internet | Missing or incorrect default gateway or subnet mask | Compare IP config to intended network settings |
| ping between segments fails | Firewall rule or ACL blocking inter-segment traffic | Use ping to test internal and external reachability; review ACLs |
| Wireless signal < −70 dBm, frequent drops, high latency | WAP too far or obstructed; EMI from nearby devices | Wireless signal analyzer (mobile app or standalone device) |
| Devices reboot unexpectedly; routing tables and DHCP leases lost | Unstable power — voltage drops or brief outages | Power analyzer logging voltage levels and interruptions |
Wireless signal thresholds
- Below −70 dBm: Weak signal — WAP too far or obstructed by walls/objects
- High noise/interference: EMI from microwaves, Bluetooth, or neighboring networks
Power voltage thresholds (120V systems)
- Below 110V: May cause devices to restart or malfunction
- Above 125V: May cause device damage or unexpected behavior
- Brief dropouts (<5s): May not trigger software alerts but can corrupt routing tables and DHCP leases
Solutions and verification (3.6.C)
Once the root cause is identified, apply the appropriate solution and verify that full connectivity is restored for both internal and external resources.
DHCP unavailable or pool exhausted
- › Restart the DHCP server
- › Expand the IP address range of the DHCP pool
- › Reduce the lease time to force addresses to recycle more quickly
Missing or incorrect gateway / subnet mask
- › Assign the correct default gateway and subnet mask to the device
- › Ensure the DHCP server settings include the correct gateway and mask for the pool
Firewall / ACL rule issues
- › Reorder ACL rules to place allow rules before broad deny rules
- › Review deny rules to avoid unintentionally blocking necessary traffic
- › Verify direction, ports, and protocols in each rule
- › Allow necessary outbound traffic to external networks if blocked
Weak wireless signal / interference
- › Move the WAP to improve coverage radius
- › Reduce physical obstructions between the WAP and devices
- › Relocate the WAP away from sources of EMI (microwaves, Bluetooth devices)
Voltage / power delivery problems
- › Move devices to a different power circuit to avoid a shared overloaded circuit
- › Install an uninterruptible power supply (UPS) to provide stable power and battery backup during brief outages
Verifying restored functionality
After applying any solution, confirm that devices can maintain a stable connection to the network and can reach both internal resources (servers, file shares, printers) and external resources (internet) as needed. Both local and cross-segment connectivity should be tested.