On 24 March 2016 at 18:34, Joel M Snyder <[email protected]> wrote: > I designed it into a network of about 90 sites (global, not US) and it was > not a resounding success. The management was ugly, but more importantly it > just didn't play well with others and at some clear points wasn't working at > all. It was pulled out in favor of a WAN opt solution (Cisco WaaS appliance > in that case). I reviewed it again and did some testing for a larger > network of 400+ sites recently, but the feature set wasn't measuring up to > the requirements and the customer stuck Riverbeds ahead of the IOS boxes and > is quite happy with the results.
Looks like PfR is lot more than just IP SLA udp jitter/icmp probe + tracking. My comments were strictly on that, I've not done the controller based PfR. -- ++ytti _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
