Hello all,
I am currently trying to get the snmpstats module up and running, for monitoring purposes.
I followed the instructions in the module documentation, I studied Net-SNMP references and I searched web resources for several days now, but still I couldn't succeed in starting the openser module properly. I have no idea what the problem could be.
The NET-SNMP part of the equation seams to work properly: I am using the 5.4.1 version. I managed to play around with the tools from the package, in local and remote scenarios too. I was able to send and receive traps, get and set different values in the MIB tree, load new MIBs...
On the openser part, I'm not doing something special. I have a config file that does nothing, except load the snmpstats module and set the limits for the dialogs and the unparsed data traps. That's it. I tried with fork on yes and on no, because I found out from my web searches that this could be a problem, but all I got was some logging in the no fork scenario, saying that the snmp agent from snmpstats could not connect to the master agent, the snmpd that runs on the same machine. The "check for a proper configuration" step in the module documentation failed also, before this (I got no output in the snmpd window after openser was started, until that point, everything was like in the documentation), so this couldn't work actually, but i still did it anyway.
The problem must be in the configuration files, but it escapes me. This is the content of the files (yes, both in the same location...):
snmpd.conf ----------------------------------- com2sec notConfigUser default public group notConfigGroup v1 notConfigUser group notConfigGroup v2c notConfigUser view systemview included .1.3.6.1.2.1.1 view systemview included .1.3.6.1.2.1.25.1.1 access notConfigGroup "" any noauth exact systemview none none syslocation localhost (edit /etc/snmp/snmpd.conf) syscontact Root root@localhost (configure /etc/snmp/snmp.local.conf) pass .1.3.6.1.4.1.4413.4.1 /usr/bin/ucd5820stat rocommunity public localhost trapsink localhost:162 public trap2sink localhost:162 public authtrapenable 1 master agentx ----------------------------------------------
snmpstats.conf ------------------------------- agentXSocket tcp:localhost:705 ----------------------------------------------
And the way I start snmpd now is: snmpd -f -Lo -M /usr/local/share/mibs -m ALL -d -x tcp:localhost:705 I did try several versions including the one found in the module documentation.
This is the context of my problem. Hopping that there is a small, but obvious mistake, in my config files, due to my lack of attention or something, and not a more serious thing, I thank you for your time.
Gabriel Mahu
--------------------------------- Check out the hottest 2008 models today at Yahoo! Autos.
Hi Gabi,
a know issue (now fixed) is that you need to run with "fork=yes" in order to initialize correctly the agentx on openser side.
regards, bogdan
Gabi Mahu wrote:
Hello all,
I am currently trying to get the snmpstats module up and running, for monitoring purposes.
I followed the instructions in the module documentation, I studied Net-SNMP references and I searched web resources for several days now, but still I couldn't succeed in starting the openser module properly. I have no idea what the problem could be.
The NET-SNMP part of the equation seams to work properly: I am using the 5.4.1 version. I managed to play around with the tools from the package, in local and remote scenarios too. I was able to send and receive traps, get and set different values in the MIB tree, load new MIBs...
On the openser part, I'm not doing something special. I have a config file that does nothing, except load the snmpstats module and set the limits for the dialogs and the unparsed data traps. That's it. I tried with fork on yes and on no, because I found out from my web searches that this could be a problem, but all I got was some logging in the no fork scenario, saying that the snmp agent from snmpstats could not connect to the master agent, the snmpd that runs on the same machine. The "check for a proper configuration" step in the module documentation failed also, before this (I got no output in the snmpd window after openser was started, until that point, everything was like in the documentation), so this couldn't work actually, but i still did it anyway.
The problem must be in the configuration files, but it escapes me. This is the content of the files (yes, both in the same location...):
snmpd.conf ----------------------------------- com2sec notConfigUser default public group notConfigGroup v1 notConfigUser group notConfigGroup v2c notConfigUser view systemview included .1.3.6.1.2.1.1 view systemview included .1.3.6.1.2.1.25.1.1 access notConfigGroup "" any noauth exact systemview none none syslocation localhost (edit /etc/snmp/snmpd.conf) syscontact Root root@localhost (configure /etc/snmp/snmp.local.conf) pass .1.3.6.1.4.1.4413.4.1 /usr/bin/ucd5820stat rocommunity public localhost trapsink localhost:162 public trap2sink localhost:162 public authtrapenable 1 master agentx
snmpstats.conf ------------------------------- agentXSocket tcp:localhost:705
And the way I start snmpd now is: snmpd -f -Lo -M /usr/local/share/mibs -m ALL -d -x tcp:localhost:705 I did try several versions including the one found in the module documentation.
This is the context of my problem. Hopping that there is a small, but obvious mistake, in my config files, due to my lack of attention or something, and not a more serious thing, I thank you for your time.
Gabriel Mahu
Check out http://us.rd.yahoo.com/evt=51201/*http://autos.yahoo.com/new_cars.html;_ylc=X3oDMTE5NWVzZGVyBF9TAzk3MTA3MDc2BHNlYwNtYWlsdGFncwRzbGsDYXV0b3MtbmV3Y2Fy the hottest 2008 models today at Yahoo! Autos.
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Hi Bogdan,
Thank you for your quick reply, but unfortunately that is not the solution. I found out about "the fork problem" searching the web for possible answers to the connection problem and I did set fork on yes. Just to be sure that the config file for openser is ok, I'll insert it here:
--------------------------------------------------------
# logging stuff...
debug=9 # debug level (cmd line: -dddddddddd) fork=yes
listen=udp:<...>:5060 alias=<...>
mpath="..."
loadmodule "tm.so" loadmodule "rr.so" loadmodule "usrloc.so" loadmodule "dialog.so" loadmodule "snmpstats.so"
# -- rr params -- modparam("rr", "enable_full_lr", 1)
# -- dialog params -- modparam("dialog", "dlg_flag", 4)
# -- snmpstats params -- modparam("snmpstats", "MsgQueueMinorThreshold", 1234) modparam("snmpstats", "MsgQueueMajorThreshold", 5678) modparam("snmpstats", "dlg_minor_threshold", 500) modparam("snmpstats", "dlg_minor_threshold", 600)
route { # nothing special, just size and loop sanity check }
--------------------------------------------------------
This is all... This is a config file, just for loading the module and setting some limits for the alarms, nothing else. I hope it is ok.
Thanks again, Gabi Mahu
____________________________________________________________________________________ Yahoo! oneSearch: Finally, mobile search that gives answers, not web links. http://mobile.yahoo.com/mobileweb/onesearch?refer=1ONXIC
Hi Gabi,
in this case, I have no clue what your problem is :(.....
regards, bogdan
Gabi Mahu wrote:
Hi Bogdan,
Thank you for your quick reply, but unfortunately that is not the solution. I found out about "the fork problem" searching the web for possible answers to the connection problem and I did set fork on yes. Just to be sure that the config file for openser is ok, I'll insert it here:
# logging stuff...
debug=9 # debug level (cmd line: -dddddddddd) fork=yes
listen=udp:<...>:5060 alias=<...>
mpath="..."
loadmodule "tm.so" loadmodule "rr.so" loadmodule "usrloc.so" loadmodule "dialog.so" loadmodule "snmpstats.so"
# -- rr params -- modparam("rr", "enable_full_lr", 1)
# -- dialog params -- modparam("dialog", "dlg_flag", 4)
# -- snmpstats params -- modparam("snmpstats", "MsgQueueMinorThreshold", 1234) modparam("snmpstats", "MsgQueueMajorThreshold", 5678) modparam("snmpstats", "dlg_minor_threshold", 500) modparam("snmpstats", "dlg_minor_threshold", 600)
route { # nothing special, just size and loop sanity check }
This is all... This is a config file, just for loading the module and setting some limits for the alarms, nothing else. I hope it is ok.
Thanks again, Gabi Mahu
Yahoo! oneSearch: Finally, mobile search that gives answers, not web links. http://mobile.yahoo.com/mobileweb/onesearch?refer=1ONXIC
Hello all again,
Related to my "sub-agent to master-agent connection problem", I found out that if I pull the snmpstats.conf file from the equation (rename it or delete it or whatever...), everything seams to work properly. I get the agentx debug output in the snmpd window just like in the module documentation. All my other configuration items are just as before.
Could someone explain this behavior, because, for me, it is far from a solid solution to the initial problem?
Thank you again, Gabriel Mahu
--------------------------------- Looking for a deal? Find great prices on flights and hotels with Yahoo! FareChase.
When you turn on the master agent (NetSNMP), are you running it as root? Also, are you seeing:
"Turning on AgentX master support."
Also, could you show me the contents of your snmpstats.conf file?
So by deleting the snmpstats.conf file, you can see the snmpstats module connecting to the the master agent, and everything works ok? I'm confused on that point. :-)
- JM
Gabi Mahu wrote:
Hello all again,
Related to my "sub-agent to master-agent connection problem", I found out that if I pull the snmpstats.conf file from the equation (rename it or delete it or whatever...), everything seams to work properly. I get the agentx debug output in the snmpd window just like in the module documentation. All my other configuration items are just as before.
Could someone explain this behavior, because, for me, it is far from a solid solution to the initial problem?
Thank you again, Gabriel Mahu
Looking for a deal? Find great prices on flights and hotels http://us.rd.yahoo.com/evt=47094/*http://farechase.yahoo.com/;_ylc=X3oDMTFicDJoNDllBF9TAzk3NDA3NTg5BHBvcwMxMwRzZWMDZ3JvdXBzBHNsawNlbWFpbC1uY20- with Yahoo! FareChase.
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Hi Jeffrey,
Yes, I do run snmpd as root and "Turning on AgentX master support" is present in the initial output. As for the snmpstats.conf file, it contains only this line: agentXSocket tcp:localhost:705. I followed the instructions in the module documentation, nothing more.
With the file in its place, with the config files in the form that I listed in previous mails, I get no agentx debug output. I renamed the snmpstats.conf file, so it can't be reached by the sub-agent in the module, and the agentx debug output is present. Maybe it has something to do with some kind of standard configuration for a NET-SNMP subagent, that happens to be ok for me.
Thanks.
Gabi Mahu
--- Jeffrey Magder jmagder@somanetworks.com wrote:
When you turn on the master agent (NetSNMP), are you running it as root? Also, are you seeing:
"Turning on AgentX master support."
Also, could you show me the contents of your snmpstats.conf file?
So by deleting the snmpstats.conf file, you can see the snmpstats module connecting to the the master agent, and everything works ok? I'm confused on that point. :-)
- JM
Gabi Mahu wrote:
Hello all again,
Related to my "sub-agent to master-agent
connection problem", I found
out that if I pull the snmpstats.conf file from
the equation (rename
it or delete it or whatever...), everything seams
to work properly. I
get the agentx debug output in the snmpd window
just like in the
module documentation. All my other configuration
items are just as
before.
Could someone explain this behavior, because, for
me, it is far from a
solid solution to the initial problem?
Thank you again, Gabriel Mahu
------------------------------------------------------------------------
Looking for a deal? Find great prices on flights
and hotels
with Yahoo! FareChase.
------------------------------------------------------------------------
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
____________________________________________________________________________________ Looking for a deal? Find great prices on flights and hotels with Yahoo! FareChase. http://farechase.yahoo.com/
Well I'm glad it works now, but I'm not sure why it does. :P
Just for fun, could you run two tests without the snmpstats.conf file? I'd like to find out if the master agent is listening on a port other than what's been specified on the command line with the -x parameter. That might explain why it works only without the snmpstats.conf file.
1) Can you run a tcpdump on port 705 (and only port 705) and let me know if there is traffic between the master agent and the subagent?
2) Can you try loading up the snmpd agent with the -x but nothing else following, and let me know if the SNMPStats module is still able to communicate with the master agent, when the snmpstats.conf file isn't there?
- Jeffrey Magder
Gabi Mahu wrote:
Hi Jeffrey,
Yes, I do run snmpd as root and "Turning on AgentX master support" is present in the initial output. As for the snmpstats.conf file, it contains only this line: agentXSocket tcp:localhost:705. I followed the instructions in the module documentation, nothing more.
With the file in its place, with the config files in the form that I listed in previous mails, I get no agentx debug output. I renamed the snmpstats.conf file, so it can't be reached by the sub-agent in the module, and the agentx debug output is present. Maybe it has something to do with some kind of standard configuration for a NET-SNMP subagent, that happens to be ok for me.
Thanks.
Gabi Mahu
--- Jeffrey Magder jmagder@somanetworks.com wrote:
When you turn on the master agent (NetSNMP), are you running it as root? Also, are you seeing:
"Turning on AgentX master support."
Also, could you show me the contents of your snmpstats.conf file?
So by deleting the snmpstats.conf file, you can see the snmpstats module connecting to the the master agent, and everything works ok? I'm confused on that point. :-)
- JM
Gabi Mahu wrote:
Hello all again,
Related to my "sub-agent to master-agent
connection problem", I found
out that if I pull the snmpstats.conf file from
the equation (rename
it or delete it or whatever...), everything seams
to work properly. I
get the agentx debug output in the snmpd window
just like in the
module documentation. All my other configuration
items are just as
before.
Could someone explain this behavior, because, for
me, it is far from a
solid solution to the initial problem?
Thank you again, Gabriel Mahu
Looking for a deal? Find great prices on flights
and hotels
with Yahoo! FareChase.
Users mailing list Users@openser.org http://openser.org/cgi-bin/mailman/listinfo/users
Looking for a deal? Find great prices on flights and hotels with Yahoo! FareChase. http://farechase.yahoo.com/