Frank Cusack wrote:
> On July 15, 2008 7:44:53 AM -0500 Jason King <[EMAIL PROTECTED]> wrote:
>
>> http://blogs.sun.com/eschrock/entry/external_storage_enclosures_in_solaris
>> has a bit more info on some of this -- while I would expect Sun
>> products to integrate that well, it's nice to know the framework is
>> there for other vendors to do the same if they wish.
>>
>
> Wow, that's hot off the presses. Sounds perfect, but I guess it will
> be awhile before it makes it into Solaris. I'm surprised Sun would
> release a storage product without the ability to know which drive has
> failed.
>
Eh? The J400 series, and almost all other Sun storage arrays, uses
the Sun Common Array Manager (CAM) software which includes
a Fault Management Service (FMS) component that will manage
faults, automatically log service calls (aka phone home), etc. For
more details on how to use CAM for the J4000 arrays, see the
docs at
http://docs.sun.com/app/docs/coll/cam6.1
especially the User Guide for the J4000 Array.
The difference between CAM and native Solaris FMA services
is that CAM runs on Solaris, Windows, and Linux servers. CAM
provides local and remote CLI as well as a BUI. So, I would say
that CAM is an array-specific manager which runs on multiple
operating systems as opposed to the work being done by Eric and
team which is to make an array-agnostic manager for Solaris.
In truth, both solutions are needed :-)
-- richard
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
