Supported Route Map Statements by Protocol
Some statements affect only a particular protocol, for example, matching the Autonomous System Number is applicable only to BGP.
If such a condition is in a routemap used by OSPF, the match condition is ignored.
Any non-applicable match conditions or actions are ignored and processing is done as if they do not exist.
A log message is written in the /var/log/messages
file for any such statements.
|
Note - The same parameter cannot appear both as a match and action statement in a routemap. These include Community, Metric, and Nexthop. |
RIP
Category |
Supported Statements |
---|---|
Import Match conditions |
|
Import Actions |
|
Export Match conditions when exporting from RIP |
|
Export Match Conditions when redistributing using Protocol match |
According to the protocol, from which route is being redistributed |
Export Actions when exporting from RIP |
|
Export Actions when redistributing |
|
OSPFv2 and OSPFv3
Category |
Supported Statements |
---|---|
Import Match conditions |
|
Import Actions |
|
Export Match conditions when other protocols redistribute OSPF routes |
|
Export Match conditions when OSPF redistributes routes from other protocols |
According to the conditions supported by that protocol |
Export Actions when redistributing to AS External |
|
BGP
When you perform initial configuration:
-
Configure the Router ID.
-
Configure the local autonomous system number of the router:
set as {<BGP AS Number> | off}
Parameter
Description
<BGP AS Number>
The local autonomous system number of the router.
This number is mutually exclusive from the confederation and routing domain identifier.
The router can be configured with either the autonomous system number or confederation number, not both.
Warning - When you change the autonomous system number, all current peer sessions are reset and all BGP routes are deleted.
off
Precedence