Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-2046829.1
Update Date:2018-03-14
Keywords:

Solution Type  Technical Instruction Sure

Solution  2046829.1 :   How to Clear an ILOM Hardware Fault Via the ILOM CLI on BDA  


Related Items
  • Big Data Appliance X3-2 Full Rack
  •  
  • Big Data Appliance X3-2 In-Rack Expansion
  •  
  • Big Data Appliance Hardware
  •  
  • Big Data Appliance X3-2 Starter Rack
  •  
Related Categories
  • PLA-Support>Eng Systems>BDA>Big Data Appliance>DB: BDA_EST
  •  




In this Document
Goal
Solution
References


Applies to:

Big Data Appliance X3-2 Starter Rack - Version All Versions and later
Big Data Appliance Hardware - Version All Versions and later
Big Data Appliance X3-2 Full Rack - Version All Versions and later
Big Data Appliance X3-2 In-Rack Expansion - Version All Versions and later
Linux x86-64

Goal


The goal of this document is to provide the steps to clear an ILOM hardware fault via the ILOM CLI on BDA. It can be useful to try to clear an existing ILOM fault once prior to BDA reimage, upgrade or install.  If persistent, then  BDA Support needs to be engaged because a hardware component replacement may be necessary.

For more details please see: How to clear FMA logs on the ILOM or Solaris on x86 platforms (Doc ID 1381773.1).

Solution

The steps to clear an ILOM warning via the ILOM CLI on BDA are below.

1. ssh into the ILOM for the node with the fault.

2.  From the ILOM CLI run these commands.  "/SYS" needs to be replaced by the component that is throwing the warning.  For example if fmadm faulty -f reported /SYS/MB/P0 faulty, the command would be 'fmadm repair /SYS/MB/P0' instead of 'fmadm repair /SYS'.

cd /SP/faultmgmt
start shell
fmadm faulty -f
fmadm repair /SYS
fmadm faulty -f
exit

Using an example of  "fault.chassis.env.temp.over-fail", output looks like:

a) Prior to clearing the fault, bdacheckhw or bdacheckcluster reports the fault like:

Running hardware checks on all nodes
*.*.*.*: WARNING: Hardware errors reported by ILOM : fault.chassis.env.temp.over-fail
*.*.*.*: WARNING: Big Data Appliance warnings during hardware validation checks

 b) Clear the fault in the ILOM CLI:

# ssh <bdanodex>-ilom
  
Password:

Oracle(R) Integrated Lights Out Manager

Version 3.0.16.10.d r74499

Copyright (c) 2012, Oracle and/or its affiliates. All rights reserved.
->  cd /SP/faultmgmt
  
/SP/faultmgmt
-> start shell
  
Are you sure you want to start /SP/faultmgmt/shell (y/n)? y
faultmgmtsp> fmadm faulty -f
  
/SYS

Fault class : fault.chassis.env.temp.over-fail

UUID        : 25811b59-52f8-6f6c-c799-fed593042673

Description : Ambient temperature is at or above the normal temperature
              threshold.

Response    : Illuminate service-required LED on the chassis.

Impact      : None.

Action      : The administrator should review the ILOM event log for
              additional information pertaining to this diagnosis.  Please
              refer to the Details section of the Knowledge Article for
              additional information.


faultmgmtsp> fmadm repair /SYS
  
 
faultmgmtsp> fmadm faulty -f
  
No faults found
faultmgmtsp> exit
-> exit
  
Connection to <bdanodex>-ilom closed.

c) After clearing the fault, bdacheckhw or bdacheckcluster reports success.  No fault.chassis.env.temp.over-fail remains.  If it does, the faulty hardware may need replacement.

 


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback