Simple explanation
Two related practices: the hands-on process of configuring a device, and the broader discipline of managing configuration consistently and safely over time.
Technical explanation
Basic device configuration procedures:
- Console access — a direct, out-of-band connection to a device for initial setup, used specifically because it works even before the device has network connectivity configured.
- Initial setup — hostname, management IP, default gateway, and basic security (changing default credentials) are typically the first things configured on any new device.
- Firmware updates — keeping device software current, following proper change management (tested, scheduled, with a rollback plan).
- Configuration backup — saving a device's running configuration so it can be restored if something goes wrong.
Configuration management concepts:
- Version control — tracking configuration changes over time, so any change can be reviewed, audited, or rolled back.
- Configuration drift — when a device's actual running configuration diverges from its documented baseline over time, often through undocumented one-off changes.
- Automation/scripting for configuration — applying changes consistently across many devices via scripts rather than manual, error-prone repetition on each device individually.
- IaC (Infrastructure as Code) — defining network configuration as version-controlled code, deployed and validated automatically rather than manually.
Synonyms / related terms
| Term | Means | |---|---| | Out-of-band management | Managing a device through a dedicated channel separate from its normal data traffic path | | Configuration drift | Divergence from the documented baseline over time | | IaC | Infrastructure as Code |
Concept Check
"A network engineer needs to configure a brand-new switch that has no IP address and isn't yet connected to the network." Remote management (SSH, web GUI) isn't an option here since the device has no network connectivity yet — console access (a direct physical/serial connection) is the only method that works for genuinely initial configuration.
Interview-style Q&A
Q: Why does configuration drift matter even when the "drifted" change was actually a reasonable fix at the time? A: "Even a reasonable one-off fix, if undocumented, breaks the reliability of your baseline as a source of truth. Six months later, nobody remembers why that setting is different, whether it's still needed, or whether it's safe to standardize away. The problem isn't that the change was wrong — it's that untracked change accumulates into a configuration nobody fully understands anymore."
Memory trick
"Console first, Config always, Backup before Change" — the operational discipline in three phrases: initial access method, ongoing management practice, and the safety net before any modification.