Specifications

Send document comments to [e-mail].
13-3
Cisco Nexus 3000 Series NX-OS Unicast Routing Configuration Guide, Release 5.0(3)U2(2)
OL-25782-02
Chapter 13 Configuring Route Policy Manager
Information About Route Policy Manager
Match Criteria
You can use a variety of criteria to match a route or IP packet in a route map. Some criteria, such as BGP
community lists, are applicable only to a specific routing protocol, while other criteria, such as the IP
source or the destination address, can be used for any route or IP packet.
When Cisco NX-OS processes a route or packet through a route map, it compares the route or packet to
each of the match statements configured. If the route or packet matches the configured criteria, Cisco
NX-OS processes it based on the permit or deny configuration for that match entry in the route map and
any set criteria configured.
The match categories and parameters are as follows:
• BGP parameters—Match based on AS numbers, AS-path, community attributes, or extended
community attributes.
• Prefix lists—Match based on an address or range of addresses.
• Multicast parameters—Match based on rendezvous point, groups, or sources.
• Other parameters—Match based on IP next-hop address or packet length.
Set Changes
Once a route or packet matches an entry in a route map, the route or packet can be changed based on one
or more configured set statements.
The set changes are as follows:
• BGP parameters—Change the AS-path, tag, community, extended community, dampening, local
preference, origin, or weight attributes.
• Metrics—Change the route-metric, the route-tag, or the route-type.
• Other parameters—Change the forwarding address or the IP next-hop address.
Access Lists
IP access lists can match the packet to a number of IP packet fields such as the following:
• Source or destination IPv4 address
• Protocol
• Precedence
• ToS
See the Cisco Nexus 7000 Series NX-OS Security Configuration Guide, Release 5.x, for more
information on ACLs.
AS Numbers for BGP
You can configure a list of AS numbers to match against BGP peers. If a BGP peer matches an AS
number in the list and matches the other BGP peer configuration, BGP creates a session. If the BGP peer
does not match an AS number in the list, BGP ignores the peer. You can configure the AS numbers as a
list, a range of AS numbers, or you can use an AS-path list to compare the AS numbers against a regular
expression.