Network administration is keeping a network working: addressing, switching, routing, names, access and monitoring, for an office, a campus or a data centre. The job is mostly designing so that faults are rare and easy to find, and documenting enough that someone else can fix the rest.
Key concepts
- Addressing plan: subnets, VLANs and DHCP laid out so growth does not force a renumbering.
- Switching and routing: switches forward by MAC address inside a segment; routers join segments; VLANs split one switch into several networks.
- Core services: DHCP, DNS and time synchronisation, which almost everything else depends on.
- Access and segmentation: firewalls, access lists and separate zones limit what a mistake or a compromise can reach.
- Monitoring and documentation: SNMP or flow data, logs, diagrams and configuration backups.
Vocabulary
- VLAN: a virtual LAN, a logical network sharing physical switches.
- DHCP: the service that hands out addresses and settings to hosts.
- Spanning tree: the protocol that stops loops in a switched network.
- NAT: translating private addresses to a public one at the edge.
- Change window: an agreed time to alter production safely.
What to study, in order
- Build a home or virtual lab: a router, a switch and a few hosts on separate subnets.
- Set up DHCP, DNS and an internal time source, and break each to see what fails.
- Configure VLANs, inter-VLAN routing and a firewall policy that denies by default.
- Add monitoring: graph interface traffic and alert on a down link.
- Write a runbook and a network diagram, then rebuild the lab from them alone.