-
This documentation has been moved
-
Cisco IOS Performance Routing Roadmap
-
Configuring Basic Performance Routing
-
Understanding Performance Routing
-
Configuring Advanced Performance Routing
-
Performance Routing Application Interface
-
BGP Inbound Optimization Using Performance Routing
-
Configuring Performance Routing Cost Policies
-
Using Performance Routing to Control EIGRP Routes with mGRE DMVPN Hub-and-Spoke Support
-
Configuring VPN IPsec/GRE Tunnel Interfaces As PfR-Managed Exit Links
-
Performance Routing Link Groups
-
Performance Routing with NAT
-
Performance Routing with NBAR/CCE Application Recognition
-
Performance Routing - Protocol Independent Route Optimization (PIRO)
-
Static Application Mapping Using Performance Routing
-
Performance Routing Traceroute Reporting
-
PfR Voice Traffic Optimization Using Active Probes
-
Feedback
Table Of Contents
Static Application Mapping Using Performance Routing
Prerequisites for Static Application Mapping Using Performance Routing
Information About Static Application Mapping Using Performance Routing
Performance Routing Traffic Class Profiling
Static Application Mapping Using PfR
How to Configure Static Application Mapping Using Performance Routing
Defining a Learn List to Automatically Learn Traffic Classes Using Static Application Mapping
Manually Selecting Traffic Classes Using Static Application Mapping
Displaying and Resetting Traffic Class and Learn List Information
Configuration Examples for Static Application Mapping Using Performance Routing
Example: Defining a Learn List for Automatically Learned Prefix-Based Traffic Classes
Example: Manually Selecting Traffic Classes Using Static Application Mapping
Example: Manually Selecting Prefix-Based Traffic Classes Using a Prefix List
Example: Manually Selecting Application Traffic Classes Using an Access List
Feature Information for Static Application Mapping Using Performance Routing
Static Application Mapping Using Performance Routing
First Published: March 19, 2010Last Updated: July 21, 2010The OER - Application Aware Routing with Static Application Mapping feature introduces the ability to configure standard applications using just one keyword to simplify the configuration of traffic classes that PfR can automatically learn, or that can be manually configured. This feature also introduces a learn list configuration mode that allows Performance Routing (PfR) policies to be applied to traffic classes profiled in a learn list. Different policies can be applied to each learn list.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the "Feature Information for Static Application Mapping Using Performance Routing" section.
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.
Contents
•
Prerequisites for Static Application Mapping Using Performance Routing
•
•
•
•
Prerequisites for Static Application Mapping Using Performance Routing
Cisco Express Forwarding (CEF) must be enabled on all participating devices. No other switching path is supported, even if otherwise supported by Policy-Based Routing (PBR).
Information About Static Application Mapping Using Performance Routing
•
•
•
Performance Routing Traffic Class Profiling
Before optimizing traffic, Performance Routing (PfR) has to determine the traffic classes from the traffic flowing through the border routers. To optimize traffic routing, subsets of the total traffic must be identified, and these traffic subsets are named traffic classes. The list of traffic classes entries is named a Monitored Traffic Class (MTC) list. The entries in the MTC list can be profiled either by automatically learning the traffic flowing through the device or by manually configuring the traffic classes. Learned and configured traffic classes can both exist in the MTC list at the same time. Both the learn mechanism and the configure mechanism for traffic classes are implemented during the PfR profile phase. The overall structure of the PfR traffic class profile process and its component parts can be seen in Figure 1.
Figure 1 PfR Traffic Class Profiling Process
PfR can automatically learn the traffic classes while monitoring the traffic flow through border routers using the embedded NetFlow capability. Although the goal is to optimize a subset of the traffic, you may not know all the exact parameters of this traffic and PfR provides a method to automatically learn the traffic and create traffic classes by populating the MTC list. Within the automatic traffic class learning process there are three components:
•
•
•
PfR can be manually configured to create traffic classes for monitoring and subsequent optimizing. Automatic learning generally uses a default prefix length of /24 but manual configuration allows exact prefixes to be defined. Within the manual traffic class configuration process there are two components:
•
•
The ultimate objective of the profile phase is to select a subset of traffic flowing through the network. This subset of traffic—the traffic classes in the MTC list—represents the classes of traffic that need to be routed based on the best performance path available.
More details about each of the traffic class profiling components in Figure 1 are contained in the "Understanding Performance Routing" module.
Static Application Mapping Using PfR
The OER - Application Aware Routing with Static Application Mapping feature introduced the ability to define an application using a keyword to simplify the configuration of application-based traffic classes. PfR uses well-known applications with fixed ports, and more than one application may be configured at the same time. The list of static applications available for profiling Performance Routing traffic classes is constantly evolving. Use the traffic-class application ? command to determine if a static application is available for use with Performance Routing.
Table 1 displays a partial list of static applications that can be configured with Performance Routing. The applications are considered static because they are defined with fixed port and protocols as shown in the table. Configuration is performed on a master controller under learn list configuration mode.
The master controller is configured to learn the top prefixes based on highest outbound throughput or delay for the filtered traffic, and the resulting traffic classes are added to the PfR application database to be passively and actively monitored.
For more details on configuring application-based traffic classes using static application mapping, see the "Defining a Learn List to Automatically Learn Traffic Classes Using Static Application Mapping" section.
Learn List Configuration Mode
The Learn List feature introduced a new configuration mode named learn list. Learn lists are a way to categorize learned traffic classes. In each learn list, different criteria including prefixes, application definitions, filters, and aggregation parameters for learning traffic classes can be configured. A traffic class is automatically learned by PfR based on each learn list criteria, and each learn list is configured with a sequence number. The sequence number determines the order in which learn list criteria are applied. Learn lists allow different PfR policies to be applied to each learn list; in previous releases, the traffic classes could not be divided, and an PfR policy was applied to all the learned traffic classes.
Four types of traffic classes—to be automatically learned or manually configured—can be profiled:
•
•
•
•
The traffic-class commands are used under learn list mode to simplify the automatic learning of traffic classes. Only one type of traffic-class command can be specified per learn list, and the throughput (PfR) and delay (PfR) commands are also mutually exclusive within a learn list.
The match traffic-class commands are used under PfR map configuration mode to simplify the manual configuration of traffic classes. Only one type of match traffic-class command can be specified per PfR map.
Note
How to Configure Static Application Mapping Using Performance Routing
•
•
•
Defining a Learn List to Automatically Learn Traffic Classes Using Static Application Mapping
Perform this task at the master controller to define a learn list using static application mapping. Within a learn list, a keyword that represents an application can be used to identify specific application traffic classes. The defined learn list will contain traffic classes to be automatically learned by PfR using the static application mapping. The resulting traffic classes can be filtered by a prefix list, if required.
In this task, a learn list is configured to create a traffic class using static application mapping keywords. Learn lists allow different PfR policies to be applied to each learn list. The resulting prefixes are aggregated to a prefix length of 24. A prefix list is applied to the traffic class to permit traffic from the 10.0.0.0/8 prefix. The master controller is configured to learn the top prefixes based on highest outbound throughput for the filtered traffic, and the resulting traffic class is added to the PfR application database.
The learn list is referenced in a PfR policy using a PfR map and activated using the policy-rules (PfR) command.
To display information about the configured learn lists and the traffic classes learned by PfR, use the "Displaying and Resetting Traffic Class and Learn List Information" section.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
DETAILED STEPS
Step 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Step 2
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 3
ip prefix-list list-name [seq seq-value] {deny network/length | permit network/length} [le le-value]
Example:Router(config)# ip prefix-list INCLUDE_10_NET permit 10.0.0.0/8
Creates an IP prefix list to filter prefixes for learning.
•
•
Step 4
pfr master
Example:Router(config)# pfr master
Enters PfR master controller configuration mode to configure a Cisco router as a master controller and to configure master controller policy and timer settings.
Step 5
policy-rules map-name
Example:Router(config-pfr-mc)# policy-rules LL_REMOTE_MAP
Selects a PfR map and applies the configuration under PfR master controller configuration mode.
•
•
Step 6
learn
Example:Router(config-pfr-mc)# learn
Enters PfR Top Talker and Top Delay learning configuration mode to automatically learn traffic classes.
Step 7
list seq number refname refname
Example:Router(config-pfr-mc-learn)# list seq 10 refname LEARN_REMOTE_LOGIN_TC
Creates an PfR learn list and enters learn list configuration mode.
•
•
•
Step 8
traffic-class application application-name... [filter prefix-list-name]
Example:Router(config-pfr-mc-learn-list)# traffic-class application telnet ssh
Defines an PfR traffic class using a pre-defined static application.
•
•
Step 9
aggregation-type {bgp | non-bgp | prefix-length} prefix-mask
Example:Router(config-pfr-mc-learn-list)# aggregation-type prefix-length 24
(Optional) Configures a master controller to aggregate learned prefixes based on traffic flow type.
•
•
•
•
•
Step 10
throughput
Example:Router(config-pfr-mc-learn-list)# throughput
Configures the master controller to learn the top prefixes based on the highest outbound throughput.
•
•
Step 11
exit
Example:Router(config-pfr-mc-learn-list)# exit
Exits learn list configuration mode, and returns to PfR Top Talker and Top Delay learning configuration mode.
Step 12
Repeat Step 7 to Step 11 to configure additional learn lists
—
Step 13
exit
Example:Router(config-pfr-mc-learn)# exit
Exits PfR Top Talker and Top Delay learn configuration mode, and returns to PfR master controller configuration mode.
Step 14
Repeat Step 13 to return to global configuration mode.
—
Step 15
pfr-map map-name sequence-number
Example:Router(config)# pfr-map LL_REMOTE_MAP 10
Enters PfR map configuration mode to configure a PfR map.
•
•
Step 16
match pfr learn list refname
Example:Router(config-oer-map)# match pfr learn list LEARN_REMOTE_LOGIN_TC
Creates a match clause entry in a PfR map to match PfR learned prefixes.
•
Note
Step 17
end
Example:Router(config-oer-map)# end
(Optional) Exits OER map configuration mode and returns to privileged EXEC mode.
Example:
In this example, two learn lists are configured to identify remote login traffic and file transfer traffic. The remote login traffic class is configured using keywords representing Telnet and Secure Shell (SSH) traffic, and the resulting prefixes are aggregated to a prefix length of 24. The file transfer traffic class is configured using a keyword that represents FTP and is also aggregated to a prefix length of 24. A prefix list is applied to the file transfer traffic class to permit traffic from the 10.0.0.0/8 prefix. The master controller is configured to learn the top prefixes based on highest outbound throughput for the filtered traffic, and the resulting traffic classes are added to the PfR application database. PfR maps are configured to match the learn lists and the File Transfer traffic class is activated using the policy-rules (PfR) command.
ip prefix-list INCLUDE_10_NET 10.0.0.0/8pfr masterpolicy-rules LL_FILE_MAPlearnlist seq 10 refname LEARN_REMOTE_LOGIN_TCtraffic-class application telnet sshaggregation-type prefix-length 24throughputexitlist seq 20 refname LEARN_FILE_TRANSFER_TCtraffic-class application ftp filter INCLUDE_10_NETaggregation-type prefix-length 24throughputexitexitexitpfr-map LL_REMOTE_MAP 10match pfr learn list LEARN_REMOTE_LOGIN_TCexitpfr-map LL_FILE_MAP 20match pfr learn list LEARN_FILE_TRANSFER_TCendManually Selecting Traffic Classes Using Static Application Mapping
Perform this task to manually select traffic classes using static application mapping. Use this task when you know the destination prefixes and the applications that you want to select for the traffic classes. In this task, an IP prefix list is created to define the destination prefixes, and static applications are defined using the match traffic-class application (PfR) command. Using a PfR map, each prefix is matched with each application to create the traffic classes.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
DETAILED STEPS
Step 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Step 2
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 3
ip prefix-list list-name [seq seq-value] {deny network/length | permit network/length} [le le-value]
Example:Router(config)# ip prefix-list LIST1 permit 10.1.1.0/24
Creates a prefix list to specify destination prefix-based traffic classes.
•
Step 4
Repeat Step 3 for more prefix list entries, as required.
—
Step 5
pfr-map map-name sequence-number
Example:Router(config)# pfr-map APPLICATION_MAP 10
Enters PfR map configuration mode to configure a PfR map.
•
•
•
Step 6
match traffic-class application application-name prefix-list prefix-list-name
Example:Router(config-pfr-map)# traffic-class application telnet ssh prefix-list LIST1
Manually configures one or more static applications as match criteria against a prefix list to create traffic classes using a PfR map.
•
•
Step 7
end
Example:Router(config-pfr-map)# end
(Optional) Exits PfR map configuration mode and returns to privileged EXEC mode.
Displaying and Resetting Traffic Class and Learn List Information
Perform this task to display traffic class and learn list information and optionally, to reset some traffic class information. These commands can be entered on a master controller after learn lists are configured and traffic classes are automatically learned, or when traffic classes are manually configured using a PfR map. The commands can be entered in any order and all the commands are optional.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Step 1
Enables privileged EXEC mode. Enter your password if prompted.
Router> enableStep 2
This command is used to display information about traffic classes learned or manually configured under PfR learn list configuration mode.
Router# show pfr master traffic-classOER Prefix Statistics:Pas - Passive, Act - Active, S - Short term, L - Long term, Dly - Delay (ms),P - Percentage below threshold, Jit - Jitter (ms),MOS - Mean Opinion ScoreLos - Packet Loss (packets-per-million), Un - Unreachable (flows-per-million),E - Egress, I - Ingress, Bw - Bandwidth (kbps), N - Not applicableU - unknown, * - uncontrolled, + - control more specific, @ - active probe all# - Prefix monitor mode is Special, & - Blackholed Prefix% - Force Next-Hop, ^ - Prefix is deniedDstPrefix Appl_ID Dscp Prot SrcPort DstPort SrcPrefixFlags State Time CurrBR CurrI/F ProtocolPasSDly PasLDly PasSUn PasLUn PasSLos PasLLos EBw IBwActSDly ActLDly ActSUn ActLUn ActSJit ActPMOS--------------------------------------------------------------------------------10.1.1.0/24 N defa N N N N# OOPOLICY 32 10.11.1.3 Et1/0 BGPN N N N N N N IBwN130 134 0 0 N NStep 3
This command is used to display one or all of the configured PfR learn lists. In this example, the information about two learn lists is displayed.
Router# show pfr master learn listLearn-List LIST1 10Configuration:Application: ftpAggregation-type: bgpLearn type: thruputPolicies assigned: 8 10Stats:Application Count: 0Application Learned:Learn-List LIST2 20Configuration:Application: telnetAggregation-type: prefix-length 24Learn type: thruputPolicies assigned: 5 20Stats:Application Count: 2Application Learned:Appl Prefix 10.1.5.0/24 telnetAppl Prefix 10.1.5.16/28 telnetStep 4
This command is used to clear PfR controlled traffic classes from the master controller database. The following example clears traffic classes defined by the Telnet application and the 10.1.1.0/24 prefix:
Router# clear pfr master traffic-class application telnet 10.1.1.0/24
Configuration Examples for Static Application Mapping Using Performance Routing
•
•
•
•
Example: Defining a Learn List to Automatically Learn Traffic Classes Using Static Application Mapping
The following example defines application traffic classes using static application mapping. In this example, the following two PfR learn lists are defined:
•
•
The goal is to optimize the remote login traffic using one policy (POLICY_REMOTE), and to optimize the file transfer traffic using a different policy (POLICY_FILE). This task configures traffic class learning based on the highest delay. The policy-rules (PfR) command activates the remote traffic class learn list. To activate the file transfer traffic class, replace the POLICY_REMOTE map name with the POLICY_FILE map name using the policy-rules (PfR) command.
ip prefix-list INCLUDE_10_NET 10.0.0.0/8pfr masterpolicy-rules POLICY_REMOTE 10learnlist seq 10 refname LEARN_REMOTE_LOGIN_TCtraffic-class application telnet sshaggregation-type prefix-length 24delayexitlist seq 20 refname LEARN_FILE_TRANSFER_TCtraffic-class application ftp filter INCLUDE_10_NETaggregation-type prefix-length 24delayexitexitpfr-map POLICY_REMOTE 10match pfr learn list LEARN_REMOTE_LOGIN_TCexitpfr-map POLICY_FILE 20match pfr learn list LEARN_FILE_TRANSFER_TCendExample: Defining a Learn List for Automatically Learned Prefix-Based Traffic Classes
The following example configured on the master controller, defines a learn list that will contain traffic classes that are automatically learned based only on a prefix list. In this example, there are three branch offices and the goal is to optimize all the traffic going to branch offices A and B using one policy (Policy1), and to optimize traffic going to branch office C using a different policy (Policy2).
Branch A is defined as any prefix that matches 10.1.0.0./16, Branch B is defined as any prefix that matches 10.2.0.0./16, and Branch C is defined as any prefix that matches 10.3.0.0./16.
This task configures prefix learning based on the highest outbound throughput. The policy-rules (PfR) command activates the traffic class learn list configured for branch offices A and B.
ip prefix-list BRANCH_A_B permit seq 10 10.1.0.0/16ip prefix-list BRANCH_A_B permit seq 20 10.2.0.0/16ip prefix-list BRANCH_C permit seq 30 10.3.0.0/16pfr masterpolicy-rules POLICY1learnlist seq 10 refname LEARN_BRANCH_A_Btraffic-class prefix-list BRANCH_A_Bthroughputexitlist seq 20 refname LEARN_BRANCH_Ctraffic-class prefix-list BRANCH_Cthroughputexitexitexitpfr-map POLICY1 10match pfr learn list LEARN_BRANCH_A_Bexitpfr-map POLICY2 10match pfr learn list LEARN_BRANCH_CendExample: Defining a Learn List for Automatically Learned Application Traffic Classes Using an Access List
The following example creates an access list that defines custom application traffic classes. In this example, the custom application consists of four criteria:
•
•
•
•
The goal is to optimize the custom application traffic using a learn list that is referenced in a PfR policy named POLICY_CUSTOM_APP. This task configures traffic class learning based on the highest outbound throughput. The policy-rules (PfR) command activates the custom application traffic class learn list.
ip access-list extended USER_DEFINED_TCpermit tcp any any 500permit tcp any any range 700 750permit udp any eq 400 anypermit ip any any dscp efexitpfr masterpolicy-rules POLICY_CUSTOM_APPlearnlist seq 10 refname CUSTOM_APPLICATION_TCtraffic-class access-list USER_DEFINED_TCaggregation-type prefix-length 24throughputexitexitexitpfr-map POLICY_CUSTOM_APP 10match pfr learn list CUSTOM_APPLICATION_TCendExample: Manually Selecting Traffic Classes Using Static Application Mapping
The following example starting in global configuration mode, configures a PfR map to include application traffic predefined as telnet or Secure Shell and destined to prefixes in the 10.1.1.0/24 network, 10.1.2.0/24 network, and 172.16.1.0/24 network.
ip prefix-list LIST1 permit 10.1.1.0/24ip prefix-list LIST1 permit 10.1.2.0/24ip prefix-list LIST1 permit 172.16.1.0/24pfr-map PREFIXES 10match traffic-class application telnet ssh prefix-list LIST1endExample: Manually Selecting Prefix-Based Traffic Classes Using a Prefix List
The following example configured on the master controller, manually selects traffic classes based only on destination prefixes. Use this task when you know the destination prefixes that you want to select for the traffic classes. An IP prefix list is created to define the destination prefixes and using a PfR map, the traffic classes are profiled.
ip prefix-list PREFIX_TC permit 10.1.1.0/24ip prefix-list PREFIX_TC permit 10.1.2.0/24ip prefix-list PREFIX_TC permit 172.16.1.0/24pfr-map PREFIX_MAP 10match traffic-class prefix-list PREFIX_TCendExample: Manually Selecting Application Traffic Classes Using an Access List
The following example configured on the master controller, manually selects traffic classes using an access list. Each access list entry is a traffic class that must include a destination prefix and may include other optional parameters.
ip access-list extended ACCESS_TCpermit tcp any 10.1.1.0 0.0.0.255 eq 500permit tcp any 172.17.1.0 0.0.255.255 eq 500permit tcp any 172.17.1.0 0.0.255.255 range 700 750permit tcp 192.168.1.1 0.0.0.0 10.1.2.0 0.0.0.255 eq 800any any dscp efexitpfr-map ACCESS_MAP 10match traffic-class access-list ACCESS_TCWhere To Go Next
For information about other Performance Routing features or general conceptual material, see the documents in the "Related Documents" section.
Additional References
Related Documents
Technical Assistance
Feature Information for Static Application Mapping Using Performance Routing
Table 2 lists the release history of the feature.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note
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)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
© 2010 Cisco Systems, Inc. All rights reserved.
