Re: snmpv3 context question

On 21 December 2010 16:27, aravind narasimhan <[email protected]> wrote:
> createUser public MD5 public123
> rwuser public

If you've got the settings above, then these are sufficient.
You don't need the following block:

> com2sec public  default public
> #com2sec public  default public
> group   mygroup  v1      public
> group   mygroup  v2c     public
> group   mygroup  usm     public
> view    all     included        .1.3.6.1.4.1.2021
> access  mygroup ""      any     noauth  exact   all     none    none

They won't be used for SNMPv3 requests at all.


>       to the agent with the above config
> I tried adding context based on an earlier e-mail thread as below.


> com2sec –Cn ucd public  default public

a)  That sets up a context for SNMPv1/2c requests
     It has no effect on SNMPv3 requests

b)  You would also need to change the MIB module code
     to *register* the information in another context.
     Just tweaking the config file is not sufficient.

Contexts are almost certainly not the solution here.

Dave

------------------------------------------------------------------------------
Forrester recently released a report on the Return on Investment (ROI) of
Google Apps. They found a 300% ROI, 38%-56% cost savings, and break-even
within 7 months.  Over 3 million businesses have gone Google with Google Apps:
an online email calendar, and document program that's accessible from your 
browser. Read the Forrester report: http://p.sf.net/sfu/googleapps-sfnew
_______________________________________________
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