Install the StorNext Client Software on Linux

To run the StorNext client software on Red Hat Linux or SUSE Linux Enterprise, first install the client software package, and then configure the client.

Caution: Before you install the StorNext client software, you must install the kernel headers for the running kernel required for building kernel modules. Obtain the kernel headers package from your Operating System vendor.

Note: Client software is extracted by default to the directory /tmp/stornext.

1. Log on to the StorNext client system as root.
2. Change to the directory where the client software archive file you downloaded is located.

3. Run the client software binary. At the command prompt, where <archive name> is the name of the client software archive file you downloaded, type:

   ./<archive name>

   For example, the file for Red Hat 7 is snfs_client_RedHat7_x86_64.

4. When you are presented with the StorNext End User License Agreement (EULA), press Enter to read the EULA. After reading the EULA enter y to accept the EULA, or enter any other key to decline. After you accept the EULA, the client software is extracted to /tmp/stornext (or to another directory if you specified an alternate location; see StorNext Client System Requirements).

   Note: If the directory into which the files are being extracted does not have enough space, the installation will fail and you will receive an error message. You will need to identify an alternate location into which to extract the files by entering the following command, where <archive name> is the name of the client software archive file you downloaded, and <dir> is the directory into which you want to extract the installation files:

   # ./<archive name> -d <dir>

   Caution: If the directory into which the files are being extracted already exists, you will receive a warning message. If this occurs, either remove the directory and try the installation again, or change the installation directory by entering the following command, where <archive name> is the name of the client software archive file you downloaded, and <dir> is the directory into which you want to extract the installation files:

   # ./<archive name> -d <dir>

   Quantum recommends that you do not force using an existing directory (by using the -f command) because this could lead to additional problems installing the .rpm files.

5. Change directories to /tmp/stornext (or to the alternate directory if you specified one in the step above).

6. List the packages extracted from the software archive file. At the command prompt, type:

   ls -l

   Identify the correct package to install. The correct package begins with snfs-client and ends with the .rpm file name extension.

   Note: The file that ends with .rpm.md5sum is a checksum file, not the client software package.

7. Install the required .rpm files in the following order. Use the command rpm -ivh before each package. For example, rpm -ivh quantum_jansson-<version>.rpm. The files are installed in the directory: /usr/cvfs.
   1. quantum_jansson-<version>.rpm
   2. quantum_libevent-<version>.rpm
   3. quantum_protobuf-<version>.rpm
   4. quantum_zeromq-<version>.rpm
   5. snfs-common-<version>.rpm
   6. snfs-client-<version>.rpm
   7. snfs-extapi-<version>.rpm

   8. snupdate-<version>.rpm

   The following additional .rpm files are required when installing the snfs_client_plus_mover packages:

   Note: For StorNext 6.2, only RHEL 6 and RHEL 7 mover packages are supported.

   9. quantum_curl-<version>.rpm

   10. quantum_libarchive-<version>.rpm

   11. quantum_mariadb-connector-odbc-<version>.rpm

   12. quantum_unixODBC-<version>.rpm

   13. quantum_openssl-util-<version>.rpm

   14. quantum_sndbapi-<version>.rpm

   15. quantum_sndbapicxx-<version>.rpm

   16. snltfs-<version>.rpm

   17. snfs-mover-<version>.rpm

   The following additional .rpm files are required when installing the snfs_gateway-agent packages:

   Note: The gateway packages are only supported on RHEL 6, RHEL 7, SLES 11, and SLES 12.

   18. quantum_curl-<version>.rpm

   19. snfs-gateway-agent-<version>.rpm

8. Configure the boot order for system services.

   Note: Skip this step for Red Hat Enterprise Linux 7.x and SUSE Linux Enterprise Server 12.x clients. The boot order is determined by systemd.unit(5) unit file dependencies.

   Perform one of the following:

   • For Red Hat Linux, at the command prompt, type:

     chkconfig --level 345 cvfs on

   • For SUSE Linux Enterprise, at the command prompt, type:

     chkconfig -s raw 235
     chkconfig -s cvfs 345

9. Edit the /usr/cvfs/config/fsnameservers text file to contain the IP address of the MDC to which the StorNext client will connect.

   The fsnameservers file on the client must be exactly the same as on the MDC. If the fsnameservers file does not exist, use a text editor to create it.

   Note: The fsnameservers file needs to contain only the IP address of the MDC.

10. Create a mount point for the file system. At the command prompt, where <mount point> is the directory path where you want the file system to be mounted, type:

    mkdir -p <mount point>
    chmod 777 <mount point>

    For example: /stornext/snfs1.

11. Add file system entry to /etc/fstab file. To do this, edit the /etc/fstab file so that it contains the following line, where <file system> is the name of the StorNext file system and <mount point> is the directory path created in the previous step:

    <file system> <mount point> cvfs rw,noauto 0 0

