Cisco Performance routing (PfR), previously optimised edge routing provides enhanced routing for traffic based on a defined policy.
Cisco PfR enables controls that can dynamically route traffic based upon traffic load, delay and jitter on links where under normal circumstances traditional routing protocols will continue to route traffic based on the best metric. Sometimes with high loads on the link this is not always the best path.
With Performnace Routing, traffic and even traffic classes can be routed based upon current conditions on the network providing the optimal path for traffic.
Cisco PfR was origianlly engineered for outbound traffic but since 12.4T it will also influence inbound traffic.
To run a stable version of PfR it is recommened to use a 15 train version of IOS.
PfR Core Components
The core components of PfR are:
Master Controller – this collects the statistical information and uploads policy decisions.
Border Routers – these routers control the traffic in and out of the external link
A Cisco router can function as a Master Controller and a Border router together.
For an introduction to PfR Cisco have a very informative video
As Performance routing is now on the CCIE R&S V4 blueprint and forms part of the Lab Exam it is a topic that CCIE students need to master.
For all the technical information on Performance Routing go to
There is also a less technical introduction to PfR here
This blog post forms an introduction to Cisco Performance Routing (PfR) and in future posts I will go through the configuration of a simple and complex routing example.
This is much better explained over at blog.ine.com
More CCIE Lab exam updates on my CCIE Blog
cisco performance routing ip routing software
cisco performance routing products
content performance routing cisco
cisco performance routing oer
cisco performance optimized edge routing