Hosting.com - First Name in Hosting

RFC1592 - Page 29


Page Navigation:

1  2  3  4  5  6  7  8  9  10  11  12  13  14  15  16  17  18  19  20  21  22  23  24  25  26  27  28  29  30  31  32  33  34  35  36  37  38  39  40  41  42  43  44  45  46  47  48  49  50  51  52  53  54 

Printable Version: RFC1592.PDF

<< Prev. Page     Next Page >>

RFC 1592                        SNMP-DPI                      March 1994


3.2.11  RESPONSE

   An SNMP sub-agent must respond to a GET, GETNEXT, GETBULK, SET,
   COMMIT, UNDO or UNREGISTER request that it has received from the
   agent (unless it fails or has a bug ;-)).  To do so, it sends an SNMP
   DPI RESPONSE packet to the agent.

   Such a packet contains the standard SNMP DPI header plus RESPONSE
   specific data:

     o   an error_code,
     o   an error_index,
     o   plus for a successful GET, GETNEXT, or GETBULK, the
         name/type/length/value tuple(s) representing the returned
         object(s).  For each varBind this is described as:

         -   two null terminated strings (in the selected character set)
             representing the group and instance ID in ASN.1 dotted
             notation.
         -   the type, value length and value of the object that is
             returned.

         The permitted types for the type field are defined in Table 17.

         See 3.3.4, "Value Representation" for information on how the
         value data is represented in the packet value field.

   For an unsuccessful GET, GETNEXT or GETBULK, the sub-agent does not
   need to return any name/type/length/value tuple(s), because by
   definition, the varBind information is the same as in the request to
   which this is a response, and the agent still has that information.

   The group ID and the packet ID must always be the same as the
   corresponding fields in request PDU which has prompted the RESPONSE.

   If the response is to a SET, COMMIT or UNDO request, there is no need
   to return any varBind information, because by definition, the varBind
   information is the same as in the request to which this is a
   response, and the agent still has that information.

   If the response is to a REGISTER or UNREGISTER, no variable
   (instance) is being returned, so the instance ID is the NULL string
   (one 0x00 byte).  In the response to a REGISTER request indicating
   success, the error index contains the priority assigned by the agent.

   If the response is to an OPEN, ARE_YOU_THERE or CLOSE, no varBind
   data will be passed, so no group ID, instance ID or value data. The
   packet will only include the header, the error code and the error



Wijnen, Carpenter, Curran, Sehgal & Waters                     [Page 29]


<< Prev. Page     Next Page >>