H3C Technologies H3C S7500E Series Switches - Manual (Page 366)

12-9
z The if-match clauses of a route policy node are in logic AND relationship, namely, routing
information has to satisfy all its if-match clauses before being executed with its apply clauses.
z You can specify no or multiple if-match clauses for a route policy node. If no if-match clause is
specified, and the route policy node is in permit mode, all routing information can pass the node.
If it is in deny mode, no routing information can pass it.
z An ACL specified in an if-match clause should be a non-VPN ACL.
z The if-match commands for matching IPv4 destination, next hop and source address are different
from those for matching IPv6 ones.
z BGP does not support criteria for matching against outbound interfaces of routing information.
Defining apply Clauses
Follow these steps to define apply clauses for a route policy:
To do… Use the command… Remarks
Enter system view system-view —
Enter route policy node view
route-policy route-policy-name
{ deny | permit } node
node-number
Required
Not created by default.
Set the AS-PATH attribute for BGP
routing information
apply as-path as-number&<1-10>
[ replace ]
Optional
Not set by default.
Delete the community attribute of
BGP routing information using the
community list
apply comm-list
comm-list-number delete
Optional
Not configured by default.
Set the community attribute for BGP
routing information
apply community { none |
additive |
{ community-number&<1-16> |
aa:nn&<1-16> | internet |
no-export-subconfed | no-export
| no-advertise } * [ additive ] }
Optional
Not set by default.
Set a cost for routing information apply cost [ + | - ] value
Optional
Not set by default.
Set a cost type for routing
information
apply cost-type [ external |
internal | type-1 | type-2 ]
Optional
Not set by default.