01↗
Physical Foundations
Copper, fiber, racks, pathways, PoE, testing, and the discipline of building from Layer 1 up.
CablingFiberPoE
Open archive →Field notes of an infrastructure engineer
From copper
to cloud.
A living collection of field-tested knowledge covering the systems beneath modern communication—built from more than 25 years of solving real infrastructure problems.
- 25+
- Years in IT
- 06
- Core disciplines
- L1–L7
- Full-path thinking
LAYER 01 · PHYSICAL
LAYER 03 · NETWORK
LAYER 07 · APPLICATION
MIDWEST REGION
CENTRAL TIME // ONLINE
CENTRAL TIME // ONLINE
NETWORKING ◆ LINUX ◆ WINDOWS ◆ AWS ◆ UNIFIED COMMUNICATIONS ◆ AUTOMATION ◆ CABLING ◆ TROUBLESHOOTING
Knowledge archive
Explore the disciplines
Each archive connects theory to field experience: what to check, why it matters, how to interpret the evidence, and how to prove the result.
02↗
Network Paths
Switching, routing, VLANs, DNS, DHCP, firewalls, QoS, and packet-level troubleshooting.
TCP/IPWiresharkQoS
Open archive →03↗
Systems Archive
Linux, Windows, virtualization, services, performance, security, and reliable operations.
LinuxWindowsVMware
Open archive →04↗
Cloud Systems
Practical cloud architecture, identity, networking, resilient design, and automation in AWS.
AWSIAMAutomation
Open archive →05↗
Communications Grid
Enterprise voice, SIP, H.323, RTP, contact centers, and unified communications platforms.
AvayaSIPRTP
Open archive →06↗
Diagnostic Records
Field-tested investigations, maintenance plans, validation steps, and sanitized mission logs.
RCATLSCase studies
Open archive →Troubleshooting doctrine
Follow the path.
Prove every layer.
Reliable troubleshooting is a repeatable process. Move from physical reality to application behavior, reducing uncertainty at every step.
- 01
Observe
Start with evidence, not assumptions.
- 02
Isolate
Follow the path and narrow the failure domain.
- 03
Resolve
Make the safest effective change.
- 04
Prove
Validate service, document results, and preserve a backout.
Keeper of the archive
Christian Lutes
Infrastructure & Cloud Engineer
I build, troubleshoot, and explain the systems that keep people connected. My experience spans the physical layer, enterprise networks, Linux and Windows systems, virtualization, AWS, and complex unified communications environments.