![]() |
IP Routing: Protocol-Independent Configuration Guide, Cisco IOS XE Release 2
|
||||||||||||||||||||
PBR Support for Multiple Tracking Options
![]() |
|||||||||||||||||||||
Contents
PBR Support for Multiple Tracking OptionsLast Updated: April 30, 2012
The PBR Support for Multiple Tracking Options feature extends the capabilities of object tracking using Cisco Discovery Protocol to allow the policy-based routing (PBR) process to verify object availability by using additional methods. The verification method can be an Internet Control Message Protocol (ICMP) ping, a User Datagram Protocol (UDP) ping, or an HTTP GET request.
Finding Feature InformationYour 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 Table at the end of this document. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required. Information About PBR Support for Multiple Tracking OptionsObject TrackingObject tracking is an independent process that monitors objects such as the following:
Clients such as Hot Standby Router Protocol (HSRP), Virtual Router Redundancy Protocol (VRRP), Gateway Load Balancing Protocol (GLBP), and (with this feature) PBR can register their interest in specific, tracked objects and then take action when the state of the objects changes. PBR Support for Multiple Tracking Options Feature DesignThe PBR Support for Multiple Tracking Options feature gives PBR access to all the objects that are available through the tracking process. The tracking process provides the ability to track individual objects--such as ICMP ping reachability, routing adjacency, an application running on a remote device, a route in the Routing Information Base (RIB)--or to track the state of an interface line protocol. Object tracking functions in the following manner. PBR will inform the tracking process that a certain object should be tracked. The tracking process will in turn notify PBR when the state of that object changes. How to Configure PBR Support for Multiple Tracking OptionsConfiguring PBR Support for Multiple Tracking OptionsPerform this task to configure PBR support for multiple tracking options. In this task, a route map is created and configured to verify the reachability of the tracked object. DETAILED STEPS ExamplesThe following output from the show track command shows that the tracked object 123 is reachable.
Router# show track 123
Track 123
Response Time Reporter 1 reachability
Reachability is Up
2 changes, last change 00:00:33
Delay up 60 secs, down 30 secs
Latest operation return code: OK
Latest RTT (millisecs) 20
Tracked by:
ROUTE-MAP 0
The following output from the show route-map command shows information about the route map named alpha that was configured in the task.
Router# show route-map alpha
route-map alpha, permit, sequence 10
Match clauses:
Set clauses:
ip next-hop verify-availability 10.1.1.1 10 track 123 [up]
Policy routing matches: 0 packets, 0 bytes
Configuration Examples for PBR Support for Multiple Tracking OptionsConfiguring PBR Support for Multiple Tracking Options ExampleThe configured policy is that packets received on GigabitEthernet interface 0/0/0 should be forwarded to 10.1.1.1 only if that device is reachable (responding to pings). If 10.1.1.1 is not up, then the packets should be forwarded to 10.2.2.2. If 10.2.2.2 is also not reachable, then the policy routing fails and the packets are routed according to the routing table. Two RTRs are configured to ping the remote devices. The RTRs are then tracked. Policy routing will monitor the state of the tracked RTRs and make forwarding decisions based on their state. ! Define and start the RTRs. ip sla monitor 1 type echo protocol ipicmpecho 10.1.1.1 ip sla monitor schedule 1 start-time now life forever ! ip sla monitor 2 type echo protocol ipicmpecho 10.2.2.2 ip sla monitor schedule 2 start-time now life forever ! ! Track the RTRs. track 123 rtr 1 reachability track 124 rtr 2 reachability ! ! Enable policy routing on the incoming interface. interface gigabitethernet 0/0/0 ip address 10.4.4.4 255.255.255.0 ip policy route-map beta ! ! 10.1.1.1 is via this interface. interface gigabitethernet 1/0/0 ip address 10.1.1.254 255.255.255.0 ! ! 10.2.2.2 is via this interface. interface gigabitethernet 2/0/0 ip address 10.2.2.254 255.255.255.0 ! ! Define a route map to set the next-hop depending on the state of the tracked RTRs. route-map beta set ip next-hop verify-availability 10.1.1.1 10 track 123 set ip next-hop verify-availability 10.2.2.2 20 track 124 Additional ReferencesThe following sections provide references related to the PBR Support for Multiple Tracking Options feature. Related Documents
MIBsTechnical Assistance
Feature Information for PBR Support for Multiple Tracking OptionsThe following table provides release information about the feature or features described in this module. This table 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. Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: 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. (1110R) 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. © 2012 Cisco Systems, Inc. All rights reserved.
|
|||||||||||||||||||||
|
|