Remarks
9. Match BGP routes having the
specified local preference.
if-match local-preference preference
By default, no local
preference is configured for
BGP routes.
10. Match routes having the
specified route type.
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 } *
By default, no route type
match criterion is configured.
11. Match RIP, OSPF, and IS-IS
routes having the specified tag
value.
if-match tag value
By default, no tag match
criterion is configured.
Configuring apply clauses
Except for the apply commands used for setting the next hop for IPv4 and IPv6 routes, all apply
commands are the same for IPv4 and IPv6 routing.
To configure apply clauses:
Ste
Remarks
1. Enter system view.
system-view N/A
2. Enter routing policy node view.
route-policy route-policy-name
{ deny | permit } node
node-number
N/A
3. Set the AS_PATH attribute for
BGP routes.
apply as-path
as-number&<1-32> [ replace ]
By default, no AS_PATH attribute is
set for BGP routes.
4. Delete the specified
COMMUNITY attribute for
BGP routes.
apply comm-list
{ comm-list-number |
comm-list-name } delete
By default, no COMMUNITY
attribute is deleted for BGP routes.
5. Set the specified COMMUNITY
attribute for BGP routes.
apply community { none |
additive |
{ community-number&<1-32> |
aa:nn&<1-32> | internet |
no-advertise | no-export |
no-export-subconfed } *
[ additive ] }
By default, no community attribute is
set for BGP routes.
6. Set a cost for routes.
apply cost [ + | - ] value By default, no cost is set for routes.
7. Set a cost type for routes.
apply cost-type { external |
internal | type-1 | type-2 }
By default, no cost type is set for
routes.
8. Set the extended community
attribute for BGP routes.
apply extcommunity { rt
route-target }&<1-32>
[ additive ]
By default, no extended community
attribute is set for BGP routes.