Wrap-up and resources
Key Takeaways
- 1. Monitoring the network: SNMP, logs and flows: Collect four things: state (SNMP), events (syslog with one clock from NTP), who talks to whom (flows), and second-by-second detail (streaming telemetry). Build a baseline before you set alert thresholds, and alert only on what needs a human.
- 2. Quality of service: voice first when the link is busy: QoS does not create capacity; it decides who waits when it runs out. Classify at the edge and mark with DSCP, put voice (EF) in a capped priority queue, give the rest fair shares, and shape traffic before the provider's link instead of letting the provider drop it.
- 3. Network automation: a source of truth, templates and checks before change: Good automation starts with data, not with a script: one source of truth, a template per device type, a diff before you push, a check after, and every change in Git reviewed by a colleague. Start with safe read-only tasks before you write.
- 4. Project: a branch with no single point of failure: A resilient network is not proven by a diagram but by testing failure: unplug every device and every link one at a time and time how long service breaks. What you do not test, you do not know works.
Glossary
| Term | Definition | Part |
|---|---|---|
| SNMPv3 | The SNMP version with authentication and encryption (authPriv); polls on 161, traps on 162. | 1 |
| syslog | An event log with eight levels from 0 (emergency) to 7 (debug). | 1 |
| NetFlow / IPFIX | A summary of every conversation: who, to whom, how much. | 1 |
| DSCP | Six bits in the IP header carrying the traffic class. | 2 |
| EF | Expedited Forwarding, value 46, for voice. | 2 |
| LLQ | A strict, capped priority queue for voice. | 2 |
| Source of truth | One place for network data that configs are derived from, such as NetBox. | 3 |
| Drift | A gap that crept in between running and desired through a manual change. | 3 |
| NETCONF | Structured management with XML and YANG on TCP 830 with commit. | 3 |
| Single point of failure | Any piece whose failure stops the service. | 4 |
| Failure test | Failing pieces on purpose and timing the recovery. | 4 |
| BFD | Fast detection of a neighbour failure in fractions of a second. | 4 |
Resources for this lesson
Grouped by type. Start with the official docs for precision, or an article or video for the explanation.
Tools3
reference3
RFC 5424: The Syslog ProtocolDefines the eight severity levels and the message format.rfc-editor.orgRFC 7011: IPFIXThe open standard for exporting flow records.rfc-editor.orgRFC 4594: Configuration Guidelines for DiffServ Service ClassesThe reference table of service classes and the DSCP suggested for each.rfc-editor.org
Done with this lesson?
Sign in to save your progress.