On Wed, 2005-06-08 at 18:42, Toth, Gregory S wrote: > We are running an application where we manage retrys of snmp requests > rather than defining the retrys in the session..... > we decided maybe if we could send all > the retrys out with the same request id as the original request.... > > Should we even be attempting this?
Which version of SNMP are you using? In terms of the "requestID" field, RFC 1905 states (in section 4.1): The value of the request-id field in a Response-PDU takes the value of the request-id field in the request PDU to which it is a response. By use of the request-id value, a SNMPv2 application can distinguish the (potentially multiple) outstanding requests, and thereby correlate incoming responses with outstanding requests. In cases where an unreliable datagram service is used, the request-id also provides a simple means of identifying messages duplicated by the network. Use of the same request-id on a retransmission of a request allows the response to either the original transmission or the retransmission to satisfy the request. However, in order to calculate the round trip time for transmission and processing of a request-response transaction, the SNMPv2 application needs to use a different request-id value on a retransmitted request. The latter strategy is recommended for use in the majority of situations. and this text is repeated in RFC 3416 SNMPv3 introduced the idea of a (separate) "msgID", which *must* be unique for retransmissions. (RFC 3412, section 6.2) Dave ------------------------------------------------------- This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput a projector? How fast can you ride your desk chair down the office luge track? If you want to score the big prize, get to know the little guy. Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
