On Tue, 26 Feb 2008 15:16:35 -0800
Hyon Kim <[EMAIL PROTECTED]> wrote:
...
> A different LUN number can be assigned through LUN mapping for the
> same physical LU when mulitple target ports
> exist. The mpathadm could show LUN number at path level but we had
> left up to transport layer utilities like fcinfo for reporting
> it. There is no such utility for mpt but as far as LUN number is
> concerned, you can check 'prtconf -v' output and find lun prop from
> pathinfo nodes of the scsi_vhci device.
Actually, no - you can't, not with *currently available*
command line utilities.
Here's an example:
:name scsi_vhci
disk (fabric, 8c00000034)
:client-guid 500000e0130c3170
:compatible (8c0000004bTBL)
| scsiclass,00.vFUJITSU.pMAY2073RCSUN72G.r0401 |
| scsiclass,00.vFUJITSU.pMAY2073RCSUN72G |
| scsiclass,00 |
| scsiclass |
:inquiry-device-type 0
:inquiry-vendor-id FUJITSU
:inquiry-product-id MAY2073RCSUN72G
:inquiry-revision-id 0401
:devid id1,[EMAIL PROTECTED]
:ddi-kernel-ioctl
:ddi-failfast-supported
:pm-hardware-state needs-suspend-resume
:pm-components (8c0000003eTBL)
| NAME=spindle-motor |
| 0=off |
| 1=on |
:ddi-no-autodetach 0x1
:devfs-path /scsi_vhci/[EMAIL PROTECTED]
:driver-name sd
:binding-name scsiclass,00
:bus-addr g500000e0130c3170
:instance 0
:_class fabric
:name disk
I can, of course, jump into mdb -k and find this info using
"::prtconf -v" :
30001007aa8 scsiclass,00, instance #0
Driver properties at 3000100ba98:
name='ddi-no-autodetach' type=int items=1
value=00000001
name='pm-components' type=string items=3
value='NAME=spindle-motor' + '0=off' + '1=on'
name='pm-hardware-state' type=string items=1
value='needs-suspend-resume'
name='ddi-failfast-supported' type=any items=0
name='ddi-kernel-ioctl' type=any items=0
Hardware properties at 3000100bb60:
name='devid' type=string items=1
value='id1,[EMAIL PROTECTED]'
name='inquiry-revision-id' type=string items=1
value='0401'
name='inquiry-product-id' type=string items=1
value='MAY2073RCSUN72G'
name='inquiry-vendor-id' type=string items=1
value='FUJITSU'
name='inquiry-device-type' type=int items=1
value=00000000
name='compatible' type=string items=4
value='scsiclass,00.vFUJITSU.pMAY2073RCSUN72G.r0401'
+ 'scsiclass,00.vFUJITSU.pMAY2073RCSUN72G' + 'scsiclass,00' +
'scsiclass' name='client-guid' type=string items=1
value='500000e0130c3170'
Client multipath info at: 0x30001002180
pciex1000,58#0, state=online
name='wwn' type=string items=1
value='500000e0130c3170'
name='target' type=int32 items=1
value=00000000
name='lun' type=int32 items=1
value=00000000
name='compatible' type=string_array items=4
value='scsiclass,00.vFUJITSU.pMAY2073RCSUN72G.r0401'
+ 'scsiclass,00.vFUJITSU.pMAY2073RCSUN72G' + 'scsiclass,00' +
'scsiclass' name='target-port' type=string items=1
value='500000e0130c3172'
name='path-class' type=string items=1
value='primary'
But that doesn't help Robert much, or anybody else who wants
to be able to get the info without having to learn any mdb-fu.
It shouldn't be too hard to hack up a utility to retrieve
this info though. (note that I'm not committing to do so!)
cheers,
James C. McPherson
--
Senior Kernel Software Engineer, Solaris
Sun Microsystems
http://blogs.sun.com/jmcp http://www.jmcp.homeunix.com/blog
_______________________________________________
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss
