This documentation has been moved
Using Performance Routing to Control EIGRP Routes with mGRE DMVPN Hub-and-Spoke Support
Download this chapter
Using Performance Routing to Control EIGRP Routes with mGRE DMVPN Hub-and-Spoke SupportUsing Performance Routing to Control EIGRP Routes with mGRE DMVPN Hub-and-Spoke Support
Download the complete book
Performance Routing Configuration Guide, Cisco IOS Release 15.1M&TPerformance Routing Configuration Guide, Cisco IOS Release 15.1M&T (PDF - 3 MB)
 Feedback

Table Of Contents

Using Performance Routing to Control EIGRP Routes with mGRE DMVPN Hub-and-Spoke Support

Finding Feature Information

Contents

Prerequisites for Using PfR to Control EIGRP Routes

Restrictions for Using PfR to Control EIGRP Routes

Information About Using PfR to Control EIGRP Routes

PfR EIGRP Route Control

PfR and mGRE Dynamic Multipoint VPN

How to Configure PfR to Control EIGRP Routes

Enabling PfR EIGRP Route Control and Setting a Community Value

Disabling PfR EIGRP Route Control

Manually Verifying the PfR EIGRP-Controlled Routes

Prerequisites

Troubleshooting Tips

Configuration Examples for Using PfR to Control EIGRP Routes

Example: Enabling PfR EIGRP Route Control and Setting a Community Value

Where to Go Next

Additional References

Related Documents

Technical Assistance

Feature Information for Using PfR to Control EIGRP Routes


Using Performance Routing to Control EIGRP Routes with mGRE DMVPN Hub-and-Spoke Support

First Published: March 19, 2010
Last Updated: July 30, 2010

The PfR EIGRP mGRE DMVPN Hub-and-Spoke Support feature introduces the ability to inject routes into the EIGRP routing table, which allows Performance Routing (PfR) to control prefixes and applications over EIGRP routes. This feature also adds support for multicast Generic Routing Encapsulation (mGRE) Dynamic Multipoint Virtual Private Network (DMVPN) deployments that follow a hub-and-spoke network design.

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 Using PfR to Control EIGRP Routes" section.

Use Cisco Feature Navigator to find information about platform support and Cisco 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 Using PfR to Control EIGRP Routes

•Restrictions for Using PfR to Control EIGRP Routes

•Information About Using PfR to Control EIGRP Routes

•How to Configure PfR to Control EIGRP Routes

•Configuration Examples for Using PfR to Control EIGRP Routes

•Additional References

•Feature Information for Using PfR to Control EIGRP Routes

Prerequisites for Using PfR to Control EIGRP Routes

This feature assumes that EIGRP is already configured in your network and that basic PfR functionality is also configured. See the "Additional References" section for more details.

Restrictions for Using PfR to Control EIGRP Routes

•PfR does not support split tunneling.

•PfR supports hub-to-spoke links only. Spoke-to-spoke links are not supported. If you are deploying EIGRP in an mGRE DMVPN topology in your network, it must conform to a hub-and-spoke network design.

•PfR is supported on DMVPN Multipoint GRE (mGRE) deployments. Any multipoint interface deployment that has multiple next hops for the same destination IP address is not supported (for example, Ethernet).

Information About Using PfR to Control EIGRP Routes

•PfR EIGRP Route Control

•PfR and mGRE Dynamic Multipoint VPN

PfR EIGRP Route Control

The PfR EIGRP mGRE DMVPN Hub-and-Spoke Support feature introduces PfR route control for EIGRP. When enabled, a parent route check is performed in the EIGRP database for controlling PfR prefixes and routes in addition to the existing BGP and static route databases.

PfR can only optimize paths for prefixes, which have an exact matching route or a less specific route (also called as parent route) in the routing protocols. The route being controlled by PfR can be an exact match of the parent route or can be a more specific one. For example, if PfR wants to control 10.1.1.0/24 but the EIGRP routing table has only 10.1.0.0/16 then the parent route is 10.1.0.0/16 and PfR will inject 10.1.1.0/24 in the EIGRP routing table.

