Problem: How do I bind eDirectory to the new IP address on the new card added (second NIC added after the eDirectory configuration).
There might be deployments where initially eDirectory is configured on a server with a single NIC. Later, if another NIC is added to it, how do we ensure that eDirectory is bounded by this new IP address as well, along with the existing IP address. One way is to make multiple instances with custom ports and the second NIC. In such a case, the administrator has to manage multiple trees.
Solution: One can associate the same instance of eDirectory to multiple IP addresses using the following the steps.
- Set the ncp port to the new ip address along with the existing.
Example: ndsconfig set n4u.server.interfaces=18.104.22.168@524,22.214.171.124@524
- Set the http port to the new ip address along with the existing.
Example: ndsconfig set n4u.server.interfaces=126.96.36.199@8028,188.8.131.52@8028
- Set the https port to the new ip address along with the existing.
Example: ndsconfig set n4u.server.interfaces=184.108.40.206@8030,220.127.116.11@8030
In the above example, 18.104.22.168 is the first NIC with which eDirectory is initially configured and 22.214.171.124 is the NIC that is added later.
There is no need to set the TCP
-636 ports because by default it listens on all. The above can also be done by editing the values of nds.conf. One has to restart eDirectory using /etc/init.d/ndsd restart to make the above changes of associating the instance with the IP addresses take effect.
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.