Re: [storage-discuss] How to blink drive light? [SEC=UNCLASSIFIED]

2010-12-07 Thread Pasi Kärkkäinen
On Mon, Dec 06, 2010 at 12:40:51PM +0200, Cyril Plisko wrote:
> On Mon, Dec 6, 2010 at 11:28 AM, Wilkinson, Alex
>  wrote:
> >
> > OK, thanks. Is there any way to manually light up an LED ? From this thread:
> > http://www.mail-archive.com/[email protected]/msg30462.html I
> > supposedly i could use: "cfgadm -x locator c0::dsk/c0t6d0* - but only on 
> > SPARC.
> >
> > Is this possible on x86_64 on say an X4540 ?
> >
> >  #pfexec cfgadm -x locator c10::dsk/c10t0d0
> >  cfgadm: Hardware specific failure: unavailable
> 
> -x locator (as well as  -x led) features are provided by cfgadm_scsi(1M) 
> plugin.
> scsi_sata(1M) doesn't have them. So I'd imaging that on SATA based chassis 
> these
> features would not be available.
> 

If the chassis has SES then it should be possible, by using sg_ses or sdparm,
or HBA specific tools.

-- Pasi

___
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss


Re: [storage-discuss] How to blink drive light? [SEC=UNCLASSIFIED]

2010-12-06 Thread Cyril Plisko
On Mon, Dec 6, 2010 at 11:28 AM, Wilkinson, Alex
 wrote:
>
> OK, thanks. Is there any way to manually light up an LED ? From this thread:
> http://www.mail-archive.com/[email protected]/msg30462.html I
> supposedly i could use: "cfgadm -x locator c0::dsk/c0t6d0* - but only on 
> SPARC.
>
> Is this possible on x86_64 on say an X4540 ?
>
>  #pfexec cfgadm -x locator c10::dsk/c10t0d0
>  cfgadm: Hardware specific failure: unavailable

-x locator (as well as  -x led) features are provided by cfgadm_scsi(1M) plugin.
scsi_sata(1M) doesn't have them. So I'd imaging that on SATA based chassis these
features would not be available.

-- 
Regards,
        Cyril
___
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss


Re: [storage-discuss] How to blink drive light? [SEC=UNCLASSIFIED]

2010-12-06 Thread Wilkinson, Alex

0n Fri, Dec 03, 2010 at 10:15:08PM +1000, James C. McPherson wrote: 

>On  3/12/10 05:42 PM, Wilkinson, Alex wrote:
>>
>>  0n Fri, Dec 03, 2010 at 10:17:18AM +1000, James C. McPherson wrote:
>>
>>  >The distinguishing feature of the current J series JBODs (J4200,
>>  >J4400 et al) is that they support SES diagnostic pagecode 0xa,
>>  >Additional Element Status and set the Element Index Present (EIP)
>>  >bit to 1 in the pagecode response. Enclosures which do not support
>>  >this pagecode, or which do not have the Element Index Present (EIP)
>>  >bit set to 1 in the pagecode response are not with libses since
>>  >we cannot know which element in the enclosure the descriptor refers
>>  >to.
>>  >
>>  >If your non-Sun JBOD adheres to the above requirement, then it
>>  >really should "just work" with FMA.
>>
>> James, are you able to confirm whether the X4540 supports the 
aforementioned ?
>>
>> Is there any magic Solaris command to verify this stuff ? Any examples ?
>
>Hi Alex,
>yes, the X4540 does provide this support. You can see
>this yourself (with OpenSolaris/Solaris 11 Express/[fork])
>by running
>
># /usr/lib/fm/fmd/fmtopo -dV

OK, thanks. Is there any way to manually light up an LED ? From this thread:
http://www.mail-archive.com/[email protected]/msg30462.html I
supposedly i could use: "cfgadm -x locator c0::dsk/c0t6d0* - but only on SPARC.

Is this possible on x86_64 on say an X4540 ?

  #pfexec cfgadm -x locator c10::dsk/c10t0d0
  cfgadm: Hardware specific failure: unavailable

  -Alex

IMPORTANT: This email remains the property of the Department of Defence and is 
subject to the jurisdiction of section 70 of the Crimes Act 1914. If you have 
received this email in error, you are requested to contact the sender and 
delete the email.
___
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss


Re: [storage-discuss] How to blink drive light? [SEC=UNCLASSIFIED]

2010-12-03 Thread Saxon, Will
> -Original Message-
> From: [email protected] [mailto:storage-discuss-
> [email protected]] On Behalf Of Markus Kovero
> Sent: Friday, December 03, 2010 8:11 AM
> To: [email protected]; [email protected]
> Subject: Re: [storage-discuss] How to blink drive light? [SEC=UNCLASSIFIED]
> 
> 
> 
> > # /usr/lib/fm/fmd/fmtopo -dV
> > This will show you information such as this:
> 
> 
> ..
> 
> 
> Any known non-sun jbods that work with this?

Is Sun building their own product? Most of the big names source these from 
other vendors (LSI, Xyratex, etc.) so one of those may work. 

-Will
___
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss


Re: [storage-discuss] How to blink drive light? [SEC=UNCLASSIFIED]

