[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Mibble-users] Functionality of SNMPv3
From: |
Birgit Arkesteijn |
Subject: |
Re: [Mibble-users] Functionality of SNMPv3 |
Date: |
Tue, 5 Jul 2005 10:41:14 +0100 |
User-agent: |
Mutt/1.4.1i |
Dear Bubul,
Try giving contextEngineID a (correct) value. Your original posting
mentions you keep it empty.
You might also have to set contextName, like Per did in his example.
However, if contextEngineID is correct and contextName wrong, I do think
you will receive a different error message.
Cheers, Birgit
On Tue, Jul 05, 2005 at 08:59:46AM +0200, Per Cederberg wrote:
> 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 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 other MIB Browser i got the correct result
> > > for SNMPv3. Can any one suggest where am i going wrong and the ways
> > > to get values for
> > > SNMPv3 compatible devices using Mibble MIB Browser.
> > >
> > > Thanks and Regards,
> > > Bubul.
--
-- Birgit Arkesteijn, address@hidden,
-- Westhawk Ltd, Albion Wharf, 19 Albion Street, Manchester M1 5LN, UK
-- tel.: +44 (0)161 237 0660
-- <URL: http://www.westhawk.co.uk>