My current setup is very simple. I have 2 WAE's with Inline adapters running across the core of my network. They both see the traffic between them, but very little gets optimized.
I have been able to figure out what is going on, but don't understand if WAAS should handle this situation. I run several VLAN's and the Core switch uses EIGRP for routing. When I do a traceroute, I see that EIGRP is choosing to send traffic between it and the Core router (Core WAE in between them) across VLANs that are not the Default VLAN. If I put in static routes at the Core switch to use the default VLAN, WAAS happily optimizes the traffic. When I let EIGRP choose routing across the Core, WAAS only optimizes a small percentage of valid traffic.
Note that there is only one physical path between the 2 WAE's. There is only one router hop in the middle. I have not found any documentation that says this should not work.
I am running 4.0.19 and will happily provide configs, etc. I would love to hear what others think about whether WAAS is working properly under the circumstances?
Oh, this is only a test. I realize that there is not much point in trying to optimized traffic across the core, but I hit this same issue when I took my Edge WAE to a remote site.
By default, traffic for a given connection must be seen by the inline module on the same VLAN in both directions to be optimized. In 4.0.19 we added the ability to disable this check using the following global configuration command:
[no] inline vlan-id-connection-check