Bug 1510839

updated config backported.

Awesome. Thanks Ben.

Reproduced on device-mapper-multipath-0.4.9-111
1, # rpm -qa | grep multipath
device-mapper-multipath-libs-0.4.9-111.el7.x86_64
device-mapper-multipath-0.4.9-111.el7.x86_64

2, # multipathd show config
	device {
		vendor "Nimble"
		product "Server"
		path_grouping_policy "group_by_prio"
		path_selector "round-robin 0"
		features "1 queue_if_no_path"
		hardware_handler "1 alua"
		prio "alua"
		failback immediate
		fast_io_fail_tmo 1
		dev_loss_tmo "infinity"
	}



Verified on device-mapper-multipath-0.4.9-111.el7_4.1
1, # rpm -qa | grep multipath
device-mapper-multipath-0.4.9-111.el7_4.1.x86_64
device-mapper-multipath-sysvinit-0.4.9-111.el7_4.1.x86_64
device-mapper-multipath-libs-0.4.9-111.el7_4.1.x86_64
device-mapper-multipath-devel-0.4.9-111.el7_4.1.x86_64
device-mapper-multipath-debuginfo-0.4.9-111.el7_4.1.x86_64

2,  # multipathd show config | grep -C 10 Nimble
		device {
		vendor "Nimble"
		product "Server"
		path_grouping_policy "group_by_prio"
		path_selector "round-robin 0"
		path_checker "tur"    <---------------------------------
		features "1 queue_if_no_path"
		hardware_handler "1 alua"
		prio "alua"
		failback immediate
		dev_loss_tmo "infinity"
	}


Test result:  added TUR path checker to default hardware table for Nimble devices

Hello shivamerla1,
Because we don't have Nimble storage, we can only check default configuration.
Could you help check if it works normally for you?
Thanks in advance.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2018:0142

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days