| Oracle® Fusion Middleware Reference for Oracle Directory Server Enterprise Edition 11g Release 1 (11.1.1.7.0) Part Number E28969-01 |
|
|
PDF · Mobi · ePub |
| Oracle® Fusion Middleware Reference for Oracle Directory Server Enterprise Edition 11g Release 1 (11.1.1.7.0) Part Number E28969-01 |
|
|
PDF · Mobi · ePub |
For information about monitoring Directory Server, see the following sections.
Directory Server can be monitored in the following ways:
Directory Service Control Center, DSCC, can be used to monitor current activities of a Directory Server instance.
DSCC provides general server information, including a resource summary, current resource usage, connection status, and global database cache information. It also provides general database information, such as the database type, status, and entry cache statistics. Cache information and information relative to each index file within the database is also provided.
The dsconf command can be used to configure logging and to monitor the replication status of Directory Server. For information about how to configure logging, see Configuring Logs for Directory Server in Administrator's Guide for Oracle Directory Server Enterprise Edition. For information about how to use the dsconf command for monitoring, see Getting Replication Status by Using the Command Line in Administrator's Guide for Oracle Directory Server Enterprise Edition.
The ldapsearch command can be used to search the cn=monitor entry for information about current activities of a Directory Server instance. For information about cn=monitor, see Directory Server Monitoring Attributes.
The Directory Server Resource Kit provides a log analyzer tool called logconv.
The logconv tool extracts usage statistics and counts the occurrences of significant events in the access logs.
Directory Server exposes management information through SNMP.
Directory Server implements the dsTable and the dsApplIfOpsTable of the Directory Server Monitoring MIB defined by RFC 2605 (http://www.ietf.org/rfc/rfc2605.txt). It does not implement the dsIntTable.
Directory Server also implements the Network Services Monitoring MIB defined by RFC 2788 (http://www.ietf.org/rfc/rfc2788.txt).
Directory Server support for SNMP has the following limitations.
SNMP support is for monitoring only, no SNMP management is supported.
No SNMP traps are implemented.
This rest of this section explains how the information flows from the monitoring application to Directory Server and back, particularly in the case where you use SNMP.
The monitoring framework is contained within the DSCC agent, which is installed alongside Directory Server. Figure 6-1 shows the monitoring framework.
Figure 6-1 Overall Monitoring Information Flow
SNMP support for monitoring Directory Server is managed by the DSCC agent.
Figure 6-2 shows how SNMP information about Directory Server flows through the DSCC Agent.
SNMP information about Directory Server flows as follows.
The network management station sends a GET message to the SNMP agent, which by default uses port 3996.
The SNMP agent forwards any requests destined for the Directory Server to the DSCC agent.
Directory Server pushes SNMP information on a regular basis to the DSCC agent.
The DSCC agent relays the response back to the SNMP client through the SNMP agent to the network management station. The network management station then displays the data through its network management application.
Server status, replication status, resource usage, and other monitoring information is available through DSCC.
Alternatively, you can monitor the Directory Server's current activities from any LDAP client by performing a search operation on the following entries:
cn=monitor
cn=monitor, cn=ldbm database, cn=plugins, cn=config
cn=monitor,cn=dbName,cn=ldbm database,cn=plugins,cn=config
dbName is the database name of the suffix that you want to monitor. Note that except for information about each connection, by default, the cn=monitor entry is readable by anyone, including clients bound anonymously.
The cn=monitor entry is an instance of the extensibleObject object class. For cn=monitor configuration attributes to be taken into account by the server, this object class, in addition to the top object class, is present in the entry. The cn=monitor read-only attributes are presented in this section.
Read-only monitoring information is stored under the cn=monitor entry.
DN for each Directory Server backend.
For further database monitoring information, refer to dse.ldif.
A list of open connections is returned only if the user is authenticated as an administrative user. The list is given in the following format:
connection=31:20010201164808Z:45:45::name="DirAdminDN" content="cn=admin,cn=Administrators,cn=config":LDAP
31 is number of the file descriptor used by the server in handling the connection
20010201164808Z is the date the connection was opened
45 is the number of operations received
45 is the number of completed operations
name="DirAdminDN" content="cn=admin,cn=Administrators,cn=config" is the bind DN
Current time usually given in Greenwich Mean Time, indicated by GeneralizedTime syntax Z notation, for example 20010202131102Z.
The number of requests waiting to be processed by a thread. Each request received by the server is accepted, then placed in a queue until a thread is available to process it. The queue backlog should always be small, 0 or close to 0. If the queue backlog is large, use the nsslapd-threadnumber attribute to increase the number of threads available in the server.
Number of connections where some requests are pending and not currently being serviced by a thread in Directory Server.
Number of persistent searches currently running on the server. You can set a maximum number of persistent searches on the server by using the command dsconf set-server-prop max-psearch-count:number.
Number of operation threads Directory Server creates during startup. This attribute can be set using the nsslapd-threadnumber attribute under cn=config. The nsslapd-threadnumber attribute is not present in the configuration by default, but can be added.
The cn=disk entry enables you to monitor disk conditions over LDAP. This entry is an instance of the extensibleObject object class. A cn=disknumber,cn=disk,cn=monitor entry exists for each disk. The following disk monitoring attributes appear under each of these individual disk entries.
Specifies the pathname of a directory used by the server on disk. Where several database instances reside on the same disk or an instance refers to several directories on the same disk, the short pathname is displayed. The disk numbering is arbitrary.
Indicates the amount of free disk space available to the server, in MB.
Note:
The disk space available to the server process may be less than the total free disk space. For example, on some platforms a process that is not running as root may not have all the free disk space available to it.
This entry holds counter information for the various subtree entry counter plug-ins, if they are enabled.
Total time in seconds spent by the worker threads from the moment an operation is received to the start of its processing. This parameter is not available on Windows.
This entry holds counters related to the Class of Service plug-in. This entry is an instance of the extensibleObject object class.
When the CoS plug-in uses the hash table for fast lookup, if more than one classic CoS template corresponds to the hash key used, the plug-in next checks for matches in what is called the clash list, a list of templates sharing an identical hash key. The value of this attribute provides the average length across all hash tables of classic CoS template clash lists, giving some indication of how much linear searching the plug-in must perform after using the hash table during fast lookup.
The average number of clashes per hash table. That is, the average percentage per hash of classic CoS templates sharing an identical hash key.
The memory overhead in bytes to hold hash tables for fast classic CoS template lookups.
The memory in bytes used to hold hash values for fast classic CoS template lookups.
The number of hash tables created for fast lookup where more than 10 classic CoS templates apply for a single CoS definition. Hash tables are not created for smaller lists of templates.
|
 Copyright © 2001, 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
