|
Command or Action |
Purpose |
Step 1 |
enable
Example:
|
Enables privileged EXEC mode.
-
Enter your password if prompted.
|
Step 2 |
configure terminal
Example:
Router# configure terminal
|
Enters global configuration mode. |
Step 3 |
pfr master
Example:
Router(config)# pfr master
|
Enters PfR 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-pfr-mc)# border 10.1.1.1 key-chain pfr
|
Enters PfR-managed border router configuration mode to establish communication with a border router.
-
An IP address is configured to identify the border router.
-
The value for the key-chain-name argument must match the key-chain name configured at the border router identified by the ip-address argument.
Note |
The key-chain keyword and key-chain-name argument must be entered when a border router is initially configured. However, this keyword is optional when reconfiguring or adding configuration for this border router. |
|
Step 5 |
interface type number external
Example:
Router(config-pfr-mc-br)# interface ethernet 0/0 external
|
Enters PfR border exit interface configuration mode to configure a border router interface as a PfR-managed external interface.
-
At least one external interface must be configured on each border router.
-
Configuring an interface as a PfR-managed external interface on a router enters PfR border exit interface configuration mode. In this mode, you can configure maximum link utilization or cost-based optimization for the interface.
|
Step 6 |
cost-minimization nickname name
Example:
Router(config-pfr-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.
-
In this example, the nickname label for the 10.1.1.1 border router link is 80-percent.
|
Step 7 |
cost-minimization summer-time start end [offset]
Example:
Router(config-pfr-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).
-
The start and end arguments are used to specify the week number, day, month and time in hours and minutes (24 hour clock) that summertime starts and ends.
-
The offset argument allows for an offset in minutes from 1 to 120 to allow for up to two additional hours to be added in the spring and subtracted in the fall.
-
In this example, summer time is configured to start the second week in March on a Sunday at 2 in the morning plus one hour, and end on Sunday in the first week in November at 2 in the morning minus one hour.
Note |
The summer-time keyword configuration is only required once for each master controller. |
|
Step 8 |
cost-minimization {fixed fee cost| tier percentage fee fee}
Example:
Router(config-pfr-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.
-
The fixed fee keywords and cost argument are used to specify a fixed (nonusage-based) cost associated with an exit link.
-
The percentage argument is used to specify the percentage of capacity utilization for a cost tier.
-
The tier fee keywords and fee argument are used to specify the fee associated with this tier.
-
In this example, the tier-based fee for 100 percent utilization is set to 1000.
Note |
The first tier specified must be the 100 percent capacity utilization. Any following tier configurations must be for lesser percentages and lower fees. When setting up tiers for load balancing, the tiers must be incrementally larger from one tier to the next tier on the same link in order for load balancing to work. |
|
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-pfr-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.
-
The utilization samples are ordered from the highest to the lowest and the number or percentage configured using this command removes the highest number or percentage from the list.
-
If the optional daily keyword is entered, samples are analyzed and discarded on a daily basis. If the daily keyword is not entered, by default the samples are analyzed and discarded on a monthly basis. At the end of the billing cycle, monthly sustained usage is calculated by averaging daily sustained utilization.
-
Use the absolute keyword to configure a set number of samples to be removed.
-
Use the percentage keyword to configure a percentage number of samples to be removed.
-
If a sampling rollup is configured, the discard values also applies to the rollup.
-
In this example, the highest 5 percent of samples are removed when calculating the sustained monthly utilization value.
|
Step 11 |
exit
Example:
Router(config-pfr-mc-br-if)# exit
|
Exits PfR border exit interface configuration mode and returns to PfR-managed border router configuration mode. |
Step 12 |
interface type number internal
Example:
Router(config-pfr-mc-br)# interface Ethernet 1/0 internal
|
Configures a border router interface as a PfR controlled internal interface.
-
Internal interfaces are used for passive monitoring only. Internal interfaces do not forward traffic.
-
At least one internal interface must be configured on each border router.
|
Step 13 |
exit
Example:
Router(config-pfr-mc-br-if)# exit
|
Exits PfR border exit interface configuration mode and returns to PfR-managed border router configuration mode. |
Step 14 |
Repeat Step 13 to return to PfR 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-pfr-mc)# mode route control
|
Configures route control for matched traffic.
-
In control mode, the master controller analyzes monitored prefixes and implements changes based on policy parameters.
|
Step 17 |
policy-rules map-name
Example:
Router(config-pfr-mc)# policy-rules cost_balance
|
Applies a configuration from a PfR map to a master controller configuration.
-
In this example, configuration from a PfR map named cost_balance is applied.
|
Step 18 |
exit
Example:
Router(config-pfr-mc)# exit
|
Exits PfR master controller configuration mode and returns to global configuration mode. |
Step 19 |
pfr-map map-name sequence-number
Example:
Router(config)# pfr-map cost_balance 10
|
Enters PfR map configuration mode to configure a PfR map. |
Step 20 |
match pfr learn {delay| inside| throughput}
Example:
Router(config-pfr-map)# match pfr learn throughput
|
Creates a match clause entry in a PfR map to match PfR learned prefixes.
-
Only a single match clause can be configured for each PfR map sequence.
-
In this example, a match clause entry is created to match traffic classes learned using the highest outbound throughput.
|
Step 21 |
set resolve cost priority value
Example:
Router(config-pfr-map)# set resolve cost priority 1
|
Creates a set clause entry in an PfR map to set policy priority for overlapping policies.
-
In this example, the resolve policy configures cost policies to have the highest priority.
-
In this task, only one type of PfR policy is given priority. Be aware that other PfR policies are usually configured and priorities must be carefully reviewed.
|
Step 22 |
end
Example:
Router(config-pfr-mc)# end
|
Exits PfR master controller configuration mode and returns to privileged EXEC mode. |