[snmp] Recieved Engine ID is not correct

[Birgit Arkesteijn]

Hi Tausif,

When using SNMPv3, the stack discovers the engineId by asking the
authoritative engine for it. If authentication or privacy is used, it
will then ask for the timeline details as well.

It does this once at the beginning. (It will repeat it only when
unsuccessful.) The details are stored for the remaining of the stack
lifetime.

In your case, the stack complains that the discovered engineId and the
one sent (by the authoritative engine) as part of a subsequent request
are not the same. 

However, you said so yourself: there is a mis-match.

The engineId is supposed to uniquely identify an authoritative engine, 
i.e. it's not supposed to change.

The only option I see is to stop/start the stack. 

If that doesn't work: 
Call AsnObject.setDebug(5), the stack will then print the engineId (and
timeline details if using authentication or privacy) it stores.  See
what you get when doing discovery.

Cheers, Birgit


On Mon, Mar 26, 2007 at 04:04:56PM +0530, tausifk wrote:
> All,
> 
> I am getting an exception - "Received engine Id ('80001F88800C330000999E0746') is not correct"
> 
> The scenario is, I run my snmp manager (Westhawk API) and fetched the snmpv3 information from an Net-SNMP agent running on a particular device. Now my manager is still up and running and I re-install the Net-SNMP agent and configure the same user with same credentials as before. Now I again try to do snmpv3 ping and get this exception:
> 
> =================================================================================
> snmpgetV3.start() PduException: Received engine Id ('80001F88800C330000999E0746') is not correct. amIAuthoritative == false
> snmpgetV3.start() PduException: 
> uk.co.westhawk.snmp.stack.DecodingException: Received engine Id ('80001F88800C330000999E0746') is not correct. amIAuthoritative == false
>  at uk.co.westhawk.snmp.stack.AsnDecoderv3.processSNMPv3(AsnDecoderv3.java:176)
>  at uk.co.westhawk.snmp.stack.SnmpContextv3Basis.processIncomingResponse(SnmpContextv3Basis.java:812)
>  at uk.co.westhawk.snmp.stack.AbstractSnmpContext.run(AbstractSnmpContext.java:545)
>  at java.lang.Thread.run(Thread.java:534)
> 
> =================================================================================
> 
> 
> I understand that the re-installation of Net-SNMP agent re-generate the engine-id and my snmp manager cached the engine-ID before when I did snmpv3 ping and there is a mis-match.
> 
> Please do let me know is there any bug with SNMP-Westhawk API or it is a wrong behaviour of Net-SNMP agent which is re-generating the different engine-id?
> 
> I am using Westhawk SNMP 5.1 version for my snmp Manager.
> 
> Thanks in advance
> Tausif
> 
> _______________________________________________
> snmp mailing list
> snmp at snmp.westhawk.co.uk
> http://snmp.westhawk.co.uk/mailman/listinfo/snmp

-- 
-- Birgit Arkesteijn, birgit at westhawk.co.uk,
-- Westhawk Ltd, Albion Wharf, 19 Albion Street, Manchester M1 5LN, UK
-- Company no: 1769350
-- Registered Office: 
-- 15 London Road, Stockton Heath, Warrington WA4 6SJ. UK.
-- tel.: +44 (0)161 237 0660
-- <URL: http://www.westhawk.co.uk>