What is the proper behavior for a GET when MFD_SKIP is returned?

"Tom Cumming" <[email protected]>
Newsgroups gmane.network.net-snmp.user
Message-ID <[email protected]>
I am writing an agent using 5.2.1 and mib2c/mfd. If my agent 
receives a GET request, but the column has not been implemented yet, I 
return MFD_SKIP. If I use snmpget to kick off a GET request, the 
*_interface.c code returns ASN_PRIV_RETRY and no error. This ends up 
causing retries, until snmpget timesout. I know that the snmp protocol 
isn't all that smart, but timing out seems a bit much.

    What should the proper behavior be? I would think that if I'm 
receiving a GET request, then I should go down the same path as 
MFD_ERROR, or something.... If so, is the proper place to check in the 
mib2c generated *_interface.c code?

    Thanx, tom.c
--------------------------------------------------------

CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and contains information that is confidential and proprietary to Applied Micro Circuits Corporation or its subsidiaries. It is to be used solely for the purpose of furthering the parties' business relationship. All unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.