FEDORA DIRECTORY SERVER

INSTALLATION GUIDE NAVDEEP MATHUR

<Installation of 389-DS

The LDAP services will be provided by 389-Directory Server (389-DS)

Master1: ibm-39.bits.ac

Master2: ibm-40.bits.ac

Downloading the packages

There is direct way to install 389-DS on RHEL 5, therefore we install repos to get all the packages.

We need to first get the repo from FedoraPeople, and then get the rest from the EPEL repo.

Place the following file in your yum.repos folder:

Downloaded the Repo from

http://ftp.jaist.ac.jp/pub/Linux/Fedora/epel/5/x86_64/

Repo was created on Nagios server ( createrepo )

Repo has following files ( at ibm-39 .39 server , path /epel/ )

389-admin-1.1.29-1.el5.i386.rpm

389-admin-1.1.29-1.el5.x86_64.rpm

389-admin-console-1.1.8-1.el5.noarch.rpm

389-admin-console-doc-1.1.8-1.el5.noarch.rpm

389-adminutil-1.1.15-1.el5.i386.rpm

389-adminutil-1.1.15-1.el5.x86_64.rpm

389-adminutil-devel-1.1.15-1.el5.x86_64.rpm

389-console-1.1.7-3.el5.noarch.rpm

389-ds-1.2.1-1.el5.noarch.rpm

389-ds-base-1.2.9.9-1.el5.x86_64.rpm

389-ds-base-devel-1.2.9.9-1.el5.x86_64.rpm

389-ds-base-libs-1.2.9.9-1.el5.x86_64.rpm

389-ds-base-selinux-devel-1.2.9.9-1.el5.x86_64.rpm

389-ds-console-1.2.6-1.el5.noarch.rpm

389-ds-console-doc-1.2.6-1.el5.noarch.rpm

389-dsgw-1.1.9-1.el5.x86_64.rpm

idm-console-framework-1.1.7-5.el5.noarch.rpm

jss-4.2.6-6.el5.x86_64.rpm

Run 'yum':

yum install 389-adminutil.x86_64

yum install 389-admin.x86_64

yum install 389-dsgw

yum install 389-ds

yum install openldap-clients

Setup

Create the 'fds' user:

# useradd fds

Type in setup-ds-admin.pl in a terminal window to setup 389 Directory Server. Most of the time, the default is simply accepted indicated by the ↵ in the sample session below.

[root@ibm-39 ~]# setup-ds-admin.pl

NOTE : = PLEASE NOTE SOME INFORMATION

1. Configuration directory server

2. Administration Domain

3. Directory server network port

4. Directory Manager DN

5. Administration port

==============================================================================

This program will set up the 389 Directory and Administration Servers.

It is recommended that you have "root" privilege to set up the software.

Tips for using this program:

- Press "Enter" to choose the default and go to the next screen

- Type "Control-B" then "Enter" to go back to the previous screen

- Type "Control-C" to cancel the setup program

Would you like to continue with set up? [yes]: ↵

==============================================================================

BY SETTING UP AND USING THIS SOFTWARE YOU ARE CONSENTING TO BE BOUND BY

AND ARE BECOMING A PARTY TO THE AGREEMENT FOUND IN THE

LICENSE.TXT FILE. IF YOU DO NOT AGREE TO ALL OF THE TERMS

OF THIS AGREEMENT, PLEASE DO NOT SET UP OR USE THIS SOFTWARE.

Do you agree to the license terms? [no]: yes

==============================================================================

Your system has been scanned for potential problems, missing patches,

etc. The following output is a report of the items found that need to

be addressed before running this software in a production

environment.

389 Directory Server system tuning analysis version 10-AUGUST-2007.

NOTICE : System is i686-unknown-linux2.6.18-53.el6 (1 processor).

WARNING: 376MB of physical memory is available on the system. 1024MB is recommended for best performance on large production system.

NOTICE : The net.ipv4.tcp_keepalive_time is set to 7200000 milliseconds

