Step
2.
Configure
extended community
list.
Configuring a routing policy
Configuration prerequisites
Configure filters and routing protocols, and determine the routing policy name, node numbers, match
criteria, and the attributes to be modified.
Creating a routing policy
For a routing policy that has more than one node, configure a minimum of one permit node. A route
that does not match any node cannot pass the routing policy. If all the nodes are in deny mode, no
routes can pass the routing policy.
To create a routing policy:
Step
1.
Enter system view.
2.
Create a routing policy and a node, and
enter routing policy node view.
Configuring if-match clauses
You can either specify no if-match clauses or multiple if-match clauses for a routing policy node. If
no if-match clause is specified for a permit node, all routes can pass the node. If no if-match clause
is specified for a deny node, no routes can pass the node.
The if-match clauses of a routing policy node have a logical AND relationship. A route must meet all
if-match clauses before it can be executed by the apply clauses of the node. If an if-match
command exceeds the maximum length, multiple if-match clauses of the same type are generated.
These clauses have a logical OR relationship. A route only needs to meet one of them.
To configure if-match clauses:
Step
1.
Enter system view.
2.
Enter routing policy node view.
Command
an
ip
extcommunity-list
{ deny | permit } { rt route-target | soo
site-of-origin }&<1-32>
Command
system-view
route-policy
route-policy-name { deny |
permit } node node-number
Command
system-view
route-policy
{ deny | permit } node node-number
478
ext-comm-list-number
Remarks
N/A
By
policies exist.
Remarks
N/A
route-policy-name
N/A
Remarks
By default, no extended
community lists exist.
default,
no
routing