With the introduction of TCP Adaptive Buffering in WAAS 4.1, TCP send and receive buffers are dynamically sized as network conditions warrant. In most cases, you do not need to modify the acceleration TCP adaptive buffering settings because your WAAS system automatically configures the TCP adaptive buffer settings based on the network bandwidth and delay experienced by each connection.
Adaptive buffering allows the WAAS software to dynamically vary the size of the send and receive buffers to increase performance and more efficiently use the available network bandwidth.Manual configuration of the buffers isn't normally necessary. Only in cases of troubleshooting performance problems, manual configuration may come handy.
So, the question is are you observing a performance problem at this site? Also, if you will be modifying the buffers on this site's WAE you should also modify them on the peer WAE(s) (e.g. the DC WAE) as well to keep the buffers in sync. Note, the TFO adaptive buffering feature will need to be disabled in order for these static buffers to take affect.
Is it all apps that are having a problem or only certain apps?
Before you introduced WAAS at this site and the clients accessed these apps over the WAN was the performance worse (e.g. what was the baseline performance before WAAS, and has WAAS improved the situation from the baseline)?
Topology & Design:
Two ACI fabrics
Stretching VLANs using OTV
Both fabrics are advertising BD subnets into same routing domain
Some BDs(or say VLANs) are stretched, but some are not.
Endpoints can move betwee...
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
Topology &Design:Traffic flow within same fabric:Endpoint moves to Fabric-2Bounce Entry Times OutTraffic Black-holedSummarySolutionAppendix:
In the Previous articles of ACI Automation, we are using Postman/Newman a...