SNMP
An IETF protocol, defined in RFC 1157, by which networked devices can be periodically polled for information as part of a network management system.
The basic communication architecture of SNMP is straightforward; there are three types of requests and one unsolicited information transmission.
To get information from an SNMP device, a "manager" (SNMP terminology for a client) will send a "GetRequest" or "GetNextRequest" to an "agent" (the SNMP term for a server) and the requested information or an error message will be sent back in a "Response." If a manager wants to modify information on an agent, a "SetRequest" will be sent with a corresponding response to confirm or report an error.
The unsolicited message form is called a "trap." This kind of message is usually sent by agents on start-up, on status change and in response to error conditions. Traps are not only unsolicited but they are also unreliable. Like syslog messages they are sent via User Datagram Protocol and whether they are received depends on whether they make it to the destination (remember, UDP is an unreliable, best-effort service) and whether the manager is listening.
The information on the agent is stored in what is called a Management Information Base (MIB). This is a hierarchical data structure (not, as it is often mistakenly called, a database) that describes all the "objects" that a device can report the status of and, in some cases, set the value of.
From Logging messages with SNMP, Network World, 07/01/02.
Also see SNMPv3.
Additional resources
Topic: Management
Latest management news, analysis and newsletters from Network World Fusion.
Comments:
comment
by Y Srinivas Reddy
Perfect. The small paragraph explains neatly the terminology and the basic architecture precisely.
Add a comment
Network World on Twitter: Get our tweets and stay plugged in to networking news
