• Mac OS X,  Mac Security,  Mass Deployment

    Yosemite and The Xsan Command Line

    Let’s start out with what’s actually available in the Server Admin CLI: serveradmin. The serveradmin command, followed by settings, followed by san shows a few pieces of information: bash-3.2# serveradmin settings san
san:computers = _empty_array
san:primaryController = "95C99FB1-80F2-5016-B9C3-BE3916E6E5DC"
san:ownerEmail = "krypted@me.com"
san:sanName = "krypted"
san:desiredSearchPolicy:_array_index:0 = ""
san:serialNumbers = _empty_array
san:dsType = 0
san:ownerName = "Charles Edge"
san:managePrivateNetwork = yes
san:metadataNetwork = "10.0.0.0/24"
san:numberOfFibreChannelPorts = 2
san:role = "CONTROLLER" Here, we see the metadata network, the GUID of the primary (active) MDC, the name of the SAN, an array of serial numbers (if applicable – in a purely Mountain Lion/Mavericks SAN they aren’t), the owner info plugged in earlier and the metadata network interface being used. Next, we’ll take a peak at…

  • Mac OS X,  Mac OS X Server,  Xsan

    xsanctl

    The xsanctl command allows you to manage basic events on an Xsan. The following options are available to xsanctl: disksChanged – Causes the FSS to scan the available LUNs mount – Mounts a volume ping – Verifies FSS (File System Server) responsiveness sanConfigChanged – Causes the FSS to reload the volume configuration file unmount – Unmounts a volume These options are used following the xsanctl command and are then followed with any options they themselves may have. For example, if you want to mount a volume you would run the xsanctl command followed by the mount option/verb and then the name of a volume, like so (assuming volume name of…