In order to successfully mount the SAN on RHEL 6.5 please follow the following steps:

 

Run all these steps as root

 

1. Installing VTrakFS Client 1.4.1-47250

 

A. Extract VTrakFSClient-Linux-1.4.1-47250.zip (Wherever you downloaded the VTrakFS zip file to)

B. [root@linux]# tar zxvfVTrakFSClient-Linux-1.4.1-47250.tar.gz

C. This will extract all the necessary files to run the Perl script.

D. Change to directory where the files were extracted to from step B

E. [root@linux]# cd VTrakFSClient-Linux-1.4.1-47250

F. [root@linux VTrakFSClient-Linux-1.4.1-47250]#./installer.pl --with-gui install

G. You will receive the License Agreement and it will ask you to accept it.

 

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.

 

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

 

cat /var/log/clientmgr_install.log

 

Install client management failed. Before install client management, you must install avahi first.

 

H. Install avahi via yum install avahi

I. Run the script again, [root@linuxVTrakFSClient-Linux-1.4.1-47250]# ./installer.pl --with-gui install

It will skip the RPMs that were installed and continue the installation. You will see various installed messages indicating that it was installed successfully.

 

 

2. Setting up DM-Multipath

 

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

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

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

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.

If the /usr/share/doc/device-mapper-multipath-0.4.9/multipath.conffile does not exist the mpathconf utility will create the /etc/multipath.conffile from scratch.

 

B. This command enables the multipath configuration file andstarts the multipathd daemon.

 

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

 

C. Run the mpathconf command with the --enable option specified:

 

[root@linux] # mpathconf --enable

 

Execute the following command:

 

[root@linux] service multipathd start

 

 

3. Install PerfectPathV0.0.0.9 for RHEL  http://www.promise.com/Download.aspx?DownloadFileUID=3953

 

A. Extract the zip file to the directory that you downloaded it to.

B. [root@linux]# cd Promise-Linux-MPIO

C. [root@linux Promise-Linux-MPIO]# sh promise.sh A-Class alua fc install

D. It will ask you to overwrite the multipath.conf file

E. Hit Y to overwrite the file.

 

 

4. Add Linux Client to the A-Class.

 

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

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

C. Click the + button to add the client. If the client doesn’t show up, this is due to the RHEL’s firewall settings.

D. In my lab, I have the firewall disabled (makes things easier);however, if you need to block certain services and need to have the firewallon, you need to enable Multicast DNS(mDNS) 5353/udp and open up the TCP port by going to Other Ports. Navigate to TCP port 5353.

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

F. In the web GUI, go to File System>Folder and click on the gear and select Access Settings

G. Give the client access settings accordingly. Your squash setting will depend on how your other clients access files and what UID you want to assign to that FC client.

H. Make sure to give the client WriteBack in regards to the Meta Data Write Policy. This will improve performance.

 

 

5. Create mount point on RHEL FS

 

A. In this example, I will create a folder under /mnt

B. [root@linux]# cd /mnt

C. [root@linux mnt]# mkdir –p Name_of_Folder

 

 

6. Open VTrakFS Client

 

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

B. in the VTrakFS GUI, type the Virtual IP Address of the A-Classunder "Add Server” 

C. You should see that the Export Path should state /fsmnt/Name_of_SAN

D. Under Mount Point, select or manually enter the folderlocation/directory that you created in step 5C

E. Mount the SAN volume via the VTrakFS Client.

F. If successful, you should see that the SAN is mounted in thefolder you created in step 5C

 

If you get any errors, you can try refreshing LMM.

 

To make sure that the machine is seeing the LUNs:

 

[root@PHILRHELphilbendeck]# 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

 

It’s always good to make sure your multpath.conf file was written correctly by the PerfectPath driver:

 

[root@PHILRHELphilbendeck]# 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

}

 

}