Re: Re: SNMPV3 get on target hardware.

[Gurusidhesh Hiremath]

Hello Wes,
Wes>If it's ours, you can run it with -f -L -Dusm and see
Wes>what it says is the problem in the debugging output

usm: USM processing begun...
usm: Unknown Engine ID.
usm: USM processing has begun (offset 52)
usm: getting user
usm: USM processing completed.
usm: USM processing begun...
usm: Verification failed.
Authentication failed for newv3user
usm: USM processing has begun (offset 52)
usm: getting user newv3user
usm: USM processing completed.

To be more specific: I am running snmpd on a Motorola hardware. If I send a get request from Intel processor pc, the authentication fails. And if I send a request from other Motorola processor pc, the request succeeds.
Is it problem with the network byte ordering?. I tried calling MDreverse() after every time MDupdate is called. But still I'm not able to contact the snmpd. Where & when should I call MDreverse?
One more observation is that it only happens whenever MD5 authentication is used. With SHA it works fine.

Guru

On Sun, 12 Dec 2004 Wes Hardaker wrote :
> >>>>> On 7 Dec 2004 05:06:06 -0000, "Gurusidhesh Hiremath" <[EMAIL PROTECTED]> said:
>
>Gurusidhesh> # snmpget -v3 10.1.111.115 -u newv3user -l authNoPriv -a MD5 -A newv3user 1.3.6.1.2.1.1.4.0
>Gurusidhesh> snmpget: Authentication failure (incorrect password, community or key)
>
>Gurusidhesh> I have created the user (newv3user) using command
>Gurusidhesh> net-snmp-config
>
>Gurusidhesh> what could be the reason for this?
>
>I'm not sure.  Is the remote agent (on 10.1.111.115) our agent, or
>someone elses?  If it's ours, you can run it with -f -L -Dusm and see
>what it says is the problem in the debugging output.
>
>Also, you should probably rearrange your arguments so the IP address
>is last.  not all getopt parsers deal with the above quite right.
>Try:
>
>snmpget -v3  -u newv3user -l authNoPriv -a MD5 -A newv3user 10.1.111.115 1.3.6.1.2.1.1.4.0
>
>--
>Wes Hardaker
>Sparta