Protocol Independent Features
Except on the first page, right running head:
Heading1 or Heading1NewPage text (automatic)
511
Alcatel-Lucent
Beta Beta
OmniAccess 5740 Unified Services Gateway CLI Configuration Guide
CONFIGURE ROUTE MAPS
Route-maps are an ordered sequence of individual statements, each having a
permit or deny result. Evaluation of route-maps consists of a list scan, in a
predetermined order, and an evaluation of the criteria of each statement that
matches. A list scan is stopped once the first statement match is found and an
action associated with the statement match is performed.
Route-maps frequently use Access-lists as matching criteria. Typical route-maps
not only permit (some) redistributed routes but also modify information associated
with the route. Route-maps are more flexible than ACLs and can verify routes
based on criteria. For example, a route-map can verify if the type of route is
internal or if it has a IP address.
During redistribution, if the route does not match any clause in a route-map then
the route redistribution is denied, as if the route-map contained deny statement at
the end.
Route-maps are preferred if you intend to either modify route information during
redistribution or if you need more powerful matching capability. Route-map is also
used for many different tasks like Border Gateway Protocol (BGP) neighbor
update modification.
E
XAMPLE
ALU(config)# route-map rip-to-ospf deny 10
ALU(config-route-map)# match ip address prefix-list test
ALU(config-route-map)# set route-type external type-1
ALU(config)# route-map ospf-to-eigrp permit 20
Command (in CM) Description
route-map < name> [ permit|deny]
[<1-65535>]
This command is used to configure route
maps to control route redistribution. It is
also used in BGP to set/match
community, as-path list, etc.
The range for the rule/sequence number
is 1-65535.
This sequence number signifies the
priority of a route-map rule.