(120 minutes). This may cause temporary server congestion from lost

client connections.

WARNING: There are only 1024 file descriptors (hard limit) available, which

limit the number of simultaneous connections.

WARNING: There are only 1024 file descriptors (soft limit) available, which

limit the number of simultaneous connections.

Would you like to continue? [no]: yes

==============================================================================

Choose a setup type:

1. Express

Allows you to quickly set up the servers using the most

common options and pre-defined defaults. Useful for quick

evaluation of the products.

2. Typical

Allows you to specify common defaults and options.

3. Custom

Allows you to specify more advanced options. This is

recommended for experienced server administrators only.

To accept the default shown in brackets, press the Enter key.

Choose a setup type [2]: ↵

==============================================================================

Enter the fully qualified domain name of the computer

on which you're setting up server software. Using the form

Example: eros.example.com.

To accept the default shown in brackets, press the Enter key.

Computer name [ibm-39.bits.ac]: ↵

==============================================================================

The servers must run as a specific user in a specific group.

It is strongly recommended that this user should have no privileges

on the computer (i.e. a non-root user). The setup procedure

will give this user/group some permissions in specific paths/files

to perform server-specific operations.

If you have not yet created a user and group for the servers,

create this user and group using your native operating

system utilities.

System User [nobody]: fds

System Group [nobody]: fds

==============================================================================

Server information is stored in the configuration directory server.

This information is used by the console and administration server to

configure and manage your servers. If you have already set up a

configuration directory server, you should register any servers you

set up or create with the configuration server. To do so, the

following information about the configuration server is required: the

fully qualified host name of the form

<hostname>.<domainname>(e.g. hostname.example.com), the port number

(default 389), the suffix, the DN and password of a user having

permission to write the configuration information, usually the

configuration directory administrator, and if you are using security

(TLS/SSL). If you are using TLS/SSL, specify the TLS/SSL (LDAPS) port

number (default 636) instead of the regular LDAP port number, and

provide the CA certificate (in PEM/ASCII format).

If you do not yet have a configuration directory server, enter 'No' to

be prompted to set up one.

Do you want to register this software with an existing

configuration directory server? [no]: ↵

==============================================================================

Please enter the administrator ID for the configuration directory

server. This is the ID typically used to log in to the console. You

will also be prompted for the password.

Configuration directory server

administrator ID [admin]: ↵

Password:

Password (confirm):

==============================================================================

The information stored in the configuration directory server can be

separated into different Administration Domains. If you are managing

multiple software releases at the same time, or managing information

about multiple domains, you may use the Administration Domain to keep

them separate.

If you are not using administrative domains, press Enter to select the

default. Otherwise, enter some descriptive, unique name for the

administration domain, such as the name of the organization

responsible for managing the domain.

Administration Domain [bits.ac]: ↵

==============================================================================

The standard directory server network port number is 389. However, if

you are not logged as the superuser, or port 389 is in use, the

default value will be a random unused port number greater than 1024.

If you want to use port 389, make sure that you are logged in as the

superuser, that port 389 is not in use.

Directory server network port [389]: ↵

==============================================================================

Each instance of a directory server requires a unique identifier.

This identifier is used to name the various

instance specific files and directories in the file system,

as well as for other uses as a server instance identifier.

Directory server identifier [ibm-39]: ↵

==============================================================================

The suffix is the root of your directory tree. The suffix must be a valid DN.

It is recommended that you use the dc=domaincomponent suffix convention.

For example, if your domain is example.com,

you should use dc=example,dc=com for your suffix.

Setup will create this initial suffix for you,

but you may have more than one suffix.

Use the directory server utilities to create additional suffixes.

Suffix [dc=bits, dc=ac]: ↵

==============================================================================

Certain directory server operations require an administrative user.

This user is referred to as the Directory Manager and typically has a

bind Distinguished Name (DN) of cn=Directory Manager.

