After downloading the StorNext client software from the metadata controller, install it on the client system using the correct procedure for your operating system:. Installing the StorNext Client on Linux on page 31. Installing the StorNext Client on Sun Solaris on page 33. Installing the StorNext Client on HP-UX on page 34. The StorNext 6.0.6 release combines an array of appliance and StorNext specific software fixes with important functional enhancements. Packaged to be easily installed on StorNext appliances, this release adds support for LTO-8 with Linear Tape File System (LTFS) formatted media along with end-to-end support for the CentOS 7 update 4 distribution. Jun 21, 2018. When trying to install the files, it may complain that selinux must be turned off. It needs to be off for the program to work correctly. 5. Once the installer is complete, navigate to /usr/cvfs/config. You will need to create a file in there called fsnameservers. In that fsnameservers file, put the IP(s) of you Metadata server(s).
Yosemite brought Xsan 4, which included a whole new way to add clients to an Xsan. Xsan Admin is gone, as of El Capitan, but unchanged from then to macOS Sierra (other than a couple of binaries moving around). These days, instead of scanning the network using Xsan Admin.
We’ll be adding clients using a Configuration Profile. This is actually a much more similar process to adding Xsan clients to a StorNext environment than it is to adding clients to Metadata Controllers running Xsan 3 and below. But instead of making a fsnameservers file, we’re plugging that information into a profile, which will do that work on the client on our behalf. To make the Xsan configuration profile, we’re going to use Profile Manager. With OS X Server 5 and 5.2, this trend continues.To get started, open the Profile Manager web interface and click on a device or device group (note, these are scoped to systems so cannot be used with users and user groups). Then click on the Settings tab for the object you’re configuring Xsan for.Click Edit for the profile listed (Settings for ) and scroll down until you see the entry for Xsan.From the Xsan screen, click Configure.This next screen should look a little similar, in terms of the information you’ve plugged into the Xsan 4 setup screen. Simply enter the name of the Xsan in the Xsan Name field, the IP address or host names of your metadata controllers in the File System Name Servers field and the Authentication Secret from the Xsan screen in the Server app into the Authentication Secret field.
Click OK to close the dialog.Click Save to save your changes. Then you’ll see the Download button become clickable.The profile will download to your /Downloads directory as Settingsfor.mobileconfig. So this was called test and will result in a name of Settingsfortest.mobileconfig. That profile will automatically attempt to install. If this is an MDC where you’re just using Profile Manager to bake a quick profile, or if you don’t actually want to install the profile yet, click Cancel.If you haven’t worked with profiles that much, note that when you click Show Profile, it will show you what is in the profile and what the profile can do.Simply open this file on each client (once you test it of course) and once installed, they’ll automatically configure to join your Xsan. If you don’t have a Profile Manager server, you can customize this file for your environment (YMMV).