Week 9 · Lesson 11

SNMP: Network Management

A network manager needs to see thousands of devices at once — their CPU, memory, interface errors, even configuration changes — without logging into each one. SNMP (Simple Network Management Protocol) is the language of that visibility: agents on devices expose standardised variables, and managers poll them or receive unsolicited alerts. This lesson maps the roles, the object model (MIB/OID), the versions and their security, and the IOS commands that enable monitoring.

CCNA 200-301 Domain 4.0 IP Services Verified 2026-10-11
Learning objectives
Part 1

Manager, agent, and the MIB

SNMP is a client–server protocol with two distinct roles. The device being managed runs an SNMP agent — a software service that answers queries about the device’s state. The network management system (NMS) runs the SNMP manager — the software that asks the questions, collects the answers, and draws the dashboards. One manager typically controls many agents.

Definitions — agent and MIB The SNMP agent is a service on the managed device that exposes management data and can send notifications. The Management Information Base (MIB) is a structured database of every variable an agent can report — interface statistics, uptime, CPU load, routing tables, and so on. Each variable in the MIB lives at a precise location called an OID (Object Identifier).

The exam will hand you a scenario (“an NMS in a server farm needs to monitor 200 switches”) and ask which nodes are agents and which is the manager. The switches/routers/servers are agents; the NMS is the manager. MIB is not a physical database file you configure — it is the logical tree of managed objects.

In this lesson · select a part to jump

Key ideas & exam traps · select one

Part 2

OIDs: naming every variable

Every MIB object is addressed by an OID — a dotted hierarchy of numbers that reads like a filesystem path. The top of the tree is managed by the IANA: .1.3.6.1 is the branch for the Internet's management subtree, and the standard MIB lives at .1.3.6.1.2.1 (MIB-II).

OIDNameWhat it reports
.1.3.6.1.2.1.1.3sysUpTimeHow long the device has been running.
.1.3.6.1.2.1.1.5sysNameThe device hostname.
.1.3.6.1.2.1.2.2.1.10ifInOctetsBytes received on an interface.
.1.3.6.1.2.1.1.1sysDescrFull device description and IOS version.
How to read an OID Break it from the left: 1 is ISO, 3 is identified organisations, 6 is the US Department of Defence (the "Internet" branch), 1 is the Internet, 2 is management, and 1 is the MIB-II group. Everything after that identifies the individual object. You do not need to memorise long OIDs for the exam, but you must recognise that an OID is a hierarchical numeric identifier for a MIB object and that vendors also register private branches under .1.3.6.1.4.1 (Cisco is .1.3.6.1.4.1.9) for their own extensions.

A get for an OID returns the value of that object. A get-next walks to the following object — the mechanism managers use to walk an entire table by repeating get-next one object at a time. This is why an NMS can discover a whole interface table without needing a separate request type for “give me everything”.

Part 3

Ports and message types

SNMP uses two well-known UDP ports, and getting them backwards is a favourite trick question:

The messages you must know by name:

MessageDirectionPurpose
getManager → AgentRetrieve the value of one OID.
get-nextManager → AgentRetrieve the next OID in the tree; used to walk tables.
get-bulk (v2/v3)Manager → AgentFetch many values in one request; efficient table loading.
setManager → AgentChange a writable variable (e.g. write a community, enable/disable an interface).
trapAgent → ManagerUnsolicited alert about an event; the manager does not acknowledge it.
informAgent → ManagerLike a trap, but the manager acknowledges receipt (delivery guarantee).
Exam tip — 161 vs 162 When configuring a firewall or access list for SNMP remember: the agent listens on UDP 161 (manager-to-agent poll traffic), and traps go from the agent to the manager on UDP 162. The exam loves the flipped pair — “SNMP traps arrive at UDP 161” is wrong; 161 is for agent polling, 162 is the trap receiver port.
Reference table · select a row

Part 4

Polling vs traps

The manager has two strategies for learning about the network, and the exam expects you to weigh them against each other:

Definition — trap vs inform A trap is a one-way, unacknowledged notification: cheap, but if the UDP packet is dropped the event is lost. An inform is the acknowledged form — the manager sends back a response, so the agent can retransmit when needed. Informs cost more on both sides; that reliability trade-off is the entire exam-worthy difference.

