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
To View the SNMP Connection Handler Properties
To Access SNMP on a Directory Server Instance
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
The simplest way to monitor replication is to use the dsreplication status command. This command provides a tabular view of the replication status, including the following information:
The topology and its connections
The latency between replicated servers
The data consistency across replicated servers
The security configuration between replicated servers
The replication protocol peer to peer
The examples in the remainder of this section assume the following simple replication topology.
To obtain the replication status, run the following command:
$ dsreplication status -h llandudno -p 4444 -I admin -w password -X -n dc=example,dc=com - Replication Enabled ======================================= Server : Entries : M.C. (1) : A.O.M.C. (2) : Port (3) : Security (4) ---------------:---------:----------:--------------:----------:------------- llandudno:4444 : 2002 : 0 : N/A : 8989 : Disabled noordhoek:5444 : 2002 : 0 : N/A : 9989 : Disabled [1] The number of changes that are still missing on this server (and that have been applied to at least one of the other servers). [2] Age of oldest missing change: the date on which the oldest change that has not arrived on this server was generated. [3] The port used to communicate between the servers whose contents are being replicated. [4] Whether the replication communication through the replication port is encrypted or not.
The output of this command includes the following:
Server. Lists the LDAP servers in the topology and the port on which they are listening for LDAP connections.
Entries. Indicates the number of entries on each server for the specified base DN. If the information in this column is not the same across all the servers, the replication topology is not synchronized.
M.C. Indicates the number of updates already pushed by the other LDAP servers in the topology, but not yet replayed on the specified LDAP server. If this number is high on a particular server, investigate the latency of that server.
A.O.M.C. Specifies the approximate date of the oldest update pushed by the other directory servers in the topology, but not yet processed on the specified LDAP server.
Port. Indicates the port of the replication server to which the specified LDAP server is directly connected.
Security. Indicates whether SSL encryption is enabled between the LDAP server and its replication server.
Note - Additional replication monitoring information is available under the cn=monitor entry. You can use the ldapsearch command to track specific monitoring attributes, which will provide you with a comprehensive view of the replication status. For more information, see Advanced Replication Monitoring.