Re: [storage-discuss] How to blink drive light?
It is based on solaris, but many of the drivers and apps are quite different, and it supports a generic sas jbod's ses functions - Supermicro in my case (which is what controls the led's), when OpenSolaris does not. What would it take to make these generic SAS JBODs work with SES? I use supermicro myself, and I guess there might be a chance for a bounty on this... Vennlige hilsener / Best regards roy -- Roy Sigurd Karlsbakk (+47) 97542685 r...@karlsbakk.net http://blogg.karlsbakk.net/ -- I all pedagogikk er det essensielt at pensum presenteres intelligibelt. Det er et elementært imperativ for alle pedagoger å unngå eksessiv anvendelse av idiomer med fremmed opprinnelse. I de fleste tilfeller eksisterer adekvate og relevante synonymer på norsk. ___ storage-discuss mailing list storage-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/storage-discuss
Re: [storage-discuss] How to blink drive light?
It is based on solaris, but many of the drivers and apps are quite different, and it supports a generic sas jbod's ses functions - Supermicro in my case (which is what controls the led's), when OpenSolaris does not. -- This message posted from opensolaris.org ___ storage-discuss mailing list storage-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/storage-discuss
Re: [storage-discuss] How to blink drive light?
On Tue, Jan 25, 2011 at 05:01:05PM -0800, Mark Bennett wrote: My conclusion was it isn't fully implemented in opensolaris. I can use the disk locate features in the Sun Unified Storage OS, which is Solaris based but with better drivers if I run that on my Supermicro system, but not when I run opensolaris. Afaik Sun Unified Storage (aka OpenStorage) is Opensolaris based appliance. Pasi This is a partial output from sestopo of the sas backplane Node Type: 1 nvlist version: 0 scsi-inquiry-vendor = LSILOGIC scsi-inquiry-product = SASX28 A.0 scsi-inquiry-revision =9 Node Type: 2 nvlist version: 0 ses-enclosure-id = 0x0 ses-enclosure-service-proc-id = 0x0 ses-enclosure-service-proc-count = 0x0 ses-logical-id = (embedded nvlist) nvlist version: 0 naa-id-integer = 0x50030480003bbf7f naa-id-type = 0x5 naa-company-id = 0x3048 naa-vendor-specific-a = 0x3bbf7f (end ses-logical-id) ses-vendor-id = LSILOGIC ses-product-id = SASX28 A.0 ses-product-revision = 9 ses-element-index = 0x12 ses-element-type = 0xe ses-class-description = Enclosure ses-status-code = 0x1 ses-swapped = 0 ses-disabled = 0 ses-failure-predicted = 0 ses-identify = 0 ses-warning = 1 ses-failed = 0 ses-power-cycle-delay = 0x0 ses-warning-indicator-requested = 0 ses-failure-indicator-requested = 0 ses-power-cycle-duration = 0x0 ses-description = BOX 001 ses-microcode-dl-status = 0x0 ses-microcode-dl-addl-status = 0x0 ses-microcode-maximum-size = 0x4 ses-microcode-buffer-id = 0xff ses-microcode-buffer-offset = 0x0 libses-element-type-name = ENCLOSURE libses-chassis-serial = 50030480003bbf7f libses-internal = 1 Node Type: 4 Element Type: ARRAY_DEVICE nvlist version: 0 ses-element-index = 0x0 ses-element-type = 0x17 ses-class-description = Array Device ses-status-code = 0x0 ses-swapped = 0 ses-disabled = 0 ses-failure-predicted = 0 ses-remap-rebuild-abort = 0 ses-remap-rebuild = 0 ses-in-failed-array = 0 ses-in-critical-array = 0 ses-consistency-check = 0 ses-hot-spare = 0 ses-reserved-device = 0 ses-ok = 0 ses-reported-via = 0 ses-identify = 0 ses-ready-to-remove = 0 ses-ready-to-insert = 0 ses-enclosure-bypassed-b = 0 ses-enclosure-bypassed-a = 0 ses-do-not-remove = 0 ses-app-client-bypassed-a = 0 ses-device-bypassed-b = 0 ses-device-bypassed-a = 0 ses-bypassed-b = 0 ses-bypassed-a = 0 ses-off = 0 ses-fault-requested = 0 ses-fault-sensed = 0 ses-app-client-bypassed-b = 0 ses-description = Array Device libses-element-type-name = ARRAY_DEVICE Node Type: 8 Element Type: ARRAY_DEVICE nvlist version: 0 ses-element-index = 0x1 ses-element-class-index = 0x0 ses-element-type = 0x17 ses-status-code = 0x1 ses-swapped = 0 ses-disabled = 0 ses-failure-predicted = 0 ses-remap-rebuild-abort = 0 ses-remap-rebuild = 0 ses-in-failed-array = 0 ses-in-critical-array = 0 ses-consistency-check = 0 ses-hot-spare = 0 ses-reserved-device = 0 ses-ok = 0 ses-reported-via = 0 ses-identify = 0 ses-ready-to-remove = 0 ses-ready-to-insert = 0 ses-enclosure-bypassed-b = 0 ses-enclosure-bypassed-a = 0 ses-do-not-remove = 0 ses-app-client-bypassed-a = 0 ses-device-bypassed-b = 0 ses-device-bypassed-a = 0 ses-bypassed-b = 0 ses-bypassed-a = 0 ses-off = 0 ses-fault-requested = 0 ses-fault-sensed = 0 ses-app-client-bypassed-b = 0 ses-description = 000 ses-sas-not-all-phys = 1 ses-bay-number = 0x0 ses-sas-phys = (array of embedded nvlists) (start ses-sas-phys[0]) nvlist version: 0 ses-sas-device-type = 0x1 ses-sas-smp-initiator-port = 0 ses-sas-stp-initiator-port = 0 ses-sas-ssp-initiator-port = 0 ses-sas-sata-device = 1 ses-sas-smp-target-port = 0 ses-sas-stp-target-port = 0 ses-sas-ssp-target-port = 0 ses-sas-attached-address = 0x50030480003bbf7f ses-sas-address = 0x50030480003bbf48 ses-sas-phy-identifier = 0x8 (end ses-sas-phys[0]) libses-element-type-name = ARRAY_DEVICE -- This message posted from opensolaris.org ___ storage-discuss mailing list storage-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/storage-discuss
Re: [storage-discuss] How to blink drive light?
My conclusion was it isn't fully implemented in opensolaris. I can use the disk locate features in the Sun Unified Storage OS, which is Solaris based but with better drivers if I run that on my Supermicro system, but not when I run opensolaris. This is a partial output from sestopo of the sas backplane Node Type: 1 nvlist version: 0 scsi-inquiry-vendor = LSILOGIC scsi-inquiry-product = SASX28 A.0 scsi-inquiry-revision =9 Node Type: 2 nvlist version: 0 ses-enclosure-id = 0x0 ses-enclosure-service-proc-id = 0x0 ses-enclosure-service-proc-count = 0x0 ses-logical-id = (embedded nvlist) nvlist version: 0 naa-id-integer = 0x50030480003bbf7f naa-id-type = 0x5 naa-company-id = 0x3048 naa-vendor-specific-a = 0x3bbf7f (end ses-logical-id) ses-vendor-id = LSILOGIC ses-product-id = SASX28 A.0 ses-product-revision = 9 ses-element-index = 0x12 ses-element-type = 0xe ses-class-description = Enclosure ses-status-code = 0x1 ses-swapped = 0 ses-disabled = 0 ses-failure-predicted = 0 ses-identify = 0 ses-warning = 1 ses-failed = 0 ses-power-cycle-delay = 0x0 ses-warning-indicator-requested = 0 ses-failure-indicator-requested = 0 ses-power-cycle-duration = 0x0 ses-description = BOX 001 ses-microcode-dl-status = 0x0 ses-microcode-dl-addl-status = 0x0 ses-microcode-maximum-size = 0x4 ses-microcode-buffer-id = 0xff ses-microcode-buffer-offset = 0x0 libses-element-type-name = ENCLOSURE libses-chassis-serial = 50030480003bbf7f libses-internal = 1 Node Type: 4 Element Type: ARRAY_DEVICE nvlist version: 0 ses-element-index = 0x0 ses-element-type = 0x17 ses-class-description = Array Device ses-status-code = 0x0 ses-swapped = 0 ses-disabled = 0 ses-failure-predicted = 0 ses-remap-rebuild-abort = 0 ses-remap-rebuild = 0 ses-in-failed-array = 0 ses-in-critical-array = 0 ses-consistency-check = 0 ses-hot-spare = 0 ses-reserved-device = 0 ses-ok = 0 ses-reported-via = 0 ses-identify = 0 ses-ready-to-remove = 0 ses-ready-to-insert = 0 ses-enclosure-bypassed-b = 0 ses-enclosure-bypassed-a = 0 ses-do-not-remove = 0 ses-app-client-bypassed-a = 0 ses-device-bypassed-b = 0 ses-device-bypassed-a = 0 ses-bypassed-b = 0 ses-bypassed-a = 0 ses-off = 0 ses-fault-requested = 0 ses-fault-sensed = 0 ses-app-client-bypassed-b = 0 ses-description = Array Device libses-element-type-name = ARRAY_DEVICE Node Type: 8 Element Type: ARRAY_DEVICE nvlist version: 0 ses-element-index = 0x1 ses-element-class-index = 0x0 ses-element-type = 0x17 ses-status-code = 0x1 ses-swapped = 0 ses-disabled = 0 ses-failure-predicted = 0 ses-remap-rebuild-abort = 0 ses-remap-rebuild = 0 ses-in-failed-array = 0 ses-in-critical-array = 0 ses-consistency-check = 0 ses-hot-spare = 0 ses-reserved-device = 0 ses-ok = 0 ses-reported-via = 0 ses-identify = 0 ses-ready-to-remove = 0 ses-ready-to-insert = 0 ses-enclosure-bypassed-b = 0 ses-enclosure-bypassed-a = 0 ses-do-not-remove = 0 ses-app-client-bypassed-a = 0 ses-device-bypassed-b = 0 ses-device-bypassed-a = 0 ses-bypassed-b = 0 ses-bypassed-a = 0 ses-off = 0 ses-fault-requested = 0 ses-fault-sensed = 0 ses-app-client-bypassed-b = 0 ses-description = 000 ses-sas-not-all-phys = 1 ses-bay-number = 0x0 ses-sas-phys = (array of embedded nvlists) (start ses-sas-phys[0]) nvlist version: 0 ses-sas-device-type = 0x1 ses-sas-smp-initiator-port = 0 ses-sas-stp-initiator-port = 0 ses-sas-ssp-initiator-port = 0 ses-sas-sata-device = 1 ses-sas-smp-target-port = 0 ses-sas-stp-target-port = 0 ses-sas-ssp-target-port = 0 ses-sas-attached-address = 0x50030480003bbf7f ses-sas-address = 0x50030480003bbf48 ses-sas-phy-identifier = 0x8 (end ses-sas-phys[0]) libses-element-type-name = ARRAY_DEVICE -- This message posted from opensolaris.org ___ storage-discuss mailing list storage-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/storage-discuss
Re: [storage-discuss] How to blink drive light?
On Thu, Dec 30, 2010 at 10:32:33AM -0800, mururoa wrote: You dont need any tool to make a disk led blink. Just do dd if=/dev/dsk/c5t0d0s0 of=/dev/null and you should be able to locate the disk c5t0d0. I think we were discussing how to blink the separate failure LED.. -- Pasi ___ storage-discuss mailing list storage-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/storage-discuss
Re: [storage-discuss] How to blink drive light?
You dont need any tool to make a disk led blink. Just do dd if=/dev/dsk/c5t0d0s0 of=/dev/null and you should be able to locate the disk c5t0d0. -- This message posted from opensolaris.org ___ storage-discuss mailing list storage-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/storage-discuss
Re: [storage-discuss] How to blink drive light? [SEC=UNCLASSIFIED]
On Mon, Dec 06, 2010 at 12:40:51PM +0200, Cyril Plisko wrote: On Mon, Dec 6, 2010 at 11:28 AM, Wilkinson, Alex alex.wilkin...@dsto.defence.gov.au wrote: OK, thanks. Is there any way to manually light up an LED ? From this thread: http://www.mail-archive.com/zfs-disc...@opensolaris.org/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 storage-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/storage-discuss
Re: [storage-discuss] How to blink drive light? [SEC=UNCLASSIFIED]
On Mon, Dec 6, 2010 at 11:28 AM, Wilkinson, Alex alex.wilkin...@dsto.defence.gov.au wrote: OK, thanks. Is there any way to manually light up an LED ? From this thread: http://www.mail-archive.com/zfs-disc...@opensolaris.org/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 storage-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/storage-discuss
Re: [storage-discuss] How to blink drive light? [SEC=UNCLASSIFIED]
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 storage-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/storage-discuss
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? Yours Markus Kovero ___ storage-discuss mailing list storage-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/storage-discuss
Re: [storage-discuss] How to blink drive light? [SEC=UNCLASSIFIED]
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 storage-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/storage-discuss
Re: [storage-discuss] How to blink drive light? [SEC=UNCLASSIFIED]
-Original Message- From: storage-discuss-boun...@opensolaris.org [mailto:storage-discuss- boun...@opensolaris.org] On Behalf Of Markus Kovero Sent: Friday, December 03, 2010 8:11 AM To: j...@opensolaris.org; storage-discuss@opensolaris.org 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 storage-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/storage-discuss
Re: [storage-discuss] How to blink drive light?
On Wed, Dec 01, 2010 at 09:53:32AM +, Markus Kovero wrote: The current backplane does not have SES. However, I am getting a new one. The brochure says that it supports SES2. Does SES-2 support a mechanism to blink LEDs? In theory, its whole different story if your controller knows how to control them, or if you are able to control them from Solaris. eg. Dell MD1000 is SES enabled JBOD, but if its connected to SAS 5e/6e basic sas-controller which does not control leds at all, you can blink leds with proprietary software, but you don't have any information on which disk is in which slot.. (enclosure does not share it's NAA identifiers from disks) Yep, if the enclosure provides all the required information through SES, then it's possible to to blink/lid the LEDs etc from the OS. I think FMA does this automatically in the case of disk failure if the enclosure is properly using/providing SES? -- Pasi ___ storage-discuss mailing list storage-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/storage-discuss
Re: [storage-discuss] How to blink drive light?
Yep, if the enclosure provides all the required information through SES, then it's possible to to blink/lid the LEDs etc from the OS. I think FMA does this automatically in the case of disk failure if the enclosure is properly using/providing SES? -- Pasi Never seen FMA doing this with non-sun JBODs, even with SES compliant ones. Would be really nice though. Yours Markus Kovero ___ storage-discuss mailing list storage-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/storage-discuss
Re: [storage-discuss] How to blink drive light?
On Thu, Dec 02, 2010 at 03:49:40PM +0200, Pasi Kärkkäinen wrote: On Wed, Dec 01, 2010 at 09:53:32AM +, Markus Kovero wrote: The current backplane does not have SES. However, I am getting a new one. The brochure says that it supports SES2. Does SES-2 support a mechanism to blink LEDs? In theory, its whole different story if your controller knows how to control them, or if you are able to control them from Solaris. eg. Dell MD1000 is SES enabled JBOD, but if its connected to SAS 5e/6e basic sas-controller which does not control leds at all, you can blink leds with proprietary software, but you don't have any information on which disk is in which slot.. (enclosure does not share it's NAA identifiers from disks) Yep, if the enclosure provides all the required information through SES, then it's possible to to blink/lid the LEDs etc from the OS. I think FMA does this automatically in the case of disk failure if the enclosure is properly using/providing SES? Just to write some kind of summary: - For an automatic blink-led-on-disk-failure the SES management processor needs to provide disk identification information, so the actual disk error can be mapped to specific SES slot. - And when that works tools like FMA can automatically blink the LED through SES when they know disk id xyz is in slot 3. You can also manually control the LEDs through the SES: - By using an utility provided by the HBA vendor. - Or by using generic tools like sdparm, which afaik allow you to control LEDs through SES. -- Pasi ___ storage-discuss mailing list storage-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/storage-discuss
Re: [storage-discuss] How to blink drive light?
On Thu, Dec 02, 2010 at 06:39:28PM +0200, Pasi Kärkkäinen wrote: On Thu, Dec 02, 2010 at 03:49:40PM +0200, Pasi Kärkkäinen wrote: On Wed, Dec 01, 2010 at 09:53:32AM +, Markus Kovero wrote: The current backplane does not have SES. However, I am getting a new one. The brochure says that it supports SES2. Does SES-2 support a mechanism to blink LEDs? In theory, its whole different story if your controller knows how to control them, or if you are able to control them from Solaris. eg. Dell MD1000 is SES enabled JBOD, but if its connected to SAS 5e/6e basic sas-controller which does not control leds at all, you can blink leds with proprietary software, but you don't have any information on which disk is in which slot.. (enclosure does not share it's NAA identifiers from disks) Yep, if the enclosure provides all the required information through SES, then it's possible to to blink/lid the LEDs etc from the OS. I think FMA does this automatically in the case of disk failure if the enclosure is properly using/providing SES? Just to write some kind of summary: - For an automatic blink-led-on-disk-failure the SES management processor needs to provide disk identification information, so the actual disk error can be mapped to specific SES slot. - And when that works tools like FMA can automatically blink the LED through SES when they know disk id xyz is in slot 3. You can also manually control the LEDs through the SES: - By using an utility provided by the HBA vendor. - Or by using generic tools like sdparm, which afaik allow you to control LEDs through SES. .. And at least on Linux you can use sg_ses to control the LEDs on the enclosure. -- Pasi ___ storage-discuss mailing list storage-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/storage-discuss
Re: [storage-discuss] How to blink drive light?
On 2/12/10 11:51 PM, Markus Kovero wrote: Yep, if the enclosure provides all the required information through SES, then it's possible to to blink/lid the LEDs etc from the OS. I think FMA does this automatically in the case of disk failure if the enclosure is properly using/providing SES? -- Pasi Never seen FMA doing this with non-sun JBODs, even with SES compliant ones. Would be really nice though. 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 C. McPherson -- Oracle http://www.jmcp.homeunix.com/blog ___ storage-discuss mailing list storage-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/storage-discuss
Re: [storage-discuss] How to blink drive light? [SEC=UNCLASSIFIED]
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 storage-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/storage-discuss
Re: [storage-discuss] How to blink drive light?
The current backplane does not have SES. However, I am getting a new one. The brochure says that it supports SES2. Does SES-2 support a mechanism to blink LEDs? In theory, its whole different story if your controller knows how to control them, or if you are able to control them from Solaris. eg. Dell MD1000 is SES enabled JBOD, but if its connected to SAS 5e/6e basic sas-controller which does not control leds at all, you can blink leds with proprietary software, but you don't have any information on which disk is in which slot.. (enclosure does not share it's NAA identifiers from disks) Yours Markus Kovero ___ storage-discuss mailing list storage-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/storage-discuss
Re: [storage-discuss] How to blink drive light?
Pasi, Thank you for your help. The current backplane does not have SES. However, I am getting a new one. The brochure says that it supports SES2. Does SES-2 support a mechanism to blink LEDs? Regards, Peter -- This message posted from opensolaris.org ___ storage-discuss mailing list storage-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/storage-discuss
Re: [storage-discuss] How to blink drive light?
On Sun, Nov 21, 2010 at 12:00:15PM -0800, Peter Taps wrote: Thank you for your help, James. Can you please give more specificity? Is this feature not implemented in OpenSolaris IPMI implementation or is it at the BMC driver level? Is there any third-party tool that I can used to blink the LED? Thank you once again for your help. Does your disk backplane have SES (SCSI Enclosure Services) ? -- Pasi ___ storage-discuss mailing list storage-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/storage-discuss
Re: [storage-discuss] How to blink drive light?
Thank you for your help, James. Can you please give more specificity? Is this feature not implemented in OpenSolaris IPMI implementation or is it at the BMC driver level? Is there any third-party tool that I can used to blink the LED? Thank you once again for your help. Regards, Peter -- This message posted from opensolaris.org ___ storage-discuss mailing list storage-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/storage-discuss
[storage-discuss] How to blink drive light?
Folks, I am running OpenIndiana. The hardware supports SGPIO. It also supports IPMI but that requires using Oracle's BMC driver and is off-limit to us. I am looking for a way to blink lights on the specified disk. Is there any tool I can download to do this? Thank you in advance for your help. Regards, Peter -- This message posted from opensolaris.org ___ storage-discuss mailing list storage-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/storage-discuss
