3Com 8800 Configuration Manual page 268

3Com Switch 8800 Configuration Guide
Cancel the matched next-hop of the routing
information set by ACL
Cancel the matched next-hop of the routing
information set by address prefix list
Match the routing cost of the routing
information
Cancel the matched routing cost of the
routing information
Match the tag domain of the OSPF routing
information
Cancel the tag domain of the matched
OSPF routing information
By default, no matching will be performed.
Note the following:
The if-match clauses for a node in the route-policy have the relationship of "AND"
for matching. That is, the route must satisfy all the clauses to match the node
before the actions specified by the apply clauses can be executed.
If no if-match clauses are specified, all the routes will pass the filtering on the
node.
III. Defining apply clauses for a route-policy
The apply clauses specify actions, which are the configuration commands executed
after a route satisfies the filtering conditions specified by the if-match clauses. Thereby,
some attributes of the route can be modified.
Perform the following configuration in route policy view.
Table 22-3 Define apply clauses
Add the specified AS number before the
as-path series of the BGP routing
information
Cancel the specified AS number added
before the as-path series of the BGP
routing information
Set the community attribute in the BGP
routing information
Cancel the set community attribute in the
BGP routing information
Operation
Operation
22-5
Chapter 22 IP Routing Policy Configuration
Command
undo if-match ip next-hop
undo if-match ip next-hop ip-prefix
if-match cost value
undo if-match cost
if-match tag value
undo if-match tag
Command
apply as-path
[ as-number-2 [ as-number-3 ... ] ]
undo apply as-path
apply community
no-export-subconfed | no-export |
no-advertise ] * [ additive ] | additive |
none ]
undo apply community
as-number-1
[ [ aa:nn |