search for: no_path_retri

Displaying 20 results from an estimated 24 matches for "no_path_retri".

Did you mean: no_path_retry
2017 Jan 31
1
multipath show config different in CentOS 7?
Hello, suppose I want to use a special configuration for my IBM/1814 storage array luns, then I put something like this in multipath.conf devices { device { vendor "IBM" product "^1814" product_blacklist "Universal Xport" path_grouping_policy "group_by_prio" path_checker
2009 Sep 17
1
multipath using defaults rather than multipath.conf contents for some devices (?) - why ?
hi all We have a rh linux server connected to two HP SAN controllers, one an HSV200 (on the way out), the other an HSV400 (on the way in). (Via a Qlogic HBA). /etc/multipath.conf contains this : device { vendor "(COMPAQ|HP)" product "HSV1[01]1|HSV2[01]0|HSV300|HSV4[05]0" getuid_callout "/sbin/scsi_id -g -u -s /block/%n"
2008 Mar 04
0
Device-mapper-multipath not working correctly with GNBD devices
Hi all, I am trying to configure a failover multipath between 2 GNBD devices. I have a 4 nodes Redhat Cluster Suite (RCS) cluster. 3 of them are used for running services, 1 of them for central storage. In the future I am going to introduce another machine for central storage. The 2 storage machine are going to share/export the same disk. The idea is not to have a single point of failure
2015 Apr 14
1
HBA enumeration and multipath configuration
# cat /etc/redhat-release CentOS Linux release 7.1.1503 (Core) # uname -r 3.10.0-123.20.1.el7.x86_64 Hi, We use iSCSI over a 10G Ethernet Adapter and SRP over an Infiniband adapter to provide multipathing to our storage: # lspci | grep 10-Gigabit 81:00.0 Ethernet controller: Intel Corporation 82599ES 10-Gigabit SFI/SFP+ Network Connection (rev 01) 81:00.1 Ethernet controller: Intel Corporation
2009 Sep 27
0
SUMMARY : multipath using defaults rather than multipath.conf contents for some devices (?) - why ?
The reason for the behaviour observed below turned out to be that the device entry in /etc/multipath.conf was inadvertently appended *after* the devices section , rather than inside it - so that we had #devices { # device { # blah blah # } (file has a bunch of defaults commented out) # etc #} # # device { our settings } *rather than*
2015 Feb 04
0
multipathd
Our cluster was supplied with two IBM DS3400 RAID arrays connected with fibre channel. Both are old and one is failing so we bought an IBM V3700 to replace it. The V3700 complained that we were using the IBM's RDAC driver (true) and we were advised to change to using Linux multipath. I've done that but the default configuration for the DS3400s is: device { vendor
2015 Feb 04
0
multipathd
Am 04.02.2015 um 15:02 schrieb Rushton Martin: > Our cluster was supplied with two IBM DS3400 RAID arrays connected with > fibre channel. Both are old and one is failing so we bought an IBM > V3700 to replace it. The V3700 complained that we were using the IBM's > RDAC driver (true) and we were advised to change to using Linux > multipath. I've done that but the default
2015 Feb 04
0
multipathd
Our cluster was supplied with two IBM DS3400 RAID arrays connected with fibre channel. Both are old and one is failing so we bought an IBM V3700 to replace it. The V3700 complained that we were using the IBM's RDAC driver (true) and we were advised to change to using Linux multipath. I've done that but the default configuration for the DS3400s is: device { vendor
2015 Feb 04
0
multipathd
Our cluster was supplied with two IBM DS3400 RAID arrays connected with fibre channel. Both are old and one is failing so we bought an IBM V3700 to replace it. The V3700 complained that we were using the IBM's RDAC driver (true) and we were advised to change to using Linux multipath. I've done that but the default configuration for the DS3400s is: device { vendor
2015 Feb 04
0
multipathd
Our cluster was supplied with two IBM DS3400 RAID arrays connected with fibre channel. Both are old and one is failing so we bought an IBM V3700 to replace it. The V3700 complained that we were using the IBM's RDAC driver (true) and we were advised to change to using Linux multipath. I've done that but the default configuration for the DS3400s is: device { vendor
2015 Feb 04
0
multipathd
Our cluster was supplied with two IBM DS3400 RAID arrays connected with fibre channel. Both are old and one is failing so we bought an IBM V3700 to replace it. The V3700 complained that we were using the IBM's RDAC driver (true) and we were advised to change to using Linux multipath. I've done that but the default configuration for the DS3400s is: device { vendor
2015 Feb 04
0
multipathd
Our cluster was supplied with two IBM DS3400 RAID arrays connected with fibre channel. Both are old and one is failing so we bought an IBM V3700 to replace it. The V3700 complained that we were using the IBM's RDAC driver (true) and we were advised to change to using Linux multipath. I've done that but the default configuration for the DS3400s is: device { vendor
2006 Apr 13
1
device-mapper multipath
I am attempting to get multipath working with device-mapper (CentOS 4.2 and 4.3). It works on EVERY install of mine from RH (also v4.2, 4.3), but the same multipath.conf imported to all my installs of CentOS do not work. Note that I have tested a working 4.2 configuration file from RH on CentOS 4.2 and a working 4.3 configuration (it changed slightly) on CentOS 4.3. Neither worked. Our production
2015 Feb 05
0
UC multipathd
>-----Original Message----- >From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On >Behalf Of Alexander Dalloz >Sent: 04 February 2015 22:44 >To: CentOS mailing list >Subject: Re: [CentOS] multipathd > >Am 04.02.2015 um 15:02 schrieb Rushton Martin: >> Our cluster was supplied with two IBM DS3400 RAID arrays connected >> with fibre channel.
2015 Feb 05
0
UC multipathd
>-----Original Message----- >From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On >Behalf Of Alexander Dalloz >Sent: 04 February 2015 22:44 >To: CentOS mailing list >Subject: Re: [CentOS] multipathd > >Am 04.02.2015 um 15:02 schrieb Rushton Martin: >> Our cluster was supplied with two IBM DS3400 RAID arrays connected >> with fibre channel.
2015 Feb 05
0
UC multipathd
>-----Original Message----- >From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On >Behalf Of Alexander Dalloz >Sent: 04 February 2015 22:44 >To: CentOS mailing list >Subject: Re: [CentOS] multipathd > >Am 04.02.2015 um 15:02 schrieb Rushton Martin: >> Our cluster was supplied with two IBM DS3400 RAID arrays connected >> with fibre channel.
2015 Feb 05
0
UC multipathd
>-----Original Message----- >From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On >Behalf Of Alexander Dalloz >Sent: 04 February 2015 22:44 >To: CentOS mailing list >Subject: Re: [CentOS] multipathd > >Am 04.02.2015 um 15:02 schrieb Rushton Martin: >> Our cluster was supplied with two IBM DS3400 RAID arrays connected >> with fibre channel.
2015 Feb 05
0
UC multipathd
>-----Original Message----- >From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On >Behalf Of Alexander Dalloz >Sent: 04 February 2015 22:44 >To: CentOS mailing list >Subject: Re: [CentOS] multipathd > >Am 04.02.2015 um 15:02 schrieb Rushton Martin: >> Our cluster was supplied with two IBM DS3400 RAID arrays connected >> with fibre channel.
2015 Feb 05
0
UC multipathd
>-----Original Message----- >From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On >Behalf Of Alexander Dalloz >Sent: 04 February 2015 22:44 >To: CentOS mailing list >Subject: Re: [CentOS] multipathd > >Am 04.02.2015 um 15:02 schrieb Rushton Martin: >> Our cluster was supplied with two IBM DS3400 RAID arrays connected >> with fibre channel.
2013 Sep 18
3
multipathing XCP 1.6
Hello, I hope to be in the right list. my question is the following. I can''t seem to get multipathing configure on XCP 1.6. In XenCenter I was able to enable "Multipath" however, in the LUN under general tab I see " multipath 1 of 1 active", the the CLI I do the following command xe --m node session it list only one session. Can someone help me please? Thanks in