Hi ju55i, Yesterday I wrestled with a same kind of a problem. Check if your /var/log/snmpd.log file has REJECTED entries. If that is the case then the culprit could be your /etc/hosts.allow file where you need to put in a line: snmpd: <your zenoss host>
Tcp wrappers use the hosts.allow and hosts.deny files to determine which hosts are allowed to connect. Didn't work....no apparent relation. Have a look at the /etc/snmpd.conf file on the zenoss server. By default it limits access to localhost only: rocommunity public 127.0.0.1 Linux is quite dumb at times, as the snmp daemon will listen only to a localhost request and not to requests from the real eth0 IP address. You should change the above line to the IP address of your zenoss server on all hosts to be monitored. Don´t forget to restart snmpd after this change! This does not explain why zenoss does not collect snmp data while snmp walk is getting a response, however. I have seen this happen after renaming a device, or if DNS resolution is not working properly. Didn't work, also...and take into account that zenOSS server is gathering SNMP info from a Windows server without problems at all... Yesterday I wrestled with a same kind of a problem. Check if your /var/log/snmpd.log file has REJECTED entries. If that is the case then the culprit could be your /etc/hosts.allow file where you need to put in a line: snmpd: <your zenoss host> This file does not exist on the Debian box. None of the configuration files I have tested seems to work...I'm getting desperate with this. Is there any tool to test SNMP real behaviour (command line output) to see which the problem is?. Regards, ------------------------ Javier Santiago -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=9291#9291 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
