Re: SNMPv3: two request needed to get response(msgAuthoritativeEngineTime)?

Dave Shield <[email protected]>
Newsgroups gmane.network.net-snmp.user
Message-ID <[email protected]>
2009/3/25 mike one <[email protected]>:
> I am facing problem with SNMPv3 authentication on swithes.

> The only difference between 1. and 3 is msgAuthoritativeEngineBoots and msgAuthoritativeEngineTime .

This is normal.
SNMPv3 authentication relies on a synchronisation of "engine uptime"
information between the two sides (to protect against replay attacks).

The first time that the client application tries to query the agent,
it has no idea of what the engineBoot/Time values ought to be,
so sends a "probe" request to discover them.
   This probe is actually a copy of the real request (but with 0 values
for these two fields), and there is no expectation that the request will
succeed.  The purpose is to trigger a failure report message, which
will include the current engineBoot/Time values for the agent,

  The request can then be sent with these two values inserted, and
this should allow the agent to authenticate it successfully.


Any subsequent request from the same management application
should succeed, without the need for another probe (unless the
agent has restarted in the meantime)

Dave

------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.