Performance Routing FAQs - Revision history

Jbarozet at 12:24, 17 October 2012

2012-10-17T12:24:06Z

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

	<font size = "4">'''Cisco Performance Routing (PfR) FAQs'''</font>		<font size = "4">'''Cisco Performance Routing (PfR) FAQs'''</font>
Line 536:		Line 542:
	Note: The legacy 'oer' and 'oer-map' keywords are currently being deprecated and were replaced by 'pfr' and 'pfr-map' in the CLI in Cisco IOS Release 15.1(2)T and Cisco IOS XE Release 3.1S. Optimized Edge Routing (OER) evolved into Performance Routing (PfR). OER represents the older technology that only optimized destination networks (i.e., prefixes), PfR represents the newer technology that is application aware and much more flexible and powerful.		Note: The legacy 'oer' and 'oer-map' keywords are currently being deprecated and were replaced by 'pfr' and 'pfr-map' in the CLI in Cisco IOS Release 15.1(2)T and Cisco IOS XE Release 3.1S. Optimized Edge Routing (OER) evolved into Performance Routing (PfR). OER represents the older technology that only optimized destination networks (i.e., prefixes), PfR represents the newer technology that is application aware and much more flexible and powerful.

		+	<br><br>

-	[[Category:~~Performance Routing~~]]	+	[[Category:AVC]]
		+	[[Category:Performance_Routing]]

Lewright: /* Q. Where can I find the Performance Routing (PfR) documentation? */

2012-02-10T02:32:25Z

Q. Where can I find the Performance Routing (PfR) documentation?

← Older revision		Revision as of 02:32, 10 February 2012
Line 15:		Line 15:

	====Q. Where can I find the Performance Routing (PfR) documentation?====		====Q. Where can I find the Performance Routing (PfR) documentation?====
