Mike> The community name you are using for the read only and read write
Mike> access should be different in order to be able to use the snmpset
Mike> command.
That's a slight simplification, but does touch on the heart of the problem.
In particular, you're mixing two different styles of access control.
First of all, you set things up using the individual VACM directives
(although with some duplicate or unnecessary entries):
> > com2sec local localhost public
> > com2sec mynetwork 10.116.20.0/24 public
> > group MyROGroup v1 mynetwork
> > group MyROGroup v2c mynetwork
> > group MyRWGroup v1 mynetwork
> > group MyRWGroup v2c mynetwork
[There's a clash here - you only want *one* of these pairs]
> > group public v2c public
[Drop this line - you haven't defined a com2sec for "public"]
> > group local v2c local
> > view all included .1
> > access MyROGroup "" any noauth exact all none none
> > access MyRWGroup "" any noauth exact all all none
> > access public "" any noauth exact system none none
[Drop this line - the group "public" is empty,
and you haven't defined a view "system"]
> > access local "" any noauth exact all all all
But then you *also* use the "shortcut" access directives,
with the same community name:
> > rwcommunity public
> > rocommunity public
> > rwcommunity public 10.116.20.0/24
This is just going to cause confusion.
Pick one style of working and stick to that - don't try to mix the two.
Plus (as Mike says), you're using the same community string for both
RO and RW access. Again, this won't work properly - use different
community strings.
And one final quibble:
> > trap2sink ipv61 public 162
> > trapsink localhost public
> > trap2sink localhost public
Do you really want to send 3 copies of *every* trap ?
Try with the following snmpd.conf file:
--------------------------
rocommunity public
rwcommunity private
trap2sink localhost public
--------------------------
and use
snmpset -v 2c -c private localhost sysContact.0 s "Jimmy"
Mike also says:
> Moreover
> if you have define the sysContact information in the snmpd.conf file
> then you are not able to set this value with snmpset command.
which is also correct.
But your snmpd.conf file doesn't seem to include such an entry, so this
probably isn't relevant here (assuming you've shown us the whole thing)
Dave
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.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
