Article

(View Disclaimer)

Problem:

I am unable to add a server into an existing tree on the same host machine, so it has multiple instances with the same tree.

Note: This assumes that eDirectory 8.8.x is installed in the default location, using the root binary.

Solution:

1: Create a new configuration of 8.8.x in the default location by running the following command:

[root@ST-NF-CLI-216 setup]# ndsconfig new -t MI-TREE -n o=novell -a cn=admin.o=novell -w novell

Please enter the absolute path for the instance [ /var/opt/novell/eDirectory ]:

Please enter absolute path of the database directory [ /var/opt/novell/eDirectory/data/dib ]:

Configuring the NDAP interfaces... Done
Configuring the LDAP interfaces... Done
Configuring the HTTP interfaces... Done
Starting the service 'ndsd'... Done.

Configuring Novell eDirectory server with following parameters
        Admin name      = cn=admin.o=novell
        Tree name       = MI-TREE
        Server Context  = o=novell
        DIB location    = /var/opt/novell/eDirectory/data/dib

Searching for Duplicate Tree Name in the network. Please wait...
Basic configuration is successful. Proceeding with additional configuration...

Extending schema... Done
For more details view schema extension logfile: /var/opt/novell/eDirectory/log/schema.log

Configuring HTTP service... Done
Configuring LDAP service... Done
Configuring SNMP service... Done
Configuring SAS service... Done
Associating certificate with the NCP server object... Done
Configuring NMAS service... Done
Configuring SecretStore... Done
Configuring LDAP Server with default SSL CertificateDNS certificate... Done
The instance at /etc/opt/novell/eDirectory/conf/nds.conf is successfully configured.

[root@ST-NF-CLI-216 setup]# ndsstat

[1] Instance at /etc/opt/novell/eDirectory/conf/nds.conf:  ST-NF-CLI-216.o=novell.MI-TREE
Tree Name: MI-TREE
Server Name: .CN=ST-NF-CLI-216.O=novell.T=MI-TREE.
Binary Version: 20112.91
Root Most Entry Depth: 0
Product Version: eDirectory for Linux v8.8 [DS]

2. Create the second configuration by adding a dummy server to the existing tree on the same box. Add it to the above created tree with -S.
Use the following command to successfully add to the 1st tree on the box.

[root@ST-NF-CLI-216 /]# ndsconfig add -t MI-TREE -n o=novell -a cn=admin.o=novell -w novell -S st-nf-cli-216a  -p 164.99.156.216 --config-file /custom/nds.conf

Please enter the absolute path for the instance [ /var/opt/novell/eDirectory ]: /custom
Setting Variable data location to : /custom/data
Setting Database location to : /custom/data/dib

Configuring the NDAP interfaces...
INFO: Port "524" is already in use on "164.99.156.216" network interface(s)
Enter a port no. [Range: 1 - 65535]: 1524
Done
Configuring the LDAP interfaces...
INFO: Port "389" is already in use on "all" network interface(s)
Please enter a valid LDAP TCP port: 1389

Configuring the LDAP interfaces...
INFO: Port "636" is already in use on "all" network interface(s)
Please enter a valid LDAP SSL port: 1636
Done
Configuring the HTTP interfaces...
INFO: Port "8028" is already in use on "164.99.156.216" network interface(s)
Enter a port no. [Range: 1 - 65535]: 18028

INFO: Port "8030" is already in use on "164.99.156.216" network interface(s)
Enter a port no. [Range: 1 - 65535]: 18030
Done
Starting the service 'ndsd'... Done.

Configuring Novell eDirectory server with following parameters
        Admin name      = cn=admin.o=novell
        Tree name       = MI-TREE
        Server Context  = o=novell
        Server name     = st-nf-cli-216a
        DIB location    = /custom/data/dib

Logging into the tree as "cn=admin.o=novell". Please wait...

Note: If this server is being upgraded into an existing context with a large number of objects or, if network traffic is excessive, then configuration could take several minutes.

Synchronizing schema
Basic configuration is successful. Proceeding with additional configuration...

