[AGENT++] Response to wrong snmpEngineId

[Frank Fock]

Marcus,

Are you sure that the engine ID is not already known by the agent?
Anyway, I will have a look at the sources...

Best regards,
Frank

Fehde, Marcus wrote:

>Hi,
> 
>I observed that the SNMP agent responses a report to a message containing a wrong snmpEngineId.
>This happened accidently, but as far as I know the command responder / message processor should response a report containing an "usmStatsUnknownEngineIDs" varbind (1.3.6.1.6.3.15.1.1.4.0).
>But the report contained an "usmStatsUnknownUserNames" varbind (1.3.6.1.6.3.15.1.1.3.0) instead.
>After forcing a new discovery in order to synchronize the engines everthing if fine again.
>Unfortunately I'm not able to activate the agent locking. I analyzed this only with Packetyzer. The Agent++ version is 3.5.22 compiled for the Win32 target.
> 
>Best regards/Mit freundlichen Gruessen 
>
>Marcus Fehde
>Dipl. Ing. Technische Informatik (FH)
>
>Research & Development 
>Business Unit Perioperative Care 
>_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
>
>DRÄGER MEDICAL 
>
>Dräger Medical AG & Co. KG
>Moislinger Allee 53-55 
>D-23542 Lübeck 
>
>Tel:  + 49-451-882-3646 
>Fax: + 49-451-882-4410 
>E-mail: marcus.fehde at draeger.com 
>www.draeger-medical.com 
>_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
>
> 
>
> 
>
> 
>
> 
> 
>  
>
>------------------------------------------------------------------------
>
>_______________________________________________
>AGENTPP mailing list
>AGENTPP at agentpp.org
>http://lists.agentpp.org/mailman/listinfo/agentpp
>  
>


-- 
AGENT++
http://www.agentpp.com
http://www.mibexplorer.com
http://www.mibdesigner.com