Skip to main content
NetApp Knowledge Base

CriticalFruNotPresentAlert is reported on a single node in the HA pair

  1. Last updated
  2. Save as PDF
Views:
795
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
hw
Last Updated:

Applies to

  • ONTAP 9
  • FAS/AFF Systems

Issue

  • The following alerts are seen in the event logs:

[Node-01: cphmd: hm.alert.raised:alert]: Alert Id = CriticalFruNotPresentAlert , Alerting Resource = PSU1 FRU#95210XXXXXX raised by monitor chassis
[Node-01: cphmd: hm.alert.raised:alert]: Alert Id = CriticalFruNotPresentAlert , Alerting Resource = PSU2 FRU#95210XXXXXX raised by monitor chassis

  • The output of system health alert show command reports the same alert:

Cluster1::*> system health alert show

               Node: Node-01
           Alert ID: CriticalFruNotPresentAlert
           Resource: PSU2 FRU#95210XXXXXX
           Severity: Critical
    Indication Time: Sat May 13 13:46:10 2023
           Suppress: false
        Acknowledge: false
     Probable Cause: PSU2 FRU is not present in the chassis 95210XXXXXX.
                     The nodes in this chassis are Node-01.
    Possible Effect: The nodes in the chassis might not function
                     effectively or redundancy might be lost.
Corrective Actions: 1. Plug in PSU2 FRU correctly into the slot.
                     2. Refer to the Hardware specification guide for more information on the position of the field-replaceable unit (FRU) and ways to check or replace it.
                     3. Contact support personnel if the alert persists.

  • The missing FRUs are reported as unreachable by the affected node:

Cluster1::*> system controller fru show
Node               FRU Name                     Subsystem          Status
------------------ ---------------------------- ------------------ -----------
Node-01            PSU1 FRU                     Environment        unreachable
Node-01            PSU2 FRU                     Environment        unreachable

  • The same FRUs report normal status from the partner node:

Node               FRU Name                     Subsystem          Status
------------------ ---------------------------- ------------------ -----------
Node-02            PSU1 FRU                     Environment        ok
Node-02            PSU2 FRU                     Environment        ok

  • The SP/BMC on the affected node is already on the latest version.
  • The details may not be shown for the missing FRU under system chassis fru show

::> system chassis fru show

Chassis ID          FRU        Type     State       Nodes Sharing the FRU
------------------- ---------- -------- ----------- -----------------------
95210XXXXXXXX       Fan2       fan      GOOD         Node-02
95210XXXXXXXX       Fan2       fan      GOOD         Node-01
95210XXXXXXXX       Fan1       fan 

  • Performing takeover/giveback of the node does not help.       

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.