Revision as of 15:57, 20 September 2012 by Jbarozet
- Performance Routing (PfR) has many features, provides many services and has a great flexibility.
- This page lists the most recent and important news and changes.
As part of the simplification initiative, IOS 15.2(3)T brings a lot of changes. Table below summarizes the changes for load-balancing and resolvers.
|Current Solution||After 15.2(3)T|
|Support utilization and range resolvers||Remove utilization and range resolvers|
|Delay, range, utilization resolvers are the default resolvers||No default resolver. PfR automatically does load balancing|
|Do random resolver for all qualified exits that satisfy the configured criteria||Do load balancing for all qualified exits that satisfy the configured criteria then random selection|
|Cost resolver can be configured with a higher priority than performance resolver in a policy||No priority option for resolver cost-min. It is always handled after any performance resolver|
|Trigger range OOP by comparing the load of an exit to all other exits.||Trigger range OOP by comparing the load of an exit to all other exits in the same group.|
|Check the soft limit before calling the resolver||Check soft limit of all exits before entering the resolver. If none of exits are below the limit, make selection by ignoring the soft limit.|