If an exact matching parent route in the EIGRP routing table is found, PfR will attempt to install a route on an exit selected by the master controller by influencing the metric. If an exact match parent is not found, then PfR introduces a new route in the EIGRP table that matches the attributes of the parent. If the route installation in the EIGRP table is successful, PfR saves the EIGRP parent and registers for any updates to the parent route. If the parent route is removed, PfR will uncontrol any routes it has installed in the EIGRP table based on this parent route.

PfR monitors traffic performance for prefixes it is controlling either passively using NetFlow or actively using IP SLA probes. Performance statistics such as delay, loss, and reachability are gathered and compared against a set of policies configured for the prefixes. If the traffic performance does not conform to the policies, the prefix is said to be out-of-policy (OOP). PfR tries to find an alternate path when the prefix goes into the OOP state.

While both BGP and static route control are enabled by default, EIGRP route control must be configured. PfR always attempts to control a prefix using BGP first. If BGP route control fails, static route control is tried. When EIGRP route control is enabled, PfR will attempt to control a prefix using BGP first. If no parent route is found, PfR will try to use EIGRP route control. If EIGRP route controls fails, static route control is tried.

To find an alternate path for a prefix, PfR tries to send active probes from all the external interfaces on the border routers to a set of hosts in the destination prefix network. Before an active probe can be sent on an external interface, a parent route lookup is performed in routing protocol tables. When the PfR EIGRP mGRE DMVPN Hub-and-Spoke Support feature is enabled, PfR checks EIGRP routing tables, in addition to BGP and static routing tables, for a parent route, before sending active probes on external interfaces. Active probes are initiated on all the external interfaces that have a parent route in the EIGRP routing table. When the probe activity completes and the timer expires, statistics are sent from the border router to the master controller for policy decision and selection of an optimal exit.

When an exit is selected, a control prefix command is sent to the border router with the selected exit, specifying EIGRP as the protocol to install or modify the route. When the border router receives the command, it checks the EIGRP table to find a parent route. If a parent route is found, PfR will install or modify the route in the EIGRP table and will notify the master controller about the route control status.

If an EIGRP route is successfully installed and advertised into the domain, PfR continues to monitor traffic performance for this prefix and takes further action as mentioned above if the prefix goes OOP.

For more details about the PfR control mode and details about other PfR exit link selection control techniques including BGP, static routes, policy-based routing, and Protocol Independent Route Optimization (PIRO), see the "Understanding Performance Routing" module and the "Performance Routing - Protocol Independent Route Optimization (PIRO)" module.

PfR and mGRE Dynamic Multipoint VPN

Performance Routing is supported on mGRE interfaces in Dynamic Multipoint VPN (DMVPN) topologies. DMVPN enables zero-touch deployment of IPsec encrypted VPN networks. Many DMVPN deployments use EIGRP networks, and support was added to PfR to allow DMVPN network deployments to use EIGRP route control within the DMVPN network. In the PfR EIGRP route control implementation, only hub-to-spoke network designs are supported.

In DMVPN topologies the mGRE interface works as a one-to-many interface and allows the dynamic creation of tunnels for each connected branch.

Figure 1 shows a typical dual DMVPN topology. The head office (R2) has one hub (hub1) that connects to the remote site spokes using one of the DMVPN networks (DMVPN 1 or DMVPN 2) or the MPLS-GETVPN network.

Remote site 1 (RS1) has spokes 1 and 2 that connect to the hub using the DMVPN1 and DMVPN2 networks. Remote site 2 (RS2) has spoke 3 and connects to the hub using DMVPN1 network only. This means that there is no redundancy at RS2 and any performance optimization is performed between the hub and RS2 only. Remote site 3 (RS3) has spoke 3 that connects to the hub using the DMVPN2 network and the MPLS-GETVPN network.

Figure 1 PfR Dual DMVPN Topology

When PfR is configured on the network, the system can perform these functions:

•Control and measure the performance of PfR traffic-classes on mGRE interfaces.

•Support load balancing for traffic over multipoint interfaces that are configured as PfR external interfaces. For example, in topologies with two DMVPN clouds PfR can be configured to load balance the traffic across the two tunnel interfaces to ensure that network performance is maintained.

•Reroute traffic from or to a multipoint interface for better performance. For example, PfR policies can be configured to select the best path to a spoke and the best path from the spoke to the hub.