2010-12-03 Thread James C. McPherson

On  3/12/10 11:11 PM, Markus Kovero wrote:




# /usr/lib/fm/fmd/fmtopo -dV
This will show you information such as this:



..


Any known non-sun jbods that work with this?


I have no idea, sorry. I don't have access to any.


James
--
Oracle
http://www.jmcp.homeunix.com/blog
___
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss


Re: [storage-discuss] How to blink drive light? [SEC=UNCLASSIFIED]

2010-12-03 Thread Markus Kovero


> # /usr/lib/fm/fmd/fmtopo -dV
> This will show you information such as this:


..


Any known non-sun jbods that work with this?


Yours
Markus Kovero
___
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss


Re: [storage-discuss] How to blink drive light? [SEC=UNCLASSIFIED]

2010-12-03 Thread James C. McPherson

On  3/12/10 05:42 PM, Wilkinson, Alex wrote:


 0n Fri, Dec 03, 2010 at 10:17:18AM +1000, James C. McPherson wrote:

 >The distinguishing feature of the current J series JBODs (J4200,
 >J4400 et al) is that they support SES diagnostic pagecode 0xa,
 >Additional Element Status and set the Element Index Present (EIP)
 >bit to 1 in the pagecode response. Enclosures which do not support
 >this pagecode, or which do not have the Element Index Present (EIP)
 >bit set to 1 in the pagecode response are not with libses since
 >we cannot know which element in the enclosure the descriptor refers
 >to.
 >
 >If your non-Sun JBOD adheres to the above requirement, then it
 >really should "just work" with FMA.

James, are you able to confirm whether the X4540 supports the aforementioned ?

Is there any magic Solaris command to verify this stuff ? Any examples ?


Hi Alex,
yes, the X4540 does provide this support. You can see
this yourself (with OpenSolaris/Solaris 11 Express/[fork])
by running

# /usr/lib/fm/fmd/fmtopo -dV


This will show you information such as this:


hc://:product-id=Sun-Fire-X4540:server-id=x4540-01:chassis-id=IDHERE:serial=serial:part=HITACHI-HUA7210SASUN1.0T-0833GZKXTE:revision=GKAOAC4A/chassis=0/bay=1/disk=0
  group: protocol   version: 1   stability: 
Private/Private
resource  fmri 
hc://:product-id=Sun-Fire-X4540:server-id=x4540-01:chassis-id=IDHERE:serial=serial:part=HITACHI-HUA7210SASUN1.0T-0833GZKXTE:revision=GKAOAC4A/chassis=0/bay=1/disk=0

label stringHD_ID_1
FRU   fmri 
hc://:product-id=Sun-Fire-X4540:server-id=x4540-01:chassis-id=IDHERE:serial=serial:part=HITACHI-HUA7210SASUN1.0T-0833GZKXTE:revision=GKAOAC4A/chassis=0/bay=1/disk=0
ASRU  fmri 
dev:///:devid=id1,s...@n5000cca216f82cf2//p...@0,0/pci10de,3...@a/pci1000,1...@0/s...@1,0
  group: authority  version: 1   stability: 
Private/Private

product-idstringSun-Fire-X4540
chassis-idstringIDHERE
server-id stringx4540-01
  group: storageversion: 1   stability: 
Private/Private

logical-disk  stringc7t1d0
manufacturer  stringHITACHI
model stringHUA7210SASUN1.0T 0833GZKXTE
serial-number stringGTE002PAKZKXTE
firmware-revision stringGKAOAC4A
capacity-in-bytes string1000204886016
  group: io version: 1   stability: 
Private/Private

devfs-pathstring/p...@0,0/pci10de,3...@a/pci1000,1...@0/s...@1,0
devid stringid1,s...@n5000cca216f82cf2
phys-path string[]  [ 
"/p...@0,0/pci10de,3...@a/pci1000,1...@0/s...@1,0" ]






James C. McPherson
--
Oracle
http://www.jmcp.homeunix.com/blog
___
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss


Re: [storage-discuss] How to blink drive light? [SEC=UNCLASSIFIED]

2010-12-02 Thread Wilkinson, Alex

0n Fri, Dec 03, 2010 at 10:17:18AM +1000, James C. McPherson wrote: 

>The distinguishing feature of the current J series JBODs (J4200,
>J4400 et al) is that they support SES diagnostic pagecode 0xa,
>Additional Element Status and set the Element Index Present (EIP)
>bit to 1 in the pagecode response. Enclosures which do not support
>this pagecode, or which do not have the Element Index Present (EIP)
>bit set to 1 in the pagecode response are not with libses since
>we cannot know which element in the enclosure the descriptor refers
>to.
>
>If your non-Sun JBOD adheres to the above requirement, then it
>really should "just work" with FMA.

James, are you able to confirm whether the X4540 supports the aforementioned ?

Is there any magic Solaris command to verify this stuff ? Any examples ?

   -Alex

IMPORTANT: This email remains the property of the Department of Defence and is 
subject to the jurisdiction of section 70 of the Crimes Act 1914. If you have 
received this email in error, you are requested to contact the sender and 
delete the email.
___
storage-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/storage-discuss