Table Of Contents
How to Configure PBR Recursive Next Hop
Setting the Recursive Next-Hop IP Address
Verifying the Recursive Next-Hop Configuration
Configuration Examples for PBR Recursive Next Hop
Recursive Next-Hop IP Address: Example
Feature Information for PBR Recursive Next Hop
PBR Recursive Next Hop
First Published: 2003Last Updated: May 4, 2009The PBR Recursive Next Hop feature enhances route maps to enable configuration of a recursive next-hop IP address that is used by policy-based routing (PBR). The recursive next-hop IP address is installed in the routing table and can be a subnet that is not directly connected. If the recursive next-hop IP address is not available, packets are routed using a default route.
Because Cisco Express Forwarding (CEF) or process switching provides the infrastructure, the benefit of this feature is the CEF loadsharing.
Finding Feature Information
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 PBR Recursive Next Hop" section.
Use Cisco Feature Navigator to find information about platform support and Cisco IOS XE 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
•
How to Configure PBR Recursive Next Hop
•
Configuration Examples for PBR Recursive Next Hop
•
Feature Information for PBR Recursive Next Hop
How to Configure PBR Recursive Next Hop
This section contains the following procedures:
•
Setting the Recursive Next-Hop IP Address (required)
•
Verifying the Recursive Next-Hop Configuration (optional)
Setting the Recursive Next-Hop IP Address
The infrastructure provided by CEF or process switching performs the recursion to the next-hop IP address. The configuration sequence, which affects routing, is as follows:
1.
Next-hop
2.
Next-hop recursive
3.
Interface
4.
Default next-hop
5.
Default interface
If both a next-hop address and a recursive next-hop IP address are present in the same route-map entry, the next hop is used. If the next hop is not available, the recursive next hop is used. If the recursive next hop is not available and no other IP address is present, the packet is routed using the default routing table; it is not dropped. If the packet is supposed to be dropped, use the set ip next-hop command with the recursive keyword, followed by a set interface null0 configuration.
Perform this task to set the IP address for the recursive next-hop router.
Prerequisites
If loadsharing is required, CEF loadsharing should be configured for per-packet or per-destination loadsharing. Loadbalancing should be done over all equal-cost routes to the subnet that has been configured by the set ip next-hop recursive command.
This functionality should be available in centralized and distributed systems.
Restrictions
Only one recursive next-hop IP address is supported per route-map entry.
SUMMARY STEPS
1.
enable
2.
configure terminal
3.
access-list access-list-number {deny | permit} source [source-wildcard] [log]
4.
route-map map-tag
5.
set ip next-hop ip-address
6.
set ip next-hop {ip-address [...ip-address] | recursive ip-address}
7.
match ip address access-list-number
8.
end
DETAILED STEPS
Verifying the Recursive Next-Hop Configuration
To verify the recursive next-hop configuration, perform the following steps.
SUMMARY STEPS
1.
show running-config | begin abccomp
2.
show route-map map-name
DETAILED STEPS
Step 1
show running-config | begin abccomp
Use this command to verify the IP addresses for a next-hop and recursive next-hop IP address, for example:
Router# show running-config | begin abccomproute-map abccomp permit 10match ip address 101 ! Defines the match criteria for an access list.set ip next-hop recursive 10.3.3.3 ! If the match criteria are met, the recursive IP address is set.set ip next-hop 10.1.1.1 10.2.2.2 10.4.4.4Step 2
show route-map map-name
Use this command to display the route maps, for example:
Router# show route-map abccomproute-map abccomp, permit, sequence 10Match clauses:ip address (access-lists): 101Set clauses:ip next-hop recursive 10.3.3.3ip next-hop 10.1.1.1 10.2.2.2 10.4.4.4Policy routing matches: 0 packets, 0 bytes
Configuration Examples for PBR Recursive Next Hop
This section provides the following configuration example:
•
Recursive Next-Hop IP Address: Example
Recursive Next-Hop IP Address: Example
The following example shows the configuration of IP address 10.3.3.3 as the recursive next-hop router:
route-map abccompset ip next-hop 10.1.1.1set ip next-hop 10.2.2.2set ip next-hop recursive 10.3.3.3set ip next-hop 10.4.4.4Additional References
The following sections provide references related to the PBR Recursive Next Hop feature.
Related Documents
Related Topic Document TitleIP routing commands: complete command syntax, command mode, command history, defaults, usage guidelines, and examples
Cisco IOS master command list, all releases
MIBs
Technical Assistance
Feature Information for PBR Recursive Next Hop
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 Cisco IOS XE 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 Cisco IOS XE software release that introduced support for a given feature in a given Cisco IOS XE software release train. Unless noted otherwise, subsequent releases of that Cisco IOS XE software release train also support that feature.
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, and 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.
© 2003-2009 Cisco Systems, Inc. All rights reserved.
