[SNMP4J] WARN Access denied by VACM for 1.3.6.1.6.3.1.1.5.1

[Saraswat, Deepak]

Hi Tony,
 
I am getting a Similar error like:
 
access Access denied by VACM for 1.3.6.1.6.3.1.1.5.1
13:37:34,443 INFO  [STDOUT] 81858 [SNMP] WARN
org.snmp4j.agent.mo.snmp.NotificationOriginatorImpl  - Access denied by
VACM for 1.3.6.1.6.3.1.1.5.1
 
And then the trap I generated is getting dropped. Could someone help me
to troubleShooted it.
 
Thanks for your help in advance.
 
Regards,
Deepak
 

Tony Willett tonywillett at hotmail.com
<mailto:snmp4j%40agentpp.org?Subject=%5BSNMP4J%5D%20WARN%20%20Access%20d
enied%20by%20VACM%20for%201.3.6.1.6.3.1.1.5.1&In-Reply-To=> 
Tue Jan 9 19:15:29 CET 2007 

*	Previous message: [SNMP4J] Latest snmp4j-agent-1.1RC1 Release
<http://lists.agentpp.org/pipermail/snmp4j/2007-January/001877.html> 
*	Next message: [SNMP4J] decode hexa from traps
<http://lists.agentpp.org/pipermail/snmp4j/2007-January/001879.html> 
*	Messages sorted by: [ date ]
<http://lists.agentpp.org/pipermail/snmp4j/2007-January/date.html#1872>
[ thread ]
<http://lists.agentpp.org/pipermail/snmp4j/2007-January/thread.html#1872
>  [ subject ]
<http://lists.agentpp.org/pipermail/snmp4j/2007-January/subject.html#187
2>  [ author ]
<http://lists.agentpp.org/pipermail/snmp4j/2007-January/author.html#1872
>  

________________________________

 
I am working on setting up a SNMPv3 Agent and I noticed in the log that
I get a warning about access denied to the OID 1.3.1.6.1.6.3.1.1.5.1
when setting up the VACM and USM user. What does this mean exactly and
is it a problem. My agent seems to work with my v3 client.
 
01/09 09:44:06.041 main       INFO  Notification 1.3.6.1.6.3.1.1.5.1
issued with []
01/09 09:44:06.041 main       DEBUG VACM access requested for context=,
securityName=yyyyyy, securityModel=3, securityLevel=3, viewType=0,
OID=1.3.6.1.6.3.1.1.5.1
01/09 09:44:06.042 main       DEBUG Found group name 'xxxxxx' for
secName 'yyyyyy' and secModel 3
01/09 09:44:06.043 main       DEBUG Got views
[DefaultMOMutableRow2PC[index=8.111.112.116.101.99.104.71.80.0.3.3,value
s=[1, fullReadWriteView, fullReadWriteView, fullReadWriteView, 3, 1]]
for group name 'zzzzzz'
01/09 09:44:06.043 main       DEBUG Matching view found for group name
'zzzzzz' is 'fullReadWriteView'
01/09 09:44:06.043 main       WARN  Access denied by VACM for
1.3.6.1.6.3.1.1.5.1
01/09 09:44:06.043 main       INFO  Successful initialition...
 
 
The code goes something like this in the agent:
 
/**
* Adds all the necessary initial users to the USM.
* @param usm
* the USM instance used by this agent.
*/
protected void addUsmUser(USM usm)
{
UsmUser user = new UsmUser(_secName, AuthMD5.ID, _authPass, PrivDES.ID,
_privPass);
_logger.writeInfo("CCSnmpAgent.addUsmUser()", "Adding user " +
user.getSecurityName().toString());
usm.addUser(_secName, new OctetString(localEngineID), user);
_logger.writeInfo("CCSnmpAgent.addUsmUser()", "Added user " +
user.getSecurityName().toString());
}
 
 
/**
* Adds initial VACM configuration.
* @param vacmMIB
* the VacmMIB holding the agent's view configuration.
*/
protected void addViews(VacmMIB vacm)
{
vacm.addGroup(SecurityModel.SECURITY_MODEL_USM, _secName, _v3Group,
StorageType.nonVolatile);
 
vacm.addAccess(_v3Group, new OctetString(),
SecurityModel.SECURITY_MODEL_USM,
SecurityLevel.AUTH_PRIV,
MutableVACM.VACM_MATCH_EXACT,
new OctetString("fullReadWriteView"),
new OctetString("fullReadWriteView"),
new OctetString("fullReadWriteView"),
StorageType.nonVolatile);
 
vacm.addViewTreeFamily(new OctetString("fullReadWriteView"), new
OID(NCSnmpUtils.NCLinkMonitorRootOID),
new OctetString(), VacmMIB.vacmViewIncluded,
StorageType.nonVolatile);
}
 
I am doing some background questions before in hopes I find an issue
where I have one application connecting without a problem and getting
and setting when another application fails (sometimes) and it is using
an instance of the exact same "client" class that abstracts all the snmp
stuff. I will possibly post other question about this.
 
Thanks in advance,
 
Tony