Install VTrakFS Client on RHEL 6.(x)

The purpose of this document is to provide the required information needed to install, configure, and deploy the installation of the VTrakFS application on a Linux SAN Client.

Requirements:

You must have a supported RHEL release and kernel in order for the VTrakFS client to properly install.

VTrak A-Class SR3.3 Compatibility List v1.01

RHEL 6.x find kernel version command

Open a command-line terminal (select Applications > Accessories > Terminal) or login to the Linux SAN client via ssh and then type:

[root@linux]# uname -r

Find Red Hat Linux Distribution Version

[root@linux]# cat /etc/redhat-release

Or you can use the lsb_release command:

[root@linux]# lsb_release -a

Installation Instructions

2019 Update: Please note that this guide was written in 2016 with version 1.4.1-47250, and the instructions below are still applicable with the latest VTrak A-Class Linux Client Package v1.4.2 (build 51151).

  1. Installing VTrakFS Client 1.4.1-47250

  2. Extract VTrakFSClient-Linux-1.4.1-47250.zip
  3. [root@linux]# tar zxvf VTrakFSClient-Linux-1.4.1-47250.tar.gz
  4. This will extract all necessary files to run the Perl Script.

  5. Change to the directory where the files were extracted to from Step 3
  6. [root@linux]# cd VTrakFSClient-Linux-1.4.1-47250
    [root@linux VTrakFSClient-Linux-1.4.1-47250]# ./installer.pl --with-gui install
  7. Note: The “--with-gui install” is not necessary, it’s only meant for users that have installed RHEL with GNOME.

  8. You will receive the License Agreement and it will ask you to accept it.
  9. Do you accept the terms of License Agreement listed Above?(y/n)y
    Installing ./RHEL/6/x86_64/VTrakFSClient-1.4.1-47250.el6.x86_64.rpm ... [Installed]
    Install client management failed! See /var/log/clientmgr_install.log for details. 
    Installing ./RHEL/6/x86_64/VTrakFSClient-gui-1.4.1-47250.el6.x86_64.rpm ... [Installed]
    Install VTrakFS client success.
    Install VTrakFS client manager failed. <— This error is usually due to not having avahi installed
    Install VTrakFS client gui success.

  10. If you do get this error, you can check the logs to make sure it is due to not having avahi installed.

  11. [root@linux]# cat /var/log/clientmgr_install.log

    Install client management failed. Before install client management, you must install avahi first.
  12. [root@linux]# yum install avahi
  13. Run the script again:

    [root@linux VTrakFSClient-Linux-1.4.1-47250]# ./installer.pl --with-gui install
  14. It will skip the RPMs that were installed and continue the installation. You will see various installed messages indicating that it was installed successfully.

Setting up DM-Multipath

  1. Before setting up DM-Multipath on your system, ensure that your system has been updated and includes the device-mapper-multipath package.

  2. You set up multipath with the mpathconf utility, which creates the multipath configuration file /etc/multipath.conf.

  3. If the /etc/multipath.conf file already exists, the mpathconf utility will edit it.

  4. If the /etc/multipath.conf file does not exist, the mpathconf utility will use the /usr/share/doc/device-mapper-multipath-0.4.9/multipath.conf file as the starting file.

  5. If the /usr/share/doc/device-mapper-multipath-0.4.9/multipath.conf file does not exist the mpathconf utility will create the /etc/multipath.conf file from scratch.
  6. This command enables the multipath configuration file and starts the multipathd daemon.

    [root@linux]# mpathconf --enable --with_multipathd y

Install Promise PerfectPath

  1. Download Linux PerfectPath – Promise Multipath Driver | v.0.0.0.14

  2. The following Linux Operating Systems are supported (Only applicable to PerfectPath):



  3. Extract the zip file to the directory that you downloaded it to.
  4. [root@linux]# cd Promise-Linux-MPIO
    [root@linux Promise-Linux-MPIO]# sh promise.sh A-Class alua fc install
  5. It will ask you to overwrite the multipath.conf file

  6. Hit Y to overwrite the file.

Firewall Prerequisites

  1. If the Linux Firewall is required on the SAN client, you will need add the the A-Class Virtual IP Address to iptables and open Multicast DNS (mDNS) 5353/udp.

    If the firewall or routing is not needed, check that the service is stopped, and stop it if necessary
  2. Add the A-Class Virtual IP to allow incoming traffic:

    [root@linux]# iptables -A INPUT -s <VTrak IP/24> -j ACCEPT
  3. Open Multicast DNS (mDNS) 5353/udp:

    [root@linux]# iptables -A INPUT -p udp -m udp --dport 5353 -j ACCEPT
  4. Restart iptables Service:

    [root@linux]# service iptables restart

