Your problem sounds EXACTLY like a problem that we've run into at two of our facilities and we have found the solution for our situation. The difficulty was the random nature of the problem, but when it occurred it had significant impact on our users' ability to access their file systems. We took a pktt trace and saw similar errors; SMB2 135 Create Response, Error: STATUS_OBJECT_NAME_NOT_FOUND or SMB2 135 Ioctl Response, Error: STATUS_INVALID_DEVICE_REQUEST. The big clues for us were the TCP 70 [TCP Dup ACK #####] 445 errors, the TCP 1518 [TCP Out-Of-Order] errors, and the [TCP ACKed unseen segment] errors.
We found that there is an incompatibility between NetApp systems using Fastpath (enabled by default) and Nexus switches using virtual port channeling (vPC) without the vPC peer-gateway feature enabled. The vPC peer-gateway was introduced in NX-OS 4.2.1 for the 7000 series switches and 5.0(3)N1(1) for the 5500 series switches after the problem was discovered. If you are using NetApp attached to Cisco Nexus 5500 or 7000 series switches, be sure you either enable the peer-gateway on your port channels, or disable Fastpath on your NetApp system. The following links provide additonal details.
I hope this is helpful for others.
KB# 2013848 Version: 6.0 Published date: 03/27/2014
- KB 1012623: OEM: How to disable ip.fastpath in Clustered Data ONTAP
- KB 3011178: How does a multimode vif interact with ip.fastpath?