route-policy

Function

The route-policy command creates a route-policy and displays the Route-policy view.

The undo route-policy command deletes the created route-policy.

By default, no route-policy is created.

Format

route-policy route-policy-name matchMode node node

undo route-policy route-policy-name [ node node ]

Parameters

Parameter	Description	Value
route-policy-name	Specifies the name of the route-policy.	The name is a string of 1 to 200 case-sensitive characters, with spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string.
matchMode	Specifies the matching mode of the route-policy.	The value is an enumerated type: permit: Specifies the matching mode of the route-policy as permit. deny: Specifies the matching mode of the route-policy as deny.
node node	Specifies the index of the node in the route-policy.	The value is an integer ranging from 0 to 65535. When the route-policy is used to filter routes, the node with the smaller value is matched against first.

Parameter

Description

Value

route-policy-name

Specifies the name of the route-policy.

The name is a string of 1 to 200 case-sensitive characters, with spaces not supported. When double quotation marks are used around the string, spaces are allowed in the string.

matchMode

Specifies the matching mode of the route-policy.

The value is an enumerated type:

permit: Specifies the matching mode of the route-policy as permit.
deny: Specifies the matching mode of the route-policy as deny.

node node

Specifies the index of the node in the route-policy.

The value is an integer ranging from 0 to 65535. When the route-policy is used to filter routes, the node with the smaller value is matched against first.

Views

System view

Default Level

2: Configuration level

Task Name and Operations

Task Name	Operations
route-base	write

Usage Guidelines

Usage Scenario

A route-policy is used to filter routes and set route attributes for the routes that match the route-policy. A route-policy consists of multiple nodes. One node can be configured with multiple if-match and apply clauses. The if-match clauses define filtering rules for this node, and the apply clauses define behaviors for the routes that match the rules.

The relationship among if-match clauses of the same node that are based on different route attributes is AND. A route matches a node only when the route matches all the filtering rules specified in the if-match clauses of the node. The apply clauses specify actions. The relationship among if-match clauses of the same node that are based on the same route attribute is OR. The system matches routes against the if-match clauses in order. If a route matches an if-match clause, the system no longer matches the route against the rest if-match clauses. For example, the if-match community-filter 1 and if-match as-path-filter 1 configurations in node 10 are based on different route attributes. Therefore, the relationship among if-match clauses of this node is AND. The if-match community-filter 1 and if-match community-filter 2 configurations in node 20 are both based on the community attribute. Therefore, the relationship among if-match clauses of this node is OR. If no if-match clause is specified, all the routes can pass the node.

The relationship between the nodes of a route-policy is "OR". That is, if a route matches one node, the route matches the route-policy. If the route does not match any node, the route fails to match the route-policy.

Precautions

You can run the display route-policy command to view the number of routes permitted or denied by the route-policy.
If the Route-Policy clause contains only the ip-prefix matching condition, only the IPv4 address prefix is checked. If the IPv6 address prefix matching condition is empty, all routes match the route-policy by default. If IPv6 prefixes also need to be filtered, add an ipv6-prefix-based if-match clause. Similarly, if the Route-Policy clause contains only the ipv6-prefix matching condition, only the IPv6 address prefix is checked. If the IPv4 address prefix matching condition is empty, all routes match the route-policy by default. If IPv4 prefixes also need to be filtered, add an ip-prefix-based if-match clause.
When a routing policy is used to control the advertisement or receiving of BGP routes, the priority of the BGP peer is higher than that of the peer group.

Example

# Configure the route-policy named policy1 whose node number is 10 and matching mode is permit.

<HUAWEI> system-view
[~HUAWEI] ip ip-prefix prefix-a index 10 permit 172.17.1.0 24
[*HUAWEI] route-policy policy1 permit node 10
[*HUAWEI-route-policy] if-match ip-prefix prefix-a
[*HUAWEI-route-policy] apply cost 100