HELP PLEASE-a popup-window during Xsan setup

[dong]

Can anybody give me a hand please for this issue? I am a novice to Xsan.
I have been trying to solve it for 2 whole work days and can't get any clue. It may be a pretty simple question for you, so it will be greatly appreciated if you can give me any help. Ta......

I've got 2 Xserve as 2 MDCs. Everything works fine during setup and installation of Xsan application.
But during Xsan setup, all are good until after "Choose Metadata Controllers" window appears. After I tick both of the Xserves as MDCs then click "continue" button, the problem follows: a small window pops up and ask Directory Admin Name with "diradmin" after it, Password and root Password.

I haven't got any clue at all why it happens and what it does mean and how to solve it.

Can anyone give me any hints,,pleaeaease?

Thanks very much.

[matx]

Hi

I don't recommend setting up the Xserve as an MDC using the Server Assistant on a fresh install.

Set up your Xserve / Mac OS XServer, get DNS and OD all set up right, then create your Xsan.

In your specific case it may be asking you for the original admin pass which could be also your diradmin (OD) password. If you set these up separately they will be different passwords.

I hope that helps.

[abstractrude]

i think whats happening, is it wants your OD admin password so it cant start the setup assistant and xsan in a way, can take over OD. I have never done it this way, though.

do the normal os x server install. on what i ill be your secondary metadata controllers setup dns and OD. attach the primary to the dns running off teh secondary controller. install xsan and update to 2.1.1 on both.. you can always do the zone transfer to the primary as well and the backup OD on the primary.

[dong]

Matx and Abstractrude, thanks so much for your quick responses.

I reinstalled OS X Server and Xsan on both Xserves. This time, I did NOT configure DNS and OD at all on either of MDCs. Surprisingly, Xsan setup process is smooth, no windows like I described before popped up.

However, an interesting thing occurs: after the Xsan has been setup successfully, the primary MDC's OD keeps unconfigured and the secondary MDC's OD has been changed into Open Directory Replica. I tried this process a few times and the same results can be seen everytime.

Why is this? Any theoretical explanations? Please......

Also, I hope the questions below are not a bit over-silly.
1. Why do we have to set up DNS and OD while the Xsan works good as depicted above?
2. Is there anything DNS and OD to do with using Xsan just in private network?

Sorry if you feel bothered. But I will be grateful if you can give me more guidance. Ta.......

[matx]

[dong]

Hello, Matt, thanks for your reply. I will be trying to figure things out.

[jtownsend]

The sheet you saw comes up if you are using Xsan to manage users and groups - in which case you have an Open Directory master on your primary MDC and OD replicas on your backup MDC(s).

If the admin password for your primary MDC works for root and the Open Directory administrator is diradmin with the same password, then the sheet will not show up. If you have changed those settings then it will pop up.

I'm not sure why your backup MDC is a replica if you reinstalled both machines, but in the initial way you were trying to set things up, Xsan Admin would have tried to make the backup MDC a replica (though it sounded like you didn't get that far).

[dong]

hello,jtownsend, many thanks for your advices.

But, after I unconfigured both of the MDCs (untick the OD in the Server Admin - so there isn't any Open Directory, either master or replica), then run Xsan setup, the sheet still pops up........
I am literally banging my head against wall and pulling my hair off my head now.........what on earth is going on?

Any advices again, please?? Ta

[jtownsend]

Unchecking the checkbox in the Services list in Server Admin only controls whether that service shows in Server Admin, not whether it is enabled or not. Prior to this did you make the servers standalone instead of master or replica?

You should make sure that SSH is enabled on your primary controller, and that you have entered the correct root password and directory domain administrator name and password.

If you want to manage Open Directory manually, you'll need to reinstall Mac OS X Server and pick the option to set up directory servers later instead of picking the option to have Xsan manage users and groups for you.

Short of doing that, you could try tearing down the Open Directory and and setting it up again. To do that, first double check that the backup controller is not an OD replica. If it is convert it to standalone in the Open Directory settings in Server Admin. Then, on the primary controller, make it standalone and then convert back to OD master, making note of the directory administrator name and password you use. You should also make sure you know the root password on the primary controller.

Hope that helps.

[dong]

Hi,jtownsend, thanks a lot again for your message.
It makes a lot more sense for me......I'll give it a try!

[arekdreyer]

While it was a great idea to make it easy for you to set up an Open Directory master, Open Directory replicas, and bind your clients to Open Directory without even thinking about it, I agree with matx and not recommending that you use that route, because tis currently implemented a little strangely, like using the metadata network for Open Directory traffic.

If you really want to start over, and you don't have anything on your Xsan volume yet, then start over. Reinstall Mac OS X Server on your metadata controllers, and when you run through the Server Assistant, DON'T choose "Xsan Metadata Controller". Just choose "Advanced". Then install Xsan from the Xsan install media once you have your servers up and updated.

You don't need to reinstall the OS for your client computers. Run the "Uninstall Xsan" installer from the Xsan install media. Use /Applications/Utilities/Directory Utility.app to remove the old entry for the Open Directory master, and bind again to your new Open Directory master.

You should *definitely* use a directory service, whether Open Directory, or Active Directory. While it is possible to use a metadata controller for Open Directory master or replica, I'd recommend that you keep it simple and dedicate your metadata controllers to just being metadata controllers. It makes troubleshooting much less complex.

[dong]

hi, Arekdreyer, thanks a lot for your post.

Regarding part of your post:

<<You should *definitely* use a directory service, whether Open Directory, or Active Directory. While it is possible to use a metadata controller for Open Directory master or replica, I'd recommend that you keep it simple and dedicate your metadata controllers to just being metadata controllers. It makes troubleshooting much less complex.>>

Do you mean I need another server to be Open Directory Master?
In addition, is the Open Directory(master and replica) just for the public network, not really functional for the private network?

Thanks again. DONG

[matx]

Yes use another server for open directory (od) or ad. And yes this stuff only travels on the public network.

[arekdreyer]

[dong]

Hi, Arek, how are you doing? Thanks for quick reply.
There is still some point that I can't grasp because I am really a newbie.
According to