Hi everybody! I followed this excellent guide to install ZenOSS on a CentOS system (now up and running): http://webaj.com/zenoss-2-0-core-installation-guide-centos-looks-network-and-server-monitoring-has-gone-web-2-0.htm
Now, I am configuring my first Linux server with SNMP to be monitored by the zenOSs system (Debian Etch 4.0, last stable). I followed some of the steps mentioned on this guide: http://www.howtoforge.com/zenoss_network_monitor_ubuntu Specifically, steps abut configuring SNMP agent n a t-be-monitored Linux system. When I try to add this device to ZenOSS ( I mainly use the web interface) no information is gathered (and the device is nt added). I tested SNMP on other hosts for what I know SNMP is up and running without problems (Windows SNMP + SNMP informant agent installed) using snmpwalk (as per the Admin's guide): #snmpwalk -v1 -c public ip_of_the_server And a lot f info is provided. When I test on the Linux box, the test check times out...I have ssh access t the Linux box and I perfectly know that SNMP agent is running. Both servers have mutual visibility (no network problem, assured). My questions are: a) Is there any sample configuration file for the snmpd.conf file for debian boxes? Maybe I am misconfigurating something... b) Is there any additional test I can perform? Thanks and regards. P.D: The snmpd.conf file : ########################################################################### # # snmpd.conf # # - created by the snmpconf configuration program # ########################################################################### # SECTION: Access Control Setup # # This section defines who is allowed to talk to your running # snmp agent. # rocommunity: a SNMPv1/SNMPv2c read-only access community name # arguments: community [default|hostname|network/bits] [oid] rocommunity public zenoss_server_ip "f f q" ########################################################################### # SECTION: System Information Setup # # This section defines some of the information reported in # the "system" mib group in the mibII tree. # syslocation: The [typically physical] location of the system. # Note that setting this value here means that when trying to # perform an snmp SET operation to the sysLocation.0 variable will make # the agent return the "notWritable" error code. IE, including # this token in the snmpd.conf file will disable write access to # the variable. # arguments: location_string syslocation Unknown (configure /etc/snmp/snmpd.local.conf) # syscontact: The contact information for the administrator # Note that setting this value here means that when trying to # perform an snmp SET operation to the sysContact.0 variable will make # the agent return the "notWritable" error code. IE, including # this token in the snmpd.conf file will disable write access to # the variable. # arguments: contact_string syscontact Root <[EMAIL PROTECTED]> (configure /etc/snmp/snmpd.local.conf) # # Unknown directives read in from other files by snmpconf # com2sec paranoid default public group MyROSystem v1 paranoid group MyROSystem v2c paranoid group MyROSystem usm paranoid group MyROGroup v1 readonly group MyROGroup v2c readonly group MyROGroup usm readonly group MyRWGroup v1 readwrite group MyRWGroup v2c readwrite group MyRWGroup usm readwrite view all included .1 80 view system included .iso.org.dod.internet.mgmt.mib-2.system access MyROSystem "" any noauth exact system none none access MyROGroup "" any noauth exact all none none access MyRWGroup "" any noauth exact all all none ------------------------ Javier Santiago -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=9278#9278 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
