We recently installed a Cisco WAAS for a customer consisting of a core 612-4GB, 512-2GB for edge, and a 512 for CM duties. We configured the 612 to export specific files on a netapp NAS to remote users at the edge. The WAN connection between core and edge is 6Mbps Metro LAN.
Acceleration works great on typical FTP/HTTP and even most of the CIFS traffic. However, there is one application that the customer is using the requires the application be located on a CIFS file share on the NetApp NAS. This is a homegrown app that calls about 50 .exe and .dll files on the local file share during startup as well as several SQL files. Its a client/server based application with a fat client installed on each users desktop.
We wan the cisco WAFS benchmark tool and examined the results. CIFS AO is definately working.
The application, however is still significantly slower to open at the edge site as compared to the central office site. 5secs locally and 30-35secs remote. Application response time inside the application is slow as well for certain queries.
We ran some packet captures on the client and examined the results. When using the SMB analysis commands inside of wireshark we can see that most of the CIFS transacation types are getting SRT in the neighborhood of <5-20msec. Their WAN is about 20-45msec, telling me that most of these transactions are getting responded to by the WAE.
Does the CIFS AO proxy on the WAE respond to the following transaction types locally?
Other Query Types
Since the application is calling about 50 or so small files i was wondering if the SMB queries are being cached on the WAE or must make the round trip to the origin server and be subject to WAN delay. Comparing the results of the same test local to the server results in all transactions getting <1msec SRT so my feeling is anything over 20msec is probably not getting cached/responded by the WAE and is subject to WAN delay.
Is there a breakdown out there of what the WAE CIFS AO will and will not cache or respond to ?