Search

Why CRC errors on the storage controller may follow the placement of a lif?
https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Why_CRC_errors_on_the_storage_controller_may_follow_the_placement_of_a_lif
CRC errors seen on ifstat may not be related to the effective communication between that port and the corresponding switch port, if the switch is cut-through A frame containing CRC error will be forwa...CRC errors seen on ifstat may not be related to the effective communication between that port and the corresponding switch port, if the switch is cut-through A frame containing CRC error will be forwarded to the outbound port by the switch, cause the switch will start forwarding the frames before complete reception When CRC errors are propagated, moving a lif to a different port will have the side effect of redirecting these packets to the new port
Unable to vMotion virtual machine(s) from ESXi host
https://kb.netapp.com/Legacy/NetApp_HCI/OS/Unable_to_vMotion_virtual_machine_s_from_ESXi_host
Applies to NetApp HCI NetApp ONTAP ESXi (All versions) vMotion Issue vMotion fails when trying to migrate virtual machines to and from certain ESXi hosts.
Incorrect "ifstat" values are displayed for the Transmit-Total errors counter for a CNA card
https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Incorrect_ifstat_values_are_displayed_for_the_Transmit_Total_errors_counter_for_a_CNA_card
4/18/2019 11:35:16 FAS2620_0125 ALERT vifmgr.cluscheck.crcerrors: Port e0c on node FAS2620_0125 is reporting a high number of observed hardware errors, possibly CRC errors. 4/18/2019 10:31:05 FAS2620_...4/18/2019 11:35:16 FAS2620_0125 ALERT vifmgr.cluscheck.crcerrors: Port e0c on node FAS2620_0125 is reporting a high number of observed hardware errors, possibly CRC errors. 4/18/2019 10:31:05 FAS2620_0126 ALERT vifmgr.cluscheck.crcerrors: Port e0c on node FAS2620_0126 is reporting a high number of observed hardware errors, possibly CRC errors.
High amount of CRC errors reported after upgrade to ONTAP 9.7
https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/High_amount_of_CRC_errors_reported_after_upgrade_to_ONTAP_9.7
Applies to FAS systems AFF systems ONTAP 9 Issue The following messages are observed in the system event logs: Port <port name> on node <node name> is reporting a high number of observed hardware erro...Applies to FAS systems AFF systems ONTAP 9 Issue The following messages are observed in the system event logs: Port <port name> on node <node name> is reporting a high number of observed hardware errors, possibly CRC errors.
CRC errors from unsupported SFP
https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/CRC_errors_from_unsupported_SFP
Applies to ONTAP 9 INTEL AFBR-709DMZ-IN2 RTXM320-571-C87 Issue EMS logs file with the following alerts: Wed May 06 20:25:55 +0200 [node: vifmgr: vifmgr.cluscheck.crcerrors:alert]: Port e0g on node nod...Applies to ONTAP 9 INTEL AFBR-709DMZ-IN2 RTXM320-571-C87 Issue EMS logs file with the following alerts: Wed May 06 20:25:55 +0200 [node: vifmgr: vifmgr.cluscheck.crcerrors:alert]: Port e0g on node node_name is reporting a high number of observed hardware errors, possibly CRC errors. Tue May 19 00:40:02 +0200 [node: vifmgr: vifmgr.cluscheck.crcerrors:alert]: Port e0g on node node_name is reporting a high number of observed hardware errors, possibly CRC errors.
How to confirm switchover safe after SAN issue
https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/How_to_confirm_switchover_safe_after_SAN_issue
Applies to ONTAP 9 MetroCluster Description After troubleshooting port cyclic redundancy check (CRC) errors in SAN and SFP replacement Is it safe to carry out power maintenance with MetroCluster switc...Applies to ONTAP 9 MetroCluster Description After troubleshooting port cyclic redundancy check (CRC) errors in SAN and SFP replacement Is it safe to carry out power maintenance with MetroCluster switchover?
vifmgr reporting CRC errors on multiple interfaces
https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/vifmgr_reporting_CRC_errors_on_multiple_interfaces
ONTAP 9 / FAS / AFF Systems: Multiple interfaces report CRC errors.
CRC errors on a data port connected to a Cisco switch
https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/CRC_errors_on_a_data_port_connected_to_a_Cisco_switch
Risk: This system has a high count of CRC errors accumulated on at least one data network port that should be investigated. Description: This system has CRC errors on data port e0e. Impact: High CRC e...Risk: This system has a high count of CRC errors accumulated on at least one data network port that should be investigated. Description: This system has CRC errors on data port e0e. Impact: High CRC errors counts, or link resets can result in packet loss and are typically caused by physical defects in the port, SFP, or cables The port is connected to a Data Switch IFSTAT-A section of AutoSupport or cluster::> ifstat -a reveals CRC errors: The stats on the node port are cleared, CRC errors return
Cluster Network Degraded alerts reported multiple times due to errors on cluster ports
https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/Cluster_Network_Degraded_alerts_reported_due_to_errors_cluster_ports
Multiple errors are reported on cluster ports of all the nodes except for one cluster port as seen in RECEIVE section of IFSTAT output. You may see the cluster switch health as degraded in the system ...Multiple errors are reported on cluster ports of all the nodes except for one cluster port as seen in RECEIVE section of IFSTAT output. You may see the cluster switch health as degraded in the system health alert show command output Cluster ports with multiple errors (may see a combination of CRC err, Error symbol, Illegal symbol, etc): The following alert may be generated against the connected switch port of the only node port without receive CRC errors:
StorageGRID reports Alert Node network reception frame error
https://kb.netapp.com/hybrid/StorageGRID/Alerts/StorageGRID_reports_increase_RX_TX_errors_in_GRID_Topology_with_NRER_or_NTER_alarms
Alert of "Node network reception frame error" is reported on GRID Alarms (NRER). This could be due to bad network SFP or cable. Refer to steps in the KB article to resolve the issue.
How to locate root cause for sCache usage increasement
https://kb.netapp.com/on-prem/solidfire/Element_OS_Kbs/How_to_locate_root_cause_for_sCache_usage_increasement
2020-11-18T05:03:38.441049Z xxxxxx sfinstall[13979]: Cache Size Current: 22800982016 Target: 5000000000 Difference: 17800982016 2020-11-18T05:08:39.062350Z xxxxxx sfinstall[13979]: Cache Size Current:...2020-11-18T05:03:38.441049Z xxxxxx sfinstall[13979]: Cache Size Current: 22800982016 Target: 5000000000 Difference: 17800982016 2020-11-18T05:08:39.062350Z xxxxxx sfinstall[13979]: Cache Size Current: 23601020928 Target: 5000000000 Difference: 18601020928 2020-11-18T05:13:39.691498Z xxxxxx sfinstall[13979]: Cache Size Current: 24701067264 Target: 5000000000 Difference: 19701067264