The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This feature roadmap lists the Cisco IOS XE features documented in the Cisco IOS XE Performance Routing Configuration Guide and maps them to the documents in which they appear.
Find the feature name you are searching for and click the URL in the "Where Documented" column to access the document containing that feature.
Note Performance Routing (PfR) is an extension of the Optimized Edge Routing (OER) technology and many of the commands and command modes still use the OER naming conventions. All of the original OER features are incorporated into the Performance Routing technology and are still listed here under the original feature name.
Note In Cisco IOS XE Release 3.1S and later releases, only border router functionality is supported. PfR syntax was also introduced in Cisco IOS XE Release 3.1S. If you are running Cisco IOS XE Release 2.6.1 with the Optimized Edge Routing (OER) syntax, you need to consult the Cisco IOS XE Release 2 section below to help you locate all the relevant documentation.
Feature and Release Support
Table 1 lists Cisco IOS Performance Routing feature support for the Cisco IOS XE software release train:
Use Cisco Feature Navigator to find information about platform support and Cisco IOS XE software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note Table 1 lists only the Cisco IOS XE software release that introduced support for a given feature in a given Cisco IOS XE software release. Unless noted otherwise, subsequent releases of that Cisco IOS XE software release train also support that feature.
Table 1 lists the most recent XE release first and the features in alphabetical order within the release.
|
|
|
|
---|---|---|---|
|
|||
XE 3.1S |
OER Active Probe Source Address |
This feature introduced the capability to configure a specific exit interface on the border router as the source for active probes. |
•"Understanding Performance Routing" |
XE 3.1S |
OER Application-Aware Routing: PBR |
This feature introduced the capability to optimize IP traffic based on the type of application that is carried by the monitored prefix. Independent policy configuration is applied to the subset (application) of traffic. |
•"Understanding Performance Routing" |
XE 3.1S |
OER - Application Aware Routing with Static Application Mapping |
This feature introduces the ability to configure standard applications using just one keyword. In Cisco IOS Release 12.4(9)T, and prior releases, the definition of application traffic involves some awkward configuration. This feature also introduces a learn list configuration mode that allows PfR policies to be applied to traffic classes profiled in a learn list. Different policies can be applied to each learn list. New traffic-class and match traffic-class commands are introduced to simplify the configuration of traffic classes that PfR can automatically learn, or that can be manually configured. |
|
XE 3.1S |
OER BGP Inbound Optimization |
This feature introduced support for best entrance selection for traffic that originates from prefixes outside an autonomous system destined for prefixes inside the autonomous system. External BGP (eBGP) advertisements from an autonomous system to another autonomous system (for example, an Internet service provider) can influence the entrance path for traffic entering the network. PfR uses eBGP advertisements to manipulate the best entrance selection. Note On Cisco ASR 1000 series aggregation services routers in Cisco IOS XE Release 2.6.1, the maximum number of internal prefixes that can be learned during a monitoring period is 30. |
|
XE 3.1S |
OER Border Router Only Functionality |
Performance Routing (PfR) introduced support for border router (BR) only functionality on Cisco ASR 1000 series aggregation services routers in Cisco IOS XE Release 2.6.1. On software images that support the border router only functionality, no master controller configuration is available. The master controller that communicates with the border router in this situation must be a router running Cisco IOS Release 15.0(1)M, or a later 15.0M release. In contrast to Border Router Only Functionality on other platforms, Cisco ASR 1000 series routers can provide full border router passive monitoring functionality as well as active monitoring capability. |
|
XE 3.1S |
OER DSCP Monitoring |
This feature introduced automatic learning of traffic classes based on protocol, port numbers, and DSCP value. Traffic classes can be defined by a combination of keys comprising of protocol, port numbers, and DSCP values, with the ability to filter out traffic that is not required, and the ability to aggregate the traffic in which you are interested. Information such as protocol, port number, and DSCP information is now sent to the master controller database in addition to the prefix information. The new functionality allows PfR to both actively and passively monitor application traffic. |
•"Understanding Performance Routing" |
XE 3.1S |
OER Support for Cost-Based Optimization and Traceroute Reporting |
This feature introduced the capability to configure exit link policies based on the ISP billing cost. This feature also introduces the capability to configure traceroute probes to determine prefix characteristics on a hop-by-hop basis. |
•"Configuring Performance Routing cost Policies" |
XE 3.1S |
OER Support for Policy-Rules Configuration |
This feature introduces the capability to select a PfR map and apply the configuration under PfR master controller configuration mode, providing an improved method to switch between predefined PfR maps. |
•"Understanding Performance Routing" |
XE 3.1S |
OER Voice Traffic Optimization |
This feature introduced support for outbound optimization of voice traffic based on the voice metrics, jitter and Mean Opinion Score (MOS). Jitter and MOS are important quantitative quality metrics for voice traffic and these voice metrics are measured using PfR active probes. |
|
XE 3.1S |
Optimized Edge Routing (OER) |
PfR provides automatic route optimization and load distribution for multiple connections between networks. PfR is an integrated Cisco IOS solution that allows you to monitor IP traffic flows and then define policies and rules based on prefix performance, link load distribution, link bandwidth monetary cost, and traffic type. PfR provides active and passive monitoring systems, dynamic failure detection, and automatic path correction. Deploying PfR enables intelligent load distribution and optimal route selection in an enterprise network. In Cisco IOS XE Release 2.6.1, PfR support for border router (BR) only functionality on Cisco ASR 1000 series aggregation services routers was introduced. |
•"Configuring Basic Performance Routing" •"Understanding Performance Routing" |
XE 3.1S |
Performance Routing - Application Interface |
This feature introduces support for a PfR application interface. The application interface defines the mode of communication and messaging between applications and the network for the purpose of optimizing the traffic associated with the applications. A provider must be registered with a PfR master controller before the application can interface with PfR. Host devices in the provider network running an application that communicates with PfR using the application interface must also be configured at a PfR master controller with an IP address and key chain password. |
|
XE 3.1S |
PfR EIGRP mGRE DMVPN Hub-and-Spoke Support |
The PfR EIGRP mGRE DMVPN Hub-and-Spoke Support feature introduced PfR route control capabilities based on EIGRP by performing a route parent check on the EIGRP database. Support was also added for multicast Generic Routing Encapsulation (mGRE) Dynamic Multipoint Virtual Private Network (DMVPN) deployments that follow a hub- and-spoke network design. |
"Using Performance Routing to Control EIGRP Routes with mGRE DMVPN Hub-and-Spoke Support" |
XE 3.1S |
PfR - Protocol Independent Route Optimization (PIRO) |
PIRO introduced the ability of PfR to search for a parent route—an exact matching route, or a less specific route—in any IP Routing Information Base (RIB), allowing PfR to be deployed in any IP-routed environment including Interior Gateway Protocols (IGPs) such as OSPF and IS-IS. |
"Performance Routing - Protocol Independent Route Optimization (PIRO)" |
XE 3.1S |
Port and Protocol Based Prefix Learning |
This feature introduced the capability to configure a master controller to learn prefixes based on the protocol type and the TCP or UDP port number. |
•"Understanding Performance Routing" |
XE 3.1S |
VPN IPsec/GRE Tunnel Optimization |
This module documents a PfR solution that describes how to configure IP security (IPsec)/Generic Routing Encapsulation (GRE) tunnel interfaces as PfR-managed exit links. Only network-based IPsec VPNs are supported. |
"Configuring VPN IPsec/GRE Tunnel Interfaces As PfR-Managed Exit Links" |
|
|||
XE 2.6.1 |
OER Active Probe Source Address |
This feature introduced the capability to configure a specific exit interface on the border router as the source for active probes. |
•"Understanding Performance Routing" |
XE 2.6.1 |
OER Application-Aware Routing: PBR |
This feature introduced the capability to optimize IP traffic based on the type of application that is carried by the monitored prefix. Independent policy configuration is applied to the subset (application) of traffic. |
•"Understanding Performance Routing" |
XE 2.6.1 |
OER - Application Aware Routing with Static Application Mapping |
This feature introduces the ability to configure standard applications using just one keyword. In Cisco IOS Release 12.4(9)T, and prior releases, the definition of application traffic involves some awkward configuration. This feature also introduces a learn list configuration mode that allows PfR policies to be applied to traffic classes profiled in a learn list. Different policies can be applied to each learn list. New traffic-class and match traffic-class commands are introduced to simplify the configuration of traffic classes that PfR can automatically learn, or that can be manually configured. |
|
XE 2.6.1 |
OER BGP Inbound Optimization |
This feature introduced support for best entrance selection for traffic that originates from prefixes outside an autonomous system destined for prefixes inside the autonomous system. External BGP (eBGP) advertisements from an autonomous system to another autonomous system (for example, an Internet service provider) can influence the entrance path for traffic entering the network. PfR uses eBGP advertisements to manipulate the best entrance selection. Note On Cisco ASR 1000 series aggregation services routers in Cisco IOS XE Release 2.6.1, the maximum number of internal prefixes that can be learned during a monitoring period is 30. |
|
XE 2.6.1 |
OER Border Router Only Functionality |
Performance Routing (PfR) introduced support for border router (BR) only functionality on Cisco ASR 1000 series aggregation services routers in Cisco IOS XE Release 2.6.1. On software images that support the border router only functionality, no master controller configuration is available. The master controller that communicates with the border router in this situation must be a router running Cisco IOS Release 15.0(1)M, or a later 15.0M release. In contrast to Border Router Only Functionality on other platforms, Cisco ASR 1000 series routers can provide full border router passive monitoring functionality as well as active monitoring capability. |
|
XE 2.6.1 |
OER DSCP Monitoring |
This feature introduced automatic learning of traffic classes based on protocol, port numbers, and DSCP value. Traffic classes can be defined by a combination of keys comprising of protocol, port numbers, and DSCP values, with the ability to filter out traffic that is not required, and the ability to aggregate the traffic in which you are interested. Information such as protocol, port number, and DSCP information is now sent to the master controller database in addition to the prefix information. The new functionality allows PfR to both actively and passively monitor application traffic. |
•"Understanding Performance Routing" |
XE 2.6.1 |
OER Support for Cost-Based Optimization and Traceroute Reporting |
This feature introduced the capability to configure exit link policies based on the ISP billing cost. This feature also introduces the capability to configure traceroute probes to determine prefix characteristics on a hop-by-hop basis. |
•"Configuring Performance Routing cost Policies" |
XE 2.6.1 |
OER Support for Policy-Rules Configuration |
This feature introduces the capability to select a PfR map and apply the configuration under PfR master controller configuration mode, providing an improved method to switch between predefined PfR maps. |
•"Understanding Performance Routing" |
XE 2.6.1 |
OER Voice Traffic Optimization |
This feature introduced support for outbound optimization of voice traffic based on the voice metrics, jitter and Mean Opinion Score (MOS). Jitter and MOS are important quantitative quality metrics for voice traffic and these voice metrics are measured using PfR active probes. |
|
XE 2.6.1 |
Optimized Edge Routing (OER) |
PfR provides automatic route optimization and load distribution for multiple connections between networks. PfR is an integrated Cisco IOS solution that allows you to monitor IP traffic flows and then define policies and rules based on prefix performance, link load distribution, link bandwidth monetary cost, and traffic type. PfR provides active and passive monitoring systems, dynamic failure detection, and automatic path correction. Deploying PfR enables intelligent load distribution and optimal route selection in an enterprise network. In Cisco IOS XE Release 2.6.1, PfR support for border router (BR) only functionality on Cisco ASR 1000 series aggregation services routers was introduced. |
•"Configuring Basic Performance Routing" •"Understanding Performance Routing" |
XE 2.6.1 |
Performance Routing - Application Interface |
This feature introduces support for a PfR application interface. The application interface defines the mode of communication and messaging between applications and the network for the purpose of optimizing the traffic associated with the applications. A provider must be registered with a PfR master controller before the application can interface with PfR. Host devices in the provider network running an application that communicates with PfR using the application interface must also be configured at a PfR master controller with an IP address and key chain password. |
|
XE 2.6.1 |
PfR EIGRP mGRE DMVPN Hub-and-Spoke Support |
The PfR EIGRP mGRE DMVPN Hub-and-Spoke Support feature introduced PfR route control capabilities based on EIGRP by performing a route parent check on the EIGRP database. Support was also added for multicast Generic Routing Encapsulation (mGRE) Dynamic Multipoint Virtual Private Network (DMVPN) deployments that follow a hub- and-spoke network design. |
"Using Performance Routing to Control EIGRP Routes with mGRE DMVPN Hub-and-Spoke Support" |
XE 2.6.1 |
PfR - Protocol Independent Route Optimization (PIRO) |
PIRO introduced the ability of PfR to search for a parent route—an exact matching route, or a less specific route—in any IP Routing Information Base (RIB), allowing PfR to be deployed in any IP-routed environment including Interior Gateway Protocols (IGPs) such as OSPF and IS-IS. |
"Performance Routing - Protocol Independent Route Optimization (PIRO)" |
XE 2.6.1 |
Port and Protocol Based Prefix Learning |
This feature introduced the capability to configure a master controller to learn prefixes based on the protocol type and the TCP or UDP port number. |
•"Understanding Performance Routing" |
XE 2.6.1 |
VPN IPsec/GRE Tunnel Optimization |
This module documents a PfR solution that describes how to configure IP security (IPsec)/Generic Routing Encapsulation (GRE) tunnel interfaces as PfR-managed exit links. Only network-based IPsec VPNs are supported. |
"Configuring VPN IPsec/GRE Tunnel Interfaces As PfR-Managed Exit Links" |