Follow

How to allow mutipathing on RedHat with paths presented by Quantastor.

Subject:

When Quantastor is presenting multiple paths to a RedHat system there is additional configuration that will be needed on the RedHat server to allow the paths to be seen.

 

Description:

Here are the steps that need to be performed on the RedHat server to allow mutipathing to the Quantastor:

 

1.

Edit the /etc/multipath.conf file.

Under the 'blacklist_exceptions section add the OSNEXUS QuantaStor device definition below to ensure that the OSNEXUS FC LUN devices are whitelisted:

device {
vendor "OSNEXUS"
product "QUANTASTOR"
}

 

2.

Under the 'devices' section add a new definition for the OSNEXUS QuantaStor FC LUN devices:

devices{

device {
vendor "OSNEXUS"
product "QUANTASTOR"
getuid_callout "/lib/udev/scsi_id --whitelisted --replace-whitespace --device=/dev/%n"
prio alua
hardware_handler "1 alua"
path_grouping_policy group_by_prio
failback immediate
no_path_retry 10
rr_min_io 100
path_checker tur
rr_weight uniform
}

}

 

3.

Next restart the Redhat multipathing driver for the new multipath driver definition to go into effect:

# service multipathd restart

 

4.

Next you can verify the devices which appear, that their paths are active and the ALUA grouping for the 'active/passive' node using the 'multipath -ll' command.

Below is the example output from this command LUN's presented to a RHEL 6.8 client server via FC:


# multipath -ll
mpathz (23763656538663133) dm-5 OSNEXUS,QUANTASTOR
size=40G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw
|-+- policy='round-robin 0' prio=50 status=active
| |- 4:0:1:25 sdg 8:96 active ready running
| `- 5:0:1:25 sdo 8:224 active ready running
`-+- policy='round-robin 0' prio=0 status=enabled
|- 4:0:0:25 sdc 8:32 active ready running
`- 5:0:0:25 sdk 8:160 active ready running
mpathy (23738366662623337) dm-3 OSNEXUS,QUANTASTOR
size=40G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw
|-+- policy='round-robin 0' prio=50 status=active
| |- 4:0:1:24 sdf 8:80 active ready running
| `- 5:0:1:24 sdn 8:208 active ready running
`-+- policy='round-robin 0' prio=0 status=enabled
|- 4:0:0:24 sdb 8:16 active ready running
`- 5:0:0:24 sdj 8:144 active ready running
mpathab (26434666531393831) dm-2 OSNEXUS,QUANTASTOR
size=40G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw
|-+- policy='round-robin 0' prio=50 status=active
| |- 4:0:1:27 sdi 8:128 active ready running
| `- 5:0:1:27 sdq 65:0 active ready running
`-+- policy='round-robin 0' prio=0 status=enabled
|- 4:0:0:27 sde 8:64 active ready running
`- 5:0:0:27 sdm 8:192 active ready running
mpathaa (23762353263653365) dm-4 OSNEXUS,QUANTASTOR
size=40G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw
|-+- policy='round-robin 0' prio=50 status=active
| |- 4:0:1:26 sdh 8:112 active ready running
| `- 5:0:1:26 sdp 8:240 active ready running
`-+- policy='round-robin 0' prio=0 status=enabled
|- 4:0:0:26 sdd 8:48 active ready running
`- 5:0:0:26 sdl 8:176 active ready running

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

Powered by Zendesk