liveBook · Manning

SNMP manager

As explained in Acing the CCNA Exam: Volume 2 Advanced Networking and Security

An SNMP manager is the SNMP component on a management system that sends requests to agents and receives their responses and notifications.

An SNMP manager is the SNMP component on a network management system (NMS) that communicates with SNMP agents on managed devices. It sends Get and Set requests, receives responses, and accepts notifications such as Traps. section 6.1.2 section 6.4

Use the message direction and UDP ports to distinguish the manager from the agent:

  • Sends Get requests to read MIB variables and Set requests to modify them or initiate actions such as reboots. section 6.1.2 section 6.4
  • Receives Response and Trap messages from agents on managed devices. section 6.1.2
  • Listens on UDP port 162, while the agent listens for manager requests on UDP port 161. section 6.1.2
  • Uses an SNMP application, often with a GUI, to let an administrator monitor and manage devices. section 6.1.2

Community-based access

With SNMPv1 or SNMPv2c, a manager supplies a community string. A read-only string permits Get, GetNext, and GetBulk requests but rejects Set; a read-write string permits both reading and writing. ACLs can restrict which managers may use each community. section 6.3.1

Figure 6.4 The components of the NMS’s and managed devices’ SNMP entities. The NMS’s SNMP entity consists of the SNMP manager and SNMP application(s). The managed devices’ SNMP entities consist of the SNMP agent and the MIB.

Use the component diagram to distinguish the NMS entity, containing the SNMP manager and application, from each managed device entity, containing the agent and MIB. section 6.1.2

How Acing the CCNA Exam: Volume 2 Advanced Networking and Security covers it

How deep it goes
Explains component placement, message types, ports, applications, and community permissions, but does not develop manager software internals.
Examples
Uses PRTG monitoring, MIB variable queries, OIDs, and Cisco community-string and Trap-destination configuration examples.
What it assumes
Assumes recognition of an NMS and managed device while identifying their SNMP entities and components explicitly.
What you can do after
Operate SNMP monitoring by distinguishing manager and agent roles, selecting message types, checking ports, and interpreting RO/RW access.
How it connects
Connects the SNMP manager with the NMS, SNMP agent, MIB, SNMP application, Get, Set, Response, Trap, and community strings.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Acing the CCNA Exam: Volume 2 Advanced Networking and Security. The section links point to the parts of the book it draws on.