<font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2"><div><span style="font-size: small;">Hi!</span></div><div><span style="font-size: small;"><br></span></div><div><span style="font-size: small;">I've been successfully implementing fibre channel multipathing, but I wonder about some things in luxadm.</span></div><div><span style="font-size: small;"><br></span></div><div><span style="font-size: small;">Here is before I connected the second fibre channel path:</span></div><div><span style="font-size: small;"><br></span></div><div><div><font size="2">root@node2:~# mpathadm list LU</font></div><div><font size="2"> /dev/rdsk/c1t600144F0CD16CB00000050CC693A0001d0s2</font></div><div><font size="2"> Total Path Count: 1</font></div><div><font size="2"> Operational Path Count: 1</font></div><div><font size="2"> /dev/rdsk/c1t600144F0CD16CB00000050C61EDB0001d0s2</font></div><div><font size="2"> Total Path Count: 1</font></div><div><font size="2"> Operational Path Count: 1</font></div><div><font size="2"> /dev/rdsk/c1t600144F0CD16CB00000050D08EB50002d0s2</font></div><div><font size="2"> Total Path Count: 1</font></div><div><font size="2"> Operational Path Count: 1</font></div><div><font size="2"> /dev/rdsk/c1t600144F0CD16CB00000050D08E9D0001d0s2</font></div><div><font size="2"> Total Path Count: 1</font></div><div><font size="2"> Operational Path Count: 1</font></div><div><font size="2"><br></font></div><div><font size="2">And here is after I connected the second path:</font></div><div><font size="2"><br></font></div><div><font size="2">root@node2:~# mpathadm list LU</font></div><div><font size="2"> /dev/rdsk/c1t600144F0CD16CB00000050CC693A0001d0s2</font></div><div><font size="2"> Total Path Count: 2</font></div><div><font size="2"> Operational Path Count: 2</font></div><div><font size="2"> /dev/rdsk/c1t600144F0CD16CB00000050C61EDB0001d0s2</font></div><div><font size="2"> Total Path Count: 2</font></div><div><font size="2"> Operational Path Count: 2</font></div><div><font size="2"> /dev/rdsk/c1t600144F0CD16CB00000050D08EB50002d0s2</font></div><div><font size="2"> Total Path Count: 2</font></div><div><font size="2"> Operational Path Count: 2</font></div><div><font size="2"> /dev/rdsk/c1t600144F0CD16CB00000050D08E9D0001d0s2</font></div><div><font size="2"> Total Path Count: 2</font></div><div><font size="2"> Operational Path Count: 2</font></div><div><font size="2"><br></font></div><div><font size="2">As you see, the paths are dubbled in the second case. And here under you can see the disks after format:</font></div><div><font size="2"> </font></div><div><span style="font-size: small;">root@node2:~# format</span></div><div><font size="2">Searching for disks...done</font></div><div><font size="2"><br></font></div><div><font size="2"><br></font></div><div><font size="2">AVAILABLE DISK SELECTIONS:</font></div><div><font size="2"> 0. c1t600144F0CD16CB00000050C61EDB0001d0 <OI-COMSTAR-1.0-10.00GB></font></div><div><font size="2"> /scsi_vhci/disk@g600144f0cd16cb00000050c61edb0001</font></div><div><font size="2"> 1. c1t600144F0CD16CB00000050CC693A0001d0 <OI-COMSTAR-1.0-10.00GB></font></div><div><font size="2"> /scsi_vhci/disk@g600144f0cd16cb00000050cc693a0001</font></div><div><font size="2"> 2. c1t600144F0CD16CB00000050D08E9D0001d0 <OI-COMSTAR-1.0 cyl 1955 alt 2 hd 255 sec 63></font></div><div><font size="2"> /scsi_vhci/disk@g600144f0cd16cb00000050d08e9d0001</font></div><div><font size="2"> 3. c1t600144F0CD16CB00000050D08EB50002d0 <OI-COMSTAR-1.0-50.00GB></font></div><div><font size="2"> /scsi_vhci/disk@g600144f0cd16cb00000050d08eb50002</font></div><div><font size="2">Specify disk (enter its number): 1</font></div><div><font size="2"><br></font></div><div><font size="2">And if I run:</font></div><div><font size="2"><br></font></div><div><font size="2"><div>root@node2:~# cfgadm -al -o show_SCSI_LUN</div><div>Ap_Id Type Receptacle Occupant Condition</div><div>c3 fc-fabric connected configured unknown</div><div>c3::2100001b329dbfc6,0 disk connected configured unknown</div><div>c3::2100001b329dbfc6,1 disk connected configured unknown</div><div>c3::2100001b329dbfc6,2 disk connected configured unknown</div><div>c3::2100001b329dbfc6,3 disk connected configured unknown</div><div>c3::2101001b32bdbfc6,0 disk connected configured unknown</div><div>c3::2101001b32bdbfc6,1 disk connected configured unknown</div><div>c3::2101001b32bdbfc6,2 disk connected configured unknown</div><div>c3::2101001b32bdbfc6,3 disk connected configured unknown</div><div>root@node2:~# </div><div><br></div><div>I got all the LUN's nicely...</div></font></div><div><font size="2"><br></font></div><div><font size="2">But if I run:</font></div><div><font size="2"><br></font></div><div><font size="2"><div>root@node2:~# luxadm -v probe</div><div>terminate called after throwing an instance of 'MoreDataException'</div><div>Abort (core dumped)</div><div>root@node2:~# </div><div><br></div><div>And if I run:</div><div><br></div><div><div>root@node2:~# luxadm disp /dev/rdsk/c1t600144F0CD16CB00000050C61EDB0001d0s2</div><div>terminate called after throwing an instance of 'MoreDataException'</div><div>Abort (core dumped)</div><div>root@node2:~#</div></div><div><br></div><div>Doesn'matter which one of the devices I try to display, they all give the same result.</div><div><br></div><div>Could it be that the vendor and product id's are unknown? And not listed in "mpathadm show mpath-support libmpscsi_vhci.so" ? SAN controller is a OI box with comstar, so it presents it self as vendor id OI, and product id comstar.</div><div><br></div></font><font size="2"><div><br></div><div>Any ideas...?</div><div><br></div><div>Rgrds Johan</div></font></div><div style="font-size: small;"><br></div></div><div></div></font>