CRC errors on MetroCluster IP or Cluster with BES-53248 running EFOS 3.4.3.3
Applies to
- ONTAP 9
- MetroCluster IP or Cluster
- BES-53248
- EFOS 3.4.3.3
Issue
CRC errors reported on e0a
Following is reported in EMS/event log:
[cshmd: hm.alert.raised:alert]: Alert Id = SwitchIfOutErrorsWarn_Alert , Alerting Resource = switch/Slot: 0 Port: 9 25G - Level raised by monitor cluster-switch
[intr: netif.linkErrors:error]: Excessive link errors on network interface e0a. Might indicate a bad cable, switch port, or NIC, or that a cable connector is not fully inserted in a socket. On a 10/100 port, might indicate a duplex mismatch.
[cshmd: hm.alert.cleared:notice]: Alert Id = SwitchIfOutErrorsWarn_Alert , Alerting Resource = switch/Slot: 0 Port: 9 25G - Level cleared by monitor cluster-switch
[vifmgr: vifmgr.cluscheck.crcerrors:alert]: Port e0a on node is reporting a high number of observed hardware errors, possibly CRC errors.
[monitor: monitor.globalStatus.critical:EMERGENCY]: Controller failover of affnode is not possible: unsynchronized log.
[cf_main: cf.fsm.takeoverOfPartnerDisabled:error]: Failover monitor: takeover of affnode disabled (unsynchronized log).
[intr: netif.linkErrors:error]: Excessive link errors on network interface e0a. Might indicate a bad cable, switch port, or NIC, or that a cable connector is not fully inserted in a socket. On a 10/100 port, might indicate a duplex mismatch.
[vifmgr: vifmgr.cluscheck.crcerrors:alert]: Port e0a on node affnode is reporting a high number of observed hardware errors, possibly CRC errors.
Following is reported in ifstat output:
...
Non-primary u/c: 0 | CRC errors: 175k | Runt frames: 0
...
Following was reported in the switch #show interface ethernet 0/14 output:
Total Packets Received with MAC Errors......... 4859
Jabbers Received............................... 3121
...
FCS Errors Received............................ 1738
...
Total Transmit Errors.......................... 106
...
Transmit errors................................ 106
...