| We encourage [http://tools.cisco.com/RPF/register/register.do registered Cisco.com users] to contribute to this wiki to collaborate on Cisco product documentation. You do not need to log in to read the text. However, you must log in to edit the text. Select the "edit" tab to edit an article or select the "discussion" tab to submit questions or comments about documentation content.<br>

| We encourage [http://tools.cisco.com/RPF/register/register.do registered Cisco.com users] to contribute to this wiki to collaborate on Cisco product documentation. You do not need to log in to read the text. However, you must log in to edit the text. Select the "edit" tab to edit an article or select the "discussion" tab to submit questions or comments about documentation content.<br>

See [[DocWiki:Terms of use|Terms of Use]] and [[DocWiki:About|About DocWiki]] for more information about Cisco DocWiki

See [[DocWiki:Terms of use|Terms of Use]] and [[DocWiki:About|About DocWiki]] for more information about Cisco DocWiki

-

-

|-

-

| If you encounter the following scenarios, feel free to add to our initial list:

-

*You find a new, valid tip and would like to share it with other PfR users.

-

*You discover an easier solution/process/workaround to a specific problem.

|-

|-

Revision as of 07:47, 30 July 2010

Performance Routing

Welcome to Cisco Performance Routing DocWiki.

Performance Routing (PfR) is the general term used for features that take into account diverse WAN characteristics and make an informed-decision on the best path to reach a network or application, given multiple choices that may have varied performance characteristics. PfR by its nature takes into account the network performance, delay, loss, and link loading, where traditional routing protocols typically rely solely on cost (total bandwidth) once reachability, in that there is a neighbor relationship between routers, exists across a WAN link.

Note

We encourage registered Cisco.com users to contribute to this wiki to collaborate on Cisco product documentation. You do not need to log in to read the text. However, you must log in to edit the text. Select the "edit" tab to edit an article or select the "discussion" tab to submit questions or comments about documentation content.