Skip to main content
NetApp Knowledge Base

SP or BMC reports critical: Heartbeat stopped due to a high network load from the management network

  1. Last updated
    Feb 24, 2025
  2. Save as PDF
Views:
3,976
Visibility:
Public
Votes:
2
Category:
fas-systems
Specialty:
hw
Last Updated:
2/24/2025, 4:04:03 PM

Applies to

Issue

  • Node panic or boot failed.
  • events all reports Heartbeat stopped and Heartbeat stopped.

Record 1731: Wed May 06 22:18:16.800000 2020 [BMC.critical]: Heartbeat stopped
Record 1732: Wed May 06 22:18:16.830000 2020 [Trap Event.warning]: hwassist loss_of_heartbeat (30)
Record 1733: Wed May 06 22:19:05.460000 2020 [ASUP.notice]: First notification email | (HEARTBEAT_LOSS) WARNING | Send failed
Record 1734: Wed May 06 22:33:22.320000 2020 [ASUP.notice]: Reminder email | (HEARTBEAT_LOSS) WARNING | Sent

Record 1679: Thu May 12 01:04:07 2022 [SP.critical]: Heartbeat stopped
Record 1680: Thu May 12 01:07:19 2022 [ASUP.notice]: Reminder email | (REBOOT (abnormal)) WARNING | Sent

  • events all may report SP load is high.

 

 

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.