[SOLVED]: the accurate description of the snmp error

Hi Dave,

Thank you! I got it.

> With SNMPv1, a read-only community (not user) trying to
> SET a value will result in a noSuchName error.

I still think noSuchName is not a suitable error type for this case.

BR

yolanda

-----Original Message-----
From: Dave Shield [mailto:[email protected]] 
Sent: 2005年9月19日 16:18
To: Ying Wang(CD)
Cc: [email protected]
Subject: Re: the accurate description of the snmp error

On Mon, 2005-09-19 at 13:49 +0800, Ying Wang(CD) wrote:
> Where can I find the accurate description of the snmp error? 

In the SNMP specification documents - RFC 1157 for SNMPv1,
RFC 1905 for SNMPv2c, RFCs 3414 and 3416 for SNMPv3/USM.


> Which error is right when a invalid user to access mib,
> such as a SNMPv1 read-only user does a configuration,
> or a unknown user read something?

With SNMPv1, a read-only community (not user) trying to
SET a value will result in a noSuchName error.
With SNMPv2c (or SNMPv3), a read-only community (or user)
trying to SET a value will result in a noAccess error.

With SNMPv1 and SNMPv2c, a completely unknown community will
be silently dropped, and no response will be returned at all.
With SNMPv3, this will return an authenticationFailure
report.



See the RFCs for the full gory details.

Dave


-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. 
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
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