Mostly harmless, conspicuously useful

The Hitchhiker's Guide to Becoming a Network Engineer

A network engineer designs, builds, secures, and mends the systems that carry packets from where they are to where they intend to be, which is a noble profession built atop an OSI model of seven layers, each with strong opinions about whose fault a problem is. You learn to translate "the network is down" into a question about routing, switching, DNS, firewalls, load balancing, and a circuit that belongs to a provider who will, after forty minutes on hold, agree that it is probably their circuit. BGP announces routes with confidence and retracts them with equal confidence, often within the same minute, while DNS propagation time is a number that means "eventually" and is believed by no one who has waited for it. The network is welcoming on the way in, commemorative on the way out, and enthusiastic about converting a single misconfigured access list into a company-wide learning event. This guide travels from reading a subnet mask without flinching to designing multi-site failover policy, with practical stops at switching, routing, services, segmentation, traffic engineering, automation, and the recurring discovery that a cable labelled "patch" is merely a cable whose documentation has not yet caught up with its consequences. The grand objective is packets that arrive where they were sent, at a speed that does not prompt a meeting; the daily evidence is usually a traceroute that explains itself, an ACL that blocks the traffic it meant to block, and a change window that closes without introducing a new reason to open another one.

Things to recognise

• A port labelled "access" in one VLAN and cabled to a trunk expecting another is a configuration mismatch dressed as an outage; verify the VLAN on both ends before escalating, because the switch is doing exactly what you asked, not what you meant.
• Subnet masks are read as binary even when typed as dotted decimal, so a mask of 255.255.255.0 and one of /24 are the same boundary described in two languages, and a /23 is twice the addresses you may have intended to advertise.
• Confirm the device, port, VLAN, and intended traffic class before re-patching, because a correct cable in the wrong port is still an incident, and unlabelled patch leads outlive their creators with indecent regularity.

Take the useful exit

Level 1 · Novice

Read the subnet mask before the switch forms an opinion about you

You inspect addressing, cabling, switch configurations, and diagrams without changing traffic, learning how a perfectly polite switch can forward a packet into the wrong VLAN before anyone has finished the sentence describing where it ought to go.

You begin with read-only artifacts: addressing plans, switch configurations, VLAN diagrams, port labels, cabling records, and packet captures that express recent opinions about traffic. An IP address is a network location expressed as a number, while a subnet mask decides which neighbouring addresses are considered local and which must be handed to a router for further deliberation. A switch is a device that forwards Ethernet frames between ports it has learned, and a VLAN is a logical grouping of ports that pretend not to share a chassis. You review these with developers, server operators, security staff, and an experienced engineer so everyone can trace how a frame travels before anyone re-patches a cable whose label has been lying with confidence for years.

Suppose a server in rack twelve cannot reach its backup target. In a lab switch with no production load, you read the port configuration, confirm the access VLAN on both ends, trace the uplink, and note that a trunk allowing the wrong set of VLANs is a polite refusal rather than an outage. You record the VLAN mismatch, the native VLAN, and the one cable labelled "temp 2009" that is now carrying production traffic. One tidy diagram is an anecdote with good posture, not an architecture; but it prevents the team from commissioning a second uplink for a problem that was, in the end, a sticker.

Words from the spaceship manual, translated

IP address: A network location expressed as a number, assigned to an interface so other devices can find it. Addresses are plentiful in theory and rationed in practice, and an address you did not document is an address someone else will eventually assign to a printer.
Subnet mask: The value that splits an address into network and host portions, deciding which neighbours are local and which require a router. A mask typed incorrectly is a small typographical error that makes an entire subnet a very remote place.
VLAN: A logical grouping of switch ports that share a broadcast domain without sharing a physical box. VLANs keep traffic apart with the diligence of a librarian who has never been told why the books are separated.
MAC address: The hardware identifier burned into a network interface, used by switches to learn which port a frame lives behind. Switches trust MAC addresses implicitly, which is why a duplicated one causes traffic to commute between two ports with great enthusiasm.