Hi Andrew,
I updated the package again. Could you please try it again? :)
http://www.opensolaris.org/os/community/device_drivers/projects/serveraid/SUNWips.tar.gz
This time I add EVPD page83 support. I put vendorID+product ID
+ ips instance# + volumeID together to generate the GUID for
IBM serveRAID volumes. Hope it works for you this time. :)
Below is the output from my test server.
==========================================
bash-3.2# prtconf -v /dev/dsk/c4t1d0p0
sd, instance #4
---snip---
Hardware properties:
name='devid' type=string items=1
value='id1,[EMAIL PROTECTED]'
name='inquiry-revision-id' type=string items=1
value='V1.0'
name='inquiry-product-id' type=string items=1
value='ServeRAID Volum'
name='inquiry-vendor-id' type=string items=1
value='IBM'
name='inquiry-device-type' type=int items=1
value=00000000
---snip---
bash-3.2# prtconf -v /dev/dsk/c4t0d0p0
sd, instance #3
---snip---
Hardware properties:
name='devid' type=string items=1
value='id1,[EMAIL PROTECTED]'
name='inquiry-revision-id' type=string items=1
value='V1.0'
name='inquiry-product-id' type=string items=1
value='ServeRAID Volum'
name='inquiry-vendor-id' type=string items=1
value='IBM'
name='inquiry-device-type' type=int items=1
---snip---
==========================================
Thanks
Javen
Andrew Deason wrote:
>On Thu, 03 Jan 2008 03:26:19 +0000
>Javen Wu <[EMAIL PROTECTED]> wrote:
>
>
>
>>Hi Andrew,
>>
>>It's weird, I am seeing different devid for different volumes on my
>>system with my new driver.
>>Could you help send the output of prtconf -v /dev/dsk/cxtydzp0?
>>cxtydz means your IBM serveRAID volume.
>>
>>
>
>Here's the same sections as what you gave; if anything else is needed,
>just let me know. (And thanks for the GUID explanation.)
>
># prtconf -v /dev/dsk/c3t0d0p0
>sd, instance #0
>[snip]
> Hardware properties:
> name='devid' type=string items=1
> value='id1,[EMAIL PROTECTED]'
> name='inquiry-revision-id' type=string items=1
> value='V1.0'
> name='inquiry-product-id' type=string items=1
> value='ServeRAID Vol0'
> name='inquiry-device-type' type=int items=1
> value=00000000
>[snip]
>
># prtconf -v /dev/dsk/c3t1d0p0
>sd, instance #1
>[snip]
> Hardware properties:
> name='devid' type=string items=1
> value='id1,[EMAIL PROTECTED]'
> name='inquiry-revision-id' type=string items=1
> value='V1.0'
> name='inquiry-product-id' type=string items=1
> value='ServeRAID Vol1'
> name='inquiry-device-type' type=int items=1
> value=00000000
>[snip]
>
>
>
>>BTW, can I ask why u want to use SVM on top of RAID volume? Since you
>>have hardware
>>RAID, why you need SVM software RAID?
>>
>>
>
>Yes, I know this isn't a common usage :). Well, for one thing, it's
>impossible as of right now to manipulate the raid configuration at all
>from Solaris, and SVM would give me some flexibility. And using SVM
>makes LiveUpgrade possible while still RAID1'ing the only drives I have
>in the system.
>
>I realize I don't need the RAID controller at all for this, but it's in
>the machine now, and I don't have physical access for awhile. I'd be
>fine with bypassing the RAID controller altogether, but from the
>reading I've done, this appears to not be possible (at least, without
>taking out the card or something). And hey, it lets me troubleshoot a
>driver.
>
>
>
>>Anyway, we should make ips driver better. Thanks for your information
>>and testing.
>>
>>
>
>Thanks for your updates! And I'd be happy to test more versions of the
>driver as you wish.
>
>
>
_______________________________________________
driver-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/driver-discuss
