I run Solaris 10 on a V240 with Emulex HBA, attached to a DS4800. I
set "mpxio-disable="no";" in /kernel/drv/fp.conf and did a reboot. So
this makes me belive that multipathing is enabling.

Unfortunately I see still all the pathes to the disks:

ROOT@serverA:/root# luxadm probe
No Network Array enclosures found in /dev/es

Found Fibre Channel device(s):
  Node WWN:200400a0b81163b8  Device Type:Disk device
    Logical Path:/dev/rdsk/c2t201400A0B81163B8d0s2
    Logical Path:/dev/rdsk/c3t201500A0B81163B8d0s2
  Node WWN:200400a0b81163d4  Device Type:Disk device
    Logical Path:/dev/rdsk/c2t201400A0B81163D4d0s2
    Logical Path:/dev/rdsk/c3t201500A0B81163D4d0s2

There is another V240 with exact the same hardware where multipathing
works perfecly fine, but this one won't. Is there anything I can
check?

Thanks, Stefan

Stifi <stefanjuon@yahoo.com> wrote:
> I run Solaris 10 on a V240 with Emulex HBA, attached to a DS4800. I
> set "mpxio-disable="no";" in /kernel/drv/fp.conf and did a reboot. So
> this makes me belive that multipathing is enabling.

stmsboot -e


Sami

-- 
  .signature: no such file or directory

On 4 Jul., 13:43, Sami Ketola <Sami.Ket...@iki.finland.invalid> wrote:
> Stifi <stefanj...@yahoo.com> wrote:
> > I run Solaris 10 on a V240 with Emulex HBA, attached to a DS4800. I
> > set "mpxio-disable="no";" in /kernel/drv/fp.conf and did a reboot. So
> > this makes me belive that multipathing is enabling.
>
> stmsboot -e
>
> Sami
>
> --
>   .signature: no such file or directory

....no improvement after running stmsboot -e ...

Stifi <stefanjuon@yahoo.com> wrote:
> There is another V240 with exact the same hardware where multipathing
> works perfecly fine, but this one won't. Is there anything I can
> check?

Compare the /kernel/drv/scsi_vhci.conf files on both machines.  You may
need a custom "device-type-scsi-options-list" option.

-- 
Brandon Hume    - hume -> BOFH.Ca, http://WWW.BOFH.Ca/

On 4 Jul., 15:28, hume.spamfil...@bofh.ca wrote:
> Stifi <stefanj...@yahoo.com> wrote:
> > There is another V240 with exact the same hardware where multipathing
> > works perfecly fine, but this one won't. Is there anything I can
> > check?
>
> Compare the /kernel/drv/scsi_vhci.conf files on both machines.  You may
> need a custom "device-type-scsi-options-list" option.
>
> --
> Brandon Hume    - hume -> BOFH.Ca,http://WWW.BOFH.Ca/

Yes, on both servers the file is identical...I added these lines just
for fun:

device-type-scsi-options-list=
"IBM   FAStT", "IBM-1815", "FAStT-0914", "symmetric-option";
 symmetric-option = 0x1000000;

....and did a reboot. Still the same output of "luxadm probe". Maybe I
have to play with the options.

Stifi <stefanjuon@yahoo.com> wrote:
> ...and did a reboot. Still the same output of "luxadm probe". Maybe I
> have to play with the options.

Was it a reconfiguring reboot?  Are the two V240s at the same patchlevel?

-- 
Brandon Hume    - hume -> BOFH.Ca, http://WWW.BOFH.Ca/

On Wed, 04 Jul 2007 08:45:02 -0700, Stifi wrote:

> On 4 Jul., 15:28, hume.spamfil...@bofh.ca wrote:
>> Stifi <stefanj...@yahoo.com> wrote:
>> > There is another V240 with exact the same hardware where multipathing
>> > works perfecly fine, but this one won't. Is there anything I can
>> > check?
>>
>> Compare the /kernel/drv/scsi_vhci.conf files on both machines.  You may
>> need a custom "device-type-scsi-options-list" option.
>>
>> --
>> Brandon Hume    - hume -> BOFH.Ca,http://WWW.BOFH.Ca/
> 
> Yes, on both servers the file is identical...I added these lines just
> for fun:
> 
> device-type-scsi-options-list=
> "IBM   FAStT", "IBM-1815", "FAStT-0914", "symmetric-option";
>  symmetric-option = 0x1000000;
> 
> ...and did a reboot. Still the same output of "luxadm probe". Maybe I
> have to play with the options.

The VendorID must have 8 characters in it.  Most likely you need 5 spaces 
of padding after the "IBM" and then the 4 digit machine code.  Run format 
and get the inquiry results from one of the disks to determine what the 
Vendor ID and Product ID of the array is.  After putting that stuff in 
the scsi_vhci.conf file reboot with "stmsboot -u"

On 5 Jul., 02:25, "Alexander J. Maidak" <ajmai...@mchsi.com> wrote:
> On Wed, 04 Jul 2007 08:45:02 -0700, Stifi wrote:
> > On 4 Jul., 15:28, hume.spamfil...@bofh.ca wrote:
> >> Stifi <stefanj...@yahoo.com> wrote:
> >> > There is another V240 with exact the same hardware where multipathing
> >> > works perfecly fine, but this one won't. Is there anything I can
> >> > check?
>
> >> Compare the /kernel/drv/scsi_vhci.conf files on both machines.  You may
> >> need a custom "device-type-scsi-options-list" option.
>
> >> --
> >> Brandon Hume    - hume -> BOFH.Ca,http://WWW.BOFH.Ca/
>
> > Yes, on both servers the file is identical...I added these lines just
> > for fun:
>
> > device-type-scsi-options-list=
> > "IBM   FAStT", "IBM-1815", "FAStT-0914", "symmetric-option";
> >  symmetric-option = 0x1000000;
>
> > ...and did a reboot. Still the same output of "luxadm probe". Maybe I
> > have to play with the options.
>
> The VendorID must have 8 characters in it.  Most likely you need 5 spaces
> of padding after the "IBM" and then the 4 digit machine code.  Run format
> and get the inquiry results from one of the disks to determine what the
> Vendor ID and Product ID of the array is.  After putting that stuff in
> the scsi_vhci.conf file reboot with "stmsboot -u"

Patchcluster was missing...shame on me ;-) Now it's working perfectly
fine, without any extensions to scsi_vhci.conf. Many thanks to all.