Displaying 2 results from an estimated 2 matches for "hsv400".
2009 Sep 27
0
SUMMARY : multipath using defaults rather than multipath.conf contents for some devices (?) - why ?
...#
device {
our settings
}
*rather than*
devices {
device {
our settings
}
}
Also - looking more closely at our multipath.conf.defaults, there is an entry for
a product pattern HSV2.*
That would explain why the multipath settings for the HSV200 looked different to
the HSV400 - the HSV200 was picking up a different set of defaults.
However still not exactly what we had specified.
(sort of like CSS behaviour....."cascading multipath.conf defaults" ! :-) )
You also possibly need to pay attention to the basic whitespace formatting of this
file - for example I...
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"
prio_callout &...