Defining If-Match Clauses - HP MSR2000 series Configuration Manual

Hide thumbs Also See for MSR2000 series:
Table of Contents

Advertisement

To create a routing policy:
Step
1.
Enter system view.
2.
Create a routing policy,
specify a node for it, and
enter routing policy view.

Defining if-match clauses

Follow these guidelines when you define if-match clauses:
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.
To define if-match clauses:
Step
1.
Enter system view.
2.
Enter routing policy view.
3.
Define match criteria for IPv4 routes.
4.
Match IPv6 routing information whose
next hop or source is specified in the ACL
or IP prefix list.
Command
system-view
route-policy route-policy-name { deny | permit } node node-number
Command
system-view
route-policy route-policy-name { deny
| permit } node node-number
Match IPv4 routing information
specified in the ACL:
if-match acl acl-number
Match IPv4 routing information
specified in the IP prefix list:
if-match ip-prefix ip-prefix-name.
Match IPv4 routing information
whose next hop or source is
specified in the ACL or IP prefix
list:
if-match ip { next-hop |
route-source } { acl acl-number |
ip-prefix ip-prefix-name }
if-match ipv6 { address | next-hop |
route-source } { acl acl-number |
prefix-list ipv6-prefix-name }
364
Remarks
N/A
N/A
Optional.
Not configured by
default.
Optional.
Not configured by
default.

Hide quick links:

Advertisement

Table of Contents
loading

This manual is also suitable for:

Msr3000 seriesMsr4000 series

Table of Contents