PfR:Technology Overview - Revision history

Jcarvaja: /* Example2 - Correct use of ACL with learn list */

2013-03-29T02:30:01Z

Example2 - Correct use of ACL with learn list

← Older revision		Revision as of 02:30, 29 March 2013
Line 380:		Line 380:
	! FTP application		! FTP application
	ip access-list extended MY_APP 10		ip access-list extended MY_APP 10
-	permit ip any any eq 21	+	permit tcp any any eq 21
	!		!
	ip prefix-list FILTER_BRANCH1 seq 10 permit 10.1.1.0/24		ip prefix-list FILTER_BRANCH1 seq 10 permit 10.1.1.0/24
Line 398:		Line 398:

	</pre>		</pre>
-	<br> <br>	+	<br> <br>

	= Measuring Phase =		= Measuring Phase =

2013-03-29T02:22:06Z

Manual Configuration

← Older revision		Revision as of 02:22, 29 March 2013
Line 246:		Line 246:
	! Define FTP application		! Define FTP application
	ip access-list extended MY_APP 10		ip access-list extended MY_APP 10
-	permit ip any any eq 21	+	permit tcp any any eq 21
	!		!
	pfr-map MYMAP 10		pfr-map MYMAP 10
Line 278:		Line 278:
	<br> This mode is used when you know the prefixes or applications to optimize and want to explicitly list them.		<br> This mode is used when you know the prefixes or applications to optimize and want to explicitly list them.

-	<br>	+	<br>

	== Automatic Configuration ==		== Automatic Configuration ==

2013-02-26T22:53:24Z

2012-10-17T12:20:45Z

← Older revision		Revision as of 12:20, 17 October 2012
Line 1:		Line 1:
		+	<meta name="keywords" content="PfR, Performance Routing, AVC, Application Visibility and Control"></meta>
		+
	<br>		<br>

Line 753:		Line 755:

	<br>		<br>
		+
		+	[[Category:AVC]]
		+	[[Category:Performance_Routing]]

2012-09-21T13:07:10Z

Measuring Phase

← Older revision		Revision as of 13:07, 21 September 2012
Line 479:		Line 479:
	<br>		<br>

-	== Mode monitor both ==	+	== Hybrid Modes ==
		+
		+	[[Image:Pfr-monitor-hybrid.png\|600px]]
		+
		+	=== Mode monitor both ===

	Mode monitor both is the default value and combines the capabilities of passive and active monitoring. Up to five IP addresses are actively probed for each destination prefix network learned through passive monitoring. By default, an IP SLA ICMP ECHO probe is automatically generated for the learned IP addresses.		Mode monitor both is the default value and combines the capabilities of passive and active monitoring. Up to five IP addresses are actively probed for each destination prefix network learned through passive monitoring. By default, an IP SLA ICMP ECHO probe is automatically generated for the learned IP addresses.
Line 493:		Line 497:
	<br>		<br>

-	== Mode monitor Fast ==	+	=== Mode monitor Fast ===

	This feature was introduced in Cisco IOS Release 12.4(15)T as a key component to the Fast Reroute feature.		This feature was introduced in Cisco IOS Release 12.4(15)T as a key component to the Fast Reroute feature.

2012-09-21T13:06:16Z

Mode monitor active

← Older revision		Revision as of 13:06, 21 September 2012
Line 454:		Line 454:

	Active monitoring is the act of generating Cisco IOS IP Service Level Agreements (SLAs) probes to generate test traffic for the purpose of obtaining information regarding the characteristics of the WAN links. PfR can either implicitly generates active probes when passive monitoring has identified destination hosts, or the network manager can explicitly configured probes in the PfR configuration.		Active monitoring is the act of generating Cisco IOS IP Service Level Agreements (SLAs) probes to generate test traffic for the purpose of obtaining information regarding the characteristics of the WAN links. PfR can either implicitly generates active probes when passive monitoring has identified destination hosts, or the network manager can explicitly configured probes in the PfR configuration.
		+
		+	[[Image:Pfr-monitor-active.png\|600px]]

	In this mode, IP SLAs probes are generated by the border routers through the current exits and transmitted at the configured probe frequency value.		In this mode, IP SLAs probes are generated by the border routers through the current exits and transmitted at the configured probe frequency value.

2012-09-21T13:05:36Z

Mode monitor passive

← Older revision		Revision as of 13:05, 21 September 2012
Line 438:		Line 438:

	The border routers report traffic flows identified by Netflow to the master controller. The average delay of the flows, packet loss, and reachability along with the outbound throughput in terms of bits per second is determined for the destination IP prefixes observed in the Netflow data.		The border routers report traffic flows identified by Netflow to the master controller. The average delay of the flows, packet loss, and reachability along with the outbound throughput in terms of bits per second is determined for the destination IP prefixes observed in the Netflow data.
		+
		+
		+	[[Image:Pfr-monitor-passive.png\|600px]]

	Measurements of the TCP traffic flows are characterized by:		Measurements of the TCP traffic flows are characterized by:

2012-04-09T16:30:47Z

Fixed typo

← Older revision		Revision as of 16:30, 9 April 2012
Line 428:		Line 428:
	* “TCP, UDP, Jitter need IP SLA responder targets defined”		* “TCP, UDP, Jitter need IP SLA responder targets defined”
	* Mode monitor Both: It is the default (recommended)		* Mode monitor Both: It is the default (recommended)
-	* Mode ~~moinitor~~ Fast: recommended for fast convergence	+	* Mode monitor Fast: recommended for fast convergence

2012-02-25T17:02:59Z

Automatic Configuration

← Older revision		Revision as of 17:02, 25 February 2012
Line 306:		Line 306:
	'''learn-list'''		'''learn-list'''
	<br>		<br>
-	PfR supports a learn list configuration mode to simplify the learning of traffic classes and to provide greater flexibility.	+	PfR supports a learn list configuration mode to simplify the learning of traffic classes (TC) and to provide greater flexibility.
-	In each learn list, different criteria including prefixes, application definitions, filters, and aggregation parameters for learning traffic classes can be configured. A traffic class is automatically learned by PfR based on each learn list criteria, and each learn list is configured with a sequence number. The sequence number determines the order in which learn list criteria are applied. Learn lists allow different PfR policies to be applied to each ~~learn list~~.	+	In each learn list, different criteria including prefixes, application definitions, filters, and aggregation parameters for learning traffic classes can be configured. A traffic class is automatically learned by PfR based on each learn list criteria, and each learn list is configured with a sequence number. The sequence number determines the order in which learn list criteria are applied. Learn lists allow different PfR policies to be applied to each TC.

	<pre>		<pre>

2011-10-24T09:37:37Z

PfR Features that Enable Load Balancing

← Older revision		Revision as of 09:37, 24 October 2011
Line 523:		Line 523:
	=== Link Utilization ===		=== Link Utilization ===

-	Usage of this policy sets an upper threshold on the amount of traffic a specific link can carry. For example, if the upper threshold for a link is 90 % of total bandwidth, and it is currently running at 95 % of bandwidth, the link is Out-of-Policy (OOP). Cisco PfR will attempt to bring the link back into policy by repeatedly moving prefixes from the over-used link onto other exit links.	+	Usage of this policy sets an upper threshold on the amount of traffic a specific link can carry. Both exit link traffic and entrance link traffic load thresholds can be configured as a PfR policy. For example, if the upper threshold for a link is 90 % of total bandwidth, and it is currently running at 95 % of bandwidth, the link is Out-of-Policy (OOP). Cisco PfR will attempt to bring the link back into policy by repeatedly moving prefixes from the over-used link onto other exit links.

	=== Range ===		=== Range ===