2.3 clients on a 3.0 XSAN?

nrausch's picture
Forums: 

Greetings gentlemen!

I just built a new 10.8.1 / xsan 3.0 san.
all the new MDCs, other servers, and 2 edit machines upgraded to 10.8.1 and connect just fine.

2 of the edit machines are older Intel mac pros.

Couldn't go up to 10.8, so we went to 10.7.5. They should be able to join the XSAN, but i get the same error on both when trying to add. They both authenticate, then fail to write the config files.

Is there something easy I may be missing? Or is there a mac pro hardware requirement that I don't know about?

Any help appreciated!

Thanks.

DNS/ OD is solid

nrausch's picture

nrausch wrote:
Or is there a mac pro hardware requirement that I don't know about?
/quote

I guess I'm asking... Even though these mac pro machines won't go up to 10.8, shouldn't they be able to join a 10.8/3.0 XSAN as 10.7.5/2.3 clients? Or does the same limitation that keeps them from running 10.8 also keep disqualified to join a 10.8/3.0 XSAN?

csanchez's picture

nrausch wrote:
Even though these mac pro machines won't go up to 10.8, shouldn't they be able to join a 10.8/3.0 XSAN as 10.7.5/2.3 clients?/quote

Yes. http://support.apple.com/kb/HT3755

Are you managing OD users and groups in Xsan Admin? Are the Lion systems already bound to OD? If yes to both, on one of the systems that can't be added to the SAN, unbind in Directory Utility and then try adding to the SAN again.

nrausch's picture

He have a stand alone OD, users not managed by xsan admin.
each machine has a local admin account which we use when we're adding machines to san and installing software etc...
I did try unbinding and rebinding anyway.

Any other thoughts?

I was thinking it may be a permissions issue keeping the config files from being written? If it wasn't the same issue on both of the Lion machines I would feel better. But since it's both and they are the same hardware, I'm concerned.

nrausch's picture

csanchez wrote:

Are you managing OD users and groups in Xsan Admin? Are the Lion systems already bound to OD? If yes to both, on one of the systems that can't be added to the SAN, unbind in Directory Utility and then try adding to the SAN again./quote

Even though we are managing users with a standalone OD, this worked.
I unbound the machines from any OD at all. Added to SAN, and the directory service on the clients automatically configured to the correct OD.

Weird, but fine with me!

Thanks for the help!