-	'''A.''' Today, we are designing part of our new PfR documentation strategy around the Cisco Docwiki server. We already have some basic and solution-type documents at [[PfR:Solutions]]. The new PfR command syntax cn be found at [http://www.cisco.com/en/US/docs/ios-xml/ios/pfr/command/pfr-cr-book.html], The feature configuration modules are documented for each release train. Cisco IOS Release 15.2M&T can be found at [http://www.cisco.com/en/US/docs/ios-xml/ios/pfr/configuration/15-2mt/pfr-15-2mt-book.html], Cisco IOS Release 15.1M&T can be found at [http://www.cisco.com/en/US/docs/ios-xml/ios/pfr/configuration/15-1mt/pfr-15-1mt-book.html], Cisco IOS Release 15.2S can be found at [http://www.cisco.com/en/US/docs/ios-xml/ios/pfr/configuration/15-2s/pfr-15-2s-book.html] and the Cisco IOS XE Release 3S PfR documents can be found at [http://www.cisco.com/en/US/docs/ios-xml/ios/pfr/configuration/xe-3s/pfr-xe-3s-book.html]. The old OER syntax documentation for Cisco IOS Release 15.1 and can be found at [http://www.cisco.com/en/US/docs/ios-xml/ios/oer/configuration/15-1mt/oer-15-1mt-book.html]. The documentation links can also be found at the [http://www.cisco.com/go/pfr PfR] Marketing page.	+	'''A.''' Today, we are designing part of our new PfR documentation strategy around the Cisco Docwiki server. We already have some basic and solution-type documents at [[PfR:Solutions]]. The new PfR command syntax can be found at [http://www.cisco.com/en/US/docs/ios-xml/ios/pfr/command/pfr-cr-book.html], The feature configuration modules are documented for each release train. Cisco IOS Release 15.2M&T can be found at [http://www.cisco.com/en/US/docs/ios-xml/ios/pfr/configuration/15-2mt/pfr-15-2mt-book.html], Cisco IOS Release 15.1M&T can be found at [http://www.cisco.com/en/US/docs/ios-xml/ios/pfr/configuration/15-1mt/pfr-15-1mt-book.html], Cisco IOS Release 15.2S can be found at [http://www.cisco.com/en/US/docs/ios-xml/ios/pfr/configuration/15-2s/pfr-15-2s-book.html] and the Cisco IOS XE Release 3S PfR documents can be found at [http://www.cisco.com/en/US/docs/ios-xml/ios/pfr/configuration/xe-3s/pfr-xe-3s-book.html]. The old OER syntax documentation for Cisco IOS Release 15.1 and can be found at [http://www.cisco.com/en/US/docs/ios-xml/ios/oer/configuration/15-1mt/oer-15-1mt-book.html]. The documentation links can also be found at the [http://www.cisco.com/go/pfr PfR] Marketing page.

	====Q. What is the difference between Performance Routing and Cisco IOS Optimized Edge Routing (OER)?====		====Q. What is the difference between Performance Routing and Cisco IOS Optimized Edge Routing (OER)?====

Lewright: /* Q. Where can I find the Performance Routing (PfR) documentation? */

2012-01-25T01:38:12Z

Q. Where can I find the Performance Routing (PfR) documentation?

← Older revision		Revision as of 01:38, 25 January 2012
Line 15:		Line 15:

	====Q. Where can I find the Performance Routing (PfR) documentation?====		====Q. Where can I find the Performance Routing (PfR) documentation?====
-	'''A.''' Today, we are designing part of our new PfR documentation strategy around the Cisco Docwiki server. We already have some basic and solution-type documents at [[PfR:Solutions]]. The new PfR command syntax cn be found at [http://www.cisco.com/en/US/docs/ios-xml/ios/pfr/command/pfr-cr-book.html], The feature configuration modules are documented for each release train. Cisco IOS Release 15.2M&T can be found at [http://www.cisco.com/en/US/docs/ios-xml/ios/pfr/configuration/15-2mt/pfr-15-2mt-book.html], Cisco IOS Release 15.1M&T can be found at [http://www.cisco.com/en/US/docs/ios-xml/ios/pfr/configuration/15-1mt/pfr-15-1mt-book.html], Cisco IOS Release 15.2S can be found at [http://www.cisco.com/en/US/docs/ios-xml/ios/pfr/configuration/15-0s/pfr-15-2s-book.html] and the Cisco IOS XE Release 3S PfR documents can be found at [http://www.cisco.com/en/US/docs/ios-xml/ios/pfr/configuration/xe-3s/pfr-xe-3s-book.html]. The old OER syntax documentation for Cisco IOS Release 15.1 and can be found at [http://www.cisco.com/en/US/docs/ios-xml/ios/oer/configuration/15-1mt/oer-15-1mt-book.html]. The documentation links can also be found at the [http://www.cisco.com/go/pfr PfR] Marketing page.	+	'''A.''' Today, we are designing part of our new PfR documentation strategy around the Cisco Docwiki server. We already have some basic and solution-type documents at [[PfR:Solutions]]. The new PfR command syntax cn be found at [http://www.cisco.com/en/US/docs/ios-xml/ios/pfr/command/pfr-cr-book.html], The feature configuration modules are documented for each release train. Cisco IOS Release 15.2M&T can be found at [http://www.cisco.com/en/US/docs/ios-xml/ios/pfr/configuration/15-2mt/pfr-15-2mt-book.html], Cisco IOS Release 15.1M&T can be found at [http://www.cisco.com/en/US/docs/ios-xml/ios/pfr/configuration/15-1mt/pfr-15-1mt-book.html], Cisco IOS Release 15.2S can be found at [http://www.cisco.com/en/US/docs/ios-xml/ios/pfr/configuration/15-2s/pfr-15-2s-book.html] and the Cisco IOS XE Release 3S PfR documents can be found at [http://www.cisco.com/en/US/docs/ios-xml/ios/pfr/configuration/xe-3s/pfr-xe-3s-book.html]. The old OER syntax documentation for Cisco IOS Release 15.1 and can be found at [http://www.cisco.com/en/US/docs/ios-xml/ios/oer/configuration/15-1mt/oer-15-1mt-book.html]. The documentation links can also be found at the [http://www.cisco.com/go/pfr PfR] Marketing page.

	====Q. What is the difference between Performance Routing and Cisco IOS Optimized Edge Routing (OER)?====		====Q. What is the difference between Performance Routing and Cisco IOS Optimized Edge Routing (OER)?====

Lewright: /* Q. Where can I find the Performance Routing (PfR) documentation? */

2012-01-25T01:36:09Z

Q. Where can I find the Performance Routing (PfR) documentation?

← Older revision		Revision as of 01:36, 25 January 2012
Line 15:		Line 15:

	====Q. Where can I find the Performance Routing (PfR) documentation?====		====Q. Where can I find the Performance Routing (PfR) documentation?====
-	'''A.''' Today, we are designing part of our new PfR documentation strategy around the Cisco Docwiki server. We already have some basic and solution-type documents at [[PfR:Solutions]]. The new PfR command syntax cn be found at [http://www.cisco.com/en/US/docs/ios-xml/ios/pfr/command/pfr-cr-book.html], The feature configuration modules are documented for each release train. Cisco IOS Release 15.2M&T can be found at [http://www.cisco.com/en/US/docs/ios-xml/ios/pfr/configuration/15-2mt/pfr-15-2mt-book.html], Cisco IOS Release 15.1M&T can be found at [http://www.cisco.com/en/US/docs/ios-xml/ios/pfr/configuration/15-1mt/pfr-15-1mt-book.html], Cisco IOS Release 15.2S can be found at [http://www.cisco.com/en/US/docs/ios-xml/ios/pfr/configuration/15-0s/pfr-15-~~2s_book~~.html] and the Cisco IOS XE Release 3S PfR documents can be found at [http://www.cisco.com/en/US/docs/ios-xml/ios/pfr/configuration/xe-3s/pfr-xe-3s-book.html]. The old OER syntax documentation for Cisco IOS Release 15.1 and can be found at [http://www.cisco.com/en/US/docs/ios-xml/ios/oer/configuration/15-1mt/oer-15-1mt-book.html]. The documentation links can also be found at the [http://www.cisco.com/go/pfr PfR] Marketing page.	+	'''A.''' Today, we are designing part of our new PfR documentation strategy around the Cisco Docwiki server. We already have some basic and solution-type documents at [[PfR:Solutions]]. The new PfR command syntax cn be found at [http://www.cisco.com/en/US/docs/ios-xml/ios/pfr/command/pfr-cr-book.html], The feature configuration modules are documented for each release train. Cisco IOS Release 15.2M&T can be found at [http://www.cisco.com/en/US/docs/ios-xml/ios/pfr/configuration/15-2mt/pfr-15-2mt-book.html], Cisco IOS Release 15.1M&T can be found at [http://www.cisco.com/en/US/docs/ios-xml/ios/pfr/configuration/15-1mt/pfr-15-1mt-book.html], Cisco IOS Release 15.2S can be found at [http://www.cisco.com/en/US/docs/ios-xml/ios/pfr/configuration/15-0s/pfr-15-2s-book.html] and the Cisco IOS XE Release 3S PfR documents can be found at [http://www.cisco.com/en/US/docs/ios-xml/ios/pfr/configuration/xe-3s/pfr-xe-3s-book.html]. The old OER syntax documentation for Cisco IOS Release 15.1 and can be found at [http://www.cisco.com/en/US/docs/ios-xml/ios/oer/configuration/15-1mt/oer-15-1mt-book.html]. The documentation links can also be found at the [http://www.cisco.com/go/pfr PfR] Marketing page.

	====Q. What is the difference between Performance Routing and Cisco IOS Optimized Edge Routing (OER)?====		====Q. What is the difference between Performance Routing and Cisco IOS Optimized Edge Routing (OER)?====

Jbarozet at 10:58, 19 January 2012

2012-01-19T10:58:37Z

← Older revision		Revision as of 10:58, 19 January 2012
Line 252:		Line 252:
	'''A.''' In PfR Active mode alone, PfR only probes the active exit alone and continues to do so until an out of policy event is detected on that exit. At that moment in Active mode, all the exits are probed to find and identify the next INPOLICY exit. In contrast to that, in PfR Fast Mode, all the defined exits are probed all the time (continually).		'''A.''' In PfR Active mode alone, PfR only probes the active exit alone and continues to do so until an out of policy event is detected on that exit. At that moment in Active mode, all the exits are probed to find and identify the next INPOLICY exit. In contrast to that, in PfR Fast Mode, all the defined exits are probed all the time (continually).

-	====Q. I found something on the PfR wiki that seems to suggest multiple probes to same destination (different ports) is “better” than a single probe. Would someone be able to elaborate?	+	====Q. I found something on the PfR wiki that seems to suggest multiple probes to same destination (different ports) is “better” than a single probe. Would someone be able to elaborate?====
-	'''A.''' Jitter/UDP probe relies on control packet. If control packet is lost then no measurement is done. So if you only have one target and if control packet is lost then there will be no probe results. Now, if the link is totally unreachable or high loss it wouldn't matter. But if there is low loss then you would be better off having three probes. At least one other probe will succeed. It is okay to loose probe packet.	+	'''A.''' Jitter/UDP probe relies on control packet. If control packet is lost then no measurement is done. So if you only have one target and if control packet is lost then there will be no probe results. Now, if the link is totally unreachable or high loss it wouldn't matter. But if there is low loss then you would be better off having three probes. At least one other probe will succeed. It is okay to loose probe packet. The other thing is with the MOS. MOS is calculated for the entire probe. With one target you will only have one MOS value. With three targets you will have 3 MOS values.
-	The other thing is with the MOS. MOS is calculated for the entire probe. With one target you will only have one MOS value. With three targets you will have 3 MOS values.	+

	==Command-Line Interface==		==Command-Line Interface==

Jbarozet at 10:56, 19 January 2012

2012-01-19T10:56:57Z

← Older revision		Revision as of 10:56, 19 January 2012
Line 251:		Line 251:
	====Q. In PfR Active Fast Mode, why can't we just change the probe frequency to match fast mode? Why have another mode?====		====Q. In PfR Active Fast Mode, why can't we just change the probe frequency to match fast mode? Why have another mode?====
	'''A.''' In PfR Active mode alone, PfR only probes the active exit alone and continues to do so until an out of policy event is detected on that exit. At that moment in Active mode, all the exits are probed to find and identify the next INPOLICY exit. In contrast to that, in PfR Fast Mode, all the defined exits are probed all the time (continually).		'''A.''' In PfR Active mode alone, PfR only probes the active exit alone and continues to do so until an out of policy event is detected on that exit. At that moment in Active mode, all the exits are probed to find and identify the next INPOLICY exit. In contrast to that, in PfR Fast Mode, all the defined exits are probed all the time (continually).
		+
		+	====Q. I found something on the PfR wiki that seems to suggest multiple probes to same destination (different ports) is “better” than a single probe. Would someone be able to elaborate?
		+	'''A.''' Jitter/UDP probe relies on control packet. If control packet is lost then no measurement is done. So if you only have one target and if control packet is lost then there will be no probe results. Now, if the link is totally unreachable or high loss it wouldn't matter. But if there is low loss then you would be better off having three probes. At least one other probe will succeed. It is okay to loose probe packet.
		+	The other thing is with the MOS. MOS is calculated for the entire probe. With one target you will only have one MOS value. With three targets you will have 3 MOS values.

	==Command-Line Interface==		==Command-Line Interface==

Lewright: /* Q. Is Performance Routing (PfR) configuration complex? */

2011-11-28T00:46:56Z

Q. Is Performance Routing (PfR) configuration complex?

← Older revision		Revision as of 00:46, 28 November 2011
Line 256:		Line 256:
	'''A.''' Basic Performance Routing configuration using the command-line interface (CLI) is very simple, with most of the configuration performed on the Master Controller. For an example of a simple link-utilization-based Performance Routing policy, see Figure 3.		'''A.''' Basic Performance Routing configuration using the command-line interface (CLI) is very simple, with most of the configuration performed on the Master Controller. For an example of a simple link-utilization-based Performance Routing policy, see Figure 3.

-	Note: The legacy 'oer' ~~and 'oer-map' keywords are~~ currently being deprecated and ~~were~~ replaced by 'pfr~~' and 'pfr-map~~' in the CLI in Cisco IOS Release 15.1(2)T and Cisco IOS XE Release 3.1S. Optimized Edge Routing (OER) evolved into Performance Routing (PfR). OER represents the older technology that only optimized destination networks (~~i.e.~~, prefixes), PfR represents the newer technology that is application aware and much more flexible and powerful.	+	Note: The legacy 'oer' keyword is currently being deprecated and is replaced by 'pfr' in the CLI in Cisco IOS Release 15.1(2)T and Cisco IOS XE Release 3.1S. Optimized Edge Routing (OER) evolved into Performance Routing (PfR). OER represents the older technology that only optimized destination networks (for example, prefixes), PfR represents the newer technology that is application aware and much more flexible and powerful.

	Figure 3. '''Cisco Performance Routing Configuration'''		Figure 3. '''Cisco Performance Routing Configuration'''

Lewright: /* Q. Is Performance Routing (PfR) configuration complex? */

2011-11-28T00:45:20Z

Q. Is Performance Routing (PfR) configuration complex?

← Older revision		Revision as of 00:45, 28 November 2011
Line 255:		Line 255:
	====Q. Is Performance Routing (PfR) configuration complex?====		====Q. Is Performance Routing (PfR) configuration complex?====
	'''A.''' Basic Performance Routing configuration using the command-line interface (CLI) is very simple, with most of the configuration performed on the Master Controller. For an example of a simple link-utilization-based Performance Routing policy, see Figure 3.		'''A.''' Basic Performance Routing configuration using the command-line interface (CLI) is very simple, with most of the configuration performed on the Master Controller. For an example of a simple link-utilization-based Performance Routing policy, see Figure 3.
		+
		+	Note: The legacy 'oer' and 'oer-map' keywords are currently being deprecated and were replaced by 'pfr' and 'pfr-map' in the CLI in Cisco IOS Release 15.1(2)T and Cisco IOS XE Release 3.1S. Optimized Edge Routing (OER) evolved into Performance Routing (PfR). OER represents the older technology that only optimized destination networks (i.e., prefixes), PfR represents the newer technology that is application aware and much more flexible and powerful.

	Figure 3. '''Cisco Performance Routing Configuration'''		Figure 3. '''Cisco Performance Routing Configuration'''

Lewright: /* Q. How do I use Performance Routing for performance monitoring when I only have one external interface? */

2011-11-28T00:41:02Z

Q. How do I use Performance Routing for performance monitoring when I only have one external interface?

← Older revision		Revision as of 00:41, 28 November 2011
Line 350:		Line 350:

	<pre>configure terminal		<pre>configure terminal
-	~~oer~~ master	+	pfr master
	border 10.1.1.1		border 10.1.1.1
	interface Dialer 1 external		interface Dialer 1 external
Line 359:		Line 359:
	'''On PfR Master Router'''		'''On PfR Master Router'''

-	<pre>~~oer~~ master	+	<pre>pfr master
	border 10.1.1.1 key-chain key1		border 10.1.1.1 key-chain key1
	interface Dialer1 external		interface Dialer1 external

Lewright: /* Q. In a PfR "OER-MAP" , what does the associated number specify: */

2011-11-28T00:39:26Z

Q. In a PfR "OER-MAP" , what does the associated number specify:

← Older revision		Revision as of 00:39, 28 November 2011
Line 525:		Line 525:
	'''A.''' PfR Route-Maps will be applied onto the Internal Interfaces. For Dynamic Route-Maps to work, PfR requires a direct L3 connection, or a common subnet between the BR's. Without this direct connection PfR's PBR requirement will not be met and dynamic route maps will not function. You can also optionally use a direct L2 connection with a GRE Tunnel configured between the BR's Internal Interfaces to connect them as well in place of a common L3 subnet connection.		'''A.''' PfR Route-Maps will be applied onto the Internal Interfaces. For Dynamic Route-Maps to work, PfR requires a direct L3 connection, or a common subnet between the BR's. Without this direct connection PfR's PBR requirement will not be met and dynamic route maps will not function. You can also optionally use a direct L2 connection with a GRE Tunnel configured between the BR's Internal Interfaces to connect them as well in place of a common L3 subnet connection.

-	====Q. In a PfR "~~OER~~-MAP" , what does the associated number specify:====	+	====Q. In a PfR "PFR-MAP" , what does the associated number specify:====
	'''A.''' In PfR you can define a policy containing multiple traffic-classes. By using different sequence numbers you can control the priority. By default the lower sequence number will be the higher priority under that policy.		'''A.''' In PfR you can define a policy containing multiple traffic-classes. By using different sequence numbers you can control the priority. By default the lower sequence number will be the higher priority under that policy.
-	~~oer~~-map MYMAP 30 <- what is 30	+	pfr-map MYMAP 30 <- what is 30

-	Note: The legacy 'oer' and 'oer-map' keywords are being deprecated and replaced by 'pfr' and 'pfr-map' in the CLI. Optimized Edge Routing (OER) evolved into Performance Routing (PfR). OER represents the older technology that only optimized destination networks (i.e., prefixes), PfR represents the newer technology that is application aware and much more flexible and powerful.	+	Note: The legacy 'oer' and 'oer-map' keywords are currently being deprecated and were replaced by 'pfr' and 'pfr-map' in the CLI in Cisco IOS Release 15.1(2)T and Cisco IOS XE Release 3.1S. Optimized Edge Routing (OER) evolved into Performance Routing (PfR). OER represents the older technology that only optimized destination networks (i.e., prefixes), PfR represents the newer technology that is application aware and much more flexible and powerful.


	[[Category:Performance Routing]]		[[Category:Performance Routing]]