Add Linux Client to the A-Class MDC

  1. Access the Virtual IP Address of the A-Class SAN via web browser.

  2. In the web GUI, go to SAN > Clients

  3. Click the + button to add the client.

  4. If the client doesn’t show up, this is due to the RHEL’s firewall settings. (See Firewall Prerequisites above)

  5. Once you have successfully added the RHEL client to the A-Class, you need to give the client Folder Access rights.

  6. In the web GUI, go to File System > Folder and click the gear. Select Access Settings

  7. Give the client access settings accordingly. Your squash setting will depend on how your other SAN clients access files on the filesystem.

  8. Ensure that you enable WriteBack for the Meta Data Write Policy.
  9. Create a mount point on the RHEL SAN Client:

    [root@linux]# cd /mnt 
    [root@linux mnt]# mkdir –p Name_of_Folder
  10. Open the VTrakFS Client and Mount the SAN Volume(s)

  11. The client is located under /usr/sbin/VTrakFSClient

  12. In the VTrakFS GUI, type the Virtual IP Address of the A-Class under Add Server

  13. You should see that the Export Path should state /fsmnt/Name_of_Export_Path

  14. Under Mount Point, select or manually enter the folder location/directory that you created in Step 9.

  15. Mount the SAN volume via the VTrakFS Client.

  16. If you are successful executing the above steps, you should see that the SAN volume is mounted in the folder you created in Step 9.

Mount VTrakFS via Command-Line

  1. Mount Syntax:

    mount -t enfs <A-Class_IP>:/fsmnt/<FS_NAME> /mnt/<FS_NAME>
  2. Mount Example:

    mount –t enfs 10.0.0.1:/fsmnt/VTrakFS1 /mnt/VTrakFS1

Configure fstab

  1. In order to have the VTrakFS mount automatically, you will need to add the filesystem mount sytanx under /etc/fstab using your favorite CLI text-editor.

  2. vi /etc/fstab
  3. Add the following line at the end of you fstab configuration file: 

    <IP address>:/fsmnt/<FS_NAME> /mnt/<FS_NAME> enfs
  4. For Example:

    10.0.0.1:/fsmnt/VTrakFS1 /mnt/VTrakFS1 enfs
  5. After you save the fstab configuration file. Proceed with mounting the volume.

    # mount –a

  6. If you receive any errors, you can try refreshing LMM (LUN Mapping and Masking) on the RHEL SAN client.

Additional Notes

  1. File Locations:

    ./usr/bin/bwclntmgrd
    ./usr/bin/bwmq_broker
    ./usr/bin/initwwn
  2. You can use initwwn to get the HBA port WWPN, with which you can verify the
    A-Class LUNMap entries (the extra 'n' is not a typo): 

    [root@linux]# initwwn n 
    wwpn count:2;wwpn string:210000108607c5e3,210000108607c5e2
  3. To make sure that the machine is accessing the LUNs via multipathd:

    [root@linux]# multipath -ll
    mpathe(2229a00015574dfa3) dm-4 Promise,VTrak A3800f
    size=4.5Tfeatures='1 queue_if_no_path' hwhandler='1 alua' wp=rw
    |-+-policy='round-robin 0' prio=50 status=active
    | `- 8:0:0:2sdc 8:32 active ready running
    `-+-policy='round-robin 0' prio=1 status=enabled
     `-9:0:0:2 sde 8:64 active ready running
    mpathd(2226300015542e3b0) dm-3 Promise,VTrak A3800f
    size=4.5Tfeatures='1 queue_if_no_path' hwhandler='1 alua' wp=rw
    |-+-policy='round-robin 0' prio=50 status=active
    | `- 9:0:0:1sdd 8:48 active ready running
    `-+-policy='round-robin 0' prio=1 status=enabled
     `-8:0:0:1 sdb 8:16 active ready running
  4. It’s always good to make sure your multpath.conf file was written correctly 
    by the PerfectPath driver:

    [root@linux]# cat /etc/multipath.conf
    defaults{
    user_friendly_names yes
    checker_timeout20
    }
     
    blacklist {
     devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*"
     devnode "^(hd|xvd)[a-z][[0-9]*]"
    devnode "^cciss!c[0-9]d[0-9]*[p[0-9]*"
    wwid"ATA"
    }
     
    devices {
    device {
    vendor"Promise"
    product"VTrak"
    path_grouping_policygroup_by_prio
    getuid_callout"/sbin/scsi_id--whitelisted --device=/dev/%n"
    prio"tpg_pref"
    path_checkertur
    path_selector"round-robin 0"
    hardware_handler"1 alua"
    failbackmanual
    rr_weightuniform
    rr_min_io_rq100
    no_path_retryqueue
    features"1 queue_if_no_path"
    product_blacklist"VTrak V-LUN"
    fast_io_fail_tmo20
    dev_loss_tmo86400
    }
     
    device {
    vendor"Promise"
    product"Vess"
    path_grouping_policygroup_by_prio
    getuid_callout"/sbin/scsi_id--whitelisted --device=/dev/%n"
    prio"tpg_pref"
    path_checkertur
    path_selector"round-robin 0"
    hardware_handler"1 alua"
    failbackmanual
    rr_weightuniform
    rr_min_io_rq100
    no_path_retryqueue
    features"1 queue_if_no_path"
    product_blacklist "Vess V-LUN"
    fast_io_fail_tmo 20
    dev_loss_tmo86400
    }
     
    }

Contact Promise Technology Support
Need more help? Save time by starting your support request online and a technical support agent will be assigned to your case.

Promise Technology Technical Support >