On 08/13/2009 05:12 PM, Edward "Koko" Konetzko wrote:
I am wonder if SNMP monitoring works in RHDS 8.1 if so I need some help getting it working.

The docs I have been using are linked below
http://directory.fedoraproject.org/wiki/Howto:SNMPMonitoring
http://www.redhat.com/docs/manuals/dir-server/8.1/admin/Monitoring_DS_Using_SNMP.html


The /etc/snmp/snmp.conf file

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
com2sec local     localhost      ldap
group MyROGroup  any        local
view all included .1 access MyROGroup "" any noauth 0 all none none
syslocation Unknown (edit /etc/snmp/snmpd.conf)
syscontact Root <r...@localhost> (configure /etc/snmp/snmp.local.conf)
pass .1.3.6.1.4.1.4413.4.1 /usr/bin/ucd5820stat
master agentx

The /etc/dirsrv/config/ldap-agent.conf

# Config file for AgentX access so FDS can pass snmp variables to net-snmp
# This is the agent config file.
#
# Start the agent with /opt/fedora-ds/bin/slapd/server/ldap-agent /opt/fedora-ds/ldap-agent.conf
#
#
## AgentX Master ##
#
# Where the agent communicates with the AgentX Master (net-snmp).
# If not specified uses the net-snmp default of a UNIX socket
# at /var/agentx/master. RTFM if you decide to use a differing location...
#
agentx-master /var/agentx/master

## AgentX Logdir ##
#
# Where the agent logs its logfile...
#
agent-logdir /var/log/dirsrv/agent/
#
## Server ##
#
# Which FDS instance you wish to monitor.
# This should be the absolute path to the log dir of the FDS instance.
#
server slapd-ldap-master-n01

When I run "snmpwalk -v 1 -c ldap localhost .1.3.6.1.4.1.2312.6.1.1.3.389" I get nothing back but when I run "snmpwalk -v 1 -c ldap localhost .1.3.6.1.4.1.2312" the following is returned.

SNMPv2-SMI::enterprises.2312.6.5.1.1.389 = STRING: "ldap master server"
SNMPv2-SMI::enterprises.2312.6.5.1.2.389 = STRING: "Red Hat-Directory/8.1.0"
SNMPv2-SMI::enterprises.2312.6.5.1.3.389 = STRING: "Rackspace Cloud"
SNMPv2-SMI::enterprises.2312.6.5.1.4.389 = STRING: "Lab"
SNMPv2-SMI::enterprises.2312.6.5.1.5.389 = STRING: "not made yet"
SNMPv2-SMI::enterprises.2312.6.5.1.6.389 = STRING: "ldap-master-n01"

All of that is correct with what is set in the Directory server.

If I run "strings /var/run/dirsrv/slapd-ldap-master-n01.stats" I get the following back and I am wondering if there is supposed to be something where it says "Not Available"?

Red Hat-Directory/8.1.0
ldap-master-n01
ldap master server
Rackspace Cloud
not made yet
Not Available
Not Available
Not Available
Not Available
Not Available
Not Available
Not Available
Not Available
Not Available
Not Available
The "Not Available" strings are from the unimplemented interactions table. This table is supposed to list the last 10 clients that the server has interacted with IIRC, but it's not implemented, so we just report "Not Available". The bulk of the stats are not strings, so what you see is everything I would expect.


/usr/bin/ldap-agent-bin -D /etc/dirsrv/config/ldap-agent.conf just outputs the following over and over again in its log file.

2009-08-13 18:51:57 Reloading stats.
2009-08-13 18:51:57 Opening stats file (/var/run/dirsrv/slapd-ldap-master-n01.stats) for server: 389


Thanks in advance.
Edward

--
389 users mailing list
389-us...@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-directory-users

--
389 users mailing list
389-us...@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-directory-users

Reply via email to