ip extcommunity-list segmented-nh advanced

Function

The ip extcommunity-list segmented-nh advanced command configures a segmented-nh attribute, which is an advanced extended community attribute.

The undo ip extcommunity-list segmented-nh advanced command deletes a segmented-nh attribute.

By default, no segmented-nh attribute is configured.

Format

ip extcommunity-list segmented-nh advanced segmented-nh-name [ index index-value ] matchMode regular

undo ip extcommunity-list segmented-nh advanced segmented-nh-name [ index index-value ]

Parameters

Parameter	Description	Value
segmented-nh-name	Sets a name for a segmented-nh attribute list.	The value is a string of 1 to 51 characters.
index index-value	Specifies a sequence number.	The value is an integer ranging from 1 to 4294967295.
matchMode	Sets the matching mode of the extended community filter.	The value is an enumerated type: permit: Indicates the permit match mode. deny: Indicates the deny match mode.
regular	Sets a regular expression for a segmented-nh attribute.	The value is a string of 1 to 1024 characters, in the text format.
advanced	Indicates an advanced extended community attribute.	-

Views

System view

Default Level

2: Configuration level

Task Name and Operations

Task Name	Operations
route-base	write

Usage Guidelines

Usage Scenario

In an NG MVPN scenario using segmented tunnels, to configure a segmented-nh (with the full name being segmented next-hop) attribute for intra-AS I-PMSI A-D routes, run the ip extcommunity-list segmented-nh command.

Precautions

The name of a basic segmented-nh extended community attribute and that of an advanced segmented-nh extended community attribute are mutually exclusive.

For an advanced segmented-nh extended community filter, if the segmented-nh attribute is set to be in the format of 4-byte AS number:2-byte user-defined number, the filtering rule that uses the segmented-nh-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 an advanced segmented-nh attribute with the sequence number being bb.

<HUAWEI> system-view
[~HUAWEI] ip extcommunity-list segmented-nh advanced bb deny 0755:*