1-5
z
Name of the route policy, and node numbers
z
Match criteria
z
Attributes to be modified
Creating a Route Policy
Follow these steps to create a route policy:
To do…
Use the command…
Remarks
Enter system view
system-view
—
Create a route policy, specify a
node for it and enter route
policy node view
route-policy
route-policy-name
{
permit
|
deny
}
node
node-number
Required
z
If a route policy node has the
permit
keyword specified, routing information matching all the
if-match
clauses of the node will be handled using the
apply
clauses of this node, without needing
to match against the next node. If routing information does not match the node, it will go to the next
node for a match.
z
If a route policy node has the
deny
keyword specified, the
apply
clauses of the node will not be
executed. When routing information matches all the
if-match
clauses of the node, it cannot pass
the node, or go to the next node. If route information cannot match all the
if-match
clauses of the
node, it will go to the next node for a match.
z
When a route policy has more than one node, at least one node should be configured with the
permit
keyword. If the route policy is used to filter routing information, routing information that does
not meet any node cannot pass the route policy. If all nodes of the route policy are set with the
deny
keyword, no routing information can pass it.
Defining if-match Clauses
Follow these steps to define if-match clauses for a route-policy node:
To do…
Use the command…
Remarks
Enter system view
system-view
—
Enter route policy node view
route-policy
route-policy-name
{
permit
|
deny
}
node
node-number
Required
Match IPv4 routing
information specified in
the ACL
if-match
acl acl-number
Define
match
criteria
for IPv4
routes
Match IPv4 routing
information specified in
the IP prefix list
if-match ip-prefix
ip-prefix-name
Optional
Not configured by default.
