Skip to main content
NetApp Knowledge Base

BES-53248 unexpected reboot due to memory leak

Views:
509
Visibility:
Public
Votes:
0
Category:
fabric-interconnect-and-management-switches
Specialty:
hw
Last Updated:

Applies to

  • BES-53248
  • EFOS 3.11.1.2

Issue

  • BES-53248 cluster switch reboots unexpectedly with no power disruption or power maintenance being confirmed:
  • The free memory is reduced over a period of 6 to 7 months eventually resulting in a reboot.

------------------------ Print file - slog0.txt ------------------------
<185> Jun  4 05:42:17 0.0.0.0-1 SIM[Cnfgr_Thread_]: sim_util.c(4302) 12 %% ALRT Switch was reset due to power disruption or unexpected restart.(error[0x0]).

  • The following ISL down alerts are reported by the partner switch:

[Node-01: cshmd: hm.alert.raised:alert]: Alert Id = ClusterIfIslDownWarn_Alert , Alerting Resource = CS2/Slot: 0 Port: 55 100G - Level raised by monitor ethernet-switch
[Node-01: cshmd: hm.alert.raised:alert]: Alert Id = ClusterIfIslDownWarn_Alert , Alerting Resource = CS2/Slot: 0 Port: 56 100G - Level raised by monitor ethernet-switch
[Node-01: mgwd: callhome.hm.alert.major:alert]: Call home for Health Monitor process cshm: ClusterIfIslDownWarn_Alert[CS2/ Link Aggregate 1].

  • The ISL links come up when the switch is back online and the alerts are cleared.

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.