Understand the system
Build the mental models behind routing, switching, security, and infrastructure.
Read the field notesTechnical knowledge for connected systems
Engineering,
layer by layer.
Practical notes, hands-on labs, and small tools for the networks and infrastructure underneath modern work.
NETWORKS / SECURITY / SYSTEMS / CLOUD
THE SYSTEM, IN CONTEXT7L / FIELD MAP
NETWORKING
SECURITY
OBSERVABILITY
LINUX
CONTAINERS
CLOUD
DEVOPS
FOUNDATIONEXPERIENCE
Learn by understanding the whole
Good engineering is connected thinking.
Practice the diagnosis
Work through realistic labs with observable symptoms, checks, and outcomes.
Explore the labsKeep useful tools close
Use small, dependable references for common engineering calculations.
Open the toolsA practical way through complexity
Every good fix starts with a better question.
Followevidenceacrossthestack.Testonelayeratatime.Sharewhatthesystemistellingyou.
See the path
TRACEStart with the symptom and map the systems that sit between the user and the service.
Test one layer
ISOLATEUse a focused check to separate what is known from what still needs evidence.
Explain the result
SHARETurn the investigation into clear notes, repeatable steps, and better decisions.
From the library
Start with a signal.
Field noteROUTING
Troubleshooting OSPF neighbor adjacencies
A calm, layer-by-layer way to isolate why two routers will not form a neighbor relationship.
Hands-on labSWITCHING
Trace a VLAN across a trunk
Follow one frame through access ports, VLAN tags, and a 802.1Q trunk.
Network toolIPV4
Calculate an IPv4 subnet
Explore the prefix, network boundary, broadcast address, and usable host range.
The landscape
Systems are connected. So is the learning.
Follow a question across the layers that shape it, from a link light to an application path.
L01Routing & switching
L02Network security
L03Observability
L04Linux & systems
L05Containers
L06Cloud infrastructure
L07DevOps practice
Built in the open
Clear notes for the work behind the work.
7LayerX is a growing engineering resource. Technical content is written to be useful, testable, and honest about what each example assumes.