Re: [Mibble-users] Functionality of SNMPv3

[Per Cederberg]

That sounds strange. I just used the SNMPv3 support in the Mibble
Browser to access a public test server. It worked without any
problems for all auth/privacy combinations available:

http://www.mg-soft.si/snmpv3.html#SNMPv3ACCESS

IP Address:    212.30.73.70
SNMP Port:     161
ContextName:   public
UserName:      noAuthUser

So, maybe there is something wrong with the agent? A clue to the
issue can be found in the definition for "snmpUnknownPDUHandlers"
OID that is returned:

snmpUnknownPDUHandlers OBJECT-TYPE
    SYNTAX       Counter32
    MAX-ACCESS   read-only
    STATUS       current
    DESCRIPTION "The total number of packets received by the SNMP
                 engine which were dropped because the PDU contained
                 in the packet could not be passed to an application
                 responsible for handling the pduType, e.g. no SNMP
                 application had registered for the proper
                 combination of the contextEngineID and the pduType.
                "
    ::= { snmpMPDStats 3 }

Mibble uses the Westhawk SNMP stack for all the SNMP protocol
operations. It has been in use for quite some time and should be
quite stable. I haven't heard of any bug reports regarding its
SNMP support.

Cheers,

/Per

On tue, 2005-07-05 at 05:36 +0100, Bubul Ghoshal wrote:
> Hi Per,
>   In the OID field i used the OID 1.3.6.1.2.1.1.5 for "sysName". But
> after the response the OID value is getting changed
> to  1.3.6.1.6.3.11.2.1.3 and giving wrong value. I also tried with the
> GETNEXT operation, but it also produces the same result and every the
> value is incremented by one. But from other MIB Browser i am getting a
> correct response.
>    Can you please tell me the general steps i need to follow to get an
> OID value using SNMPv3.
>  
> Thanks,
> Bubul.
> 
> Per Cederberg <address@hidden> wrote:
>         Hi,
>         
>         Try using GetNext instead of Get and see what the agent
>         returns in that case.
>         
>         Also, the OID specified seems wrong. OID 1.3.6.1.6.3.11.2.1.3
>         corresponds to "snmpUnknownPDUHandlers" in SNMP-MPD-MIB. The
>         "sysName" field in SNMPv2-MIB instead has OID 1.3.6.1.2.1.1.5.
>         
>         Cheers,
>         
>         /Per
>         
>         On mon, 2005-07-04 at 15:14 +0100, Bubul Ghoshal wrote:
>         > Hi,
>         > I just wanted to test the working of SNMPv3. So i chose
>         Mibble MIB
>         > Browser. I did the following settings
>         > Host IP Address : 172.16.2.112
>         > Port Number : 161
>         > UserName : ss
>         > Authentication : None
>         > Privacy : None
>         > Context Name : 
>         > Context Engine :
>         > When i tried to get the value for "sysName", the OID value
>         was
>         > changed to 1.3.6.1.6.3.11.2.1.3.0 and i got a value 6441 as
>         shown in
>         > the output
>         > GET: 1.3.6.1.6.3.11.2.1.3.0: 6441
>         > But when i performed the same operation for the same
>         configuration
>         > using some othe MIB Browser i got the correct result for
>         SNMPv3. Can
>         > any one sugest where am i going wrong and the ways to get
>         values for
>         > SNMPv3 compatible devices using Mibble MIB Browser.
>         > 
>         > Thanks and Regards,
>         > Bubul.