Extending schema... Done
For more details view schema extension logfile: /custom/log/schema.log

Configuring HTTP service... Done
Configuring LDAP service... Done
Configuring SNMP service... Done
Configuring SAS service... Done
Associating certificate with the NCP server object... Done
Adding replica... Done
Configuring NMAS service... Done
Configuring SecretStore... Done
Configuring LDAP Server with default SSL CertificateDNS certificate... Done
Updating LDAP TCP port with 1389... Done
Updating LDAP SSL port number with 1636... Done
The instance at /custom/nds.conf is successfully configured.

In the above command, -S specifies the server name. Because the second instance configuration is on the same box, you must use a dummy server name. In the above example, the actual server is st-nf-cli-216. During the second instance configuration, the dummy server name "st-nf-cli-216a" has been used.

You must provide non-default ports and non-default locations for .dib files, .conf files, and variable data, in order to successfully configure the second instance. The -p switch in the above command configures the eDirectory server into an existing tree by specifying the IP address and port number of a server hosting the tree. If this option is used, SLP is not used for tree lookup. In this case we are adding to a tree on the same box, so the IP address is the local ip address of the box.

Now multiple instances have been successfully configured on the same box, with the same tree.

Verification

You can use ndsmanage to manage eDirectory instances. With the "l" option (List the replicas on the server) you can view both the server names.

1. Run ndsmanage as follows:

[root@ST-NF-CLI-216 /]# ndsmanage
Novell Utility to manage eDirectory instances - Version: 1.0

The following are the instances configured by root

[1] /etc/opt/novell/eDirectory/conf/nds.conf : .ST-NF-CLI-216.NOVELL.MI-TREE. : 164.99.156.216@524 : ACTIVE

[2] /custom/nds.conf : .ST-NF-CLI-216A.NOVELL.MI-TREE. : 164.99.156.216@1524 : ACTIVE

Enter [1 - 2] for more options, [c] for creating a new instance or [q] to quit: 2
[l] List the replicas on the server
[s] Start the instance
[k] Stop the instance
[t] Run ndstrace
[d] Deconfigure
[q] Quit
What do you want to do with this instance? [ Choose from above]: l

Replicas of Partition : .T=MI-TREE.
Server Name                            Replica Type    Replica State
.CN=ST-NF-CLI-216.O=novell.T=MI-T...   Master          On
.CN=st-nf-cli-216a.O=novell.T=MI-...   Read/Write      On

2. Use ndsstat to view information for both instances.

[root@ST-NF-CLI-216 /]# ndsstat

[1] Instance at /etc/opt/novell/eDirectory/conf/nds.conf:  ST-NF-CLI-216.o=novell.MI-TREE

[2] Instance at /custom/nds.conf:  st-nf-cli-216a.o=novell.MI-TREE
Select the instance you want to operate on: [ 1 - 2 ] or 'q' to quit: 1
Tree Name: MI-TREE
Server Name: .CN=ST-NF-CLI-216.O=novell.T=MI-TREE.
Binary Version: 20112.91
Root Most Entry Depth: 0
Product Version: eDirectory for Linux v8.8 [DS]

[root@ST-NF-CLI-216 /]# ndsstat

[1] Instance at /etc/opt/novell/eDirectory/conf/nds.conf:  ST-NF-CLI-216.o=novell.MI-TREE

[2] Instance at /custom/nds.conf:  st-nf-cli-216a.o=novell.MI-TREE
Select the instance you want to operate on: [ 1 - 2 ] or 'q' to quit: 2
Tree Name: MI-TREE
Server Name: .CN=st-nf-cli-216a.O=novell.T=MI-TREE.
Binary Version: 20112.91
Root Most Entry Depth: 0
Product Version: eDirectory for Linux v8.8 [DS]

3. Log in to iManager, using the NCP port that the instance is configured with.

For the default configuration with default NCP port 524, there is no need to specify the port number. For multiple instances, you need to provide the non-default NCP port. A sample screen shot is below.

Click to view.

You can also view the replicas by going to Partitions and Replicas > Replica View plug-in in iManager, as shown below.

Click to view.

Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).

It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.