The route recursive-lookup tunnel command configures the unlabeled routes of the public network to iterate to LSP tunnels.
The undo route recursive-lookup tunnel command restores the default configuration.
By default, the unlabeled routes can iterate to only an outgoing interface and the next hop instead of an LSP tunnel.
route recursive-lookup tunnel [ ip-prefix ip-prefix-name ]
undo route recursive-lookup tunnel
| Parameter | Description | Value |
|---|---|---|
ip-prefix ip-prefix-name |
Specifies the name of an IP prefix list. After the parameter is configured, only the unlabeled routes matching the specified IP prefix list can iterate to LSP tunnels. If you do not specify this parameter, the route recursive-lookup tunnel command takes effect on all the unlabeled routes of a public network. |
The name is a string of 1 to 169 characters. |
Usage Scenario
In a carrier MPLS L3VPN scenario, provider carrier CEs can iterate non-labeled public routes to only outbound interfaces and next hops. Therefore, public traffic is forwarded using IP instead of MPLS between customer carrier devices. To solve this problem, run the route recursive-lookup tunnel command to iterate non-labeled public routes to LSPs.
If you specify the ip-prefix ip-prefix-name parameter, only the non-labeled routes matching the specified IP prefix list are iterated to LSP tunnels. If you do not specify the ip-prefix ip-prefix-name parameter, all non-labeled routes are iterated to LSP tunnels.
Prerequisites
An IP prefix list is configured using the ip ip-prefix command.
Precautions
If the route recursive-lookup tunnel command is run more than once, the latest configuration overrides the previous one.
Creating an IP prefix list before it is referenced is recommended. By default, nonexistent IP prefix lists cannot be referenced using the command. If the route-policy nonexistent-config-check disable command is run in the system view and a nonexistent IP prefix list is referenced using the current command, all routes match the IP prefix list.