 Feedback
|
Table Of Contents
Configuring Performance Routing Cost Policies
Prerequisites for Performance Routing Cost Policies
Information About Performance Routing Cost Policies
Traffic Load (Utilization) Policy
Link Utilization Rollup Calculations
Monthly Sustained Utilization Calculation
How to Configure Performance Routing Cost Policies
Configuring a Basic PfR Cost-Based Policy
Using a PfR Cost Policy to Minimize Billing and Load Balance Traffic
Verifying and Debugging PfR Cost-Minimization Policies
Configuration Examples for Performance Routing Cost Policies
Configuring a Basic PfR Cost-Based Policy: Example
Using a PfR Cost Policy to Minimize Billing and Load Balance Traffic: Example
Feature Information for Configuring Performance Routing Cost Policies
Configuring Performance Routing Cost Policies
First Published: September 2, 2009Last Updated: September 2, 2009This module describes how to configure and apply Cisco IOS Performance Routing (PfR) cost policies. Performance Routing is an extension of the Optimized Edge Routing (OER) technology and many of the commands and command modes still use the OER naming conventions. All of the original OER features are incorporated into the Performance Routing technology. Some of the early OER features have been superseded by newer techniques and the more recent configuration module titles now use Performance Routing naming.
A PfR policy can be configured to optimize traffic based on the monetary cost of the exit links. The PfR Cost Based Optimization feature provides financial benefits by directing traffic to lower cost links, while at the same time honoring other configured policies such as delay, loss, and utilization. Cost Based Optimization can be applied to links that are billed using a fixed or tiered billing method. Load balancing based on cost can also be achieved.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the "Feature Information for Configuring Performance Routing Cost Policies" section.
Use Cisco Feature Navigator to find information about platform support and Cisco IOS and Catalyst OS software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•
Prerequisites for Performance Routing Cost Policies
•
•
•
•
Prerequisites for Performance Routing Cost Policies
Before implementing PfR policies, you need to understand an overview of how PfR works and how to set up PfR network components. See the "Cisco IOS Optimized Edge Routing Overview" and "Setting Up OER Network Components" modules for more details. If you are following the PfR performance loop, the PfR profile and measure phases precede this phase. See the "Where to Go Next" section for more details.
Information About Performance Routing Cost Policies
To configure and apply PfR policies, you should understand the following concepts:
•
•
Overview of PfR Link Policies
PfR link policies are a set of rules that are applied against PfR-managed external links (an external link is an interface on a border router on the network edge). Link policies define the desired performance characteristics of the links. Instead of defining the performance of an individual traffic class entry that uses the link (as in traffic class performance policies), link policies are concerned with the performance of the link as a whole. In Cisco IOS Release 12.4(6)T and prior releases, link policies are applied only to exit (egress) links, but in Cisco IOS Release 12.4(9)T, 12.2(33)SRB, and later releases, support for selected entrance (ingress) link policies was introduced. The following link policy types describe the different performance characteristics that can be managed using link policies:
•
Traffic Load (Utilization) Policy
A traffic load (also referred to as utilization) policy consists of an upper threshold on the amount of traffic that a specific link can carry. Cisco IOS PfR supports per traffic class load distribution. Every 20 seconds, by default, the border router reports the link utilization to the master controller, after an external interface is configured for a border router. In Cisco IOS Release 12.4(6)T and prior releases, only exit link traffic load thresholds can be configured as a PfR policy, but in Cisco IOS Release 12.4(9)T, 12.2(33)SRB, and later releases, entrance link traffic load thresholds can be configured. If the exit or entrance link utilization is above the configured threshold, or the default threshold of 75 percent, the exit or entrance link is in an out-of-policy (OOP) state and PfR starts the monitoring process to find an alternative link for the traffic class. The link utilization threshold can be manually configured either as an absolute value in kilobytes per second (kbps) or as a percentage. A load utilization policy for an individual interface is configured on the master controller under the border router configuration.
Tip
A traffic load policy describes an upper limit for the traffic to be carried on a single link. For more details about configuring a traffic load policy, see the "Configuring an Exit Link Load Balancing OER Policy" task in the Configuring and Applying OER Policies module.
Range Policy
A range policy is defined to maintain all links within a certain utilization range, relative to each other in order to ensure that the traffic load is distributed. For example, if a network has multiple exit links, and there is no financial reason to choose one link over another, the optimal choice is to provide an even load distribution across all links. The load-sharing provided by traditional routing protocols is not always evenly distributed, because the load-sharing is flow-based rather than performance- or policy-based. Cisco PfR range functionality allows you to configure PfR to maintain the traffic utilization on a set of links within a certain percentage range of each other. If the difference between the links becomes too great, PfR will attempt to bring the link back to an in-policy state by distributing traffic classes among the available links. The master controller sets the maximum range utilization to 20 percent for all PfR-managed links by default, but the utilization range can be configured using a maximum percentage value.
Note
In Cisco IOS Release 12.4(6)T and prior releases, only an exit link utilization range can be configured as a PfR policy, but in Cisco IOS Release 12.4(9)T, 12.2(33)SRB, and later releases, an entrance link utilization range can be configured.
A range policy describes a method of load-balancing the traffic over multiple links. For more details about configuring a range policy, see the "Configuring an Exit Link Load Balancing OER Policy" task in the Configuring and Applying OER Policies module.
Cost Policy
PfR support for cost-based optimization was introduced in Cisco IOS Release 12.3(14)T, 12.2(33)SRB, and later releases. Cost-based optimization allows you to configure policies based on the monetary cost (ISP service level agreements [SLAs]) of each exit link in your network. To implement PfR cost-based optimization the PfR master controller is configured to send traffic over exit links that provide the most cost-effective bandwidth utilization, while still maintaining the desired performance characteristics. A cost policy describes a method of load-balancing the traffic over multiple links.
In response to changing business practices, in Cisco IOS Release 12.4(15)T9 and later releases, the calculation of the Momentary Target Link Utilization (MTLU) algorithm is modified to allow for more efficient bandwidth utilization while minimizing the link cost.
To understand how cost-based optimization works, review the following sections:
•
•
Cost Policy Billing Models
PfR cost-based optimization supports two methods of billing: fixed-rate billing or tier-based billing.
Fixed-rate billing is used when the ISP bills one flat rate for a link regardless of bandwidth usage. If fixed-rate billing only is configured on the exit links, all exits are considered equal with regard to cost-optimization and other policy parameters (such as delay, loss, and utilization) are used to determine if the prefix or exit link is in-policy.
Tier-based billing is used when the ISP bills at a tiered rate based on the percentage of exit link utilization. Each cost tier is configured separately with an associated monetary cost and a percentage of bandwidth utilization that activates the tier is defined. The lowest cost tier for an exit using tier-based billing is charged each month regardless of the bandwidth actually utilized. An allowance is made for bursting in the algorithm used to determine the tier-based billing. In this situation, bursting is defined as short periods of high bandwidth usage that would be expensive under fixed-rate billing.
A fixed-rate billing is a set monthly fee regardless of utilization. Tier-based billing also incurs at least the lowest-tier cost per month, but the final monthly tier-based billing charge is determined by the cost assigned to the tier that matches the sustained monthly utilization as explained in the following sections:
•
•
For details about a task to configure a basic cost-minimization policy, see the "Configuring a Basic PfR Cost-Based Policy" section. For details about a task to optimize the cost per link and achieve load-balancing of traffic between multiple exit links, see the "Using a PfR Cost Policy to Minimize Billing and Load Balance Traffic" section.
Link Utilization Rollup Calculations
The first step in determining the billing fee for each exit link per month is to calculate the link utilization rollup values. Link utilization rollup values are the averages of the link utilization readings taken at regular intervals (sampling period) from the ingress and egress interfaces at the border routers for a given rollup period. For example, if a sampling period was set to 60 minutes, and the rollup was set at 1440 minutes (24 hours), we would have 24 ingress and 24 egress link utilization samples used for calculating the link utilization rollup. An average is taken for each set of ingress and egress samples from that rollup period to get a link utilization rollup value for the ingress and egress links.
Monthly Sustained Utilization Calculation
After the link utilization rollup calculation is performed, the monthly sustained utilization is calculated, The specific details of tier-based billing models vary by ISP. However, most ISPs use some variation of the following algorithm to calculate what an enterprise should pay in a tiered billing plan:
•
•
•
•
•
•
Note
The monthly sustained utilization rollup calculations can be configured to use one of the following three techniques:
•
•
•
In the following explanations of the sustained utilization calculation techniques, the discard value is configured as an absolute value of 10. The default discard value is 5 percent.
Using the combined technique, the monthly sustained utilization calculation is based on a combination of the egress and ingress rollup samples on a single sorted stack, the highest 10 rollup values are discarded, and the next highest rollup value is the MTLU.
Using the separate technique, the egress and ingress rollup samples for a link are sorted into separate stacks and the highest 10 rollup values for each stack are discarded. The highest remaining rollup value of the two stacks is selected as the MTLU.
Using the summed technique the egress and ingress rollup samples are added together. The summed values of each rollup sample are placed into one stack, the top 10 rollup values are discarded, leaving the next highest rollup value as the MTLU.
The following table displays an example of how the sustained monthly utilization is calculated using the separate technique. In Table 1 the rollup values for a 30-day period are displayed in order from the highest bandwidth to the lowest bandwidth for both the egress and ingress rollup values. The top 10 values (shown in italic) are discarded because the master controller has been configured to discard this absolute number of rollups. The next highest rollup value remaining in the two stacks, 62 (shown in bold), is the sustained monthly utilization. The sustained monthly utilization is used to determine the tier at which the customer is billed for bandwidth usage on that link for that billing period.
How to Configure Performance Routing Cost Policies
This section contains the following tasks:
•
•
•
Configuring a Basic PfR Cost-Based Policy
Perform this task to configure basic PfR cost-based optimization. Cost-based optimization is configured on a master controller using the cost-minimization command in OER border exit interface configuration mode (under the external interface configuration). Cost-based optimization supports tiered and fixed billing methods.
In this task, the configuration is performed on the master controller router and it assumes that the border routers are configured. Tier-based billing is configured with three cost tiers and a nickname for the service provider is set to ISP1. The monthly sustained utilization calculation technique is configured to use the sum technique and the last day of the billing cycle is on the 30th day of the month with an offset of 3 hours to allow for a difference in time zones.
The cost-minimization command contains many variations of keywords and arguments. Only one of the required keywords and its associated syntax can be configured on one CLI line, but multiple instances of this command can be entered. Only the fixed and tier keywords are mutually exclusive within the configuration for each border router link. For details about the full syntax, see the Cisco IOS Optimized Edge Routing Command Reference.
Prerequisites
This task requires the master controller and border routers to be running Cisco IOS Release 12.3(14)T, 12.2(33)SRB, or later releases.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
DETAILED STEPS
Step 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Step 2
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 3
oer master
Example:Router(config)# oer master
Enters OER master controller configuration mode to configure global prefix and exit link policies.
Step 4
border ip-address [key-chain key-chain-name]
Example:Router(config-oer-mc)# border 10.100.1.1 key-chain PFR_cost
Enters OER-managed border router configuration mode to establish communication with a border router.
•
•
Note
Step 5
interface type number external
Example:Router(config-oer-mc-br)# interface ethernet 0/0 external
Enters OER border exit interface configuration mode to configure a border router interface as an external interface.
•
Step 6
cost-minimization nickname name
Example:Router(config-oer-mc-br-if)# cost-minimization nickname ISP1
Configures a nickname for a border router interface within a cost-based optimization policy on a master controller.
•
•
Step 7
cost-minimization calc {combined | separate | sum}
Example:Router(config-oer-mc-br-if)# cost-minimization calc sum
Configures how the cost-minimization fee is calculated.
•
•
•
•
Step 8
cost-minimization sampling period minutes [rollup minutes]
Example:Router(config-oer-mc-br-if)# cost-minimization sampling period 10 rollup 60
Specifies the sampling period in minutes.
•
•
•
Step 9
cost-minimization end day-of-month day [offset [-] hh:mm]
Example:Router(config-oer-mc-br-if)# cost-minimization end day-of-month 30 offset 5:00
Configures the parameters used to configure the last day of the billing cycle.
•
•
Step 10
cost-minimization {fixed fee cost | tier percentage fee fee}
Example:Router(config-oer-mc-br-if)# cost-minimization tier 100 fee 1000
Configures a nonusage-based fixed cost billing cycle or a tier of a tier-based billing cycle.
•
•
•
•
Note
Step 11
Repeat Step 9 to configure additional tiers for a tier-based billing cycle.
—
Step 12
exit
Example:Router(config-oer-mc-br-if)# exit
Exits OER border exit interface configuration mode and returns to OER-managed border router configuration mode.
Step 13
interface type number internal
Example:Router(config-oer-mc-br)# interface Ethernet 1/0 internal
Configures a border router interface as a PfR controlled internal interface.
•
•
Note
Step 14
exit
Example:Router(config-oer-mc-br-if)# exit
Exits OER border exit interface configuration mode and returns to OER-managed border router configuration mode.
Step 15
Repeat Step 14 to return to OER master controller configuration mode.
—
Step 16
Repeat from Step 4 to Step 15 to configure additional cost-based optimization policies for other links, if required.
—
Step 17
mode route control
Example:Router(config-oer-mc)# mode route control
Configures route control for matched traffic.
•
Note
Step 18
resolve cost priority value
Example:Router(config-oer-mc)# resolve cost priority 1
Sets policy priority for cost policies.
•
•
Note
Step 19
end
Example:Router(config-oer-mc)# end
Exits OER master controller configuration mode and returns to privileged EXEC mode.
Examples
The following example is just a sample configuration as shown in the task but with the added tiers to complete the tier-based fee configuration. For a more complete example configuration of a basic PfR cost policy that includes both fixed-rate and tier-based billing, see the "Configuring a Basic PfR Cost-Based Policy: Example" section.
oer masterborder 10.100.1.1 key-chain PFR_costinterface Ethernet 0/0 externalcost-minimization nickname ISP1cost-minimization calc sumcost-minimization sampling period 10 rollup 60cost-minimization end day-of-month 30 offset 5:00cost-minimization tier 100 fee 1000cost-minimization tier 70 fee 700cost-minimization tier 50 fee 500exitinterface Ethernet 1/0 internalexitmode route controlresolve cost priority 1endUsing a PfR Cost Policy to Minimize Billing and Load Balance Traffic
While basic PfR cost-based optimization can be useful, many organizations have multiple border router exit links and possibly several different service providers charging different billing rates that increase according to the bandwidth utilized. In this situation, some form of traffic load balancing across the links may be required in addition to the cost minimization policy.
Perform this task on the master controller to configure a Performance Routing cost policy to minimize the monthly billing charge for multiple border router exit links while load balancing traffic across the links. In this scenario, the network has both fixed-rate and tier-based billing, and assuming that the customer is paying a monthly fee for the fixed-rate billing and the pre-paid (lowest cost) tier of tier-based billing, PfR can perform traffic load balancing while optimizing for cost.
Figure 1 shows an example of how different billing rates can be defined for each link using bandwidth and cost parameters that are defined through service level agreements (SLAs) that are identified as rules in the diagram. The main goal of this task is to minimize the billing charge per exit link and to load balance traffic across the exit links. Although Link 1 may be billed at a fixed-rate and Links 2 through 4 are subject to tier-based billing, all the links are set up as PfR tiers. To accomplish the cost minimization the first rule is to utilize 80 percent of Link 1 and 30 percent of Links 2, 3 and 4, as shown in Figure 1. The second rule is to distribute additional traffic across Links 2, 3 and 4 to balance the traffic load. To achieve the traffic load balancing while minimizing cost, the solution is to configure a PfR cost policy using multiple tiers representing bandwidth percentages that are assigned artificial costs to ensure that the PfR traffic is optimized for cost and load balanced across all the exits. To illustrate the configured tiers, see Figure 1.
The steps in this task create a cost policy in which PfR is configured to direct traffic through any of the lowest cost exits first; Link 1 at 10.1.1.1 and the pre-paid tier of the other three exits. When the pre-paid tier bandwidth at each link is fully utilized, the software determines the next lowest incremental cost between the tiers at all the links. The incremental cost of utilizing the next tier at Link 1 is $990. The incremental cost of utilizing the next tier at Link 2 is only $10. PfR forwards traffic to the next lowest cost tier which is the blue bar representing 40 percent of the bandwidth at Link 2, as shown in Figure 1. The process continues to use cost to balance the load across Links 2, 3, and 4. This task illustrates how the monthly billing rate per exit link is minimized by utilizing the pre-paid bandwidth at Links 1 though 4 first, and then the traffic is effectively load balanced across Links 2, 3 and 4 by determining the lowest incremental cost between tiers.
Figure 1 Diagram Showing PfR Cost-Minimization Solution to Minimize Billing and Load Balance Traffic
In the following task steps, the exit link 10.1.1.1 is configured as a tier-based link although it is actually charged at a fixed rate. If a fixed rate link is configured as a tier for load balancing, the monthly cost calculation will not reflect the true cost for that link. Using this solution, the artificial costs assigned to the multiple tiers may affect the accuracy of all the monthly cost calculations.
Only some of the configuration steps for this task scenario are shown in the summary and detailed steps, the full configuration for the master controller is displayed in the Examples section shown after the detailed steps table.
Note
Note
The cost-minimization command contains many variations of keywords and arguments. Only one of the required keywords and its associated syntax can be configured on one CLI line, but multiple instances of this command can be entered. Only the fixed and tier keywords are mutually exclusive within the configuration for each border router link. For details about the full syntax, see the Cisco IOS Optimized Edge Routing Command Reference.
For another example of configuring cost-minimization and balancing traffic load, see the configuration example "Using a PfR Cost Policy to Minimize Billing and Load Balance Traffic: Example" section.
Prerequisites
This task requires the master controller and border routers to be running Cisco IOS Release 12.3(14)T, 12.2(33)SRB, or later releases.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
DETAILED STEPS
Step 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Step 2
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 3
oer master
Example:Router(config)# oer master
Enters OER master controller configuration mode to configure global prefix and exit link policies.
Step 4
border ip-address [key-chain key-chain-name]
Example:Router(config-oer-mc)# border 10.1.1.1 key-chain pfr
Enters OER-managed border router configuration mode to establish communication with a border router.
•
•
Note
Step 5
interface type number external
Example:Router(config-oer-mc-br)# interface ethernet 0/0 external
Enters OER border exit interface configuration mode to configure a border router interface as a PfR-managed external interface.
•
•
Step 6
cost-minimization nickname name
Example:Router(config-oer-mc-br-if)# cost-minimization nickname 80-percent
Configures a nickname for a border router interface within a cost-based optimization policy on a master controller.
•
Step 7
cost-minimization summer-time start end [offset]
Example:Router(config-oer-mc-br-if)# cost-minimization summer-time 2 Sunday March 02:00 1 Sunday November 02:00 60
Specifies the start and end dates and times for summer time (daylight savings).
•
•
•
Note
Step 8
cost-minimization {fixed fee cost | tier percentage fee fee}
Example:Router(config-oer-mc-br-if)# cost-minimization tier 100 fee 1000
Configures a nonusage-based fixed cost billing cycle or a tier of a tier-based billing cycle.
•
•
•
•
Note
Step 9
Repeat Step 8 to configure additional tiers for a tier-based billing cycle.
—
Step 10
cost-minimization discard [daily] {absolute number | percent percentage}
Example:Router(config-oer-mc-br-if)# cost-minimization discard percent 5
Configures the number of samples that are removed for bursty link utilization when calculating the sustained monthly utilization value.
•
•
•
•
•
•
Step 11
exit
Example:Router(config-oer-mc-br-if)# exit
Exits OER border exit interface configuration mode and returns to OER-managed border router configuration mode.
Step 12
interface type number internal
Example:Router(config-oer-mc-br)# interface Ethernet 1/0 internal
Configures a border router interface as a PfR controlled internal interface.
•
•
Note
Step 13
exit
Example:Router(config-oer-mc-br-if)# exit
Exits OER border exit interface configuration mode and returns to OER-managed border router configuration mode.
Step 14
Repeat Step 13 to return to OER master controller configuration mode.
—
Step 15
Repeat from Step 4 to Step 14 to configure additional cost-based optimization policies for other links, if required.
—
Step 16
mode route control
Example:Router(config-oer-mc)# mode route control
Configures route control for matched traffic.
•
Note
Step 17
policy-rules map-name
Example:Router(config-oer-mc)# policy-rules cost_balance
Applies a configuration from an OER map to a master controller configuration.
•
Step 18
exit
Example:Router(config-oer-mc)# exit
Exits OER master controller configuration mode and returns to global configuration mode.
Step 19
oer-map map-name sequence-number
Example:Router(config)# oer-map cost_balance 10
Enters OER map configuration mode to configure an OER map.
Step 20
match oer learn {delay | inside | throughput}
Example:Router(config-oer-map)# match oer learn throughput
Creates a match clause entry in an OER map to match OER learned prefixes.
•
•
Step 21
set resolve cost priority value
Example:Router(config-oer-map)# set resolve cost priority 1
Creates a set clause entry in an OER map to set policy priority for overlapping policies.
•
•
Note
Step 22
end
Example:Router(config-oer-mc)# end
Exits OER master controller configuration mode and returns to privileged EXEC mode.
Examples
The following configuration example is a complete configuration for all the links controlled by the master controller in Figure 1. Note the set resolve cost priority 1 command in the OER map titled cost_balance that is used to ensure that cost is the first priority for this task. In contrast, the resolve range and resolve utilization commands are disabled to avoid optimization conflicts. For output from associated show commands see the "Verifying and Debugging PfR Cost-Minimization Policies" section.
oer masterloggingborder 10.1.1.1 key-chain pfrinterface Ethernet1/0 internalinterface Ethernet0/0 externalcost-minimization nickname 80-percentcost-minimization summer-time 2 Sunday March 02:00 1 Sunday November 02:00 60cost-minimization tier 100 fee 1000cost-minimization tier 80 fee 10cost-minimization discard percent 5exitexitborder 10.2.1.2 key-chain pfrinterface Ethernet1/0 internalinterface Ethernet0/0 externalcost-minimization nickname 30-megcost-minimization tier 100 fee 290cost-minimization tier 90 fee 220cost-minimization tier 80 fee 160cost-minimization tier 70 fee 110cost-minimization tier 60 fee 70cost-minimization tier 50 fee 40cost-minimization tier 40 fee 20cost-minimization tier 30 fee 10cost-minimization discard percent 5exitexitborder 10.3.1.3 key-chain pfrinterface Ethernet1/0 internalinterface Ethernet0/0 externalcost-minimization nickname 30-meg-2cost-minimization tier 100 fee 290cost-minimization tier 90 fee 220cost-minimization tier 80 fee 160cost-minimization tier 70 fee 110cost-minimization tier 60 fee 70cost-minimization tier 50 fee 40cost-minimization tier 40 fee 20cost-minimization tier 30 fee 10cost-minimization discard percent 5exitexitborder 10.4.1.4 key-chain pfrinterface Ethernet1/0 internalinterface Ethernet0/0 externalcost-minimization nickname 30-meg-3cost-minimization tier 100 fee 290cost-minimization tier 90 fee 220cost-minimization tier 80 fee 160cost-minimization tier 70 fee 110cost-minimization tier 60 fee 70cost-minimization tier 50 fee 40cost-minimization tier 40 fee 20cost-minimization tier 30 fee 10cost-minimization discard percent 5exitexitlearnthroughputperiodic-interval 0monitor-period 1prefixes 2500aggregation-type prefix-length 32exitmode route controlpolicy-rules cost_balancemax-range-utilization percent 100exitoer-map cost_balance 10match oer learn throughputset resolve cost priority 1no set resolve rangeno set resolve utilizationset probe frequency 10endVerifying and Debugging PfR Cost-Minimization Policies
Perform this task on a master controller to display information to verify any cost-minimization policies and to help debug any issues. After cost-minimization policies are configured and applied to traffic the show command steps allow you to verify that the policy configuration is working as expected. If not, the debug command steps can help troubleshoot any issues. The show and debug commands are all optional and can be entered in any order.
Prerequisites
•
•
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Step 1
Enables privileged EXEC mode. Enter your password if prompted.
Router> enableStep 2
Both the border and the nickname keywords of the show oer master cost-minimization command display the same cost-minimization information. The keywords and arguments can be used to identify a specified border router by its nickname or by an IP address and, optionally, for a specific interface on the router. Only the syntax applicable to this step is shown. For the full syntax, see the Cisco IOS Optimized Edge Routing Command Reference.
In this example, the information is displayed about the 10.2.1.2 link from Figure 1. Note the number of cost tiers configured for this link. The links at 10.3.1.3 and 10.4.1.4 have the same set of cost tiers to allow more precise load balancing. There is information about the rollup values and parameters set for the discard values shown as an absolute value of 5. For more details about the fields shown in this output, refer to the Cisco IOS Optimized Edge Routing Command Reference.
Router# show oer master cost-minimization border 10.2.1.2 Ethernet 0/0pM - per Month, pD - per Day--------------------------------------------------------------------------------Nickname : 30-meg Border: 10.2.1.2 Interface: Et0/0Calc type : SeparateEnd Date : 1Summer time: Enabled, 2 Sun Mar 02:00 1 Sun Nov 02:00 60Fee : Tier BasedTier 1: 100, fee: 290Tier 2: 90, fee: 220Tier 3: 80, fee: 160Tier 4: 70, fee: 110Tier 5: 60, fee: 70Tier 6: 50, fee: 40Tier 7: 40, fee: 20Tier 8: 30, fee: 10Period : Sampling 5, Rollup 5Discard : Type Absolute, Value 5Rollup Information:Total(pM) Discard(pM) Remaining(pM) Collected(pM)8928 5 1460 264Current Rollup Information:MomentaryTgtUtil: 382 Kbps CumRxBytes: 747167StartingRollupTgt: 400 Kbps CumTxBytes: 4808628CurrentRollupTgt: 400 Kbps TimeRemain: 00:03:23Rollup Utilization (Kbps):Egress Utilization Rollups (Descending order)1 : 0 2 : 440 3 : 439 4 : 3985 : 383 6 : 378 7 : 375 8 : 3729 : 371 10 : 371 11 : 370 12 : 37013 : 368 14 : 365 15 : 255 16 : 23117 : 216 18 : 197 19 : 196 20 : 19621 : 195 22 : 194 23 : 191 24 : 19025 : 190 26 : 184 27 : 183 28 : 18229 : 178 30 : 177 31 : 176 32 : 175Step 3
This command is used to display the billing information for the previous billing period. In this example, the monthly sustained utilization is 62 and the cost is $10,000 for the Ethernet interface 3/1 link on border router 10.1.1.1. Note that the figures in Table 1 were used to create this example output.
Router# show oer master cost-minimization billing-historyBilling History for the past three monthsISP2 on 10.4.1.4 Se4/0No cost min on 10.2.1.2 Et3/2ISP1 on 10.1.1.1 Et3/1Mon1 Mon2 Mon3Nickname SustUtil Cost SustUtil Cost SustUtil Cost---------- ------------------ ------------------ ------------------ISP2 0 3000 ---NA--- ---NA---ISP1 62 10000 ---NA--- ---NA------------- ------------------ ------------------ ------------------Total Cost 13000 0 0Step 4
This command is used to display debugging information for cost-minimization policies. The following example displays detailed cost-minimization policy debug information.
Router# debug oer master cost-minimization detailOER Master cost-minimization Detail debugging is on*May 14 00:38:48.839: OER MC COST: Momentary target utilization for exit 10.2.1.2 i/fEthernet1/0 nickname ISP1 is 7500 kbps, time_left 52889 secs, cumulative 16 kb, rollup period 84000 secs, rollup target 6000 kbps, bw_capacity 10000 kbps*May 14 00:38:48.839: OER MC COST: Cost OOP check for border 10.2.1.2, current util: 0 target util: 7500 kbps*May 14 00:39:00.199: OER MC COST: ISP1 calc separate rollup ended at 55 ingress Kbps*May 14 00:39:00.199: OER MC COST: ISP1 calc separate rollup ended at 55 egress bytes*May 14 00:39:00.199: OER MC COST: Target utilization for nickname ISP1 set to 6000, rollups elapsed 4, rollups left 24*May 14 00:39:00.271: OER MC COST: Momentary target utilization for exit 10.2.1.2 i/f Ethernet1/0 nickname ISP1 is 7500 kbps, time_left 52878 secs, cumulative 0 kb, rollup period 84000 secs, rollup target 6000 kbps, bw_capacity 10000 kbps*May 14 00:39:00.271: OER MC COST: Cost OOP check for border 10.2.1.2, current util: 0 target util: 7500 kbps
Configuration Examples for Performance Routing Cost Policies
The following examples in this section show various PfR policy configurations:
•
•
Configuring a Basic PfR Cost-Based Policy: Example
The following example shows how to configure cost-based optimization on a master controller. Cost optimization configuration is applied under the external interface configuration. In this example, a policy is configured for multiple exits with a tiered billing cycle for one exit interface on border router 10.2.1.2 and a fixed fee billing cycle for the other exit interface on border router 10.2.1.2 and both exit interfaces on border router 10.3.1.3.
In this scenario, PfR sends traffic first through the fixed-rate exits, serial interface 3/0 at border router 10.2.1.2 and serial interfaces 2/0 and 3/0 at border router 10.3.1.3, because the bandwidth cost is lower for these fixed fee exits than the tier-based exit. When the fixed-rate exits are all fully utilized, the traffic is sent through serial interface 2/0 on border router 10.2.1.2. If the monthly sustained utilization is 40 percent or lower, the billing fee for the month will be $4000. If the monthly sustained utilization is higher then the tier that matches the monthly sustained utilization is charged. In this example, no calculation configuration was entered and the default behavior is triggered; the calculation is performed separately for egress and ingress samples.
This configuration example assumes that the border routers are already configured.
oer masterno periodicresolve cost priority 1no resolve delayno resolve utilizationborder 10.2.1.2 key-chain key_cost1interface Serial12/0 externalcost-minimization tier 100 fee 10000cost-minimization tier 75 fee 8000cost-minimization tier 40 fee 4000cost-minimization end day-of-month 31interface Serial13/0 externalcost-minimization fixed fee 3000border 10.3.1.3 key-chain key_cost2interface Serial12/0 externalcost-minimization fixed fee 3000interface Serial13/0 externalcost-minimization fixed fee 3000endUsing a PfR Cost Policy to Minimize Billing and Load Balance Traffic: Example
The following configuration example shows how to configure cost-minimization policies and balance PfR traffic loads across multiple links. This task is designed to minimize the cost of each link and to precisely control load balancing across multiple border router links. This task controls the load balancing between multiple links by forcing PfR to use the bandwidth of the lowest cost tier first and then use the next lowest cost tiers on all the links.
Keywords in the show oer master cost-minimization command are used to view the utilization of a specific link with the monthly egress and ingress rollup values. After the monthly billing period ends another keyword option for the billing history shows the sustained monthly utilization and link cost.
Border Router 10.1.1.1
key chain key1key 1key-string border1!oer borderlogginglocal Ethernet3/0master 10.1.1.1 key-chain key1Don't forget to configure all the border routers using a similar configuration but with appropriate changes. Now configure the master controller.
Master Controller
key chain key1key 1key-string border1key chain key2key 1key-string border2key chain key3key 1key-string border3oer masterloggingborder 10.1.1.1 key-chain key1interface Ethernet3/1 externalcost-minimization nickname ISP1cost-minimization tier 100 fee 50000cost-minimization tier 65 fee 10000cost-minimization tier 30 fee 500cost-minimization end day-of-month 24cost-minimization sampling period 5 rollup 1440cost-minimization discard absolute 10exitinterface Ethernet0/2 internalexitborder 10.2.1.2 key-chain key2interface Ethernet3/2 externalinterface Ethernet0/2 internalexitborder 10.4.1.4 key-chain key3interface Serial4/0 externalcost-minimization nickname ISP2cost-minimization fixed fee 3000cost-minimization end day-of-month 24exitinterface Ethernet0/2 internalexitno max range receivedelay threshold 10000loss threshold 1000000mode route controlmode monitor passivemode select-exit bestresolve cost priority 1active-probe echo 10.1.9.1endNow enter the show oer master cost-minimization border command at the master controller to show the configuration and the utilization statistics. The rollup values during the 30-day March through April 24th billing period for the Ethernet interface 3/1 on border router 10.1.1.1 are shown in the output:
Router# show oer master cost-minimization border 10.1.1.1pM - per Month, pD - per Day--------------------------------------------------------------------------------Nickname : ISP1 Border: 10.1.1.1 Interface: Et3/1Calc type : SeparateEnd Date : 24Summer time: DisabledFee : Tier BasedTier 1: 100, fee: 50000Tier 2: 65, fee: 10000Tier 3: 30, fee: 500Period : Sampling 5, Rollup 1440Discard : Type Absolute, Value 10Rollup Information:Total(pM) Discard(pM) Remaining(pM) Collected(pM)31 10 1 29Current Rollup Information:MomentaryTgtUtil: 75 Kbps CumRxBytes: 0StartingRollupTgt: 75 Kbps CumTxBytes: 0CurrentRollupTgt: 75 Kbps TimeRemain: 00:00:51Rollup Utilization (Kbps):Egress Utilization Rollups (Descending order)1 : 0 2 : 89 3 : 80 4 : 715 : 70 6 : 65 7 : 65 8 : 519 : 50 10 : 49 11 : 49 12 : 4513 : 42 14 : 39 15 : 35 16 : 3417 : 30 18 : 30 19 : 30 20 : 2921 : 25 22 : 20 23 : 19 24 : 1225 : 10 26 : 10 27 : 9 28 : 829 : 4 30 : 1Ingress Utilization Rollups (Descending order)1 : 0 2 : 92 3 : 84 4 : 825 : 80 6 : 78 7 : 75 8 : 739 : 72 10 : 70 11 : 63 12 : 6213 : 60 14 : 55 15 : 53 16 : 5217 : 45 18 : 43 19 : 35 20 : 3321 : 31 22 : 25 23 : 23 24 : 2125 : 15 26 : 11 27 : 10 28 : 1029 : 5 30 : 1If we assume that the March through April 24th billing period is over, we can see the billing for the previous billing period using the show oer master cost-minimization billing-history command. The monthly sustained utilization is 62 and the cost is $10,000 for the Ethernet interface 3/1 link on border router 10.1.1.1. Note that the same figures in Table 1 were used to create this example output.
Router# show oer master cost-minimization billing-historyBilling History for the past three monthsISP2 on 10.4.1.4 Se4/0No cost min on 10.2.1.2 Et3/2ISP1 on 10.1.1.1 Et3/1Mon1 Mon2 Mon3Nickname SustUtil Cost SustUtil Cost SustUtil Cost---------- ------------------ ------------------ ------------------ISP2 0 3000 ---NA--- ---NA---ISP1 62 10000 ---NA--- ---NA------------- ------------------ ------------------ ------------------Total Cost 13000 0 0Where to Go Next
This module covers PfR cost policies. To learn more about PfR, start with the "Cisco IOS Optimized Edge Routing Overview" and the "Setting Up OER Network Components" module. To learn more about the OER phases (same as Performance Routing phases) identified in the Overview module, read through the other modules in the following list:
•
•
•
•
Additional References
The following sections provide references related to configuring and applying PfR cost policies.
Related Documents
Technical Assistance
Feature Information for Configuring Performance Routing Cost Policies
Table 2 lists the features in this module and provides links to specific configuration information. Only features that were introduced or modified in Cisco IOS Release 12.3(8)T, 12.2(33)SRB, 12.2(33)SXH, or a later release appear in the table.
For information on a feature in this technology that is not documented here, see the "Cisco IOS Optimized Edge Routing Feature Roadmap."
Not all commands may be available in your Cisco IOS software release. For release information about a specific command, see the command reference documentation.
Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which Cisco IOS and Catalyst OS software images support a specific software release, feature set, or platform. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Note
Table 2 Feature Information for Configuring Performance Routing Cost Policies
Optimized Edge Routing
12.3(8)T
12.2(33)SRB
12.2(33)SXHOER was introduced.
OER Support for Cost-Based Optimization
12.3(14)T
12.2(33)SRB
12.4(15)T9The OER Support for Cost-Based Optimization feature introduced the capability to configure exit link policies based monetary cost and the capability to configure traceroute probes to determine prefix characteristics on a hop-by-hop basis.
In Cisco IOS Release 12.4(15)T9 and later releases, the calculation of the MTLU algorithm is modified to allow for more efficient bandwidth utilization while minimizing the link cost.
The following sections provide information about this feature:
•
•
•
•
•
•
The following commands were introduced or modified by this feature: cost-minimization, debug oer master cost-minimization, show oer master cost-minimization.
CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card, and One Million Acts of Green are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0910R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
© 2009 Cisco Systems, Inc. All rights reserved.
