similar to: UC multipathd

Displaying 20 results from an estimated 2000 matches similar to: "UC multipathd"

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 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
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 05
0
UC multipathd
Yep, that's what I do at home. The trouble for off-net machines is the download time - over 24 hours for CentOS 7 + epel, and then copy over. If you don't grab everything, the one package you miss is the one that stops the update. :-( >-----Original Message----- >From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On >Behalf Of John R Pierce >Sent: 04
2015 Feb 05
0
UC multipathd
Yep, that's what I do at home. The trouble for off-net machines is the download time - over 24 hours for CentOS 7 + epel, and then copy over. If you don't grab everything, the one package you miss is the one that stops the update. :-( >-----Original Message----- >From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On >Behalf Of John R Pierce >Sent: 04
2015 Feb 05
0
UC multipathd
Yep, that's what I do at home. The trouble for off-net machines is the download time - over 24 hours for CentOS 7 + epel, and then copy over. If you don't grab everything, the one package you miss is the one that stops the update. :-( >-----Original Message----- >From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On >Behalf Of John R Pierce >Sent: 04
2015 Feb 05
0
UC multipathd
Yep, that's what I do at home. The trouble for off-net machines is the download time - over 24 hours for CentOS 7 + epel, and then copy over. If you don't grab everything, the one package you miss is the one that stops the update. :-( >-----Original Message----- >From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On >Behalf Of John R Pierce >Sent: 04
2015 Feb 05
0
UC multipathd
Yep, that's what I do at home. The trouble for off-net machines is the download time - over 24 hours for CentOS 7 + epel, and then copy over. If you don't grab everything, the one package you miss is the one that stops the update. :-( >-----Original Message----- >From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On >Behalf Of John R Pierce >Sent: 04
2015 Feb 05
0
UC multipathd
Yep, that's what I do at home. The trouble for off-net machines is the download time - over 24 hours for CentOS 7 + epel, and then copy over. If you don't grab everything, the one package you miss is the one that stops the update. :-( >-----Original Message----- >From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On >Behalf Of John R Pierce >Sent: 04
2013 Nov 07
1
IBM Storwize V3700 storage - device names
Hello, I have IBM Storwize V3700 storage, connected to 2 IBM x3550 M4 servers via fiber channel. The servers are with QLogic ISP2532-based 8Gb Fibre Channel to PCI Express HBA cards and run Centos 5.10 When I export a volume to the servers, each of them sees the volume twice, i.e /dev/sdb and /dev/sdc, with the same size. Previously I have installed many systems with IBM DS3500 series of
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