12. Reboot the StorNext client system. After reboot, the StorNext file system is mounted at the mount point you specified.

    Note: To manually mount a file system, at the command prompt, where <file system> is the name of the StorNext file system and <volume> is the name of the Xsan volume you will use, and <mount point> is the directory path where you want the file system to be mounted, type:

    mount -t cvfs <file system/volume> <mount point>

To run the StorNext client software on Debian or Ubuntu Linux, first install the client software package, and then configure the StorNext client. To install the client software package:

1. Log on to the StorNext client system as root.
2. Change to the directory where the client software archive file you downloaded is located.
3. Execute the snfs_client_Debian60_26x86_64.bin or snfs_client_Ubuntu14_x86_64.bin package.

4. When you are presented with the StorNext End User License Agreement (EULA), press Enter to read the EULA. After reading the EULA enter y to accept the EULA, or enter any other key to decline.

   After you accept the EULA, the client software is extracted to /tmp/stornext (or to another directory if you specified an alternate location; see StorNext Client System Requirements).

   Note: If the directory into which the files are being extracted does not have enough space, the installation will fail and you will receive an error message. You will need to identify an alternate location into which to extract the files by entering the following command, where <archive name> is the name of the client software archive file you downloaded, and <dir> is the directory into which you want to extract the installation files:

   # ./<archive name> -d <dir>

   Caution: If the directory into which the files are being extracted already exists, you will receive a warning message. If this occurs, either remove the directory and try the installation again, or change the installation directory by entering the following command, where <archive name> is the name of the client software archive file you downloaded, and <dir> is the directory into which you want to extract the installation files:

   # ./<archive name> -d <dir>

   Quantum recommends that you do not force using an existing directory (by using the -f command) because this could lead to additional problems installing the .rpm files.

5. From the /tmp/stornext directory, install all the .deb packages pacakges by typing:

   # dpkg -i *.deb

6. Copy the fsnameservers file from MDC to /usr/cvfs/config/fsnameservers.

   Note: Note: The fsnameservers file on the client must be exactly the same as on the MDC.

7. If this is a SAN client, check to make sure LUNs are visible. At the command prompt, type:

   /usr/cvfs/bin/cvlabel -l

8. Create a mount point, where <snfs1> is the name of the StorNext File System/Xsan volume you are using on your system. For example:

   /stornext/<snfs1>

9. Edit the /etc/fstab to add the client mount options, where <snfs1> is the name of the StorNext File System/Xsan volume you are using on your system. For example:

   <snfs1> /stornext/snfs1 cvfs rw,noauto 0 0

10. Start the file system service. At the command prompt, type:

    service cvfs start
11. Verify file systems are mounted.

To run the StorNext Client software on Sun Solaris, first install the client software package, and then configure the client.

1. Log on to the StorNext Client system as root.
2. Change to the directory where the client software archive file you downloaded is located.

3. Run the client software binary. At the command prompt, where <archive name> is the name of the client software archive file you downloaded, type:

   ./<archive name>

   For example, the file for RH5 is snfs_client_RedHat50AS_26x86_64.bin.

4. When you are presented with the StorNext End User License Agreement (EULA), press Enter to read the EULA. After reading the EULA enter y to accept the EULA, or enter any other key to decline. After you accept the EULA, the client software is extracted to /tmp/stornext (or to another directory if you specified an alternate location; see StorNext Client System Requirements).

   Note: If the directory into which the files are being extracted does not have enough space, the installation will fail and you will receive an error message. You will need to identify an alternate location into which to extract the files by entering the following command, where <archive name> is the name of the client software archive file you downloaded, and <dir> is the directory into which you want to extract the installation files:

   # ./<archive name> -d <dir>

   Caution: If the directory into which the files are being extracted already exists, you will receive a warning message. If this occurs, either remove the directory and try the installation again, or change the installation directory by entering the following command, where <archive name> is the name of the client software archive file you downloaded, and <dir> is the directory into which you want to extract the installation files:

   # ./<archive name> -d <dir>

   Quantum recommends that you do not force using an existing directory (by using the -f command) because this could lead to additional problems installing the .rpm files.

   Caution: If you have other Quantum products that share the zeromq and protobuf packages, it is recommend you use the newer versions. Consult the other product’s documentation on how to remove the older versions.

5. Change to the /tmp/stornext directory.

6. Install the required SNFS packages first, and then install the client software package. At the command prompt, type:

   pkgadd -d . QUANTUMjansson
   pkgadd -d . QUANTUMprotobuf
   pkgadd -d . QUANTUMzeromq
   pkgadd -d . ADICsnfs
   pkgadd -d . QUANTUMsnupdate
   
   This package contains scripts which will be executed with super-user permission during the process of installing this package.
   
   Do you want to continue with the installation of <ADICsnfs> [y,n,?]
