CRC errors when 40G/100G CX5 NIC connect to Broadcom BES-53248 cluster switch
Applies to
- FAS/AFF
- BES-53248
- cluster interconnect
Issue
- System alert for inbound packet errors.
Example:
cluster1::*> alert show
(system health alert show)
Node: cluster1-01
Resource: <switch port>
Severity: Major
Indication Time: Tue Feb 08 18:01:43 2022
Suppress: false
Acknowledge: false
Probable Cause: The percentage of inbound packet errors of switch
interface "switchname/<switch port>" is above the warning threshold.
CLUSTER NETWORK DEGRADEDdue toCRC Errors Detectedon all cluster ports when connect to BES-53248.
Example:
<LR d="02Sep2021 13:17:24" n="node1" t="0000000" id="0/26207890441008" p="1" s="Ok" o="vifmgr" vf="" type="1" seq="180177" supp="98" >
<callhome_clus_net_degraded_1
subject="CLUSTER NETWORK DEGRADED"
event_type="CRC Errors Detected"
event_details="High CRC errors detected on port e0c node node1"/>
</LR>- Packet loss when ping from cluster lif.
Example:
[?] Tue Sep 07 07:43:56 +0800 [node1: vifmgr: vifmgr.cluscheck.ctdpktloss:alert]: Continued packet loss when pinging from cluster lif clusterlif (node node1) to cluster lif clusterlif(node node2)- Cluster alert raised/cleard multiple times for ethernet-switch.
Example:
[?] Tue Sep 07 02:31:14 +0800 [na02: cshmd: hm.alert.raised:alert]: Alert Id = ClusterIfInErrorsWarn_Alert , Alerting Resource = CS1/Slot: 0 Port: 50 100G - Level raised by monitor ethernet-switch[?] Tue Sep 07 02:31:14 +0800 [na02: cshmd: hm.alert.cleared:notice]: Alert Id = ClusterIfInErrorsWarn_Alert , Alerting Resource = CS2/Slot: 0 Port: 50 100G - Level cleared by monitor ethernet-switch