You will also be prompted for the password for this user. The password must

be at least 8 characters long, and contain no spaces.

Directory Manager DN [cn=Directory Manager]: ↵

Password:

Password (confirm):

==============================================================================

The Administration Server is separate from any of your web or application

servers since it listens to a different port and access to it is

restricted.

Pick a port number between 1024 and 65535 to run your Administration

Server on. You should NOT use a port number which you plan to

run a web or application server on, rather, select a number which you

will remember and which will not be used for anything else.

Administration port [9830]: ↵

==============================================================================

The interactive phase is complete. The script will now set up your

servers. Enter No or go Back if you want to change something.

Are you ready to set up your servers? [yes]: ↵

Creating directory server . . .

Your new DS instance 'ldap1' was successfully created.

Creating the configuration directory server . . .

Beginning Admin Server creation . . .

Creating Admin Server files and directories . . .

Updating adm.conf . . .

Updating admpw . . .

Registering admin server with the configuration directory server . . .

Updating adm.conf with information from configuration directory server . . .

Updating the configuration for the httpd engine . . .

Starting admin server . . .

The admin server was successfully started.

Admin server was successfully created, configured, and started.

Exiting . . .

Log file is '/tmp/setupcT78dr.log'

Edit /etc/openldap/ldap.conf as follows:

URI ldap://localhost

BASE dc=bits,dc=ac

Replication

Ref:http://www.directory.fedora.redhat.com/wiki/Howto:WalkthroughMultimasterSSL

Add the Replication Manager DN Account via 389-console. Ensure it has the following fields:

dn: cn=replication manager,cn=config

changetype: add

objectclass: top

objectclass: person

cn: Replication Manager

sn: Manager

userPassword: PASSWORD

Note: Ensure both hosts have the same time, and have /etc/hosts entries of each other.

Set Up Multi-Master Replication

Configure Master Node1 and Node2

(Node1=ibm-39.bits.ac ; Node2=ibm-40.bits.ac)

We will configure without SSL. On the left side in the tree structure, expand all the possible boxes until you see the Directory Server icon, click on it. On the right hand side you will see a button that says 'Open' near the top. This will open the Directory Server GUI.

Click the Configuration Tab
Click on the Replication Folder on the left, this will bring up a page on the right. Click 'Enable Changelog' and then click the 'Use Default' button to populate the box. Be sure to click 'Save'
Back on the left, expand the Replication Folder until you see your databases. Click on the database you wish to replicate. On the right you will see a menu in which you need to use the following options.

Click 'Enable Replica'
Choose the 'Multi-Master' radio button
Under Common Settings choose a unique replica ID. Start with 1 and increment, make sure not to reuse a number twice.
Where it asks for a Supplier DN, use the special Replication Manager DN we set up earlier (cn=replication manager, cn=config) and add it
Under current referrals use the other read/write nodes. (ie, if you're setting up Node1, use Node2's hostname) Use the construct button to easily build this line. Make sure you click the 'Add' button afterwords.
Save your settings

Configure Multi-Master Replication Agreements

Now that MMR has been set up on all nodes, we need to create replication agreements on all supplier servers.

Back at the Replication Folder...

1) Right-click on the database you just configured in the previous step. Choose 'New Replication Agreement'

2) Name it something logical like: 'Node B' or the hostname of Node B, etc.

3) Under Consumer, choose the 'Other' button. Type in the name of the other supplier hosts. (IE if you're doing Node1, choose Node2 here)

4) Uncheck box about using SSL connections

5) Under the Bind section, enter your special Replication Manager DN yet again. (cn=replication manager, cn=config)

6) Click 'Next' twice until prompted for initialization settings

7) It is much easier to choose 'Do Not Initialize Now' and do them all at the same time later on in the install.

8) Repeat this process for ibm-40.bits.ac as well.

Ensure that the schema for and is the same. The schema is stored here:

/etc/dirsrv/slapd-ibm-39/schema/