I currently have WAAS deployed in my environment. I would like to introduce wred to prevent sessions from overiding my network. However, my WAAS engineer thinks that using WAAS would pose a problem.
Issue:
At least once a week a user attempts to ftp a large file from the internet, which ends up causing performance issues and saturation. The internet is via the datacenter so egress qos is being used.
Internet --WAAS---Router=====MPLS======Router----WAAS----Client
Since there is no way to do ingress shaping. And that would not entirely help either. I need a way to manage session by session during congestion. So introduce WRED. Which will look like that.
Internet----WAAS---Router======MPLS======Router--(wred)---WAAS---Client
So on the internal interface going egress to the LAN to regulate ingress sessions to the lan during a congestion state.
The problem for thought.
Lets say in a congestion state WRED randomly drops packets to throttle back the window size of an ftp session going through WAAS. How would WAAS respond to the random dropping of packets? Do those drops go to the source of the packets to throttle back or does WAAS act as the source? WAAS specialty is performance so it is supposed to compensate for drop packets. In this scenerio is WAAS the problem?
If your an expert in WAAS I welcome your opinion.
