I have run into an issue that i believe is file server related however i just want to run it by the board for clarification.
A remote site was recently converted from a standalone server site to one that is supported via WAFS/WAAS 4.0.11 installed on a 512 WAE w/ 2GB of Ram acting as wafs edge. The core is a 612 w/ 4GB of ram.
All user home folders reside across the WAN in the data center on a NetApp NAS SAN hosting the home folder natively (there is no windows server involved).
The issue is with file locking. Periodically, when a user opens a file on the server that is already been opened they are not getting any indication that the file is in use. Once they go to save the file they are told by the system that they cannot save the file using the same filename since it is being modified.
From reading the docs on WAFS/WAAS this looks like it is a problem with the OpLocks coming from the NetApp NAS and nothing to do with WAFS since WAFS/WAAS doesn't act on file locking requests, only passing them through to the file server.
Are my assumptions correct in this regard? Could WAFS be interferring some how with this communication and causing the file locking information being received from the NetApp NAS not to be correctly sent to the client?
Any way for me to debug this besides a packet capture? Any show commands that could indicate an issue? or logs?