HP-UX Directory Server Administrator Guide HP-UX Directory Server Version 8.1 (5900-3098, May 2013)

server slapd-phonebook
server slapd-example
server slapd-directory
15.3.2 Starting the subagent
After your master agent is running and you have created your subagent configuration file, start
the subagent. To start your subagent, run the ldap-agent program, specifying the absolute path
to the subagent configuration file as an argument. For example:
ldap-agent /etc/opt/dirsrv/config/ldap-agent.conf
To enable extra debug logging, specify the -D option during startup:
ldap-agent -D /etc/opt/dirsrv/config/ldap-agent.conf
NOTE:
The Directory Server does not have to be started for the subagent to be started.
To stop your subagent, you must use the kill command against its process ID. Your subagent
will print its process ID in its log file, or you can run ps -ef | grep ldap-agent to find the
process ID.
15.3.3 Testing the subagent
To test your subagent, use any SNMP client tools to query the master agent. Net-SNMP contains
simple command line utilities such as snmpwalk and snmpget. In order for these tools to use
variable names for queries, configure them to load the Directory Server's MIB file. The Directory
Server's MIB file, hp-directory.mib is located in /opt/dirsrv/share/mibs. There are
some additional common required MIB files in this mibs directory if you do not already have them
with your MIB tools.
The MIB file is not needed for the subagent to operate; it is only required for any SNMP client
application to use variable names instead of numeric OIDs to refer to the monitored information
provided by the subagent.
Each monitored server instance uses its port number as an index to identify that particular Directory
Server instance. For example, querying for the dsEntityName.389 SNMP variable returns the
variable value for a server running on port 389, assuming that instance exists and is being monitored
by the subagent.
For details on configuring and using the Net-SNMP command line tools, check out the Net-SNMP
website, http://www.net-snmp.org.
15.4 Configuring SNMP traps
An SNMP trap is essentially a threshold that triggers a notification if it is encountered by the
monitored server. To use traps, the master agent must be configured to accept traps and do
something with them. For example, a trap can trigger an email notification for an administrator of
the Directory Server instance stops.
The subagent is only responsible for sending the traps to the master agent. The master agent and
a trap handler must be configured according to the documentation for the SNMP master agent
you are using.
Traps are accompanied by information from the Entity Table, which contains information
specific to the Directory Server instance, such as its name and version number. The Entity Table
is described in “Entity table” (page 536). This means that the action the master agent takes when
it receives a trap is flexible, such as sending an email message to an email address defined in the
dsEntityContact variable for one instance while sending a notification to a pager number in
the dsEntityContact variable for another instance.
15.4 Configuring SNMP traps 533