Production monitoring typically uses both together: polls keep the baseline and verify agent liveness, while traps deliver the urgent, event-driven alerting that polling would miss until it was too late. The snmp-server enable traps command decides which classes of events the agent may push.

Switch SW1 (agent) Switch SW2 (agent) Server (agent) NMS (manager) listens for traps on UDP 162 get (UDP 161) responses on UDP 161 trap (agent → manager UDP 162) pushed only when an event happens
Managers poll agents with get requests on UDP 161; agents answer on the same port. When an event occurs, the agent pushes a trap to the manager’s UDP 162 listener instead of waiting for the next poll.
Part 5

v1, v2c, v3 — and the security difference

The three versions the exam cares about differ mostly in how they authenticate. The first two are functionally similar and both insecure by default; v3 is the security rewrite.

VersionSecurityCommunity stringNotes
v1NonePlaintextLegacy. Sends everything, including any set, in cleartext.
v2cNonePlaintextMost common legacy version; adds get-bulk and inform. The "c" marks the community-based access model.
v3AuthN/AuthP (USM)Replaced by user accountsAdds message integrity, authentication (MD5/SHA), optional privacy (AES/DES encryption), and model views. The modern secure choice.
What a community string is A community string is effectively a shared password that an SNMP request must carry so the agent will answer. v1/v2c send it in plaintext — anyone sniffing the network (or reading the MIB with SNMP on UDP 161, no less) can read it. That is why production deployments should use v3, which replaces the string with a real user account plus authentication (the message really came from that user) and privacy (encryption of the payload), selectable per user.

Access control is also granular in v3: a view limits which MIB branches an account may read or write. You can give a monitoring account read-only access to interface statistics and a change account read-write to just the few settable variables that deserve it — an exam-recognised security practice that no amount of community strings can reproduce.

Exam tip — version-versus-version questions Typical forms: “Which SNMP version provides authentication and encryption?” → v3. “Which feature is exclusive to v3?” → message integrity / user-based authentication and privacy (the choice will read like “the agent and manager authenticate the exchanged messages”). “What does the ‘c’ in v2c mean?” → community-based security. The word community itself is the giveaway that a question is about v1/v2c, not v3.
Part 6

Configuring SNMP on IOS

Read-only and read-write community strings, plus a trap destination. The exam-safe baseline for a lab with an NMS at 192.168.1.100:

R1(config)# snmp-server community MyReadOnly RO
R1(config)# snmp-server community MyReadWrite RW
R1(config)# snmp-server location DataCenter Rack 4
R1(config)# snmp-server contact netadmin@example.com

To push traps to the management station, give the agent a destination and enable at least one trap class:

R1(config)# snmp-server host 192.168.1.100 version 2c MyReadOnly
R1(config)# snmp-server enable traps snmp linkdown linkup

The snmp-server host line names the trap receiver, the SNMP version to use for traps, and the community string that the trap will carry. Traps stay off until you enable at least one class, so linkdown/linkup here immediately produce useful notifications for the lab.

The same bottom line as every management protocol SNMP v1/v2c community strings are sent in cleartext — the same reason you would use SSH rather than Telnet. Keep RO (read-only) as the default, reserve RW for accounts that genuinely need it, use long random strings instead of public/private, filter UDP 161/162 at the edge, and prefer v3 with authentication and encryption for anything leaving the management VLAN.
Key terms

The vocabulary you need

Every term below appears in the lesson text above. Select one to read its definition, then use the quiz at the end to check what stuck.

Key terms · select a term

Part 7 · Your turn

Review

Check what you have learned with these review questions.

Review · 5 questions

Sources

Sources & references

  1. Cisco. CCNA (200-301) Exam Topics. cisco.com.
  2. IETF. Request for Comments (RFCs). rfc-editor.org.
  3. IANA. Internet Assigned Numbers Authority registries. iana.org.

Target exams: CCNA 200-301 v1.1 · CyberOps Associate 200-201. Last content verification: 2026-10-11.