•Provide a back-up connection if the primary connection fails. For example, in a topology with one MPLS-GETVPN and one DMVPN connection, the MPLS-GETVPN could act as a primary connection and PfR could be configured to use the DMVPN connection if the primary connection fails.

The DMVPN topology leverages protocols like multipoint GRE (mGRE) for hub-to-spoke functionality, and for spoke-to-spoke functionality it utilizes the Next Hop Resolution Protocol (NHRP). For more details about configuring mGRE DMVPN networks, see the Dynamic Multipoint VPN module. For general information about DMVPN, go to http://www.cisco.com/go/dmvpn.

How to Configure PfR to Control EIGRP Routes

•Enabling PfR EIGRP Route Control and Setting a Community Value

•Disabling PfR EIGRP Route Control

•Manually Verifying the PfR EIGRP-Controlled Routes

Enabling PfR EIGRP Route Control and Setting a Community Value

Perform this task on the master controller to enable EIGRP route control. While both BGP and static route control are enabled by default, EIGRP route control must be enabled using a command-line interface (CLI) command, mode route metric eigrp. PfR always attempts to control a prefix using BGP first. If BGP route control fails, static route control is tried. When EIGRP route control is enabled, PfR will attempt to control a prefix using BGP first. If no parent route is found, PfR will try to use EIGRP route control. If EIGRP route controls fails, static route control is tried.

This task can also set an extended community value for an injected EIGRP route to allow the routes to be uniquely identified. An EIGRP route may be injected by PfR to control the traffic defined by a traffic class when it goes out-of-policy (OOP). In this task, the PfR route control mode is configured globally with the mode route control command in PfR master controller configuration mode, and any injected EIGRP routes will be tagged with a value of 700.

SUMMARY STEPS

1. enable

2. configure terminal

3. pfr master

4. mode route control

5. mode route metric eigrp tag community

6. end

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

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 a router as a master controller and to configure global operations and policies.

Step 4 

mode route control

Example:

Router(config-pfr-mc)# mode route control

Configures the PfR route control mode on a master controller.

•The route and control keywords enable route control mode. In control mode, the master controller analyzes monitored traffic classes and implements changes based on policy parameters.

Step 5 

mode route metric eigrp tag community

Example:

Router(config-pfr-mc)# mode route metric eigrp tag 7000

Enables EIGRP route control and sets an EIGRP tag and community number value for injected EIGRP routes.

•Use the tag keyword to apply a tag to an EIGRP route under PfR control. The community argument is a number from 1 to 65535.

Step 6 

end

Example:

Router(config-pfr-mc)# end

Exits PfR master controller configuration mode and returns to privileged EXEC mode.

Disabling PfR EIGRP Route Control

Note When this task is complete, PfR withdraws all the routes that are being controlled using the EIGRP protocol.

SUMMARY STEPS

1. enable

2. configure terminal

3. pfr master

4. no mode route metric eigrp

5. end

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

enable

Example:

Router> enable

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 a router as a master controller and to configure global operations and policies.

Step 4 

no mode route metric eigrp

Example:

Router(config-pfr-mc)# no mode route metric eigrp

Disables EIGRP route control and removes all the routes that are being controlled using the EIGRP protocol.

Step 5 

end

Example:

Router(config-pfr-mc)# end

Exits PfR master controller configuration mode and returns to privileged EXEC mode.

Manually Verifying the PfR EIGRP-Controlled Routes

PfR automatically verifies route control changes in the network using NetFlow output. PfR monitors the NetFlow messages and uncontrols a traffic class if a message does not appear to verify the route control change. Perform the steps in this optional task if you want to manually verify that the traffic control implemented in the PfR control phase actually changes the traffic flow, and brings the OOP event to be in-policy.

All the steps in this task are optional and are not in any order. The information from these steps can verify that a specific prefix associated with a traffic class has been moved to another exit or entrance link interface, or that it is being controlled by PfR. The first two commands are entered at the master controller, the last two commands are entered at a border router.

Only partial command syntax for some of the show commands used in this task is displayed. For more details about PfR show commands, see the Cisco IOS Performance Routing Command Reference.

