OpenSolaris

1. Community: OS/Net (ON)
   1. Blogs
   2. Development Process
   3. Developer's Reference
      1. Introduction
      2. Prerequisites
      3. The Source Tree, part 1
      4. The Source Tree, part 2
      5. Building OpenSolaris
      6. Installing and Testing OpenSolaris
      7. Integration Procedure
      8. Best Practices and Requirements
      9. Glossary
   4. Discussions
   5. Installation (from source) Quickstart
      1. Annotated nightly(1) Mail Example
   6. Currently Known Issues
   7. CRT
      1. Advocates & Sponsors
      2. Becoming a CRT Advocate
      3. Charter
      4. RTI nits to avoid
      5. Sponsor Tasks
      6. Becoming a Sponsor
   8. Schedule
   9. ONNV Flag Days, Heads Ups, and Project Integration History
      1. All
      2. Builds 91-95
      3. Builds 86-90
      4. Builds 81-85
      5. Builds 76-80
      6. Builds 71-75
      7. Builds 66-70
      8. Builds 61-65
      9. Builds 56-60
      10. Builds 51-55
      11. Builds 46-50
      12. Builds 41-45
      13. Builds 36-40
      14. Builds 31-35
      15. Builds 26-30
      16. Builds 21-25
   10. Leaders
   11. Observers
   12. Putback Logs
   13. Developing Solaris
       1. Quality Death Spiral
   14. wx
   15. findunref and unreferenced files
   16. Bourne/Korn Shell Coding Conventions

Heads Up: Sun Fire X4500 Disk FMA

Date: Mon, 22 May 2006 14:20:28 -0700 (PDT)
From: Seth Goldberg <Seth dot Goldberg at Sun dot COM>
To: on-all at eng dot sun dot com, onnv-gate at onnv dot eng dot sun dot com
Subject: Heads Up: Sun Fire X4500 Disk FMA


With the putback of:

  	6416735 Sun Fire X4500 systems need a disk diagnosis engine

Solaris Nevada now supports monitoring SATA disks in the Sun Fire X4500 
(formerly known as Thumper) for predictive failures (by polling the drive's 
SMART firmware) and for hotplug events.  LEDs next to each disk (OK-to-Remove, 
Faulted) now function as they were designed.

Fault information is logged with fmd(1M) (and displayed in the system log), 
and the standard FMA administration utilities may be used to identify the 
fault and faulty disk (fmdump(1M) and fmadm(1M) faulty) or repair the fault 
(fmadm repair) manually.  Replacing the faulted disk automatically clears the 
fault.  Disks that are not repaired will continue to generate FMA fault 
messages to the system console when fmd is restarted.

In addition, the Sun Fire X4500 diagnosis engine informs the service processor 
of the current states of the disk as well as the disks' FRU information 
(model, manufacturer, serial number, firmware revision, and capacity). 
External agents can observe the current disk state and disk FRU information 
remotely through the service processor, via IPMI (see ipmitool(1m), fru 
subcommand).

ARC cases:
----------
PSARC/2006/322 FMA for Sun Fire X4500 SATA Disks
PSARC/2006/221 /dev/bmc interface upgrade

Portfolio:
----------
2006/012.thumper

Please let me know if you have any questions.

  Thanks,
  The Solaris Thumper Team