Asset Inventory, Baselines, SLAs, SOPs, and Runbooks
Key Takeaways
- Asset inventory identifies what exists, where it is, who owns it, how it is supported, and whether it is still in scope.
- Baselines define normal configuration or performance so teams can detect drift and abnormal behavior.
- SLAs define service expectations such as availability, response time, resolution targets, and escalation terms.
- SOPs standardize routine work, while runbooks provide step-by-step procedures for operational tasks and incident response.
- Operational records should be version controlled, reviewed, and updated after changes, incidents, and lessons learned.
Network operations is easier when teams can answer basic questions quickly: what devices exist, what normal looks like, what service level is promised, and what procedure should be followed.
Asset Inventory
An asset inventory is the authoritative list of network-related items. It may live in a CMDB, inventory tool, IPAM platform, endpoint management system, or ticketing system.
| Inventory field | Example |
|---|---|
| Asset ID | NET-SW-IDF2-004 |
| Device type | Access switch |
| Manufacturer and model | Switch model and hardware revision |
| Serial number | Vendor serial for support |
| Location | Building, floor, room, rack, RU |
| Owner | Network operations |
| Support status | Covered by maintenance contract through a specific date |
| Software version | Current network operating system or firmware |
| Criticality | Core, distribution, access, lab, or spare |
Inventory quality matters because every other operation depends on it. Patch planning, contract renewal, vulnerability response, incident triage, capacity planning, and decommissioning all start with knowing what exists.
Baselines
A baseline is a documented normal state. It can describe configuration, performance, traffic, or security posture. Baselines let teams recognize drift or abnormal behavior.
| Baseline type | Examples |
|---|---|
| Configuration baseline | Approved firmware, NTP servers, SNMP settings, syslog destination, AAA method |
| Performance baseline | Typical CPU, memory, interface utilization, latency, jitter, packet loss |
| Traffic baseline | Normal application flows, busy-hour bandwidth, expected protocols |
| Wireless baseline | Normal RSSI, SNR, channel utilization, client counts |
Baselines should be measured during normal business cycles. A baseline taken at midnight may not represent a busy call center at 10 a.m. A baseline taken during a known outage should not be treated as healthy.
SLAs, SLOs, and Support Expectations
An SLA is a formal service level agreement. It commonly defines availability targets, support hours, response time, resolution targets, maintenance windows, reporting, and escalation. Internal teams may also use service level objectives or operating level agreements to define expectations between departments.
| Term | Meaning |
|---|---|
| SLA | Agreement with a customer or service consumer |
| SLO | Target objective used to measure service quality |
| OLA | Internal support agreement between teams |
| Maintenance window | Approved time for planned service impact |
| Escalation path | Who is contacted when targets are at risk |
SOPs and Runbooks
Standard operating procedures describe repeatable routine work. Runbooks are more task-specific and often include exact commands, checks, decision points, rollback steps, and escalation contacts.
| Document | Best use |
|---|---|
| SOP | Monthly firewall rule review process |
| Runbook | Steps to fail over a WAN circuit |
| Checklist | Pre-change validation items |
| Escalation matrix | Who to contact based on severity and system |
A good runbook includes prerequisites, required access, expected output, verification steps, rollback instructions, and evidence to attach to a ticket. It should also be tested. A runbook that has never been practiced may fail during a real outage.
Practical Scenario
A monitoring alert shows high latency across a WAN link. The team checks the inventory to identify the circuit and provider, compares current metrics to the baseline, reviews the SLA for provider response expectations, opens a ticket, and follows the runbook for collecting evidence and escalating if thresholds are exceeded.
Common Exam Traps
| Trap | Better exam reasoning |
|---|---|
| "Inventory is only for accounting." | Inventory supports supportability, security, troubleshooting, and lifecycle decisions. |
| "A baseline is a maximum limit." | A baseline is normal behavior used for comparison, not necessarily a hard threshold. |
| "An SLA is the same as a runbook." | An SLA defines service expectations; a runbook tells operators what steps to perform. |
| "SOPs should live only in one engineer's notes." | Procedures need shared access, ownership, review, and version control. |
Quick Drill
Match the need:
- Determine whether interface utilization is unusual: performance baseline.
- Find the serial number for a failed switch: asset inventory.
- Know whether a provider must respond within one hour: SLA.
- Replace a failed firewall using approved steps: runbook.
- Define the recurring process for reviewing access rules: SOP.
A router CPU normally runs between 20 and 35 percent during business hours. Today it is steady at 92 percent. What operational record makes that comparison meaningful?
Which items are typical asset inventory fields? Choose two.
Select all that apply
Which document is most likely to contain step-by-step instructions, validation checks, and rollback steps for failing over a WAN connection?