Best way for OD redundancy in an AD environment?

[mac_ville]

I have two xserves that I will connect to an AD network for mgmt purposes only. I would like to have the OD as redundant as possible. I don’t plan to use Kerberos on the OD servers since no services will run except for OD.

1. OD Master and Slave on network as separate servers – will give redundancy but how about ‘search policies’ in the client. Do I have have to specify ‘Authentication’ for each server on the client?

2. OD Master and Slave setup with IP Failover, does it work?

Any other options?

[mac_ville]

Thanks for the tip.

I have a ‘classic’ OD setup in test with Master/Slave – problem is that I get timeouts and login problems when the ‘closest’ OD server is down. I want to get redundancy with no timeouts – hence my question. I have both 10.3 and 10.4 clients and in my prel testing I had problems maiinly with 10.3 clients and timeouts getting the login window.

[mac_ville]

So there is no way to get round the timeouts by activating IP Failover on the servers. (Haven’t had time to try it myself yet).

I have a hard time convincing that the timeouts are acceptable – even if they can be tuned… I have mostly 10.3’s and as mentioned they most affected

[Author]

Posts