Beginning with Apple's macOS El Capitan (10.11), support is provided to mount Xsan volumes as StorNext DLC clients. This section provides additional information which should clarify the conditions necessary for this mount to succeed.
When the StorNext services are loaded, the environment is scanned to determine the default mount type - storage area network (SAN) with access to data disks, or DLC with proxy access to data disks through a StorNext gateway node.
If a fibre channel card is detected or internet Small Computer Systems Interface (iSCSI) logical unit numbers (LUNs) are present, the default mode is SAN. If neither or these conditions are true, the default mode is DLC.
In the case that a SAN mount is attempted and not all data LUNs for the file system are present, the mount fails and no error message is logged. If a DLC mount is desired, there are several ways to accomplish this.
First, if the presence of iSCSI LUNs is causing the SAN mount attempt, and these LUNs are not needed, the iSCSI targets can be disconnected. If this is done, the StorNext service must be unloaded and loaded to detect the change.
Example of unload and load:
sh-3.2# launchctl unload /System/Library/LaunchDaemons/com.apple.xsan.plist
sh-3.2# launchctl load -w /System/Library/LaunchDaemons/com.apple.xsan.plist
If iSCSI LUNs or a fibre channel card are present, the DLC mount is accomplished by indicating this to the driver. There are two ways to achieve this:
- Set the Xsan Preferences Payload "preferDLC" for the Volume that is to be DLC Mounted
- Set the diskproxy=client Mount Options in the /etc/fstab File
Example of setting preferDLC payload and verifying:
For more information on the preferDLC payload and Xsan configuration profiles, see https://support.apple.com/en-us/HT205333.
An alternative way to indicate to the driver that a DLC mount is desired to set the
diskproxy=client mount options in the
Example of the
diskproxy=client mount options in
In either of the above scenarios, a driver unload and load must be performed to enact the change. Once the Volume is mounted, its status as a DLC client can be verified by using the sub-command
who of the
cvadmin CLI. First select the file system, then enter
who. Look for the
C after the
CLI in the client entry.
Example of the
cvadmin who sub-command: