This documentation has been moved
Cisco IOS Performance Routing Roadmap
Downloads: This chapterpdf (PDF - 126.0KB) The complete bookPDF (PDF - 2.05MB) | Feedback

Cisco IOS Performance Routing Feature Roadmap

Table Of Contents

Cisco IOS Performance Routing Feature Roadmap


Cisco IOS Performance Routing Feature Roadmap


First Published: March 19, 2010
Last Updated: July 21, 2010

This feature roadmap lists the Cisco IOS features documented in the Cisco IOS Performance Routing configuration guide and maps them to the documents in which they appear. Performance Routing is an extension of the Optimized Edge Routing (OER) technology. All of the original OER features are incorporated into the Performance Routing technology and are still listed here under the original feature name and original release train. Find the feature name you are searching for and click on the URL in the "Where Documented" column to access the document containing that feature.


Note The PfR configuration modules refer to the PfR syntax introduced in Cisco IOS Release 15.1(2)T. If you are running Cisco IOS Release 15.1(1)T, or an earlier release, or any 12.2SR or 12.2SX image, you need to consult the "Cisco IOS Optimized Edge Feature Roadmap" module to help you locate all the Optimized Edge Routing documentation.


Feature and Release Support

Table 1 lists Cisco IOS Performance Routing (PfR) feature support for features introduced in the following Cisco IOS software release trains:

Cisco IOS Releases 12.3T, 12.4, and 12.4T

Cisco IOS Release 15.0

Use Cisco Feature Navigator to find information about platform support and Cisco 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 software release that introduced support for a given feature in a given Cisco IOS software release train. Unless noted otherwise, subsequent releases of that Cisco IOS software release train also support that feature.


Table 1 lists the most recent release of each software train first and the features in alphabetical order within the release.

Table 1 Supported Cisco IOS Performance Routing Features 

Release
Feature Name
Feature Description
Where Documented
Cisco IOS Releases 12.3T, 12.4, and 12.4T

12.4(24)T

PfR - Protocol Independent Route Optimization (PIRO)

PIRO introduced the ability of OER to search for a parent route—an exact matching route, or a less specific route—in any IP Routing Information Base (RIB), allowing OER 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)"

12.4(20)T

Performance Routing with NBAR/CCE Application Recognition

The Performance Routing with NBAR/CCE Application Recognition feature introduces the ability to profile an application-based traffic class using NBAR. Network-Based Application Recognition (NBAR) is a classification engine that recognizes and classifies a wide variety of protocols and applications, including web-based and other difficult-to-classify applications and protocols that use dynamic TCP/UDP port assignments. PfR uses NBAR to recognize and classify a protocol or application, and the resulting traffic classes are added to the PfR application database to be passively and actively monitored.

"Performance Routing with NBAR/CCE Application Recognition"

12.4(15)T

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 Optimized Edge Routing (OER) 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 OER can automatically learn, or that can be manually configured.

"Static Application Mapping Using Performance Routing"

12.4(15)T

Performance Routing - Application Interface

This feature introduces support for an OER 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 an OER master controller before the application can interface with OER. Host devices in the provider network running an application that communicates with OER using the application interface must also be configured at an OER master controller with an IP address and key chain password.

"Performance Routing Application Interface"

12.4(15)T

Performance Routing - Link Groups

This feature introduces the ability to define a group of exit links as a preferred set of links, or a fallback set of links for OER to use when optimizing traffic classes specified in an OER policy.

"Performance Routing Link Groups"

12.4(9)T

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. OER uses eBGP advertisements to manipulate the best entrance selection.

"BGP Inbound Optimization Using Performance Routing"

12.4(9)T

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 OER to both actively and passively monitor application traffic.

"Understanding Performance Routing"

"Configuring Advanced Performance Routing"

12.4(6)T

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 OER active probes.

"PfR Voice Traffic Optimization Using Active Probes"

12.4(2)T

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"

"Configuring Advanced Performance Routing"

12.4(2)T

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"

"Configuring Advanced Performance Routing"

12.3(14)T

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"

"Performance Routing Traceroute Reporting"

12.3(11)T

OER Support for Policy-Rules Configuration

This feature introduces the capability to select an OER map and apply the configuration under OER master controller configuration mode, providing an improved method to switch between predefined OER maps.

"Understanding Performance Routing"

"Configuring Advanced Performance Routing"

12.3(11)T

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"

12.3(11)T

VPN IPsec/GRE Tunnel Optimization

This module documents an OER solution that describes how to configure IP security (IPsec)/Generic Routing Encapsulation (GRE) tunnel interfaces as OER-managed exit links. Only network-based IPsec VPNs are supported.

"Configuring VPN IPsec/GRE Tunnel Interfaces As PfR-Managed Exit Links"

12.3(8)T

Optimized Edge Routing (OER)

OER provides automatic route optimization and load distribution for multiple connections between networks. OER 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. OER provides active and passive monitoring systems, dynamic failure detection, and automatic path correction. Deploying OER enables intelligent load distribution and optimal route selection in an enterprise network.

"Configuring Basic Performance Routing"

"Understanding Performance Routing"

"Configuring Advanced Performance Routing"

Cisco IOS Release 15.0

15.0(1)M

PfR EIGRP mGRE DMVPN Hub-and-Spoke Support

The PfR EIGRP mGRE DMVPN Hub-and-Spoke Support feature introduced the ability to inject routes into the EIGRP routing table allowing PfR to control prefixes and applications over EIGRP routes. This feature also adds support 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"



Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)