This discussion is locked
Him-Andersen

Q: Xsan - Cant add clients, tried everything.

So.

 

 

Im sitting here with a Mac Pro as MDC, and a 20TB SAN.

Ive added multiple clients on here before, and never had any issues.

Now I need to add more clients, but it simply won't work! I get the "client config error" when using the MDC to add them.

 

 

I have tried to remove the xsan config folder, disabling/enabling xsan, restarted all machines and servers etc.

 

 

When I remove everything from the client, and go to the xsan to add a machine, I can see the machine, I can authenticate, and I don't make it a MDC - but then it starts to write the conf file, and it fails.

 

 

Anyone has any suggestions at all?

Posted on Mar 2, 2015 12:12 AM

Close

Q: Xsan - Cant add clients, tried everything.

  • All replies
  • Helpful answers

  • by Claudio Sanchez1,

    Claudio Sanchez1 Claudio Sanchez1 Mar 2, 2015 9:55 AM in response to Him-Andersen
    Level 1 (65 points)
    Mar 2, 2015 9:55 AM in response to Him-Andersen

    How does it "not work"? What exactly did you try? How did it fail? What error did you see in the user interface and logs? If you have some clients that are working, what's different about them and the ones you're trying to add? What version of OS X is MDC and client?


    Assuming this is pre-Yosemite: Make sure the client is able to run "sudo cvlabel -c" without hanging, and if not fix fibre channel. Remove all LDAP and AD bindings in Directory Utility before adding to the SAN. (If this helps, then add them back later if adding to the SAN doesn't re-add them.) Make sure the network is healthy between Xsan Admin system and client (no packet loss).

  • by Him-Andersen,

    Him-Andersen Him-Andersen Mar 3, 2015 12:50 AM in response to Claudio Sanchez1
    Level 1 (0 points)
    Mar 3, 2015 12:50 AM in response to Claudio Sanchez1

    HI Claudio.

     

    When I try to add the clients in the Xsan admin I can authenticate etc. but then it comes  up with the "can't write config file" error.

    These machines have been connected to the Xsan before, but I removed all config files etc. All the machines and servers are 10.9 newest version.

     

    Ill try the "sudo cvlabel -c" and report back.

     

    Thank you so far!

  • by Him-Andersen,

    Him-Andersen Him-Andersen Mar 3, 2015 6:39 AM in response to Claudio Sanchez1
    Level 1 (0 points)
    Mar 3, 2015 6:39 AM in response to Claudio Sanchez1

    So I ran the sudo command, and I received a perfect "reply" right away.

    I can see the LUNS there, so does it mean it should be working?

  • by Claudio Sanchez1,

    Claudio Sanchez1 Claudio Sanchez1 Mar 4, 2015 7:09 PM in response to Him-Andersen
    Level 1 (65 points)
    Mar 4, 2015 7:09 PM in response to Him-Andersen

    That's good, but that's just one potential problem that might have caused this. I had two more suggestions above:

     

    "Remove all LDAP and AD bindings in Directory Utility before adding to the SAN. (If this helps, then add them back later if adding to the SAN doesn't re-add them.) Make sure the network is healthy between Xsan Admin system and client (no packet loss)."

     

    Also check this:

     

    Make sure xsanmgrd is running--or servermgrd if this is Lion or older. Note that if you've deleted /Library/Preferences/com.apple.xsanmgrd.plist from the system, that file won't regenerate itself, and xsanmgrd won't start. You'll have to copy it over from another system.

     

    If you have really old pre-Lion systems (which required an Xsan serial number), you should check that you don't have serial number errors in your system log or serial number log. You can't add a client if its serial number is already in use.