Configuring the Directory Server
Configuring Security in the Directory Server
Monitoring the Directory Server
Working With Monitor Providers
Viewing Monitoring Information Using the cn=monitor Entry
To View the Available Monitoring Information
To Monitor General-Purpose Server Information
To Monitor Version Information
To Monitor the User Root Back End
To Monitor the Backup Back End
To Monitor the monitor Back End
To Monitor the Schema Back End
To Monitor the adminRoot Back End
To Monitor the ads-truststore Back End
To Monitor the LDAP Connection Handler
To Monitor LDAP Connection Handler Statistics
To Monitor Connections on the LDAP Connection Handler
To Monitor the Administration Connector
To Monitor Administration Connector Statistics
To Monitor Connections on the Administration Connector
To Monitor the LDIF Connection Handler
To Monitor the userRoot Database Environment
To Monitor JVM Stack Trace Information
To Monitor the JVM Memory Usage
Monitoring Using Managed Tasks
Configuring Alert Notifications and Account Status Notification Handlers
To View the Replication Repair Logs
General Purpose Enterprise Monitoring Solutions
Monitoring the Directory Server With JConsole
To Configure JMX on a Directory Server Instance
Accessing a Directory Server Instance From JConsole
Viewing Directory Monitoring Information With JConsole
Monitoring the Directory Server With SNMP
Configuring SNMP in the Directory Server
To Configure SNMP in the Directory Server
Monitoring the Directory Server With the Control Panel
To View Monitoring Information With the Control Panel
Configuring Logs With dsconfig
Overview of Directory Server Logs
To Configure Log Retention Policies
To Configure Log Rotation Policies
Logging Access Control Information
Differences Between Logging in Sun OpenDS Standard Edition and Sun Java System Directory Server
Configuring Alerts and Account Status Notification Handlers
To View All Configured Alert Handlers
Managing Account Status Notification Handlers
To View the Configured Account Status Notification Handlers
To Enable Account Status Notification Handlers
To Create a New Account Status Notification Handler
To Delete an Account Status Notification Handler
Monitoring a Replicated Topology
Monitoring Replication Status With dsreplication
The directory server provides an SNMP connection handler that you can enable and configure. The SNMP connection handler is provided as a jar file extension and is located in install-dir/lib/extensions/snmp-mib2605.jar.
The directory server can be configured for monitoring through the Simple Network Management Protocol (SNMP). The directory server uses the Java Dynamic Management Kit (JDMK) to create smart agents for the SNMP connection handler. To enable SNMP for your directory server, you must specify the file path for the JDMK jar file (jdmkrt.jar) that is bundled with the product distribution.
Use dsconfig to view the list of current connection handlers.
$ dsconfig -D "cn=directory manager" -w password -n list-connection-handlers Connection Handler : Type : enabled : listen-port : use-ssl -------------------------:------:---------:-------------:-------- JMX Connection Handler : jmx : false : 1689 : false LDAP Connection Handler : ldap : true : 1389 : false LDAPS Connection Handler : ldap : false : 636 : true LDIF Connection Handler : ldif : true : - : - SNMP Connection Handler : snmp : false : 161 : -
$ dsconfig -D "cn=Directory Manager" -w password -n set-connection-handler-prop \ --handler-name "SNMP Connection Handler" --set enabled:true --set listen-port:8085 \ --set opendmk-jarfile:install-dir/addons/jdmkrt.jar
$ dsconfig -D "cn=directory manager" -w password -n get-connection-handler-prop \ --handler-name "SNMP Connection Handler" Property : Value(s) --------------------:------------------------------------------ allowed-client : - allowed-manager : * allowed-user : * community : OpenDS denied-client : - enabled : false listen-port : 161 opendmk-jarfile : - registered-mbean : false security-agent-file : config/snmp/security/opends-snmp.security security-level : authnopriv trap-port : 162 traps-community : OpenDS traps-destination : -
If the server was started and no modifications were made to the configuration, the restart operation is not required.
$ snmpwalk -v 2c -c OpenDS@OpenDS localhost:8085 mib-2.66 SNMPv2-SMI::mib-2.66.1.1.1.1 = STRING: "OpenDS Directory Server 1.3.0 - 20090310152800Z" SNMPv2-SMI::mib-2.66.1.1.2.1 = STRING: "Sun-OpenDS-SE-installation-directory/bin" SNMPv2-SMI::mib-2.66.1.1.3.1 = Gauge32: 35 SNMPv2-SMI::mib-2.66.1.1.4.1 = Gauge32: 1 SNMPv2-SMI::mib-2.66.1.1.5.1 = Gauge32: 0 SNMPv2-SMI::mib-2.66.1.1.6.1 = Counter32: 0 SNMPv2-SMI::mib-2.66.1.1.7.1 = Counter32: 1 SNMPv2-SMI::mib-2.66.2.1.1.1.1 = INTEGER: 1 SNMPv2-SMI::mib-2.66.2.1.1.1.2 = INTEGER: 2 SNMPv2-SMI::mib-2.66.2.1.1.1.3 = INTEGER: 3 SNMPv2-SMI::mib-2.66.2.1.2.1.1 = OID: SNMPv2-SMI::internet.27.3.8085 SNMPv2-SMI::mib-2.66.2.1.2.1.2 = OID: SNMPv2-SMI::internet.27.3.1389 SNMPv2-SMI::mib-2.66.2.1.2.1.3 = OID: SNMPv2-SMI::enterprises.42 SNMPv2-SMI::mib-2.66.2.1.3.1.1 = Counter32: 1 SNMPv2-SMI::mib-2.66.2.1.3.1.2 = Counter32: 1 SNMPv2-SMI::mib-2.66.2.1.3.1.3 = Counter32: 1 SNMPv2-SMI::mib-2.66.2.1.4.1.1 = Counter32: 1 SNMPv2-SMI::mib-2.66.2.1.4.1.2 = Counter32: 1 SNMPv2-SMI::mib-2.66.2.1.4.1.3 = Counter32: 1 SNMPv2-SMI::mib-2.66.2.1.5.1.1 = Counter32: 1 SNMPv2-SMI::mib-2.66.2.1.5.1.2 = Counter32: 1 ...
The managed objects included in the MIB 2605 are divided into three tables: dsTable, dsAppliIfOpsTable, and dsIntTable. Currently, the dsIntTable table is not implemented.