PfR:News
From DocWiki
(Difference between revisions)
(→IOS 15.2(3)T) |
(→IOS 15.2(3)T) |
||
| Line 14: | Line 14: | ||
<br> | <br> | ||
| - | ==IOS 15.2(3)T== | + | ==IOS 15.2(3)T and IOS-XE 3.6== |
As part of the simplification initiative, IOS 15.2(3)T brings a lot of changes. | As part of the simplification initiative, IOS 15.2(3)T brings a lot of changes. | ||
| Line 24: | Line 24: | ||
|- | |- | ||
| style="color:black; background-color:#ffffcc;" | '''Current Solution''' | | style="color:black; background-color:#ffffcc;" | '''Current Solution''' | ||
| - | | style="color:black; background-color:#ffffcc;" | '''After 15.2(3)T''' | + | | style="color:black; background-color:#ffffcc;" | '''After 15.2(3)T / XE 3.6''' |
|- | |- | ||
| width="50%" | Support utilization and range resolvers | | width="50%" | Support utilization and range resolvers | ||
| Line 30: | Line 30: | ||
|- | |- | ||
| Delay, range, utilization resolvers are the default resolvers | | Delay, range, utilization resolvers are the default resolvers | ||
| - | | | + | | Load-balancing is used as the last resolver and cannot be disabled. Resolver range and utilization removed. |
|- | |- | ||
| Do random resolver for all qualified exits that satisfy the configured criteria | | Do random resolver for all qualified exits that satisfy the configured criteria | ||
Revision as of 06:50, 21 September 2012
- 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.
Navigation
IOS 15.2(3)T and IOS-XE 3.6
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 / XE 3.6 |
| Support utilization and range resolvers | Remove utilization and range resolvers |
| Delay, range, utilization resolvers are the default resolvers | Load-balancing is used as the last resolver and cannot be disabled. Resolver range and utilization removed. |
| 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. |
