Chapters0/30 ▾
0 of 30 lessons finished
- 1.Models, Media & Topologies0/5
- 2.IP Addressing, Subnetting & Routing0/5
- 3.Ports, Protocols & Services0/5
- 4.Network Operations0/5
- 5.Network Security0/5
- 6.Network Troubleshooting0/5
Chapter 4 · Lesson 2 of 5
Monitoring with baselines, SNMP and syslog
1 min read
A number means nothing until you compare it with normal. A performance baseline records typical utilization, latency and errors across peak and quiet periods, so 45% on an uplink can be judged as usual or alarming. Do not confuse it with a configuration baseline, or golden configuration, which records approved settings rather than metric ranges.
- SNMPv3 at the authPriv level both authenticates and encrypts. authNoPriv only authenticates, and noAuthNoPriv does neither. A v2c community string is a cleartext shared password, however unusual its value.
- A trap is fire-and-forget. An inform must be acknowledged by the manager, so the agent can resend it if it was lost.
- Syslog severity runs from 0 Emergency through Alert, Critical, Error, Warning, Notice and Informational to 7 Debug.
Example: a design says a switch must report a link failure on its own and must know the report arrived. A scheduled GET is manager-initiated and a trap gives no delivery confirmation, so the answer is an inform.
Check yourself
1. In the syslog severity scale, which numeric value and label identify the most severe condition a device can report?
2. Users report that the network 'feels slow.' Monitoring shows the main uplink averaging 45% utilization and round-trip latency of 12 ms. What does the team need in order to decide whether these figures actually represent a problem?
Facts checked 2026-11-16 · Sources: CompTIA Network+ certification overview, RFC 5424: The Syslog Protocol, NIST SP 800-34 Rev. 1: Contingency Planning Guide for Federal Information Systems
CompTIA Network+ cheat sheet: every key fact on one page →