Skip to main content
NetApp Knowledge Base

Node goes down due to SP HBT STOPPED alert

Views:
1,100
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
HW
Last Updated:

Applies to

  • AFF-A300
  • FAS8200
  • FAS8700
  • FAS2720
  • FAS2620
  • ONTAP 9

Issue

  • Node goes down with the following errors in event logs:

[Node-02: spsm_listener: sp.heartbeat.stopped:error]: Have not received a IPMI heartbeat from the Service Processor (SP) in last 20 seconds.
[Node-02: spsm_listener: callhome.sp.hbt.missed:notice]: Call home for SP HBT MISSED
[Node-02: env_mgr: sp.ipmi.lost.shutdown:EMERGENCY]: SP heartbeat stopped and cannot be recovered. To prevent hardware damage and data loss, the system will shut down in 2 minutes.
[Node-02: spsm_listener: callhome.sp.hbt.stopped:alert]: Call home for SP HBT STOPPED

  • Before node goes down, SP-LATEST-IPMI may report multiple sensor can not be read normally:

Sensor Name              State          Current    Critical     Warning     Warning    Critical
                                        Reading       Low         Low         High       High
-------------------------------------------------------------------------------------------------
Partner Status           not_available      --
PSU1 Present             not_available      --
PSU1 5V                  not_available     -- mV       --          --          --          --
PSU1 12V                 not_available     -- mV       --          --          --          --
PSU1 5V Curr             not_available     -- mA       --          --          --          --
PSU1 12V Curr            not_available     -- mA       --          --          --          --
PSU1 Fan 1               not_available     -- RPM      --          --          --          --
PSU1 Fan 2               not_available     -- RPM      --          --          --          --
PSU1 Inlet Temp          not_available     -- C         0 C         5 C        57 C        62 C
PSU1 Hotspot Temp        not_available     -- C         0 C         5 C        90 C       100 C
PSU2 Present             not_available      --
PSU2 5V                  not_available     -- mV       --          --          --          --
PSU2 12V                 not_available     -- mV       --          --          --          --
PSU2 5V Curr             not_available     -- mA       --          --          --          --
PSU2 12V Curr            not_available     -- mA       --          --          --          --
PSU2 Fan 1               not_available     -- RPM      --          --          --          --
PSU2 Fan 2               not_available     -- RPM      --          --          --          --
PSU2 Inlet Temp          not_available     -- C         0 C         5 C        57 C        62 C
PSU2 Hotspot Temp        not_available     -- C         0 C         5 C        90 C       100 C
PSU_FAN                  not_available      --
Module B Expander Temp   failed            -- C         0 C         5 C        80 C        90 C
Module A Expander Temp   failed            -- C         0 C         5 C        80 C        90 C
Midplane 4 Temp          failed            -- C         0 C         5 C        47 C        52 C
Midplane 3 Temp          failed            -- C         0 C         5 C        47 C        52 C
Midplane 2 Temp          failed            -- C         0 C         5 C        47 C        52 C
Midplane 1 Temp          failed            -- C         0 C         5 C        47 C        52 C
Ambient Temp             failed            -- C         0 C         5 C        47 C        50 C
Internal Shelf           not_available      --

  • The node is unable to boot even after a power cycle and reseat.

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.