Prerequisites

This task assumes that you have previously enabled EIGRP route control using PfR. To enable PfR EIGRP route control, see the "Enabling PfR EIGRP Route Control and Setting a Community Value" section.

SUMMARY STEPS

1. enable

2. show pfr master prefix prefix [detail]

3. Move to a border router to enter the next step.

4. enable

5. show pfr border routes eigrp [parent]

DETAILED STEPS

Step 1 enable

Enables privileged EXEC mode. Enter your password if prompted. 

Router> enable

Step 2 show pfr master prefix prefix [detail]

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, protocol, prefix delay, and egress and ingress interface bandwidth. In this example, the protocol displayed for the prefix 10.1.0.0/16 is EIGRP, which means that the parent route for the traffic class exists in the EIGRP routing table and EIGRP community values are used to control the prefix. Only syntax relevant to this task is shown in this step. 

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

Step 3 Move to a border router to enter the next step.

The next command is entered on a border router, not the master controller.


Step 4 enable

Enables privileged EXEC mode. Enter your password if prompted. 

Router> enable

Step 5 show pfr border routes eigrp [parent]

This command is entered on a border router. Use this command to display information about EIGRP routes controlled by PfR on a border router. 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

10.1.2.0/24        6

Troubleshooting Tips

If the show commands are not displaying output that verifies the EIGRP route control, use the debug pfr border routes eigrp command with the optional detail keyword for more information. Debugging must be enabled before entering the required commands, and the debug output depends on which commands are subsequently entered.

Configuration Examples for Using PfR to Control EIGRP Routes

•Example: Enabling PfR EIGRP Route Control and Setting a Community Value

Example: Enabling PfR EIGRP Route Control and Setting a Community Value

In the following configuration example, PfR route control is enabled first, and then the EIGRP route control is enabled and configured to set an extended community value of 700 to any injected EIGRP routes: 

pfr master 

 mode route control

 mode route metric eigrp tag 700 

 end

Where to Go Next

This module covers PfR EIGRP route control and presumes that you are familiar with the PfR technology. If you want to review more information about PfR, see the documents that are listed under "Related Documents" section.

Additional References

Related Documents

Related Topic
Document Title

Cisco IOS commands

Cisco IOS Master Commands List, All Releases

Cisco PfR commands: complete command syntax, command mode, command history, defaults, usage guidelines and examples

Cisco IOS Performance Routing Command Reference

Basic PfR configuration

"Configuring Basic Performance Routing" module

Advanced PfR configuration

"Configuring Advanced Performance Routing" module

Concepts required to understand the Performance Routing operational phases

"Understanding Performance Routing" module

Location of PfR features

"Cisco IOS Performance Routing Features Roadmap" module

EIGRP Routing Protocol commands

Cisco IOS IP Routing: EIGRP Command Reference

Configuring mGRE DMVPN networks

Dynamic Multipoint VPN

General information about the DMVPN technology

http://www.cisco.com/go/dmvpn

Command Lookup Tool

http://tools.cisco.com/Support/CLILookup


Technical Assistance

Description
Link

The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies.

To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds.

Access to most tools on the Cisco Support website requires a Cisco.com user ID and password.

http://www.cisco.com/cisco/web/support/index.html


Feature Information for Using PfR to Control EIGRP Routes

Table 1 lists the release history for this feature.

Use Cisco Feature Navigator to find information about platform support and software image support. Cisco Feature Navigator enables you to determine which 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 1 lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.

Table 1 Feature Information for Using PfR to Control EIGRP Routes 

Feature Name
Releases
Feature Information

PfR EIGRP mGRE DMVPN Hub-and-Spoke Support

12.2(33)SRE
15.0(1)M
15.0(1)S

The PfR EIGRP feature introduces PfR route control capabilities based on EIGRP by performing a route parent check on the EIGRP database. This feature also adds support for mGRE Dynamic Multipoint VPN (DMVPN) deployments that follow a hub-and-spoke network design.

The following commands were introduced or modified: debug pfr border routes, mode (PfR), show pfr border routes, and show pfr master prefix.


Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned 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. (1005R)


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.

© 2010 Cisco Systems, Inc. All rights reserved.