- set active-probe (PfR)
- set backoff (PfR)
- set delay (PfR)
- set holddown (PfR)
- set interface (PfR)
- set jitter (PfR)
- set link-group (PfR)
- set loss (PfR)
- set mode (PfR)
- set mos (PfR)
- set next-hop (PfR)
- set periodic (PfR)
- set probe (PfR)
- set resolve (PfR)
- set traceroute reporting (PfR)
- set unreachable (PfR)
- show pfr api provider
- show pfr border
- show pfr border active-probes
- show pfr border defined application
- show pfr border passive applications
- show pfr border passive cache learned
- show pfr border passive learn
- show pfr border passive prefixes
- show pfr border routes
- show pfr master
- show pfr master active-probes
- show pfr master appl
- show pfr master border
- show pfr master cost-minimization
- show pfr master defined application
- show pfr master learn list
- show pfr master link-group
- show pfr master nbar application
- show pfr master policy
- show pfr master prefix
- show pfr master traffic-class
- show pfr master traffic-class application nbar
- show pfr proxy
- shutdown (PfR)
- throughput (PfR)
- traceroute probe-delay (PfR)
- traffic-class access-list (PfR)
- traffic-class aggregate (PfR)
- traffic-class application (PfR)
- traffic-class application nbar (PfR)
- traffic-class filter (PfR)
- traffic-class keys (PfR)
- traffic-class prefix-list (PfR)
- unreachable (PfR)
set active-probe (PfR)
To configure a Performance Routing (PfR) active probe with a forced target assignment within a PfR map, use the set active-probe command in PfR map configuration mode. To disable the active probe, use the no form of this command.
set active-probe probe-type ip-address target-port number [codec codec-name] [dscp value]
no set active-probe probe-type ip-address
Syntax Description
Command Default
No active probes are configured with a forced target assignment.
Command Modes
PfR map configuration (config-pfr-map)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Usage Guidelines
If the optional dscp keyword and value argument are not specified, active probes are created using the DSCP value of the traffic class. For example, the software creates two sets of probes for the following three traffic classes. Traffic class 2 is assigned a probe with a DSCP value of ef, and the other two traffic classes share a probe with a DSCP value of 0.
•
Traffic class 1: 10.1.1.0/24, destination port 23
•Traffic class 2: 10.1.2.0/24, dscp ef
•Traffic class 3: 10.1.2.0/24, destination port 991
If the optional dscp keyword and value argument are provided, probes are created using the specified DSCP value. For example, if the DSCP value specified for the set active-probe command is cs1, only one probe is created for the three traffic classes.
Examples
The following example shows how to configure an ICMP reply (ping) message probe with a forced target assignment within a PfR map. The 10.1.2.10 address is the forced target assignment. A remote responder does not have to be enabled on the target device.
Router(config)# pfr-map MAP1 10
Router(config-pfr-map)# match ip prefix-list LIST1
Router(config-pfr-map)# set active-probe echo 10.1.2.10
The following example shows how to configure a TCP connection message probe with a forced target assignment within an PfR map. The 10.1.2.10 address is the forced target assignment, the target port is defined as 29, and the DSCP value is set to ef. A remote responder must be enabled on the target device.
Router(config)# pfr-map MAP2 10
Router(config-pfr-map)# match ip prefix-list LISTMAP2
Router(config-pfr-map)# set active-probe tcp-conn 10.1.2.10 target-port 29 dscp ef
Related Commands
set backoff (PfR)
To configure a Performance Routing (PfR) map to set the backoff timer to adjust the time period for prefix policy decisions, use the set backoff command in PfR map configuration mode. To delete the set clause entry and reset the backoff timers to the default values, use the no form of this command.
set backoff min-timer max-timer [step-timer]
no set backoff
Syntax Description
Command Default
PfR uses the following default values if this command is not configured or if the no form of this command is entered:
min-timer: 300
max-timer: 3000
step-timer: 300
Command Modes
PfR map configuration (config-pfr-map)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Usage Guidelines
The set backoff command is entered on a master controller in PfR map configuration mode. This command is used to configure a PfR map to set the transition period for which the master controller holds an out-of-policy prefix. The master controller uses a backoff timer to schedule the prefix transition period for which PfR holds the out-of-policy prefix before moving the prefix to an in-policy state by selecting an in-policy exit. This command is configured with a minimum and maximum timer value and can be configured with an optional step timer.
Minimum Timer—The min-timer argument is used to set the minimum transition period in seconds. If the current prefix is in-policy when this timer expires, no change is made and the minimum timer is reset to the default or configured value. If the current prefix is out-of-policy, PfR will move the prefix to an in-policy and reset the minimum timer to the default or configured value.
Maximum Timer—The max-timer argument is used to set the maximum length of time for which PfR holds an out-of-policy prefix when there are no PfR-controlled in-policy prefixes. If all PfR-controlled prefixes are in an out-of-policy state and the value from the max-timer argument expires, PfR will select the best available exit and reset the minimum timer to the default or configured value.
Step Timer—The step-timer argument allows you to optionally configure PfR to add time each time the minimum timer expires until the maximum time limit has been reached. If the maximum timer expires and all PfR-managed exits are out-of-policy, PfR will install the best available exit and reset the minimum timer.
Configuring a new timer value will immediately replace the existing value if the new value is less than the time remaining. If the new value is greater than the time remaining, the new timer value will be used when the existing timer value expires.
Examples
The following example creates a PfR map named BACKOFF that sets the minimum timer to 400 seconds, the maximum timer to 4000 seconds, and the step timer to 400 seconds for traffic from the prefix list named CUSTOMER:
Router(config)# pfr-map BACKOFF 70
Router(config-pfr-map)# match ip address prefix-list CUSTOMER
Router(config-pfr-map)# set backoff 400 4000 400
Related Commands
set delay (PfR)
To configure a Performance Routing (PfR) map to configure PfR to set the delay threshold, use the set delay command in PfR map configuration mode. To delete the set clause entry and reset the delay threshold values, use the no form of this command.
set delay {relative percentage | threshold maximum}
no set delay
Syntax Description
Command Default
PfR uses the default values if this command is not configured or if the no form of this command is entered.
Command Modes
PfR map configuration (config-pfr-map)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Usage Guidelines
The set delay command is entered on a master controller in PfR map configuration mode. This command is configured in a PfR map to set the delay threshold as a relative percentage or as an absolute value for match criteria.
The relative keyword is used to configure a relative delay percentage. The relative delay percentage is based on a comparison of short-term and long-term measurements. The short-term measurement reflects the delay percentage within a 5-minute time period. The long-term measurement reflects the delay percentage within a 60-minute period. The following formula is used to calculate this value:
Relative delay measurement = ((short-term measurement - long-term measurement) / long-term measurement) * 100
The master controller measures the difference between these two values as a percentage. If the percentage exceeds the user-defined or default value, the delay percentage is determined to be out-of-policy. For example, if the long-term delay measurement is 100 milliseconds and the short-term delay measurement is 120 milliseconds, the relative delay percentage is 20 percent.
The threshold keyword is used to configure the absolute maximum delay period in milliseconds.
If the measured delay of the prefix is higher than the configured delay threshold, the prefix is out-of-policy. If the short-term delay of the prefix is more than the long-term delay by the percentage value configured, the prefix is out-of-policy.
Examples
The following example creates a PfR map named DELAY that sets the absolute maximum delay threshold to 2000 milliseconds for traffic from the prefix list named CUSTOMER:
Router(config)# pfr-map DELAY 80
Router(config-pfr-map)# match ip address prefix-list CUSTOMER
Router(config-pfr-map)# set delay threshold 2000
Related Commands
|
|
|
|---|---|
delay (PfR) |
Configures prefix delay parameters. |
pfr-map |
Enters PfR map configuration mode to configure a PfR map to apply policies to selected IP prefixes. |
set holddown (PfR)
To configure a Performance Routing (PfR) map to set the prefix route dampening timer for the minimum period of time in which a new exit must be used before an alternate exit can be selected, use the set holddown command in PfR map configuration mode. To delete the set clause entry and resets the holddown timer to the default value, use the no form of this command.
set holddown timer
no set holddown
Syntax Description
timer |
Sets the prefix route dampening time period, in seconds. The range for this argument is from 90 to 65535. The default value is 300. |
Command Default
PfR uses the default value of 300 seconds for the prefix route dampening time period if this command is not configured or if the no form of this command is entered.
Command Modes
PfR map configuration (config-pfr-map)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Usage Guidelines
The set holddown command is entered on a master controller in PfR map configuration mode. This command is used to configure the prefix route dampening timer for the minimum period of time in which a new exit must be used before an alternate exit can be selected. The master controller puts a prefix in a holddown state during an exit change to isolate the prefix during the transition period, preventing the prefix from flapping because of rapid state changes. PfR does not implement policy changes while a prefix is in the holddown state. A prefix will remain in a holddown state for the default or configured time period. When the holddown timer expires, PfR will select the best exit based on performance and policy configuration. However, an immediate route change will be triggered if the current exit for a prefix becomes unreachable.
Configuring a new timer value will immediately replace the existing value if the new value is less than the time remaining. If the new value is greater than the time remaining, the new timer value will be used when the existing timer is reset.
Examples
The following example creates a PfR map named HOLDDOWN that sets the holddown timer to 120 seconds for traffic from the prefix list named CUSTOMER:
Router(config)# pfr-map HOLDDOWN 10
Router(config-pfr-map)# match ip address prefix-list CUSTOMER
Router(config-pfr-map)# set holddown 120
Related Commands
set interface (PfR)
To configure a Performance Routing (PfR) map to send packets that match prefixes in an access list on PfR border routers to the null interface, use the set interface command in PfR map configuration mode. To delete the set clause entry, use the no form of this command.
set interface null0
no set interface null0
Syntax Description
null0 |
Specifies that packets will be sent to the null interface, which means that the packets are discarded. |
Command Default
No packets are sent to the null interface.
Command Modes
PfR map configuration (config-pfr-map)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Usage Guidelines
The set interface command is entered on a master controller in PfR map configuration mode. This command can be used for PfR black hole filtering if the border routers detect a denial-of-service (DoS) attack by directing packets to the null interface. The null interface is a virtual network interface that is similar to the loopback interface. Whereas traffic to the loopback interface is directed to the router itself, traffic sent to the null interface is discarded. This interface is always up and can never forward or receive traffic; encapsulation always fails. The null interface functions similarly to the null devices available on most operating systems. Null interfaces are used as a low-overhead method of discarding unnecessary network traffic.
Examples
The following example shows how to configure a PfR map named BLACK_HOLE_MAP to direct packets to the null interface. To use this configuration for a DoS attack, leave the access list empty until an attack is detected and add the prefix or prefixes that are determined to be the source of the attack. Subsequent packets received from the specified prefix or prefixes will be discarded.
Router(config)# pfr-map black-hole-map 10
Router(config-pfr-map)# match ip address access-list black-hole-list
Router(config-pfr-map)# set interface null0
Related Commands
set jitter (PfR)
To configure a Performance Routing (PfR) map to set the maximum jitter value that PfR will permit for an exit link, use the set jitter command in PfR map configuration mode. To delete the set clause entry, use the no form of this command.
set jitter threshold maximum
no set jitter threshold maximum
Syntax Description
Command Default
No jitter values are set.
Command Modes
PfR map configuration (config-pfr-map)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Usage Guidelines
The set jitter command is entered on a master controller in PfR map configuration mode. This command is used to specify the maximum tolerable jitter value permitted on an exit link. Jitter is a measure of voice quality where the lower the jitter value, the higher the voice quality. If the jitter value is greater than the user-defined or default value, PfR determines that the exit link is out-of-policy and searches for an alternate exit link.
Another measure of voice quality is the estimated Mean Opinion Score (MOS). Use the set mos command and the set jitter command in a PfR map to define voice quality.
Examples
The following example shows how to configure a PfR map named JITTER that sets the threshold jitter value. If the jitter threshold value exceeds 20 milliseconds, and more than 30 percent of the MOS samples are below the MOS threshold of 3.80 for voice quality, the master controller searches for a new exit link.
Router(config)# oer-map JITTER 10
Router(config-oer-map)# set jitter threshold 20
Router(config-oer-map)# set mos threshold 3.80 percent 30
Related Commands
set link-group (PfR)
To specify a link group for traffic classes defined in a Performance Routing (PfR) policy, use the set link-group command in PfR map configuration mode. To delete the set clause entry and remove the link group, use the no form of this command.
set link-group link-group-name [fallback link-group-name]
no set link-group link-group-name
Syntax Description
link-group-name |
Name of a link group. |
fallback |
(Optional) Specifies a fallback link group to be used if the primary link group is out-of-policy (OOP). |
Command Default
No link groups are specified for a traffic class.
Command Modes
PfR map configuration (config-pfr-map)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Usage Guidelines
The set link-group command is entered on a master controller in PfR map configuration mode. This command is used to define a link group for the traffic class matched in a PfR map.
Introduced in Cisco IOS Release 12.4(15)T, link groups are used to define a group of exit links as a preferred set of links or a fallback set of links for PfR to use when optimizing traffic classes specified in a PfR policy. Up to three link groups can be specified for each interface. Use the link-group (PfR) command to define the link group for an interface and use the set link-group command to define the primary link group and a fallback link group for a specified traffic class in a PfR map.
Use the show pfr master link-group command to view information about configured PfR link groups.
Examples
The following example shows how to configure a PfR map named link_video_map that configures PfR to create a traffic class that matches an access list named video_list. The traffic class is configured to use a link group named video as the primary link group, and a fallback group named voice. The video link group may be a set of high bandwidth links that are preferred for video traffic.
Router(config)# pfr-map link_video_map 10
Router(config-pfr-map)# match ip address access-list video_list
Router(config-pfr-map)# set link-group video fallback voice
Related Commands
set loss (PfR)
To configure a Performance Routing (PfR) map to set the relative or maximum packet loss limit that PfR will permit for an exit link, use the set loss command in PfR map configuration mode. To delete the set clause entry and reset the relative percentage of packet loss to the default value, use the no form of this command.
set loss {relative average | threshold maximum}
no set loss
Syntax Description
Command Default
PfR uses a default relative percentage of 100 (10 percent) if this command is not configured or if the no form of this command is entered.
Command Modes
PfR map configuration (config-pfr-map)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Usage Guidelines
The set loss command is entered on a master controller in PfR map configuration mode. This command is used to configure a PfR map to set the relative percentage or maximum number of packets that PfR will permit to be lost during transmission on an exit link. If packet loss is greater than the user-defined or the default value, PfR determines that the exit link is out-of-policy and searches for an alternate exit link.
The relative keyword is used to configure the relative packet loss percentage. The relative packet loss percentage is based on a comparison of short-term and long-term packet loss. The short-term measurement reflects the percentage of packet loss within a 5-minute period. The long-term measurement reflects the percentage of packet loss within a 60-minute period. The following formula is used to calculate this value:
Relative packet loss = ((short-term loss - long-term loss) / long-term loss) * 100
The master controller measures the difference between these two values as a percentage. If the percentage exceeds the user-defined or default value, the exit link is determined to be out-of-policy. For example, if long-term packet loss is 200 PPM and short-term packet loss is 300 PPM, the relative loss percentage is 50 percent.
The threshold keyword is used to configure the absolute maximum packet loss. The maximum value is based on the actual number of PPM that have been lost.
Examples
The following example creates a PfR map named LOSS that sets the relative percentage of acceptable packet loss for traffic from the prefix list named CUSTOMER to a 20 percent relative percentage. If the packet loss on the current exit link exceeds 20 percent, the master controller will search for a new exit.
Router(config)# pfr-map LOSS 10
Router(config-pfr-map)# match ip address prefix-list CUSTOMER
Router(config-pfr-map)# set loss relative 200
Related Commands
set mode (PfR)
To configure a Performance Routing (PfR) map to configure route monitoring, route control, or exit selection for matched traffic, use the set mode command in PfR map configuration mode. To delete the set clause entry and reset the default values, use the no form of this command.
set mode {monitor {active [throughput] | both | fast | passive} | route {control | observe} | select-exit {best | good}}
no set mode {monitor | route {control | observe} | select-exit}
Syntax Description
Command Default
PfR uses the following default settings if this command is not configured or if the no form of this command is entered:
•Monitoring: Both active and passive monitoring is enabled.
•Route control: Observe mode route control is enabled.
•Exit Selection: The first in-policy exit is selected.
Command Modes
PfR map configuration (config-pfr-map)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Usage Guidelines
The set mode command is entered on a master controller in PfR map configuration mode. This command is used to configure a PfR map to enable and configure observe mode and control mode settings, passive monitoring and active monitoring, and exit link selection for traffic that is configured as match criteria.
Observe Mode
Observe mode monitoring is enabled by default. In observe mode, the master controller monitors prefixes and exit links based on default and user-defined policies and then reports the status of the network and the decisions that should be made, but it does not implement any changes. This mode allows you to verify the effectiveness of this feature before it is actively deployed.
Control Mode
In control mode, the master controller coordinates information from the border routers and makes policy decisions just as it does in observe mode. The master controller monitors prefixes and exits based on default and user-defined policies, but then it implements changes to optimize prefixes and to select the best exit. In this mode, the master controller gathers performance statistics from the border routers and then transmits commands to the border routers to alter routing as necessary in the PfR managed network.
Passive Monitoring
The master controller passively monitors IP prefixes and TCP traffic flows. Passive monitoring is configured on the master controller. Monitoring statistics are gathered on the border routers and then reported back to the master controller. PfR uses NetFlow to collect and aggregate passive monitoring statistics on a per-prefix basis. No explicit NetFlow configuration is required. NetFlow support is enabled by default when passive monitoring is enabled. PfR uses passive monitoring to measure the following information:
Delay—PfR measures the average delay of TCP flows for a prefix. Delay is the measurement of the time between the transmission of a TCP synchronization message and receipt of the TCP acknowledgement.
Packet Loss—PfR measures packet loss by tracking TCP sequence numbers for each TCP flow. PfR estimates packet loss by tracking the highest TCP sequence number. If a subsequent packet is received with a lower sequence number, PfR increments the packet loss counter.
Reachability—PfR measures reachability by tracking TCP synchronization messages that have been sent repeatedly without receiving a TCP acknowledgement.
Throughput—PfR measures outbound throughput for optimized prefixes. Throughput is measured in bits per second (bps).
Note PfR passively monitors TCP traffic flows for IP traffic. Passive monitoring of non-TCP sessions is not supported.
Active Monitoring
PfR uses Cisco IOS IP Service Level Agreements (SLAs) to enable active monitoring. IP SLAs support is enabled by default. IP SLAs support allows PfR to be configured to send active probes to target IP addresses to measure the jitter and delay, determining if a prefix is out-of-policy and if the best exit is selected. The border router collects these performance statistics from the active probe and transmits this information to the master controller. The master controller uses this information to optimize the prefix and select the best available exit based on default and user-defined policies. The active-probe command is used to create an active probe.
The throughput keyword enables the throughput data from passive mode monitoring to be considered when optimizing UDP traffic for both performance and load-balancing. UDP traffic can be optimized only for performance (for example, delay, jitter, and loss) when active monitoring data is available. To enable load-balancing of UDP traffic, throughput data from passive monitoring is required.
Fast Failover Monitoring
Fast monitoring sets the active probes to continuously monitor all the exits (probe-all), and passive monitoring is enabled too. Fast failover monitoring can be used with all types of active probes: ICMP echo, jitter, TCP connection, and UDP echo. When the mode monitor fast command is enabled, the probe frequency can be set to a lower frequency than for other monitoring modes, to allow a faster failover ability. Under fast monitoring with a lower probe frequency, route changes can be performed within 3 seconds of an out-of-policy situation. When an exit becomes OOP under fast monitoring, the select best exit is operational and the routes from the OOP exit are moved to the best in-policy exit. Fast monitoring is a very aggressive mode that incurs a lot of overhead with the continuous probing. We recommend that you use fast monitoring only for performance-sensitive traffic.
Optimal Exit Link Selection
The master controller can be configured to select a new exit for an out-of-policy prefix based on performance or policy. You can configure the master controller to select the first in-policy exit by entering the good keyword, or you can configure the master controller to select the best exit with the best keyword. If the good keyword is used and there is no in-policy exit, the prefix is uncontrolled.
Examples
The following example creates a PfR map named OBSERVE that configures PfR to observe and report but not control traffic from the prefix list named CUSTOMER:
Router(config)# pfr-map OBSERVE 80
Router(config-pfr-map)# match ip address prefix-list CUSTOMER
Router(config-pfr-map)# set mode route observe
Related Commands
set mos (PfR)
To configure a Performance Routing (PfR) map to set the threshold and percentage Mean Opinion Score (MOS) values that PfR will permit for an exit link, use the set mos command in PfR map configuration mode. To reset the threshold MOS values to their default value, use the no form of this command.
set mos threshold minimum percentage percent
no set mos threshold minimum percentage percent
Syntax Description
Command Default
The default MOS value is 3.60.
Command Modes
PfR map configuration (config-pfr-map)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Usage Guidelines
The set mos command is entered on a master controller in PfR map configuration mode and is used to determine voice quality. The number of MOS samples over a period of time that are below the threshold MOS value are calculated. If the percentage of MOS samples below the threshold is greater than the configured percentage, PfR determines that the exit link is out-of-policy and searches for an alternate exit link.
Another measure of voice quality is the jitter value. Use the set mos (PfR) command and the set jitter (PfR) command in a PfR map to define voice quality.
Examples
The following example creates a PfR map named MOS that configures the master controller to search for a new exit link if more than 30 percent of the MOS samples are below the MOS threshold of 3.80.
Router(config)# pfr-map MOS 10
Router(config-pfr-map)# match ip address prefix-list LIST1
Router(config-pfr-map)# set mos threshold 3.80 percent 30
Related Commands
set next-hop (PfR)
To configure a Performance Routing (PfR) map to send packets that match prefixes in an access list on PfR border routers to the specified next hop, use the set next-hop command in PfR map configuration mode. To delete the set clause entry, use the no form of this command.
set next-hop ip-address
no set next-hop ip-address
Syntax Description
ip-address |
IP address of the next hop to which the packets will be sent. |
Command Default
No packets that match prefixes in an access list on PfR border routers are sent to the next hop.
Command Modes
PfR map configuration (config-pfr-map)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Usage Guidelines
This command can be used for PfR sinkhole filtering if the border routers detect a denial-of-service (DoS) attack by directing packets to the specified next hop. The packets may be saved, analyzed, or discarded at the next hop.
Examples
The following example shows how to configure a PfR map named SINKHOLE_MAP that directs packets to the specified next hop. Use this configuration in preparation for a DoS attack, leave the access list empty until an attack is detected, and add the prefix or prefixes that are determined to be the source of the attack. Subsequent packets received from the specified prefix or prefixes will be sent to the specified next hop.
Router(config)# pfr-map SINKHOLE_MAP 10
Router(config-pfr-map)# match ip address access-list SINKHOLE-LIST
Router(config-pfr-map)# set next-hop 10.20.24.3
Related Commands
set periodic (PfR)
To configure a Performance Routing (PfR) map to set the time period for the periodic timer, use the set periodic command in PfR map configuration mode. To delete the set clause entry and remove the periodic timer setting, use the no form of this command.
set periodic timer
no set periodic
Syntax Description
timer |
Length of time set for the periodic timer, in seconds. The value for the timer argument is from 180 to 7200. |
Command Default
The periodic timer is not set using a PfR map.
Command Modes
PfR map configuration (config-pfr-map)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Usage Guidelines
The set periodic command is entered on a master controller in PfR map configuration mode. This command is used to configure a PfR map to configure PfR to periodically select the best exit based on the periodic timer value for traffic that is configured as match criteria in a PfR map. When this timer expires, PfR will automatically select the best exit, whether the current exit is in-policy or out-of-policy. The periodic timer is reset when the new exit is selected.
Examples
The following example creates a PfR map named PERIODIC that sets the periodic timer to 300 seconds for traffic from the prefix list named CUSTOMER. When the timer expires, PfR will select the best exit.
Router(config)# pfr-map PERIODIC 80
Router(config-pfr-map)# match ip address prefix-list CUSTOMER
Router(config-pfr-map)# set periodic 300
Related Commands
|
|
|
|---|---|
periodic (PfR) |
Configures PfR to periodically select the best exit. |
pfr-map |
Enters PfR map configuration mode to configure a PfR map to apply policies to selected IP prefixes. |
set probe (PfR)
To set the frequency of a Performance Routing (PfR) active probe, use the set probe command in PfR map configuration mode. To reset the frequency of a PfR active probe to its default values, use the no form of this command.
set probe {frequency seconds | packets packet-count}
no set probe {frequency seconds | packets packet-count}
Syntax Description
Command Default
The default active probe frequency is 60 seconds.
The default number of packets per probe is 100.
Command Modes
PfR map configuration (config-pfr-map)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Usage Guidelines
The set probe command is entered on a master controller in PfR map configuration mode. This command is used within a PfR map configuration to set the frequency of the active probes. Unless the default frequency of 60 seconds is used, configuring the set probe command will increase the frequency of the probes. Increased probe frequency results in a lower response time of PfR. The frequency can be increased for a number of policies, but if all active probes are set to an increased frequency, an Intrusion Detection Service (IDS) may be triggered.
Fast monitoring sets the active probes to continuously monitor all the exits (probe-all), and passive monitoring is enabled too. Fast failover monitoring can be used with all types of active probes: ICMP echo, jitter, TCP connection, and UDP echo. When the mode monitor fast command is enabled, the probe frequency can be set to a lower frequency than for other monitoring modes, to allow a faster failover ability. The minimum number of seconds was lowered from 4 seconds to 2 seconds to support the fast failover monitoring mode. Under fast monitoring with a lower probe frequency, route changes can be performed within 3 seconds of an out-of-policy situation.
Using the packets keyword and the packet-count argument, the number of probe packets per jitter probe can be set. The new keyword is supported under PfR map configuration mode only, not at a global level. The new keyword applies only to jitter probes, and the configuration affects global probes and forced probes for all traffic classes.
Examples
The following example shows how to set the frequency of an active probe to be 10 seconds using a PfR map named PROBE:
Router(config)# pfr-map PROBE 10
Router(config-pfr-map)# set probe frequency 10
The following example shows how to set the frequency of an active probe to be 2 seconds using a PfR map named FAST after the fast failover monitoring mode is enabled:
Router(config)# pfr-map FAST 10
Router(config-pfr-map)# set mode monitor fast
Router(config-pfr-map)# set probe frequency 2
The following example shows how to set the number of probe packets for a jitter probe at 33 packets using a PfR map named JITTER:
Router(config)# pfr-map JITTER
Router(config-pfr-map)# set probe packets 33
Related Commands
set resolve (PfR)
To configure a PfR map to set policy priority for overlapping policies, use the set resolve command in PfR map configuration mode. To delete the set clause entry, use the no form of this command.
set resolve {cost priority value | delay priority value variance percentage | jitter priority value variance percentage | loss priority value variance percentage | mos priority value
variance percentage | range priority value | utilization priority value variance percentage}
no set resolve {cost | delay | jitter | loss | mos | range | utilization}
Syntax Description
Command Default
PfR uses the following default settings if this command is not configured or if the no form of this command is entered:
•An unreachable prefix: highest priority
•delay priority: 11
•utilization priority: 12
Command Modes
PfR map configuration (config-pfr-map)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Usage Guidelines
The set resolve command is entered on a master controller in PfR map configuration mode. This command is used to set priority when multiple policies are configured for the same prefix. When this command is configured, the policy with the highest priority will be selected to determine the policy decision.
The priority keyword is used to specify the priority value. The number 1 assigns the highest priority to the policy. The number 10 sets the lowest priority. Each policy must be assigned a different priority number. If you try to assign the same priority number to two different policy types, an error message will be displayed on the console.
The variance keyword is used to set an allowable variance for a user-defined policy. This keyword configures the allowable percentage by which an exit link or prefix can vary from the user-defined policy value and still be considered equivalent. For example, if exit link delay is set to 80 percent and a 10 percent variance is configured, exit links with delay values from 80 to 89 percent will be considered equal.
Note Variance cannot be set for cost or range policies.
Examples
The following example creates a PfR map named RESOLVE that sets the priority for delay policies to 1 for traffic learned based on highest outbound throughput. The variance is set to allow a 10 percent difference in delay statistics before a prefix is determined to be out-of-policy.
Router(config)# pfr-map RESOLVE 10
Router(config-pfr-map)# match pfr learn throughput
Router(config-pfr-map)# set resolve delay priority 1 variance 10
Related Commands
set traceroute reporting (PfR)
To configure a Performance Routing (PfR) map to enable traceroute reporting, use the set traceroute reporting command in PfR map configuration mode. To delete the set clause entry, use the no form of this command.
set traceroute reporting [policy {delay | loss | unreachable}]
no set traceroute reporting [policy {delay | loss | unreachable}]
Syntax Description
Command Default
Traceroute reporting is not enabled using a PfR map.
Command Modes
PfR map configuration (config-pfr-map)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Usage Guidelines
The set traceroute reporting command is entered on a master controller in PfR map configuration mode. This command is used to enable continuous and policy-based traceroute probing. Traceroute probing allows you to monitor prefix performance on a hop-by-hop basis. Delay, loss, and reachability measurements are gathered for each hop from the probe source to the target prefix.
The following types of traceroute reporting are configured with this command:
Continuous—A traceroute probe is triggered for each new probe cycle. Entering this command without any keywords enables continuous reporting. The probe is sourced from the current exit of the prefix.
Policy based—A traceroute probe is triggered automatically when a prefix goes into an out-of-policy state. Entering this command with the policy keyword enables policy-based traceroute reporting. Policy-based traceroute probes are configured individually for delay, loss, and reachability policies. The monitored prefix is sourced from a match clause in a PfR map. Policy-based traceroute reporting stops when the prefix returns to an in-policy state.
The show pfr master prefix command is used to display traceroute probe results. An on-demand traceroute probe can be initiated when entering the show pfr master prefix command with the current and now keywords. The set traceroute reporting command does not have to be configured to initiate an on-demand traceroute probe.
Examples
The following example, starting in global configuration mode, enables continuous traceroute probing for prefixes that are learned based on delay:
Router(config)# pfr-map TRACE 10
Router(config-pfr-map)# match pfr learn delay
Router(config-pfr-map)# set traceroute reporting
Related Commands
set unreachable (PfR)
To configure a Performance Routing (PfR) map to set the maximum number of unreachable hosts, use the set unreachable command in PfR map configuration mode. To delete the set clause entry and reset the relative percentage of unreachable hosts to the default value of 50 (5 percent), use the no form of this command.
set unreachable {relative average | threshold maximum}
no set unreachable
Syntax Description
Command Default
PfR uses a default relative percentage of 50 (5 percent) unreachable hosts if this command is not configured or if the no form of this command is entered.
Command Modes
PfR map configuration (config-pfr-map)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Usage Guidelines
The set unreachable command is entered on a master controller in PfR map configuration mode. This command is used to set the relative percentage or the absolute maximum number of unreachable hosts, based on flows per million, that PfR will permit from a PfR-managed exit link. If the absolute number or relative percentage of unreachable hosts is greater than the user-defined or the default value, PfR determines that the exit link is out-of-policy and searches for an alternate exit link.
The relative keyword is used to configure the relative percentage of unreachable hosts. The relative unreachable host percentage is based on a comparison of short-term and long-term measurements. The short-term measurement reflects the percentage of hosts that are unreachable within a 5-minute period. The long-term measurement reflects the percentage of unreachable hosts within a 60-minute period. The following formula is used to calculate this value:
Relative percentage of unreachable hosts = ((short-term percentage - long-term percentage) / long-term percentage) * 100
The master controller measures the difference between these two values as a percentage. If the percentage exceeds the user-defined or default value, the exit link is determined to be out-of-policy. For example, if 10 hosts are unreachable during the long-term measurement and 12 hosts are unreachable during short-term measurement, the relative percentage of unreachable hosts is 20 percent.
The threshold keyword is used to configure the absolute maximum number of unreachable hosts. The maximum value is based on the actual number of hosts that are unreachable based on fpm.
Examples
The following example creates a PfR map named UNREACHABLE that configures the master controller to search for a new exit link when the difference between long- and short-term measurements (relative percentage) is greater than 10 percent for traffic learned based on highest delay:
Router(config)# pfr-map UNREACHABLE 10
Router(config-pfr-map)# match pfr learn delay
Router(config-pfr-map)# set unreachable relative 100
Related Commands
show pfr api provider
To display information about application programming interface providers that are registered with Performance Routing (PfR), use the show pfr api provider command in privileged EXEC mode.
show pfr api provider [detail]
Syntax Description
detail |
(Optional) Displays detailed information about application interface providers. |
Command Default
Detailed information about API providers is not displayed.
Command Modes
Privileged EXEC (#)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Usage Guidelines
The show pfr api provider command is entered on a master controller. This command is used to display application interface provider and host information including the ID of each configured provider, the priority of the provider and the host (if configured), and the IP addresses of each configured host device. The detail keyword is used to display more detailed information.
The PfR 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 is defined as an entity outside the network in which the router configured as a PfR master controller exists, for example, an ISP, or a branch office of the same company. The provider has one or more host devices running one or more applications that use the PfR application interface to communicate with a PfR master controller. A provider must be registered with a PfR master controller before an application on a host device can interface with PfR. Use the api provider command to register the provider, and use the host-address (PfR) command to configure a host device. After registration, a host device in the provider network can initiate a session with a PfR master controller. The PfR application interface provides an automated method for networks to be aware of applications and provides application-aware performance routing.
Examples
The following example shows information about configured application interface providers and host devices:
Router# show pfr api provider
API Version: Major 2, Minor 0
Provider id 1, priority 4000
Host ip 172.17.1.1, priority 4001
Host ip 10.1.2.2, priority 3001
Provider id 2, priority 20
Provider id 3, priority 10
Table 23 describes the significant fields shown in the display.
The following example shows detailed information about configured application interface providers and host devices:
Router# show pfr api provider detail
API Version: Major 2, Minor 0
Provider id 1001, priority 65535
Host ip 10.3.3.3, priority 65535
Session id 9, Version Major 2, Minor 0
Num pfx created 2, Num policies created 2
Last active connection time (sec) 00:00:01
Policy ids : 101, 102,
Host ip 10.3.3.4, priority 65535
Session id 10, Version Major 2, Minor 0
Num pfx created 1, Num policies created 1
Last active connection time (sec) 00:00:03
Policy ids : 103,
Provider id 2001, priority 65535
Host ip 172.19.198.57, priority 65535
Session id 11, Version Major 2, Minor 0
Num pfx created 0, Num policies created 0
All Prefix report enabled
All exit report enabled
Table 24 describes the significant fields shown in the display that are different from Table 23.
Related Commands
show pfr border
To display information about a Performance Routing (PfR) border-router connection and PfR-controlled interfaces, use the show pfr border command in privileged EXEC mode.
show pfr border
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Cisco IOS XE Release 3.1S |
This command was integrated into Cisco IOS XE Release 3.1S. |
Usage Guidelines
The show pfr border command is entered on a PfR border router. The output displays information about the border router, the status of the master controller connection, and border router interfaces.
Examples
The following example shows the status of a border router:
Router# show pfr border
OER BR 10.1.1.3 ACTIVE, MC 10.1.1.1 UP/DOWN: UP 00:57:55,
Auth Failures: 0
Conn Status: SUCCESS, PORT: 3949
Exits
Et0/0 INTERNAL
Et1/0 EXTERNAL
Table 25 describes the significant fields shown in the display.
Related Commands
|
|
|
|---|---|
pfr |
Enables a PfR process and configures a router as a PfR border router or as a PfR master controller. |
show pfr border active-probes
To display connection status and information about active probes on a Performance Routing (PfR) border router, use the show pfr border active-probes command in privileged EXEC mode.
show pfr border active-probes
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Cisco IOS XE Release 3.1S |
This command was integrated into Cisco IOS XE Release 3.1S. |
Usage Guidelines
The show pfr border active-probes command is entered on a border router. This command displays the target active-probe assignment for a given prefix and the current probing status, including the border router or border routers that are executing the active probes.
Examples
The following example shows three active probes, each configured for a different prefix. The target port, source IP address, and exit interface are displayed in the output.
Router# show pfr border active-probes
PfR Border active-probes
Type = Probe Type
Target = Target IP Address
TPort = Target Port
Source = Send From Source IP Address
Interface = Exit interface
Att = Number of Attempts
Comps = Number of completions
N - Not applicable
Type Target TPort Source Interface Att Comps
udp-echo 10.4.5.1 80 10.0.0.1 Et1/0 1 0
tcp-conn 10.4.7.1 33 10.0.0.1 Et1/0 1 0
echo 10.4.9.1 N 10.0.0.1 Et1/0 2 2
Table 26 describes the significant fields shown in the display.
Related Commands
show pfr border defined application
To display information about user-defined applications on a Performance Routing (PfR) border router, use the show pfr border defined application command in privileged EXEC mode.
show pfr border defined application
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Cisco IOS XE Release 3.1S |
This command was integrated into Cisco IOS XE Release 3.1S. |
Usage Guidelines
The show pfr border defined application command is entered on a PfR border router. This command displays all user-defined applications that are defined on the master controller. To define a custom application to be used by PfR, use the application define (PfR) command on the PfR master controller.
To display the same information on the PfR master controller, use the show pfr master defined application command.
Examples
The following partial output shows information about the user-defined application definitions configured for use with PfR:
Router# show pfr border defined application
PfR Defined Applications:
Name Appl_ID Dscp Prot SrcPort DstPort SrcPrefix
--------------------------------------------------------------------------------
telnet 1 defa tcp 23-23 1-65535 0.0.0.0/0
telnet 1 defa tcp 1-65535 23-23 0.0.0.0/0
ftp 2 defa tcp 21-21 1-65535 0.0.0.0/0
ftp 2 defa tcp 1-65535 21-21 0.0.0.0/0
cuseeme 4 defa tcp 7648-7648 1-65535 0.0.0.0/0
cuseeme 4 defa tcp 7649-7649 1-65535 0.0.0.0/0
dhcp 5 defa udp 68-68 67-67 0.0.0.0/0
dns 6 defa tcp 53-53 1-65535 0.0.0.0/0
dns 6 defa tcp 1-65535 53-53 0.0.0.0/0
dns 6 defa udp 53-53 1-65535 0.0.0.0/0
dns 6 defa udp 1-65535 53-53 0.0.0.0/0
finger 7 defa tcp 79-79 1-65535 0.0.0.0/0
finger 7 defa tcp 1-65535 79-79 0.0.0.0/0
gopher 8 defa tcp 70-70 1-65535 0.0.0.0/0
.
.
.
Table 27 describes the significant fields shown in the display.
Related Commands
show pfr border passive applications
To display the list of application traffic classes that are monitored by Performance Routing (PfR), use the show pfr border passive applications command in privileged EXEC mode.
show pfr border passive applications
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Cisco IOS XE Release 3.1S |
This command was integrated into Cisco IOS XE Release 3.1S. |
Usage Guidelines
The show pfr border passive applications command is entered on a border router. This command displays a list of application traffic classes that are monitored by the border router using NetFlow passive monitoring.
Examples
The following example displays an application traffic class that is monitored by a border router:
Router# show pfr border passive applications
OER Passive monitored Appl:
+ - monitor more specific
Prefix /Mask Prot Dscp SrcPort DstPort Appl_ID
10.1.3.0 /24 17 ef [1, 65535] [3000, 4000] 1
Table 28 describes the significant fields shown in the display.
Related Commands
|
|
|
|---|---|
pfr |
Enables a PfR process and configures a router as a PfR border router or as a PfR master controller. |
show pfr border passive cache learned
To display passive measurement information that is collected by NetFlow for Performance Routing (PfR) monitored learned prefixes, use the show pfr border passive cache learned command in privileged EXEC mode.
show pfr border passive cache learned [application | traffic-class]
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Cisco IOS XE Release 3.1S |
This command was integrated into Cisco IOS XE Release 3.1S. |
Usage Guidelines
The show pfr border passive cache learned command is entered on a border router. This command displays real-time prefix information that is collected from the border router through NetFlow passive monitoring.
A maximum of five host addresses and five ports are collected for each prefix. The output will also show the throughput in bytes and the delay in milliseconds. If the application keyword is entered, the output displays information about learned prefixes that match other application criteria such as the Differentiated Services Code Point (DSCP) value, protocol, or port number. The traffic-class keyword displays cache information about monitored learned prefixes for a PfR traffic class.
Examples
The following example displays passive monitoring information about learned prefixes:
Router# show pfr border passive cache learned
OER Learn Cache:
State is enabled
Measurement type: throughput, Duration: 2 min
Aggregation type: prefix-length, Prefix length: 24
4096 oer-flows per chunk,
22 chunks allocated, 32 max chunks,
1 allocated records, 90111 free records, 8913408 bytes allocated
Prefix Mask Pkts B/Pk Delay Samples Active
Host1 Host2 Host3 Host4 Host5
dport1 dport2 dport3 dport4 dport5
10.1.5.0 /24 17K 46 300 2 45.1
10.1.5.2 10.1.5.3 0.0.0.0 0.0.0.0 0.0.0.0
1024 80 0 0 0
Table 29 describes the significant fields shown in the display.
The following example uses the application keyword to display measurement information about monitored application traffic classes that have been learned by PfR. In this example for voice traffic, the voice application traffic is identified by the User Datagram Protocol (UDP) protocol, a DSCP value of ef, and port numbers in the range from 3000 to 4000.
Router# show pfr border passive cache learned application
OER Learn Cache:
State is enabled
Measurement type: throughput, Duration: 2 min
Aggregation type: prefix-length, Prefix length: 24
4096 oer-flows per chunk,
8 chunks allocated, 32 max chunks,
5 allocated records, 32763 free records, 4588032 bytes allocated
Prefix Mask Pkts B/Pk Delay Samples Active
Prot Dscp SrcPort DstPort
Host1 Host2 Host3 Host4 Host5
dport1 dport2 dport3 dport4 dport5
10.1.3.0 /24 873 28 0 0 13.3
17 ef [1, 65535] [3000, 4000]
10.1.3.1 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0
3500 0 0 0 0
10.1.1.0 /24 7674 28 0 0 13.4
17 ef [1, 65535] [3000, 4000]
10.1.1.1 0.0.0.0 0.0.0.0 0.0.0.0 0.0.0.0
3600 0 0 0 0
Related Commands
|
|
|
|---|---|
pfr |
Enables a PfR process and configures a router as a PfR border router or as a PfR master controller. |
show pfr border passive learn
To display the configured, learned parameters to be used with passive measurement information collected by NetFlow for Performance Routing (PfR) learned traffic flows, use the show pfr border passive learn command in privileged EXEC mode.
show pfr border passive learn
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Cisco IOS XE Release 3.1S |
This command was integrated into Cisco IOS XE Release 3.1S. |
Usage Guidelines
The show pfr border passive learn command is entered on a border router. This command displays configured parameters including filter and aggregate application information that is collected from the border router through NetFlow passive monitoring.
Examples
The following example displays passive monitoring information about learned traffic flows:
Router# show pfr border passive learn
OER Border Learn Configuration :
State is enabled
Measurement type: throughput, Duration: 2 min
Aggregation type: prefix-length, Prefix length: 24
No port protocol config
Traffic Class Filter List:
List: SrcPrefix SrcMask DstPrefix DstMask
Prot DSCP sport_opr sport_range dport_opr dport_range Grant
1: 0.0.0.0 0 10.1.0.0 16
17 ef 0 [1, 65535] 0 [1, 65535] Permit
Traffic Class Aggregate List:
List: Prot DSCP sport_opr sport_range dport_opr dport_range Grant
1: 17 ef 0 [1, 65535] 7 [3000, 4000] Permit
Keys: protocol dscp DstPort
Table 30 describes the significant fields shown in the display.
Related Commands
|
|
|
|---|---|
pfr |
Enables a PfR process and configures a router as a PfR border router or as a PfR master controller. |
show pfr border passive prefixes
To display information about passive monitored prefixes, use the show pfr border passive prefixes command in privileged EXEC mode.
show pfr border passive prefixes
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Cisco IOS XE Release 3.1S |
This command was integrated into Cisco IOS XE Release 3.1S. |
Usage Guidelines
The show pfr border passive prefixes command is entered on a border router. The output of this command displays prefixes that are monitored by NetFlow on the border router. The prefixes displayed in the output are monitored by the master controller.
Examples
The following example shows a prefix that is passively monitored by NetFlow:
Router# show pfr border passive prefixes
OER Passive monitored prefixes:
Prefix Mask Match Type
10.1.5.0 /24 exact
Table 31 describes the significant fields shown in the display.
Related Commands
|
|
|
|---|---|
pfr |
Enables a PfR process and configures a router as a PfR border router or as a PfR master controller. |
show pfr border routes
To display information about Performance Routing (PfR) controlled routes, use the show pfr border routes command in privileged EXEC mode.
show pfr border routes {bgp | cce | eigrp [parent] | rwatch | static}
Syntax Descriptionshow pfr border routes {bgp | cce | eigrp [parent] | rwatch | static}
Command Modes
Privileged EXEC (#)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Cisco IOS XE Release 3.1S |
This command was integrated into Cisco IOS XE Release 3.1S. |
Usage Guidelines
The show pfr border routes command is entered on a border router. This command is used to display information about PfR-controlled routes on a border router. You can display information about BGP or static routes.
The show pfr border routes cce command displays information about PfR-controlled traffic classes that are identified using Network-Based Application Recognition (NBAR).
Examples
The following example displays BGP-learned routes on a border router:
Router# show pfr border routes bgp
OER BR 10.1.1.2 ACTIVE, MC 10.1.1.3 UP/DOWN: UP 00:10:08,
Auth Failures: 0
Conn Status: SUCCESS, PORT: 3949
BGP table version is 12, local router ID is 10.10.10.2
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale
Origin codes: i - IGP, e - EGP, ? - incomplete
OER Flags: C - Controlled, X - Excluded, E - Exact, N - Non-exact, I - Injected
Network Next Hop OER LocPrf Weight Path
*> 10.1.0.0/16 10.40.40.2 CE 0 400 600 i
Table 32 describes the significant fields shown in the display.
The following example displays PfR-controlled routes that are identified using NBAR:
Router# show pfr border routes cce
Class-map oer-class-acl-oer_cce#2-stile-telnet, permit, sequence 0, mask 24
Match clauses:
ip address (access-list): oer_cce#2
stile: telnet
Set clauses:
ip next-hop 10.1.3.2
interface Ethernet2/3
Statistic:
Packet-matched: 60
Table 33 describes the significant fields shown in the display.
The following example displays EIGRP-controlled routes on a border router with information about the parent route that exists in the EIGRP routing table. In this example, the output shows that prefix 10.1.2.0/24 is being controlled by PfR. This command is used to show parent route lookup and route changes to existing parent routes when the parent route is identified from the EIGRP routing table.
Router# show pfr border routes eigrp
Flags: C - Controlled by oer, X - Path is excluded from control,
E - The control is exact, N - The control is non-exact
Flags Network Parent Tag
CE 10.1.2.0/24 10.0.0.0/8 5000
In this example, the parent keyword is used and more details are shown about the parent route lookup.
Router# show pfr border routes eigrp parent
Network Gateway Intf Flags
10.0.0.0/8 10.40.40.2 Ethernet4 1
Child Networks
Network Flag
Related Commands
|
|
|
|---|---|
pfr |
Enables a PfR process and configures a router as a PfR border router or as a PfR master controller. |
show pfr master
To display information about a Performance Routing (PfR) master controller, use the show pfr master command in privileged EXEC mode.
show pfr master
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Usage Guidelines
The show pfr master command is entered on a master controller. The output of this command displays information about the status of the PfR-managed network; the output includes information about the master controller, the border routers, PfR-managed interfaces, and default and user-defined policy settings.
Examples
The following example displays the status of a PfR-managed network on a master controller:
Router# show pfr master
OER state: ENABLED and ACTIVE
Conn Status: SUCCESS, PORT: 3949
Number of Border routers: 2
Number of Exits: 2
Number of monitored prefixes: 10 (max 5000)
Border Status UP/DOWN AuthFail
10.4.9.7 ACTIVE UP 02:54:40 0
10.4.9.6 ACTIVE UP 02:54:40 0
Global Settings:
max-range-utilization percent 20
mode route metric bgp local-pref 5000
mode route metric static tag 5000
trace probe delay 1000
logging
Default Policy Settings:
backoff 300 3000 300
delay relative 50
holddown 300
periodic 0
mode route control
mode monitor both
mode select-exit best
loss relative 10
unreachable relative 50
resolve delay priority 11 variance 20
resolve utilization priority 12 variance 20
Learn Settings:
current state : SLEEP
time remaining in current state : 4567 seconds
throughput
delay
no protocol
monitor-period 10
periodic-interval 20
aggregation-type bgp
prefixes 100
expire after time 720
Table 34 describes the significant fields shown in the display.
Related Commands
|
|
|
|---|---|
pfr |
Enables a PfR process and configures a router as a PfR border router or as a PfR master controller. |
show pfr master active-probes
To display connection and status information about active probes on a Performance Routing (PfR) master controller, use the show pfr master active-probes command in privileged EXEC mode.
show pfr master active-probes [appl | forced]
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Usage Guidelines
The show pfr master active-probes command is entered on a master controller. This command is used to display the status of active probes. The output from this command displays the active probe type and destination, the border router that is the source of the active probe, the target prefixes that are used for active probing, and whether the probe was learned or configured. Entering the appl keyword filters the output to display information about applications optimized by the master controller. Entering the forced keyword filters the output to display information about voice traffic that is configured with a forced target assignment optimized by the master controller.
Examples
The following example shows the status of configured and running active probes:
Router# show pfr master active-probes
OER Master Controller active-probes
Border = Border Router running this Probe
State = Un/Assigned to a Prefix
Prefix = Probe is assigned to this Prefix
Type = Probe Type
Target = Target Address
TPort = Target Port
How = Was the probe Learned or Configured
N - Not applicable
State Prefix Type Target TPort How
Assigned 10.1.1.1/32 echo 10.1.1.1 N Lrnd
Assigned 10.1.4.0/24 echo 10.1.4.1 N Lrnd
Assigned 10.1.2.0/24 echo 10.1.2.1 N Lrnd
Assigned 10.1.4.0/24 udp-echo 10.1.4.1 65534 Cfgd
Assigned 10.1.3.0/24 echo 10.1.3.1 N Cfgd
Assigned 10.1.2.0/24 tcp-conn 10.1.2.1 23 Cfgd
The following Probes are running:
Border State Prefix Type Target TPort
192.168.2.3 ACTIVE 10.1.4.0/24 udp-echo 10.1.4.1 65534
172.16.1.1 ACTIVE 10.1.2.0/24 tcp-conn 10.1.2.1 23
Table 35 describes the significant fields shown in the display.
The following example shows the status of configured and running active probes when a jitter probe has been configured:
Router# show pfr master active-probes
OER Master Controller active-probes
Border = Border Router running this Probe
State = Un/Assigned to a Prefix
Prefix = Probe is assigned to this Prefix
Type = Probe Type
Target = Target Address
TPort = Target Port
How = Was the probe Learned or Configured
N - Not applicable
The following Probes exist:
State Prefix Type Target TPort How codec
Assigned 10.1.1.0/24 jitter 10.1.1.10 2000 Cfgd g711ulaw
Assigned 10.1.1.0/24 echo 10.1.1.2 N Lrnd N
The following Probes are running:
Border State Prefix Type Target TPort
10.1.1.2 ACTIVE 10.1.1.0/24 jitter 10.1.1.10 2000
10.1.1.2 ACTIVE 10.1.1.0/24 echo 10.1.1.6 N
10.2.2.3 ACTIVE 10.1.1.0/24 jitter 10.1.1.10 2000
10.2.2.3 ACTIVE 10.1.1.0/24 echo 10.1.1.6 N
10.1.1.1 ACTIVE 10.1.1.0/24 jitter 10.1.1.10 2000
10.1.1.1 ACTIVE 10.1.1.0/24 echo 10.1.1.6 N
Table 36 describes the significant fields shown in the display that are different from those in Table 35.
Related Commands
show pfr master appl
To display information about application traffic classes that are monitored and controlled by a Performance Routing (PfR) master controller, use the show pfr master appl command in privileged EXEC mode.
show pfr master appl [access-list name] [detail] [learned [delay | throughput]] | [tcp | udp] [protocol-number] [min-port max-port] [dst | src] [detail | policy]
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Usage Guidelines
The show pfr master appl command is entered on a PfR master controller. This command is used to display information about application traffic classes that are configured for monitoring and optimization.
Examples
The following example shows TCP application traffic filtered based on port 80 (HTTP):
Router# show pfr master appl tcp 80 80 dst policy
Prefix Appl Prot Port Port Type Policy
--------------------------------------------------------------------------------
10.1.0.0/16 tcp [80, 80] dst 20
10.1.1.0/24 tcp [80, 80] dst 10
Table 37 describes the significant fields shown in the display.
The following example shows information about learned application traffic classes:
Router# show pfr master appl learned
PfR 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 Score
Los - Packet Loss (packets-per-million), Un - Unreachable (flows-per-million),
E - Egress, I - Ingress, Bw - Bandwidth (kbps), N - Not applicable
U - unknown, * - uncontrolled, + - control more specific, @ - active probe all
# - Prefix monitor mode is Special, & - Blackholed Prefix
% - Force Next-Hop, ^ - Prefix is denied
Prefix Prot Port [src][dst] DSCP Source Prefix
State Time Curr BR CurrI/F Proto
PasSDly PasLDly PasSUn PasLUn PasSLos PasLLos
ActSDly ActLDly ActSUn ActLUn EBw IBw
ActSJit ActPMOS
--------------------------------------------------------------------------------
10.1.1.0/24 udp [1, 65535] [3000, 4000] ef 0.0.0.0/0
INPOLICY* @70 1.1.1.2 Et0/0 PBR
U U 0 0 0 0
11 7 0 0 1 0
N N
10.1.3.0/24 udp [1, 65535] [3000, 4000] ef 0.0.0.0/0
INPOLICY* @70 1.1.1.2 Et0/0 PBR
U U 0 0 0 0
3 4 0 0 1 0
N N
Table 38 describes the significant fields shown in the display that are different from those in Table 37.
The following example shows information about application traffic classes learned using delay as the learning criterion:
Router# show pfr master appl learned delay
OER 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 Score
Los - Packet Loss (packets-per-million), Un - Unreachable (flows-per-million),
E - Egress, I - Ingress, Bw - Bandwidth (kbps), N - Not applicable
U - unknown, * - uncontrolled, + - control more specific, @ - active probe all
# - Prefix monitor mode is Special, & - Blackholed Prefix
% - Force Next-Hop, ^ - Prefix is denied
Prefix Prot Port [src][dst] DSCP Source Prefix
State Time Curr BR CurrI/F Proto
PasSDly PasLDly PasSUn PasLUn PasSLos PasLLos
ActSDly ActLDly ActSUn ActLUn EBw IBw
ActSJit ActPMOS
--------------------------------------------------------------------------------
10.1.3.0/24 udp [1, 65535] [3000, 4000] ef 0.0.0.0/0
INPOLICY* @70 1.1.1.2 Et0/0 PBR
U U 0 0 0 0
3 4 0 0 1 0
N N
The following example shows information about application traffic classes learned using throughput as the learning criterion:
Router# show pfr master appl learned throughput
OER 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 Score
Los - Packet Loss (packets-per-million), Un - Unreachable (flows-per-million),
E - Egress, I - Ingress, Bw - Bandwidth (kbps), N - Not applicable
U - unknown, * - uncontrolled, + - control more specific, @ - active probe all
# - Prefix monitor mode is Special, & - Blackholed Prefix
% - Force Next-Hop, ^ - Prefix is denied
Prefix Prot Port [src][dst] DSCP Source Prefix
State Time Curr BR CurrI/F Proto
PasSDly PasLDly PasSUn PasLUn PasSLos PasLLos
ActSDly ActLDly ActSUn ActLUn EBw IBw
ActSJit ActPMOS
--------------------------------------------------------------------------------
10.1.1.0/24 udp [1, 65535] [3000, 4000] ef 0.0.0.0/0
INPOLICY* @70 1.1.1.2 Et0/0 PBR
U U 0 0 0 0
11 7 0 0 1 0
N N
Related Commands
|
|
|
|---|---|
pfr |
Enables a PfR process and configures a router as a PfR border router or as a PfR master controller. |
show pfr master border
To display the status of connected Performance Routing (PfR) border routers, use the show pfr master border command in privileged EXEC mode.
show pfr master border [ip-address] [detail | report | topology]
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Usage Guidelines
The show pfr master border command and all the keywords are entered on a master controller. The output of this command shows the status of connections with border routers.
Examples
The following example displays the status of border router connections with a master controller:
Router# show pfr master border
OER state: ENABLED and ACTIVE
Conn Status: SUCCESS, PORT: 3949
Version: 2.2
Number of Border routers: 3
Number of Exits: 3
Number of monitored prefixes: 1 (max 5000)
Max prefixes: total 5000 learn 2500
Prefix count: total 1, learn 0, cfg 1
PBR Requirements met
Nbar Status: Inactive
Border Status UP/DOWN AuthFail Version
10.165.201.5 ACTIVE UP 00:05:29 0 2.2
10.165.201.6 ACTIVE UP 00:05:29 0 2.2
10.165.201.7 ACTIVE UP 00:05:29 0 2.2
Table 39 describes the significant fields shown in the display. All the other fields in the output are self-explanatory.
The following example displays detailed information about border router connections with a master controller:
Router# show pfr master border detail
Border Status UP/DOWN AuthFail Version
10.1.1.2 ACTIVE UP 14:03:40 0 3.0
Et2/0 EXTERNAL UP
Et0/0 INTERNAL UP
Et1/0 EXTERNAL UP
External Capacity Max BW BW Used Load Status Exit Id
Interface (kbps) (kbps) (kbps) (%)
--------- -- -------- ------ ------- ---- ------ -------
Et2/0 Tx 800 600 226 28 UP 2
Rx 800 0 0
Et1/0 Tx 800 600 97 12 UP 1
Rx 800 55 6
Table 40 describes the significant fields shown in the display.
The following example displays whether the PBR requirement for the application control by PfR is met or not:
Router# show pfr master border topology
LocalBR LocalEth RemoteBR RemoteEth nbar_type
--------------------------------------------------------------------------------
10.165.201.4 Ethernet0/0 10.165.202.2 Ethernet0/0 Directly Connected
10.165.201.4 Ethernet0/0 10.165.201.3 Ethernet0/0 Directly Connected
10.165.201.3 Ethernet0/0 10.165.201.4 Ethernet0/0 Directly Connected
10.165.201.3 Ethernet0/0 10.165.201.3 Ethernet0/0 Directly Connected
10.165.201.2 Ethernet0/0 10.165.201.4 Ethernet0/0 Directly Connected
10.165.201.2 Ethernet0/0 10.165.201.2 Ethernet0/0 Directly Connected
PBR Requirements met
Table 41 describes the significant fields shown in the display.
The following example displays the border router link report:
Router# show pfr master border report
Border Status UP/DOWN AuthFail Version
10.165.202.132 ACTIVE UP 00:05:54 0 2.2
10.165.202.131 ACTIVE UP 00:05:57 0 2.2
10.165.202.130 ACTIVE UP 00:06:00 0 2.2
10.165.202.129 ACTIVE UP 00:06:03 0 2.2
Table 42 describes the significant fields shown in the display.
Related Commands
|
|
|
|---|---|
pfr |
Enables a PfR process and configures a router as a PfR border router or as a PfR master controller. |
show pfr master cost-minimization
To display the status of cost-based optimization policies, use the show pfr master cost-minimization command in privileged EXEC mode.
show pfr master cost-minimization {billing-history | border ip-address [interface] | nickname name}
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Usage Guidelines
The show pfr master cost-minimization command is entered on a master controller. The output of this command shows the status of cost-based policies.
Examples
The following example displays the billing history for cost policies:
Router# show pfr master cost-minimization billing-history
Billing History for the past three months
ISP2 on 10.1.1.2 Ethernet0/0
80-percent on 10.1.1.1 Ethernet0/0
Mon1 Mon2 Mon3
Nickname SustUtil Cost SustUtil Cost SustUtil Cost
---------- ------------------ ------------------ ------------------
ISP2 ---NA--- 1737222676 1737222676 ---NA---
80-percent ---NA--- 1737231684 1737231684 ---NA---
---------- ------------------ ------------------ ------------------
Total Cost 0 3474454360 0
Table 43 describes the significant fields shown in the display.
The following example displays cost optimization information only for Ethernet interface 1/0:
Router# show pfr master cost-minimization border 10.1.1.2 Ethernet1/0
Nickname : ispname Border: 10.1.1.2 Interface: Et1/0
Calc type : Combined
Start Date: 20
Fee : Tier Based
Tier1 : 100, fee: 10000
Tier2 : 90, fee: 9000
Period : Sampling 22, Rollup 1400
Discard : Type Percentage, Value 22
Rollup Information:
Total Discard Left Collected
60 13 36 0
Current Rollup Information:
MomentaryTgtUtil: 7500 Kbps CumRxBytes: 38669
StartingRollupTgt: 7500 Kbps CumTxBytes: 39572
CurrentRollupTgt: 7500 Kbps TimeRemain: 09:11:01
Rollup Utilization (Kbps):
Egress/Ingress Utilization Rollups (Descending order)
1 : 0 2 : 0
Table 44 describes the significant fields shown in the display.
The following example displays cost optimization information for the specified service provider:
Router# show pfr master cost-minimization nickname ISP1
Nickname : ISP1 Border: 10.1.1.2 Interface: Et1/0
Calc type : Combined
Start Date: 20
Fee : Tier Based
Tier1 : 100, fee: 10000
Tier2 : 90, fee: 9000
Period : Sampling 22, Rollup 1400
Discard : Type Percentage, Value 22
Rollup Information:
Total Discard Left Collected
60 13 36 0
Current Rollup Information:
MomentaryTgtUtil: 7500 Kbps CumRxBytes: 38979
StartingRollupTgt: 7500 Kbps CumTxBytes: 39692
CurrentRollupTgt: 7500 Kbps TimeRemain: 09:10:49
Rollup Utilization (Kbps):
Egress/Ingress Utilization Rollups (Descending order)
1 : 0 2 : 0
Related Commands
show pfr master defined application
To display information about user-defined application definitions on a Performance Routing (PfR) master controller, use the show pfr master defined application command in privileged EXEC mode.
show pfr master defined application
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Usage Guidelines
The show pfr master defined application command is entered on a PfR master controller. This command displays all applications that are user-defined. To define a custom application to be used by PfR, use the application define (PfR) command on the PfR master controller.
To display the same information on a PfR border router, use the show pfr border defined application command.
Examples
The following partial example output shows information about the user-defined applications configured for use with PfR:
Router# show pfr master defined application
OER Defined Applications:
Name Appl_ID Dscp Prot SrcPort DstPort SrcPrefix
--------------------------------------------------------------------------------
telnet 1 defa tcp 23-23 1-65535 0.0.0.0/0
telnet 1 defa tcp 1-65535 23-23 0.0.0.0/0
ftp 2 defa tcp 21-21 1-65535 0.0.0.0/0
ftp 2 defa tcp 1-65535 21-21 0.0.0.0/0
cuseeme 4 defa tcp 7648-7648 1-65535 0.0.0.0/0
cuseeme 4 defa tcp 7649-7649 1-65535 0.0.0.0/0
cuseeme 4 defa tcp 1-65535 7648-7648 0.0.0.0/0
dhcp 5 defa udp 68-68 67-67 0.0.0.0/0
dns 6 defa tcp 53-53 1-65535 0.0.0.0/0
dns 6 defa tcp 1-65535 53-53 0.0.0.0/0
dns 6 defa udp 53-53 1-65535 0.0.0.0/0
dns 6 defa udp 1-65535 53-53 0.0.0.0/0
finger 7 defa tcp 79-79 1-65535 0.0.0.0/0
finger 7 defa tcp 1-65535 79-79 0.0.0.0/0
gopher 8 defa tcp 70-70 1-65535 0.0.0.0/0
.
.
.
Table 45 describes the significant fields shown in the display.
Related Commands
show pfr master learn list
To display configuration information about Performance Routing (PfR) learn lists, use the show pfr master learn list command in privileged EXEC mode.
show pfr master learn list [list-name]
Syntax Description
list-name |
(Optional) Name of a learn list. |
Command Modes
Privileged EXEC (#)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Usage Guidelines
The show pfr master learn list command is entered on a PfR master controller. This command is used to display configuration information about learn lists. Learn lists are a way to categorize learned traffic classes. In each learn list, different criteria for learning traffic classes including prefixes, application definitions, filters, and aggregation parameters 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.
Examples
The following example shows how to display configuration information about two learn lists, LIST1 and LIST2:
Router# show pfr master learn list
Learn-List LIST1 10
Configuration:
Application: ftp
Aggregation-type: bgp
Learn type: thruput
Policies assigned: 8 10
Stats:
Application Count: 0
Application Learned:
Learn-List LIST2 20
Configuration:
Application: telnet
Aggregation-type: prefix-length 24
Learn type: thruput
Policies assigned: 5 20
Stats:
Application Count: 2
Application Learned:
Appl Prefix 10.1.5.0/24 telnet
Appl Prefix 10.1.5.16/28 telnet
Table 46 describes the significant fields shown in the display.
Related Commands
|
|
|
|---|---|
pfr |
Enables a PfR process and configures a router as a PfR border router or as a PfR master controller. |
show pfr master link-group
To display information about Performance Routing (PfR) link groups, use the show pfr master link-group command in privileged EXEC mode.
show pfr master link-group [link-group-name]
Syntax Description
link-group-name |
(Optional) Name of a link group. |
Command Modes
Privileged EXEC (#)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Usage Guidelines
The show pfr master link-group command is entered on a PfR master controller. This command is used to display information about link groups including the link group name, the border router, and the interface on the border router that is the exit link, and the ID of the exit link.
Link groups are used to define a group of exit links as a preferred set of links or as a fallback set of links for PfR to use when optimizing a specified traffic class. Up to three link groups can be specified for each interface. Use the link-group (PfR) command to define the link group for an interface, and use the set link-group (PfR) command to define the primary link group and a fallback link group for a specified traffic class in an PfR map.
Examples
The following example displays information about all configured link groups:
Router# show pfr master link-group
link group video
Border Interface Exit id
192.168.1.2 Serial2/0 1
link group voice
Border Interface Exit id
192.168.1.2 Serial2/0 1
192.168.1.2 Serial3/0 2
192.168.3.2 Serial4/0 4
link group data
Border Interface Exit id
192.168.3.2 Serial3/0 3
Table 47 describes the significant fields shown in the display.
The following example displays information only about the link group named voice:
Router# show pfr master link-group voice
link group voice
Border Interface Exit id
192.168.1.2 Serial2/0 1
192.168.1.2 Serial3/0 2
192.168.3.2 Serial4/0 4
Related Commands
show pfr master nbar application
To display information about the status of an application identified using Network-Based Application Recognition (NBAR) for each Performance Routing (PfR) border router, use the show pfr master nbar application command in privileged EXEC mode.
show pfr master nbar application
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Usage Guidelines
The show pfr master nbar application command is entered on a PfR master controller. This command is used to verify the validity of an application that is identified using NBAR at each PfR border router. If the NBAR application is not supported on one or more border routers, all the traffic classes related to that NBAR application are marked inactive and cannot be optimized using PfR.
NBAR is capable of identifying applications based on the following three types of protocols:
•Non-UDP and non-TCP IP protocols—For example, Generic Routing Encapsulation (GRE) and Internet Control Message Protocol (ICMP).
•TCP and UDP protocols that use statically assigned port numbers—For example, CU-SeeMe desktop video conference (CU-SeeMe-Server) and Post Office Protocol over Transport Layer Security (TLS) and Secure Sockets Layer (SSL) server (SPOP3-Server).
•TCP and UDP protocols that dynamically assign port numbers and require stateful inspection—For example, Real-Time Transport Protocol audio streaming (RTP-audio) and BitTorrent File Transfer Traffic (BitTorrent).
The list of applications identified using NBAR and available for profiling of PfR traffic classes is constantly evolving. For lists of many of the NBAR applications defined using static or dynamically assigned ports, see the "Performance Routing with NBAR/CCE Application Recognition" module.
For more details about NBAR, see the "Classifying Network Traffic Using NBAR" section of the Cisco IOS Quality of Service Solutions Configuration Guide.
Examples
The following partial output shows information about the status of a number of applications identified using NBAR at three PfR border routers. In this example, applications based on BGP, BitTorrent, and HTTP protocols are valid at all three PfR border routers, and traffic classes for these applications are active. While applications such as ConnectionLess Network Service (CLNS) and KaZaA are invalid on at least one border router, all traffic classes based on these application are marked inactive.
Router# show pfr master nbar application
NBAR Appl 10.1.1.4 10.1.1.2 10.1.1.3
-------------------------------------------------------------------
aarp Invalid Invalid Invalid
appletalk Invalid Invalid Invalid
arp Invalid Invalid Invalid
bgp Valid Valid Valid
bittorrent Valid Valid Valid
bridge Invalid Invalid Invalid
bstun Invalid Invalid Invalid
cdp Invalid Invalid Invalid
citrix Invalid Invalid Invalid
clns Valid Invalid Invalid
clns_es Invalid Invalid Invalid
clns_is Invalid Invalid Invalid
cmns Invalid Invalid Invalid
compressedtcp Invalid Invalid Invalid
cuseeme Invalid Invalid Invalid
decnet Invalid Invalid Invalid
decnet_node Invalid Invalid Invalid
decnet_router-l1 Invalid Invalid Invalid
decnet_router-l2 Invalid Invalid Invalid
dhcp Invalid Invalid Invalid
directconnect Invalid Invalid Invalid
dlsw Invalid Invalid Invalid
dns Invalid Invalid Invalid
edonkey Invalid Invalid Invalid
egp Invalid Invalid Invalid
eigrp Invalid Invalid Invalid
exchange Invalid Invalid Invalid
fasttrack Invalid Invalid Invalid
finger Invalid Invalid Invalid
ftp Invalid Invalid Invalid
gnutella Invalid Invalid Invalid
Morpheus Invalid Invalid Invalid
gopher Invalid Invalid Invalid
gre Invalid Invalid Invalid
h323 Invalid Invalid Invalid
http Valid Valid Valid
icmp Invalid Invalid Invalid
imap Invalid Invalid Invalid
ip Invalid Invalid Invalid
ipinip Invalid Invalid Invalid
ipsec Invalid Invalid Invalid
ipv6 Invalid Invalid Invalid
ipx Invalid Invalid Invalid
irc Invalid Invalid Invalid
kazaa2 Valid Invalid Valid
.
.
.
Table 48 describes the significant fields shown in the display.
Related Commands
show pfr master policy
To display policy settings on a Performance Routing (PfR) master controller, use the show pfr master policy command in privileged EXEC mode.
show pfr master policy {sequence-number | policy-name | default | dynamic}
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Usage Guidelines
The show pfr master policy command is entered on a master controller. The output of this command displays default policy and policies configured with a PfR map.
The PfR application provider interface (API) 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 is defined as an entity outside the network in which the router configured as an PfR master controller exists, for example, an ISP, or a branch office of the same company. The provider has one or more host devices running one or more applications that use the PfR API to communicate with a PfR master controller. The PfR API allows applications running on a host device in the provider network to dynamically create policies to influence the existing traffic classes, or specify new traffic class criteria. The dynamic keyword displays the policies dynamically created by an API provider application.
Examples
The following example displays default policy and policies configured in a PfR map named CUSTOMER. The asterisk(*) character is displayed next to policy settings that override default settings.
Router# show pfr master policy
* Overrides Default Policy Setting
Default Policy Settings:
backoff 300 3000 300
delay relative 50
holddown 300
periodic 0
mode route control
mode monitor both
mode select-exit best
loss relative 10
unreachable relative 50
resolve delay priority 11 variance 20
resolve utilization priority 12 variance 20
pfr-map CUSTOMER 10
match ip prefix-lists: NAME
backoff 300 3000 300
delay relative 50
holddown 300
periodic 0
mode route control
mode monitor both
mode select-exit best
loss relative 10
unreachable relative 50
*resolve utilization priority 1 variance 10
*resolve delay priority 11 variance 20
*probe frequency 30
pfr-map CUSTOMER 20
match ip prefix-lists:
match pfr learn delay
backoff 300 3000 300
delay relative 50
holddown 300
periodic 0
*mode route control
mode monitor both
mode select-exit best
loss relative 10
unreachable relative 50
resolve delay priority 11 variance 20
resolve utilization priority 12 variance 20
Table 49 describes the significant fields shown in the display.
The following example displays dynamic policies created by applications using the PfR application interface. The asterisk(*) character is displayed next to policy settings that override default settings.
Router# show pfr master policy dynamic
Dynamic Policies:
proxy id 10.3.3.3
sequence no. 18446744069421203465, provider id 1001, provider priority 65535
host priority 65535, policy priority 101, Session id 9
backoff 90 90 90
delay relative 50
holddown 90
periodic 0
probe frequency 56
mode route control
mode monitor both
mode select-exit good
loss relative 10
jitter threshold 20
mos threshold 3.60 percent 30
unreachable relative 50
next-hop not set
forwarding interface not set
resolve delay priority 11 variance 20
resolve utilization priority 12 variance 20
proxy id 10.3.3.3
sequence no. 18446744069421269001, provider id 1001, provider priority 65535
host priority 65535, policy priority 102, Session id 9
backoff 90 90 90
delay relative 50
holddown 90
periodic 0
probe frequency 56
mode route control
mode monitor both
mode select-exit good
loss relative 10
jitter threshold 20
mos threshold 3.60 percent 30
unreachable relative 50
next-hop not set
forwarding interface not set
resolve delay priority 11 variance 20
resolve utilization priority 12 variance 20
proxy id 10.3.3.4
sequence no. 18446744069421334538, provider id 1001, provider priority 65535
host priority 65535, policy priority 103, Session id 10
backoff 90 90 90
delay relative 50
holddown 90
periodic 0
probe frequency 56
mode route control
mode monitor both
mode select-exit good
loss relative 10
jitter threshold 20
mos threshold 3.60 percent 30
unreachable relative 50
next-hop not set
forwarding interface not set
resolve delay priority 11 variance 20
resolve utilization priority 12 variance 20
Table 50 describes the significant fields shown in the display.
Related Commands
show pfr master prefix
To display the status of monitored prefixes, use the show pfr master prefix command in privileged EXEC mode.
show pfr master prefix [detail | inside [detail] | learned [delay | inside | throughput] | prefix [detail | policy | report | traceroute [exit-id | border-address | current] [now]]]
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Usage Guidelines
The show pfr master prefix command is entered on a master controller. This command is used to display the status of monitored prefixes. The output from this command includes information about the source border router, current exit interface, prefix delay, and egress and ingress interface bandwidth. The output can be filtered to display information for only a single prefix, learned prefixes, inside prefixes, and prefixes learned based on delay or throughput.
The traceroute keyword is used to display traceroute probe results. The output generated by this keyword provides hop by hop statistics to the probe target network. The output can be filtered to display information only for the exit ID (PfR assigns an ID number to each exit interface) or for the specified border router. The current keyword displays traceroute probe results from the most recent traceroute probe. The now keyword initiates a new traceroute probe and displays the results.
Examples
The following example shows the status of a monitored prefix:
Router# show pfr master prefix
OER Prefix Stats:
Dly: Delay in ms
EBw: Egress Bandwidth
IBw: Ingress Bandwidth
Prefix State Curr BR CurrI/F Dly EBw IBw
----------------------------------------------------------
10.1.5.0/24 INPOLICY 10.1.1.2 Et1/0 19 1 1
Table 51 describes the significant fields shown in the display.
The following output shows the detailed status of a monitored prefix:
Router# show pfr master prefix detail
Prefix: 10.1.1.0/26
State: DEFAULT* Time Remaining: @7
Policy: Default
Policy: Default
Most recent data per exit
Border Interface PasSDly PasLDly ActSDly ActLDly
*10.2.1.1 Et1/0 181 181 250 250
10.2.1.2 Et2/0 0 0 351 351
10.3.1.2 Et3/0 0 0 94 943
Latest Active Stats on Current Exit:
Type Target TPort Attem Comps DSum Min Max Dly
echo 10.1.1.1 N 2 2 448 208 240 224
echo 10.1.1.2 N 2 2 488 228 260 244
echo 10.1.1.3 N 2 2 568 268 300 284
Prefix performance history records
Current index 2, S_avg interval(min) 5, L_avg interval(min) 60
Age Border Interface OOP/RteChg Reasons
Pas: DSum Samples DAvg PktLoss Unreach Ebytes Ibytes Pkts Flows
Act: Dsum Attempts DAvg Comps Unreach
00:00:03 10.1.1.1 Et1/0
0 0 0 0 0 0 0 0 0
1504 6 250 6 0
Table 52 describes the significant fields shown in the display.
The following example shows prefix statistics from a traceroute probing:
Router# show pfr master prefix 10.1.5.0/24 traceroute
* - current exit, + - control more specific
Ex - Exit ID, Delay in msec
--------------------------------------------------------------------------------
Path for Prefix: 10.1.5.0/24 Target: 10.1.5.2
Exit ID: 2, Border: 10.1.1.3 External Interface: Et1/0
Status: DONE, How Recent: 00:00:08 minutes old
Hop Host Time(ms) BGP
1 10.1.4.2 8 0
2 10.1.3.2 8 300
3 10.1.5.2 20 50
--------------------------------------------------------------------------------
Exit ID: 1, Border: 10.1.1.2 External Interface: Et1/0
Status: DONE, How Recent: 00:00:06 minutes old
Hop Host Time(ms) BGP
1 0.0.0.0 3012 0
2 10.1.3.2 12 100
3 10.1.5.2 12 50
--------------------------------------------------------------------------------
Table 53 describes the significant fields shown in the display.
The following example shows prefix statistics including Jitter and MOS percentage values when the Jitter probe is configured for the 10.1.5.0 prefix:
Router# show pfr master prefix 10.1.5.0/24
OER Prefix Statistics:
Pas - Passive, Act - Active, S - Short term, L - Long term, Dly - Delay (ms),
P - Percentage below threshold, Jit - Jitter, MOS - Mean Opinion Score,
Los - Packet Loss (packets-per-million), Un - Unreachable (flows-per-million),
E - Egress, I - Ingress, Bw - Bandwidth (kbps), N - Not applicable
U - unknown, * - uncontrolled, + - control more specific, @ - active probe all
Prefix State Time Curr BR CurrI/F Protocol
PasSDly PasLDly PasSUn PasLUn PasSLos PasLLos
ActSDly ActLDly ActSUn ActLUn EBw IBw
%ActSJit %ActPMOS
--------------------------------------------------------------------------------
10.1.1.0/24 DEFAULT* @3 10.1.1.1 Et5/0 U
U U 0 0 0 0
6 6 400000 400000 17 1
1.45 25
Table 54 describes the significant fields shown in the display that are different from Table 51 and Table 52.
The following example shows detailed prefix statistics when Jitter or MOS are configured as a priority:
Router# show pfr master prefix 10.1.1.0/24 detail
Prefix: 10.1.1.0/24
State: DEFAULT* Time Remaining: @9
Policy: Default
Most recent data per exit
Border Interface PasSDly PasLDly ActSDly ActLDly
*10.1.1.1 Et5/0 0 0 6 6
10.2.2.3 Et2/0 0 0 7 7
10.1.1.2 Et0/0 0 0 14 14
Most recent voice data per exit
Border Interface ActSJit ActPMOS
*10.1.1.1 Et5/0 2.00 0
10.2.2.3 Et2/0 2.01 20
10.1.1.2 Et0/0 4.56 50
Latest Active Stats on Current Exit:
Type Target TPort Attem Comps DSum Min Max Dly
udpJit 10.1.1.8 2000 2 2 8 4 4 4
udpJit 10.1.1.7 3000 2 2 20 4 16 10
udpJit 10.1.1.6 4000 2 2 8 4 4 4
echo 10.1.1.4 N 2 0 0 0 0 0
echo 10.1.1.3 N 2 0 0 0 0 0
Latest Voice Stats on Current Exit:
Type Target TPort Codec Attem Comps JitSum MOS
udpJit 10.1.1.8 2000 g711alaw 2 2 2.34 4.56
udpJit 10.1.1.7 3000 g711ulaw 2 2 2.56 4.11
udpJit 10.1.1.6 4000 g729a 2 2 1.54 3.57
udpJit 10.1.1.5 4500 none 2 2 1.76 NA
Prefix performance history records
Current index 3, S_avg interval(min) 5, L_avg interval(min) 60
Age Border Interface OOP/RteChg Reasons
Pas: DSum Samples DAvg PktLoss Unreach Ebytes Ibytes Pkts Flows
Act: Dsum Attempts DAvg Comps Unreach Jitter LoMOSCnt MOSCn
00:00:07 10.1.1.1 Et5/0
0 0 0 0 0 5920 0 148 1
36 10 6 6 4 2 1 1
00:01:07 10.1.1.1 Et5/0
0 0 0 0 0 12000 12384 606 16
36 10 6 6 4 3 0 1
00:02:07 10.1.1.1 Et5/0
0 0 0 0 0 409540 12040 867 9
36 10 6 6 4 15 1 1
Table 55 describes the significant fields shown in the display that are different from Table 52.
The following example shows prefix statistics including information about application interface provider report requests for the 10.1.1.0 prefix:
Router# show pfr master prefix 10.1.1.0/24 report
Prefix Performance Report Request
Created by: Provider 1001, Host 10.3.3.3, Session 9
Last report sent 3 minutes ago, context 589855, frequency 4 min
Prefix Performance Report Request
Created by: Provider 1001, Host 10.3.3.4, Session 10
Last report sent 1 minutes ago, context 655372, frequency 3 min
OER 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 Score
Los - Packet Loss (packets-per-million), Un - Unreachable (flows-per-million),
E - Egress, I - Ingress, Bw - Bandwidth (kbps), N - Not applicable
U - unknown, * - uncontrolled, + - control more specific, @ - active probe all
# - Prefix monitor mode is Special, & - Blackholed Prefix
% - Force Next-Hop, ^ - Prefix is denied
Prefix State Time Curr BR CurrI/F Protocol
PasSDly PasLDly PasSUn PasLUn PasSLos PasLLos
ActSDly ActLDly ActSUn ActLUn EBw IBw
ActSJit ActPMOS ActSLos ActLLos
--------------------------------------------------------------------------------
10.1.1.0/24 INPOLICY 0 10.3.3.3 Et4/3 BGP
N N N N N N
138 145 0 0 N N
N N
Table 56 describes the significant fields shown in the display that are different from Table 51, Table 53 and Table 55.
PIRO provides the ability for PfR to search for a parent route—an exact matching route, or a less specific route—in any IP Routing Information Base (RIB). The following example shows that the protocol displayed for the prefix 10.1.0.0 is RIB-PBR, which means that the parent route for the traffic class exists in the RIB and policy-based routing is used to control the prefix.
Router# show pfr master prefix 10.1.0.0
OER 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 Score
Los - Packet Loss (packets-per-million), Un - Unreachable (flows-per-million),
E - Egress, I - Ingress, Bw - Bandwidth (kbps), N - Not applicable
U - unknown, * - uncontrolled, + - control more specific, @ - active probe all
# - Prefix monitor mode is Special, & - Blackholed Prefix
% - Force Next-Hop, ^ - Prefix is denied
Prefix State Time Curr BR CurrI/F Protocol
PasSDly PasLDly PasSUn PasLUn PasSLos PasLLos
ActSDly ActLDly ActSUn ActLUn EBw IBw
ActSJit ActPMOS ActSLos ActLLos
--------------------------------------------------------------------------------
10.1.0.0/24 INPOLICY 0 10.11.1.3 Et1/0 RIB-PBR
129 130 0 0 214 473
U U 0 0 33 3
N N
EIGRP route control provides the ability for PfR to search for a parent route—an exact matching route, or a less specific route—in the EIGRP routing table. In this example, the protocol displayed for the prefix 10.1.0.0 is EIGRP and this means that the parent route for the traffic class exists in the EIGRP routing table and OER is controlling the prefix.
Router# show pfr master prefix 10.1.0.0
OER 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 Score
Los - Packet Loss (packets-per-million), Un - Unreachable (flows-per-million),
E - Egress, I - Ingress, Bw - Bandwidth (kbps), N - Not applicable
U - unknown, * - uncontrolled, + - control more specific, @ - active probe all
# - Prefix monitor mode is Special, & - Blackholed Prefix
% - Force Next-Hop, ^ - Prefix is denied
Prefix State Time Curr BR CurrI/F Protocol
PasSDly PasLDly PasSUn PasLUn PasSLos PasLLos
ActSDly ActLDly ActSUn ActLUn EBw IBw
ActSJit ActPMOS
--------------------------------------------------------------------------------
10.1.0.0/16 DEFAULT* @69 10.1.1.1 Gi1/22 EIGRP
U U 0 0 0 0
U U 0 0 22 8
N N
Related Commands
show pfr master traffic-class
To display information about traffic classes that are monitored and controlled by a Performance Routing (PfR) master controller, use the show pfr master traffic-class command in privileged EXEC mode.
show pfr master traffic-class [access-list access-list-name | application application-name [prefix] | inside | learned [delay | inside | list list-name | throughput] | prefix prefix | prefix-list prefix-list-name] [active] [passive] [status] [detail]
Syntax Description
access-list |
(Optional) Displays information about traffic classes defined by an access list. |
access-list-name |
(Optional) Name of an access list. Names cannot contain either a space or quotation marks and must begin with an alphabetic character to distinguish them from numbered access lists. |
application |
(Optional) Displays information about application traffic classes. |
application-name |
(Optional) Name of a predefined static application using fixed ports. See Table 57. |
prefix |
(Optional) An IP address and bit length mask representing a prefix to be cleared. |
inside |
(Optional) Displays information about inside traffic classes. |
learned |
(Optional) Displays information about learned traffic classes. |
delay |
(Optional) Displays information about learned traffic classes defined using delay. |
list |
(Optional) Displays information about learned traffic classes defined in a PfR learn list. |
list-name |
(Optional) Name of an PfR learn list. |
throughput |
(Optional) Displays information about learned traffic classes defined using throughput. |
prefix |
(Optional) Displays information about traffic classes defined by a specified destination prefix. |
prefix-list |
(Optional) Displays information about traffic classes defined by a prefix list. |
prefix-list-name |
(Optional) Name of a prefix list. Names cannot contain either a space or quotation marks and must begin with an alphabetic character to distinguish them from numbered access lists. |
active |
(Optional) Displays active performance monitoring information only. |
passive |
(Optional) Displays passive performance monitoring information only. |
status |
(Optional) Displays status information only. |
detail |
(Optional) Displays detailed information. |
Command Modes
Privileged EXEC (#)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Usage Guidelines
The show pfr master traffic-class command is entered on an PfR master controller. This command is used to display information about traffic classes that are configured for monitoring and optimization. The traffic-class and match traffic-class commands simplify the learning of traffic classes. Four types of traffic classes can be automatically learned using a traffic-class command in a learn list, or manually configured using a match traffic-class command in a PfR map:
•Traffic classes based on destination prefixes.
•Traffic classes representing custom application definitions using access lists.
•Traffic classes based on a static application mapping name with an optional prefix list filtering to define destination prefixes.
•Traffic classes based on an NBAR-identified application mapping name with an optional prefix list filtering to define destination prefixes.
If none of the active, passive, or status keywords is specified, then the output will display the active, passive, and status information for the traffic classes. To restrict the amount of output, you can specify one or two of the active, passive, or status keywords, but the order of the keywords is important. If you specify the active keyword first then the passive or status keywords can be entered, if you specify the passive keyword first, then only the status keyword can be entered. The status keyword can be entered only by itself; the active and passive keywords are not accepted if they follow the status keyword. The optional detail keyword will display detailed output for the traffic classes.
To display information about traffic classes identified using NBAR, use the show pfr master traffic-class application nbar command.
Table 57 displays the keywords that represent the application that can be configured with the show pfr master traffic-class command. Replace the application-name argument with the appropriate keyword from the table.
Examples
The following example shows information about traffic classes destined for the 10.1.1.0/24 prefix:
Router# show pfr master traffic-class
OER 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 Score
Los - Packet Loss (packets-per-million), Un - Unreachable (flows-per-million),
E - Egress, I - Ingress, Bw - Bandwidth (kbps), N - Not applicable
U - unknown, * - uncontrolled, + - control more specific, @ - active probe all
# - Prefix monitor mode is Special, & - Blackholed Prefix
% - Force Next-Hop, ^ - Prefix is denied
DstPrefix Appl_ID Dscp Prot SrcPort DstPort SrcPrefix
Flags State Time CurrBR CurrI/F Protocol
PasSDly PasLDly PasSUn PasLUn PasSLos PasLLos EBw IBw
ActSDly ActLDly ActSUn ActLUn ActSJit ActPMOS ActSLos ActLLos
--------------------------------------------------------------------------------
10.1.1.0/24 N defa N N N N
# OOPOLICY 32 10.11.1.3 Et1/0 BGP
N N N N N N N IBwN
130 134 0 0 N N
The following example of the show pfr master traffic-class command with the inside keyword shows information about traffic classes:
Router# show pfr master traffic-class inside
OER 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 Score
Los - Packet Loss (packets-per-million), Un - Unreachable (flows-per-million),
E - Egress, I - Ingress, Bw - Bandwidth (kbps), N - Not applicable
U - unknown, * - uncontrolled, + - control more specific, @ - active probe all
# - Prefix monitor mode is Special, & - Blackholed Prefix
% - Force Next-Hop, ^ - Prefix is denied
DstPrefix (inside) Appl_ID Dscp Prot SrcPort DstPort SrcPrefix
Flags State Time CurrBR CurrI/F Protocol
PasSDly PasLDly PasSUn PasLUn PasSLos PasLLos EBw IBw
ActSDly ActLDly ActSUn ActLUn ActSJit ActPMOS ActSLos ActLLos
--------------------------------------------------------------------------------
10.0.0.0/16 N N N N N N
DEFAULT* 0 U U
Table 58 describes the significant fields shown in the display.
Related Commands
show pfr master traffic-class application nbar
To display information about application traffic classes that are identified using Network-Based Application Recognition (NBAR) and are monitored and controlled by a Performance Routing (PfR) master controller, use the show pfr master traffic-class application nbar command in privileged EXEC mode.
show pfr master traffic-class application nbar nbar-appl-name [prefix] [[active passive status] | detail]
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Usage Guidelines
The show pfr master traffic-class application nbar command is entered on a PfR master controller. This command is used to display information about application traffic classes that are identified using NBAR. To display information about traffic classes defined using static application mapping, use the show pfr master traffic-class command.
The optional detail keyword will display detailed output for the NBAR application traffic classes. If the detail keyword is not specified, and if none of the active, passive, or status keywords is specified, then the output will display the active, passive, and status information for the traffic classes. To restrict the amount of output, specify just one or two of the active, passive, or status keywords. If specified, the active, passive, or status keywords must be specified in the order shown in the syntax.
NBAR is capable of identifying applications based on the following three types of protocols:
•Non-UDP and Non-TCP IP protocols—For example, Generic Routing Encapsulation (GRE), and Internet Control Message Protocol (ICMP).
•TCP and UDP protocols that use statically assigned port numbers—For example, CU-SeeMe desktop video conference (CU-SeeMe-Server) and Post Office Protocol over Transport Layer Security (TLS) and Secure Sockets Layer (SSL) server (SPOP3-Server).
•TCP and UDP protocols that dynamically assign port numbers and require stateful inspection—For example, Real-Time Transport Protocol audio streaming (RTP-audio) and BitTorrent File Transfer Traffic (BitTorrent).
The list of applications identified using NBAR and available for profiling PfR traffic classes is constantly evolving. For lists of many of the NBAR applications defined using static or dynamically assigned ports, see the "Performance Routing with NBAR/CCE Application Recognition" module.
For more details about NBAR, see the "Classifying Network Traffic Using NBAR" section of the Cisco IOS Quality of Service Solutions Configuration Guide.
If the prefix argument is specified, only the PfR-controlled traffic class that matches the application specified by the nbar-appl-name argument and the destination prefix specified by the prefix argument are displayed. If the prefix argument is not specified, all PfR-controlled traffic classes that match the application specified by the nbar-appl-name argument, regardless of the destination prefix, are displayed.
Examples
The following example shows information about traffic classes consisting of Real-time Transport Protocol streaming audio (RTP-audio) traffic:
Router# show pfr master traffic-class application nbar rtp-audio
OER 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 Score
Los - Packet Loss (packets-per-million), Un - Unreachable (flows-per-million),
E - Egress, I - Ingress, Bw - Bandwidth (kbps), N - Not applicable
U - unknown, * - uncontrolled, + - control more specific, @ - active probe all
# - Prefix monitor mode is Special, & - Blackholed Prefix
% - Force Next-Hop, ^ - Prefix is denied
DstPrefix Appl_ID Dscp Prot SrcPort DstPort SrcPrefix
Flags State Time CurrBR CurrI/F Protocol
PasSDly PasLDly PasSUn PasLUn EBw IBw
ActSDly ActLDly ActSUn ActLUn ActSJit ActPMOS
--------------------------------------------------------------------------------
100.1.1.0/28 RTP-Audio defa N N N 0.0.0.0/0
DEFAULT* 461 101.1.1.2 Et1/0 U
U U 0 0 1 2
150 130 0 0 15 0
100.1.1.16/28 RTP-Audio defa N N N 0.0.0.0/0
DEFAULT* 461 101.1.1.2 Et1/0 U
U U 0 0 1 2
250 200 0 0 30 0
Table 59 describes the significant fields shown in the display.
Related Commands
show pfr proxy
To display Performance Routing (PfR) proxy information, use the show pfr proxy command in privileged EXEC mode.
show pfr proxy
Syntax Description
This command has no arguments or keywords.
Command Default
No debugging messages are enabled.
Command Modes
Privileged EXEC (#)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Usage Guidelines
The show pfr proxy command is entered on a master controller. This command is used to display IP address information and connection status of a PfR proxy.
Examples
The following is sample output from the show pfr proxy command:
Router# show pfr proxy
OER PROXY 0.0.0.0 DISABLED, MC 0.0.0.0 UP/DOWN: DOWN
Conn Status: NOT OPEN, Port 3949
Table 60 describes the significant fields shown in the display.
Related Commands
|
|
|
|---|---|
show pfr api |
Displays information about PfR application interface clients. |
shutdown (PfR)
To stop a Performance Routing (PfR) master controller or PfR border router process without removing the PfR process configuration, use the shutdown command in PfR master controller or PfR border router configuration mode. To start a stopped PfR process, use the no form of this command.
shutdown
no shutdown
Syntax Description
This command has no arguments or keywords.
Command Default
No master controller or border router is stopped.
Command Modes
PfR master controller configuration (config-pfr-mc)
PfR border router configuration (config-pfr-br)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Cisco IOS XE Release 3.1S |
This command was integrated into Cisco IOS XE Release 3.1S. |
Usage Guidelines
The shutdown command is entered on a master controller or border router. Entering the shutdown command stops an active master controller or border router process but does not remove any configuration parameters. The shutdown command is displayed in the running configuration file when enabled. To disable a master controller or border router and completely remove the process configuration from the running configuration file, use the no pfr master or no pfr border command in global configuration mode.
Cisco IOS XE Release 3.1S
This command is supported only in PfR border router configuration mode.
Examples
The following example stops an active PfR border router session:
Router(config)# pfr border
Router(config-pfr-br)# shutdown
The following example starts an inactive PfR master controller session:
Router(config)# pfr master
Router(config-pfr-mc)# no shutdown
Related Commands
|
|
|
|---|---|
pfr |
Enables a PfR process and configures a router as a PfR border router or as a PfR master controller. |
throughput (PfR)
To configure Performance Routing (PfR) to learn the top prefixes based on the highest outbound throughput, use the throughput command in Top Talker and Top Delay learning configuration mode or learn list configuration mode. To disable learning based on outbound throughput, use the no form of this command.
throughput
no throughput
Syntax Description
This command has no arguments or keywords.
Command Default
No prefixes are learned based on outbound throughput.
Command Modes
PfR Top Talker and Top Delay learning configuration (config-pfr-mc-learn)
Learn list configuration (config-pfr-mc-learn-list)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Usage Guidelines
The throughput command is entered on a master controller. The master controller creates a list of prefixes based on the highest outbound throughput. This command is used to configure a master controller to learn prefixes based on the highest outbound packet throughput. When this command is enabled, PfR will learn the top prefixes across all border routers according to the highest outbound throughput.
Examples
Top Talker and Top Delay Learning Configuration Mode
The following example shows how to configure a master controller to learn the top prefixes based on the highest outbound throughput:
Router(config)# pfr master
Router(config-pfr-mc)# learn
Router(config-pfr-mc-learn)# throughput
Learn List Configuration Mode
The following example shows how to configure a master controller to learn top prefixes based on the highest throughput for a learn list named LEARN_REMOTE_LOGIN_TC that learns Telnet and Secure Shell (SSH) application TCF entries:
Router(config)# pfr master
Router(config-pfr-mc)# learn
Router(config-pfr-mc-learn)# list seq 10 refname LEARN_REMOTE_LOGIN_TC
Router(config-pfr-mc-learn-list)# traffic-class application telnet ssh
Router(config-pfr-mc-learn-list)# aggregation-type prefix-length 24
Router(config-pfr-mc-learn-list)# throughput
Related Commands
traceroute probe-delay (PfR)
To set the time interval between traceroute probe cycles, use the traceroute probe-delay command in Performance Routing (PfR) master controller configuration mode. To set the interval between probes to the default value, use the no form of this command.
traceroute probe-delay milliseconds
no traceroute probe-delay
Syntax Description
milliseconds |
Configures the time interval, in milliseconds, between traceroute probes. The configurable range for this argument is a number from 0 to 65535. |
Command Default
The default time interval between traceroute probes is 10,000 milliseconds when this command is not configured or when the no form is entered.
Command Modes
PfR master controller configuration (config-pfr-mc)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Usage Guidelines
The traceroute probe-delay command is entered on a master controller. This command is used to set the delay interval between traceroute probes.
Continuous and policy-based traceroute reporting is configured with the set traceroute reporting (PfR) command. The time interval between traceroute probes is configured with the traceroute probe-delay command in PfR master controller configuration mode. On-demand traceroute probes are triggered by entering the show pfr master prefix (PfR) command with the current and now keywords.
Examples
The following example, which starts in global configuration mode, sets the delay interval between traceroute probes to 10000 milliseconds:
Router(config)# pfr master
Router(config-pfr-mc)# traceroute probe-delay 10000
Related Commands
traffic-class access-list (PfR)
To define a Performance Routing (PfR) application traffic class using an access list applied to learned traffic flows, use the traffic-class access-list command in learn list configuration mode. To disable the definition of PfR-learned traffic flows into application traffic classes using an access list, use the no form of this command.
traffic-class access-list access-list-name [filter prefix-list-name]
no traffic-class access-list
Syntax Description
Command Default
PfR application traffic classes are not defined using an access list.
Command Modes
Learn list configuration (config-pfr-mc-learn-list)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Usage Guidelines
The traffic-class access-list command is used to configure the master controller to automatically learn application traffic defined in an access list. Only one access list can be specified, but the access list may contain many access list entries (ACEs) to help define the traffic class parameters.
PfR learn lists are a way to categorize learned traffic classes. In each learn list, different criteria for learning traffic classes including prefixes, application definitions, filters, and aggregation parameters 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 a PfR policy was applied to all the traffic classes.
Note The traffic-class access-list command, the traffic-class application command, and the traffic-class prefix-list commands are all mutually exclusive in a PfR learn list. Only one of these commands can be specified per PfR learn list.
Examples
The following example, starting in global configuration mode, shows how to define a custom application traffic class using an access list. Every entry in the access list defines one application, and the destination network of the traffic class is determined by the specified aggregation method. After the access list is configured, the master controller automatically learns the defined application traffic based on highest throughput. A prefix list may be used to filter the traffic flows by destination prefix.
Router(config)# ip access-list extended USER_DEFINED_TC
Router(config-ext-nacl)# permit tcp any any 500
Router(config-ext-nacl)# permit tcp any any range 700 750
Router(config-ext-nacl)# permit udp 10.1.1.1 0.0.0.0 any
Router(config-ext-nacl)# permit ip any any dscp ef
Router(config-ext-nacl)# exit
Router(config)# pfr master
Router(config-pfr-mc)# learn
Router(config-pfr-mc-learn)# list seq 10 refname LEARN_USER_DEFINED_TC
Router(config-pfr-mc-learn-list)# traffic-class access-list USER_DEFINED_TC
Router(config-pfr-mc-learn-list)# aggregation-type prefix-length 24
Router(config-pfr-mc-learn-list)# throughput
Router(config-pfr-mc-learn-list)# end
Related Commands
traffic-class aggregate (PfR)
To aggregate Performance Routing (PfR) learned traffic flows into application traffic classes using an access list, use the traffic-class aggregate command in PfR Top Talker and Top Delay learning configuration mode. To disable the aggregation of PfR-learned traffic flows into application traffic classes using an access list, use the no form of this command.
traffic-class aggregate access-list access-list-name
no traffic-class aggregate access-list access-list-name
Syntax Description
Command Default
PfR-learned traffic flows are not aggregated into application traffic classes using an access list.
Command Modes
PfR Top Talker and Top Delay learning configuration (config-pfr-mc-learn)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Usage Guidelines
The traffic-class aggregate command can be used with the traffic-class filter (PfR) and traffic-class keys (PfR) commands to configure the master controller to automatically learn defined application traffic. Only one access list can be specified, but the access list may contain many access list entries to help define the traffic class parameters.
Note The traffic-class aggregate command is different from the aggregation-type (PfR) command that aggregates learned prefixes based on the type of traffic flow. The traffic-class aggregate command introduces the ability to use an access list to aggregate learned traffic flows to create an application traffic class. Both commands can be used in the same configuration.
Examples
The following example, starting in global configuration mode, configures the master controller to automatically learn defined application traffic. In this example, two access lists are created to identify and define voice traffic in the network. Using the traffic-class aggregate (PfR) and the traffic-class filter (PfR) commands with the access lists, only voice traffic with a Differentiated Services Code Point (DSCP) bit set to ef, a User Datagram Protocol (UDP), and a destination port in the range of 3000 to 4000 is learned and added to the PfR application database on the master controller.
Router(config)# ip access-list extended voice-filter-acl
Router(config-ext-nacl)# permit udp any 10.1.0.0 0.0.255.255 dscp ef
Router(config-ext-nacl)# exit
Router(config)# ip access-list extended voice-agg-acl
Router(config-ext-nacl)# permit udp any any range 3000 4000 dscp ef
Router(config-ext-nacl)# exit
Router(config)# pfr master
Router(config-pfr-mc)# learn
Router(config-pfr-mc-learn)# aggregation-type prefix-length 24
Router(config-pfr-mc-learn)# throughput
Router(config-pfr-mc-learn)# traffic-class filter access-list voice-filter-acl
Router(config-pfr-mc-learn)# traffic-class aggregate access-list voice-agg-acl
Router(config-pfr-mc-learn)# traffic-class keys protocol dport dscp
Router(config-pfr-mc-learn)# end
Related Commands
traffic-class application (PfR)
To define a Performance Routing (PfR) traffic class using a predefined static application, use the traffic-class application command in learn list configuration mode. To remove the definition of a PfR-learned traffic class using a predefined static application, use the no form of this command.
traffic-class application application-name [application-name ...] [filter prefix-list-name]
no traffic-class application application-name ... [filter prefix-list-name]
Syntax Description
application-name |
Name of a predefined static application using fixed ports. See Table 61. One application must be specified, but the ellipsis shows that more than one application keyword can be specified up to a maximum of ten. |
filter |
(Optional) Specifies that the traffic flows are filtered on the basis of a prefix list. |
prefix-list-name |
(Optional) Name of a prefix list (created using the ip prefix-list command). |
Command Default
PfR traffic classes are not defined using a static application mapping.
Command Modes
Learn list configuration (config-pfr-mc-learn-list)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Usage Guidelines
The traffic-class application command is used to configure the master controller to automatically learn traffic using a keyword that represents an application. PfR maps the application keyword to a protocol—TCP or UDP, or both—and one or more ports, and this mapping is shown in Table 61. More than one application can be configured as part of the traffic class.
Learn lists are a way to categorize learned traffic classes. In each learn list, different criteria for learning traffic classes including prefixes, application definitions, filters, and aggregation parameters 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 a PfR policy was applied to all the traffic classes.
Note The traffic-class application (PfR) command, the traffic-class access-list (PfR) command, the traffic-class application nbar (PfR) command, and the traffic-class prefix-list (PfR) commands are all mutually exclusive in a PfR learn list. Only one of these commands can be specified per PfR learn list.
Table 61 displays the keywords that represent the application that can be configured with the traffic-class application command. Replace the application-name argument with the appropriate keyword from the table.
Examples
The following example, starting in global configuration mode, shows how to define application traffic classes using two PfR learn lists, LEARN_REMOTE_LOGIN_TC and LEARN_FILE_TRANSFER_TC. The number of traffic classes to be learned in both learn list sessions is set to 50, and the maximum number of traffic classes to be learned for all sessions of the learn list is set to 90. 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 to be passively and actively monitored.
Router(config)# ip prefix-list INCLUDE_10_NET 10.0.0.0/8
Router(config)# pfr master
Router(config-pfr-mc)# learn
Router(config-pfr-mc-learn)# list seq 10 refname LEARN_REMOTE_LOGIN_TC
Router(config-pfr-mc-learn-list)# count 50 max 90
Router(config-pfr-mc-learn-list)# traffic-class application telnet ssh
Router(config-pfr-mc-learn-list)# aggregation-type prefix-length 24
Router(config-pfr-mc-learn-list)# throughput
Router(config-pfr-mc-learn-list)# exit
Router(config-pfr-mc-learn)# list seq 20 refname LEARN_FILE_TRANSFER_TC
Router(config-pfr-mc-learn-list)# count 50 max 90
Router(config-pfr-mc-learn-list)# traffic-class application ftp filter INCLUDE_10_NET
Router(config-pfr-mc-learn-list)# aggregation-type prefix-length 24
Router(config-pfr-mc-learn-list)# throughput
Router(config-pfr-mc-learn-list)# end
Related Commands
traffic-class application nbar (PfR)
To define a Performance Routing (PfR) traffic class using a Network-Based Application Recognition (NBAR) application mapping, use the traffic-class application nbar command in learn list configuration mode. To remove the definition of a PfR-learned traffic class using an application identified using NBAR, use the no form of this command.
traffic-class application nbar nbar-app-name [nbar-app-name ...] [filter prefix-list-name]
no traffic-class application nbar [nbar-app-name ...]
Syntax Description
Command Default
PfR traffic classes are not defined using an NBAR application mapping.
Command Modes
Learn list configuration (config-pfr-mc-learn-list)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Usage Guidelines
The traffic-class application nbar command is used to configure the master controller to automatically learn traffic using a keyword that represents an application that can be identified using NBAR. More than one application can be configured as part of the traffic class with a maximum of ten applications entered per command line. Enter multiple traffic-class application nbar command statements if you need to specify more than ten applications.
NBAR is capable of identifying applications based on the following three types of protocols:
•Non-UDP and non-TCP IP protocols—For example, Generic Routing Encapsulation (GRE) and Internet Control Message Protocol (ICMP).
•TCP and UDP protocols that use statically assigned port numbers—For example, CU-SeeMe desktop video conference (CU-SeeMe-Server), Post Office Protocol over Transport Layer Security (TLS), and Secure Sockets Layer (SSL) server (SPOP3-Server).
•TCP and UDP protocols that dynamically assign port numbers and require stateful inspection—For example, Real-Time Transport Protocol audio streaming (RTP-audio) and BitTorrent File Transfer Traffic (BitTorrent).
Use the traffic-class application nbar ? command to determine if an application can be identified using NBAR and replace the nbar-app-name argument with the appropriate keyword from the screen display.
The list of applications identified using NBAR and available for profiling PfR traffic classes is constantly evolving. For lists of many of the NBAR applications defined using static or dynamically assigned ports, see the "Performance Routing with NBAR/CCE Application and Recognition" module.
For more details about NBAR, see the "Classifying Network Traffic Using NBAR" section of the Cisco IOS Quality of Service Solutions Configuration Guide.
Note The traffic-class application nbar (PfR) command, the traffic-class application (PfR) command, the traffic-class access-list (PfR) command, and the traffic-class prefix-list (PfR) commands are all mutually exclusive in a PfR map. Only one of these commands can be specified per PfR map.
Examples
The following example, starting in global configuration mode, shows how to define application traffic classes identified by using NBAR and two PfR learn lists, LEARN_VOICE_TC and LEARN_VIDEO_TC. The number of traffic classes to be learned in both learn list sessions is 50, and the maximum number of traffic classes to be learned for all sessions of the learn list is 90.
The Voice over IP (VoIP) traffic class is configured using keywords representing RTP-Audio and the resulting prefixes are aggregated to a prefix length of 24. The video traffic class is configured using a keyword that represents RTP-video and is also aggregated to a prefix length of 24. A prefix list is applied to the video traffic class to match traffic for the destination prefix of 10.0.0.0/8. The master controller is configured to learn the top prefixes based on highest outbound throughput for the learned traffic, and the resulting traffic classes are added to the PfR application database.
The traffic streams that the learn list profiles for both the RTP-audio and the RTP-video applications are:
10.1.1.1
10.1.2.1
172.17.1.1
172.17.2.1
The traffic classes that are learned for each application are:
10.1.1.0/24 rtp-audio
10.1.2.0/24 rtp-audio
172.17.1.0/24 rtp-audio
172.17.2.0/24 rtp-audio
10.1.1.0/24 rtp-video
10.1.2.0/24 rtp-video
The difference in traffic classes learned is due to the optional INCLUDE_10_NET prefix list that only includes RTP-video application traffic with a destination prefix that matches the prefix 10.0.0.0/8.
Router(config)# ip prefix-list INCLUDE_10_NET 10.0.0.0/8
Router(config)# pfr master
Router(config-pfr-mc)# learn
Router(config-pfr-mc-learn)# list seq 10 refname LEARN_VOICE_TC
Router(config-pfr-mc-learn-list)# count 50 max 90
Router(config-pfr-mc-learn-list)# traffic-class application nbar rtp-audio
Router(config-pfr-mc-learn-list)# aggregation-type prefix-length 24
Router(config-pfr-mc-learn-list)# throughput
Router(config-pfr-mc-learn-list)# exit
Router(config-pfr-mc-learn)# list seq 20 refname LEARN_VIDEO_TC
Router(config-pfr-mc-learn-list)# count 50 max 90
Router(config-pfr-mc-learn-list)# traffic-class application nbar rtp-video filter INCLUDE_10_NET
Router(config-pfr-mc-learn-list)# aggregation-type prefix-length 24
Router(config-pfr-mc-learn-list)# throughput
Router(config-pfr-mc-learn-list)# end
Related Commands
traffic-class filter (PfR)
To filter uninteresting traffic from Performance Routing (PfR) learned traffic flows using an access list, use the traffic-class filter command in PfR Top Talker and Top Delay learning configuration mode. To disable the filtering of PfR-learned traffic flows using an access list, use the no form of this command.
traffic-class filter access-list access-list-name
no traffic-class filter access-list access-list-name
Syntax Description
Command Default
Uninteresting traffic is not filtered from PfR traffic flows using an access list.
Command Modes
PfR Top Talker and Top Delay learning configuration (config-pfr-mc-learn)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Usage Guidelines
PfR is used to optimize the performance of selected traffic flows in your network. While defining the selected traffic flows, this command is used to filter out traffic that you are not interested in optimizing.
The traffic-class filter command can be used with the traffic-class aggregate (PfR) and traffic-class keys (PfR) commands to configure the master controller to automatically learn defined application traffic. Only one access list can be specified, but the access list may contain many access list entries (ACEs) to help define the traffic class parameters.
Examples
The following example, starting in global configuration mode, configures the master controller to automatically learn defined application traffic. In this example, two access lists are created to identify and define voice traffic in the network. Using the traffic-class aggregate (PfR) and the traffic-class filter commands with the access lists, only voice traffic with a Differentiated Services Code Point (DSCP) bit set to ef, a User Datagram Protocol (UDP), and a destination port in the range of 3000 to 4000 is learned and added to the PfR application database on the master controller.
Router(config)# ip access-list extended voice-filter-acl
Router(config-ext-nacl)# permit udp any 10.1.0.0 0.0.255.255 dscp ef
Router(config-ext-nacl)# exit
Router(config)# ip access-list extended voice-agg-acl
Router(config-ext-nacl)# permit udp any any range 3000 4000 dscp ef
Router(config-ext-nacl)# exit
Router(config)# pfr master
Router(config-pfr-mc)# learn
Router(config-pfr-mc-learn)# aggregation-type prefix-length 24
Router(config-pfr-mc-learn)# throughput
Router(config-pfr-mc-learn)# traffic-class filter access-list voice-filter-acl
Router(config-pfr-mc-learn)# traffic-class aggregate access-list voice-agg-acl
Router(config-pfr-mc-learn)# traffic-class keys dscp protocol dport
Router(config-pfr-mc-learn)# end
Related Commands
traffic-class keys (PfR)
To specify a key list of fields in the traffic flows that a Performance Routing (PfR) border router uses to aggregate traffic flows into application traffic classes, use the traffic-class keys command in PfR Top Talker and Top Delay learning configuration mode. To remove the key list, use the no form of this command.
traffic-class keys [default | [dscp] [protocol [dport] [sport]]]
no traffic-class keys [default | [dscp] [protocol [dport] [sport]]]
Syntax Description
Command Default
No PfR traffic class key lists are created.
Command Modes
PfR Top Talker and Top Delay learning configuration (config-pfr-mc-learn)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Usage Guidelines
The traffic-class keys command can be used with the traffic-class filter (PfR) and traffic-class aggregate (PfR) commands to configure the master controller to automatically learn defined application traffic. This command is used only if the traffic-class aggregate (PfR) command is not configured or returns no matches.
Examples
In this example, only voice traffic with a DSCP bit set to ef, a User Datagram Protocol (UDP), and a destination port in the range of 3000 to 4000 is learned and added to the PfR application database on the master controller.
Router(config)# ip access-list extended voice-filter-acl
Router(config-ext-nacl)# permit udp any 10.1.0.0 0.0.255.255 dscp ef
Router(config-ext-nacl)# exit
Router(config)# ip access-list extended voice-agg-acl
Router(config-ext-nacl)# permit udp any any range 3000 4000 dscp ef
Router(config-ext-nacl)# exit
Router(config)# pfr master
Router(config-pfr-master)# learn
Router(config-pfr-master-learn)# aggregation-type prefix-length 24
Router(config-pfr-master-learn)# throughput
Router(config-pfr-master-learn)# traffic-class filter access-list voice-filter-acl
Router(config-pfr-master-learn)# traffic-class aggregate access-list voice-agg-acl
Router(config-pfr-master-learn)# traffic-class keys dscp protocol dport
Router(config-pfr-master-learn)# end
Related Commands
traffic-class prefix-list (PfR)
To define a Performance Routing (PfR) traffic class using a prefix list applied to learned traffic classes, use the traffic-class prefix-list command in learn list configuration mode. To disable the definition of PfR-learned traffic flows into traffic classes using a prefix list, use the no form of this command.
traffic-class prefix-list prefix-list-name [inside]
no traffic-class prefix-list
Syntax Description
Command Default
PfR application traffic classes are not defined using a prefix list.
Command Modes
Learn list configuration (config-pfr-mc-learn-list)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Usage Guidelines
The traffic-class prefix-list command is used to configure the master controller to automatically learn traffic based only on destination prefixes. Use the optional inside keyword to specify prefixes that are within the internal network.
Learn lists are a way to categorize learned traffic classes. In each learn list, different criteria for learning traffic classes including prefixes, application definitions, filters, and aggregation parameters 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 a PfR policy was applied to all the traffic classes.
Note The traffic-class prefix-list command, the traffic-class application (PfR) command, the traffic-class application nbar (PfR) command, and the traffic-class access-list (PfR) commands are all mutually exclusive in a PfR learn list. Only one of these commands can be specified per PfR learn list.
Examples
The following example, starting in global configuration mode, shows how to define traffic classes based only on destination prefixes for a learn list named LEARN_PREFIX_TC. The traffic classes are created using the prefix list, LEARN_LIST1, in which every entry in the prefix list defines one destination network of a traffic class. After the prefix list is configured, the master controller automatically learns the traffic classes based on the highest throughput.
Router(config)# ip prefix-list LEARN_LIST1 permit seq 10 10.0.0.0/8
Router(config)# ip prefix-list LEARN_LIST1 permit seq 20 172.16.0.0/16
Router(config)# pfr master
Router(config-pfr-mc)# learn
Router(config-pfr-mc-learn)# list seq 10 refname LEARN_PREFIX_TC
Router(config-pfr-mc-learn-list)# aggregation-type prefix-length 24
Router(config-pfr-mc-learn-list)# traffic-class prefix-list LEARN_LIST1
Router(config-pfr-mc-learn-list)# throughput
Router(config-pfr-mc-learn-list)# end
Related Commands
unreachable (PfR)
To set the relative percentage or maximum number of unreachable hosts that Performance Routing (PfR) permits from a PfR-managed exit link, use the unreachable command in PfR master controller configuration mode. To return the relative percentage of unreachable hosts to the default value, use the no form of this command.
unreachable {relative average | threshold maximum}
no unreachable
Syntax Description
Command Default
PfR uses a default relative percentage of 50 (5 percent) unreachable hosts if this command is not configured or if the no form of this command is entered.
Command Modes
PfR master controller configuration (config-pfr-mc)
Command History
|
|
|
|---|---|
15.1(2)T |
This command was introduced. |
Usage Guidelines
The unreachable command is entered on a master controller. This command is used to set the relative percentage or the absolute maximum number of unreachable hosts, based on flows per million, that PfR will permit from a PfR-managed exit link. If the absolute number or relative percentage of unreachable hosts is greater than the user-defined or the default value, PfR determines that the exit link is out-of-policy and searches for an alternate exit link.
The relative keyword is used to configure the relative percentage of unreachable hosts. The relative unreachable host percentage is based on a comparison of short-term and long-term measurements. The short-term measurement reflects the percentage of hosts that are unreachable within a 5-minute period. The long-term measurement reflects the percentage of unreachable hosts within a 60-minute period. The following formula is used to calculate this value:
Relative percentage of unreachable hosts = ((short-term percentage - long-term percentage) / long-term percentage) * 100
The master controller measures the difference between these two values as a percentage. If the percentage exceeds the user-defined or default value, the exit link is determined to be out-of-policy. For example, if 10 hosts are unreachable during the long-term measurement and 12 hosts are unreachable during the short-term measurement, the relative percentage of unreachable hosts is 20 percent.
The threshold keyword is used to configure the absolute maximum number of unreachable hosts. The maximum value is based on the actual number of hosts that are unreachable based on fpm.
Examples
The following example configures the master controller to search for a new exit link when the difference between long- and short-term measurements (relative percentage) is greater than 10 percent:
Router(config)# pfr master
Router(config-pfr-mc)# unreachable relative 100
The following example configures PfR to search for a new exit link when 10,000 hosts are unreachable:
Router(config)# pfr master
Router(config-pfr-mc)# unreachable threshold 10000
Feedback