The nexthop recursive-lookup route-filter command configures route-filter-based next hop recursion.
The undo nexthop recursive-lookup route-filter command disables route-filter-based next hop recursion.
By default, route-filter-based next hop recursion is disabled.
| Parameter | Description | Value |
|---|---|---|
| route-filter route-filter-name |
Indicates the name of a route-filter. |
The value is a string of 1 to 200 case-sensitive characters, spaces not supported. If parameters are included in the referenced route-filter, specify values for them in the format of (var1, var2, ...var8) behind the route-filter name. A maximum of eight parameters can be specified, and each value ranges from 1 to 200 characters. |
Usage Scenario
BGP needs route recursion in case of next hops. If route recursion is not limited, BGP routes may be incorrectly iterated, causing traffic loss. Therefore, next hops should perform recursion according to certain conditions.
To control route recursion based on a route-filter, run the nexthop recursive-lookup route-filter command. If a target recursive route is filtered out by the route-filter, the route is considered unreachable. In this manner, BGP route recursion will fail.Prerequisites
The target recursive route has been determined, and a route-filter has been configured.
Note: Before configuring a route-filter, ensure that all desired target recursive routes will not be filtered out by the route-filter.Precautions
The command does not apply to the routes received from LinkLocal peers.
<HUAWEI> system-view [~HUAWEI] xpl route-filter aaa [~HUAWEI-xpl-filter] end-filter [*HUAWEI] bgp 100 instance a [*HUAWEI-bgp-instance-a] ipv4-family vpnv4 [*HUAWEI-bgp-instance-a-af-vpnv4] nexthop recursive-lookup route-filter aaa