| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
SNMP Protocol Basic Request/Response Information Poll Using GetRequest and (Get)Response Messages The obvious place to begin our detailed look at SNMP protocol operations is with the simplest type of information exchange. This would be a simple poll operation to read one or more management information variables, used by one SNMP entity (typically an SNMP manager) to request or read information from another entity (normally an SNMP agent on a managed device). SNMP implements this as a simple two-message request/response protocol exchange, similar the request/reply processes found in so many TCP/IP protocols. This information request process typically begins with the user of an application wanting to check the status of a device or look at information about it. As we've seen, all this information is stored on the device in the form of MIB objects. The communication, therefore, takes the form of a request for particular MIB objects and a reply from the device containing those objects' values. In simplified form, the steps in the process are as follows (and as shown in Figure 274):
The Response-PDU message is called GetResponse-PDU in SNMPv1. Presumably, this name was chosen from the fact that it was a response to a get operation, to make the names GetRequest-PDU and GetResponse-PDU somewhat symmetric. The problem is that this name is confusing, for two reasons. First, it sounds to some people like the purpose of the PDU is to get a response. Second, the GetResponse-PDU was also defined as the response message for operations other than gets, including the reply message for SetRequest-PDU. Having a GetResponse message be sent in reply to a SetRequest is disconcerting; the new name is more generic and avoids these problems.
Home - Table Of Contents - Contact Us The TCP/IP Guide (http://www.TCPIPGuide.com) Version 3.0 - Version Date: September 20, 2005 © Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved. Not responsible for any loss resulting from the use of this site. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||