HP UX Red Hat Direry Server Software manual Configuring the Master Agent Configuring the Subagent

Chapter 14. Monitoring Directory Server Using SNMP

managed objects, have values and titles that are reported to the NMS as necessary. Communication between an NMS and a managed device takes place either by the NMS sending updates or requesting information or by the managed object sending a notice or warning, called a trap, when a server shuts down or starts up.

2. Configuring the Master Agent

To use the subagent, you must have a master agent that supports AgentX. A common agent is Net-SNMP master agent, which may be available through your operating system vendor or can be downloaded from the Net-SNMP website, http://www.net-snmp.org.

The SNMP subagent included with Directory Server uses the AgentX protocol to communicate with the SNMP master agent running on your system. You must make sure that you enable AgentX support on your master agent. For Net-SNMP, add a line containing agentx master in the master agent'ssnmpd.conf file. For more details on configuring the master agent for AgentX support, refer to the Net-SNMP website, http://www.net-snmp.org.

3. Configuring the Subagent

The Directory Server SNMP subagent is located in installed with the Directory Server tools. On Red Hat Enterprise Linux and Solaris, this is in /usr/bin/ldap-agent. On HP-UX, this is in /opt/dirsrv/bin/ldap-agent.

3.1. Subagent Configuration File

To use the subagent, first create a subagent configuration file. This file can be named and located wherever you like. This configuration file is used to specify how to communicate with your master agent, logfile location, and which Directory Server instances to monitor.

3.1.1. agentx-master

The agentx-mastersetting tells the subagent how to communicate with the SNMP master agent. If this setting is not specified, the subagent tries to communicate the the master agent through the Unix domain socket /var/agentx/master. This is also where the Net-SNMP master agent listens for AgentX communications by default. If you configured your master agent to listen on a different Unix domain socket, you must use the agentx-master setting for your subagent to communicate with your master agent by setting the new path for the agentx-masterparameter. For example:

agentx-master /var/snmp/agentx

Make sure that the user as whom you are running the subagent has the appropriate permissions to write to this socket.

If the master agent is listening for AgentX communications on a TCP port, the agentx-mastersetting has the hostname and port number. For example:

454