PfR route injection examples and doc

anyone out there been able to find any examples on "how to" do static route
injection? the docs have this to say, but there is no further information
or examples on how to configure it.

please share if you do...

many thanks!
LG

 OER Exit Link Selection Control Techniques

To enforce an exit link selection, OER offers the following methods:

Static Route
Injection<https://mail.google.com/mail/html/compose/static_files/blank_quirks
.html#wp1054090>

BGP Control
Techniques<https://mail.google.com/mail/html/compose/static_files/blank_quirk
s.html#wp1054095>

EIGRP Route
Control<https://mail.google.com/mail/html/compose/static_files/blank_quirks.h
tml#wp1054102>

Policy-Based Routing
Control<https://mail.google.com/mail/html/compose/static_files/blank_quirks.h
tml#wp1065820>

Protocol Independent Route Optimization
(PIRO)<https://mail.google.com/mail/html/compose/static_files/blank_quirks.ht
ml#wp1062672>

Static Route Injection

An OER master controller can enforce the use of a particular border router
as the preferred exit link for a traffic class by injecting temporary static
routes. These static routes exist only in the memory of the router, and are
intentionally not saved to the permanent configuration. There are a few
different methods that the master controller can use to inject static routes
on the border routers. Existing static routes can be overwritten with new
static routes, which have a better routing metric. If a default route, or
even a less specific route, exists on the border router, the master
controller can add a specific static route for the monitored traffic
classes, which will be preferred to the existing default route. Finally, the
master controller can also use something known as split prefixes.

A split prefix refers to the addition of a more specific route, which will
be preferred over a less specific route. For example, if the border router
already has a route of 10.10.10.0/24, adding a static route of
10.10.10.128/25 will also cause the addresses 10.10.10.129-10.10.10.254 to
be forwarded using the newly injected route. If OER has been configured to
monitor a subset of a larger network, it will add an appropriate route to
the existing routing table. OER can use split prefixes to redirect subsets
of an existing prefix to a more optimal exit link, and can use split
prefixes for both internal BGP (iBGP) and static routes.

OER will never inject a route where one does not already exist in the
routing protocol table. Before injecting a route of a particular type, OER
will verify that a route exists in the BGP or static table that includes the
prefix and points to the exit link. This route may be a default route.

BGP Control Techniques

OER uses two BGP techniques to enforce the best exit path; injecting a BGP
route, or modifying the BGP local preference attribute.

If the traffic associated with the traffic class is defined only by a
prefix, the master controller can instruct a border router to inject a BGP
route into the BGP table to influence traffic to use a different link. All
OER injected routes remain local to an autonomous system, and these injected
routes are never shared with external BGP peers. As a safeguard to ensure
this behavior, when OER injects a BGP route, it will set the no-export
community on it. This is done automatically, and does not require any user
configuration. However, because these routes now have a special marking,
some extra configuration is required to allow the information to be shared
with internal BGP peers. For each iBGP peer, the send community
configuration must be specified. Although the border routers know about the
best exit for the injected route, it may also be necessary to redistribute
this information further into the network. For more details about
redistribution in an OER-managed network, see the "Setting Up OER Network
Components"<http://www.cisco.com/en/US/docs/ios/oer/configuration/guide/oer-s
etup_netw.html>
module.

OER also uses BGP local preference to control traffic classes. BGP local
preference (Local_Pref) is a discretionary attribute applied to a BGP prefix
to specify the degree of preference for that route during route selection.
The Local_Pref is a value applied to a BGP prefix, and a higher Local_Pref
value causes a route to be preferred over an equivalent route. The master
controller instructs one of the border routers to apply the Local_Pref
attribute to a prefix or set of prefixes associated with a traffic class.
The border router then shares the Local_Pref value with all of its internal
BGP peers. Local_Pref is a locally significant value within an autonomous
system, but it is never shared with external BGP peers. Once the iBGP
reconvergence is complete, the router with the highest Local_Pref for the
prefix will become the exit link from the network.

--
r/
LG
Blogs and organic groups at http://www.ccie.net