![]() | Sun System Handbook - ISO 4.1 October 2012 Internal/Partner Edition | ||
|
|
![]() |
||||||||||||||||
Solution Type Problem Resolution Sure Solution 1451275.1 : Sun SPARC[R] Enterprise M3000/M4000/M5000/M8000/M9000 Servers (OPL): Why FMA Events remain in the FMA history of M-Series XSCFUs
FMA event history should be left intact and does not necessarily indicate a current fault In this Document
Created from <SR 3-5606197971> Applies to:Sun SPARC Enterprise M3000 Server - Version Not Applicable to Not Applicable [Release N/A]Sun SPARC Enterprise M4000 Server - Version Not Applicable to Not Applicable [Release N/A] Sun SPARC Enterprise M5000 Server - Version Not Applicable to Not Applicable [Release N/A] Sun SPARC Enterprise M8000 Server - Version Not Applicable to Not Applicable [Release N/A] Sun SPARC Enterprise M9000-32 Server - Version Not Applicable to Not Applicable [Release N/A] Oracle Solaris on SPARC (64-bit) SymptomsFMA events on XSCF remain after clearing associated issues: XSCF> showstatus XSCF> fmdump CauseOn this platform FMA on the XSCF is managed in a different manner to the Solaris FMA implementation. 'showstatus' is utilised in a similar manner to 'fmadm faulty' in Solaris; if a component is reported in showstatus then usual process is to investigate the FMA events to determine a cause and action-plan. The FMA event history is generally left intact (to provide some history for any future diagnsosis). If there are no components reported in 'showstatus' then the platform is considered not to have any current fault. The only way a component will be removed from the 'showstatus' output is either:
If this is done and there is still a fault, the XSCF software will put the status back to degraded/faulted/deconfigured when it re-runs it's fault tests. The 'restoredefaults' command is provided to reset the XSCF to factory settings (but this also clears all configuration data and setup). This command is intended for resellers and system installers who need to clear the status of platforms as errors can be generated during platform configuration especially on earlier versions of XSCF firmware. Assuming any previous components listed in showstatus have been addressed and issue is perceived to be that the events are still listed in FMA (and no new events have been created) then there is no actual fault on the system. SolutionNo further action is required Attachments This solution has no attachment |
||||||||||||||||
|