CIFS caching happens on Edge only to server content locally, the contents are checked for freshness (with the Server) every time a request is received at the edge before it's served. For the upload scenario, the reverse will be true. Verify your Edge/Core config and Connectivity directive.
You should also verify that your CIFS accelerator is registered on both WAEs (show tfo accelerator)
Configured 2 connectivity directives for both direction,
Client--WAE A (Edge)--- WAE B (Core)-- Server
Server--WAE A (Core)--- WAE B (Edge)-- Client
While doing a download from any office, the edge will use the respective connectivity directive and caches the content locally.
What happens for upload action..
- I understand that It must be using the same connectivity directive (WAE near to client -Edge, near to server -Core). When it is not caching in the core, how the acceleration happens (I can see good performance difference but not as good as download action)
Introduction This article will help you understand the steps on how to
download the UCS licenses from the Cisco Systems website and then
installing it on the UCS. The redacted (blue lines) just covers up
certain numbers for privacy please do not take them...
Introduction This article will help you understand and educate the
customer on how to clear their "expired licenses"
(license-graceperiod-expired) from their UCS-M. If a customer just
purchased a license and needs a step by step guide on how to download
Introduction Prepositioning is a powerful tools on the WAAS platform but
it is not always easy to figure out why your jobs are failing when
trying to retrieve the files.Here is a method that should help you to
figure out the reason why they are not succes...