I have a WAAS demo setup in a test lab and have a simulated T1 span connecting two networks. When I transfer a file using CIFS or web initially, I see the traffic flow through the WAN. When I do the transfer a second time, I know it is getting the data from cache as there is no WAN traffic, but I am not getting it at wire speed. It is only coming to the client at about double the T1 speed. I expected almost line speed access when getting data from local cache. Is there a setting I missed or is this expected behaviour?
Have you had a chance to get the router configuration along with the wccp output? In the event that unoptimized traffic reaches a WAE, the WAE forwards the traffic in pass-through mode without affecting the performance of the application using the passed-through connection. The following url will help you
Did you get this figured out? I know that if you rename the file or change the file that it has to be sent across the WAN again as the WAAS solution cannot just update incremental changes to files. If you didn't change the file then I would think you should be seeing better speeds once its already come across the WAN.
We changed the setup to use the WAN Bridge emulator package to simulate a T1 rather that rate-limit it and have gotten slightly better results. The main issue at this point is that initial transfers are actually slower than a direct connection with out inline setup. Waiting on a response from our local SE to review the configuration.
Yes, I understand some things could break if you are careful with those commands, but doing some simple "show" commands (or using the gui) shouldn't hurt when troubleshooting without TAC. I've used some expert show commands to see which files are actively being accelerated through the edge device.
A little off-topic, but how are the drives partitioned? Our WAE-512 edge has 2 250GB drives mirrored, the "Maximum Cache Disk Size" only shows 93GB. I understand there are probably OS, swap, and log partitions, but it would be nice to know more definitely how it is split up to explain to a customer why they don't get the "full" size of the drive.
VMware Trunk Port Group is supported from ACI version 2.1
VMM integration must be configured properly
ASA device package must be uploaded to APIC
ASAv version must be compatible with ACI and device package version
In the Previous articles of ACI Automation, we are using Postman/Newman as the Rest API tool to automate the ACI Configuration.
In this article I’m going to discuss on usin...
One of the first steps in building your ACI Fabric is to go through Fabric Discovery. While Fabric Discovery is usually a straightforward process, there are various issues that may prevent you from discovering an ACI switch. This article wil...