edit xpl extcommunity-list rt

Function

The edit xpl extcommunity-list rt command displays the route target set paragraph editing interface view.

By default, no route target sets are configured.

Format

edit xpl extcommunity-list rt rt-list-name

Parameters

Parameter	Description	Value
rt-list-name	Specifies the name of a route target set.	The value is a string of 1 to 200 case-sensitive characters, spaces not supported. The string can contain letters, digits, underscores (_), hyphens (-), and dots (.). It must start with a letter or digit.

Parameter

Description

Value

rt-list-name

Specifies the name of a route target set.

The value is a string of 1 to 200 case-sensitive characters, spaces not supported. The string can contain letters, digits, underscores (_), hyphens (-), and dots (.). It must start with a letter or digit.

Views

User view

Default Level

2: Configuration level

Task Name and Operations

Task Name	Operations
route-base	write

Usage Guidelines

Usage Scenario

A route target set is a group of data related to the route target (RT) extended community attribute and can be used by route-filters to filter VPN routes. To enter the route target set paragraph editing interface view, run the edit xpl extcommunity-list rt command.

Implementation Procedure

To configure a route target set in the route target set paragraph editing interface view, perform the following steps:

Configure a start clause (xpl extcommunity-list rt rt-list-name) for the route target set.
Configure elements for the set and separate every two neighboring elements with a comma (,). The elements can be configured in any of the following formats:
- 2-byte AS number:4-byte user-defined number, for example, 1:3. The AS number is an integer ranging from 0 to 65535, and the user-defined number is an integer ranging from 0 to 4294967295.
- IPv4 address:2-byte user-defined number, for example, 192.168.122.15:1. The IPv4 address ranges from 0.0.0.0 to 255.255.255.255, and the user-defined number is an integer ranging from 0 to 65535.
- Integral 4-byte AS number:2-byte user-defined number, for example, 0:3 or 65537:3. The integral 4-byte AS number ranges from 65536 to 4294967295, and the user-defined number is an integer ranging from 0 to 65535.
- 4-byte AS number in dotted notation (x.y):2-byte user-defined number, for example, 0.0:3 or 0.1:0. The x, y, and user-defined number are integers ranging from 0 to 65535.
- regular regular-expression: matches VPN routes with RTs in the specified regular expression. For detailed description about regular expressions, see Configuration Guide - Basic Configuration.
  In the preceding elements, either value around a colon (:) can be replaced by an asterisk (*) to match any value.
  Regular expression processing is computing-intensive. When a large number of regular expressions are configured in an XPL policy to match a BGP route attribute and the length of the route attribute is long, the processing performance of the XPL policy deteriorates. To improve the processing performance of the routing policy, decrease the number of regular expressions or use a non-regular expression matching command.
  It is recommended that a maximum of 100 regular expressions be configured for each policy.
Configure an end clause (end-list) for the route target set.

Precautions

A route target set is only a group of data used as matching rules and does not have the permit or deny function. Therefore, a route target set can be used to filter routes only after it is referenced by a route-filter.

If the VPN-Target attribute is set to be in the format of 4-byte AS number:2-byte user-defined number, the filtering rule that uses the VPN-Target-based regular expression is affected by the as-notation plain command:

If the as-notation plain command is run, route matching can succeed only after the regular expression is set to be in the format of integral 4-byte AS number:2-byte user-defined number.
If the as-notation plain command is not run, route matching can succeed only after the regular expression is set to be in the format of 4-byte AS number in dotted notation:2-byte user-defined number.
Note: If the as-notation plain command is run after the regular expression is configured, you need to reconfigure the regular expression; otherwise, route matching may fail against an import or export route-policy, causing a network fault.

Example

# Configure a route target set named aaa.

<HUAWEI> edit xpl extcommunity-list rt aaa
xpl extcommunity-list rt aaa
2:1,
2:12,
192.168.122.15:1,
regular ^10:?3
end-list