match ipv6 address prefix-list-name
• Match next-hop routes specified in a prefix list (IPv4).
CONFIG-ROUTE-MAP mode
match ip next-hop {access-list-name | prefix-list prefix-list-name}
• Match next-hop routes specified in a prefix list (IPv6).
CONFIG-ROUTE-MAP mode
match ipv6 next-hop {access-list-name | prefix-list prefix-list-name}
• Match source routes specified in a prefix list (IPv4).
CONFIG-ROUTE-MAP mode
match ip route-source {access-list-name | prefix-list prefix-list-name}
• Match source routes specified in a prefix list (IPv6).
CONFIG-ROUTE-MAP mode
match ipv6 route-source {access-list-name | prefix-list prefix-list-name}
• Match routes with a specific value.
CONFIG-ROUTE-MAP mode
match metric metric-value
• Match BGP routes based on the ORIGIN attribute.
CONFIG-ROUTE-MAP mode
match origin {egp | igp | incomplete}
• Match routes specified as internal or external to OSPF, ISIS level-1, ISIS level-2, or locally generated.
CONFIG-ROUTE-MAP mode
match route-type {external [type-1 | type-2] | internal | level-1 | level-2 |
local }
• Match routes with a specific tag.
CONFIG-ROUTE-MAP mode
match tag tag-value
To create route map instances, use these commands. There is no limit to the number of match
commands per route map, but the convention is to keep the number of match filters in a route map low.
Set commands do not require a corresponding match command.
Configuring Set Conditions
To configure a set condition, use the following commands.
• Add an AS-PATH number to the beginning of the AS-PATH.
CONFIG-ROUTE-MAP mode
set as-path prepend as-number [... as-number]
• Generate a tag to be added to redistributed routes.
CONFIG-ROUTE-MAP mode
set automatic-tag
Access Control Lists (ACLs)
103
To Next Page
Loading...
Need help?
General