Hi Dave,
It is working fine now. Thank you very much for your great support.
Best regards
Nicolas Cogne
Dave Shield a écrit :
On Thu, 2006-01-19 at 17:49 +0100, Nicolas Cogne wrote:
What does
snmpget -v 1 -c public localhost:7071 .1.3.6.1.4.1.2390.1.3.1.1.0
give?
my subagent answers correctly:
OK - so the problem is on the master agent side.
I send you back the two configuration files:
snmpd.conf for the master agent (5.1.2 master agent).
subagent.conf for the subagent (4.2.3 subagent).
OK - I think I've spotted the problem.
Or to be strictly accurate, the *two* problems.
In the "snmpd.conf" file you have the following:
# sec.name source community
com2sec notConfigUser default public
com2sec localro default public
So there are two security names specified for the
communmity name "public" (not counting the host
specific one).
These get mapped to "notConfigGroup" and "localrogp"
respectively, when then use the following access
settings:
access notConfigGroup "" any noauth exact systemview ....
access localrogp "" any noauth exact ferma ....
I assume that you want "public" requests to use the
localro/localrogp entries, but the agent is probably
picking up the first match ("notConfig*") instead.
So the master agent is allowing access to the system group (and
hrSystem) - but nothing else. That's the first problem - you
need to get rid of the notConfig* settings.
The second problem is that I can't immediately spot where
the view "ferma" is defined. So I strongly suspect that
this view does not exist, and the "localro*" settings won't
work either. You need to define an appropriate view "ferma".
Quite honestly, I wouldn't recommend that you use the
com2sec/group/view/access settings at all. It's a lot
simpler to use the basic "rocommunity"/"rwcommunity"
directives instead. That way you only need one line,
not five or more.
Dave
|
