Defining Apply Clauses - HP 3600 v2 series Configuration Manual

To do...
Match BGP routing information whose
community attribute is specified in the
community lists
Match routes having the specified cost
Match BGP routing information whose
extended community attribute is specified in
the extended community list(s)
Match routing information having specified
outbound interface(s)
Match routing information having the specified
route type
Match RIP, OSPF, and IS-IS routing information
having the specified tag value
NOTE:
The if-match clauses of a routing policy node are in logic AND relationship. Routing information must
•
satisfy all of its if-match clauses before being executed with its apply clauses. If an if-match command
exceeds the maximum length, multiple identical if-match clauses are generated. These clauses are in
logical OR relationship. Routing information only needs to match one of them.
You can specify any number of if-match clauses for a routing policy node. If no if-match clause is
•
specified, and the routing 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.
If the ACL referenced by an if-match clause does not exist, the clause is always satisfied; if no rules of the
•
referenced ACL are matched or the matching rule is inactive, the clause is not satisfied.
• An ACL specified in an if-match clause must be a non-VPN ACL.
The if-match commands for matching IPv4 destination, next hop, and source address are different from
•
those for matching IPv6 ones.
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 routing policy:
To do...
Enter system view
Use the command...
if-match community
{ { basic-community-list-number |
comm-list-name } [ whole-match ] |
adv-community-list-number }&<1-16>
if-match cost value
if-match extcommunity
ext-comm-list-number&<1-16>
if-match interface { interface-type
interface-number }&<1-16>
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
Use the command...
system-view
367
Remarks
Optional
Not configured by
default.
Optional
Not configured by
default.
Optional
Not configured by
default.
Optional
Not configured by
default.
Optional
Not configured by
default.
Optional
Not configured by
default.
Remarks
—