overridden when the server replaces these values with its own guessed values at a later stage of the server startup. For more technical information on this attribute, see the cache size section of the Berkeley DB reference guide.

Attempting to set a value that is not a number or is too big for a 32-bit signed integer returns an LDAP_UNWILLING_TO_PERFORM error message with additional error information explaining the problem.

The server has to be restarted for changes to this attribute to take effect.

Entry DN:

cn=config,cn=ldbm database,cn=plugins,cn=config

Valid Range:

500KB to 4GB for 32-bit platforms and 500KB to 2^64-1

 

for 64-bit platforms

Default Value:

10,000,000 bytes

Syntax:

Integer

Example:

nsslapd-dbcachesize: 10,000,000

The database cache is used by the database to create and manage indexes and perform other database specific work. The nsslapd-dbcacheparameter is set globally for the server and is shared by all the database backends on the server.

Tuning nsslapd-dbcachesizecan be done by following these steps:

Step 1: Set the value of nsslapd-dbcachesizeand then start the directory server.

Step 2: Prime the directory by sending the following ldapsearch command (label it as “ldapsearch command 1”):

#./ldapsearch –b “<root suffix>” –h <host> -p <port> -D “cn=directory manager” –w passwd “objectclass=*” > /dev/null

Step 3: Check database-related monitoring attributes by sending a different ldapsearch request (label it as “ldapsearch command 2”):

#./ldapsearch -p PORT -b "cn=monitor, cn=ldbm database, cn=plugins, cn=config" –D "cn=directory manager" -w PASSWD “objectclass=*"

grep dbcache dbcachehits: 236 dbcachetries: 280 dbcachehitratio: 84 dbcachepagein: 44 dbcachepageout: 0 dbcacheroevict: 0 dbcacherwevict: 0

Step 4: If dbcachepageout, dbcacheroevict, and dbcacherwevict are not equal to zero, you might want to increase nsslapd-dbcachesize, and repeat steps 1 - 3 until these three attribute values equal zero, or dbcachesize reaches the maximum value, or dbcachepagein stops increasing. When nsslapd-dbcachesize is not big enough, pages need to be discarded from the dbcache to make room for new pages. This is indicated by attributes dbcachepageout, dbcacheroevict, and dbcacherwevict. For more information about these attributes, see the HP-UX Directory Server configuration, command, and file reference.

To estimate the amount of RAM needed for an optimized database cache, you can use the following formula:

7

Page 7
Image 7
HP UX Direry Server manual

UX Direry Server specifications

HP UX Directory Server is a robust and scalable solution designed for managing directory information within enterprise networks. Developed by Hewlett-Packard (HP), this server offers an extensive set of features tailored to meet the needs of organizations that require an efficient way to store, manage, and retrieve identity and access data.

One of the key features of HP UX Directory Server is its ability to handle large directories with significant volumes of data. Built on a highly optimized architecture, it provides excellent performance and can support millions of entries without sacrificing speed or reliability. This capability makes it an ideal choice for large-scale deployments in enterprises that require high availability and responsiveness.

In addition to its scalability, HP UX Directory Server supports a wide range of protocols, including LDAP (Lightweight Directory Access Protocol), which ensures seamless integration with diverse applications and systems across various platforms. The server maintains standards compliance, which facilitates interoperability and simplifies administration tasks.

Security is a top priority for HP UX Directory Server, offering an array of features to protect sensitive information. It supports secure data transmission via TLS/SSL protocols, ensuring encrypted communication between clients and servers. Advanced access controls allow administrators to define fine-grained permissions, helping to safeguard directory data against unauthorized access.

Another salient feature of HP UX Directory Server is its replication capabilities. The server can replicate directory data across multiple instances, ensuring data consistency and availability in distributed environments. This feature is essential for businesses operating across different geographical locations or requiring failover solutions for disaster recovery.

HP UX Directory Server also comes equipped with tools for data management, including an intuitive administration console for configuring and monitoring the server. Additionally, it offers customizable schema capabilities, enabling organizations to tailor the directory structure to fit their specific needs.

Integration with existing identity management solutions is streamlined through connectors and APIs, allowing organizations to extend their directory services and enhance user experience.

In summary, HP UX Directory Server is a powerful directory management solution that combines scalability, security, and integration flexibility. Its support for industry standards, advanced replication, and comprehensive administrative tools makes it an essential asset for organizations seeking to manage identity and access efficiently. By leveraging this technology, businesses can improve their operational efficiency and ensure a secure and organized approach to directory management.