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.
In the above example, 184.108.40.206 is the first NIC with which eDirectory is initially configured and 220.127.116.11 is the NIC that is added later.