7. Type y to confirm installation of the ADICsnfs package.

8. Edit the /usr/cvfs/config/fsnameservers text file to contain the IP address of the MDC to which the client will connect. The fsnameservers file on the client must be exactly the same as on the MDC. If the fsnameservers file does not exist, use a text editor to create it.

   Note: The fsnameservers file needs to contain only the IP address of the MDC. For example, if the IP address for the MDC is 192.168.143.1, then the fsnameservers file should contain a single line with 192.168.143.1

9. Create a mount point for the file system. At the command prompt, where <mount point> is the directory path where you want the file system to be mounted. For example: /stornext/snfs1, type:

   mkdir -p <mount point>
   chmod 777 <mount point>

10. Configure the file system to automatically mount after a reboot. To do this, edit the /etc/vfstab file so that it contains the following line, where <file system> is the name of the StorNext file system and <mount point> is the directory path created in Step 9:

    <file system> - <mount point> cvfs 0 auto rw

    While a reboot is not required at this time, in the future, a reboot of the client will mount the StorNext file system at the mount point you specified.

11. Restart StorNext services on the solaris client. To restart the services, type:

    /usr/cvfs/bin/cvfs stop
    /usr/cvfs/bin/cvfs start

    To manually mount a file system, at the command prompt, where <file system/volume> is the name of the StorNext file system/Xsan volume you will use, and <mount point> is the directory path where you want the file system to be mounted, type:

    mount -F cvfs <file system/volume> <mount point>

To run the StorNext Client software on HP-UX, first install the client software package, and then configure the client.

1. Log on to the StorNext Client system as root.
2. Change to the directory where the client software archive file you downloaded is located.

3. Run the client software binary. At the command prompt, where <archive name> is the name of the software archive file you downloaded from the MDC, type:

   ./<archive name>

   For example, the file for RH5 is snfs_client_RedHat50AS_26x86_64.bin.

4. When you are presented with the StorNext End User License Agreement (EULA), press Enter to read the EULA. After reading the EULA enter y to accept the EULA, or enter any other key to decline. After you accept the EULA, the client software is extracted to /tmp/stornext (or to another directory if you specified an alternate location; see StorNext Client System Requirements).

5. Note: If the directory into which the files are being extracted does not have enough space, the installation will fail and you will receive an error message. You will need to identify an alternate location into which to extract the files by entering the following command, where <archive name> is the name of the client software archive file you downloaded, and <dir> is the directory into which you want to extract the installation files:

   # ./<archive name> -d <dir>

6. Caution: If the directory into which the files are being extracted already exists, you will receive a warning message. If this occurs, either remove the directory and try the installation again, or change the installation directory by entering the following command, where <archive name> is the name of the client software archive file you downloaded, and <dir> is the directory into which you want to extract the installation files:

   # ./<archive name> -d <dir>

   Quantum recommends that you do not force using an existing directory (by using the -f command) because this could lead to additional problems installing the .rpm files.

7. Change directories to /tmp/stornext.

8. List the packages extracted from the software archive file. At the command prompt, type:

   ls -l

   Identify the correct package to install. The correct package begins with snfs-client and ends with the .depot file name extension.

9. Install the required SNFS packages first, and then install the client software package. At the command prompt, type:

   swinstall -s /tmp/stornext/quantum_zeromq-<version>.depot -x mount_all_filesystems=false \*
   swinstall -s /tmp/stornext/quantum_protobuf-<version>.depot-xmount_all_filesystems=false \*
   swinstall -s /tmp/stornext/snfs-client_hpux-<version>.depot -x mount_all_filesystems=false \*

10. Edit the /usr/cvfs/config/fsnameservers text file to contain the IP address of the MDC to which the client will connect. The fsnameservers file on the client must be exactly the same as on the MDC. If the fsnameservers file does not exist, use a text editor to create it.

    Note: The fsnameservers file needs to contain only the IP address(es) of the MDC(s).

11. Create a mount point for the file system. At the command prompt, where <mount point> is the directory path where you want the file system to be mounted. For example: /stornext/snfs1, type:

    mkdir -p <mount point>
    chmod 777 <mount point>

12. Add file system entry to /etc/fstab file. To do this, edit the /etc/fstab file so that it contains the following line:

    /stornext/snfs1 /stornext/snfs1 cvfs rw,noauto,<fsname>=RH5-DATA 0 0
    • fsname defines the StorNext file system name (for example, RH5-DATA).

    • /stornext/snfs1 is the StorNext mount point.

    Note: Regarding the two file system mount points in the /etc/fstab file, the first mount point entry is ignored and the second mount point entry is the StorNext mount point you want to have the file system mounted on.

