Recent Comments

  • Reply to: Xsan4 with StorNext Windows Client Configuration Help!   3 hours 13 min ago

    I've forgotten to mention that ... I was able to configure as local disk.

    Actually, in the VERY end ... our reseller gave us a Brocade 300 and everything now works GREAT!!

  • Reply to: Xsan 4 - Volumes not appearing in Server app after Open Directory reconfig   1 week 4 days ago

    billgarmen wrote:

    I am in the same situation and have followed this, When I do the sudo xsanctl pushConfigUpdate I get the following:

    bash-3.2# sudo xsanctl pushConfigUpdate
    2015-07-22 17:55:31.088 xsanctl[1751:25017] buildSanConfig started
    2015-07-22 17:55:31.089 xsanctl[1751:25017] buildSanConfig about to check LDAP
    2015-07-22 17:55:31.106 xsanctl[1751:25017] buildSanConfig: getXsanConfig said nothing

    I am not sure what already exists or what else I need to do. Thoughts?

    /quote
    Something is messed up in your new LDAP configuration. xsanctl is using ldapi to connect to the local server. When it asks for the com.apple.xsan.conf.SANNAME, it gets no response even though the record exists. Alternatively you don't have the group but you have the com.apple.xsan.auth.SANNAME user.

    This state is very odd to be in if you just configured the SAN again.

  • Reply to: Xsan 4 - Volumes not appearing in Server app after Open Directory reconfig   1 week 4 days ago

    Also I can cvadmin into the xsan, see it and start and stop it. I just cant get it to show up in the server GUI

  • Reply to: Xsan 4 - Volumes not appearing in Server app after Open Directory reconfig   1 week 4 days ago

    I am in the same situation and have followed this, When I do the sudo xsanctl pushConfigUpdate I get the following:

    bash-3.2# sudo xsanctl pushConfigUpdate
    2015-07-22 17:55:31.088 xsanctl[1751:25017] buildSanConfig started
    2015-07-22 17:55:31.089 xsanctl[1751:25017] buildSanConfig about to check LDAP
    2015-07-22 17:55:31.106 xsanctl[1751:25017] buildSanConfig: getXsanConfig said nothing
    2015-07-22 17:55:31.109 xsanctl[1751:25017] buildSanConfig returning error Error Domain=com.apple.OpenDirectory Code=4102 "Could not create the record because one already exists with the same name." UserInfo=0x7fd42ac0d110 {NSLocalizedDescription=Could not create the record because one already exists with the same name., NSLocalizedFailureReason=Could not create the record because one already exists with the same name.}
    xsanctl: error pushing configuration: Error Domain=com.apple.OpenDirectory Code=4102 "Could not create the record because one already exists with the same name." UserInfo=0x7fd42ac0d110 {NSLocalizedDescription=Could not create the record because one already exists with the same name., NSLocalizedFailureReason=Could not create the record because one already exists with the same name.}
    bash-3.2#

    I am not sure what already exists or what else I need to do. Thoughts?

  • Reply to: Xsan 4 - Volumes not appearing in Server app after Open Directory reconfig   1 week 6 days ago

    This is an old Post but I hope this info will help anyone with this issue. Its not that uncommon to need to trash OD and start over. Corruption, change of host name etc.

    First creating a new Volume containing LUNS that where part of an old san will destroy the data. Second never delete anything without a backup. Server BU, Xsan BU, Xsan Config BU, Xsan Metadata dump, etc

    Unlike the past versions of Xsan, Xsan 4 stores an Xsan config group in LDAP. If you trash OD you in turn trash the Xsan SAN info as well. This prevents the GUI from reading the config and prevents Clients from installing the profile to connect to the SAN.

    The best case scenario would be to have an archive of your OD to restore to in the event of corruption. If you do not have a backup here is what you could do if you still have your Xsan config directory (/Library/Preferences/Xsan).

    Use cvadmin and stop and unmount the volumes
    Backup Xsan Config - sudo cp -r /Library/Preferences/Xsan /Library/Preferences/Xsan.old
    Destroy you OD MASTER in server app GUI
    Move server app to the trash
    Destroy any remnants of OD - sudo slapconfig -destroyldapserver
    Remove Certs - sudo rm -R /var/root/Library/Application\ Support/Certificate\ Authority
    Remove Kerberos - sudo rm -R /var/db/krb5kdc
    Remove Xsan Config (MAKE SURE YOU HAVE BACKUP) - sudo rm -r /Library/Preferences/Xsan
    Move server app back to applications
    In Server App Create New OD MASTER
    In Server App turn on Xsan (For SAN NAME use the exact same name you had used before)
    This creates new Xsan config files and a new xsan config group in LDAP
    Close Server app
    Copy the original xsan config files and fsmlist you made a backup of into /Library/Preferences/Xsan
    Copy those config files into LDAP - sudo xsanctl pushConfigUpdate
    Open server app
    You should now have your original volumes listed in the Xsan pan
    You can start the SAN from the GUI

    Once you have your users and groups back make a new archive of OD and Backup of /Library/Preferences/Xsan

  • Reply to: Anyone trying out El Capitan?   1 week 6 days ago

    Will try to test out El Capitan ASAP. Need to test DLC client with an existing StorNext setup.

  • Reply to: Anyone trying out El Capitan?   2 weeks 4 days ago

    Y'all should look at it. The devforum post notes that a main Xsan feature in El Capitan is DLC client support.

  • Reply to: Anyone trying out El Capitan?   3 weeks 5 days ago

    i think 7.0.3 is dead. It doesn't seem to work in 10.10.4 either.

  • Reply to: Anyone trying out El Capitan?   1 month 2 days ago

    I am also question about it now, can anyone who can give me a answer? Thanks for your effort. click here to know more about my question.

  • Reply to: Anyone trying out El Capitan?   1 month 3 days ago

    I'm also curious if the good old Final cut Pro 7.0.3 works with El Capitan.

    Anyone knows about it?