File access and performance issues while CRC errors are present on Network ports
Applies to
- ONTAP 9
- CIFS/NFS (NAS)
- Network Ports
- Cyclic Redundancy Check (CRC)
Issue
File access and performance issues while CRC errors are present on Network port.
- High number of CRC errors reported on a port; example e4a:
Sat Nov 13 00:06:09 +0100 [cluster1-01: vifmgr: vifmgr.cluscheck.crcerrors:alert]: Port e4a on node cluster1-01 is reporting a high number of observed hardware errors, possibly CRC errors- Continued packet loss:
Sat Nov 13 01:02:00 +0100 [cluster1-01: vifmgr: vifmgr.cluscheck.ctdpktloss:alert]: Continued packet loss when pinging from cluster lif ams2-cluster1-01_clus1 (node cluster1-01) to cluster lif cluster1-02_clus1 (node cluster1-02)
- Nblade.CifsOperationTimedOut:
Sun Nov 14 08:07:56 +0100 [cluster1-01: kernel: Nblade_CifsOperationTimedOut_1:error]: params: {'remoteBladeID': '61a30da8-624a-11eb-b2e2-d039ea4631cc (cluster1-02)', 'cmdRestartCnt': '0', 'vserverId': '4', 'commandName': 'SMB2_COM_CLOSE', 'isQosEnabled': 'QoS_disabled', 'lastSpinNpError': 'SPINNP_NO_FO_ERROR', 'localIpAddress': '<local_IP>', 'lastCsmError': 'CSM_TIMEOUT', 'clientIpAddress': '<client_IP>', 'suspensionCnt': '31', 'dsId': '2084480404'}- Junction root lookup errors:
Sun Nov 14 08:05:04 +0100 [cluster1-01: nblade2: Nblade.JunctionRootLookup2:error]: Junction root lookup of a volume in Vserver 5 with MSID 3221226001 has failed for reason "CSM_TIMEOUT".
- Secd and dns timed out errors reported in EMS :
secd.lsa.noServers: None of the LSA servers configured for Vserver (SVM1) are currently accessible via the network.
secd.dns.srv.lookup.failed: DNS server failed to look up service (_ldap._tcp.dc._msdcs.domain.com) for vserver (SVM1) with error (Operation timed out).
secd.dns.server.timed.out: DNS server 192.xx.xx.xx did not respond to vserver = SVM1 within timeout interval.