Hi Jeffrey,
This is the log of the agent when is started in debug mode, and later
Openser is started:
/opt/net-snmp/sbin/snmpd -f -Dagentx -x tcp:localhost:705 2>&1
No log handling enabled - turning on stderr logging
registered debug token agentx, 1
agentx_register_app_config_handler: registering .conf token for
"agentxsocket"
agentx_register_app_config_handler: registering .conf token for
"agentxperms"
agentx_register_app_config_handler: registering .conf token for
"agentxRetries"
agentx_register_app_config_handler: registering .conf token for
"agentxTimeout"
Turning on AgentX master support.
agentx/master: initializing...
agentx/master: initializing... DONE
NET-SNMP version 5.4
agentx/master: unexpected callback op 4
agentx/master: handle pdu (req=0x54fb3d2b,trans=0x0,sess=0x0)
agentx/master: open 0018efc0
agentx/master: opened 001ad130 = 5 with flags = a0
agentx/master: send response, stat 0 (req=0x54fb3d2b,trans=0x0,sess=0x0)
agentx_build: packet built okay
I have tried changing too the keywork agentXsocket to agentXSocket, and with
a minimal snmpd config, and still reports error:
# /opt/net-snmp/bin/snmpwalk -v 2c -c public localhost .1.3.6.1.4.1.27483
OPENSER-REG-MIB::openser = No Such Object available on this agent at this
OID
And the snmpd log:
agentx/master: send response, stat 0 (req=0x54fb3d2f,trans=0x0,sess=0x0)
agentx_build: packet built okay
agentx/master: handle pdu (req=0x54fb3d30,trans=0x0,sess=0x5)
agentx/master: send response, stat 0 (req=0x54fb3d30,trans=0x0,sess=0x5)
agentx_build: packet built okay
Thanks!
On 3/29/07, Jeffrey Magder <jmagder(a)somanetworks.com> wrote:
It looks like there is communication going on between the NetSNMP master
agent, and OpenSER's SNMPStats sub-agent. Would you be able to provide
me some more of the /var/log/snmpd.log snmpd logs? Specifically, I'm
looking for what happens after:
Turning on AgentX master support.
agentx/master: initializing...
agentx/master: initializing... DONE
NET-SNMP version 5.3.1
There should be something similar to the following:
agentx/master: unexpected callback op 4
agentx/master: handle pdu (req=0x1da53a0c,trans=0x0,sess=0x0)
agentx/master: open 0x81137c8
agentx/master: opened 0x814b558 = 6 with flags = a0
agentx/master: send response, stat 0 (req=0x1da53a0c,trans=0x0,sess=0x0)
If thats there, I'm wondering if you have set up any special view
restrictions for certain parts of the OID Tree given a certain community
strings?
Perhaps it would be helpful to rule that out with a minimal snmpd.conf
file containing only:
rocommunity public
master agentx
Finally, I don't think this matters (it doesn't matter on my system),
but could you change:
agentXsocket tcp:localhost:705 ---> agentXSocket tcp:localhost:705
The "S" wasn't capitalized. :-)
Thanks again!
- Jeffrey Magder
Sergio Gutierrez wrote:
Hi Jefrey
Thanks for your answer.
I will reply every point:
# /opt/net-snmp/bin/snmpwalk -v 2c -c community localhost
.1.3.6.1.4.1.27483
OPENSER-REG-MIB::openser = No Such Object available on this agent at
this OID
# ps -ef | grep snmpd
root 1649 579 0 17:50:07 pts/2 0:17
/opt/net-snmp/sbin/snmpd -d -f -Dagentx -x tcp:localhost:705
root 2935 2778 0 09:59:21 pts/3 0:00 grep snmpd
(I am running debug mode; the syntax of ps command is a little bti
different because I am using Solaris)
# grep -i agentx /var/log/snmpd.log
agentx_build: packet built okay
agentx/master: handle pdu (req=0x3ac55fdb,trans=0x0,sess=0xf)
agentx/master: send response, stat 0 (req=0x3ac55fdb,trans=0x0,sess=0xf)
agentx_build: packet built okay
agentx/master: handle pdu (req=0x3ac55fdc,trans=0x0,sess=0xf)
agentx/master: send response, stat 0 (req=0x3ac55fdc,trans=0x0,sess=0xf)
agentx_build: packet built okay
agentx/master: handle pdu (req=0x3ac55fdd,trans=0x0,sess=0xf)
agentx/master: send response, stat 0 (req=0x3ac55fdd,trans=0x0,sess=0xf)
agentx_build: packet built okay
...
# cat /opt/net-snmp/share/snmp/snmpstats.conf
agentXsocket tcp:localhost:705
# cat /opt/net-snmp/share/snmp/snmpd.conf
syslocation XXXX
syscontact XXXX
agentaddress udp:161
rocommunity community localhost
master agentx
As you can see, both of the files are located at the same directory.
Finally, I do have tried the check. I can see Openser starts OK and
the master agent receives the connection of the sub agent.
Thank you very much for your help.
Kind regards.
Sergio G.
On 3/29/07, *jmagder* <jmagder(a)somanetworks.com
<mailto:jmagder@somanetworks.com>> wrote:
Hi Sergio,
First off, could you try running "/opt/net-snmp/bin/snmpwalk -v 2c
-c
community sipserver
.1.3.6.1.4.1.27483"? If that isn't succeeding,
then it would greatly help me debug your problem if you could
answer the
following questions:
1) What is the output of "ps aux | grep snmpd"?
2) What is the output of "cat /var/log/messages | grep AgentX"
3) Can you show me the contents of snmpstats.conf ?
4) Does snmpd.conf contain "master agentx"?
5) Is snmpd.conf located in the same directory as snmpstats.conf?
6) Have you tried the steps in "Testing for a proper
Configuration" in
section 1.6.4?
Thanks Sergio!
- Jeffrey Magder
Sergio Gutierrez wrote:
> Hi list.
>
> I have installed Openser 1.2.0, with Net-snmp version 5.4 to
support
the
SNMPstats module. I have configured the subagent according to
the
> instructions on the documentation, but I am not being able to
obtain
> any data.
>
> I am running both products on Solaris 10 Sparc.
>
> # /opt/net-snmp/bin/snmpwalk -v 2c -c community sipserver
> .1.3.6.1.4.1.27483.3.1.1.1.1.1.1
> SNMPv2-SMI::enterprises.27483.3.1.1.1.1.1 = No Such Object
available
> on this agent at this OID
>
> # /opt/net-snmp/bin/snmpwalk -v 2c -c community sipserver
> openserSIPProtocolVersion
> SNMPv2-SMI::enterprises.27483.3.1.1.1.1.1 = No Such Object
available
on this
agent at this OID
Is there any other thing I should do after compiling and
configuring?
>
> Thanks in advance for your attention
>
> Kind Regards.
>
> Sergio Gutiérrez
>
>
>
>
------------------------------------------------------------------------
_______________________________________________
Users mailing list
Users(a)openser.org <mailto:Users@openser.org>
http://openser.org/cgi-bin/mailman/listinfo/users