Skip to main content
NetApp Knowledge Base

Call home for Health Monitor process cshm: ClusterIfInErrorsWarn_Alert

  1. Last updated
  2. Save as PDF
Views:
152
Visibility:
Public
Votes:
0
Category:
aff-series
Specialty:
hw
Last Updated:

Applies to

  • FAS/AFF
  • Cluster switch BES-53248

Issue

  • Below events are seen
Mon Jan 20 18:51:24 +0200 [Node1: mgwd: callhome.hm.alert.major:alert]: Call home for Health Monitor process cshm: ClusterIfInErrorsWarn_Alert[sw1/Slot: 0 Port: 52 100G - Level].
Mon Jan 20 15:24:56 +0200 [Node1: cshmd: hm.alert.raised:alert]: Alert Id = ClusterIfInErrorsWarn_Alert , Alerting Resource = sw1/Slot: 0 Port: 52 100G - Level raised by monitor ethernet-switch
Mon Jan 20 15:29:56 +0200 [Node1: cshmd: hm.alert.raised:alert]: Alert Id = ClusterIfOutErrorsWarn_Alert , Alerting Resource = sw1/Slot: 0 Port: 49 100G - Level raised by monitor ethernet-switch
Mon Jan 20 15:31:23 +0200 [Node1: mgwd: callhome.hm.alert.major:alert]: Call home for Health Monitor process cshm: ClusterIfOutErrorsWarn_Alert[sw1/Slot: 0 Port: 49 100G - Level].
  • We are experiencing FCS errors on switch port 0/52, where FEC is currently disabled. It is important to note that FEC should be enabled on both ends of the link. In contrast, all other 100G ports have FEC enabled. This discrepancy may be contributing to the errors we are observing.
     
  • From switch Logs, we can confirm that FEC status like if it is enabled on ports or not.

Total Packets Received with MAC Errors......... 360532
Jabbers Received............................... 0
Fragments Received............................. 0
Undersize Received............................. 0
Alignment Errors Received...................... 0
FCS Errors Received............................ 360532
Overruns Received.............................. 0
URPF Discards.................................. 0

  • One switch port on both switches is configured to disable FEC.

interface 0/52
no fec 
service-policy in CLUSTER
no shutdown
description "40/100GbE Node Port"
spanning-tree edgeport
mtu 9216
switchport mode trunk
switchport trunk allowed vlan 1,17-18
datacenter-bridging
priority-flow-control mode on
priority-flow-control priority 2 no-drop
priority-flow-control priority 5 no-drop
exit

 

 

 

 

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.