From: keith.busch@intel.com (Keith Busch)
Subject: NVMe U.2 Concurrent Maintenance - Identify LED
Date: Fri, 14 Oct 2016 11:57:22 -0400 [thread overview]
Message-ID: <20161014155722.GA19383@localhost.localdomain> (raw)
In-Reply-To: <OF6508F29F.5646743D-ON8625804C.0051E01E-8625804C.00552F15@notes.na.collabserv.com>
On Fri, Oct 14, 2016@10:30:26AM -0500, Murali N Iyer wrote:
> We were wondering how NVMe SSDs planned to be serviced in the field
> compared to the SATA/SAS. As far as I know typically there are two LEDs
> standard 2.5" (U.2) devices provide. One is a activity LED and the other is
> Identification/Fault LED. Activity LED is controlled by the device itself
> and no issues there. As far as Identify LED is concern it is typically
> controller by the device enclosure or the system enclosure services. As we
> know in case of SCSI/SAS there is a SCSI Enclosure Service (SES) that
> provides interface to control the ID/Fault LED.
>
> I see some systems providing access to the NVMe SSD ID/Fault LED via out of
> band service provided by the service processor like BMC. Is there any
> inband mechanism defined by NVMe? I glanced through NVMe and NVMe
> Management Interface but couldn't find. Any insight is appreciated..
Currently it's platform/vendor specific.
There are multiple TPars under consideration in NVMe-MI that bring this
capabilitity in various way, but I'm not directly involved with any
of these.
parent reply other threads:[~2016-10-14 15:57 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <OF6508F29F.5646743D-ON8625804C.0051E01E-8625804C.00552F15@notes.na.collabserv.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161014155722.GA19383@localhost.localdomain \
--to=keith.busch@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.