Step
11. Match routing information having the
specified route type.
12. Match RIP, OSPF, and IS-IS routing
information having the specified tag
value.
Configuring apply clauses
The difference between IPv4 and IPv6 apply clauses is the command for setting the next hop for
routing information.
To configure apply clauses for a routing policy:
Step
Enter system view.
1.
Enter routing policy view.
2.
Set the AS_PATH attribute for
3.
BGP routes.
Delete the COMMUNITY
4.
attribute of BGP routing
information using the
community list.
Set the COMMUNITY
5.
attribute for BGP routes.
Set a cost for routing
6.
information.
Set a cost type for routing
7.
information.
Set the extended community
8.
attribute for BGP routes.
Command
if-match route-type { external-type1 |
external-type1or2 | external-type2 |
internal | is-is-level-1 | is-is-level-2 |
nssa-external-type1 |
nssa-external-type1or2 |
nssa-external-type2 } *
if-match tag value
Command
system-view
route-policy route-policy-name
{ deny | permit } node
node-number
apply as-path as-number&<1-10>
[ replace ]
apply comm-list
{ comm-list-number |
comm-list-name } delete
apply community { none |
additive |
{ community-number&<1-16> |
aa:nn&<1-16> | internet |
no-advertise | no-export |
no-export-subconfed } *
[ additive ] }
apply cost [ + | - ] value
apply cost-type [ external |
internal | type-1 | type-2 ]
apply extcommunity { { rt
route-target }&<1-16> [ additive ] |
soo site-of-origin additive }
355
Remarks
Optional.
Not configured by
default.
Optional.
Not configured by
default.
Remarks
N/A
Not created by default.
Optional.
Not set by default.
Optional.
Not configured by default.
Optional.
Not set by default.
Optional.
Not set by default.
Optional.
Not set by default.
Optional.
Not set by default.