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.

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.

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.

The following example defines application traffic classes using static application mapping. In this example, the following two PfR learn lists are defined:

• LEARN_REMOTE_LOGIN_TC--Remote login traffic represented by Telnet and SSH.
• LEARN_FILE_TRANSFER_TC--File transfer traffic represented by FTP and filtered by the 10.0.0.0/8 prefix.

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/8
pfr master
 policy-rules POLICY_REMOTE 10 
 learn 
 list seq 10 refname LEARN_REMOTE_LOGIN_TC
 traffic-class application telnet ssh
 aggregation-type prefix-length 24 
 delay
 exit
 list seq 20 refname LEARN_FILE_TRANSFER_TC
 traffic-class application ftp filter INCLUDE_10_NET
 aggregation-type prefix-length 24 
 delay
 exit
 exit
pfr-map POLICY_REMOTE 10
 match pfr learn list LEARN_REMOTE_LOGIN_TC
 exit
pfr-map POLICY_FILE 20
 match pfr learn list LEARN_FILE_TRANSFER_TC
 end

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/16
ip prefix-list BRANCH_A_B permit seq 20 10.2.0.0/16
ip prefix-list BRANCH_C permit seq 30 10.3.0.0/16
pfr master
 policy-rules POLICY1
 learn 
  list seq 10 refname LEARN_BRANCH_A_B 
   traffic-class prefix-list BRANCH_A_B
   throughput
   exit
  list seq 20 refname LEARN_BRANCH_C
   traffic-class prefix-list BRANCH_C
   throughput
   exit
  exit
 exit
pfr-map POLICY1 10
 match pfr learn list LEARN_BRANCH_A_B
 exit
pfr-map POLICY2 10
 match pfr learn list LEARN_BRANCH_C
 end

The following example creates an access list that defines custom application traffic classes. In this example, the custom application consists of four criteria:

• Any TCP traffic on destination port 500
• Any TCP traffic on ports in the range from 700 to 750
• Any UDP traffic on source port 400
• Any IP packet marked with a DSCP bit of ef

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_TC
 permit tcp any any 500
 permit tcp any any range 700 750
 permit udp any eq 400 any
 permit ip any any dscp ef 
 exit
pfr master
 policy-rules POLICY_CUSTOM_APP 
 learn 
  list seq 10 refname CUSTOM_APPLICATION_TC 
   traffic-class access-list USER_DEFINED_TC
   aggregation-type prefix-length 24 
   throughput
   exit 
  exit
 exit
pfr-map POLICY_CUSTOM_APP 10
 match pfr learn list CUSTOM_APPLICATION_TC
 end

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/24
ip prefix-list LIST1 permit 10.1.2.0/24
ip prefix-list LIST1 permit 172.16.1.0/24
pfr-map PREFIXES 10 
 match traffic-class application telnet ssh prefix-list LIST1 
 end 

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/24
ip prefix-list PREFIX_TC permit 10.1.2.0/24
ip prefix-list PREFIX_TC permit 172.16.1.0/24
pfr-map PREFIX_MAP 10 
 match traffic-class prefix-list PREFIX_TC
 end

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_TC
 permit tcp any 10.1.1.0 0.0.0.255 eq 500
 permit tcp any 172.17.1.0 0.0.255.255 eq 500
 permit tcp any 172.17.1.0 0.0.255.255 range 700 750 
 permit tcp 192.168.1.1 0.0.0.0 10.1.2.0 0.0.0.255 eq 800any any dscp ef 
 exit
pfr-map ACCESS_MAP 10 
 match traffic-class access-list ACCESS_TC