Article
Recherche
Shameless Plugs
Most Popular
Who's online
User login
3706
eDirectory on Multiple NICs
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=164.99.156.15@524,164.99.156.14@524 - Set the http port to the new ip address along with the existing.
Example: ndsconfig set n4u.server.interfaces=164.99.156.15@8028,164.99.156.14@8028 - Set the https port to the new ip address along with the existing.
Example: ndsconfig set n4u.server.interfaces=164.99.156.15@8030,164.99.156.14@8030
In the above example, 164.99.156.15 is the first NIC with which eDirectory is initially configured and 164.99.156.14 is the NIC that is added later.
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.
Related Articles
User Comments
- Be the first to comment! To leave a comment you need to Login or Register
Hey, you've got the ndsconfig
Submitted by lhaeger on 21 April 2010 - 11:37pm.
Hey, you've got the ndsconfig parameters slightly wrong, should be three different ones instead of only n4u.server.interfaces over and over again:
n4u.server.interfaces=164.99.156.15@524,164.99.156.14@524
http.server.interfaces=164.99.156.15@8028,164.99.156.14@8028
https.server.interfaces=164.99.156.15@8030,164.99.156.14@8030
Anyway, I always change those parameters to
n4u.server.interfaces=@524
http.server.interfaces=@8028
https.server.interfaces=@8030
on my servers, so Edirectory listens on all available interfaces, even on dynamically added virtual ip addresses. Simply run "sed -i.bak 's/=..*@/=@/g' /path/to/nds.conf && rcndsd restart" as root...
Some reason *not* to do that would be
a) multiple edir instances on a single server (same ports, different ip addresses) or
b) if you have to prevent Edirectory to bind to a specific interface
Finally, there's a similar parameter for the LDAP interface, check "ldapconfig get" for the current settings.
- Be the first to comment! To leave a comment you need to Login or Register
2