13. Reboot the client system. After reboot, the StorNext file system is mounted at the mount point you specified. To manually mount a file system, where <mount point> is the directory path where you want the file system to be mounted, at the command prompt type:

    mount -F cvfs <mount point> <mount point>

To run the StorNext Client software on IBM AIX, first install the client software package, and then configure the client.

1. Log on to the StorNext Client system as root.
2. Change to the directory where the client software archive file you downloaded is located.

3. Run the client software binary. At the command prompt, where <archive name> is the name of the software archive file you downloaded, type:

   ./<archive name>

   For example, the file for RH5 is snfs_client_RedHat50AS_26x86_64.bin.

4. When you are presented with the StorNext End User License Agreement (EULA), press Enter to read the EULA. After reading the EULA enter y to accept the EULA, or enter any other key to decline. After you accept the EULA, the client software is extracted to /tmp/stornext (or to another directory if you specified an alternate location; see StorNext Client System Requirements).

   Note: If the directory into which the files are being extracted does not have enough space, the installation will fail and you will receive an error message. You will need to identify an alternate location into which to extract the files by entering the following command, where <archive name> is the name of the client software archive file you downloaded, and <dir> is the directory into which you want to extract the installation files:

   # ./<archive name> -d <dir>

   Caution: If the directory into which the files are being extracted already exists, you will receive a warning message. If this occurs, either remove the directory and try the installation again, or change the installation directory by entering the following command, where <archive name> is the name of the client software archive file you downloaded, and <dir> is the directory into which you want to extract the installation files:

   # ./<archive name> -d <dir>

   Quantum recommends that you do not force using an existing directory (by using the -f command) because this could lead to additional problems installing the .rpm files.

5. Change directories to /tmp/stornext.

6. List the packages extracted from the software archive file. At the command prompt, type:

   ls -l

   Identify the correct package to install. The correct package begins with snfs and ends with the .bff file name extension.

7. Install the required SNFS packages, and then install the client software package. At the command prompt, type:

   installp -ac -d . all

8. Edit the /usr/cvfs/config/fsnameservers file for the IP address of the MDC to which the client will connect. The fsnameservers file on the StorNext Client must be exactly the same as on the MDC. If the fsnameservers file does not exist, use a text editor to create it.

   Note: The fsnameservers file needs to contain only the IP address(es) of the MDC(s).

9. Create a mount point for the file system. At the command prompt, where <mount point> is the directory path where you want the file system to be mounted, type:

   mkdir -p <mount point>
   chmod 777 <mount point>

   For example: /stornext/snfs1.

10. Configure the file system to automatically mount. For default mount options, at the command prompt, where <file system> is the name of the StorNext file system and <mount point> is the directory path created in Step 9, type:

    crfs -v cvfs -d <file system> -a verbose=yes -a type=cvfs -A yes -m <mount point>

    Or, if any mount options are required, where <mount options> is a comma separated list. StorNext mount options are documented in the mount_cvfs(8) man-page, type:

    crfs -v cvfs -d <file system> -a verbose=yes –a options=<mount options> -a type=cvfs -A yes -m <mount point>

    The StorNext file system is mounted at the mount point you specified.

    Note: To manually mount a file system, at the command prompt, where <mount point> is the directory path where you want the file system to be mounted, type:

    mount <mount point>

11. Start the new StorNext client software. At the command prompt, type:

    /etc/rc.cvfs start

    Alternatively, you can reboot the system.

In Red Hat Enterprise Linux 7.x and SUSE Linux Enterprise Server 12.x clients, the init.d(7)/service(8) system service utilities have been replaced by the systemd(1)/systemctl(1) utilities.

The most notable difference is that the systemctl(1) utility does not write status output to the controlling TTY during start and stop operations. The user must run systemctl status cvfs after the start or stop request to view the status information.

Red Hat Enterprise Linux 7.x and SUSE Linux Enterprise Server 12.x clients provide a script in /sbin/service for convenience and compatibility that is simply a wrapper that calls the systemctl(1) command with appropriate arguments. Like systemctl(1), the service(8) script will not write status output to the TTY during start and stop operations. The user must execute /sbin/service cvfs status to view the status information.

Additional kernel module verification is enabled in Red Hat Enterprise Linux 7.x and SUSE Linux Enterprise Server 12.x clients. Since StorNext is not shipped with a signed cvfs kernel module, an additional warning message will be seen in the syslog when the cvfs kernel module is loaded:

You can safely ignore the warning message if the kernel does not check the module signature.

If you use UEFI Secure Boot, your system requires and checks for a signed module; if you load cvfs.ko, then the process fails and displays an error:

Red Hat Enterprise Linux and Ubuntu provide tools to self sign a module; if you use UEFI Secure Boot, see the RHEL and Ubuntu product documentation on how to sign a kernel module for secure boot.