HP 6125XLG R2306-HP 6125XLG Blade Switch Layer 3 - IP Routing Configuration Gu - Page 359
Configuring if-match clauses
View all HP 6125XLG manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 359 highlights
Configuring if-match clauses You can either specify no if-match clauses or multiple if-match clauses for a routing policy node. If no if-match clause is specified for a permit-mode node, all routing information can pass the node. If no if-match clause is specified for a deny-mode node, no routing information can pass the node. The if-match clauses of a routing policy node have a logical AND relationship. A route must satisfy all if-match clauses before it can be executed by the apply clauses of the node. If an if-match command exceeds the maximum length, multiple identical if-match clauses are generated. These clauses have a logical OR relationship. A route only needs to match one of them. To configure if-match clauses: Step Command 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 • Match IPv4 routes whose By default, no IPv4 or IPv6 destination, next hop, or source matches the IPv4 prefix list: prefix list match criterion is configured. if-match ip { address | next-hop | If the ACL used by an if-match route-source } { acl acl-number | clause does not exist, the 3. Match routes whose destination, prefix-list prefix-list-name } clause is always satisfied. If next hop, or source matches a • Match IPv6 routes whose no rules of the specified ACL specified prefix list. destination, next hop, or source are matched or the match matches the IPv6 prefix list: rules are inactive, the clause if-match ipv6 { address | is not satisfied. next-hop | route-source } { acl acl6-number | prefix-list prefix-list-name } The ACL specified in an if-match clause must be a non-VPN ACL. 4. Match BGP routes whose AS_PATH attribute matches a specified AS path list. if-match as-path as-path-number& By default, no AS path match criterion is configured. if-match community 5. Match BGP routes whose { { basic-community-list-number | COMMUNITY attribute matches name comm-list-name } a specified community list. [ whole-match ] | By default, no COMMUNITY match criterion is matched. adv-community-list-number }& 6. Match routes having the specified cost. 7. Match BGP routes whose extended community attribute matches a specified extended community list. if-match cost value if-match extcommunity ext-comm-list-number& By default, no cost match criterion is configured. By default, no extended community list match criterion is configured. 8. Match routes having the specified output interface. if-match interface { interface-type interface-number }& By default, no output interface match criterion is configured. This command is not supported by BGP. 348