H3C Technologies H3C S12500 Series Switches - Manual (Page 426)

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